39efc2bde8
This patch adds support for migration of share servers. This migration is performed using a two-phase approach. Administrators are now able to request the migration of a share server within and across backends, with the possibility of chooosing a different share network for the destination share server. - A new field called `task_state` was added to the share server model in order to help the administrator to track the share server migration steps. A new field called `source_share_server_id` was added to link destination and source share servers. - A new periodic task was added to track migration of share servers and its resources. - Two new states were added: `server_migrating` and `server_migrating_to` to represent that share migration is in progress. - When performing the server migration, manila will not go to the scheduler, instead it will provide a request spec to drivers during migration check driver call. It'll be up to the driver validate if there is free space to handle the share server. - A new API called `share-server-migration-check' was added to check the feasibility of a migration, before actually triggering the start operation. APIImpact DocImpact Partially Implements: bp share-server-migration Co-Authored-By: Andre Beltrami <debeltrami@gmail.com> Co-Authored-By: Carlos Eduardo <ces.eduardo98@gmail.com> Co-Authored-By: Felipe Rodrigues <felipefuty01@gmail.com> Change-Id: Ic0751027d2c3f1ef7ab0f7836baff3070a230cfd Signed-off-by: Douglas Viroel <viroel@gmail.com>
27 lines
1.5 KiB
YAML
27 lines
1.5 KiB
YAML
---
|
||
features:
|
||
- |
|
||
Added the ability to migrate share servers within and across backends in
|
||
Manila. As designed in share migration, a two-phase approach is now
|
||
available for share servers, with the addition of a new API to check the
|
||
feasibility of a migration, called ``share-server-migration-check``. Now,
|
||
Manila can start, complete, cancel and retrieve the progress of a share
|
||
server migration. These operations were designed for Administrators and
|
||
will work only when operating under `driver_handles_share_servers=True`
|
||
mode. When starting a share server migration, it is possible to choose
|
||
which capabilities must be supported by the driver: remain ``writable``
|
||
during the first phase, ``preserve_snapshots``, be ``nondisruptive`` and
|
||
migrate to a different share network.
|
||
upgrade:
|
||
- |
|
||
The share server entity now contains two new fields: ``task_state`` and
|
||
`source_share_server_id`. The `task_state` field helps tracking the
|
||
migration progress of a share server. The ``source_share_server_id`` field
|
||
will hold the source share server identification until the migration gets
|
||
completed or cancelled.
|
||
New statuses were added in order to control whether a share server, its
|
||
shares or snapshots are being migrated to a different location. Share
|
||
server shares’ are going to remain in the status ``server_migrating`` while
|
||
the migration is in course. When the migration gets completed, the
|
||
statuses are going to be updated.
|