Go to file
Sergey Kraynev 9a9b27c926 Handle replace and rollback cases for Port
Add prepare_for_replace and restore_after_rollback methods for port
resource. Now if port has fixed_ip address it will be correctly handled
during UpdateReplace, i.e. we detach this ip and store it in self.data.
In case, when rollback happens, fixed_ips data will be taken from
self.data of resource in _backup_stack.

Follow functional tests was added:
 - enable test with simple replacing port
 - test for failed update with rollback
 - test for failed update without rollback and second repair update

implements bp rich-network-prop

Change-Id: Id3877ed8cb1097f6c93725806d137ea67ab07466
Closes-Bug: #1455100
2015-09-16 14:05:45 +00:00
2012-12-02 17:46:15 +00:00
2012-03-14 09:25:54 +11:00
2015-07-08 09:13:35 -04:00
2015-04-28 16:47:07 -04:00
2015-06-23 08:30:39 +02:00
2015-08-28 14:43:37 +05:30
2015-09-03 08:45:49 +08:00
2015-09-07 21:28:44 +03:00
2015-07-15 07:33:24 +00:00
2015-09-08 09:18:36 +05:30
2012-06-23 22:41:30 -04:00

Heat

Heat is a service to orchestrate multiple composite cloud applications using templates, through both an OpenStack-native REST API and a CloudFormation-compatible Query API.

Why heat? It makes the clouds rise and keeps them there.

Getting Started

If you'd like to run from the master branch, you can clone the git repo:

git clone git@github.com:openstack/heat.git

Python client

https://github.com/openstack/python-heatclient

References

We have integration with

Description
OpenStack Orchestration (Heat)
Readme 215 MiB
Languages
Python 99.5%
Shell 0.5%