[Spacewalk-list] Assigning packages to a group

[Colin Coe]

Hmm, ISWYM.

My take on this is that groups is the wrong place to do this.  For
example, at a previous site we had groups for distro version
(RHEL3,4&5), arch (i386, x86_64) and role (workstation, HPC node,
server). All machines were in at least these groups.  My workstation
was in the workstation, x86_64 and rhel5 groups.

So, I get what you're saying, just having troubles imagining how this
could be done sanely with groups.  It needs to be remembered that
while we all use the Spacewalk/Satellite features (like groups and
custom info keys), we use them differently in a lot of cases.  How
stuff gets implemented needs to bare this in mind.

Just my 0.015 cents (and with KRudd at the helm, it'll be worth even less soon).

CC

On Fri, May 21, 2010 at 7:07 PM, John Hodrien <J.H.Hodrien at leeds.ac.uk> wrote:
> On Fri, 21 May 2010, Colin Coe wrote:
>
>> Can you not have a software channel with the alpine RPM and subscribe
>> 'Group A' systems to said software channel?  That way they'll get
>> updates to the package as well.
>>
>> I'd use the activation key as well.
>
> Have a group gets you updates, but it doesn't get you additions.
>
> So you end up having to add package X to the activation key, and doing an
> install to all machines in the group.  It'd be quite nice if there was an
> easy
> way of doing that.  Something like System Groups, Packages, Add Packages,
> IYSWIM.  Then you'd just have to add the package to the group, and it'd be
> installed on all machines in the group and on any new members to the group.
>
> jh
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
>



-- 
RHCE#805007969328369