On Fri, Dec 3, 2010 at 12:48 PM, Don Jackson <
puppet-us...@clark-communications.com> wrote:
>
> So here is a scenario:
>
> I have a directory:
>
>./foo
>./foo/file1
>./foo/file2
>./foo/file3
>…
>./foo/fileN
>
> I populate this directory on a configu
Was going to open a new ticket but saw this --
http://projects.puppetlabs.com/issues/5414
The user reports the issue in 2.6.3, i see it in 2.6.4 as well, on
CentOS 5.5. If I modify a file in a folder that is being deployed
recursively, that update is not happening on the clients.
This has led us
Puppet won't bother other files in a directory it manages unless you turn on
"purge => true".
On Fri, Dec 3, 2010 at 2:15 PM, Don Jackson <
puppet-us...@clark-communications.com> wrote:
>
> On Dec 3, 2010, at 12:56 PM, Patrick wrote:
>
> Why not sync the files directly to that directory?
>
>
> Th
On Dec 1, 2:15 am, walexey wrote:
> Hello everybody!
>
> I use puppet storeconfig for configuring server side of bacula.
> But when i remove one of client node, its information keeps in
> storeconfig db.
> How can i expire it?
>
> wbr, alw
In the meantime theres a contrib script which will purge
Yeah that's useful for the client side but I'm really looking for the
picture of the full catalog.
The original poster I think put it best:
"I'm looking for something that shows the
relationship of classes and defines rather than the resources that
result from their use."
On 12/3/2010 3:28 PM
The catalog that is shipped to the client is immediately applied
without reevaluating the state of the client (that evaluation is done
during catalog compilation on the master with the provided facts).
I think what you're looking for is for puppet to download a catalog,
revise the resources that s
I have a similar problem. When trying to have puppet setup a hadoop
namenode it may need to format the hdfs if this is a first time
install. This requires giving the hadoop namenode -format command a
"Y" for each disk being formatted. Ideally in addition to feeding the
right prompt response we'd al
Have you seen the --graph option that generates .dot files of your
generated catalogs? It's not global to all of your manifests, but it's
a start.
http://docs.puppetlabs.com/guides/faq.html#how-do-i-use-puppets-graphing-support
-Hunter
On Fri, Dec 3, 2010 at 14:50, psyber wrote:
> bump?
>
> O
bump?
On 5/22/2010 9:03 AM, Trevor Vaughan wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Well, it turns out that 0.25 completely broke my code (no big surprise).
I was using the 'classes' method off of the parser, but I'll have to
re-write it all now since the parser appears to have bee
Hi Martijn,
Looking here and at source:
http://docs.puppetlabs.com/references/stable/type.html#schedule
It reads to me that you might be able to use:
schedule { puppet: period => weekly, repeat => 3 }
And have it ran three days a week for example, but being specific
about the day does not seem
On Dec 3, 2010, at 12:56 PM, Patrick wrote:
> Why not sync the files directly to that directory?
There are other files in the parent directory that are not managed by puppet.
And the names of the files are dynamic enough that it would be painful to
explicity manage each file in the puppet mani
On Fri, Dec 3, 2010 at 11:58 AM, Derek Yarnell wrote:
> So we run puppetd as a long running ruby process on the hosts. When we
> update a fact that gets auto sync'd to the host it seems when puppetd wakes
> up and starts its catalog run it doesn't re-sync the facts. It you run it
> standalone
On Fri, Dec 3, 2010 at 9:04 AM, Lars Francke wrote:
> Hi!
>
> Again thank you for the detailed answer.
>
>> One of the things that sometimes gives Puppet newbies trouble is that
>> it employs a declarative model rather than an imperative one. In
>> other words, it's an expert system, not a script
Why not sync the files directly to that directory?
On Dec 3, 2010, at 12:48 PM, Don Jackson wrote:
>
> So here is a scenario:
>
> I have a directory:
>
> ./foo
> ./foo/file1
> ./foo/file2
> ./foo/file3
> …
> ./foo/fileN
>
> I populate this directory on a co
On Dec 2, 2010, at 1:03 PM, Sid wrote:
> ruby: 1.8.7.302-4
> ruby-augeas: 0.3.0-1.el5 (EPEL)
> augeas-libs: 0.7.3-1.el5 (EPEL)
> puppet: 2.6.4
>
> I am unable to get Puppet/Augeas to update the sysctl.conf file when
> using the following configuration. I have tested changing the file
> with augt
So here is a scenario:
I have a directory:
./foo
./foo/file1
./foo/file2
./foo/file3
…
./foo/fileN
I populate this directory on a configured machine via a recursive file resource.
What I would like to do is create a symlink from the parent direct
So we run puppetd as a long running ruby process on the hosts. When we update
a fact that gets auto sync'd to the host it seems when puppetd wakes up and
starts its catalog run it doesn't re-sync the facts. It you run it standalone
it will or if you restart the service then it will do the righ
On Fri, Dec 3, 2010 at 8:28 AM, tecneeq wrote:
>
>
> On 1 Dez., 18:28, Nigel Kersten wrote:
>
>> Make a fact that reports whether or not the directory exists, and make
>> the include of the class conditional on the fact value.
>
> Thanks, i did just that and it works.
>
> However, during testing
Hi!
Again thank you for the detailed answer.
> One of the things that sometimes gives Puppet newbies trouble is that
> it employs a declarative model rather than an imperative one. In
> other words, it's an expert system, not a scripting language. The
> Puppet language is all about describing t
On 1 Dez., 18:28, Nigel Kersten wrote:
> Make a fact that reports whether or not the directory exists, and make
> the include of the class conditional on the fact value.
Thanks, i did just that and it works.
However, during testing it turned out that myfacts.rb isn't sent to
the remote puppet
On Fri, 3 Dec 2010 07:59:55 -0800
Nigel Kersten wrote:
[...]
> I think we're saying exactly the same thing, so either that, or I fail
> at reading comprehension :)
we're saying the same thing.
your comprehension is fine, my English not :-)
> > cheers,
> > Arnau
--
You received this message bec
On Fri, Dec 3, 2010 at 7:38 AM, Arnau Bria wrote:
> On Fri, 3 Dec 2010 07:21:33 -0800
> Nigel Kersten wrote:
>
>> On Fri, Dec 3, 2010 at 7:15 AM, Arnau Bria wrote:
>> > On Fri, 3 Dec 2010 12:55:38 +0100
>> > Arnau Bria wrote:
>> >
>> >> Hi all,
>> >> modulepath=/etc/puppet/manifests/modules:/etc/
On Fri, 3 Dec 2010 07:21:33 -0800
Nigel Kersten wrote:
> On Fri, Dec 3, 2010 at 7:15 AM, Arnau Bria wrote:
> > On Fri, 3 Dec 2010 12:55:38 +0100
> > Arnau Bria wrote:
> >
> >> Hi all,
> >> modulepath=/etc/puppet/manifests/modules:/etc/puppet/manifests/modules/common:/etc/puppet/manifests/services
On Fri, Dec 3, 2010 at 7:15 AM, Arnau Bria wrote:
> On Fri, 3 Dec 2010 12:55:38 +0100
> Arnau Bria wrote:
>
>> Hi all,
>> modulepath=/etc/puppet/manifests/modules:/etc/puppet/manifests/modules/common:/etc/puppet/manifests/services/workernode/modules/
> ^^
On Fri, 3 Dec 2010 12:55:38 +0100
Arnau Bria wrote:
> Hi all,
> modulepath=/etc/puppet/manifests/modules:/etc/puppet/manifests/modules/common:/etc/puppet/manifests/services/workernode/modules/
^
this is wrong. /modules/c
On Dec 2, 2:56 pm, Kikanny wrote:
> I'm trying to run puppet using the tarball and so far, I've been
> unsuccessful. The system I'm trying to run puppet on is running RHEL
> 5.3. Now first of all, this system does not have access to internet.
> Therefore I don't have any access to any of the rep
On Dec 2, 10:13 pm, Paul Johnson wrote:
> file { "/tmp/bar": audit => content } exec { '/usr/bin/true':
> refreshonly => true, subscribe => File['/tmp/bar'] }
>
> and it produces this error every time:
>
> err: /Stage[main]//Node[localhost]/File[/tmp/bar]: Could not evaluate:
> Could not retriev
On Fri, Dec 3, 2010 at 3:55 AM, Daniel Pittman wrote:
> Héctor Rivas Gándara writes:
>
>> I have been searching in the puppet documentation for the these
>> functionalities (see below for examples):
>>
>> - Access to resource attributes or parameters to use in the recipes.
>> I say attributtes b
Hi all,
I'm reading
http://docs.puppetlabs.com/guides/modules.html#module-lookup and trying
to understand how puppet autoload modules. It says:
"From version Puppet 0.23.1 onwards, everything under the modulepath is
automatically imported into Puppet and is available to be used"
so, if our modu
Anyone had any experience getting puppet to update multiple OS's on a
single server?
For example, for a set of blades Network booting from a primary
server, the OS for each blade would be stored on the primary server.
For example:
/pxe/host1/
/pxe/host2/
.
/pxe/hostn/
Can puppet be run in a mo
Hardly controlling my ire ( :-) ) I must confess that the server is
(sadly) an Ubuntu 10.04...
Thanks anyway
Af
On Dec 3, 12:20 am, Avi Miller wrote:
> Al @ Lab42 wrote:
> > Now, please, don't tell me that I should make a php-oci8 package and
> > distribute it, I know that.
>
> At the risk of rai
31 matches
Mail list logo
