Go to file
Steve Baker 7470a5e919 Deployment signal_transport: TEMP_URL_SIGNAL
This change allows swift TempURLs to be used to signal heat from
server deployments.

When signal_transport: TEMP_URL_SIGNAL is specified, the following will happen:
* On creation a swift object will be created with an associated TempURL for PUTs
* The PUT URL is used for the deploy_signal_id input value, along with the new
  deploy_signal_verb input being set to PUT
* In the deployment resource check_complete, the swift object is polled for
  new signal contents, and signal() is called when the swift object contents change

By specifying deployment signal_transport: TEMP_URL_SIGNAL and
server software_config_transport: POLL_TEMP_URL it should now be possible to use
config/deployment resources with only a keystone v2 API (or with a standalone heat)

Implements-Blueprint: software-config-swift-signal

Change-Id: I1dfba248dcfc90c3d872ba35f0aa935cca5c5606
2015-02-25 13:48:52 +13:00
2015-02-02 13:05:46 +05:30
2015-01-23 16:02:53 +00:00
2012-12-02 17:46:15 +00:00
2014-03-03 10:49:28 -05:00
2012-03-14 09:25:54 +11:00
2014-06-26 06:45:52 +02:00
2014-12-15 10:55:09 +02:00
2014-05-09 02:42:01 +00:00
2012-06-23 22:41:30 -04:00
Description
OpenStack Orchestration (Heat)
Readme 215 MiB
Languages
Python 99.5%
Shell 0.5%