openstack/deb-heat
Code Issues Proposed changes
5859c68bf0
deb-heat/contrib/rackspace
History
Anderson Mesquita bc9a1cc9c1 Restructure Rackspace resources 
During doc generation, resources have their own templates and need
to be separate from non-resource modules.  This removes the ``heat``
``engine`` and ``plugins`` folders and moves all resources into a
``resources`` folder, effectively separating the custom Rackspace
Client from custom Rackspace resources.

Partial-Bug: #1271226
Change-Id: Idbdc8400d30e2e745a2dc1b2d2fa1b7cff50d57b
2014-02-06 09:12:30 -06:00
..
resources Restructure Rackspace resources 2014-02-06 09:12:30 -06:00
tests Restructure Rackspace resources 2014-02-06 09:12:30 -06:00
__init__.py Resources for Rackspace Auto Scale 2013-10-30 16:39:18 +00:00
clients.py Restructure Rackspace resources 2014-02-06 09:12:30 -06: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