HI Guys,
It was gr8 to find your interest in solving the nested stack resource
listing.
Lets move ahead by finishing any discussions left over the BP and getting
an approval on It.
Till now what makes sense to me are :
a) an additional flag in the client call --nested (randall)
b) A flattened
Hey, sorry for the slow follow. I have to put some finishing touches on a spec
and submit that for review. I'll reply to the list with the link later today.
Hope to have an initial patch up as well in the next day or so.
On Jun 5, 2014, at 10:03 AM, Nilakhya Chatterjee
I have submitted a new/expanded spec for this feature:
https://review.openstack.org/#/c/98219/. I hope to start some WiP patches this
afternoon/tomorrow morning. Spec reviews and input most welcome.
On Jun 5, 2014, at 11:35 AM, Randall Burt randall.b...@rackspace.com wrote:
Hey, sorry for the
I've submitted the spec (finally) and will work on some initial patches this
afternoon/tomorrow. Please provide any feedback and thanks!
https://review.openstack.org/#/c/98219
On Jun 5, 2014, at 11:35 AM, Randall Burt randall.b...@rackspace.com wrote:
Hey, sorry for the slow follow. I have to
Hi Tim,
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?
Best,
Bartosz
On 05/19/2014 09:13 PM, Tim Schnell wrote:
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.
On May 20, 2014, at 1:24 PM, Bartosz Górski bartosz.gor...@ntti3.com
wrote:
Hi Tim,
Maybe instead of just a flag like --nested (bool value) to resource-list we
can add
Nilakhya, We discussed this a bit at the summit and I think the consensus was
that this would be a good thing to do by passing a flag to resource-list that
would flatten the structure of nested stacks in the call. Tim Schnell brought
this up as well and may be interested in helping define the
Excerpts from Tim Schnell's message of 2014-05-19 08:26:22 -0700:
Hi Nilakhya,
As Randall mentioned we did discuss this exact issue at the summit. I was
planning on putting a blueprint together today to continue the discussion.
The Stack Preview call is already doing the necessary recursion
On Mon, May 19, 2014 at 03:26:22PM +, Tim Schnell wrote:
Hi Nilakhya,
As Randall mentioned we did discuss this exact issue at the summit. I was
planning on putting a blueprint together today to continue the discussion.
The Stack Preview call is already doing the necessary recursion to
On May 19, 2014, at 11:39 AM, Steven Hardy sha...@redhat.com
wrote:
On Mon, May 19, 2014 at 03:26:22PM +, Tim Schnell wrote:
Hi Nilakhya,
As Randall mentioned we did discuss this exact issue at the summit. I was
planning on putting a blueprint together today to continue the discussion.
On 5/19/14 12:35 PM, Randall Burt randall.b...@rackspace.com wrote:
On May 19, 2014, at 11:39 AM, Steven Hardy sha...@redhat.com
wrote:
On Mon, May 19, 2014 at 03:26:22PM +, Tim Schnell wrote:
Hi Nilakhya,
As Randall mentioned we did discuss this exact issue at the summit. I
was
Blueprint:
https://blueprints.launchpad.net/heat/+spec/explode-nested-resources
Spec: https://wiki.openstack.org/wiki/Heat/explode-resource-list
Tim
On 5/19/14 1:53 PM, Tim Schnell tim.schn...@rackspace.com wrote:
On 5/19/14 12:35 PM, Randall Burt randall.b...@rackspace.com wrote:
On May
Hi All,
I recently tried to create a nested stack with the following example :
http://paste.openstack.org/show/79156/
heat resource-list gives only MyStack but intention should be to list
all the resources created by the nested templates, as also pointed by the
command help:
resource-list
# heat stack-create -f example.yaml
# heat stack-list
Assume the stack id is: 5d44526e-e75c-4cec-aeea-252d6d15254b
# heat resource-list 5d44526e-e75c-4cec-aeea-252d6d15254b
You get the resource named 'MyStack'. To check the details:
# heat resource-show 5d44526e-e75c-4cec-aeea-252d6d15254b
14 matches
Mail list logo
