Luis A. Garcia 9004239b9f Enable localizable REST API responses via the Accept-Language header
Add support for doing language resolution for a request, based on the
Accept-Language HTTP header. Using the lazy gettext functionality, from
oslo gettextutils, it is possible to use the resolved language to
translate exception messages to the user requested language and
return that translation from the API.

The patch removes individually imported _() so they don't replace the
one installed service-wide.

Also, it adds the ability to fully re-create a remote error
with the same kwargs with which it was originally created, so that we
can translate it and show it to the user.

Partially implements bp user-locale-api.

Change-Id: I63edc8463836bfff257daa8a2c66ed5d3a444254
2013-08-03 00:19:17 +00:00
2013-07-27 11:37:32 +12:00
2013-07-24 11:02:22 +12:00
2013-07-18 12:01:02 -07:00
2012-12-02 17:46:15 +00:00
2013-04-30 13:51:07 -07:00
2012-03-14 09:25:54 +11:00
2013-05-25 08:46:32 +02:00
2013-07-13 09:17:14 -07:00
2013-05-29 12:50:45 +00:00
2013-05-25 08:35:00 +02:00
2013-07-22 06:54:50 +00:00
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

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