I sense the concern about ceph distributions via containers generally
has to do with what you might call a feeling of 'opaqueness'. The
feeling is amplified as most folks who choose open source solutions
prize being able promptly to address the particular concerns affecting
them without having to wait for 'the next (might as well be opaque)
release'.
An easy way forward might be if the ceph devs would document an approved
set of steps that would add to the current ability to 'ssh in' to a
container to make on the fly changes. If there was a cephadm command
to 'save the current state of a container' in a format that adds a
'.lcl.1' '.lcl.2' , then smooth the command line process to allow the
cephadm upgrade process to use those saved local images with the local
changes as targets, so as to automate pushing out the changes to the rest?
??
Harry Coin
_______________________________________________
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io
