yahoo-eng-team team mailing list archive

[sean mooney <2078669@xxxxxxxxxxxxxxxxxx>]

since the intorduction of AZ nova has documented that pinning to the
nova az should never be done

https://docs.openstack.org/nova/latest/admin/availability-zones.html

"""
The use of the default availability zone name in requests can be very error-prone. Since the user can see the list of availability zones, they have no way to know whether the default availability zone name (currently nova) is provided because a host belongs to an aggregate whose AZ metadata key is set to nova, or because there is at least one host not belonging to any aggregate. Consequently, it is highly recommended for users to never ever ask for booting an instance by specifying an explicit AZ named nova and for operators to never set the AZ metadata for an aggregate to nova. This can result is some problems due to the fact that the instance AZ information is explicitly attached to nova which could break further move operations when either the host is moved to another aggregate or when the user would like to migrate the instance.
"""

while it is possible to do it is generally considered unsupported and
incorrect by the nova core team.

hoizon has historically been the leading culpert to people actually
using nova in the request as it places it in the dropdown when creating
a VM.

this is a horizon bug and has never been a valid approach.

you do not need to specify an az when creating a VM in nova and you
should not in this case.

** Changed in: nova
       Status: In Progress => Opinion

-- 
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/2078669

Title:
  Specify --availability-zone=nova does not work since caracal

Status in OpenStack Compute (nova):
  Opinion

Bug description:
  openstack server create with --availability-zone=nova can place
  instance onto the compute which belongs to non default AZ since
  caracal release. The issue is introduced by removal of nova
  availabilityZone filter
  https://review.opendev.org/c/openstack/nova/+/886779.

  When using placement to filter AZs we add member_of=XXX, where XXX is
  the aggregate UUID which corresponds to AZ. In case of default AZ
  (nova) there is no any aggregate. As result we request computes
  without any aggregate/az filtering.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/2078669/+subscriptions