On 07.12.2009 21:01, Silviu Paragina wrote:
> I forgot to add, I need some resources applied in this case so fail
> won't be enough because it fails before applying any resources.
>
> example: in the case where lsb-release isn't installed on a
> $operatingsystem == "Debian" system I would like to i
I added some text to
http://reductivelabs.com/trac/puppet/wiki/FunctionReference. It explains that
functions get evaluated at compile time, before execution time, and that this
matters if you're using functions whose values depend on the results of your
manifests.
http://reductivelabs.com/trac/pu
On 08.12.2009 11:31, Andrew Schulman wrote:
> I added some text to
> http://reductivelabs.com/trac/puppet/wiki/FunctionReference. It explains that
> functions get evaluated at compile time, before execution time, and that this
> matters if you're using functions whose values depend on the results
> I'd appreciate it if someone would check the accuracy of what I wrote, and if
> it's deemed to be accurate and useful, apply it upstream so that it
> will stay in
> the wiki.
hmm, I'm not sure whether it is now even more misleading than before.
The point with function is that they are evalua
> On 08.12.2009 11:31, Andrew Schulman wrote:
> > I added some text to
> > http://reductivelabs.com/trac/puppet/wiki/FunctionReference. It explains
> > that
> > functions get evaluated at compile time, before execution time, and that
> > this
> > matters if you're using functions whose values de
> > I'd appreciate it if someone would check the accuracy of what I wrote, and
> > if
> > it's deemed to be accurate and useful, apply it upstream so that it
> > will stay in
> > the wiki.
>
> hmm, I'm not sure whether it is now even more misleading than before.
> The point with function is t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrew
I don't know your background but have you considered cloning the git
repo and directly editing the reference source and submitting
patches? That way it's straight upstream and you get credit for the
update.
You can find some instructions at:
> I don't know your background but have you considered cloning the git
> repo and directly editing the reference source and submitting
> patches? That way it's straight upstream and you get credit for the
> update.
>
> You can find some instructions at:
>
> http://reductivelabs.com/trac/puppet/w
On 08.12.2009 12:17, David Schmitt wrote:
> On 07.12.2009 21:01, Silviu Paragina wrote:
>
>> I forgot to add, I need some resources applied in this case so fail
>> won't be enough because it fails before applying any resources.
>>
>> example: in the case where lsb-release isn't installed on a
>
Russ Allbery wrote:
> Joe McDonagh writes:
>
>
>> It would be nice if we could preseed the puppet installation package
>> with some values. This way during boot up, preseeding debian-installer,
>> I could also preseed the puppet package to start in a certain
>> environment. Beyond that you coul
Ohad Levy wrote:
> Or Foreman - it generates a preseed file and also everything you need
> to start puppet (e.g. Your env and friends).
>
> Ohad
>
> On 12/8/09, Russ Allbery wrote:
>
>> Joe McDonagh writes:
>>
>>
>>> It would be nice if we could preseed the puppet installation package
>>>
On Dec 7, 4:13 pm, jokeeffe wrote:
> It probably doesn't need to be virtual but I thought I read in the
> documentation that it was better to do so.
The best practices documentation has at times recommended declaring
users virtually. I don't know whether it still does now, but even
when it di
On Dec 7, 11:19 am, jokeeffe wrote:
> How do I make sure a module is loaded before puppet requests a
> specific resource type. For example,
[...]
> This fails with "err: Could not create my-test-cron: Could not find a
> default provider for cron" because the cron module doesn't get called
> be
I've uploaded version 0.1 of ssh::auth to
http://reductivelabs.com/trac/puppet/wiki/Recipes/ModuleSSHAuth .
ssh::auth is a Puppet module that provides centralized creation,
distribution, and revocation of ssh keys for users. Features:
* Each user may have one or more ssh key pairs, centrally cre
Thank you Silviu,
Very simple and straight forward. I followed a previous thread that
discussed the sources.list.d directory, but didn't quite connect the
dots. With your advise, I looked at a few of my systems and found that
Google parks the repo for their Chrome browser there. That example
shoul
On 08.12.2009 19:37, Ron wrote:
> Thank you Silviu,
>
> Very simple and straight forward. I followed a previous thread that
> discussed the sources.list.d directory, but didn't quite connect the
> dots. With your advise, I looked at a few of my systems and found that
> Google parks the repo for
Joe McDonagh writes:
> A preseed file for debian-installer? I don't need it. I am saying,
> adding support for preseeded values to the puppet package itself. I
> talked to Nigel and I got the idea that it doesn't currently support
> preseeding any values, so he suggested emailing the community
On Mon, Dec 7, 2009 at 2:27 AM, Peter Meier wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> > The base of the code is something like:
> >
> > require "puppet"
> > require "yaml"
> > require "find"
> > Puppet[:config] = "/etc/puppet/puppet.conf"
> > Puppet.parse_config
> > Puppet[:nam
Greetings Puppeteers,
Reductive Labs and the Puppet Dashboard team (that would be me) are
proud to announce the immediate release of Puppet Dashboard 0.0.1,
codenamed "Enterra". Because the Enterra is a car. And cars have
dashboards. Puppet Dashboard is (or will be) a web front end that keeps you
Not yetwe're hoping to firm that up next week. We'll post in the
Newsgroup and send to our Newsletter list when the dates have been
locked down.
On Dec 7, 11:37 pm, "Michael T. Halligan"
wrote:
> Does anyone have the details for the Feb training in SF yet? I want to send
> one of my crew to
Hi,
We're using thin stored configs heavily to manage things like Munin
and Nagios and we're currently wondering what to do when nodes go
away, or change considerably.
If we get rid of a server then all it's stored config is still present
in the database, as well as it's nagios and munin configur
This is similar to what I'm talking about. It looks like this resource is
specifically using modified time as the "checksum." Is this something you've
configured or is this a default of those directories as something internal to
puppet.
- "Tony G." wrote:
> I've see this very often but
On Tue, Dec 8, 2009 at 11:14 AM, Rein Henrichs wrote:
> Greetings Puppeteers,
>
> Reductive Labs and the Puppet Dashboard team (that would be me) are
> proud to announce the immediate release of Puppet Dashboard 0.0.1,
> codenamed "Enterra". Because the Enterra is a car. And cars have
> dashboards
> I meant implementing a new type like aptrepo there. Actually the best
> design decision would be: rename yumrepo as packagerepo, split some of
> the code as a provider yumrepo, add new code for a provider aptrepo. But
> that isn't easy as pie and it requires ruby knowledge, apt and puppet
> inter
On 08.12.2009 21:14, Rein Henrichs wrote:
> Greetings Puppeteers,
>
> Reductive Labs and the Puppet Dashboard team (that would be me) are
> proud to announce the immediate release of Puppet Dashboard 0.0.1,
> codenamed "Enterra". Because the Enterra is a car. And cars have
> dashboards. Puppet Dash
My vote then
_Client:_
server
environment
certname
maybe include the client/server certificates (not so sure since they are
kind of big)
The certificate would be useful to allow secure <> auto-signing
for puppet with the help of some custom functions.
Ie it allows initial connect, on this run y
The log you posted looks like a bad date/time timezone conversion, are
all the clients/puppetmasters on the same timezone?
Notice that the dates are actually identical but one is in utc the other
US eastern (I think).
Silviu
On 08.12.2009 22:43, Digant C Kasundra wrote:
> This is similar to wh
On Tue, Dec 8, 2009 at 12:54 PM, Nigel Kersten wrote:
> First thoughts are that I really quite like it, it's zippy and clean.
Thanks! That's one of the design goals for the UI. Namely, to get out
of the way and let you see the information that's important to you.
> Are you planning to expose st
Hi all,
We just hired a new developer, Jesse Wolfe:
For most of the last decade, Jesse has been writing web applications
and sysadmining web servers, usually at the same time. He sees
programming languages as a form of user interface, and thinks the Ruby
language is the best way to talk to
Joe McDonagh writes:
> Because FAI is deprecated.
By whom?
> You can preseed nearly all necessart values via the debian-installer,
> and LVM can be done in the late-command.
I think you'd be way better off using FAI. It really makes handling
things like this much easier rather than relying on
Hi,
They are supposed to have GMT:
puppetmaster:
$ date
Wed Dec 9 00:59:02 *GMT* 2009
puppetclient:
$ date
Wed Dec 9 00:58:59 *GMT* 2009
But digging more I found this:
puppetmaster:
$ cat /etc/sysconfig/clock
*ZONE="GMT"*
*UTC=false*
ARC=false
puppetclient:
$ cat /etc/sysconfig/clock
*ZONE="US
Tony G. writes:
> They are supposed to have GMT:
In these modern times UTC is generally a better universal standard than
GMT.
> But the timezone file in */etc/localtime* is the same on them:
> md5sum /usr/share/zoneinfo/* 2>/dev/null|grep $(md5sum /etc/localtime|cut
> -d" " -f1)
> fcccbcf95
Try this
ruby -e 'puts Time.at(0)'
In case ruby treats timezones different from how it should (how I think
it should actually)
Silviu
On 09.12.2009 03:21, Tony G. wrote:
> Hi,
>
> They are supposed to have GMT:
> puppetmaster:
> $ date
> Wed Dec 9 00:59:02 *GMT* 2009
> puppetclient:
> $ date
>
if you want utc, you should use:
ruby -e 'puts Time.at(0).utc'
cheers,
Ohad
On Wed, Dec 9, 2009 at 9:51 AM, Silviu Paragina wrote:
> Try this
> ruby -e 'puts Time.at(0)'
> In case ruby treats timezones different from how it should (how I think it
> should actually)
>
>
> Silviu
>
>
> On 09.1
The output should give a clue if the timezone is wrong for ruby on the
client/server machine. If I use utc it will discard that info so it is:
ruby -e 'puts Time.at(0)'
and if all things are sane it should output
Thu Jan 01 00:00:00 +000 1970 (without +something or -something)
Not sure how much it
The output is the same on both:
puppetmaster:
$ ruby -e 'puts Time.at(0)'
Thu Jan 01 00:00:00 + 1970
puppetclient:
ruby -e 'puts Time.at(0)'
Thu Jan 01 00:00:00 + 1970
Then sometime else might be causing the checksum output.
Thanks for the other suggestions and explanations.
On Tue, De
On 08.12.2009 15:00, Silviu Paragina wrote:
> On 08.12.2009 12:17, David Schmitt wrote:
>> On 07.12.2009 21:01, Silviu Paragina wrote:
>>
>>> I forgot to add, I need some resources applied in this case so fail
>>> won't be enough because it fails before applying any resources.
>>>
>>> example: in t
On 08.12.2009 17:53, Rus Hughes wrote:
> Hi,
>
> We're using thin stored configs heavily to manage things like Munin
> and Nagios and we're currently wondering what to do when nodes go
> away, or change considerably.
>
> If we get rid of a server then all it's stored config is still present
> in th
38 matches
Mail list logo
