| 2014-09-08 18:46:48 |
Mike Spreitzer |
description |
In a HOT, you can use a filename as a resource type --- but this is not documented. I am not entirely sure whether this is true generally or is only a feature of the new scaling groups. I am not sure whether I should be saying filename or relative URL reference.
For an example of such usage, look at the template hot/autoscaling.yaml in the heat-templates project; note how it uses "lb_server.yaml" as a resource type. Note that lb_server.yaml is NOT a provider template, rather it is one of the user's templates. I am able to create a stack from autoscaling.yaml using the Heat CLI but NOT using the dashboard; in the latter case an error arises because the lb_server.yaml file does not get packaged into the request. |
In a HOT, you can use a filename as a resource type --- but this is not documented. I am not entirely sure whether this is true generally or is only a feature of the new scaling groups. I am not sure whether I should be saying filename or relative URL reference.
For an example of such usage, look at the template hot/autoscaling.yaml in the heat-templates project; note how it uses "lb_server.yaml" as a resource type. Note that lb_server.yaml is NOT a provider template, rather it is one of the user's templates.
FYI, not as part of this bug (it is already a separate bug, https://bugs.launchpad.net/horizon/+bug/1322258): I am able to create a stack from autoscaling.yaml using the Heat CLI but NOT using the dashboard; in the latter case an error arises because the lb_server.yaml file does not get packaged into the request. |
|
