ceph osd create XX

ceph osd create XX

[Stefan Priebe]

Hello List,

ceph osd create $NUM

does not seem to work anymore ;-(

# ceph osd createosd. 62
unknown command createosd

Crushmap is already changed and imported ceph.conf is altered and reloaded.

Greets
Stefan

Re: ceph osd create XX

[Gregory Farnum]

On Wed, Dec 12, 2012 at 1:31 PM, Stefan Priebe <s.priebe@profihost.ag> wrote:
> Hello List,
>
> ceph osd create $NUM
>
> does not seem to work anymore ;-(
>
> # ceph osd createosd. 62
> unknown command createosd

Read those two lines again. Very slowly. :)

The correct syntax is
ceph osd create <uuid>

The uuid is optional, but you don't specify IDs; it gives you an ID back.
-Greg

>
> Crushmap is already changed and imported ceph.conf is altered and reloaded.
>
> Greets
> Stefan
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: ceph osd create XX

[Stefan Priebe]

HI Greg,

sorry just a copy & paste error.

[cloud1-ceph1: ~]# ceph osd create 61
(22) Invalid argument

> Read those two lines again. Very slowly. :)
>
> The correct syntax is
> ceph osd create <uuid>
>
> The uuid is optional, but you don't specify IDs; it gives you an ID back.

Stefan

Re: ceph osd create XX

[Gregory Farnum]

Yeah; 61 is not a valid UUID and you can't specify anything else on that line.

On Wed, Dec 12, 2012 at 1:38 PM, Stefan Priebe <s.priebe@profihost.ag> wrote:
> HI Greg,
>
> sorry just a copy & paste error.
>
> [cloud1-ceph1: ~]# ceph osd create 61
> (22) Invalid argument
>
>
>> Read those two lines again. Very slowly. :)
>>
>> The correct syntax is
>> ceph osd create <uuid>
>>
>> The uuid is optional, but you don't specify IDs; it gives you an ID back.
>
>
> Stefan

Re: ceph osd create XX

[Stefan Priebe]

Hi Greg,

i don't get it. I was using this doc:
http://ceph.com/docs/master/rados/operations/add-or-rm-osds/

There is written that i have to use the osd-num for ceph osd create. 
Which UUID is now meant?

I've already added osd.61,62,63 and 64 to ceph.conf

Greets,
Stefan
Am 12.12.2012 22:41, schrieb Gregory Farnum:
> Yeah; 61 is not a valid UUID and you can't specify anything else on that line.
>
> On Wed, Dec 12, 2012 at 1:38 PM, Stefan Priebe <s.priebe@profihost.ag> wrote:
>> HI Greg,
>>
>> sorry just a copy & paste error.
>>
>> [cloud1-ceph1: ~]# ceph osd create 61
>> (22) Invalid argument
>>
>>
>>> Read those two lines again. Very slowly. :)
>>>
>>> The correct syntax is
>>> ceph osd create <uuid>
>>>
>>> The uuid is optional, but you don't specify IDs; it gives you an ID back.
>>
>>
>> Stefan
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

Re: ceph osd create XX

[Gregory Farnum]

On Wed, Dec 12, 2012 at 1:43 PM, Stefan Priebe <s.priebe@profihost.ag> wrote:
> Hi Greg,
>
> i don't get it. I was using this doc:
> http://ceph.com/docs/master/rados/operations/add-or-rm-osds/
>
> There is written that i have to use the osd-num for ceph osd create. Which
> UUID is now meant?

Ah, you're right — I don't think that doc has been correct since
before argonaut, but prior to ~v0.55 it wouldn't complain on non-UUID
values.

The basic "ceph osd create" call simply allocates a new OSD ID and
bumps the max allowed, and returns the new ID back to the caller. If
you also specify the UUID, then it will check and see if that UUID
already exists and simply return the allocated ID if it does
(otherwise, create a new one as before). In argonaut, there's a bug
that will silently ignore any non-UUID extra arguments, which is what
was happening with those IDs.

John, can you fix this in the docs please? :)
-Greg

(All this is assuming I've got my commit dates right; if not there
might be a bit of variation about when which version took effect.)


> I've already added osd.61,62,63 and 64 to ceph.conf
>
> Greets,
> Stefan
> Am 12.12.2012 22:41, schrieb Gregory Farnum:
>>
>> Yeah; 61 is not a valid UUID and you can't specify anything else on that
>> line.
>>
>> On Wed, Dec 12, 2012 at 1:38 PM, Stefan Priebe <s.priebe@profihost.ag>
>> wrote:
>>>
>>> HI Greg,
>>>
>>> sorry just a copy & paste error.
>>>
>>> [cloud1-ceph1: ~]# ceph osd create 61
>>> (22) Invalid argument
>>>
>>>
>>>> Read those two lines again. Very slowly. :)
>>>>
>>>> The correct syntax is
>>>> ceph osd create <uuid>
>>>>
>>>> The uuid is optional, but you don't specify IDs; it gives you an ID
>>>> back.
>>>
>>>
>>>
>>> Stefan
>>
>> --
>>
>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: ceph osd create XX

[Stefan Priebe]

Hi Greg,

thanks for explanation. I'm using current next branch.

I'm using:
host1:
osd 11 .. 14
host2:
osd 21 .. 24
host3:
osd 31 .. 34
host4:
osd 41 .. 44
host5:
osd 51 .. 54

Right now i want to add host6. But i still don't know even with your 
explanation how to add osd 61-64 to osdmap.

Greets Stefan
Am 12.12.2012 22:57, schrieb Gregory Farnum:
> On Wed, Dec 12, 2012 at 1:43 PM, Stefan Priebe <s.priebe@profihost.ag> wrote:
>> Hi Greg,
>>
>> i don't get it. I was using this doc:
>> http://ceph.com/docs/master/rados/operations/add-or-rm-osds/
>>
>> There is written that i have to use the osd-num for ceph osd create. Which
>> UUID is now meant?
>
> Ah, you're right — I don't think that doc has been correct since
> before argonaut, but prior to ~v0.55 it wouldn't complain on non-UUID
> values.
>
> The basic "ceph osd create" call simply allocates a new OSD ID and
> bumps the max allowed, and returns the new ID back to the caller. If
> you also specify the UUID, then it will check and see if that UUID
> already exists and simply return the allocated ID if it does
> (otherwise, create a new one as before). In argonaut, there's a bug
> that will silently ignore any non-UUID extra arguments, which is what
> was happening with those IDs.
>
> John, can you fix this in the docs please? :)
> -Greg
>
> (All this is assuming I've got my commit dates right; if not there
> might be a bit of variation about when which version took effect.)
>
>
>> I've already added osd.61,62,63 and 64 to ceph.conf
>>
>> Greets,
>> Stefan
>> Am 12.12.2012 22:41, schrieb Gregory Farnum:
>>>
>>> Yeah; 61 is not a valid UUID and you can't specify anything else on that
>>> line.
>>>
>>> On Wed, Dec 12, 2012 at 1:38 PM, Stefan Priebe <s.priebe@profihost.ag>
>>> wrote:
>>>>
>>>> HI Greg,
>>>>
>>>> sorry just a copy & paste error.
>>>>
>>>> [cloud1-ceph1: ~]# ceph osd create 61
>>>> (22) Invalid argument
>>>>
>>>>
>>>>> Read those two lines again. Very slowly. :)
>>>>>
>>>>> The correct syntax is
>>>>> ceph osd create <uuid>
>>>>>
>>>>> The uuid is optional, but you don't specify IDs; it gives you an ID
>>>>> back.
>>>>
>>>>
>>>>
>>>> Stefan
>>>
>>> --
>>>
>>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>>
>>
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: ceph osd create XX

[Gregory Farnum]

On Wed, Dec 12, 2012 at 2:00 PM, Stefan Priebe <s.priebe@profihost.ag> wrote:
> Hi Greg,
>
> thanks for explanation. I'm using current next branch.
>
> I'm using:
> host1:
> osd 11 .. 14
> host2:
> osd 21 .. 24
> host3:
> osd 31 .. 34
> host4:
> osd 41 .. 44
> host5:
> osd 51 .. 54
>
> Right now i want to add host6. But i still don't know even with your
> explanation how to add osd 61-64 to osdmap.

Yeah, it's not going to let you allocate non-sequential IDs at this
point, sorry. We are slowly divorcing the ID and the name, but it's
not done yet...

Re: ceph osd create XX

[Stefan Priebe]

ah OK good to know.

UUIDs are a good decision but right now the journal devices (if you use 
a block device) are still absolute.

[osd.23]
         host = cloud1-ceph2
         public addr = 10.255.0.101
         cluster addr = 10.255.0.101
         osd journal  = /dev/sdd1

Greets,
Stefan

Am 12.12.2012 23:09, schrieb Gregory Farnum:
> On Wed, Dec 12, 2012 at 2:00 PM, Stefan Priebe <s.priebe@profihost.ag> wrote:
>> Hi Greg,
>>
>> thanks for explanation. I'm using current next branch.
>>
>> I'm using:
>> host1:
>> osd 11 .. 14
>> host2:
>> osd 21 .. 24
>> host3:
>> osd 31 .. 34
>> host4:
>> osd 41 .. 44
>> host5:
>> osd 51 .. 54
>>
>> Right now i want to add host6. But i still don't know even with your
>> explanation how to add osd 61-64 to osdmap.
>
> Yeah, it's not going to let you allocate non-sequential IDs at this
> point, sorry. We are slowly divorcing the ID and the name, but it's
> not done yet...
>