** Also affects: horizon
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1337172
Title:
Topology for the stacks created from a nested template, template with
ResourceGroup resource and provider resource in the template doesn't
show the actual topology
Status in Orchestration API (Heat):
Triaged
Status in OpenStack Dashboard (Horizon):
New
Bug description:
Create stacks as mentioned below
1. Nested template
template 1 has server, volume and volume_attachment resources.
template 2 just has one resource of type "template 1". That is, template 2 is
a nested template.
create a stack using the template 2
This kind of template can be found at
https://github.com/hardys/demo_templates/tree/master/juno_summit_intro_to_heat/example2_server_with_volume_nested
2. provider resource in the template
template 1 has server, volume and volume_attachment resources.
template 2 defines the provider resource as follows
resource_registry:
My::Server::WithVolume: template 1
template 3 has only one resource of type "My::Server::WithVolume" (as
defined in resource_registry)
Create a stack using the template 3
This kind of template can be found at
https://github.com/hardys/demo_templates/tree/master/juno_summit_intro_to_heat/example4_provider_environment
3. ResourceGroup resource in the template
template 1 has server, volume and volume_attachment resources.
template 2 has resource group resource of type: OS::Heat::ResourceGroup and
points to the template 1 and define count > 1
Create a stack using template 2
This kind of template can be found at
https://github.com/hardys/demo_templates/tree/master/juno_summit_intro_to_heat/example3_server_with_volume_group
After the stacks are created, navigate to view the topology of the stacks.
In the topology of the each stack, we can see only one resource that is
defined in the template that is used to create the stack.
This is correct literally but doesn't make any sense.
Find the screen shot of the topologies attached to this bug.
For a nested template, shouldn't the resources from the template that is
being referred also needs to be displayed in the topology?
Same case for provider resource in the template and ResourceGroup
resource in the template
To manage notifications about this bug go to:
https://bugs.launchpad.net/heat/+bug/1337172/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
