Bug 1888670 - [RFE][cinder] Allow in use volumes to be migrated (live) between different Ceph clusters
Summary: [RFE][cinder] Allow in use volumes to be migrated (live) between different Ce...
Keywords:
Status: NEW
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-cinder
Version: 7.0 (Kilo)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: z2
: ---
Assignee: Cinder Bugs List
QA Contact: Evelina Shames
RHOS Documentation Team
URL:
Whiteboard:
Depends On: 1949701 905125 1293440 1306562 1306569 1623877 1780119 1888672 1888674
Blocks: 1434362 1543156 1601807 1728334 1728337
TreeView+ depends on / blocked
 
Reported: 2020-10-15 13:19 UTC by Luigi Toscano
Modified: 2023-10-23 11:02 UTC (History)
20 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of: 1293440
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-2158 0 None None None 2021-12-03 15:17:32 UTC

Description Luigi Toscano 2020-10-15 13:19:39 UTC
+++ This bug was initially created as a clone of Bug #1293440 +++

Description
=========

Migrating volumes between different storage backends or different storage clusters while the volume is in use in Cinder.

Currently, you can migrate an offline volume between different storage clusters, or technologies, like LVM and Ceph, but the Volume needs to be not in use.

User Stories
========
- As an operator, I want to migrate images between storage clusters without regard for their active or idle status.

---


This bug/RFE is a special case of 1293440 to track the case where the live migration is performed between different Ceph clusters.

Comment 13 Gregory Charot 2023-09-14 15:18:58 UTC
This RFE did not make 17.1GA and is being deprioritised due because BZ#1949701 is being deprioritised. If you think this RFE should be reconsidered please provide the customer's use case and business justification.


Note You need to log in before you can comment on or make changes to this bug.