Ceph configuration data sharing requirements

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

 



Hi Ceph,

Configuring a Ceph cluster requires sharing data between clients and daemons. It would be helpful for the architecture of a puppet module to have a detailed descripiton of what these requirements are. As far as I understand there is:

* The IP address of at least one MON in the Ceph cluster

If cephx is disabled:

* no other requirement

If cephx is enabled:

* an admin user is created by providing a keyring file with its description when the first
  MON is bootstraped
  http://ceph.com/docs/next/dev/mon-bootstrap/

* users must be created by injecting them into the MONs, for instance with auth import
   https://github.com/ceph/ceph/blob/master/src/mon/MonCommands.h#L162
   or auth add. There is not need to ask the MONs for a key, although it can be done. It is
   not a requirement. When a user is created or later on, its capabilities can be set.

* an osd must be created by the mon which return an unique osd ID which is then used to
   further configure the osd.
   https://github.com/ceph/ceph/blob/master/src/mon/MonCommands.h#L471

* a client must be given a user id and a secret key

It would also be helpful to better understand why people are happy with the way ceph-deploy currently works and how it deals with these requirements.

Cheers

-- 
Loïc Dachary, Artisan Logiciel Libre
All that is necessary for the triumph of evil is that good people do nothing.


Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
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