00bddf04da
Provider network map directly to an existing physical network in
a data center. It's routable by default. Neutron v2.0 API implements
it using Provider Networks Neutron API Extension. This is different
from tenant network(implemented by 'OS::Neutron::Net'resource) and has
different requirements.
This ('OS::Neutron::ProviderNet') resource leverages additional
attributes as listed below from Neutron API extension.
provider:network_type - Specifies the nature of the physical network
mapped to this network resource. Examples are flat and vlan.
provider:physical_network - Identifies the physical network on top of
which this network object is being implemented.
provider:segmentation_id - Identifies an isolated segment on the
physical network.
Change-Id: Ic085d13c866722b0e6ed9fd7a4f43dd92d5b1a0b
Implements: blueprint neutron-net-resource-add-provider-network
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
- Wiki: http://wiki.openstack.org/Heat
- Developer docs: http://docs.openstack.org/developer/heat
Python client
https://github.com/openstack/python-heatclient
References
- http://docs.amazonwebservices.com/AWSCloudFormation/latest/APIReference/API_CreateStack.html
- http://docs.amazonwebservices.com/AWSCloudFormation/latest/UserGuide/create-stack.html
- http://docs.amazonwebservices.com/AWSCloudFormation/latest/UserGuide/aws-template-resource-type-ref.html
- http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=tosca