Native Tools - Bootstrap instance configuration

Registered by Clint Byrum on 2013-08-16

The purpose of bootstrapping an orchestrated server is to provide just enough package installation and configuration to be able to hand off to a full Configuration Management tool. Traditionally this has been achieved in heat templates with cfn-init from the heat-cfntools package however this has the following issues:

It needs to be invoked explicitly from the template UserData
It is limited to providing cfn compatible functionality
It acts on a single block of metadata which is associated with the instance resource, which makes it difficult to write templates that are composable (ie, templates which split the application configuration from the architecture the application is being orchestrated into).
Heat's current underlying implementation relies on cloud-init to deliver the Metadata and the UserData script to the instance on boot.

This blueprint proposes that the functionality of blessed configuration management tools be directly exposed in heat templates to fulfill server config tasks.

Blueprint information

Status:
Complete
Approver:
Steve Baker
Priority:
High
Drafter:
Steve Baker
Direction:
Approved
Assignee:
Steve Baker
Definition:
Obsolete
Series goal:
None
Implementation:
Not started
Milestone target:
None
Completed by
Steve Baker on 2013-11-19

Related branches

Sprints

Whiteboard

This blueprint will morph into a proposal for some cloud-init heat resources

Actually this can be obsoleted by blueprint cloud-init-resource

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.