Ceph » mgr

According to the output of vstart.sh --help, the -k option is supposed to "keep old configuration files". However, this does not seem to apply to configuration data stored in the MONs, in particular the dashboard's username and password as well as the SSL certificate and key that was created during the initial vstart run:

# OSD=5 MON=3 MDS=0 RGW=1 ../src/vstart.sh -k
rm -f core* 
hostname metis
ip 192.168.178.21
port 40838
/ceph/build/bin/ceph-mon -i a -c /ceph/build/ceph.conf 
/ceph/build/bin/ceph-mon -i b -c /ceph/build/ceph.conf 
/ceph/build/bin/ceph-mon -i c -c /ceph/build/ceph.conf 
Populating config ...
/ceph/build/bin/ceph -c /ceph/build/ceph.conf -k /ceph/build/keyring config set mgr mgr/dashboard/x/server_port 41838 
/ceph/build/bin/ceph -c /ceph/build/ceph.conf -k /ceph/build/keyring config set mgr mgr/restful/x/server_port 42838 
Starting mgr.x
/ceph/build/bin/ceph-mgr -i x -c /ceph/build/ceph.conf 
/ceph/build/bin/ceph -c /ceph/build/ceph.conf -k /ceph/build/keyring tell mgr dashboard set-login-credentials admin admin 
Username and password updated
/ceph/build/bin/ceph -c /ceph/build/ceph.conf -k /ceph/build/keyring tell mgr dashboard create-self-signed-cert 
Self-signed certificate created

This makes it difficult to test certain things, e.g. when storing custom SSL certificates and performing a restart of the Manager in order to activate the new certificate.

When using the -k option, I would expect that the vstart script also preserves these kind of configuration changes.