Hi Hongbin,
We have presented some approaches to this that extend Heat resources to
talk to native cloud API in EC2 and SoftLayer. Here's the OpenStack Summit
talk that described what we've done in this space:
OpenStack Summit Slides http://slidesha.re/1lyeFNs
OpenStack Summit Video
with Heat software
configurations and KeystoneV2
On Sun, Apr 06, 2014 at 10:22:15PM -0400, Michael Elder wrote:
If Keystone is configured with an external identity provider (LDAP,
OpenID, etc), how does the creation of a new user per resource affect
that
external identity source?
My
Adam,
I was imprecise, thank you for correcting that error.
I think the net of the statement still holds though: the Keystone token
mechanism defines a mechanism for authorization, why doesn't the heat
stack manage a token for any behavior that requires authorization?
-M
@lists.openstack.org
Date: 04/06/2014 09:16 PM
Subject:Re: [openstack-dev] [heat] Problems with Heat software
configurations and KeystoneV2
On 07/04/14 12:52, Michael Elder wrote:
I think the net of the statement still holds though: the Keystone token
mechanism defines a mechanism
how to solve the
customer’s problem.” -Mark Cook
From: Steve Baker sba...@redhat.com
To: openstack-dev@lists.openstack.org
Date: 04/03/2014 10:13 PM
Subject:Re: [openstack-dev] [heat] Problems with software config
and Heat standalone configurations
On 04/04/14 14:26, Michael
and KeystoneV2
On 04/04/14 14:05, Michael Elder wrote:
Hello,
I'm looking for insights about the interaction between keystone and the
software configuration work that's gone into Icehouse in the last month or
so.
I've found that when using software configuration, the KeystoneV2 is
broken because
Hello,
I'm looking for insights about the interaction between keystone and the
software configuration work that's gone into Icehouse in the last month or
so.
I've found that when using software configuration, the KeystoneV2 is
broken because the server.py#_create_transport_credentials()
Hello,
While adopting the latest from the software configurations in Icehouse, we
discovered an issue with the new software configuration type and its
assumptions about using the heat client to perform behavior.
The change was introduced in:
commit 21f60b155e4b65396ebf77e05a0ef300e7c3c1cf
