Bug 1041434

Summary:	[RFE][nova]: Allow instance user_data to be updated
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	RFEs	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	markmc, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/nova/+spec/update-userdata
Whiteboard:	upstream_milestone_none upstream_status_unknown upstream_definition_obsolete
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-19 17:14:23 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description RHOS Integration 2013-12-12 16:07:17 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/update-userdata.

Description:

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://169.254.169.254/latest/user-data but it is currently not possible to update this data on a running instance.

This blueprint proposes that nova allows user_data to be updated via the server update API, with corresponding support in novaclient.

Specification URL (additional information):

None