2b57d15c64
Manila can now configure a share network with multiple subnets
in an availability zone. Also, it can add a new subnet for an
availability that has share servers, which will triger an update
share server allocations.
Changes:
- API:
- Bump version to 2.70.
- setup share network with multiple subents per az.
- Block manage server with multiple subnets.
- Allow add subnet for in-use share servers.
- `share_network_subnet_id` is dropped from ShareServer view
- `share_network_subnet_ids` is added in ShareServer view
- `network_allocation_update_support` is added to ShareServer and
ShareNetwork views.
- Add a check operation for share network subnet create.
- DB:
- Remove `share_network_subnet_id` from share_servers.
- Create mapping table `share_server_share_network_subnet_mappings`.
- Fix queries with new db design.
- Add migration downgrade and upgrade alembic.
- Add `share_network_subnet_id` to the NetworkAllocations.
- Scheduler:
- Change `AvailabilityZoneFilter` to take in account if the
host supports the allocation required by the setup request.
- Manager:
- Bump RPC API version.
- `_setup_server` allocating multiple subnets.
- Modify signature of driver `_setup_server` interface, passing a
list of `network_info` for each subnet.
- Share server DB creation to inform a list of subnets and
create with `network_allocation_update_support`.
- Implement `check_update_share_server_network_allocations` and
`update_share_server_network_allocations`.
- Drivers:
- For legacy compatibility, all drivers implementing `_setup_server`
consume the first element of the `network_ino`.
- Dummy Driver:
- Implement `_setup_server` with new signature as multiple subnet.
- Modify the `backend_details` to save allocations for all subnets.
- Report update allocation and share server multiple subnet support.
- Implement `check_update_share_server_network_allocations` and
`update_share_server_network_allocations` interfaces.
Signed-off-by: Felipe Rodrigues <felipefuty01@gmail.com>
Co-Authored-By: Andre Beltrami <debeltrami@gmail.com>
Co-Authored-By: Fábio Oliveira <fabioaurelio1269@gmail.com>
Co-Authored-By: Nahim Alves de Souza <nahimsouza@outlook.com>
Co-Authored-By: Caique Mello <caique_mellosbo@hotmail.com>
DocImpact
APIImpact
Partially-Implements: blueprint multiple-share-network-subnets
Change-Id: I7de9de4ae509182e9494bba604979cce03acceec
26 lines
1.2 KiB
YAML
26 lines
1.2 KiB
YAML
---
|
|
features:
|
|
- |
|
|
Add support for multiple subnet per availability zone. The multiple
|
|
configuration can be done either on share server deployment or updating
|
|
a pre-existent share server.
|
|
|
|
The new field ``network_allocation_update_support`` was added to share
|
|
server's model This field defaults to ``False``, and all of the
|
|
already deployed share servers are going to get the default value even if
|
|
their backend support it. Administrators will be able to update the field
|
|
value using ``manila-manage`` commands.
|
|
|
|
The driver will report its support for adding a subnet on a pre-existent
|
|
share server through ``network_allocation_update_support``. Also, it will
|
|
report the support for creating the server with multiple subnets with the
|
|
``share_server_multiple_subnet_support``. The scheduler will filter out
|
|
backend that does not handle this request during some operations. Example,
|
|
creating a share with a share network containing multiple subnets, only
|
|
hosts that support this deployment will be selected.
|
|
deprecations:
|
|
- |
|
|
Remove 'share_network_subnet_id' attribute from share server view and
|
|
add 'share_network_subnet_ids' starting with microversion '2.70'. The share
|
|
server has a list of subnets.
|