[Nova Scheduler] Option any availability zone (AZ)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Expired
|
Undecided
|
Unassigned |
Bug Description
In many cases, first time, admin only uses default_
After that, admin ungroups their hosts into some separate AZs. However, many before functions did not specified any AZs such as auto healing, heat template. So, after deviding into many AZs, creating new VM lead that VM can boot on the zone different from default zone "nova". It is not convenient!
Solution for this situation is modify all old functions to add specified AZ.
To avoid above situation, I think if not specify AZ in creating new instance, nova scheduler should choice default_
I'm not sure I understand the issue.
https:/ /docs.openstack .org/nova/ latest/ configuration/ config. html#DEFAULT. default_ availability_ zone
is the default AZ for a compute service. If the server is created without specifying an availability zone, it can be scheduled to any host and migrated to any other host across AZs.
The only time the server is restricted to a certain AZ is:
1. The user requested a specific AZ when creating the server (and the user should not request "nova", see the warning here: https:/ /docs.openstack .org/nova/ latest/ user/aggregates .html#availabil ity-zones- azs).
2. The default_ schedule_ zone https:/ /docs.openstack .org/nova/ latest/ configuration/ config. html#DEFAULT. default_ schedule_ zone option is set.
It sounds like what you want is #2 so that VMs which are created without a specific AZ being requested will go into a default AZ. If so, then configure that option in nova-api.