Subject: Re: [openstack-dev] [openstack][magnum][heat]problems for
synchronizing stack parameters from heat
Hi all,
Magnum creates a stack when a bay is created and update the stack
parameters when the bay is updated. Magnum has a periodic task
to synchronize stack status from
We can get stacks by stack list call, but it does not provide info about
stack parameters. If we need stack parameters, we have to use stack.get.
Yeah that part is right. I believe we consider stack parameters somewhat
private to the user, which may be the reason they are not easily
Magnum creates a stack when a bay is created and update the stack
parameters when the bay is updated. Magnum needs a periodic task to synchronize
stack status and parameters from heat to keep data consistency.
Regards,
Wanghua
On Fri, Aug 14, 2015 at 5:02 PM, Thomas Herve the...@redhat.com
Hi all,
Magnum creates a stack when a bay is created and update the stack
parameters when the bay is updated. Magnum has a periodic task
to synchronize stack status from heat.
And now we want to synchronize stack parameters from heat, too. But heat
don't allow admin user to show stack
Excerpts from 王华's message of 2015-08-14 00:52:43 -0700:
Hi all,
Magnum creates a stack when a bay is created and update the stack
parameters when the bay is updated. Magnum has a periodic task
to synchronize stack status from heat.
And now we want to synchronize stack parameters from
We can get stacks by stack list call, but it does not provide info about
stack parameters. If we need stack parameters, we have to use stack.get.
Regards,
Wanghua
On Fri, Aug 14, 2015 at 4:30 PM, Thomas Herve the...@redhat.com wrote:
Hi all,
Magnum creates a stack when a bay is created
Can this option be used for in show stack details call?
Date: Fri, 14 Aug 2015 04:30:19 -0400
From: the...@redhat.com
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [openstack][magnum][heat]problems for
synchronizing stack parameters from heat
Hi all,
Magnum
On Fri, Aug 14, 2015 at 05:34:59PM +0800, 王华 wrote:
Hi Clint Byrum,
Trusts can solve this problem, but it may cause performance problem.
When we want to get a stack, we need to get the trust_id from db first,
andA
authenticate with the trust_id, then we can get the stack. A
Hi Clint Byrum,
Trusts can solve this problem, but it may cause performance problem.
When we want to get a stack, we need to get the trust_id from db first, and
authenticate with the trust_id, then we can get the stack.
On Fri, Aug 14, 2015 at 5:13 PM, Clint Byrum cl...@fewbar.com wrote:
Excerpts from 王华's message of 2015-08-14 02:34:59 -0700:
Hi Clint Byrum,
Trusts can solve this problem, but it may cause performance problem.
When we want to get a stack, we need to get the trust_id from db first, and
authenticate with the trust_id, then we can get the stack.
Indeed,
10 matches
Mail list logo
