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

Bug #1337172 reported by Ashraf Vazeer
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Heat
Triaged
Wishlist
Unassigned
heat-dashboard
Triaged
Medium
Unassigned

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

Tags: heat
Revision history for this message
Ashraf Vazeer (ashraf-vazeer) wrote :
Revision history for this message
Ashraf Vazeer (ashraf-vazeer) wrote :

screen shot of topology for provider resource in the template

Revision history for this message
Ashraf Vazeer (ashraf-vazeer) wrote :

screen shot of topology for ResourceGroup resource in the template

Revision history for this message
Steve Baker (steve-stevebaker) wrote :

Yes, the topology diagram is technically correct, but not very useful.

In the short term, the topology diagram could be enhanced so that clicking on a nested stack resource will load the topology diagram for the nested stack.

Longer term once blueprint https://github.com/openstack/heat-specs/blob/master/specs/explode-nested-resources.rst is implemented there could be an option in all of the tabs for a stack to display the exploded resources, not just the ones in the parent stack.

Changed in heat:
status: New → Triaged
importance: Undecided → Wishlist
Akihiro Motoki (amotoki)
tags: added: heat
Angus Salkeld (asalkeld)
tags: removed: heat
Changed in horizon:
importance: Undecided → Medium
status: New → Triaged
tags: added: heat
Revision history for this message
Akihiro Motoki (amotoki) wrote :

heat panel is split out to heat-dashboard. Retargeting to heat-dashboard.

affects: horizon → heat-dashboard
Rico Lin (rico-lin)
Changed in heat:
milestone: none → no-priority-tag-bugs
Revision history for this message
Sharmistha (prasad-sharmistha) wrote :

Hi,

I am also facing the same issue.
Can you please let me know if this will be fixed in pike ?

Regards,
Sharmistha

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.