Re: [Puppet Users] addition to wiki/FunctionReference
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 of your
manifests.
http://reductivelabs.com/trac/puppet/wiki/FunctionReference?action=diffversion=26old_version=25
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.
Not quite: The functions are actually evaluated on the server. You
example of using file($path) and file { $path: ... } will never work,
since the file() function will read $path on the puppetmaster, while the
File[$path] resource will manage $path on the client.
Regards, DavidS
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] addition to wiki/FunctionReference
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 evaluated at compile time and as compilation happens on the master it will also only see things on the master. So your example is so far only working if you either run puppet as standalone app or you are talking about a file resource which will get applied on the master. Everything else won't work. In general your explanation is correct, but I think maybe it is misleading for some people, as many people don't understand at first why functions are only evaluated on the master. I think it's good to extend the function explanation, there is also some part in the language tutorial: http://reductivelabs.com/trac/puppet/wiki/LanguageTutorial#functions Maybe we should simply put the warning in the FunctionReference as well and redirect for further information to the LanguageTutorial where people can extend the documentation how they would like to extend it. So imho your explanation would fit better there. thanks and cheers pete -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] addition to wiki/FunctionReference
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 of your
manifests.
http://reductivelabs.com/trac/puppet/wiki/FunctionReference?action=diffversion=26old_version=25
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.
Not quite: The functions are actually evaluated on the server. You
example of using file($path) and file { $path: ... } will never work,
since the file() function will read $path on the puppetmaster, while the
File[$path] resource will manage $path on the client.
Well, not never. It works if it's run on the puppetmaster, which is the case I
actually was thinking of and where I first encountered the problem. It's also
the case if you run a puppet script standalone with /usr/bin/puppet.
But you're right of course that the statement needs to be make clear that
functions are evaluated on the puppetmaster. I'll think on that.
Thanks,
Andrew.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] addition to wiki/FunctionReference
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 evaluated at compile time and as compilation happens on the master it will also only see things on the master. So your example is so far only working if you either run puppet as standalone app or you are talking about a file resource which will get applied on the master. Everything else won't work. In general your explanation is correct, but I think maybe it is misleading for some people, as many people don't understand at first why functions are only evaluated on the master. Agreed-- see my answer to David. I've backed it out for now and will rework it. I think it's good to extend the function explanation, there is also some part in the language tutorial: http://reductivelabs.com/trac/puppet/wiki/LanguageTutorial#functions Maybe we should simply put the warning in the FunctionReference as well and redirect for further information to the LanguageTutorial where people can extend the documentation how they would like to extend it. So imho your explanation would fit better there. To me it seems like more specialized material that should go in the reference rather than the tutorial. But wherever it goes best is fine with me. Thanks for your comments. Andrew. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] addition to wiki/FunctionReference
-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: http://reductivelabs.com/trac/puppet/wiki/Development/DevelopmentLifecycle Cheers James Turnbull - -- Author of: * Pro Linux System Administration (http://tinyurl.com/linuxadmin) * Pulling Strings with Puppet (http://tinyurl.com/pupbook) * Pro Nagios 2.0 (http://tinyurl.com/pronagios) * Hardening Linux (http://tinyurl.com/hardeninglinux) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEVAwUBSx49XiFa/lDkFHAyAQKiBAgAov6VP0SNg3DqpF2I2lFQjcyPHc8Z1ITu w1GahuFuK83BhxjpZaCtznJrMAcAYqDRZ58rRjqF7tQ9iXoee2UfZuHFfSvdgPtw kvJCKIehvxrku18nlWNdw9ECgWO4crrFMbmdoMQ8zu5Ww0/NwKtTA/1r0kgjycA0 ER26TDyL1RdIyBLuoOnmQYN6hhIFKicEnJ35Gv/Ihou9cMSKOpRt/LxznGaVuxkE bLbgWLt4uOuwUMkVYtKhuZ5CimSBvm2ZCRKEUWXeDLe2huI+KWJS06E238AChPYk UqS20AVJL7qlkjW25945ZbzwlAsmwYfMuvvtW7srNSwQMA9WQIvUBg== =UWN9 -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] addition to wiki/FunctionReference
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/wiki/Development/DevelopmentLifecycle Thanks. I'm a bzr guy, but I'll see about getting up to speed with git. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Stop(or restart and/or reload facts/providers) execution on some conditions
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 $operatingsystem == Debian system I would like to install lsb-realease and then fail or restart just to be sure I'm not actually on a Ubuntu system Another example would be augeas, where, even if in a run augeas would be installed, puppet would fail because of missing augeas provider. Put all clients which do not have lsb-release and/or augeas installed into a separate bootstrap mode. You can use environments and/or tags to implement this. In this special mode just install the tools you need. The next run will resume with the full information available. Normally this special bootstrap run is already done from the installer to make this very easy, e.g. in debian-installer's postcmd: puppetd --environment bootstrap-debian --onetime --no-daemonize Regards, DavidS Can this be automated, if somebody uninstalls lsb-release by mistake for example? aptitude has a bad habit of doing this... And can it be done from a manifest the standard puppet way? One possible way I can think of this is to run puppet (not puppetd) with an exec, but I'm not sure about the locks puppet uses (if the locks are different from puppetd):-? . Silviu Silviu PS sorry for spamming the list : On 07.12.2009 21:31, Silviu Paragina wrote: Is this possible? There are some cases when you really require this. Some are related to providers which don't load unless some packages are installed (see augeas, the recent post about cron). The biggest problem where I need to do this is when lsb-release isn't installed on a Ubuntu system and as a result the system is detected as debian, which can seriously damage the system. Silviu -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Debian preseed values for puppet deb package
Russ Allbery wrote: Joe McDonagh joseph.e.mcdon...@gmail.com 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 could preseed certname, server, etc. This e-mail is to basically gather thoughts and see if it's worth filing a debian bug to get this functionality into the .deb. Out of curiosity, why not use FAI? Because FAI is deprecated. You can preseed nearly all necessart values via the debian-installer, and LVM can be done in the late-command. Pre-seeding the puppet package itself is a separate issue entirely, that doesn't have to be tied to provisioning. -- Joe McDonagh Silent Penguin Services Operations Engineer AIM: YoosingYoonickz IRC: joe-mac on freenode Blog: www.colonfail.com -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Debian preseed values for puppet deb package
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 r...@stanford.edu wrote: Joe McDonagh joseph.e.mcdon...@gmail.com 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 could preseed certname, server, etc. This e-mail is to basically gather thoughts and see if it's worth filing a debian bug to get this functionality into the .deb. Out of curiosity, why not use FAI? -- Russ Allbery (r...@stanford.edu) http://www.eyrie.org/~eagle/ -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. 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 to get a list of settings that people would like to be able to preseed. -- Joe McDonagh Silent Penguin Services Operations Engineer AIM: YoosingYoonickz IRC: joe-mac on freenode Blog: www.colonfail.com -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: User Modification
On Dec 7, 4:13 pm, jokeeffe jete.okee...@gmail.com 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 did, it was not recommending the model you showed.
Virtual resources help you out mainly when you want to define a
resource that multiple independent classes may need. Each resource
(virtual or not) can be *declared* only once, but virtual resources
can be *realized* as many times as desired (including zero).
For users, the recommended model involved creating a class containing
virtual User declarations for all users that Puppet need ever manage.
Any class that needed any user management must then include the class
of virtual users, and realize those users it cares about. The main
advantage here is centralized user management.
Basically, at my organization, admins come and go. I was hoping to use
puppet to get rid of all logins of admins that no longer work for the
company. So, I was hoping I could just use a simple array to add users
as time goes by to ensure those user no longer have an account.
Puppet can definitely do this job for you. I'm not certain whether
the array syntax gains you anything, though, even if it can be made to
work. Here are some alternatives:
1) If the objective is to minimize the amount of Puppet code required
for this specific task, then I think you could do something like this:
# include this class on all nodes for which the specified users need
to be absent:
class remove_nonusers {
# defaults for user resources declared within the scope of this
class
User { ensure = absent }
# the users that need to be absent; not much more verbose than an
array declaration
user {
bill: ;
billy: ;
bob: ;
}
}
2) If you are willing to use Puppet to manage all non-system accounts
on your machines, then you can rely on user purging by putting this in
an appropriate scope:
resources { user: purge = true, unless_system_user = true }
In that case, Puppet removes any users not known to it and not
considered system accounts (UID 500 by default). Using this
approach requires that you tell Puppet which ordinary user accounts
you want to be present, so overall it may require more code than
option 1. On the other hand, user management is one of the more
common tasks that admins want Puppet to handle, so you may already be
planning or doing this.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Require Module before Resource Type
On Dec 7, 11:19 am, jokeeffe jete.okee...@gmail.com 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
before the cron resource type. How do I fix this? I'm using puppet
0.24.8
I think it's important to understand the Puppet execution model here.
It is described among Reductive's docs:
http://reductivelabs.com/trac/puppet/wiki/PuppetInternals
The key point related to this question is that Puppet instantiates its
entire configuration model before it makes any changes to the client
system (including choosing a provider for each resource), so no effort
to tweak its order of operation is going to solve the problem.
(Indeed, with Puppet it is rarely useful to think in terms of
execution order.)
Things you could try:
1) If you cannot rely on a cron package to be installed before the
Puppet run, then it may help to explicitly specify the provider for
your cron resource:
cron { my-test-cron:
# ...
provider = crontab,
require = Package[vixie-cron],
}
2) Search this group for threads about bootstrapping. You should find
several discussing the use of tags and / or environments bootstrap a
client configuration before applying its normal manifest.
Note also: you probably don't need that Exec resource for crond, as
the Service resource with enable = true will normally handle the
task. You only need an Exec if you want different runlevels than
Service gives you, in which case you should use two Execs -- one to
turn on the service in the runlevels you want, and one to turn it off
in all the others. (Service's support for runlevel control is sadly
lacking through 0.25.1; there is an outstanding feature request to
make it better.)
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] ssh::auth version 0.1 released
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 created on the keymaster and distributed to servers and clients. * Each key pair may be installed onto any set of clients, and enabled for authentication as any user(s) on any set of servers. * Keys may have login options set as in authorized_keys(5), e.g. to force certain commands to run or limit port forwarding. * Keys can be uninstalled or revoked, either manually or automatically at given intervals, and new ones automatically created and distributed. Installation is easy, as it's just one file. ssh::auth aims to provide a complete solution for managing ssh keys for users, with a well-defined and -documented interface. There's a comparison to the other ssh-related tools available in Puppet at http://reductivelabs.com/trac/puppet/wiki/Recipes/ModuleSSHAuth#comparisons . Version 0.1 is an unstable release. It's fully functional in my testing, and meets the documentation as far as I know, but will certainly benefit from some testing and feedback. I call it unstable because once people have had a change to try it out, I'll consider changing the interface from its current definition-oriented version to a more virtual resource-oriented one. Andrew. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] How to add Ubuntu PPA repository (with signing key)?
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
should help me debug any problems.
As far as the yumrepo, I'm still smarting from Red Hat going all
enterprisie ... I jumped 5 machines to Gentoo, and after 3 years of
daily compiles, I twitch a bit when the Ubuntu Update Manager pops
up ;-)
Thanks again!
On Mon, 2009-12-07 at 20:00 +0200, Silviu Paragina wrote:
Use the /etc/apt/sources.list.d/ for adding repositories. Note the files
in there must have .list extension to be considered.
For signing the easy way out is creating a define similar to this one:
I'd advise against this one because I made it when I started using puppet.
In a class:
$folder = /etc/apt/rkeys/
file { $folder :
owner = root,
group = root,
mode= 700,
ensure = directory
}
In the define
define apt_sign_key($sign_key)
{
$file_dest = ${folder}${sign_key}
file { $file_dest :
owner = root,
group = root,
mode= 600,
source = puppet:///somepath/${sign_key},
require = File[$folder]
}
exec { apt-key add ${file_dest}:
refreshonly = true,
require = File[$file_dest],
subscribe = File[$file_dest]
}
}
Another way would be doing something like
file{ ${repokey}: ..}
exec { apt-key add ${repokey}:
require= File[$repokey],
unless= apt-key list | grep $repokeyid
}
And of course the best way would be to do another provider like yumrepo
in ruby :-)
Silviu
On 07.12.2009 17:54, Ron wrote:
I'm new to Puppet. I've read the docs, followed the tutorials, and have
the software up and running on 4 Ubuntu systems. I've written a few
simple modules but could use some help.
I use several PPAs (Personal Package Archives/Ubuntu). Can anyone
suggest how to add a PPA repository, along with the signing key, into
the base Ubuntu repository? (My goal is to manage Ubuntu upgrades on
heavily customized systems, should anyone have pointers or code that
might help.)
(I intend to practice by installing VLC from the PPA -
https://launchpad.net/~c-korn/+archive/vlc )
Thank you.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] How to add Ubuntu PPA repository (with signing key)?
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 their Chrome browser there. That example
should help me debug any problems.
Super cool. :-)
As far as the yumrepo, I'm still smarting from Red Hat going all
enterprisie ... I jumped 5 machines to Gentoo, and after 3 years of
daily compiles, I twitch a bit when the Ubuntu Update Manager pops
up ;-)
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
internals. This is the elegant, but complex solution. Now I'm balabbering.
Distro change requires a lot of work, so I wouldn't recommend that that
easily (and I didn't).
Silviu
Thanks again!
On Mon, 2009-12-07 at 20:00 +0200, Silviu Paragina wrote:
Use the /etc/apt/sources.list.d/ for adding repositories. Note the files
in there must have .list extension to be considered.
For signing the easy way out is creating a define similar to this one:
I'd advise against this one because I made it when I started using puppet.
In a class:
$folder = /etc/apt/rkeys/
file { $folder :
owner = root,
group = root,
mode= 700,
ensure = directory
}
In the define
define apt_sign_key($sign_key)
{
$file_dest = ${folder}${sign_key}
file { $file_dest :
owner = root,
group = root,
mode= 600,
source = puppet:///somepath/${sign_key},
require = File[$folder]
}
exec { apt-key add ${file_dest}:
refreshonly = true,
require = File[$file_dest],
subscribe = File[$file_dest]
}
}
Another way would be doing something like
file{ ${repokey}: ..}
exec { apt-key add ${repokey}:
require= File[$repokey],
unless= apt-key list | grep $repokeyid
}
And of course the best way would be to do another provider like yumrepo
in ruby :-)
Silviu
On 07.12.2009 17:54, Ron wrote:
I'm new to Puppet. I've read the docs, followed the tutorials, and have
the software up and running on 4 Ubuntu systems. I've written a few
simple modules but could use some help.
I use several PPAs (Personal Package Archives/Ubuntu). Can anyone
suggest how to add a PPA repository, along with the signing key, into
the base Ubuntu repository? (My goal is to manage Ubuntu upgrades on
heavily customized systems, should anyone have pointers or code that
might help.)
(I intend to practice by installing VLC from the PPA -
https://launchpad.net/~c-korn/+archive/vlc )
Thank you.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Debian preseed values for puppet deb package
Joe McDonagh joseph.e.mcdon...@gmail.com 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 to get a list of settings that people would like to be able to preseed. I think the only one I care about is server. For me, everything after that is set by puppet itself. But you could also add environment, wait-time, boot-or-cron. seph -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: other end went away leads to multiple report mails
On Mon, Dec 7, 2009 at 2:27 AM, Peter Meier peter.me...@immerda.ch 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[:name] = puppetmasterd
Puppet::Node::Facts.terminus_class = :yaml
File.find(/var/puppet/reports) do | report |
next if FileTest.directory?(report)
thisreport = open(report) { |fh| YAML::load(fh) }
print Host: + thisreport.host
reporttime = File.stat(report).mtime.to_i # seconds since epoch...
thisreport.logs.each do |log|
# Whatever you want to find out about each message...
end
File.unlink(report) # If you don't need them anymore...
end
would be nice to have such a working example in ext/
I agree, a working example would be awesome.
Luke
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Puppet Dashboard 0.0.1 Release Announcement
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 informed and in control of everything going on in your Puppet ecosystem. It currently functions as a reporting dashboard and an external node repository and will soon do much more, including having better marketing copy. This release is a minimally functional alpha release targeted especially at those of you who are interested in playing with a shiny new tool and helping to shape its further development. As Puppet Dashboard is under active development, you can expect future releases to be frequent and driven largely by feedback from the Puppet community (that would be you). Code and installation instructions: http://github.com/reductivelabs/puppet-dashboard Tickets: http://projects.reductivelabs.com/projects/dashboard I am also available via the puppet-users list and in #puppet on irc.freenode.net as ReinH for any questions. -- Rein Henrichs | http://reductivelabs.com | http://reinh.com -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Training for February?
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 mich...@halligan.org wrote: Does anyone have the details for the Feb training in SF yet? I want to send one of my crew to it, but they also want to go to PyCon ... -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Cleaning Out Stored Configs
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 configurations. We created a script that iterates through the database deleting associated lines from hosts/fact_values/resources/resource_tags/param_values tables cleaning out information for old hosts, but then doing a puppet run on say our Munin or Nagios doesn't seem to fix things, Puppet doesn't seem to notice that the extra Nagios or virtual configurations we're using for Munin have vanished, so isn't rebuilding the Nagios/Munin files. Does anyone have any idea how we can solve this problem? We're using Puppet 0.25.1. Cheers. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Timestamps need to be in sync on all puppetmasters?
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. tony...@gmail.com wrote:
I've see this very often but not sure if this is the issue you are
describing:
Dec 4 03:36:19 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib]/checksum) checksum changed '{mtime}Fri Oct
30 11:05:32 -0700 2009' to '{mtime}Fri Oct 30 18:05:50 + 2009'
Dec 4 03:36:20 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet]/checksum) checksum changed
'{mtime}Fri Oct 30 11:05:33 -0700 2009' to '{mtime}Fri Oct 30 18:05:50
+ 2009'
Dec 4 03:36:21 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/type]/checksum) checksum changed
'{mtime}Fri Oct 30 11:05:49 -0700 2009' to '{mtime}Fri Oct 30 18:05:50
+ 2009'
Dec 4 03:36:24 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/parser]/checksum) checksum changed
'{mtime}Fri Oct 30 11:05:50 -0700 2009' to '{mtime}Fri Oct 30 18:05:50
+ 2009'
Dec 4 03:36:29 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/parser/functions]/checksum) checksum
changed '{mtime}Fri Oct 30 11:05:50 -0700 2009' to '{mtime}Fri Oct 30
18:05:50 + 2009'
Dec 4 03:36:29 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider]/checksum) checksum changed
'{mtime}Fri Oct 30 11:05:33 -0700 2009' to '{mtime}Fri Oct 30 18:05:48
+ 2009'
Dec 4 03:36:36 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider/package]/checksum) checksum
changed '{mtime}Fri Oct 30 11:05:35 -0700 2009' to '{mtime}Fri Oct 30
18:05:48 + 2009'
Dec 4 03:37:00 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider/sysctl]/checksum) checksum
changed '{mtime}Fri Oct 30 11:05:48 -0700 2009' to '{mtime}Fri Oct 30
18:05:49 + 2009'
Dec 4 03:37:01 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider/volumegroup]/checksum)
checksum changed '{mtime}Fri Oct 30 11:05:34 -0700 2009' to
'{mtime}Fri Oct 30 18:05:35 + 2009'
Dec 4 03:37:06 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider/logicalvolume]/checksum)
checksum changed '{mtime}Fri Oct 30 11:05:33 -0700 2009' to
'{mtime}Fri Oct 30 18:05:34 + 2009'
Dec 4 03:37:07 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider/physicalvolume]/checksum)
checksum changed '{mtime}Fri Oct 30 11:05:34 -0700 2009' to
'{mtime}Fri Oct 30 18:05:34 + 2009'
Dec 4 03:37:15 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/facter]/checksum) checksum changed
'{mtime}Fri Oct 30 11:05:50 -0700 2009' to '{mtime}Tue Nov 03 08:00:05
+ 2009'
Dec 4 03:37:33 puppetclient puppetd[16163]: Starting catalog run
Dec 4 03:39:46 puppetclient puppetd[16163]: Finished catalog run in
133.44 seconds
I've not been able to look on what is causing it, I belive it's coming
after we change the environment the puppetclient is pointing to,
although we use the same puppetmaster to use different
environments(dev, prod).
Thoughts?
Thanks
On Thu, Dec 3, 2009 at 2:31 PM, Digant C Kasundra
dig...@stanford.edu wrote:
Hey guys,
We're using multiple puppetmasters and I could have sworn I had
uncovered an issue once where if a file had a different timestamp on
two puppetmasters, clients would keep replacing the file depending on
which puppetmaster they talked to because the clients thought the
files were changing. But I've been unable to reproduce this problem.
Is this only an issue in certain situations? We're not using the
checksum parameter to tell file resources to use timestamps and the
type references seems to indicate that the default is md5 but I could
have sworn I uncovered the aforementioned issue before but cannot for
the life of me replicate it now. Anyone else know what I'm talking
about?
--
Digant C Kasundra dig...@stanford.edu
Technical Lead, ITS Unix Systems and Applications, Stanford University
--
You received this message because you are subscribed to the Google
Groups Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com .
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com .
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en .
--
Tony
-- You received this message because you are subscribed to the Google
Groups Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
Digant C Kasundra dig...@stanford.edu
Technical Lead, ITS Unix Systems and Applications, Stanford University
--
You received this
Re: [Puppet Users] Puppet Dashboard 0.0.1 Release Announcement
On Tue, Dec 8, 2009 at 11:14 AM, Rein Henrichs r...@reductivelabs.com 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 Dashboard is (or will be) a web front end that keeps you informed and in control of everything going on in your Puppet ecosystem. It currently functions as a reporting dashboard and an external node repository and will soon do much more, including having better marketing copy. This release is a minimally functional alpha release targeted especially at those of you who are interested in playing with a shiny new tool and helping to shape its further development. As Puppet Dashboard is under active development, you can expect future releases to be frequent and driven largely by feedback from the Puppet community (that would be you). Code and installation instructions: http://github.com/reductivelabs/puppet-dashboard Tickets: http://projects.reductivelabs.com/projects/dashboard I am also available via the puppet-users list and in #puppet on irc.freenode.net as ReinH for any questions. First thoughts are that I really quite like it, it's zippy and clean. Are you planning to expose storeconfigs data as well? I'd love to at least be able to see thin_storeconfigs fact/value data for hosts as well as reports. (I've actually often thought facts would make sense as part of a report) -- Rein Henrichs | http://reductivelabs.com | http://reinh.com -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- nigel -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] How to add Ubuntu PPA repository (with signing key)?
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 internals. This is the elegant, but complex solution. Now I'm balabbering. You're not blabbering. A new type in Puppet seems like the right idea to me. J. -- Julian Simpson Software Build and Deployment http://www.build-doctor.com http://twitter.com/builddoctor -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Puppet Dashboard 0.0.1 Release Announcement
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 Dashboard is (or will be) a web front end that keeps you informed and in control of everything going on in your Puppet ecosystem. It currently functions as a reporting dashboard and an external node repository and will soon do much more, including having better marketing copy. This release is a minimally functional alpha release targeted especially at those of you who are interested in playing with a shiny new tool and helping to shape its further development. As Puppet Dashboard is under active development, you can expect future releases to be frequent and driven largely by feedback from the Puppet community (that would be you). Code and installation instructions: http://github.com/reductivelabs/puppet-dashboard Tickets: http://projects.reductivelabs.com/projects/dashboard I am also available via the puppet-users list and in #puppet on irc.freenode.net as ReinH for any questions. It may sound stupid but are there any screen shots to see (at least) some of the functionality currently exposed by the dashboard? Silviu -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Debian preseed values for puppet deb package
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 pseudo auto-signing for puppet with the help of some custom functions. Ie it allows initial connect, on this run you get the real hostname via a custom fact, call a function, delayed (anacron or something) sign the certificate, modify via manifests the puppet.conf to be what you got for the real hostname. Also you could include some other bootstrap stuff in this run. _Server:_ For the server package I counter recommend anything. If you need to automate a puppet master install it would be a good idea to do it via some manifest and/or with the help of another puppet master. Silviu On 08.12.2009 16:57, Joe McDonagh wrote: 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 Allberyr...@stanford.edu wrote: Joe McDonaghjoseph.e.mcdon...@gmail.com 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 could preseed certname, server, etc. This e-mail is to basically gather thoughts and see if it's worth filing a debian bug to get this functionality into the .deb. Out of curiosity, why not use FAI? -- Russ Allbery (r...@stanford.edu)http://www.eyrie.org/~eagle/ -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. 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 to get a list of settings that people would like to be able to preseed. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Timestamps need to be in sync on all puppetmasters?
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 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.tony...@gmail.com wrote:
I've see this very often but not sure if this is the issue you are
describing:
Dec 4 03:36:19 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib]/checksum) checksum changed '{mtime}Fri Oct
30 11:05:32 -0700 2009' to '{mtime}Fri Oct 30 18:05:50 + 2009'
Dec 4 03:36:20 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet]/checksum) checksum changed
'{mtime}Fri Oct 30 11:05:33 -0700 2009' to '{mtime}Fri Oct 30 18:05:50
+ 2009'
Dec 4 03:36:21 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/type]/checksum) checksum changed
'{mtime}Fri Oct 30 11:05:49 -0700 2009' to '{mtime}Fri Oct 30 18:05:50
+ 2009'
Dec 4 03:36:24 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/parser]/checksum) checksum changed
'{mtime}Fri Oct 30 11:05:50 -0700 2009' to '{mtime}Fri Oct 30 18:05:50
+ 2009'
Dec 4 03:36:29 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/parser/functions]/checksum) checksum
changed '{mtime}Fri Oct 30 11:05:50 -0700 2009' to '{mtime}Fri Oct 30
18:05:50 + 2009'
Dec 4 03:36:29 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider]/checksum) checksum changed
'{mtime}Fri Oct 30 11:05:33 -0700 2009' to '{mtime}Fri Oct 30 18:05:48
+ 2009'
Dec 4 03:36:36 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider/package]/checksum) checksum
changed '{mtime}Fri Oct 30 11:05:35 -0700 2009' to '{mtime}Fri Oct 30
18:05:48 + 2009'
Dec 4 03:37:00 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider/sysctl]/checksum) checksum
changed '{mtime}Fri Oct 30 11:05:48 -0700 2009' to '{mtime}Fri Oct 30
18:05:49 + 2009'
Dec 4 03:37:01 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider/volumegroup]/checksum)
checksum changed '{mtime}Fri Oct 30 11:05:34 -0700 2009' to
'{mtime}Fri Oct 30 18:05:35 + 2009'
Dec 4 03:37:06 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider/logicalvolume]/checksum)
checksum changed '{mtime}Fri Oct 30 11:05:33 -0700 2009' to
'{mtime}Fri Oct 30 18:05:34 + 2009'
Dec 4 03:37:07 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider/physicalvolume]/checksum)
checksum changed '{mtime}Fri Oct 30 11:05:34 -0700 2009' to
'{mtime}Fri Oct 30 18:05:34 + 2009'
Dec 4 03:37:15 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/facter]/checksum) checksum changed
'{mtime}Fri Oct 30 11:05:50 -0700 2009' to '{mtime}Tue Nov 03 08:00:05
+ 2009'
Dec 4 03:37:33 puppetclient puppetd[16163]: Starting catalog run
Dec 4 03:39:46 puppetclient puppetd[16163]: Finished catalog run in
133.44 seconds
I've not been able to look on what is causing it, I belive it's coming
after we change the environment the puppetclient is pointing to,
although we use the same puppetmaster to use different
environments(dev, prod).
Thoughts?
Thanks
On Thu, Dec 3, 2009 at 2:31 PM, Digant C Kasundra
dig...@stanford.edu wrote:
Hey guys,
We're using multiple puppetmasters and I could have sworn I had
uncovered an issue once where if a file had a different timestamp on
two puppetmasters, clients would keep replacing the file depending on
which puppetmaster they talked to because the clients thought the
files were changing. But I've been unable to reproduce this problem.
Is this only an issue in certain situations? We're not using the
checksum parameter to tell file resources to use timestamps and the
type references seems to indicate that the default is md5 but I could
have sworn I uncovered the aforementioned issue before but cannot for
the life of me replicate it now. Anyone else know what I'm talking
about?
--
Digant C Kasundra dig...@stanford.edu
Technical Lead, ITS Unix Systems and Applications, Stanford University
--
You received this message because you are subscribed to the Google
Groups Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com .
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com .
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en .
--
Tony
-- You received this message because you are subscribed to the Google
Groups Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
Re: [Puppet Users] Puppet Dashboard 0.0.1 Release Announcement
On Tue, Dec 8, 2009 at 12:54 PM, Nigel Kersten nig...@google.com 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 storeconfigs data as well? I'd love to at least be able to see thin_storeconfigs fact/value data for hosts as well as reports. We're definitely planning on exposing node facts and other information in an upcoming release. (I've actually often thought facts would make sense as part of a report) Once we have more structured reporting data to work with (which we're currently adding to Puppet), we'll be able to do more interesting and informative reporting without having to parse log data (which is slow, inaccurate and bound to be quickly obsoleted). On Tue, Dec 8, 2009 at 1:25 PM, Silviu Paragina sil...@paragina.ro wrote: It may sound stupid but are there any screen shots to see (at least) some of the functionality currently exposed by the dashboard? It doesn't sound stupid at all. In fact, I'm writing up a blog post on the Reductive Labs blog[1] this week to provide screenshots and an overview of the existing functionality. Please don't hesitate to use the Redmine tracker[2] for feature or enhancement requests and bug reports. We're definitely interested in the feedback. Also, apologies for the double post. [1] http://reductivelabs.com/home/blog/ [2] http://projects.reductivelabs.com/projects/dashboard -- Rein Henrichs | http://reductivelabs.com | http://reinh.com -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] New developer: Jesse Wolfe
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 a computer that he's found so far -- but even so, he was eager to join a project that included a parser. Recently, Jesse has been seen trying to talk small business owners into moving their servers onto the Amazon cloud, having long conversations about how to balance between object-oriented and pure- functional programming styles, and competing in programming competitions. His hobbies include drinking coffee. You might have already seen Jesse's contributions, first as a means of proving both his commitment and ability, and more recently as a contractor. His work has been great, so we're happy that we're able to bring him on full time at Reductive Labs. Cheers, Luke -- My favorite was a professor at a University I Used To Be Associated With who claimed that our requirement of a non-alphabetic character in our passwords was an abridgement of his freedom of speech. -- Jacob Haller - Luke Kanies -|- http://reductivelabs.com -|- +1(615)594-8199 -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Debian preseed values for puppet deb package
Joe McDonagh joseph.e.mcdon...@gmail.com 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 debian-installer and all packages to support the preseeds that you want. -- Russ Allbery (r...@stanford.edu) http://www.eyrie.org/~eagle/ -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Timestamps need to be in sync on all puppetmasters?
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/Pacific*
*UTC=true*
ARC=false
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)
fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT
fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT0
fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT-0
fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT+0
fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/Greenwich
Could the /etc/sysconfig/clock file cause this?
Thanks!
On Tue, Dec 8, 2009 at 1:50 PM, Silviu Paragina sil...@paragina.ro wrote:
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 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.tony...@gmail.com wrote:
I've see this very often but not sure if this is the issue you are
describing:
Dec 4 03:36:19 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib]/checksum) checksum changed '{mtime}Fri Oct
30 11:05:32 -0700 2009' to '{mtime}Fri Oct 30 18:05:50 + 2009'
Dec 4 03:36:20 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet]/checksum) checksum changed
'{mtime}Fri Oct 30 11:05:33 -0700 2009' to '{mtime}Fri Oct 30 18:05:50
+ 2009'
Dec 4 03:36:21 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/type]/checksum) checksum changed
'{mtime}Fri Oct 30 11:05:49 -0700 2009' to '{mtime}Fri Oct 30 18:05:50
+ 2009'
Dec 4 03:36:24 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/parser]/checksum) checksum changed
'{mtime}Fri Oct 30 11:05:50 -0700 2009' to '{mtime}Fri Oct 30 18:05:50
+ 2009'
Dec 4 03:36:29 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/parser/functions]/checksum) checksum
changed '{mtime}Fri Oct 30 11:05:50 -0700 2009' to '{mtime}Fri Oct 30
18:05:50 + 2009'
Dec 4 03:36:29 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider]/checksum) checksum changed
'{mtime}Fri Oct 30 11:05:33 -0700 2009' to '{mtime}Fri Oct 30 18:05:48
+ 2009'
Dec 4 03:36:36 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider/package]/checksum) checksum
changed '{mtime}Fri Oct 30 11:05:35 -0700 2009' to '{mtime}Fri Oct 30
18:05:48 + 2009'
Dec 4 03:37:00 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider/sysctl]/checksum) checksum
changed '{mtime}Fri Oct 30 11:05:48 -0700 2009' to '{mtime}Fri Oct 30
18:05:49 + 2009'
Dec 4 03:37:01 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider/volumegroup]/checksum)
checksum changed '{mtime}Fri Oct 30 11:05:34 -0700 2009' to
'{mtime}Fri Oct 30 18:05:35 + 2009'
Dec 4 03:37:06 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider/logicalvolume]/checksum)
checksum changed '{mtime}Fri Oct 30 11:05:33 -0700 2009' to
'{mtime}Fri Oct 30 18:05:34 + 2009'
Dec 4 03:37:07 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider/physicalvolume]/checksum)
checksum changed '{mtime}Fri Oct 30 11:05:34 -0700 2009' to
'{mtime}Fri Oct 30 18:05:34 + 2009'
Dec 4 03:37:15 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/facter]/checksum) checksum changed
'{mtime}Fri Oct 30 11:05:50 -0700 2009' to '{mtime}Tue Nov 03 08:00:05
+ 2009'
Dec 4 03:37:33 puppetclient puppetd[16163]: Starting catalog run
Dec 4 03:39:46 puppetclient puppetd[16163]: Finished catalog run in
133.44 seconds
I've not been able to look on what is causing it, I belive it's coming
after we change the environment the puppetclient is pointing to,
although we use the same puppetmaster to use different
environments(dev, prod).
Thoughts?
Thanks
On Thu, Dec 3, 2009 at 2:31 PM, Digant C Kasundra
dig...@stanford.edu wrote:
Hey guys,
We're using multiple puppetmasters and I could have sworn I had
uncovered an issue once where if a file had a different timestamp on
two puppetmasters, clients would keep replacing the file depending on
which puppetmaster they talked to because the clients thought the
files were changing. But I've been unable to reproduce this problem.
Is this only an issue in certain situations? We're not using the
checksum
Re: [Puppet Users] Timestamps need to be in sync on all puppetmasters?
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) fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT0 fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT-0 fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT+0 fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/Greenwich Could the /etc/sysconfig/clock file cause this? UNIX time is based on the number of seconds since January 1, 1970 00:00 UTC. This is converted to local time for display based on the TZ environment variable, with /etc/localtime specifying the default local time conversions rule (and usually a copy or link to a corresponding rule file in /usr/share/zoneinfo). /etc/sysconfig/clock has only to do with management of the hardware clock. The ZONE setting in combination with the UTC boolean determine whether the hardware clock is treated as local time or UTC when the hardware clock is set from the UNIX clock during shutdown. For most server configurations it is advisable to manage the hardware clock in UTC (UTC=true). In particular this can avoid some problems with reboots around daylight savings time changes introducing 1 hour offsets. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Timestamps need to be in sync on all puppetmasters?
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
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/Pacific*
*UTC=true*
ARC=false
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)
fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT
fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT0
fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT-0
fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT+0
fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/Greenwich
Could the /etc/sysconfig/clock file cause this?
Thanks!
On Tue, Dec 8, 2009 at 1:50 PM, Silviu Paragina sil...@paragina.ro
mailto:sil...@paragina.ro wrote:
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 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.tony...@gmail.com mailto:tony...@gmail.com
wrote:
I've see this very often but not sure if this is the issue you are
describing:
Dec 4 03:36:19 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib]/checksum) checksum changed
'{mtime}Fri Oct
30 11:05:32 -0700 2009' to '{mtime}Fri Oct 30 18:05:50 + 2009'
Dec 4 03:36:20 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet]/checksum) checksum changed
'{mtime}Fri Oct 30 11:05:33 -0700 2009' to '{mtime}Fri Oct 30
18:05:50
+ 2009'
Dec 4 03:36:21 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/type]/checksum) checksum changed
'{mtime}Fri Oct 30 11:05:49 -0700 2009' to '{mtime}Fri Oct 30
18:05:50
+ 2009'
Dec 4 03:36:24 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/parser]/checksum) checksum
changed
'{mtime}Fri Oct 30 11:05:50 -0700 2009' to '{mtime}Fri Oct 30
18:05:50
+ 2009'
Dec 4 03:36:29 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/parser/functions]/checksum)
checksum
changed '{mtime}Fri Oct 30 11:05:50 -0700 2009' to '{mtime}Fri
Oct 30
18:05:50 + 2009'
Dec 4 03:36:29 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider]/checksum) checksum
changed
'{mtime}Fri Oct 30 11:05:33 -0700 2009' to '{mtime}Fri Oct 30
18:05:48
+ 2009'
Dec 4 03:36:36 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider/package]/checksum)
checksum
changed '{mtime}Fri Oct 30 11:05:35 -0700 2009' to '{mtime}Fri
Oct 30
18:05:48 + 2009'
Dec 4 03:37:00 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider/sysctl]/checksum)
checksum
changed '{mtime}Fri Oct 30 11:05:48 -0700 2009' to '{mtime}Fri
Oct 30
18:05:49 + 2009'
Dec 4 03:37:01 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider/volumegroup]/checksum)
checksum changed '{mtime}Fri Oct 30 11:05:34 -0700 2009' to
'{mtime}Fri Oct 30 18:05:35 + 2009'
Dec 4 03:37:06 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider/logicalvolume]/checksum)
checksum changed '{mtime}Fri Oct 30 11:05:33 -0700 2009' to
'{mtime}Fri Oct 30 18:05:34 + 2009'
Dec 4 03:37:07 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider/physicalvolume]/checksum)
checksum changed '{mtime}Fri Oct 30 11:05:34 -0700 2009' to
'{mtime}Fri Oct 30 18:05:34 + 2009'
Dec 4 03:37:15 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/facter]/checksum) checksum changed
'{mtime}Fri Oct 30 11:05:50 -0700 2009' to '{mtime}Tue Nov 03
08:00:05
+ 2009'
Dec 4 03:37:33 puppetclient puppetd[16163]: Starting catalog run
Dec 4 03:39:46 puppetclient puppetd[16163]: Finished catalog run in
133.44 seconds
I've not been able to look on what is causing it, I belive it's
coming
after we change the environment the puppetclient is pointing to,
although we
Re: [Puppet Users] Timestamps need to be in sync on all puppetmasters?
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 sil...@paragina.ro 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.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
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/Pacific*
*UTC=true*
ARC=false
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)
fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT
fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT0
fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT-0
fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT+0
fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/Greenwich
Could the /etc/sysconfig/clock file cause this?
Thanks!
On Tue, Dec 8, 2009 at 1:50 PM, Silviu Paragina sil...@paragina.rowrote:
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 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.tony...@gmail.com wrote:
I've see this very often but not sure if this is the issue you are
describing:
Dec 4 03:36:19 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib]/checksum) checksum changed '{mtime}Fri Oct
30 11:05:32 -0700 2009' to '{mtime}Fri Oct 30 18:05:50 + 2009'
Dec 4 03:36:20 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet]/checksum) checksum changed
'{mtime}Fri Oct 30 11:05:33 -0700 2009' to '{mtime}Fri Oct 30 18:05:50
+ 2009'
Dec 4 03:36:21 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/type]/checksum) checksum changed
'{mtime}Fri Oct 30 11:05:49 -0700 2009' to '{mtime}Fri Oct 30 18:05:50
+ 2009'
Dec 4 03:36:24 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/parser]/checksum) checksum changed
'{mtime}Fri Oct 30 11:05:50 -0700 2009' to '{mtime}Fri Oct 30 18:05:50
+ 2009'
Dec 4 03:36:29 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/parser/functions]/checksum) checksum
changed '{mtime}Fri Oct 30 11:05:50 -0700 2009' to '{mtime}Fri Oct 30
18:05:50 + 2009'
Dec 4 03:36:29 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider]/checksum) checksum changed
'{mtime}Fri Oct 30 11:05:33 -0700 2009' to '{mtime}Fri Oct 30 18:05:48
+ 2009'
Dec 4 03:36:36 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider/package]/checksum) checksum
changed '{mtime}Fri Oct 30 11:05:35 -0700 2009' to '{mtime}Fri Oct 30
18:05:48 + 2009'
Dec 4 03:37:00 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider/sysctl]/checksum) checksum
changed '{mtime}Fri Oct 30 11:05:48 -0700 2009' to '{mtime}Fri Oct 30
18:05:49 + 2009'
Dec 4 03:37:01 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider/volumegroup]/checksum)
checksum changed '{mtime}Fri Oct 30 11:05:34 -0700 2009' to
'{mtime}Fri Oct 30 18:05:35 + 2009'
Dec 4 03:37:06 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider/logicalvolume]/checksum)
checksum changed '{mtime}Fri Oct 30 11:05:33 -0700 2009' to
'{mtime}Fri Oct 30 18:05:34 + 2009'
Dec 4 03:37:07 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider/physicalvolume]/checksum)
checksum changed '{mtime}Fri Oct 30 11:05:34 -0700 2009' to
'{mtime}Fri Oct 30 18:05:34 + 2009'
Dec 4 03:37:15 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/facter]/checksum) checksum changed
'{mtime}Fri Oct 30 11:05:50 -0700 2009' to '{mtime}Tue Nov 03 08:00:05
+ 2009'
Dec 4 03:37:33 puppetclient puppetd[16163]: Starting catalog run
Dec 4 03:39:46 puppetclient puppetd[16163]: Finished catalog run in
133.44 seconds
I've not been able to look on what is causing it, I belive it's coming
after we change the environment the puppetclient is pointing to,
although we use the same puppetmaster to use different
environments(dev, prod).
Thoughts?
Thanks
On Thu, Dec 3, 2009 at 2:31 PM, Digant C Kasundra
dig...@stanford.edu wrote:
Hey guys,
We're using multiple puppetmasters and I could have sworn I had
Re: [Puppet Users] Timestamps need to be in sync on all puppetmasters?
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 can help, since there are a lot of other components
that could change the standard behavior depending on setup
(apache/nginx/passenger/mongrel etc)
Silviu
On 09.12.2009 03:53, Ohad Levy wrote:
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 sil...@paragina.ro
mailto:sil...@paragina.ro 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.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
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/Pacific*
*UTC=true*
ARC=false
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)
fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT
fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT0
fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT-0
fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT+0
fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/Greenwich
Could the /etc/sysconfig/clock file cause this?
Thanks!
On Tue, Dec 8, 2009 at 1:50 PM, Silviu Paragina
sil...@paragina.ro mailto:sil...@paragina.ro wrote:
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 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.tony...@gmail.com
mailto:tony...@gmail.com wrote:
I've see this very often but not sure if this is the issue
you are
describing:
Dec 4 03:36:19 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib]/checksum) checksum changed
'{mtime}Fri Oct
30 11:05:32 -0700 2009' to '{mtime}Fri Oct 30 18:05:50
+ 2009'
Dec 4 03:36:20 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet]/checksum) checksum changed
'{mtime}Fri Oct 30 11:05:33 -0700 2009' to '{mtime}Fri Oct
30 18:05:50
+ 2009'
Dec 4 03:36:21 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/type]/checksum) checksum
changed
'{mtime}Fri Oct 30 11:05:49 -0700 2009' to '{mtime}Fri Oct
30 18:05:50
+ 2009'
Dec 4 03:36:24 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/parser]/checksum)
checksum changed
'{mtime}Fri Oct 30 11:05:50 -0700 2009' to '{mtime}Fri Oct
30 18:05:50
+ 2009'
Dec 4 03:36:29 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/parser/functions]/checksum)
checksum
changed '{mtime}Fri Oct 30 11:05:50 -0700 2009' to
'{mtime}Fri Oct 30
18:05:50 + 2009'
Dec 4 03:36:29 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider]/checksum)
checksum changed
'{mtime}Fri Oct 30 11:05:33 -0700 2009' to '{mtime}Fri Oct
30 18:05:48
+ 2009'
Dec 4 03:36:36 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider/package]/checksum)
checksum
changed '{mtime}Fri Oct 30 11:05:35 -0700 2009' to
'{mtime}Fri Oct 30
18:05:48 + 2009'
Dec 4 03:37:00 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider/sysctl]/checksum)
checksum
changed '{mtime}Fri Oct 30 11:05:48 -0700 2009' to
'{mtime}Fri Oct 30
18:05:49 + 2009'
Dec 4 03:37:01 puppetclient puppetd[16163]:
Re: [Puppet Users] Timestamps need to be in sync on all puppetmasters?
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, Dec 8, 2009 at 5:59 PM, Silviu Paragina sil...@paragina.ro wrote:
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 can help, since there are a lot of other components
that could change the standard behavior depending on setup
(apache/nginx/passenger/mongrel etc)
Silviu
On 09.12.2009 03:53, Ohad Levy wrote:
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 sil...@paragina.rowrote:
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
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/Pacific*
*UTC=true*
ARC=false
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)
fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT
fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT0
fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT-0
fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/GMT+0
fcccbcf95c718cf2fdee557763e460be /usr/share/zoneinfo/Greenwich
Could the /etc/sysconfig/clock file cause this?
Thanks!
On Tue, Dec 8, 2009 at 1:50 PM, Silviu Paragina sil...@paragina.rowrote:
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 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.tony...@gmail.com wrote:
I've see this very often but not sure if this is the issue you are
describing:
Dec 4 03:36:19 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib]/checksum) checksum changed '{mtime}Fri Oct
30 11:05:32 -0700 2009' to '{mtime}Fri Oct 30 18:05:50 + 2009'
Dec 4 03:36:20 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet]/checksum) checksum changed
'{mtime}Fri Oct 30 11:05:33 -0700 2009' to '{mtime}Fri Oct 30 18:05:50
+ 2009'
Dec 4 03:36:21 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/type]/checksum) checksum changed
'{mtime}Fri Oct 30 11:05:49 -0700 2009' to '{mtime}Fri Oct 30 18:05:50
+ 2009'
Dec 4 03:36:24 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/parser]/checksum) checksum changed
'{mtime}Fri Oct 30 11:05:50 -0700 2009' to '{mtime}Fri Oct 30 18:05:50
+ 2009'
Dec 4 03:36:29 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/parser/functions]/checksum) checksum
changed '{mtime}Fri Oct 30 11:05:50 -0700 2009' to '{mtime}Fri Oct 30
18:05:50 + 2009'
Dec 4 03:36:29 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider]/checksum) checksum changed
'{mtime}Fri Oct 30 11:05:33 -0700 2009' to '{mtime}Fri Oct 30 18:05:48
+ 2009'
Dec 4 03:36:36 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider/package]/checksum) checksum
changed '{mtime}Fri Oct 30 11:05:35 -0700 2009' to '{mtime}Fri Oct 30
18:05:48 + 2009'
Dec 4 03:37:00 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider/sysctl]/checksum) checksum
changed '{mtime}Fri Oct 30 11:05:48 -0700 2009' to '{mtime}Fri Oct 30
18:05:49 + 2009'
Dec 4 03:37:01 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider/volumegroup]/checksum)
checksum changed '{mtime}Fri Oct 30 11:05:34 -0700 2009' to
'{mtime}Fri Oct 30 18:05:35 + 2009'
Dec 4 03:37:06 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider/logicalvolume]/checksum)
checksum changed '{mtime}Fri Oct 30 11:05:33 -0700 2009' to
'{mtime}Fri Oct 30 18:05:34 + 2009'
Dec 4 03:37:07 puppetclient puppetd[16163]:
(/File[/var/lib/puppet/lib/puppet/provider/physicalvolume]/checksum)
Re: [Puppet Users] Stop(or restart and/or reload facts/providers) execution on some conditions
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 the case where lsb-release isn't installed on a $operatingsystem == Debian system I would like to install lsb-realease and then fail or restart just to be sure I'm not actually on a Ubuntu system Another example would be augeas, where, even if in a run augeas would be installed, puppet would fail because of missing augeas provider. Put all clients which do not have lsb-release and/or augeas installed into a separate bootstrap mode. You can use environments and/or tags to implement this. In this special mode just install the tools you need. The next run will resume with the full information available. Normally this special bootstrap run is already done from the installer to make this very easy, e.g. in debian-installer's postcmd: puppetd --environment bootstrap-debian --onetime --no-daemonize Regards, DavidS Can this be automated, if somebody uninstalls lsb-release by mistake for example? aptitude has a bad habit of doing this... And can it be done from a manifest the standard puppet way? One possible way I can think of this is to run puppet (not puppetd) with an exec, but I'm not sure about the locks puppet uses (if the locks are different from puppetd):-? If you can detect from the facts that an erreneous situation is ocurring, you could change the environment at the node level or in an external node script. Regards, DavidS -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Cleaning Out Stored Configs
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 the database, as well as it's nagios and munin configurations. We created a script that iterates through the database deleting associated lines from hosts/fact_values/resources/resource_tags/param_values tables cleaning out information for old hosts, but then doing a puppet run on say our Munin or Nagios doesn't seem to fix things, Puppet doesn't seem to notice that the extra Nagios or virtual configurations we're using for Munin have vanished, so isn't rebuilding the Nagios/Munin files. Does anyone have any idea how we can solve this problem? We're using Puppet 0.25.1. There is a puppetstoredconfigclean.rb in the ext/ directory of the puppet distribution. You can use that to cleanly remove nodes from stored configs. On the matter of managing munin and nagios, you need to use a mechanism like concatenated_file[1], which purges unmanaged parts. After deleting a node from the stored configs db, the resources formerly collected become unmanaged and will be removed by purging. Regards, DavidS [1]http://github.com/puppet-modules/puppet-common/blob/0caa32db1aaad6dabc9542c5e0aa20e76ea94f48/manifests/defines/concatenated_file.pp -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
