Open Stack

I don't know why this is not merged to github.

It is a problem with the system.

Nguyen Huu Khoi


On Sun, Mar 26, 2023 at 7:52 PM Nguyễn Hữu Khôi <nguyenhuukhoinw at gmail.com>
wrote:

> Hello.
> Many thanks for your information. It's very helpful for me. :)
> Nguyen Huu Khoi
>
>
> On Sun, Mar 26, 2023 at 7:24 PM Rafael Weingärtner <
> rafaelweingartner at gmail.com> wrote:
>
>> 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.
>>
>> On Sun, Mar 26, 2023 at 8:20 AM Nguyễn Hữu Khôi <
>> nguyenhuukhoinw at 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
>>> <https://docs.openstack.org/nova/latest/admin/scheduling.html#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
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.openstack.org/pipermail/openstack-discuss/attachments/20230326/8289068f/attachment.htm>