On Wed, Sep 18, 2013 at 2:56 PM, Warren Wang <warren@xxxxxxxxxxxxx> wrote:
> Just got done deploying the largest ceph install I've had yet (9 boxes,
> 179TB), , and I used ceph-deploy, but not without much consternation. I
> have a question before I file a bug report.
>
> Is the expectation that the deploy host will never be used as the admin
> host?
I don't think we have that restriction with ceph-deploy.
I ran into various issues related to this. For instance, if you run
> ceph-deploy to (re)create osds, it will pull the boostrap keyring from
> /etc/ceph, if available, instead of your deployment dir.
Was this only when re-creating osds? Or both when creating and re-creating?
ceph-deploy will go through each host and retrieve the keyrings from
/var/lib/ceph/*
Depending on the command, for `gatherkeys` and osd's it would look for
(something similar to) this file:
/var/lib/ceph/bootstrap-osd/ceph.keyring
However, if you
> create a mon host, it assumes that it must be generated, so when you gather,
> you have a mismatch of keys between the mon and osd boxes.
For osds it does generate one though, this is the log output I get
(and what I would expect in your case):
[node1][INFO ] write cluster configuration to /etc/ceph/{cluster}.conf
[node1][INFO ] keyring file does not exist, creating one at:
/var/lib/ceph/bootstrap-osd/ceph.keyring
[node1][INFO ] create mon keyring file
>
> Should we not be using admin and deploy on the same box? I don't see a good
> reason why we shouldn't. I went through the changelog for today's release,
> but I don't see anything that addresses this.
It would help *a lot* to get some log output from what you describe as
a problem.
>
> Thanks,
> Warren
>
> _______________________________________________
> 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
