Candidates for live cluster configuration update
by Simental Magana, Marcos
Hello,
I'd like to get some feedback about which fields in the current configuration
payload would be candidates for live updates.
Below I'm pasting the current template of the configuration file
and the purposed action to be done in the case the setting can be updated with
the cluster up and running or why it cannot be updated:
`/etc/ciao/configuration.yaml`
---
configure:
scheduler:
storage_uri: YES / write new config yaml to new location, write configuration{TIMESTAMP}.yaml backup previously to rw
storage:
ceph_id: ??? (unknown on-change behaviour)
controller:
compute_port: YES / test an API call(TBD) with new controller port
compute_ca: NO / certificates should change only on controller reboot
compute_cert: NO / certificates should change only on controller reboot
identity_user: NO / user should change only on controller reboot
identity_password: NO / password should change only on controller reboot
launcher:
compute_net: NO / It would require reset of the tunnel (expensive)
mgmt_net: NO / It would require reset of the tunnel (expensive)
disk_limit: YES / change launcher setup of disk_limit
mem_limit: YES / change launcher setup of mem_limit
image_service:
type: *UNUSED*
url: *UNUSED*
identity_service:
type: YES / test an API call(TBD) with new type
url: YES / test an API call(TBD) with new url
In the case of the compute certificates and the identity credentials I purpose not to change them
due to security issues, if the admin credentials of the cluster were compromised would be really easy to
change also the certificates without taking the cluster down.
The respective github issue about this topic is https://github.com/01org/ciao/issues/1050
--
Don't Panic!
Marcos Simental.
