Open Stack

On 08/10/2015 10:45 AM, Richard Raseley wrote:
> On 08/07/2015 01:58 PM, Rich Megginson wrote:
>> Would someone who actually has to deploy/maintain puppet manifests and
>> supporting code chime in here?  How do you feel about having to ensure
>> that every domain scoped Keystone resource name must end in
>> "::domain"?  At the very least, if not using domains, and not changing
>> the default domain, you would have to ensure "something::Default"
>> _everywhere_ - and I do mean everywhere - every user and tenant name
>> use, including in keystone_user_role, and in other, higher level
>> classes/defines that refer to keystone users and tenants.
>>
>> Anyone?
>>
>> I also wonder how the Ansible folks are handling this, as they move to
>> support domains and other Keystone v3 features in openstack-ansible code?
> As an operator, I like the "::$domain" notation. I think the benefits it
> brings in terms of clarity outweigh any downsides.

If you have to add "::$domain" to all of your manifests and supporting 
code, what impact does that have?

>
>
>
> __________________________________________________________________________
> 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/20150810/9d5d89da/attachment.html>