During the adoption process, we need to take care about the RGW daemon, which is a critical component in the Ceph cluster deployment.
In particular, RGW in TripleO is configured through [1] to provide HA, and pacemaker manages the VIP according to the vip_map.json provided by heat/puppet [2] [3].
We need to investigate and figure out which is the best strategy to migrate this daemon without affecting the other services that rely on haproxy+pacemaker using the same VIP.
Other concerns are related to tls-everywhere, but that can be a different spike on top of this one.

[1] https://github.com/openstack/puppet-tripleo/blob/master/manifests/haproxy.pp#L1744-L1765
[2] https://github.com/openstack/tripleo-ansible/blob/master/tripleo_ansible/roles/tripleo_hieradata/templates/vip_data.j2
[3] https://github.com/openstack/tripleo-heat-templates/blob/master/overcloud-resource-registry-puppet.j2.yaml