You can either live migrate the instances or stop the instances and start the instances on the required host.
If you need a consistent behaviour on the host selection, you can create new service offerings with the same (or whatever compute values you need) values but with host tags now. Stop the instances and change the service offering using scaleVM operation. During start of those instances, it will pick the right host based on the host tags in the new offerings. If the dynamic scaling is enabled on the instances, you can scale the VM directly to the new offering and select auto migrate during the scale VM operation. Hope this helps. Thanks, Harikrishna From: Francisco Arencibia Quesada <[email protected]> Date: Sunday, 10 December 2023 at 5:05 PM To: [email protected] <[email protected]> Subject: Re: Force VM and VR to be on the same host Awesome, this case will work for new VMs, but what happens with those Vms already created? Is there an easy way to relocate them? Thanks and Regards On Sun, 10 Dec 2023, 03:43 Harikrishna Patnala, < [email protected]> wrote: > Hi, > > You can use host tags. > > 1. Set tag on the host > 2. Create service offering with the same host tag > 3. Create system service offering of System VM type “Domain Router” > with the same host tag > 4. Create Network offering and select the system service offering > created above and create network using that > > Regards, > Harikrishna > > From: Francisco Arencibia Quesada <[email protected]> > Date: Saturday, 9 December 2023 at 9:58 PM > To: [email protected] <[email protected]> > Subject: Force VM and VR to be on the same host > Hello guys, > > > Is it possible to force the location of a VM and it's VR in order to have > it in the same host? Why is this behaviour of splitting both by default? > > Kind regards > > > >
