4249e94c6b
Administrators configure share types and make them available to projects within an OpenStack cloud. These share types will define capabilities to match back-end storage pools that manila provisions shares within. Administrators may want to limit share types to specific Availability zones, given they may have different classes of storage in different availability zones in the cloud. A major use case of this is edge computing, where, provisioning can be driven to specific edge locations with the help of share types. This commit will: - Introduce 'availability_zones' as a new common share type extra spec that is user visible when configured. - In and beyond microversion 2.48, validate that the AZ chosen in the POST /shares API is supported by the configured availability zones for the share type being used. - Share types can be filtered by AZs through extra-specs: $ manila type-list --extra-specs availability_zone=nova now gives you all types that explicitly (and implicitly) are supported within the AZ 'nova'. - Improve experimental APIs: - Add validation of AZ to POST /share-replicas - Add validation of AZ to POST /share-groups - Add validation of AZ to POST /shares/id {'action': 'migration_start'} - Also fix old unit tests by using a helper method to generate appropriate mock values. DocImpact Change-Id: Idf274cd73e3b1b33f49668fca768ae676ca30164 Implements: bp share-type-supported-azs
11 lines
558 B
YAML
11 lines
558 B
YAML
---
|
|
features:
|
|
- |
|
|
A new common user-visible share types extra-spec called
|
|
"availability_zones" has been introduced. When using API version 2.48,
|
|
user requests to create new shares in a specific availability zone will
|
|
be validated against the configured availability zones of the share type.
|
|
Similarly, users requests to create share groups and share replicas are
|
|
validated against the share type ``availability_zones`` extra-spec when
|
|
present. Users can also filter share types by one or more AZs that are
|
|
supported by them. |