You can define the UUID in the secret.xml file. That way you can generate one yourself, or let it autogenerate the first one for you and then use the same one on all the other compute nodes. In the Ceph docs, it actually generates one using "uuidgen", then puts that UUID in the secret.xml file itself. See the very last part here: http://ceph.com/docs/master/rbd/rbd-openstack/#setup-ceph-client-authentication Hope that's clear. It's definitely possible (and pretty much required) to have all the nodes have the same secret UUID -- as you saw, you only put one UUID into cinder. - Travis On Sat, May 24, 2014 at 9:39 AM, 10 minus <t10tennn at gmail.com> wrote: > Hi, > > I went through the docs fo setting up cinder with ceph. > > from the docs - I have to perform on every compute node > > virsh secret-define --file secret.xml > > The issue I see is that I have to perform this on 5 compute nodes and on > cinder it expects to have only one > > rbd_secret_uuid= uuid > > > as the former command will generate 5 uuids . How can I pass 5 uuids to > cinder > > Cheers > > > > _______________________________________________ > ceph-users mailing list > ceph-users at lists.ceph.com > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.ceph.com/pipermail/ceph-users-ceph.com/attachments/20140524/c53850fc/attachment.htm>
 |