In RHEV 3.6, users can now add new HE hosts via the Admin Portal. The process for doing so much be documented, and is a good candidate for the SHE Guide.
This feature was pushed for 4.0. Changing target, I updated the beta priorities to make sure we do not have more ticket like this one.
Hi Yaniv, Thank you for the heads up - I have removed the beta tag from the title, and we will target this one for RHEV 4.0 instead. Kind regards, Andrew
oVirt 4.0 Alpha has been released, moving to oVirt 4.0 Beta target.
Adding doc text in this bug, so it can be used to capture the deprecated functionality part that comes with this feature.
Assigning to Megan for review.
A quick note that the REST API part of this functionality is tracked in bug 1351677.
Hi, We would like to be proactive and create a kcs on this as well. What would happen if you run # 'hosted-engine --deploy' On an existing setup? Would it cause any harm or it will simply fail? Roy, can you help please?
(In reply to Marina from comment #20) > Hi, > We would like to be proactive and create a kcs on this as well. > > What would happen if you run > # 'hosted-engine --deploy' > On an existing setup? > > Would it cause any harm or it will simply fail? > Roy, can you help please? Currently it will work as in 3.6 without any warning. The mani concern is that, as in 3.6, choosing the host ID is up to the user who has to manually sync with the engine to avoid conflicts. Deploying from the engine instead implicitly resolves this issue.
(In reply to Marina from comment #20) > Hi, > We would like to be proactive and create a kcs on this as well. > > What would happen if you run > # 'hosted-engine --deploy' > On an existing setup? > > Would it cause any harm or it will simply fail? > Roy, can you help please? For more info on comment 21 see the summary here https://bugzilla.redhat.com/show_bug.cgi?id=1322849#c28
Are there any plans to block this command line option or we just keep it as not recommended? If the second, we should add a warning before running it, saying that: - it is not recommended, the UI way is the correct one and that the user should be careful choosing host id. Or something between those lines. If such bug does not exist yet, I'd be happy to file one. Otherwise customers will run it the way they are used to and we may have issues with that, based on what I am reading in the bug.
(In reply to Marina from comment #23) > Are there any plans to block this command line option or we just keep it as > not recommended? We don't test it anymore and we will not support it. We will be removing those options in the 4.1. > If the second, we should add a warning before running it, saying that: > - it is not recommended, the UI way is the correct one and that the user > should be careful choosing host id. Or something between those lines. > > If such bug does not exist yet, I'd be happy to file one. > Otherwise customers will run it the way they are used to and we may have > issues with that, based on what I am reading in the bug. Please do.
Yaniv, How about cockpit RHV-H UI? People reported they used that option and found it convenient. But I believe this bug also applies to cockpit.
https://bugzilla.redhat.com/show_bug.cgi?id=1376114
(In reply to Marina from comment #25) > Yaniv, > > How about cockpit RHV-H UI? > People reported they used that option and found it convenient. But I believe > this bug also applies to cockpit. Yes, only via engine.
The documentation for this bug is now available here: https://access.redhat.com/documentation/en/red-hat-virtualization/4.0/single/self-hosted-engine-guide/#chap-Installing_Additional_Hosts_to_a_Self-Hosted_Environment