Open Stack

I see a reported bug which describes this problem clearly.

https://bugs.launchpad.net/nova/+bug/2018318

I also do google and many people ask about this problem.

Can I know why is it pain for us? If we can resolve this issue, system will
be more stable(in my opinion)

I know that we can resolve this problem with default az scheduler but look
likes there is no way with existing instances.

>From a cloud operator view.

Nguyen Huu Khoi


On Wed, Aug 16, 2023 at 10:51 PM Nguyễn Hữu Khôi <nguyenhuukhoinw at gmail.com>
wrote:

> Thank you for the information!
> Can we set AZ for existing instance?
>
> On Wed, Aug 16, 2023, 10:47 PM <smooney at redhat.com> wrote:
>
>> On Wed, 2023-08-16 at 21:43 +0700, Nguyễn Hữu Khôi wrote:
>> > Hello guys.
>> >
>> > I need to verify whether an existing instance was created with AZ or
>> > without AZ. How can we check on an existing instance?
>> the only way to check this is via the request spec in the api db
>> you can check if an AZ is in the request spec if its empyt then none was
>> requested.
>> >
>> > I did not setup default AZ scheduler before. At this time I plan to
>> expand
>> > the system by a new AZ.
>> >
>> > as document
>> >
>> > 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 am worried about when I migrate instances and they will be free to be
>> > moved to other zones.
>> well that would be working a intended.
>> but if you are concerned baout it because you use the config option to
>> prevent cross AZ attache
>> then we have special code to pin the instance in that sepcicic case.
>> >
>> > Nguyen Huu Khoi
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.openstack.org/pipermail/openstack-discuss/attachments/20230817/5ebe1fad/attachment.htm>