Wow, that was quite simple mkdir /var/lib/ceph/mds/ceph-0 ceph auth get-or-create mds.0 mds 'allow' osd 'allow *' mon 'allow *' > /var/lib/ceph/mds/ceph-0/keyring ceph-mds --id 0
mount -t ceph ceph-mon01:6789:/ /mnt -o name=admin,secret=<client.admin secret> Can you confirm that I need the caps above for the MDS, or can it get away with far less? Also, what is the state of the various *rank parameters? I see that the doco says that only one MDS should be used, but what is the plans on how those parameters should be used. For example, say I wanted to co-host mon and mds services, 3 or 5 of them. What would appropriate settings for each be? Cheers Adam On Fri, Apr 11, 2014 at 10:42 AM, Gregory Farnum <g...@inktank.com> wrote: > I don't know if there's any formal documentation, but it's a lot simpler > than the other components because it doesn't use any local storage (except > for the keyring). You basically just need to generate a key and turn it on. > Have you set one up by hand before? > -Greg > > > On Thursday, April 10, 2014, Adam Clark <clark.ada...@gmail.com> wrote: > >> Hey all, >> I am working through orchestrating the build of various ceph components >> using Puppet. >> >> So far the stackforge puppet-ceph has given me a heap to go on, but it is >> largely unfinished. >> >> I have sorted out the manual procedure for the MONs and OSDs via the >> documentation but there is scant information on how to manually deploy the >> the MDS. >> >> Only ceph-deploy. >> >> Is the manual procedure documented somewhere? >> >> Cheers >> >> Adam >> >> >> > > -- > Software Engineer #42 @ http://inktank.com | http://ceph.com >
_______________________________________________ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
