David Vallee Delisle 0f7ce2cfa6 Adding oslo.config entry points for yaql and cache opts
To assist with automated configuration validation, we need entry points
for oslo.config.opts for yaql and cache options.

Change-Id: I228282d2c05f6583fe972470b326e7182f635b39
2024-01-09 10:39:46 +09:00
2023-03-22 17:16:30 +00:00
2023-10-18 00:17:55 +09:00
2023-03-22 17:16:30 +00:00
2019-04-22 09:36:50 +05:30
2020-09-10 14:19:03 -04:00
2019-04-19 19:33:28 +00:00
2023-03-22 17:16:30 +00:00
2017-12-15 12:39:37 +05:30
2018-07-27 13:38:27 +00:00
2018-01-28 09:11:18 +05:30
2020-04-09 14:14:38 +08:00
2023-06-14 04:09:52 +09: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://opendev.org/openstack/heat

Python client

Report a Story (a bug/blueprint)

If you'd like to report a Story (we used to call a bug/blueprint), you can report it under Report a story in Heat's StoryBoard. If you must report the story under other sub-project of heat, you can find them all in Heat StoryBoard Group. if you encounter any issue.

References

We have integration with

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