On Mon, Jun 10, 2024 at 5:11 PM Goutham Pacha Ravi
<gouthampravi@gmail.com> wrote:
>
> Hello,
>
> For a long time we've had multiple ways of deploying ceph for devstack
> environments in single and over multiple nodes to test integration
> with nova, cinder, manila, glance and rgw. Of late, we've preferred
> using the ceph community's preferred installation method: using the
> ceph orchestrator via its cephadm API.
>
> For OpenStack services, it really shouldn't matter _how_ ceph is
> deployed; and so I wanted to clean up the devstack plugin project to
> just have one installation method: cephadm. This installation method
> has been stable since the 2024.1 release cycle; so if there are no
> objections, I'd love to delete a bunch of code to deploy ceph via
> packages (apt/rpm) and with docker/podman containers. No new devstack
> options are _required_ unless you want to customize things. There's an
> integrated job, several cinder, manila and nova jobs that use both
> all-in-one and multi-node test jobs with cephadm.
>
> Any objections?
Following up with some links:
The plugin's old installer code is here:
https://opendev.org/openstack/devstack-plugin-ceph/src/branch/master/devstack/lib/ceph
Patches on Gerrit to clean up this installer code:
https://review.opendev.org/q/topic:%22cleanup-ceph-installer%22
Thank you Goutham for working on this.
+1 to remove the package based deploy. cephadm is pretty stable at this point and it
covers all the use cases that devstack/lib/ceph used to take care of.
I'll keep following the cleanup topic and comment in case of issues, but in general
I'm in favor of only keeping a single deployment mechanism based on cephadm.
>
> Thanks,
> Goutham