On 01/30/2012 05:30 AM, Jeff McCune wrote:
In the meantime, I document and leave it up to the end user to create
another class that composes modules together. With your example, I'd
do something like this as the end user. As the module author, I'd try
and write mysql and ldap as if the other di
On 02/07/2012 03:54 PM, jimbob palmer wrote:
# The right way
class foo::specific {
include 'foo::common'
# specific stuff
}
So can I be sure that the include will run first, before the "specific
stuff" here?
Kind of, but you need to change your thinking. The include does not
_run_ b
On 16. feb. 2012 00:34, Eric Shamow wrote:
In theory it should be easy to write something through the cloud
provisioning framework that takes even less time and is more flexible
than our tools, but it's a fairly straightforward task.
I've been thinking about doing exactly that but I'm a bit wo
On 02/16/2012 03:30 PM, jcbollinger wrote:
If the File resource behaved as documented then there would be no
uncertainty. With "recurse => true, links => manage, force => true"
the File resource would always manage a node's corresponding directory
tree into an exact match to the master's. W
On 02. mars 2012 14:15, Daysmen wrote:
Hi Folks
To begin with i am looking to deploy a completely new puppet config
based on the truth module
https://github.com/jordansissel/puppet-examples/tree/master/nodeless-puppet/modules/truth
Just a general comment of nodeless Puppet and the truth-enfor
On 15. mars 2012 22:06, Florian Koch wrote:
Hi Dennis,
i have found a better solution via create_resources (look at my reply to
Gery)
Not neccessarily better in my mind because ..
You should try something like this:
class tomcat::instance {
$instances = hiera('tomcat_instances')
puppetwinbuilder.zip .. I haven't done this
myself yet, someone else will most likely help out with more info.
Jan Ivar Beddari
--
http://www.uib.no/personer/Jan.Ivar.Beddari
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this gr
On 03/24/2012 10:58 AM, Fernandez Pablo wrote:
Hi,
That would define $primary_group as a variable, not as a fact. Indeed, what I
want to do is:
:backends: - puppet
:hierarchy: - %{primary_group}
:puppet:
:datasource: data
And that requires primary_group to be a fact.
No, that's not
On 28. mars 2012 05:27, Gino Lisignoli wrote:
I'm rather new to puppet and taking over an existing "work in progress"
installation of puppet.
The problem I have at the moment is that we have a mysql database that
contain some facts about our servers (what their ip address are supposed
to be, who
In a multi-tenant scenario (or easier even, in a scenario where all your
servers have a common root password) where would you place your source
of truth?
Don't know if you see this or care but still fired this off.
best,
Jan Ivar Beddari
Linux/Mac architect University of Bergen, Norway
--
h
On 02. juli 2012 17:26, Darryl Wisneski wrote:
Regards,
-dkw
Ouch, sorry Darryl, I hit the wrong button and posted what I thought of
as a private very quick reply to you .. right on the list.
Now at least everyone sees my honest-to-god thoughts on the matter. And
the scope of the messa
refer. All the pieces and neccessary people
are right there, pull it together!
Jan Ivar Beddari
--
http://www.uib.no/personer/Jan.Ivar.Beddari
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-use
e -a /etc/hosts
and read
http://docs.puppetlabs.com/guides/setting_up.html#configure-dns-optional
best,
Jan Ivar Beddari
--
http://www.uib.no/personer/Jan.Ivar.Beddari
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to thi
All,
this might only be if interest to any Norwegian-speaking list members
but still - organized through DevOps Norway on meetup.com, today I'm
hosting the first of what might become a series of informal Google
Hangouts on Puppet-specific topics:
http://www.meetup.com/DevOps-Norway/events/10
14 matches
Mail list logo
