The engine includes custom Heat resource types that represent resources on cloud systems
and artifacts from the IBM® UrbanCode™ Deploy
server.
These custom Heat types are in addition to the standard Heat resource types.
For more
information about the Heat Orchestration Templates (HOT), see the following reference
information.http://docs.openstack.org/developer/heat/template_guide/hot_spec.html. The standard resource types are described on the following page: http://docs.openstack.org/developer/heat/template_guide/index.html.To see a list of the types that are installed on your engine,
open a command-line window and run the following
command:
heat resource-type-list
To see information about a
specific type, including its properties, use the
heat resource-type-show
command. For example, to see information about the
IBM::UrbanCode::SoftwareDeploy::UCD type, run the following
command:
heat resource-type-show IBM::UrbanCode::SoftwareDeploy::UCD
Not
all properties that are inherited from standard Heat resource types are implemented in the
custom Heat types. See the individual topics about the custom types for details about which
properties are implemented.
Resource types have properties and
attributes. Properties are input values; properties are typically bound to
properties in the blueprint. Attributes are output values that can be referenced from other
places.