Manila UI enumerates availability zones from Nova

[Clinton Knight]

When creating shares and share replicas, the user may select an availability zone (AZ) from a drop-down list. The list is currently populated by a call to Nova.

Manila maintains its own DB table of availability zones, and they may be listed using the /services API. The set of AZs for manila-share services should be presented in manila-ui.

It is reasonable to expect that a complete OpenStack deployment would have the same AZs for Nova, Manila, Cinder, etc. But Manila is also expected to work independently of the other core services, so Manila-UI should get its AZ list from Manila, not Nova.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/367992

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/367992
Committed: https://git.openstack.org/cgit/openstack/manila-ui/commit/?id=7c90c46990235511b4e9c9435db9229ee05ed846
Submitter: Jenkins
Branch: master

commit 7c90c46990235511b4e9c9435db9229ee05ed846
Author: Valeriy Ponomaryov <email address hidden>
Date: Fri Sep 9 15:27:45 2016 +0300

    Read list of AZs using manila's API instead of nova's

    Manila UI calls Nova API for getting list of availability zones,
    and it is incorrect for following reasons:
    - manila can work without nova
    - list of AZs can differ as nova services may be located in different
      zones.

    So, use for such case manila's API 'service list' that provides all
    required data.

    Depends-on: Ie7ff8234b5cd4a20d94148c7512b2d5cd621e190
    Change-Id: Ib7935ecb24e250d0280e12ee706dbe6f985167e9
    Closes-Bug: #1621721

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/manila-ui 2.6.0 release.