14d3e268a0
This patch adds the possibility to create share networks with multiple subnets in Manila. It also updates the share server api to receive "share_network_subnet_id" instead of "share_network_id". Each share network subnet must be associated with only one availability zone. Each share network must have a single default share network subnet. DocImpact APIImpact Depends-On: I13bb48e7c03e16c26946ccf9d48e80592391a3d1 Partially-implements: bp share-network-multiple-subnets Change-Id: Id8814a8b26c9b9dcb1fe71d0d7e9b79e8b8a9210 Closes-Bug: #1588144 Co-Authored-By: lseki <luciomitsuru.seki@fit-tecnologia.org.br> Co-Authored-By: dviroel <viroel@gmail.com>
22 lines
1.1 KiB
YAML
22 lines
1.1 KiB
YAML
---
|
|
features:
|
|
- Added APIs with default policy set to 'rule:default' that allow the
|
|
creation of share networks with multiple subnets. This gives the users
|
|
the ability to create multiple subnets in a share network for different
|
|
availability zones. Also, users will be able to delete and show
|
|
existing subnets.
|
|
- Updated the share server API to make possible to manage share servers
|
|
in a specific subnet when the driver is operating in
|
|
``driver_handles_share_servers`` enabled mode.
|
|
- Share servers are now associated with a single share network subnet, which
|
|
pertain to a share network.
|
|
upgrade:
|
|
- On upgrading to this release, all existing share networks will be updated
|
|
to accommodate an availability zone assignment. Existing share networks
|
|
will have their availability zone set to "empty" indicating that they are
|
|
available across all storage availability zones known to manila.
|
|
fixes:
|
|
- A share network cannot be provided while creating a share replica. Replicas
|
|
will inherit the share's share network if one exists.
|
|
|