Re: Question about the OSD host option

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

 



mon.* and osd.* sections are not mandatory in config. So unless you want to set something per daemon, you can skip them completely.

On 17-04-21 19:07, Fabian wrote:
Hi Everyone,

I play a bit around with ceph on a test cluster with 3 servers (each MON
and OSD at the same time). 
I use some self written ansible rules to deploy the config and crate
the OSD with ceph-disk. Because ceph-disk use the next free OSD-ID, my
ansible scrip is not aware which ID belongs to which OSD and host. So I
don't create any [OSD.ID] section in my config and my cluster runs
fine. 

Now I have read in [1] "the Ceph configuration file MUST specify the
host for each daemon". As I consider each OSD as daemon, I'm a bit
confused that it worked without the host specified. 

Why do the OSD daemon need the host option? What happened if it doesn't
exist? 

Is there any best practice about naming the OSDs? Or a trick to avoid
the [OSD.ID] for each daemon?

[1]http://docs.ceph.com/docs/master/rados/configuration/network-config-ref/#ceph-daemons

Thank you,

Fabian


_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com


_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

[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