Crag Wolfe 0550659f5f Store resource attributes in the DB
Store resource attributes that may be cached in the DB, saving the
cost of re-resolving them later. This works for most resources,
specifically those that do not override the get_attribute() method.

Change-Id: I71f8aa431a60457326167b8c82adc03ca750eda6
Partial-Bug: #1660831
2017-06-21 20:18:46 -04:00
2017-03-25 17:11:50 +08:00
2017-06-21 20:18:46 -04:00
2017-03-24 11:58:38 +08:00
2017-04-06 11:42:05 -07:00
2017-04-03 09:32:25 +00:00
2012-12-02 17:46:15 +00:00
2012-03-14 09:25:54 +11:00
2017-01-18 11:50:52 +08:00
2017-03-02 17:42:22 +00:00
2016-01-17 05:20:40 +00:00

Team and repository tags

image

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 https://git.openstack.org/openstack/heat

Python client

https://git.openstack.org/cgit/openstack/python-heatclient

References

We have integration with

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