Open Stack

Rich Megginson <rmeggins at redhat.com> writes:

>>> This seems to be the hardest part - I still cannot figure out how to
>>> use "compound" names with Puppet.
>> I don't get this point.  what is "2 or more resource could exists" and
>> how it relates to compound names ?
>
> I would like to uniquely specify a resource by the _combination_ of
> the name + the domain.  For example:
>
>   keystone_user { 'domain A admin user':
>     name => 'admin',
>     domain => 'domainA',
>   }
>
>   keystone_user { 'domain B admin user':
>     name => 'admin',
>     domain => 'domainB',
>   }
>
> Puppet doesn't like this - the value of the 'name' property of
> keystone_user is not unique throughout the manifest/catalog, even
> though both users are distinct and unique because they existing in
> different domains (and will have different UUIDs assigned by
> Keystone).
>
> Gilles posted links to discussions about how to use isnamevar and
> title_patterns with Puppet Ruby providers, but I could not get it to
> work.  I was using Puppet 3.8 - perhaps it only works in Puppet 4.0 or
> later.  At any rate, this is an area for someone to do some research

Thanks for the explanation.  I will definitively look into it.

>>>>>       - More difficult to debug
>>> More difficult than it is already? :P
>> require 'pry';binding.pry :)
>
> Tried that on Fedora 22 (actually - debugger pry because pry by itself
> isn't a debugger, but a REPL inspector).  Didn't work.
>
> Also doesn't help you when someone hands you a pile of Puppet logs . . .

Agreed, more useful for creating provider than debugging puppet logs.

-- 
Sofer Athlan-Guyot