Bug 1874905

Summary:	Add documentation on upgrading Websocket-Proxy on separate host
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Sandro Bonazzola <sbonazzo>
Component:	Documentation	Assignee:	Steve Goodman <sgoodman>
Status:	CLOSED WONTFIX	QA Contact:	Lucie Leistnerova <lleistne>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.4.1	CC:	didi, lsurette, mhicks, sgoodman, srevivo
Target Milestone:	---	Keywords:	Documentation, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-24 12:32:44 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Integration	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Sandro Bonazzola 2020-09-02 14:48:31 UTC

Description of problem:
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html/upgrade_guide/index
doesn't document how to upgrade Websoket-Proxy running on separate host.

Comment 1 Sandro Bonazzola 2020-09-10 07:27:00 UTC

Here the flow should be more or less like:
- take a backup on el7
- reinstall on el8 with websocket only
- restore the backup

PKI and configuration should be restored properly at this point, engine-setup may still be required.

Comment 2 Steve Goodman 2020-09-10 09:14:02 UTC

(In reply to Sandro Bonazzola from comment #1)
> Here the flow should be more or less like:
> - take a backup on el7
> - reinstall on el8 with websocket only

Can this host be the same host as the remote DWH machine (if there is one)? Can this host be used as a hypervisor as well as hosting the proxy?

Comment 3 Sandro Bonazzola 2020-10-15 08:50:27 UTC

(In reply to Steve Goodman from comment #2)
> (In reply to Sandro Bonazzola from comment #1)
> > Here the flow should be more or less like:
> > - take a backup on el7
> > - reinstall on el8 with websocket only
> 
> Can this host be the same host as the remote DWH machine (if there is one)?

Yes it can

> Can this host be used as a hypervisor as well as hosting the proxy?

No, websocket proxy shouldn't be on the hypervisor hosts. It's better to not mix RHV-M channels with hosts channels.

Comment 4 Steve Goodman 2020-10-26 15:54:18 UTC

Didi,

Can you provide any more details on this?

Comment 5 Sandro Bonazzola 2020-11-24 12:32:44 UTC

Closing this bug as won't fix. It has been decided to drop the effort of maintaining the possibility to install websocket proxy on separate host.

Comment 6 Yedidyah Bar David 2020-11-26 14:21:34 UTC

I didn't test, but I think comment 1 is mostly correct.

Not sure there is much value in this, though - it's probably easier to just install a new websocket-proxy on a new machine against the upgraded engine. This requires testing as well.