Share Migration In Data Service

Registered by Rodrigo Barbieri

After Data Service is introduced in Manila, it allows Share Migration to be offloaded to it.

Share Migration code should be moved to it.

There has been discussion of a 2-phase migration, where an admin may want to request a migration, and after copy is completed, request migration to be completed (delete source instance and revert access rules).

Share Migration in Data Service should also support Admin Export locations.

A Share Migration request should not block Data Service, so Data Copying should be multi-threaded.

Also, new Share Migration API functions can be added:
- migration_cancel
- migration_get_progress
- migration_complete

Blueprint information

Status:
Complete
Approver:
Ben Swartzlander
Priority:
Medium
Drafter:
Rodrigo Barbieri
Direction:
Approved
Assignee:
Rodrigo Barbieri
Definition:
Approved
Series goal:
Accepted for mitaka
Implementation:
Implemented
Milestone target:
milestone icon mitaka-3
Started by
Ben Swartzlander
Completed by
Ben Swartzlander

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/data-service-migration,n,z

Addressed by: https://review.openstack.org/250515
    Move Share Migration code to Data Service

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.