yahoo-eng-team team mailing list archive

[Sylvain Bauza <sbauza@xxxxxxx>]

There is clear upstream consensus on the fact that since availability
zones are for end-users, updating an AZ from an operator point-of-view
would confuse their users.

Let me explain further : say you'd like to change AZ "foo" into "bar".
For end-users looking at the AZ API before booting their instances, they
can see "foo" as a valid target. So they just use --availability_zone
foo in their instance boot calls and they expect to see their instances
in AZ foo.

Now, what if operator turns "foo" into "bar" ? If I'm an end-user, I'd
be very surprised to see my instances being now in "bar" while I
explicitely asked "foo"!

As a clear design decision, we really want to make it explicit that renaming an AZ should be forbidden if there are active instances hosted within that AZ. 
Closing that bug as Wontfix since I feel not being able to modify an AZ is not a bug but rather a design decision, but I feel we also need to modify the aggregates API to return a HTTP40x if someone is wanting to update an aggregate metadata containing AZ information when there are instances attached to it.

** Changed in: nova
       Status: In Progress => Won't Fix

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

Title:
  renaming availability zone doesn't modify host's availability zone

Status in OpenStack Compute (nova):
  Won't Fix

Bug description:
  Hi,

  After renaming our availability zones via Horizon Dashboard, we
  couldn't migrate any "old" instance anymore, the scheduler returning
  "No valid Host found"...

  After searching, we found in the nova DB `instances` table, the
  "availability_zone" field contains the name of the availability zone,
  instead of the ID ( or maybe it is intentional ;) ).

  So renaming AZ leaves the hosts created prior to this rename orphan
  and the scheduler cannot find any valid host for them...

  Our openstack install is on debian wheezy, with the icehouse
  "official" repository from archive.gplhost.com/debian/, up to date.

  If you need any more infos, I'd be glad to help.

  Cheers

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