Signaling SoftwareDeployment resources via Swift

Registered by Steve Baker on 2015-01-28

Currently the only option for signaling a deployment resource requires making
an authenticated API request to heat. A SoftwareDeployment resource
signal_transport: TEMP_URL_POLL will allow unauthenticated signaling using a
similar approach to OS::Heat::SwiftSignal.

Problem description
===================

OS::Heat::SoftwareDeployment signal_transport options currently both require
resource scoped credentials and network connectivity from the server to a
heat API to work.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Medium
Drafter:
Steve Baker
Direction:
Needs approval
Assignee:
Steve Baker
Definition:
Drafting
Series goal:
Accepted for kilo
Implementation:
Implemented
Milestone target:
milestone icon 2015.1.0
Started by
Angus Salkeld on 2015-02-02
Completed by
Angus Salkeld on 2015-03-09

Related branches

Sprints

Whiteboard

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

Addressed by: https://review.openstack.org/151526
    Deployment signal_transport: TEMP_URL_SIGNAL

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

Addressed by: https://review.openstack.org/113711
    Integration test for software-config tools

Addressed by: https://review.openstack.org/157210
    Move deployment handle_signal to rpc call

Addressed by: https://review.openstack.org/164897
    heat.conf options for transport properties default

Addressed by: https://review.openstack.org/131602
    Signaling SoftwareDeployment resources via Swift

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.