Hot Software Config Component

Registered by JunJie Nan on 2013-08-01

Software config component in heat is a resource which is used to define software configuration.

Software config component is hosted on a server. One or more software configs can be hosted on one instance resource.

There may be dependencies between software config components.

Blueprint information

Status:
Complete
Approver:
Steve Baker
Priority:
High
Drafter:
JunJie Nan
Direction:
Approved
Assignee:
Steve Baker
Definition:
Approved
Series goal:
Accepted for icehouse
Implementation:
Implemented
Milestone target:
milestone icon 2014.1
Started by
JunJie Nan on 2013-08-14
Completed by
Steve Baker on 2014-03-11

Related branches

Sprints

Whiteboard

Discussion moved to: https://etherpad.openstack.org/p/software-config-component

Gerrit topic: https://review.openstack.org/#q,topic:bp/hot-software-config,n,z

Addressed by: https://review.openstack.org/40842 -- deprecated
    Hot SoftwareConfig model part

Addressed by: https://review.openstack.org/41641 -- deprecated
    Hot software config config set translation

Gerrit topic: https://review.openstack.org/#q,topic:bp/i,n,z

Addressed by: https://review.openstack.org/58873 -- deprecated
    Add heatclient to available clients

Addressed by: https://review.openstack.org/58874
    Property methods for resource metadata

Addressed by: https://review.openstack.org/58875
    Service authorize stack user from provided stack

Addressed by: https://review.openstack.org/58876
    Database model for software config/deployment

Addressed by: https://review.openstack.org/58877
    RPC service for software config/deployment

Addressed by: https://review.openstack.org/58878
    REST API for software config/deployment

Addressed by: https://review.openstack.org/58879
    Resource types for software config/deployment

Addressed by: https://review.openstack.org/58880
    OS::Nova::Server support for software config

Addressed by: https://review.openstack.org/57546
    Add heatclient to available clients

Addressed by: https://review.openstack.org/59110
    Make build_userdata user_data_format aware

Addressed by: https://review.openstack.org/59111
    Instance call build_userdata directly

Addressed by: https://review.openstack.org/61902
    Allow choice in how SignalResponder user id is stored.

Gerrit topic: https://review.openstack.org/#q,topic:bp/cloud-init-resource,n,z

Addressed by: https://review.openstack.org/67621
    Resource type for software configuration

Addressed by: https://review.openstack.org/67624
    Resource type implementation for software deployment

Addressed by: https://review.openstack.org/67625
    OS::Nova::Server support for software config

Addressed by: https://review.openstack.org/69238
    Nova server to ref cloud-config resources in user_data

Addressed by: https://review.openstack.org/72199
    Function to query all deployments for a server

Addressed by: https://review.openstack.org/74205
    SignalResponder move signed URL deleting to its own method

Addressed by: https://review.openstack.org/74206
    Resource type implementation for structured software config

Addressed by: https://review.openstack.org/76369
    Raise NotFound in software_config_get/software_deployment_get

Addressed by: https://review.openstack.org/74203
    REST deployment metadata method

Addressed by: https://review.openstack.org/74202
    RPC method to fetch deployments metadata

Addressed by: https://review.openstack.org/77061
    Change software_config storage of config and io columns

Addressed by: https://review.openstack.org/77798
    Server property for software config transport

Addressed by: https://review.openstack.org/77799
    Remove signal_id from deployments API and model

Addressed by: https://review.openstack.org/81407
    Document software config classes

Addressed by: https://review.openstack.org/80169
    Provide the necessary inputs to enable HEAT_SIGNAL

Addressed by: https://review.openstack.org/80869
    Implement an identifier stack_path()

Addressed by: https://review.openstack.org/80868
    Store stack domain credentials for deployments

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.