Page History

...

1. On start of management server, if the key doesn't exist, it auto-generates one using SHA1 and stores it in db
2. Key is saved in encrypted form (db encryption is enabled) in the configuration table as hidden configuration with name upload.secret.key
   
3. During SSVM start-up, the key is passed on to it by management server 
4. SSVM stores this key in a file at /etc/cloudstack/agent/ms-psk
5. If the key sharing fails SSVM agent would shut itself down
6. Updating the PSK would involve the following:
   1. Delete the upload.secret.key config from configuration table in db
   2. Restart the MS, so that it gets regenerated again
   3. Destroy all the existing SSVMs
   4. When the new SSVMs starts up the key is copied to it
   5. There will be a window when the key is not in sync between management server and SSVMs

Sequence Diagram

Management server and SSVM agent interaction

...