Re: [ceph-users] Deterministic naming of LVM volumes (ceph-volume)

2017-12-13 Thread Webert de Souza Lima
On Wed, Dec 13, 2017 at 11:51 AM, Stefan Kooman wrote: > If we want to remove the OSD (for whatever reason) and release the ID then > we > will use "ceph osd purge* osd.$ID" ... which basically does what you > suggest (ceph auth del osd.$OSD_ID, crush remove osd.$OSD_ID, ceph osd

Re: [ceph-users] Deterministic naming of LVM volumes (ceph-volume)

2017-12-13 Thread Stefan Kooman
Quoting Burkhard Linke (burkhard.li...@computational.bio.uni-giessen.de): > Just my 2 cents: > > What is happening if ansible runs on multiple hosts in parallel? We won't do that to avoid race conditions that might arise. We don't need parallel deployment of massive amount of OSDs overnight, so

Re: [ceph-users] Deterministic naming of LVM volumes (ceph-volume)

2017-12-13 Thread Stefan Kooman
Quoting Webert de Souza Lima (webert.b...@gmail.com): > Cool > > > On Wed, Dec 13, 2017 at 11:04 AM, Stefan Kooman wrote: > > > So, a "ceph osd ls" should give us a list, and we will pick the smallest > > available number as the new osd id to use. We will make a check in the > >

Re: [ceph-users] Deterministic naming of LVM volumes (ceph-volume)

2017-12-13 Thread Burkhard Linke
Hi, On 12/13/2017 02:12 PM, Webert de Souza Lima wrote: Cool On Wed, Dec 13, 2017 at 11:04 AM, Stefan Kooman > wrote: So, a "ceph osd ls" should give us a list, and we will pick the smallest available number as the new osd id to use. We

Re: [ceph-users] Deterministic naming of LVM volumes (ceph-volume)

2017-12-13 Thread Webert de Souza Lima
Cool On Wed, Dec 13, 2017 at 11:04 AM, Stefan Kooman wrote: > So, a "ceph osd ls" should give us a list, and we will pick the smallest > available number as the new osd id to use. We will make a check in the > (ansible) deployment code to see Ceph will indeed use that number. >

Re: [ceph-users] Deterministic naming of LVM volumes (ceph-volume)

2017-12-13 Thread Stefan Kooman
Quoting Willem Jan Withagen (w...@digiware.nl): > LOG.debug('Allocating OSD id...') > secrets = Secrets() > try: > wanttobe = read_one_line(path, 'wanttobe') > if os.path.exists(os.path.join(path, 'wanttobe')): > os.unlink(os.path.join(path, 'wanttobe')) >

Re: [ceph-users] Deterministic naming of LVM volumes (ceph-volume)

2017-12-13 Thread Stefan Kooman
Quoting Webert de Souza Lima (webert.b...@gmail.com): > if I may suggest, "ceph osd create" allocates and returns an OSD ID. So you > could take it by doing: > > ID=$(ceph osd create) > > then remove it with > > ceph osd rm $ID > > Now you have the $ID and you can deploy it with ceph-volume

Re: [ceph-users] Deterministic naming of LVM volumes (ceph-volume)

2017-12-13 Thread Webert de Souza Lima
Hello, On Wed, Dec 13, 2017 at 7:36 AM, Stefan Kooman wrote: > Hi, > > Is there a way to ask Ceph which OSD_ID > would be next up? if I may suggest, "ceph osd create" allocates and returns an OSD ID. So you could take it by doing: ID=$(ceph osd create) then remove it with

Re: [ceph-users] Deterministic naming of LVM volumes (ceph-volume)

2017-12-13 Thread Willem Jan Withagen
On 13-12-2017 10:36, Stefan Kooman wrote: > Hi, > > The new style "ceph-volume" LVM way of provisioning OSDs introduces a > little challange for us. In order to create the OSDs as logical, > consistent and easily recognizable as possible, we try to name the > Volume Groups (VG) and Logical

[ceph-users] Deterministic naming of LVM volumes (ceph-volume)

2017-12-13 Thread Stefan Kooman
Hi, The new style "ceph-volume" LVM way of provisioning OSDs introduces a little challange for us. In order to create the OSDs as logical, consistent and easily recognizable as possible, we try to name the Volume Groups (VG) and Logical Volumes (LV) the same as the OSD. For example: OSD no. 12