[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]
** Changed in: nova
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1806344
Title:
[Nova Scheduler] Option any availability zone (AZ)
Status in OpenStack Compute (nova):
Expired
Bug description:
In many cases, first time, admin only uses default_availability_zone as
unique AZ. That means any functions create new VM lead that VM boot on default
zone: "nova" (all current host).
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_availability_zone instead of any zone.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1806344/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
