You could also place the mon, mds and mgr daemons in containers - these don't have to be docker containers - you can also use LXD on Ubuntu which gives you a full system container.

This is the approach that the OpenStack Charms deployment tooling takes - it allows each personality within the deployment to be upgraded individually.

On Wed, Aug 28, 2019 at 10:41 AM Mark Schouten <mark@tuxis.nl> wrote:
Cool, thanks!

--

Mark Schouten <mark@tuxis.nl>

Tuxis, Ede, https://www.tuxis.nl

T: +31 318 200208 

 

----- Originele bericht -----
Van: James Page (james.page@canonical.com)
Datum: 28-08-2019 11:02
Naar: Mark Schouten (mark@tuxis.nl)
Cc: ceph-users@ceph.io
Onderwerp: Re: [ceph-users] Upgrade procedure on Ubuntu Bionic with stock packages

Hi Mark

On Wed, Aug 28, 2019 at 9:51 AM Mark Schouten <mark@tuxis.nl> wrote:
Hi,

I have a cluster running on Ubuntu Bionic, with stock Ubuntu Ceph packages. When upgrading, I always try to follow the procedure as documented here: https://docs.ceph.com/docs/master/install/upgrading-ceph/

However, the Ubuntu packages restart all daemons upon upgrade, per node. So if I upgrade the first node, it will restart mon, osds, rgw, and mds'es on that node, even though the rest of the cluster is running the old version.

I tried upgrading a single package, to see how that goes, but due to dependencies in dpkg, all other packages are upgraded as well.

This is a known issue in the Ceph packages in Ubuntu:


the behaviour of debhelper (which generates snippets for maintainer scripts) changed and it was missed - fix being worked on at the moment.

Cheers

James