On Sun, Jan 23, 2011 at 23:36, Stig Sandbeck Mathisen wrote:
> Jesse Reynolds writes:
>
>> --manual
>
> Looks better than --interactive, since I don't assume it will start
> asking me questions. :)
I like it too.
Daniel
--
⎋ Puppet Labs Developer – http://puppetlabs.com
✉ Daniel Pittman
Nigel Kersten a écrit :
On Sun, Jan 23, 2011 at 4:53 PM, James Louis wrote:
exactly. to what purpose?
To trigger an immediate run on a client with the common options used
when testing a real run, not a noop run.
If there was a clear word that described this functionality, we
probably
On Mon, Jan 24, 2011 at 3:23 AM, eshamow wrote:
> The Fedora 13 SRPMs backport pretty easily, and you get the advantage
> of Ruby 1.8.6.
>
> -Eric
>
Sure, but for those who don't want to replace/break the internals of ruby on
rhel4... :)
>
> On Jan 22, 11:32 am, Ohad Levy wrote:
> > On Sat, Ja
+1
El 24/01/2011 9:13, Daniel Pittman escribió:
On Sun, Jan 23, 2011 at 23:36, Stig Sandbeck Mathisen wrote:
Jesse Reynolds writes:
--manual
Looks better than --interactive, since I don't assume it will start
asking me questions. :)
I like it too.
Daniel
--
Carles Amigó
Linux
What would be a better name for "--test"?
Using Gentoo's emerge as an example, how about --oneshot?
It's more than that though.
--onetime
--no-daemonize
--ignorecache
--verbose
--no-usecacheonfailure
and I think I'm missing some newer additions too.
Hmm that's true, and it is similar to --
On 24/01/11 11:00, Adam Nielsen wrote:
What would be a better name for "--test"?
Using Gentoo's emerge as an example, how about --oneshot?
It's more than that though.
--onetime
--no-daemonize
--ignorecache
--verbose
--no-usecacheonfailure
and I think I'm missing some newer additions too.
It's more than that though.
--onetime
--no-daemonize
--ignorecache
--verbose
--no-usecacheonfailure
and I think I'm missing some newer additions too.
Hmm that's true, and it is similar to --onetime. How about --explain?
The end result is that you get a detailed explanation of what is happening
On Jan 24, 2011, at 12:00, Adam Nielsen wrote:
What would be a better name for "--test"?
>>>
>>> Using Gentoo's emerge as an example, how about --oneshot?
>>
>> It's more than that though.
>>
>> --onetime
>> --no-daemonize
>> --ignorecache
>> --verbose
>> --no-usecacheonfailure
>>
>> and
Hi Nan,
thanks. I have removed the schedule (re)definition but it does still the same -
the tidy is called on every run (every 30 minutes). the state.yaml after a
typical run has following records:
* puppet log:
Jan 24 10:37:32 puppet puppet-agent[24504]:
(/Stage[main]/Puppet::Master/Tidy[/va
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Can you try it with a different type, say a sample 'notify' statement?
Tidy appears to have some magic going on at times. I just noticed that
it *appears* to be run before anything else, even in the pre-stage but
that could be a fluke in my setup.
Tr
On 01/24/2011 11:38 AM, Carles Amigó wrote:
> +1
>
> El 24/01/2011 9:13, Daniel Pittman escribió:
>> On Sun, Jan 23, 2011 at 23:36, Stig Sandbeck Mathisen
>> wrote:
>>> Jesse Reynolds writes:
>>>
--manual
Seconded (or, fourthed?)
Also, I'll outright *refuse* to install a software that
Hi all,
Is there a way to use the Package type to find the version number of an
installed RPM?
I've consulted this page [1] and I can't see any documentation there
that says this might be possible.
I want to simply query my package manager and ask which version of a
package is installed. I
On 01/24/2011 02:07 PM, Jonathan Gazeley wrote:
> Hi all,
>
> Is there a way to use the Package type to find the version number of an
> installed RPM?
>
> I've consulted this page [1] and I can't see any documentation there
> that says this might be possible.
>
> I want to simply query my packag
On 24/01/11 13:31, Felix Frank wrote:
On 01/24/2011 02:07 PM, Jonathan Gazeley wrote:
Hi all,
Is there a way to use the Package type to find the version number of an
installed RPM?
I've consulted this page [1] and I can't see any documentation there
that says this might be possible.
I want to
am just curious as to why do you think that would be possible? Did you
use some other "puppet type" to similarly obtain information? like get
the size of a file, using File type?
Thanks,
Mohamed.
On Mon, Jan 24, 2011 at 9:15 AM, Jonathan Gazeley
wrote:
> On 24/01/11 13:31, Felix Frank wrote:
>>
Just to clarify, I do not know the answer to your question... it's
just that I would not have had that question at all, so am wondering
why :)
On Mon, Jan 24, 2011 at 9:21 AM, Mohamed Lrhazi wrote:
> am just curious as to why do you think that would be possible? Did you
> use some other "puppet t
On this page [1] it says that using Package with yum as a backend is
"versionable", i.e. "The provider is capable of interrogating the
package database for installed version(s), and can select which out of a
set of available versions of a package to install if asked."
The data (the version num
- Original Message -
> On this page [1] it says that using Package with yum as a backend is
> "versionable", i.e. "The provider is capable of interrogating the
> package database for installed version(s), and can select which out of
> a
> set of available versions of a package to install
Russel, I'm glad it's working for you now. I just want to clear up a
typo in my previous comments, lest it confuse someone else later:
On Jan 21, 9:36 am, jcbollinger wrote:
[...]
> 3) Puppet automatically generates dependencies between File["/parent/
> foo"] and File["/parent"] (the former requ
Hi,
> All that being said, if its just one or two packages you care about you can
> simply add a fact for the package versions, but this fact will only show the
> version on the next puppet run not the one during which you install said
> package
> since the compile stage of the puppet run is hap
Hi, I have a the annoying problem that the puppet master cannot connect
to itself. It fails with:
puppet# puppetd --test
err: Could not retrieve catalog from remote server: SSL_connect returned=1
errno=0 state=SSLv3 read finished A: tlsv1 alert decrypt error
History:
I have had this problem on
How about --apply
On Jan 23, 9:33 pm, Nigel Kersten wrote:
> https://projects.puppetlabs.com/issues/2476
>
> This does seem to confuse a fair few new users.
>
> What would be a better name for "--test"?
--
You received this message because you are subscribed to the Google Groups
"Puppet Users"
On 01/24/2011 11:48 AM, chris.does.t...@googlemail.com wrote:
> How about --apply
Please don't. That's begging for confusion of "puppet apply" vs. "puppet
agent --apply".
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, se
good hint - it does work for notify - eg:
notify { "test": message => "TEST TEST TEST", schedule => daily }
tidy { "/var/lib/puppet/reports":
age => "1w",
recurse => true,
matches => "*.yaml",
schedule => daily
}
the notify is executed only once but tidy still during each run.
On Mon, Jan 24, 2011 at 12:27 AM, DEGREMONT Aurelien
wrote:
> Please take care that, for my site, and I think other ones,
>
> puppetd -t
>
> is *the* way to run puppet.
> We never use puppetd in daemonized mode, and manual runs puppet when needed
> with -t option.
You shouldn't be doing this. If
No, that works a treat. Thanks a lot
(to all who answered).
On Sat, Jan 22, 2011 at 1:00 PM, donavan wrote:
> On Jan 21, 11:13 am, Dick Davies wrote:
>> ensurable do
>> defaultto 'present'
>> end
>
> I've always specified the methods:
> ensurable do
> newvalue(:present) do
>
We're utilizing the Dashboard to manage which modules are included for
each node. In this setup, nodes.pp is empty.
E.g.:
modules/repos includes the various repository files for each OS.
...And in the dashboard, there is a class titled 'repos' and is
assigned to the various nodes that we want t
On Jan 24, 4:51 pm, sbb wrote:
> class { "repos": stage => pre; }
I don't think Dashboard has native support for run levels of classes,
so you might have to do something like:
class repos_pre {
class { "repos": stage => pre; }
}
and then assign repos_pre to your nodes in Dashboard.
--
You
Dear list,
I'm attempting to mirror a folder containing a few large files from an
NFS location to the local drive. Subsequent runs take a lot longer than
I'd have expected, after the first run.
Using the following block a puppet apply run is currently taking 30 seconds:
file { '/usr/share/target'
Hi Robert,
Yes, you shouldn't need to delete $ssldir on the Master. I'll reply to
you fully tomorrow (or someone on American time can this evening). The
error itself is strange (TLS handshake?) but describing what you've
done I'd think you'd have a certificate / hostname mismatch problem.
Have a
On Jan 24, 5:07 am, Jonathan Gazeley
wrote:
> Hi all,
>
> Is there a way to use the Package type to find the version number of an
> installed RPM?
Have you seen 'ralsh', or 'puppet resource'[1]? You can use these
interactively to interrogate the state of a system, 'puppet resource
package foo'.
On Mon, Jan 24, 2011 at 01:19:35PM +0100, Felix Frank wrote:
> On 01/24/2011 11:38 AM, Carles Amigó wrote:
> > +1
> >
> > El 24/01/2011 9:13, Daniel Pittman escribió:
> >> On Sun, Jan 23, 2011 at 23:36, Stig Sandbeck Mathisen
> >> wrote:
> >>> Jesse Reynolds writes:
> >>>
> --manual
>
>
If we don't want --manual you could go with --watch as that's really what
I'm doing - watching puppet run. :)
On Mon, Jan 24, 2011 at 1:24 PM, Stefan Schulte <
stefan.schu...@taunusstein.net> wrote:
> On Mon, Jan 24, 2011 at 01:19:35PM +0100, Felix Frank wrote:
> > On 01/24/2011 11:38 AM, Carles
- Original Message -
> If we don't want --manual you could go with --watch as that's really
> what I'm doing - watching puppet run. :)
I like --watch too
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send ema
Hello,
I'm trying to realize resources on a node but it looks like they never
get realized.
Here is an example
node /mynode/ inherits default {
$logging_retention = 365
$puppet_lab = true
# Including modules
#
include defaults
include itms
Cron <| tag == "default_cron" |>
}
Th
I have encountered what might be a bug in the package resource type. I'm
using puppet 0.25.5 so perhaps it has been fixed in a later version.
The problem involves installing a package from two different providers
(e.g.: apt and get) with the same name in the provider's environment. For
example, su
I'm sorry...
I was using the wrong "tag" name... duh! I changed it to the correct
one and it worked great.
Thx.
On Jan 24, 11:49 am, Roberto Bouza wrote:
> Hello,
>
> I'm trying to realize resources on a node but it looks like they never
> get realized.
>
> Here is an example
>
> node /mynode/
On Mon, Jan 24, 2011 at 11:57 AM, Barry Jaspan wrote:
> I have encountered what might be a bug in the package resource type. I'm
> using puppet 0.25.5 so perhaps it has been fixed in a later version.
>
> The problem involves installing a package from two different providers
> (e.g.: apt and get) w
On Jan 24, 2011, at 2:38 AM, Carles Amigó wrote:
> +1
>
> El 24/01/2011 9:13, Daniel Pittman escribió:
>> On Sun, Jan 23, 2011 at 23:36, Stig Sandbeck Mathisen wrote:
>>> Jesse Reynolds writes:
>>>
--manual
>>>
>>> Looks better than --interactive, since I don't assume it will start
>>>
On Jan 24, 2011, at 3:00 AM, Adam Nielsen wrote:
What would be a better name for "--test"?
>>>
>>> Using Gentoo's emerge as an example, how about --oneshot?
>>
>> It's more than that though.
>>
>> --onetime
>> --no-daemonize
>> --ignorecache
>> --verbose
>> --no-usecacheonfailure
>>
>> a
On Jan 24, 2011, at 3:01 AM, Jonathan Gazeley wrote:
> On 24/01/11 11:00, Adam Nielsen wrote:
> What would be a better name for "--test"?
Using Gentoo's emerge as an example, how about --oneshot?
>>>
>>> It's more than that though.
>>>
>>> --onetime
>>> --no-daemonize
>>> --ignor
On Jan 24, 2011, at 3:22 AM, Thorsten Biel wrote:
>
> On Jan 24, 2011, at 12:00, Adam Nielsen wrote:
>
> What would be a better name for "--test"?
Using Gentoo's emerge as an example, how about --oneshot?
>>>
>>> It's more than that though.
>>>
>>> --onetime
>>> --no-daemonize
On Jan 24, 2011, at 11:17 AM, R.I.Pienaar wrote:
> - Original Message -
>> If we don't want --manual you could go with --watch as that's really
>> what I'm doing - watching puppet run. :)
>
>
> I like --watch too
I hope this is a joke. I really think this name is a worse fit than "--t
- Original Message -
> On Jan 24, 2011, at 11:17 AM, R.I.Pienaar wrote:
>
> > - Original Message -
> >> If we don't want --manual you could go with --watch as that's
> >> really
> >> what I'm doing - watching puppet run. :)
> >
> >
> > I like --watch too
>
> I hope this is a jok
On Jan 24, 2011, at 9:14 AM, Daniel Piddock wrote:
> Dear list,
>
> I'm attempting to mirror a folder containing a few large files from an
> NFS location to the local drive. Subsequent runs take a lot longer than
> I'd have expected, after the first run.
>
> Using the following block a puppet a
On Jan 24, 2011, at 12:39 PM, R.I.Pienaar wrote:
> - Original Message -
>> On Jan 24, 2011, at 11:17 AM, R.I.Pienaar wrote:
>>
>>> - Original Message -
If we don't want --manual you could go with --watch as that's
really
what I'm doing - watching puppet run. :)
>>>
Thanks for the reply.
That is perhaps an interim solution, albeit not elegant and not within
the motivations and spirit of the puppet goals.
How about a feature request to manage class/module parameters like
this directly in the Dashboard within the Class configuration? Or in
the module definiti
Well, I see where you're coming from, but I see all flags as commands given
to the program meaning you're telling puppet to do that thing. So,
"--no-daemonize" tells puppet not to daemonize. In this case, I'd expect
"watch" to tell puppet to watch something. I really think this is a bad
choice
The problem seems to be --test does so many things you can't concisely
describe it.
On the other hand, maybe --live-test would be good, as it makes it clear
changes will be made which seems to be the biggest complaint about --test.
Cheers,
Adam.
--
You received this message because you are s
On Sun, Jan 23, 2011 at 1:59 PM, Daniel Pittman wrote:
> I would love to know what the details of your configuration are, including
> web server version (Apache, Passenger, etc), and what timeouts you have
> configured at that level.
Let's see here...
ii puppet
On Mon, Jan 24, 2011 at 1:13 PM, sbb wrote:
> Thanks for the reply.
>
> That is perhaps an interim solution, albeit not elegant and not within
> the motivations and spirit of the puppet goals.
>
> How about a feature request to manage class/module parameters like
> this directly in the Dashboard w
On Jan 24, 2011, at 1:17 PM, Adam Nielsen wrote:
>> The problem seems to be --test does so many things you can't concisely
>> describe it.
>
> On the other hand, maybe --live-test would be good, as it makes it clear
> changes will be made which seems to be the biggest complaint about --test.
I
On Mon, Jan 24, 2011 at 13:20, Jason Wright wrote:
> On Sun, Jan 23, 2011 at 1:59 PM, Daniel Pittman wrote:
>> I would love to know what the details of your configuration are, including
>> web server version (Apache, Passenger, etc), and what timeouts you have
>> configured at that level.
[...]
On Mon, Jan 24, 2011 at 2:30 PM, Daniel Pittman wrote:
> Thanks for sharing those details. As I expected, none of that looks
> like it should have any relationship with the failure, and helps me
> eliminate some "is it slow I/O" from my early mental space to explore
> to understand the problem.
On Mon, Jan 24, 2011 at 14:39, Jason Wright wrote:
> On Mon, Jan 24, 2011 at 2:30 PM, Daniel Pittman wrote:
[...]
>> By hilariously, how terrible is it? "Fails in nasty but obvious ways"
>> would be OK; "sets fire to your cat" would be pretty undesirable, and
>> would encourage me to think abo
On Mon, Jan 24, 2011 at 2:42 PM, Daniel Pittman wrote:
> That qualifies into the first class of problems. I don't like it, but
> it isn't miscompiling the catalog and sending something entirely
> broken to the client without warning, so that isn't so dire as it
> could be.
Puppet is doing the rig
Hi,
As far as I understand it we need to modify puppet/share/puppet-
dashboard/config/environment.rb in order to adjust the time zone of
the Puppet Dashboard. I've changed the UTC variable to "Sydney" and
the reports are now displaying the right time.
Unfortunately the "Run Time" chart is complet
I'm the first to admit that I'm an idiot.
I want to get puppet 2.6.4 on Ubuntu 10.10. As far as I can tell, I
need to compile puppet. I've downloaded the 2.6.4 code, but don't know
where to go from there. Any advice or pointers to existing
documentation on this would be greatly appreciated.
Tha
You don't have to compile puppet since ruby is an interpreted language
and puppet is written in ruby.
To install puppet and get familiar with it this looks like a good
starting point: http://docs.puppetlabs.com
To install puppet you can just untar the sources, cd in the new
directory and run
I'm just starting out with Puppet (version 2.6.4 installed), trying to
figure out how to migrate an old Cfengine 2 implementation. The
packages we build and install internally are made using pkgsrc, for
which we have no repository. The way we presently install packages in
cfengine 2 is as follows:
On Mon, Jan 24, 2011 at 5:40 PM, Erik wrote:
> I'm just starting out with Puppet (version 2.6.4 installed), trying to
> figure out how to migrate an old Cfengine 2 implementation. The
> packages we build and install internally are made using pkgsrc, for
> which we have no repository. The way we pr
On Mon, Jan 24, 2011 at 14:30, Daniel Pittman wrote:
> On Mon, Jan 24, 2011 at 13:20, Jason Wright wrote:
>> On Sun, Jan 23, 2011 at 1:59 PM, Daniel Pittman
>> wrote:
>
>>> I would love to know what the details of your configuration are, including
>>> web server version (Apache, Passenger, etc)
From: puppet-users@googlegroups.com
[mailto:puppet-users@googlegroups.com] On Behalf Of
puppet-users+nore...@googlegroups.com
Sent: Monday, January 24, 2011 1:00 PM
To: Abridged Recipients
Subject: [Puppet Users] Abridged summary
63 matches
Mail list logo
