Allow instance user_data to be updated
A feature of Heat is to allow updates to existing compute servers triggered by changes to polled data.
Currently compute servers must poll for changes via a cfn API metadata lookup, which requires authentication to be delivered to the server, plus extra complexity in the heat template to enable this authentication.
This same data exists in the nova metadata server http://
This blueprint proposes that nova allows user_data to be updated via the server update API, with corresponding support in novaclient.
Blueprint information
- Status:
- Not started
- Approver:
- sean mooney
- Priority:
- Undefined
- Drafter:
- Steve Baker
- Direction:
- Approved
- Assignee:
- Jan Hartkopf
- Definition:
- Approved
- Series goal:
- Accepted for zed
- Implementation:
-
Deferred
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Allow user_data to be updated on nova API update
Addressed by: https:/
Implement a v3 API extension to update user_data
Gerrit topic: https:/
Addressed by: https:/
Allow user_data to be updated on nova API update
Addressed by: https:/
Implement a v3 API extension to update user_data
If you are still working on this, please re-submit via nova-specs. If not, please mark as obsolete, and add a quick comment to describe why. --johnthetubaguy (20th April 2014)
I am not currently pursuing this approach. Heat doesn't currently require the user_data to be updatable after boot.
Addressed by: https:/
Allow user_data to be updated
Addressed by: https:/
Allow modification of user-data via the server update
[bauzas 20220517] Spec was approved
Gerrit topic: https:/
Addressed by: https:/
Repropose spec for updating user data
