973b7ea6b7
Since contrib plugins may not be installed at the time the docs are generated, the resource_mapping function needs to return all resource types defined by the resource module. To selectively load such resource types - based on requirements being met, for instance, the available_resource_mapping function should be used instead. This makes the necessary changes to Rackspace::Cloud::Network so that its docs are generated correctly. Related-Bug: 1403897 Change-Id: I7c12c055924e7a16a5b9cc573d91c12089a2395d |
||
---|---|---|
.. | ||
rackspace | ||
README.md | ||
requirements.txt | ||
setup.cfg | ||
setup.py |
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.
1. Install the Rackspace plugins in Heat
NOTE: These instructions assume the value of heat.conf plugin_dirs includes the default directory /usr/lib/heat.
To install the plugin, from this directory run: sudo python ./setup.py install
2. Restart heat
Only the process "heat-engine" needs to be restarted to load the newly installed plugin.
Resources
The following resources are provided for compatibility:
Rackspace::Cloud::Server
:
Provide compatibility with
OS::Nova::Server
and allow for workinguser_data
andMetadata
. This is deprecated and should be replaced withOS::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.