Re: Disabling automatic provisioning of OSD's

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

 



Ah, looks like ceph orch rm osd.dashboard-admin-1603406157941 actually did
the trick despite the docs saying it would only work for a group of
stateless services.

Op zo 21 nov. 2021 om 13:31 schreef Tinco Andringa <tinco@xxxxxxxxxxx>:

> Thank you Weiwen Hu, your idea pointed me towards looking into the
> orchestrator. There I discovered there's a bunch of osd services and it's a
> bit of a mess:|
>
> *tinco@automator-1*:*~*$ sudo ceph orch ls osd
>
> NAME                               RUNNING  REFRESHED  AGE  PLACEMENT    IMAGE
> NAME                  IMAGE ID
>
> osd.None                              51/0  4m ago     -    <unmanaged>
> quay.io/ceph/ceph:v15.2.14  mix
>
> osd.all-available-devices              0/3  -          -    <unmanaged>  <unknown>
>                   <unknown>
>
> osd.dashboard-admin-1603406157941      0/2  4m ago     13M  *
> quay.io/ceph/ceph:v15.2.14  <unknown>
>
> osd.dashboard-admin-1603812430616      0/1  -          -    big-data-1   <unknown>
>                   <unknown>
>
> osd.dashboard-admin-1603812754993      0/1  -          -    big-data-1   <unknown>
>                   <unknown>
>
>
> So some of them indeed are unmanaged, and some of them are not. I wanted
> to run your idea of updating the unmanaged value in the spec and running it
> with --dry-run first, but the dry run feature doesn't seem to work. If I
> make no changes to the spec at all, I get this output:
>
> *tinco@automator-1*:*~*$ sudo ceph orch apply -i osd_spec_old.yaml
> --dry-run
>
> [sudo] password for tinco:
>
> WARNING! Dry-Runs are snapshots of a certain point in time and are bound
>
> to the current inventory setup. If any on these conditions changes, the
>
> preview will be invalid. Please make sure to have a minimal
>
> timeframe between planning and applying the specs.
>
> ####################
>
> SERVICESPEC PREVIEWS
>
> ####################
>
> +---------+------+--------+-------------+
>
> |SERVICE  |NAME  |ADD_TO  |REMOVE_FROM  |
>
> +---------+------+--------+-------------+
>
> +---------+------+--------+-------------+
>
> ################
>
> OSDSPEC PREVIEWS
>
> ################
>
> +---------+------+------+------+----+-----+
>
> |SERVICE  |NAME  |HOST  |DATA  |DB  |WAL  |
>
> +---------+------+------+------+----+-----+
>
> +---------+------+------+------+----+-----+
>
>
>
> That doesn't look right to me, shouldn't it show all services as they
> currently are?
>
> I want to clean up the mess that's currently in there, how do I mark the
> existing services for deletion, I couldn't find this in the documentation
> of the orchestrator.
>
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx



[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux