Utilize Remote Replication on NexentaStor for Volume Migration
Implement volume migration in Nexenta Volume Driver for direct host-to-host volume migration omitting to send traffic over the Cinder node.
Please go to https:/
Blueprint information
- Status:
- Complete
- Approver:
- Avishay Traeger
- Priority:
- Low
- Drafter:
- Mikhail Khodos
- Direction:
- Approved
- Assignee:
- Mikhail Khodos
- Definition:
- Approved
- Series goal:
- Accepted for liberty
- Implementation:
-
Implemented
- Milestone target:
-
7.0.0
- Started by
- Mike Perez
- Completed by
- Mike Perez
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Add volume migration code to Nexenta iSCSI volume driver
Avishay: Can you please explain how the migration is done? Does it work only for 'available' volumes or also 'in-use'? How does the in-use case work?
Caitlin Bestler: Why would the method of replication require documentation for a same-to-same migration?
Avishay: Because a blueprint should have some information on what is being proposed, and because I looked at the code and would be very surprised if it worked for migrating 'in-use' volumes, so I was hoping for some further explanation.
Mikhail: Updated the code review to support only "available" volume as Avishay has pinpointed. "In-use" volume migration can be performed via incremental snapshot replication but this would require a new generic API like "volume_
