Hi!

yes, setting `default_schedule_zone` should help.
But it doesn't really help when you don't want to have a default AZ and you just want to prevent a VM from being migrated between AZs.

I've described the issue in this bug report some time ago: https://bugs.launchpad.net/nova/+bug/2047182

Unfortunately, it turned out that it's quite hard to fix this behavior :/

On Thu, Dec 19, 2024 at 12:56 PM Kees Meijs | Nefos <keesm@nefos.nl> wrote:

Hi,

(Very) interested in this as well.

So: +1

Cheers,
Kees

On 19-12-2024 12:36, Tobias Urdin - Binero IT wrote:

IIRC this is the reason we are setting `default_schedule_zone` in nova.conf so
that the zone is populated explicitly in the request_spec in the database so that
it can’t be moved to another zone later, but im not 100% sure.

Obviously the drawback being that you populate one zone only if none is
selected.

I don’t think there is an option to “schedule to any zone and then hardcode it
in request_spec”, we would be interested if that’s available today or something
that could be added.