Thanks a lot Janne, Well, maybe I'm missunderstanding how ceph stores keyrings in etcd...
https://github.com/ceph/ceph-container/blob/master/src/daemon/config.kv.etcd.sh bootstrap="bootstrap${array[1]}Keyring" etcdctl "${ETCDCTL_OPTS[@]}" "${KV_TLS[@]}" set "${CLUSTER_PATH}"/" ${bootstrap}" < "$keyring" But I'd like to know what happens if etcd loses the keyrings sotred in it when etcd is used to deploy ceph daemons as containers: https://hub.docker.com/r/ceph/daemon/ With KV backend: docker run -d --net=host \ --privileged=true \ --pid=host \ -v /dev/:/dev/ \ -e OSD_DEVICE=/dev/vdd \ -e KV_TYPE=etcd \ -e KV_IP=192.168.0.20 \ ceph/daemon osd Thanks a lot for your help, Óscar El mar., 16 jul. 2019 17:34, Janne Johansson <[email protected]> escribió: > Den mån 15 juli 2019 kl 23:05 skrev Oscar Segarra <[email protected] > >: > >> Hi Frank, >> Thanks a lot for your quick response. >> Yes, the use case that concerns me is the following: >> 1.- I bootstrap a complete cluster mons, osds, mgr, mds, nfs, etc using >> etcd as a key store >> > > as a key store ... for what? Are you stuffing anything ceph-related there? > If so, please tell us what. > > As previously said, ceph has no etcd concept so unless you somehow pull > stuff out of ceph and feed it into etcd, ceph will be completely careless > if you lose etcd data. > > -- > May the most significant bit of your life be positive. >
_______________________________________________ ceph-users mailing list [email protected] http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
