Got it working using:
node /^synd.*\.path2\.some\.domain$/ {
include ibapps
include db
}
On Jul 4, 4:32 pm, cmvelo wrote:
> I am trying to match groups of nodes - i.e.
>
> Node: synd1-path2.path2.some.domain
> Node: synd2-path2.path2.some.domain
>
> By using either of the node definition
I am trying to match groups of nodes - i.e.
Node: synd1-path2.path2.some.domain
Node: synd2-path2.path2.some.domain
By using either of the node definitions below:
node /^synd\w+\.path2\.some\.domain$/ {
include ibapps
include db
}
~~
On 2 July 2010 09:50, David Schmitt wrote:
> On 6/30/2010 10:57 AM, Matt wrote:
>>
>> On 29 June 2010 17:22, Luke Kanies wrote:
>>>
>>> Hi all,
>>>
>>> Given the number of threads on variable scoping recently, it's pretty
>>> clear
>>> we need to change how it works. Markus has a lot of this red
I have since found out that actually using puppet standalone and node
classifier is possible. In our tests, we added the classifier to the
wrong part of the config file which is probably why we didn't get very
far. Good news is this makes everything simpler. Still very happy to
hear your thoughts a
Hi all,
I read today my first book about ruby, and try modify code:
http://github.com/camptocamp/puppet-mysql
Unfortunatly, creator of this code don't replay from my e-mail (may
be, he don't have free time)
I'm stupid about paramters in provider. I add:
__
A little history, I work with a small startup and we are looking at
rolling out a automated cloud based provisioning platform. We have a
dilemma and i wanted to ask your communities thoughts.
As far as I am aware there are 3 ways to run puppet, standalone with
puppet, Client/Server and a hybrid of
