Steve Baker ceb26ad46a Sometimes use quantum for SecurityGroup
This implements the following properties in AWS::EC2::SecurityGroup
- VpcId
- SecurityGroupEgress

If VpcId is specified, completely separate code paths
are used which make quantum calls instead of nova calls.

This implements blueprint quantum-security-group

This is based off https://review.openstack.org/#/c/22280/
with a few enhancements:
- Quantum firewall rules translated to acceptable format for ICMP
- remote_ip_prefix used for security group rule creation

Change-Id: I8f1953cb559da0e97821ae0072dfb01dc8267c0c
Signed-off-by: Jeff Peeler <jpeeler@redhat.com>
2013-05-02 16:12:44 -04:00
2013-04-24 09:18:15 +12:00
2013-05-01 10:33:30 -07:00
2013-04-30 13:51:31 -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-03-20 14:21:08 -04:00
2013-02-18 17:27:14 +00:00
2013-05-01 10:33:30 -07:00
2013-03-19 14:54:35 -07: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

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