Container deployment - Ceph-volume activation
Hello, TL;DR Looking for guidance on ceph-volume lvm activate --all as it would apply to a containerized ceph deployment (Nautilus or Octopus). Detail: I’m planning to upgrade my Nautilus non-container cluster to Octopus (eventually containerized). There’s an expanded procedure that was tested and working in our lab, however won’t go into the whole process. My question is around existing OSD hosts. I have to re-platform the host OS, and one of the ways in the OSDs were reactivated previously when this was done (non-containerized) was to install ceph packages, deploy keys, config, etc. then run ceph-volume lvm activate --all to magically bring up all OSDs. Looking for a similar approach except if the OSDs are containerized, and I re-platform the host OS (Centos -> Ubuntu), how could I reactivate all OSDs as containers and avoid rebuilding data on the OSDs? Thank you.
Hi, Assuming you are using cephadm? Checkout this https://docs.ceph.com/en/latest/cephadm/osd/#activate-existing-osds ceph cephadm osd activate <host>... 在 2021年3月11日，23:01，Cloud Guy <cloudguy25@gmail.com> 写道： Hello, TL;DR Looking for guidance on ceph-volume lvm activate --all as it would apply to a containerized ceph deployment (Nautilus or Octopus). Detail: I’m planning to upgrade my Nautilus non-container cluster to Octopus (eventually containerized). There’s an expanded procedure that was tested and working in our lab, however won’t go into the whole process. My question is around existing OSD hosts. I have to re-platform the host OS, and one of the ways in the OSDs were reactivated previously when this was done (non-containerized) was to install ceph packages, deploy keys, config, etc. then run ceph-volume lvm activate --all to magically bring up all OSDs. Looking for a similar approach except if the OSDs are containerized, and I re-platform the host OS (Centos -> Ubuntu), how could I reactivate all OSDs as containers and avoid rebuilding data on the OSDs? Thank you. _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
Am 11.03.21 um 18:40 schrieb 胡 玮文:
Hi,
Assuming you are using cephadm? Checkout this https://docs.ceph.com/en/latest/cephadm/osd/#activate-existing-osds
ceph cephadm osd activate <host>...
Might not be backported. see https://tracker.ceph.com/issues/46691#note-1 for the workaround
在 2021年3月11日，23:01，Cloud Guy <cloudguy25@gmail.com> 写道：
Hello,
TL;DR
Looking for guidance on ceph-volume lvm activate --all as it would apply to a containerized ceph deployment (Nautilus or Octopus).
Detail:
I’m planning to upgrade my Nautilus non-container cluster to Octopus (eventually containerized). There’s an expanded procedure that was tested and working in our lab, however won’t go into the whole process. My question is around existing OSD hosts.
I have to re-platform the host OS, and one of the ways in the OSDs were reactivated previously when this was done (non-containerized) was to install ceph packages, deploy keys, config, etc. then run ceph-volume lvm activate --all to magically bring up all OSDs.
Looking for a similar approach except if the OSDs are containerized, and I re-platform the host OS (Centos -> Ubuntu), how could I reactivate all OSDs as containers and avoid rebuilding data on the OSDs?
Thank you. _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
-- SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany (HRB 36809, AG Nürnberg). Geschäftsführer: Felix Imendörffer
Hi, The osd activate will probably be nice in the future, but for now I'm doing it like this:
ceph-volume activate --all for id in `ls -1 /var/lib/ceph/osd`; do echo cephadm adopt --style legacy --name ${id/ceph-/osd.}; done It's not ideal because you still need the ceph rpms installed and start each osd twice, but it's the only way I found to do this semi-automatically
K On 12/03/2021 14:09, Sebastian Wagner wrote:
Am 11.03.21 um 18:40 schrieb 胡 玮文:
Hi,
Assuming you are using cephadm? Checkout this https://docs.ceph.com/en/latest/cephadm/osd/#activate-existing-osds
ceph cephadm osd activate <host>...
Might not be backported.
see https://tracker.ceph.com/issues/46691#note-1 for the workaround
在 2021年3月11日，23:01，Cloud Guy <cloudguy25@gmail.com> 写道：
Hello,
TL;DR
Looking for guidance on ceph-volume lvm activate --all as it would apply to a containerized ceph deployment (Nautilus or Octopus).
Detail:
I’m planning to upgrade my Nautilus non-container cluster to Octopus (eventually containerized). There’s an expanded procedure that was tested and working in our lab, however won’t go into the whole process. My question is around existing OSD hosts.
I have to re-platform the host OS, and one of the ways in the OSDs were reactivated previously when this was done (non-containerized) was to install ceph packages, deploy keys, config, etc. then run ceph-volume lvm activate --all to magically bring up all OSDs.
Looking for a similar approach except if the OSDs are containerized, and I re-platform the host OS (Centos -> Ubuntu), how could I reactivate all OSDs as containers and avoid rebuilding data on the OSDs?
Thank you. _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
_______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
Thanks Everyone.. So it seems like the cephadm activate is a development branch capability currently.. And the workaround is to activate all as legacy daemons, then adopt as containers. Appreciate the inputs. Will try it out. From: Kenneth Waegeman <kenneth.waegeman@ugent.be> Date: Friday, March 12, 2021 at 10:37 To: Sebastian Wagner <swagner@suse.com>, 胡 玮文 <huww98@outlook.com>, Cloud Guy <cloudguy25@gmail.com> Cc: "ceph-users@ceph.io" <ceph-users@ceph.io> Subject: Re: [ceph-users] Re: Container deployment - Ceph-volume activation Hi, The osd activate will probably be nice in the future, but for now I'm doing it like this: ceph-volume activate --all for id in `ls -1 /var/lib/ceph/osd`; do echo cephadm adopt --style legacy --name ${id/ceph-/osd.}; done It's not ideal because you still need the ceph rpms installed and start each osd twice, but it's the only way I found to do this semi-automatically K On 12/03/2021 14:09, Sebastian Wagner wrote: Am 11.03.21 um 18:40 schrieb 胡 玮文: Hi, Assuming you are using cephadm? Checkout this https://docs.ceph.com/en/latest/cephadm/osd/#activate-existing-osds ceph cephadm osd activate <host>... Might not be backported. see https://tracker.ceph.com/issues/46691#note-1 for the workaround 在 2021年3月11日，23:01，Cloud Guy <cloudguy25@gmail.com><mailto:cloudguy25@gmail.com> 写道： Hello, TL;DR Looking for guidance on ceph-volume lvm activate --all as it would apply to a containerized ceph deployment (Nautilus or Octopus). Detail: I’m planning to upgrade my Nautilus non-container cluster to Octopus (eventually containerized). There’s an expanded procedure that was tested and working in our lab, however won’t go into the whole process. My question is around existing OSD hosts. I have to re-platform the host OS, and one of the ways in the OSDs were reactivated previously when this was done (non-containerized) was to install ceph packages, deploy keys, config, etc. then run ceph-volume lvm activate --all to magically bring up all OSDs. Looking for a similar approach except if the OSDs are containerized, and I re-platform the host OS (Centos -> Ubuntu), how could I reactivate all OSDs as containers and avoid rebuilding data on the OSDs? Thank you. _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io<mailto:ceph-users@ceph.io> To unsubscribe send an email to ceph-users-leave@ceph.io<mailto:ceph-users-leave@ceph.io> _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io<mailto:ceph-users@ceph.io> To unsubscribe send an email to ceph-users-leave@ceph.io<mailto:ceph-users-leave@ceph.io> _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io<mailto:ceph-users@ceph.io> To unsubscribe send an email to ceph-users-leave@ceph.io<mailto:ceph-users-leave@ceph.io>
participants (4)
-
Cloud Guy
-
Kenneth Waegeman
-
Sebastian Wagner
-
胡 玮文