[openstack-dev] [openstack][magnum][heat]problems for synchronizing stack parameters from heat

王华 wanghua.humble at gmail.com
Fri Aug 14 09:34:59 UTC 2015


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 <clint at fewbar.com> wrote:

> 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 heat, too. But heat
> > don't allow admin user to show stack in other tenants, so we can not get
> > stack parameters.
> >
> > I think it is necessary. Nova allows admin user to show instance in other
> > tenants. Neutron allow admin user to show port in other tenants. Nova
> uses
> > it to synchronize network info for instance from neutron. So can heat
> allow
> > admin user to show stack in other tenants?
> >
>
> This seems like a problem for trusts to solve. Why are you not using
> trusts to fetch the stack _as the user_?


> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150814/af0274b1/attachment.html>


More information about the OpenStack-dev mailing list