It will help any person with problem with ceph cookbook to ask question
Hi, I have some questions regarding the cookbook...
Ok, I'll rather make a pull request and let's see
sorry I didn't get any notification
Good afternoon. Was just trying to figure out if there was currently a way to add osd location information, i.e. in my case a datacenter name, which would be configured on a per-node basis?
Looks like nobody's around at the moment so I'll ask this as an issue.
Can someone please help me with using these cookbooks to setup federated ceph
Hi @akshatknsl exactly would you like to do? An all on one host installation for test usecases?
@treenerd I am looking to setup a federated rados gateway
which will have 1 region and 2 zones using the same storage cluster
wanted assistance in using the cookbooks to setup a federated gateway
@jsuchome@hufman ....can you guys also help me out
Sorry @akshatknsl I never used the radosgw part of that cookbook; So I don't have experience with it. We used that cookbook for tests with ceph as backend for our Opennebula/KVM infrastructure. Hope someone can help you with the radosgw;
I've made a pull request to help set up radosgw with different pool settings, #154. However, there isn't support for actually creating the pools
additionally, the cookbook doesn't yet have support for running the federation daemon, because i haven't gotten it figured out yet
I'm having issues with using the ceph-cookbook to bootstrap a new cluster
It seems when I'm setting up the first monitor, I get stopped at the point where it's trying to get the key for client.boostrap-osd
I don't remember the exact output of the command when run manually, but I believe it was an issue of not being able to authenticate
So I manually added a client.admin user/key and with that was able to run ceph auth list, which didn't show a client.bootstrap-osd
Adding subsequent monitor nodes required having the client.admin key in place for them to proceed past the same step.
Sergio de Carvalho
Hi, I'm having trouble to deploy a Ceph cluster with the ceph-cookbook using an encrypted data bag (EDB) to store the monitor and OSD secrets (I can deploy a cluster just fine if I'm not using an EDB). This is what I'm doing: I've manually created 2 random secret keys and uploaded them to an EDB on my Chef server. I can then deploy the first node with a monitor using the mon secret stored in the EDB. However, once this node is deployed and the cluster is up, a bootstrap-osd key is automatically generated in the auth system. As a result, when another node of the cluster is deployed with an OSD daemon, the OSD secret stored in the EDB obviously won't match the one generated by the first node, and the OSD then fails to activate. The OSD recipe retrieves the OSD secret from the EDB but I don't see how this secret ever gets imported into the cluster. I'd appreciate if anyone could help me understand how the cookbook works with EDBs. Thanks!
Thanks, @tomzo. I have already deployed Ceph with the ceph-cookbook without EDB but security is a major concern for me right now and I don't keys exposed on node attributes. I've read the code many times over but just can't see how it could possibly work once EDB is enabled. I'm actually wondering if anyone is using the ceph-cookbook with EDB.
Sergio de Carvalho
I've created a pull request with a change that makes the cookbook work for me with EDB: ceph/ceph-cookbook#201