Le dim. 26 mars 2023 à 14:30, Rafael Weingärtner <rafaelweingartner@gmail.com> a écrit :

Hello Nguyễn Hũu Khôi,
You might want to take a look at: https://review.opendev.org/c/openstack/nova/+/864760. We created a patch to avoid migrating VMs to any AZ, once the VM has been bootstrapped in an AZ that has cross zone attache equals to false.

Well, I'll provide some comments in the change, but I'm afraid we can't just modify the request spec like you would want.

Anyway, if you want to discuss about it in the vPTG, just add it in the etherpad and add your IRC nick so we could try to find a time where we could be discussing it : https://etherpad.opendev.org/p/nova-bobcat-ptg

Also, this kind of behaviour modification is more a new feature than a bugfix, so fwiw you should create a launchpad blueprint so we could better see it.

-Sylvain

On Sun, Mar 26, 2023 at 8:20 AM Nguyễn Hữu Khôi <nguyenhuukhoinw@gmail.com> wrote:
Hello guys.
I playing with Nova AZ and Masakari

https://docs.openstack.org/nova/latest/admin/availability-zones.html

Masakari will move server by nova scheduler.

Openstack Docs describe that:

If the server was not created in a specific zone then it is free to be moved to other zones, i.e. the AvailabilityZoneFilter is a no-op.

I see that everyone usually creates instances with "Any Availability Zone" on Horzion and also we don't specify AZ when creating instances by cli.

By this way, when we use Masakari or we miragrated instances( or evacuate) so our instance will be moved to other zones.

Can we attach AZ to server create requests API based on Any Availability Zone to limit instances moved to other zones?

Thank you. Regards

Nguyen Huu Khoi

--
Rafael Weingärtner