This release introduces a new alternative deployment flow for self-hosted engines. The new flow will use the current engine code to create all entities needed for successful self-hosted engine deployment.
A local bootstrap VM with the RHV-M Appliance will be created on the host and hosted-engine-setup will use it (via Ansible) to add a host (the same one it is running on), storage domain, storage disks, and finally a VM that will later become the Manager VM in the engine (thus eliminating the need for importing it).
Once all the entities are created, hosted-engine-setup can shut down the bootstrap VM, copy its disk to the disk it created using the engine, create the self-hosted engine configuration files, start the agent and the broker, and the Manager VM will start.
Feature page: https://github.com/oVirt/ovirt-site/pull/1273/files
From the feature page:
All of this will be implemented using an Ansible script.
The current answer file will need to be converted to an Ansible vars file.
The configuration files will be created using Ansible templates and then packaged and copied to the correct location.
To run the script install Ansible and run:
The script will install all the packages and will start the deployment.
For now, the vars file needs to be populated manually. Later the user's answers in the setup stage will be used to populate the values.
The RFE on which this depends is currently ON_QA. Given the fact that this is a new flow, it probably makes sense to wait until the flow is verified before beginning to document it.
Accepting into GA program and assigning to Tahlia for review.
After further reading, bumping up the time estimate for testing and chapter restructure.
*** Bug 1573751 has been marked as a duplicate of this bug. ***
Now published at https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html/self-hosted_engine_guide/chap-deploying_self-hosted_engine