Bases: ResourceInfo
Store the mapping of resource name to python class implementation.
Bases: object
Bases: MapResourceInfo
Store the mapping (with wild cards) of one resource type to another.
like: OS::Networking::* -> OS::Neutron::*
Also supports many-to-one mapping (mostly useful together with special “OS::Heat::None” resource)
like: OS::* -> OS::Heat::None
Bases: ResourceInfo
Store the mapping of one resource type to another.
like: OS::Networking::FloatingIp -> OS::Neutron::FloatingIp
Bases: object
Base mapping of resource type to implementation.
Bases: object
By looking at the environment, find the resource implementation.
Find possible matches to the resource type and name.
Chain the results from the global and user registry to find a match.
Returns a set of restricted actions.
For a given resource we get the set of restricted actions.
Actions are set in this format via resources:
{
"restricted_actions": [update, replace]
}
A restricted_actions value is either update, replace or a list of those values. Resources support wildcard matching. The asterisk sign matches everything.
Return a list of valid resource types.
Return whether a resource have a hook set in the environment.
For a given resource and a hook type, we check to see if the passed group of resources has the right hook associated with the name.
Hooks are set in this format via resources:
{
"res_name": {
"hooks": [pre-create, pre-update]
},
"*_suffix": {
"hooks": pre-create
},
"prefix_*": {
"hooks": pre-update
}
}
A hook value is either pre-create, pre-update or a list of those values. Resources support wildcard matching. The asterisk sign matches everything.
Bases: ResourceInfo
Store the info needed to start a TemplateResource.
Build a child environment using the parent environment and params.
This is built from the child_params and the parent env so some resources can use user-provided parameters as if they come from an environment.
resource_registry must be merged (child env should be loaded after the parent env to take precedence).
child parameters must overwrite the parent’s as they won’t be relevant in the child template.
If child_resource_name is provided, resources in the registry will be replaced with the contents of the matching child resource plus anything that passes a wildcard match.
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.