Re: handling osd removal with ceph-volume?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Oct 29, 2018 at 6:36 PM Noah Watkins <nwatkins@xxxxxxxxxx> wrote:
>
> On Fri, Oct 26, 2018 at 5:06 AM Alfredo Deza <adeza@xxxxxxxxxx> wrote:
> >
> > There are a couple of reasons why 'deactivate' hasn't made it into
> > ceph-volume. One of them is that, it wasn't clear (to me) if
> > deactivation meant full removal/purging of the OSD or if
> > it meant to leave it in a state where it wouldn't start (e.g.
> > disabling the systemd units).
> >
> > My guess is that there is a need for both and for a few more use
> > cases, like disabling the systemd unit so that the same OSD can be
> > provisioned. So far we've concentrated in the creation of OSDs
> > surpassing ceph-disk
> > features, but I think that we can start exploring the complexity of
> > deactivation now.
>
> Would it be fair to say that the blocker right now is an enumeration
> of the use cases and a proposed update to the CLI command set to
> handle those cases?

That would surely help prioritize. Thanks Noah!



[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux