<div dir="ltr"><div><div><div><div><div><div>HI Guys, <br><br></div>It was gr8 to find your interest in solving the nested stack resource listing.<br><br></div>Lets move ahead by finishing any discussions left over the BP and getting an approval on It.<br>
<br></div>Till now what makes sense to me are : <br><br></div>a) an additional flag in the client call --nested (randall)<br></div>b) A flattened DS in the output (tim) <br><br><br></div>Thanks all ! <br></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Wed, May 21, 2014 at 12:42 AM, Randall Burt <span dir="ltr"><<a href="mailto:randall.burt@rackspace.com" target="_blank">randall.burt@rackspace.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Bartosz, would that be in addition to --nested? Seems like id want to be able to say "all of it" as well as "some of it".<br>
<br>
On May 20, 2014, at 1:24 PM, Bartosz Górski <<a href="mailto:bartosz.gorski@ntti3.com">bartosz.gorski@ntti3.com</a>><br>
<div class="HOEnZb"><div class="h5"> wrote:<br>
<br>
> Hi Tim,<br>
><br>
> Maybe instead of just a flag like --nested (bool value) to resource-list we can add optional argument like --depth X or --nested-level X (X - integer value) to limit the depth for recursive listing of nested resources?<br>
><br>
> Best,<br>
> Bartosz<br>
><br>
> On 05/19/2014 09:13 PM, Tim Schnell wrote:<br>
>> Blueprint:<br>
>> <a href="https://blueprints.launchpad.net/heat/+spec/explode-nested-resources" target="_blank">https://blueprints.launchpad.net/heat/+spec/explode-nested-resources</a><br>
>><br>
>> Spec: <a href="https://wiki.openstack.org/wiki/Heat/explode-resource-list" target="_blank">https://wiki.openstack.org/wiki/Heat/explode-resource-list</a><br>
>><br>
>> Tim<br>
>><br>
>> On 5/19/14 1:53 PM, "Tim Schnell" <<a href="mailto:tim.schnell@RACKSPACE.COM">tim.schnell@RACKSPACE.COM</a>> wrote:<br>
>><br>
>>> On 5/19/14 12:35 PM, "Randall Burt" <<a href="mailto:randall.burt@RACKSPACE.COM">randall.burt@RACKSPACE.COM</a>> wrote:<br>
>>><br>
>>><br>
>>>> On May 19, 2014, at 11:39 AM, Steven Hardy <<a href="mailto:shardy@redhat.com">shardy@redhat.com</a>><br>
>>>> wrote:<br>
>>>><br>
>>>>> On Mon, May 19, 2014 at 03:26:22PM +0000, Tim Schnell wrote:<br>
>>>>>> Hi Nilakhya,<br>
>>>>>><br>
>>>>>> As Randall mentioned we did discuss this exact issue at the summit. I<br>
>>>>>> was<br>
>>>>>> planning on putting a blueprint together today to continue the<br>
>>>>>> discussion.<br>
>>>>>> The Stack Preview call is already doing the necessary recursion to<br>
>>>>>> gather<br>
>>>>>> the resources so we discussed being able to pass a stack id to the<br>
>>>>>> preview<br>
>>>>>> endpoint to get all of the resources.<br>
>>>>>><br>
>>>>>> However, after thinking about it some more, I agree with Randall that<br>
>>>>>> maybe this should be an extra query parameter passed to the<br>
>>>>>> resource-list<br>
>>>>>> call. I'Ll have the blueprint up later today, unless you have already<br>
>>>>>> started on it.<br>
>>>>> Note there is a patch from Anderson/Richard which may help with this:<br>
>>>>><br>
>>>>> <a href="https://review.openstack.org/#/c/85781/" target="_blank">https://review.openstack.org/#/c/85781/</a><br>
>>>>><br>
>>>>> The idea was to enable easier introspection of resources backed by<br>
>>>>> nested<br>
>>>>> stacks in a UI, but it could be equally useful to generate a "tree"<br>
>>>>> resource view in the CLI client by walking the links.<br>
>>>>><br>
>>>>> This would obviously be less efficient than recursing inside the<br>
>>>>> engine,<br>
>>>>> but arguably the output would be much more useful if it retains the<br>
>>>>> nesting<br>
>>>>> structure, as opposed to presenting a fully flattened "soup" of<br>
>>>>> resources<br>
>>>>> with no idea which stack/layer they belong to.<br>
>>>>><br>
>>>>> Steve<br>
>>>> Could we simply add stack name/id to this output if the flag is passed? I<br>
>>>> agree that we currently have the capability to traverse the tree<br>
>>>> structure of nested stacks, but several folks have requested this<br>
>>>> capability, mostly for UI/UX purposes. It would be faster if you want the<br>
>>>> flat structure and we still retain the capability to create your own<br>
>>>> tree/widget/whatever by following the links. Also, I think its best to<br>
>>>> include this in the API directly since not all users are integrating<br>
>>>> using the python-heatclient.<br>
>>> +1 for adding the stack name/id to the output to maintain a reference to<br>
>>> the initial stack that the resource belongs to. The original stated<br>
>>> use-case that I am aware of was to have a flat list of all resources<br>
>>> associated with a stack to be displayed in the UI when the user prompts to<br>
>>> delete a stack. This would prevent confusion about what and why different<br>
>>> resources are being deleted due to the stack delete.<br>
>>><br>
>>> This use-case does not require any information about the nested stacks but<br>
>>> I can foresee that information being useful in the future. I think a<br>
>>> flattened data structure (with a reference to stack id) is still the most<br>
>>> efficient solution. The patch landed by Anderson/Richard provides an<br>
>>> alternate method to drill down into nested stacks if the hierarchy is<br>
>>> important information though this is not the optimal solution in this<br>
>>> case.<br>
>>><br>
>>> Tim<br>
>>>><br>
>>>> _______________________________________________<br>
>>>> OpenStack-dev mailing list<br>
>>>> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
>>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>>><br>
>>> _______________________________________________<br>
>>> OpenStack-dev mailing list<br>
>>> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>><br>
>> _______________________________________________<br>
>> OpenStack-dev mailing list<br>
>> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
><br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div dir="ltr"><font size="-1"><br><span style="vertical-align:baseline;font-variant:normal;font-style:normal;font-size:12px;background-color:transparent;text-decoration:none;font-family:Arial;font-weight:bold">Nilakhya | Consultant Engineering</span><br>
<span style="vertical-align:baseline;font-variant:normal;font-style:normal;font-size:12px;background-color:transparent;text-decoration:none;font-family:Arial;font-weight:normal">GlobalLogic</span><br><span style="vertical-align:baseline;font-variant:normal;font-style:normal;font-size:12px;background-color:transparent;text-decoration:none;font-family:Arial;font-weight:normal">P +x.xxx.xxx.xxxx M +91.989.112.5770 S skype</span><br>
<a href="http://www.globallogic.com/" target="_blank"><span style="font-size:12px;font-family:Arial;color:#1155cc;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:underline;vertical-align:baseline">www.globallogic.com</span></a><span style="vertical-align:baseline;font-variant:normal;font-style:normal;font-size:12px;background-color:transparent;text-decoration:none;font-family:Arial;font-weight:normal"></span><br>
<a href="http://www.globallogic.com/" target="_blank"><span style="font-size:12px;font-family:Arial;color:#1155cc;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:underline;vertical-align:baseline"></span></a><br>
<a href="http://www.globallogic.com/email_disclaimer.txt" target="_blank"><span style="font-size:11px;font-family:Arial;color:#1155cc;background-color:transparent;font-weight:normal;font-style:normal;font-variant:normal;text-decoration:underline;vertical-align:baseline">http://www.globallogic.com/email_disclaimer.txt</span></a><span style="vertical-align:baseline;font-variant:normal;font-style:normal;font-size:11px;background-color:transparent;text-decoration:none;font-family:Arial;font-weight:normal"></span></font></div>
</div>