Re: [Puppet Users] Enable yum repositories as needed
On Fri, Jun 24, 2011 at 3:37 PM, Nathan Clemons wrote:
> There's an open bug concerning this very issue, in regards to being able to
> specify which repos to use when installing an rpm using the package
> resource.
>
> http://projects.puppetlabs.com/issues/2247
>
> --
> Nathan Clemons
> http://www.livemocha.com
> The worlds largest online language learning community
>
>
>
> On Fri, Jun 24, 2011 at 12:27 PM, Craig White wrote:
>
>>
>> On Jun 24, 2011, at 11:48 AM, James A. Peltier wrote:
>>
>> > Hi All,
>> >
>> > I'm new to puppet and I'm having some difficulty enabling and disabling
>> yum repositories on an as needed basis and I was wondering if you all might
>> be able to provide me with some assistance. I've been able to get puppet to
>> configure a yum repository, I'm going to use EPEL as an example here but I'd
>> like it for all, by creating a class called epel.pp containing
>> >
>> > class epel {
>> > yumrepo { "epel": descr => "Extra Packages for Enterprise Linux
>> \$releasever - \$basearch", baseurl => "
>> http://mirror.its.sfu.ca/mirror/CentOS-Third-Party/epel/\$releasever/\$basearch";,
>> gpgcheck => 1, gpgkey => "
>> http://mirror.its.sfu.ca/mirror/CentOS-Third-Party/epel/RPM-GPG-KEY-EPEL";,
>> enabled=0 }
>> > }
>> >
>> > and it does create and populate the /etc/yum.repos.d/epel.repo file with
>> this information. Now I want to be able to install ganglia-gmond
>> automatically from this repository but I can't figure out how to enable and
>> disable the repo afterwards? Can anyone please provide an example of how
>> something like this may be accomplished?
>>
>> I've been at this for less than a week and primarily concentrating on
>> ubuntu, not RHEL/CentOS so take this with a grain of salt
>>
>> You have to be careful when installing packages from another repo but
>> generally, you just keep the EPEL repo disabled and instead of using the
>> built-in package command, you would want to 'exec' something like...
>>
>> exec('/usr/bin/yum --enablerepo=epel install -y ganglia-gmond') and I
>> would also note that you have to ensure that the rpm-gpg key is installed
>> for the epel repo BEFORE that command is executed - I believe you already
>> provided the gpg-key URL to us.
>>
>> something like this should work (adapt for rpm/yum and note that rpm
>> stores keys in /etc/pki/rpm-gpg)...
>>
>> class apt {
>> package { "apt":
>>ensure => installed,
>>}
>> file{"/etc/apt/sources.list":
>>ensure => present,
>>owner => root,
>>group => root,
>>mode=> 0444,
>>content => template("apt/sources.list.erb"),
>>require => Package["apt"],
>> }
>> exec{"/usr/bin/apt-get update":
>>refreshonly => true,
>>subscribe => File["/etc/apt/sources.list"],
>>require => File["/etc/apt/sources.list"],
>> }
>> # MongoDB Key
>> apt::key { "7F0CEB10":
>>keyid => "7F0CEB10",
>>ensure => present,
>> }
>> }
>> define apt::key($keyid, $ensure, $keyserver = "keyserver.ubuntu.com") {
>> case $ensure {
>>present: {
>> exec { "Import $keyid to apt keystore":
>>path=> "/bin:/usr/bin",
>>environment => "HOME=/root",
>>command => "gpg --keyserver $keyserver --recv-keys $keyid &&
>> gpg --export --armor $keyid | apt-key add -",
>>user=> "root",
>>group => "root",
>>unless => "apt-key list | grep $keyid",
>>logoutput => on_failure,
>> }
>>}
>>absent: {
>> exec { "Remove $keyid from apt keystore":
>>path=> "/bin:/usr/bin",
>>environment => "HOME=/root",
>>command => "apt-key del $keyid",
>>user=> "root",
>>group => "root",
>>onlyif => "apt-key list | grep $keyid",
>> }
>>}
>> default: {
>> fail "Invalid 'ensure' value '$ensure' for apt::key"
>> }
>> }
>> }
>>
>> --
>&g
Re: [Puppet Users] Re: How to use Puppet to ensure the Sun JDK is installed on CentOS-5.5
On Wed, Apr 13, 2011 at 3:53 PM, Shi wrote:
> Thank Jon.
> Based on your class, I've come up with the following code which worked
> for me.
> class sun-jdk {
> package {"java-1.6.0-openjdk":
>ensure => absent,
>}
> exec {"jdk_install":
>cwd => "/root",
>command => "/root/jdk-6u24-linux-x64-rpm.bin",
>creates => "/usr/java/jdk1.6.0_24/bin/javac",
>require => [Package["java-1.6.0-openjdk"], file["/root/
> jdk-6u24-linux-x64-rpm.bin"]],
>}
>package {jdk:
>require => Exec["jdk_install"],
>}
>file {"/root/jdk-6u24-linux-x64-rpm.bin":
>ensure => present,
>source => "puppet:///modules/sun-jdk/jdk-6u24-linux-x64-
> rpm.bin";
>}
> }
> I didn't use NFS share but made use of the puppet file server.
>
> If anyone has suggestions for improvement, please let me know.
> Thanks a lot.
> Shi
>
> On Apr 12, 10:38 pm, Jon Jaroker wrote:
> > I have the same requirement to install Sun JDK, not openJDK. Below is
> > the module I am using. I would be grateful for suggestions on how
> > this install can be done better.
> >
> > Thank you,
> > Jon
> >
> > class java {
> >
> > package {"java-1.6.0-openjdk":
> > ensure => absent,
> > }
> >
> > exec {"java_install":
> > cwd => "/opt",
> > command => "/usr/bin/yes | /opt/share/downloads/java/jdk-6u24-
> > linux-x64.bin",
> > creates => "/opt/jdk1.6.0_24/COPYRIGHT",
> > require => Package["java-1.6.0-openjdk"],
> > }
> >
> > file {"/usr/bin/java":
> > ensure => "/opt/jdk1.6.0_24/bin/java",
> > require => Exec["java_install"],
> > }
> >
> > }
> >
> > On Apr 12, 3:55 pm, Shi wrote:
> >
> >
> >
> >
> >
> >
> >
> > > Hi there,
> >
> > > I am new to Puppet and am writing my first module to manage our
> > > cluster. So far, it worked out reasonably well. I can add yum
> > > repositories and install packages with Puppet automatically.
> > > However, one package requires the use of Sun JDK, not the openjdk
> > > coming with CentOS.
> > > The only way to do this is to download the jdk-6u24-linux-x64-rpm.bin
> > > file and run it.
> >
> > > I figure I might be able to use something like
> >
> > > package {jdk:
> > > source="/mnt/share/jdk-6u24-linux-x64-rpm.bin",
> > > ensure => installed;
> > > }
> >
> > > I guess I could put the file under the shared NFS /mnt/share. But
> > > there is no way I can tell puppet to simply run the source as an
> > > executable. All the PROVIDER options are for a particular format, such
> > > as RPM or DEB. I guess I could run the file once on one machine, and
> > > it will extract the rpms. I could then just use the rpms, but that is
> > > less than ideal.
> >
> > > Also, if I don't want to pre-mount the NFS share, is there any way to
> > > scp the file from the master node? Do I then have to set up ssh
> > > without password for the root?
> >
> > > Thank you very much.
> > > Shi
>
> --
> 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.
>
>
Hi,
Having been down this road with java and various other packages I'd suggest
managing the package at the pkg. manager/mirror level (i.e. custom pkg) and
_then_ pull from that with java-ensure class as required (also consider
utilizing alternatives command for the system implementation.
Of course './jdk-6u21-linux-x64-rpm.bin -x ' will extract the RPM ...
--
Cheers,
Steven
---
Steven Acres
UNIX/Linux System Administrator
--
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.
Re: [Puppet Users] How to create multi-option yum repo file?
On Sat, Apr 16, 2011 at 7:07 AM, Sans wrote:
> Dear all,
>
> How can I create a yum repo like this?
>
> [rpmforge]
> name = RHEL $releasever - RPMforge.net - dag
> baseurl = http://apt.sw.be/redhat/el5/en/$basearch/rpmforge
> enabled = 1
> protect = 0
> gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmforge-dag
> gpgcheck = 1
>
> [rpmforge-extras]
> name = RHEL $releasever - RPMforge.net - extras
> baseurl = http://apt.sw.be/redhat/el5/en/$basearch/extras
> enabled = 0
> protect = 0
>
> I see, "descr" can't be used more than once in the same yumrepo{}
> section. What's the work around? 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-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.
>
>
Hey,
Take a look at the yum module from puzzle.ch here:
https://github.com/puzzle/puppet-yum
--
Cheers,
Steven
---
Steven Acres
UNIX/Linux System Administrator
--
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.
Re: [Puppet Users] Script to find potential puppet clients
On Tue, Apr 19, 2011 at 5:44 PM, Corey Osman wrote: > Has anybody written a script that will scan the network to find systems not > running puppet and ultimately send an email with the findings? > > > > > > I was thinking I can do this by just scanning for port 8141 or is it 8139? > This would assume listen=true is setup on all the existing clients though. > I could then filter out any of the candidates by ensuring the ssh port is > open (this might tell me its a unix system). > > Anybody interested in such a script run via a cron job? > > > Corey > > -- > 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. > > Hi Corey, I have a few scripts that do this (and provision the hosts with the missing parts if needed) .. though all servers which are built now include puppet and friends via KS/cobbler. I've also noted that many organizations don't have _usable_ and/or current inventory management (not to mention dns records with PTR _current_) in place (which I tackle first to make all else manageable). I'd like to see your whack at it though. -- Cheers, Steven --- Steven Acres UNIX/Linux System Administrator -- 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.
Re: [Puppet Users] Re: Inventory service and dashboard 1.1.0 rc1
On Tue, Apr 19, 2011 at 12:32 PM, Prateep wrote: > Forget that. I discovered that there were remnants of the old puppet > version still installed on my master after upgrade. > > Working fine now! > > > On Apr 19, 4:27 pm, Prateep wrote: > > Hi, > > > > I'm seeing exactly the same problem. I have 2.6.7 on both the master > > and client. Any ideas? > > > > Prateep > > > > On Mar 18, 6:48 pm, Jacob Helwig wrote: > > > > > On Thu, 17 Mar 2011 21:32:29 -0700, Luke Baker wrote: > > > > > > I just set up the latest dashboard release candidate in hopes of > > > > trying out the new inventory service. After modifying the puppet- > > > > dashboard config to use the inventory service and after changing my > > > > auth.conf I gave it a whirl but ran into some issues.. > > > > > > I initially tried using fact_terminus = yaml and was able to do some > > > > queries via curl. I'm currently using storeconfigs so setting up > > > > another database for the inventory service was pretty easy, however > > > > when I set fact_terminus to 'inventory_active_record' I receive this > > > > error when performing a puppet run, > > > > > > "Could not find terminus inventory_active_record for indirection > > > > facts" > > > > > > Should this be set to something else for use with puppet-dashboard? > > > > > Are you also using a 2.6.7rc1 puppet master? We probably didn't call > > > this out well enough, but the inventory service features in Dashboard > > > require the new version of Puppet on the master. > > > > > -- > > > Jacob Helwig > > > > > signature.asc > > > < 1KViewDownload > > -- > 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. > > Hi, Prateep, you mentioned "...I discovered that there were remnants of the old puppet version still installed on my master after upgrade..." . That's something I'd rather not experience. Would you please expand on that with regards to install/upgrade method? Thanks. -- Cheers, Steven --- Steven Acres UNIX/Linux System Administrator -- 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.
Re: [Puppet Users] Re: What to do if something is not required on the clients?
On Tue, Apr 19, 2011 at 9:31 PM, Ian Mortimer wrote: > On Wed, 2011-04-20 at 07:37 +1000, Sans wrote: > > > if I know that I definitely don't want httpd to > > be installed on the system at the first place, then why should I care > > about all the packages (maybe installed by default) that need httpd - > > What happens if an update of a required package introduces a new > dependency on httpd. "yum update" will install httpd to satisfy > the dependency but then you have a conflict in your puppet manifest > between ensuring httpd is absent while ensuring the dependent package > is latest. > > (Admittedly I haven't seen this with httpd but something similar > with mysql-server on Fedora). > > > -- > Ian > > > -- > 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. > > This is an excellent example of 'right tool for the job'. The native package manager should be used to manage packages. Puppet is the tool we are using to manage/configure that package manager in an automated fashion keeping in mind that it's not usurping the package manager's function. Yum is a frontend to rpm (man, I don't miss rpm dependency hell of days gone by) and puppet is basically an extra team member (or team even) IMHO. -- Cheers, Steven --- Steven Acres UNIX/Linux System Administrator -- 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.
Re: [Puppet Users] scheduling package installs - ignore schedule if not installed
On Fri, Apr 22, 2011 at 2:34 PM, trey85stang wrote:
> Is there a way to override a schedule for a package if the package is
> not installed?
>
> class packages {
> schedule { installs:
>range => "2-4",
>period => daily,
>repeat => 1,
> }
> package { openssh:
>ensure => latest,
>schedule => installs,
> }
> }
>
> I dont want to check if openssh is the latest package everytime puppet
> runs; but I do want it installed if it is not already installed
> regardless of the schedule.
>
> Anyway to do this?
>
>
Hi,
Sure, there are many ways to achieve this. You would be better off defining
which packages should be present on which nodes in another class. Then use
an include in the node(s) definition (or whatever method you have defined
for your architecture structure).
BTW, if you're using yum and you would like to keep pkgs. updated, you may
want to look into yum-cron.
--
Cheers,
Steven
---
Steven Acres
UNIX/Linux System Administrator
--
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.
Re: [Puppet Users] ssh::auth Question
On Sat, Apr 30, 2011 at 6:21 PM, Douglas Garstang wrote: > So... I was looking at the docs for ssh::auth at > http://projects.puppetlabs.com/projects/1/wiki/Module_Ssh_Auth_Patterns. > > It seems like auth.pp runs on the puppet master rather than the client. How > does that work exactly? > > Doug. > > -- > 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. > Hi Doug, I'm unclear what you're asking. -- Cheers, Steven --- Steven Acres UNIX/Linux System Administrator -- 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.
Re: [Puppet Users] ssh::auth Question
On Sat, Apr 30, 2011 at 7:01 PM, Douglas Garstang
wrote:
> On Sat, Apr 30, 2011 at 3:36 PM, Steven Acres wrote:
>
>> On Sat, Apr 30, 2011 at 6:21 PM, Douglas Garstang <
>> doug.garst...@gmail.com> wrote:
>>
>>> So... I was looking at the docs for ssh::auth at
>>> http://projects.puppetlabs.com/projects/1/wiki/Module_Ssh_Auth_Patterns.
>>>
>>>
>>> It seems like auth.pp runs on the puppet master rather than the client.
>>> How does that work exactly?
>>>
>>> Doug.
>>>
>>> --
>>> 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.
>>>
>>
>> Hi Doug,
>>
>> I'm unclear what you're asking.
>>
>>
> Hmmm... I'm not sure how else to ask it. Does auth.pp run on the puppet
> master or the clients?
>
> Doug.
>
>
> --
> 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.
>
Are you by chance thinking that auth.pp is ... 'handling' authentication de
facto? (it doesn't).
Otherwise, the module provisions the ssh-{server,client} (install, setup,
the daemon and provision the node's keys and users) as specified.
It's actually a good working example of Virtual Resources
http://docs.puppetlabs.com/guides/virtual_resources.html too.
--
Cheers,
Steven
---
Steven Acres
UNIX/Linux System Administrator
--
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.
Re: [Puppet Users] How to check if a package exists
On Sun, May 1, 2011 at 12:48 AM, vagn scott wrote:
>
> Please look at
>
>ldconfig -N
>
> it will update the links for you.
>
> You could try something like (warning untested)
>
> class foo {
>package { "liblcgdm":
>notify => Exec[ "ldconfig::update" ],
>}
>
>include ldconfig::update
> }
>
> class ldconfig::update {
>exec { "ldconfig -N":
>refreshonly => true,
>}
> }
>
> Of course, the package manager should set up these
> links for you when installing the lib.
>
> The other thing to note: If you are installing a library
> without using the package manager you should run
>
>ldconfig
>
> anyway, in order to update your loader's idea of
> what libraries exist, and where they are.
> It also creates any missing links.
>
> again, see ldconfig(8)
>
> --
> vagn
>
> --
> 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.
>
>
As vagn noted, the package manager should be handling this, there most
likely is a valid reason it isn't creating those links (aside from 'bugs').
And if you're sure you want to customize a pkg., re-roll the pkg. You'll
thank yourself later, guaranteed.
--
Cheers,
Steven
---
Steven Acres
UNIX/Linux System Administrator
--
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.
Re: [Puppet Users] at which size to use a "real" webserver
On Tue, May 3, 2011 at 9:00 AM, joel.merr...@gmail.com < joel.merr...@gmail.com> wrote: > On Tue, May 3, 2011 at 11:21 AM, Andreas Kuntzagk > wrote: > > > 1. minimal Ubuntu install using pxeboot with preseed file (from web-URL) > > I use FAI personally, which enables me to automatically include the > puppet client and kick the 1st run. You could achieve the same thing > with preseed, kickstart etc.. I also use the debianized packages as > gems are a little more difficult to use when bootstrapping imho. > > I also use passenger for *everything* (even testing). It's really > simple to setup, > http://m.etrono.me/posts/5-simple-ish-puppet-infrastructure - a hell > of a lot of this could be puppetified, granted.. > > > > -- > $ echo "kpfmAdpoofdufevq/dp/vl" | perl -pe 's/(.)/chr(ord($1)-1)/ge' > > -- > 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. > > Hi Andreas, Deploying with scaling in mind is the best route at onset. You'll then be able to load test, debug and evaluate _before_ you reach the wall. Which in these days of virtualization can happen between morning and afternoon. -- Cheers, Steven --- Steven Acres UNIX/Linux System Administrator -- 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.
Re: [Puppet Users] scheduling package installs - ignore schedule if not installed
On Thu, Apr 28, 2011 at 3:36 AM, Felix Frank <
felix.fr...@alumni.tu-berlin.de> wrote:
> On 04/23/2011 04:01 AM, Steven Acres wrote:
> > On Fri, Apr 22, 2011 at 2:34 PM, trey85stang > <mailto:trey85st...@gmail.com>> wrote:
> >
> > Is there a way to override a schedule for a package if the package is
> > not installed?
> >
> > class packages {
> > schedule { installs:
> >range => "2-4",
> >period => daily,
> >repeat => 1,
> > }
> > package { openssh:
> >ensure => latest,
> >schedule => installs,
> > }
> > }
> >
> > I dont want to check if openssh is the latest package everytime
> puppet
> > runs; but I do want it installed if it is not already installed
> > regardless of the schedule.
> >
> > Anyway to do this?
> >
> >
> > Hi,
> >
> > Sure, there are many ways to achieve this. You would be better off
> > defining which packages should be present on which nodes in another
> > class. Then use an include in the node(s) definition (or whatever method
> > you have defined for your architecture structure).
> >
> > BTW, if you're using yum and you would like to keep pkgs. updated, you
> > may want to look into yum-cron.
>
> Hi,
>
> I don't agree. Telling puppet to "install at all times but update only
> on a specific schedule" is not trivial if at all possible.
>
> Doing the upgrades outside the package provider may indeed be a sensible
> workaround.
>
> Cheers,
> Felix
>
> --
> 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.
>
> Hi all,
Easy as could be .. simple conditionals and cron, at if we're in the
'old' days .. but since we now have the 'magic' of pkg. managers ... we
manage this effortlessly now. Not only does this free time to catch up on
BOFH ... it also ties into DR, auditing and compliance (i.e. PCI-DSS) which
need to be included and documented in our architectural process/design. The
most time is and should be spent on that design and the rest is primarily
fine-tuning.
--
Cheers,
Steven
---
Steven Acres
UNIX/Linux System Administrator
--
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.
Re: [Puppet Users] scheduling package installs - ignore schedule if not installed
On Fri, May 6, 2011 at 4:23 AM, Martin Willemsma wrote:
> Hi Steven,
>
> Do you mind sharing how you manage this with us here or in some sort of a
> blog post?
>
> Martin
>
>
> 2011/5/6 Steven Acres
>
>> On Thu, Apr 28, 2011 at 3:36 AM, Felix Frank <
>> felix.fr...@alumni.tu-berlin.de> wrote:
>>
>>> On 04/23/2011 04:01 AM, Steven Acres wrote:
>>> > On Fri, Apr 22, 2011 at 2:34 PM, trey85stang >> > <mailto:trey85st...@gmail.com>> wrote:
>>> >
>>> > Is there a way to override a schedule for a package if the package
>>> is
>>> > not installed?
>>> >
>>> > class packages {
>>> > schedule { installs:
>>> >range => "2-4",
>>> >period => daily,
>>> >repeat => 1,
>>> > }
>>> > package { openssh:
>>> >ensure => latest,
>>> >schedule => installs,
>>> > }
>>> > }
>>> >
>>> > I dont want to check if openssh is the latest package everytime
>>> puppet
>>> > runs; but I do want it installed if it is not already installed
>>> > regardless of the schedule.
>>> >
>>> > Anyway to do this?
>>> >
>>> >
>>> > Hi,
>>> >
>>> > Sure, there are many ways to achieve this. You would be better off
>>> > defining which packages should be present on which nodes in another
>>> > class. Then use an include in the node(s) definition (or whatever
>>> method
>>> > you have defined for your architecture structure).
>>> >
>>> > BTW, if you're using yum and you would like to keep pkgs. updated, you
>>> > may want to look into yum-cron.
>>>
>>> Hi,
>>>
>>> I don't agree. Telling puppet to "install at all times but update only
>>> on a specific schedule" is not trivial if at all possible.
>>>
>>> Doing the upgrades outside the package provider may indeed be a sensible
>>> workaround.
>>>
>>> Cheers,
>>> Felix
>>>
>>> --
>>> 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.
>>>
>>> Hi all,
>>
>> Easy as could be .. simple conditionals and cron, at if we're in the
>> 'old' days .. but since we now have the 'magic' of pkg. managers ... we
>> manage this effortlessly now. Not only does this free time to catch up on
>> BOFH ... it also ties into DR, auditing and compliance (i.e. PCI-DSS) which
>> need to be included and documented in our architectural process/design. The
>> most time is and should be spent on that design and the rest is primarily
>> fine-tuning.
>>
>>
>>
>> --
>> Cheers,
>>
>> Steven
>> ---
>> Steven Acres
>> UNIX/Linux System Administrator
>>
>> --
>> 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.
>>
>
>
>
> --
> Met vriendelijke groet,
>
> Martin Willemsma
>
> --
> 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.
>
Hi Martin,
Sure, which process are you referring to?
--
Cheers,
Steven
---
Steven Acres
UNIX/Linux System Administrator
--
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.
Re: [Puppet Users] RHEL 6 Optional channel
On Mon, Jun 13, 2011 at 10:31 PM, Len Rugen wrote: > It looks like all of our RHEL 6 systems now need to connect to the RHN > Optional Channel. (puppet, ruby vs. selinux deps) > > Is there a way to do that with a script without having to enter RHN userid > and password? Is there a way to add a channel during kickstart? > > Thanks > > -- > 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. > Hi Len, https://access.redhat.com/kb/docs/DOC-2475 -- Cheers, Steven --- Steven Acres UNIX/Linux System Administrator -- 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.
