[Spacewalk-list] Assigning packages to a group

[Mike Hanby]

So far as multiple users editing configurations, not really other than using group permissions or ACL on the puppet manifests.

I keep all of my puppet configuration files in subversion so that we can back out any changes that don't work :-)

Regarding the group package assignment, here's what I do.

Create a class for the group, say el5_workstation, that defines the packages that you want, among other configurations specific to EL5 workstations:

cat /etc/puppet/manifests/classes/el5_workstation.pp

class el5_workstation {
  # These packages should always be the latest
  package {["openssh", "openssh-server", "openssh-clients"]:
     ensure   => latest,
  }

  # These packages should always be installed
  package {["inkscape","rhythmbox","cadaver","ImageMagick","emacs","pigin"]:
     ensure   => installed,
  }

  # Make sure sshd is running
  service { "sshd":
     enable => true,
     ensure => running
  }
}

Create one for each group. You can also do multiple releases in a single class using case statements.

Then, inside your node definition just include that class. Say for example my wks-01 node:

vi /etc/puppet/manifests/nodes.pp

node 'wks-01' {
   include baseclass # configs that all systems must have
   include spacewalk_client
   include el5_workstation
   include puppet_client
}

I agree, having this functionality inside of spacewalk would be great :-)

-----Original Message-----
From: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Daniel Wittenberg
Sent: Friday, May 21, 2010 11:32 AM
To: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] Assigning packages to a group

There are a couple web gui's for puppet as well, I've been playing around with them but don't have the URL's handy at the moment, but that might work too ?

Dan

On May 21, 2010, at 11:27 AM, Edward Simmonds wrote:

> Mike Hanby wrote:
>> I'm enjoying the discussion so far.
>> We handle this type of scenario using Puppet. The machines get the packages and updates from Spacewalk with Puppet telling them which packages to get and whether or not they should always be at the latest version.
>> Perhaps this capability could be part of the Puppet entry in:
>> https://fedorahosted.org/spacewalk/wiki/TheRoadmap#FutureIdeas
> 
> We've considered this, and I just started figuring out how to do this with Puppet a few minutes before I saw your response.  I was hoping to do this with Spacewalk because it will give us the ability to assign groups of machines to certain people and give them a nice GUI to do RPM management.  I'm sure we can hack something together with Puppet as well, but it won't have the visual advantages of Spacewalk for folks that aren't fond of the command line.
> 
> Do you have any tips or tricks for using Puppet to do this?
> 
> Best,
> 
> Ed
> 
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list


_______________________________________________
Spacewalk-list mailing list
Spacewalk-list at redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list