Please, give me some idea how to migrade rhvm self-hosted engine from one rhvh host to another in two rhvh hostd cluster.
Generally speaking, a RHV Manager will only reside in the cluster that was originally deployed on. Why do you need to move your rhv-m to a new cluster?
Some ideas:
- Add your new hosts into the old cluster, and make the hosts candidates for RHVM (then decomission the old hypervisors if necessary, or move them to a different cluster in the same RHVM datacenter).
- Convert your Hosted Engine into a standalone RHVM ( https://access.redhat.com/solutions/3550032 ) , then migrate from standalone to hosted engine in the new cluster. Please open a support case for the first part, to clarify whether it is still supported / tested. The note was tested for 4.1 and things might have changed since then.
Right. You should have at least two hypervisors that have been deployed in "Hosted Engine" mode. If you check your inventory, one of them should have a yellow star, marking it's the current-running RHVM host. Other hosts that are candidates to running the Hosted Engine VM will have a gray start, indicating they might run the HE. Hypervisors with a crossed star are the ones that could run the HE, but can't at the moment because some error/situation. (Maintenance mode, missing HA score, etc).
In order to have an hypervisor with Hosted Engine capabilities, you need to reinstall it from the RHVM web ui, and ensure that Hosted Engine option is set to "Deploy". If you already have some hypervisors with the gray start, you can skip this step. https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html/administration_guide/p...
Finally, when you have at least two hypervisors with a star (yellow and gray), you can set them in maintenance mode, and the Hosted Engine VM will live-migrate automatically between hosts.
Generally speaking, a RHV Manager will only reside in the cluster that was originally deployed on. Why do you need to move your rhv-m to a new cluster?
Some ideas:
- Add your new hosts into the old cluster, and make the hosts candidates for RHVM (then decomission the old hypervisors if necessary, or move them to a different cluster in the same RHVM datacenter).
- Convert your Hosted Engine into a standalone RHVM ( https://access.redhat.com/solutions/3550032 ) , then migrate from standalone to hosted engine in the new cluster. Please open a support case for the first part, to clarify whether it is still supported / tested. The note was tested for 4.1 and things might have changed since then.
Thank @Fran_Garcia
But I am asking about migrating between two hosts into one cluster, not about two clusters. For example, for maintanence propose
Right. You should have at least two hypervisors that have been deployed in "Hosted Engine" mode. If you check your inventory, one of them should have a yellow star, marking it's the current-running RHVM host. Other hosts that are candidates to running the Hosted Engine VM will have a gray start, indicating they might run the HE. Hypervisors with a crossed star are the ones that could run the HE, but can't at the moment because some error/situation. (Maintenance mode, missing HA score, etc).
In order to have an hypervisor with Hosted Engine capabilities, you need to reinstall it from the RHVM web ui, and ensure that Hosted Engine option is set to "Deploy". If you already have some hypervisors with the gray start, you can skip this step. https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html/administration_guide/p...
Finally, when you have at least two hypervisors with a star (yellow and gray), you can set them in maintenance mode, and the Hosted Engine VM will live-migrate automatically between hosts.
Thank. It is really I wanted
@Fran_Garcia These are wonderful suggestions - thank you for your input!
Thanks Deanna, happy to help! :·)
Red Hat
Learning Community
A collaborative learning environment, enabling open source skill development.