← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1366501] Re: No update mechanism to report host storage port changes

 

This wishlist bug has been open a year without any activity. I'm going
to move it to "Opinion / Wishlist", which is an easily-obtainable queue
of older requests that have come on. If you decide to work on this
consider using a blueprint [1] (maybe with a spec [2]). I'll recommend to 
read [3] if not yet done. 

References:
[1] https://blueprints.launchpad.net/nova/
[2] https://github.com/openstack/nova-specs
[3] https://wiki.openstack.org/wiki/Blueprints

** Changed in: nova
       Status: Confirmed => 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/1366501

Title:
  No update mechanism to report host storage port changes

Status in OpenStack Compute (nova):
  Opinion

Bug description:
  *Descriprtion*
  When a volume is being attached to an instance, the compute transfers the host ports to the storage driver through cinder inside the initialize_connection call. The compute will only pass online ports and will not report any ports that are down (linkdown).

  *Issue*
  If a port that was down at the attach time, comes up afterwards, or ports were physically added at some points, there is no update mechanism to inform the storage driver about them so the driver will be able to utilize them.

  *Solution*
  There should be an update mechanism that runs periodically and reports host changes to the driver through cinder.

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


References