yahoo-eng-team team mailing list archive

[norman shen <1995229@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Description
===========

Instance.availability_zone is set in nova.conductor while scheduling.
But host's availability_zone could be modified when host is added to an
aggregate, but instance.availability_zone will not be changed, instead
'availabity_zone' will be cached in applications like memcached.

The issue of this strategy causes /servers/detail to cost around extra 1
second when returned list containing more than 500 servers.

So my proposal is to update instance.availability_zone when host is
added to a new aggregate.

** Affects: nova
     Importance: Undecided
         Status: New

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

Title:
  [Opinion] Update instance availability_zone when reset host AZ

Status in OpenStack Compute (nova):
  New

Bug description:
  Description
  ===========

  Instance.availability_zone is set in nova.conductor while scheduling.
  But host's availability_zone could be modified when host is added to
  an aggregate, but instance.availability_zone will not be changed,
  instead 'availabity_zone' will be cached in applications like
  memcached.

  The issue of this strategy causes /servers/detail to cost around extra
  1 second when returned list containing more than 500 servers.

  So my proposal is to update instance.availability_zone when host is
  added to a new aggregate.

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