Bug 1738236

Summary:	[RFE] Migrate an RHCS4 cluster deployed by director from filestore to bluestore
Product:	Red Hat OpenStack	Reporter:	John Fulton <johfulto>
Component:	ceph-ansible	Assignee:	John Fulton <johfulto>
Status:	CLOSED EOL	QA Contact:	Yogev Rabl <yrabl>
Severity:	high	Docs Contact:
Priority:	high
Version:	15.0 (Stein)	CC:	fpantano, gabrioux, gcharot, gfidente, scohen, stchen, yrabl
Target Milestone:	---	Keywords:	FutureFeature, Tracking, Triaged, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:	1733577	Environment:
Last Closed:	2020-09-30 19:43:50 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1697511, 1729267, 1733577, 1738576, 1756366, 1756371
Bug Blocks:

Description John Fulton 2019-08-06 15:10:57 UTC

+++ This bug was initially created as a clone of Bug #1733577 +++

Customers who have completed the process enabled by RFE 1697511 will be running OSP16 and RHCS4 but with the filestore ceph backend. They will then wish to migrate to the bluestore ceph backend. This is an RFE to track OSPd's ability to manage that migration. This RFE will ultimately depend on a ceph-ansible playbook to perform the migration.

--- Additional comment from RHEL Product and Program Management on 2019-07-26 15:17:34 UTC ---

The keyword FutureFeature has been added. If this bug is not a FutureFeature, please remove from the Summary field any strings containing "RFE, rfe, FutureFeature, FEAT, Feat, feat". Additionally, if this feature is being backported to a previous release, clone this BZ to older releases and add the "FeatureBackport" keyword only to those cloned BZs.

--- Additional comment from John Fulton on 2019-07-26 15:25:41 UTC ---

Guillaume, do you have an RFE to track filestore to bluestore migration? I'd like to make this RFE depends-on it.

--- Additional comment from John Fulton on 2019-07-26 15:28:38 UTC ---

(In reply to John Fulton from comment #2)
> Guillaume, do you have an RFE to track filestore to bluestore migration? I'd
> like to make this RFE depends-on it.

1729267

--- Additional comment from John Fulton on 2019-07-26 16:00:15 UTC ---

Since tripleo can now generate an inventory which is compatible with ceph-ansible [0] and since all ceph-ansible runs in OSP16 will already use the tripleo inventory [1], I think we should be able to test and then document the following rough process:

1. tripleo-ansible-inventory --static-yaml-inventory ~/inventory.yaml [2]
2. ansible-playbook -i ~/inventory.yaml ... /usr/share/ceph-ansible/infrastructure-playbooks/filestore_to_bluestore.yml

making this almost a test-only RFE.

[0] https://review.opendev.org/#/c/663466 
[1] https://github.com/openstack/tripleo-heat-templates/commit/f86635803793c006210495b0c2fe8c34bf301f6c
[2] https://www.redhat.com/en/blog/greater-control-red-hat-openstack-platform-deployment-ansible-integration

--- Additional comment from John Fulton on 2019-08-06 14:54:03 UTC ---

If we're going to clone this for osp15, then we cannot simply do what's described in #4. It would need another step:

1. tripleo-ansible-inventory --static-yaml-inventory ~/openstack-inventory.yaml
2. run a python script which takes ~/openstack-inventory.yaml as input and produces ~/ceph-inventory.yaml as output
3. ansible-playbook -i ~/ceph-inventory.yaml ... /usr/share/ceph-ansible/infrastructure-playbooks/filestore_to_bluestore.yml

So we'd have to implement #2 in addition. Alternatively, we could backport the following:

 https://review.opendev.org/#/c/663466/3/tripleo_common/inventory.py

I think the backport is my preference. I'll attempt that.

 https://review.opendev.org/#/c/674822/

Comment 1 John Fulton 2019-09-06 15:17:22 UTC

(In reply to John Fulton from comment #0)
> --- Additional comment from John Fulton on 2019-07-26 16:00:15 UTC ---
> 
> Since tripleo can now generate an inventory which is compatible with
> ceph-ansible [0] and since all ceph-ansible runs in OSP16 will already use
> the tripleo inventory [1], I think we should be able to test and then
> document the following rough process:
> 
> 1. tripleo-ansible-inventory --static-yaml-inventory ~/inventory.yaml [2]
> 2. ansible-playbook -i ~/inventory.yaml ...
> /usr/share/ceph-ansible/infrastructure-playbooks/filestore_to_bluestore.yml
> 
> making this almost a test-only RFE.
> 
> [0] https://review.opendev.org/#/c/663466 
> [1]
> https://github.com/openstack/tripleo-heat-templates/commit/
> f86635803793c006210495b0c2fe8c34bf301f6c
> [2]
> https://www.redhat.com/en/blog/greater-control-red-hat-openstack-platform-
> deployment-ansible-integration
> 
> --- Additional comment from John Fulton on 2019-08-06 14:54:03 UTC ---
> 
> If we're going to clone this for osp15, then we cannot simply do what's
> described in #4. It would need another step:
> 
> 1. tripleo-ansible-inventory --static-yaml-inventory
> ~/openstack-inventory.yaml
> 2. run a python script which takes ~/openstack-inventory.yaml as input and
> produces ~/ceph-inventory.yaml as output
> 3. ansible-playbook -i ~/ceph-inventory.yaml ...
> /usr/share/ceph-ansible/infrastructure-playbooks/filestore_to_bluestore.yml
> 
> So we'd have to implement #2 in addition. Alternatively, we could backport
> the following:
> 
>  https://review.opendev.org/#/c/663466/3/tripleo_common/inventory.py
> 
> I think the backport is my preference. I'll attempt that.
> 
>  https://review.opendev.org/#/c/674822/

The above backport has merged. Assuming the depends-on bug (1729267) works, this bug should be TestOnly with some docs.

Comment 2 stchen 2020-09-30 19:43:50 UTC

Closing EOL, OSP 15 has been retired as of Sept 19, 2020