openstack/heat
Code Issues Proposed changes
heat/contrib/rackspace
History
Christopher Armstrong 90e29eaf46 RS LoadBalancer should return its ID as Ref 
Previously the Rackspace::Cloud::LoadBalancer resource returned the name as
its reference ID. This patch reverts this to the default resource behavior
of returning the resource ID if available, and then falling back to the
name. Otherwise there is no way to access the ID of the load balancer,
which is necessary for other Rackspace APIs, such as Rackspace Auto Scale.

Closes-Bug: #1241194
Change-Id: Ib5ca296b338e912daa8c3dc1c71fc3e994a0156e
2013-10-21 22:26:20 +00:00
..
heat
RS LoadBalancer should return its ID as Ref
2013-10-21 22:26:20 +00:00
__init__.py
Move Rackspace resources into contrib
2013-09-24 12:39:58 -05:00
README.md
Move Rackspace resources into contrib
2013-09-24 12:39:58 -05:00

README.md

Heat resources for working with the Rackspace Cloud

The resources and configuration in this module are for using Heat with the Rackspace Cloud. These resources either allow using Rackspace services that don't have equivalent services in Openstack or account for differences between a generic Openstack deployment and Rackspace Cloud.

Resources

The following resources are provided for compatibility:

  • Rackspace::Cloud::Server:

Provide compatibility with OS::Nova::Server and allow for working user_data and Metadata. This is deprecated and should be replaced with OS::Nova::Server once service compatibility is implemented by Rackspace.

  • Rackspace::Cloud::LoadBalancer:

Use the Rackspace Cloud Loadbalancer service; not compatible with OS::Neutron::LoadBalancer.

  • Rackspace::Cloud::DatabaseInstance:

Use the Rackspace implementation of Trove. This is deprecated and should eventually be replaced with OS::Trove::Instance or similar.

Usage

Templates

Configuration