Description of problem: There should be a cockpit plugin to start the hosted.engine-setup on the first host. The UI of the plugin should do everything inside cockpit, there should not be any need to drop to shell or alike. Additional hosts can be deployed from Engine.
(In reply to Fabian Deutsch from comment #0) > Description of problem: > There should be a cockpit plugin to start the hosted.engine-setup on the > first host. > The UI of the plugin should do everything inside cockpit, there should not > be any need to drop to shell or alike. > > Additional hosts can be deployed from Engine. As well as provide status on the HE VM, etc. With a bit of luck, perhaps it can do the deploy on other hosts as well...
This basically works. Patch is pending upstream (with some small amounts of cosmetic work still going into it), but: hosted-engine setup works The elements are hidden until a "Start Setup" button is pressed. INFO, WARNING, and ERROR messages are propagated to patternfly messages. Unclassified output is sent to a textbox. The input field is pre-populated if a suggested input is part of the output (Yes/No) [Yes]:, for example. The input field is flagged as invalid if hosted-engine setup returns an error from some value. There's a copr at https://copr.fedorainfracloud.org/coprs/rbarry/cockpit-ovirt/ hosting the results (updated when a patch is submitted) until it merges upstream.
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.
Start the hosted.engine-setup on the first host is basically worked in rhev-hypervisor7-ng-4.0-20160527.0(cockpit-ovirt-dashboard-0.10.1-0.0.1.el7ev.noarch) now. But it still has some detail issue need to be fixed. Due to this is a RFE bug, we prefer to verify this issue and let detail bugs to track the specific issues.
oVirt 4.0.0 has been released, closing current release.