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
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
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 c
On 21 May 2010 16:27, James Hogarth wrote:
> Hi all,
>
> I'm in the process of converting some VMware guests into KVM guests at
> the moment.
>
> These guests were already managed under spacewalk but as they were
> vmware machines they were considered normal systems.
>
> A freshly built system usi
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
Hi all,
I'm in the process of converting some VMware guests into KVM guests at
the moment.
These guests were already managed under spacewalk but as they were
vmware machines they were considered normal systems.
A freshly built system using a kickstart marked as a kvm virtual guest
shows after bu
John Hodrien wrote:
On Fri, 21 May 2010, Colin Coe wrote:
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
On 05/21/2010 01:50 PM, James Hogarth wrote:
2010/5/21 Miroslav Suchý:
On 05/21/2010 12:46 PM, Miroslav Suchý wrote:
I'm not sure if server send for repodata Last-Modified header. I had to
check it, but I doubt it is send.
I was wrong. Server *send* Last-Modified header.
So we can lower tha
2010/5/21 Miroslav Suchý :
> On 05/21/2010 12:46 PM, Miroslav Suchý wrote:
>>
>> I'm not sure if server send for repodata Last-Modified header. I had to
>> check it, but I doubt it is send.
>
> I was wrong. Server *send* Last-Modified header.
> So we can lower that percent.
>
> --
> Miroslav Suchy
On 05/21/2010 12:46 PM, Miroslav Suchý wrote:
I'm not sure if server send for repodata Last-Modified header. I had to
check it, but I doubt it is send.
I was wrong. Server *send* Last-Modified header.
So we can lower that percent.
--
Miroslav Suchy
Red Hat Satellite Engineering
_
On 21 May 2010 12:41, Milan Zazrivec wrote:
> On Friday 21 May 2010 12:08:19 James Hogarth wrote:
>> On 21 May 2010 10:45, Milan Zazrivec wrote:
>> > On Friday 21 May 2010 11:25:26 James Hogarth wrote:
>> >> On 21 May 2010 10:21, Milan Zazrivec wrote:
>> >> > On Friday 21 May 2010 11:05:08 James
On Friday 21 May 2010 12:08:19 James Hogarth wrote:
> On 21 May 2010 10:45, Milan Zazrivec wrote:
> > On Friday 21 May 2010 11:25:26 James Hogarth wrote:
> >> On 21 May 2010 10:21, Milan Zazrivec wrote:
> >> > On Friday 21 May 2010 11:05:08 James Hogarth wrote:
> >> >> On 20 May 2010 10:32, James
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,
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 y
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.
CC
On Fri, May 21, 2010 at 6:43 PM, John Hodrien wrote:
> On Fri, 21 May 2010, Benedetto Va
On 05/21/2010 11:23 AM, James Hogarth wrote:
2010/5/21 James Hogarth:
2010/5/21 Miroslav Suchý:
On 05/20/2010 03:46 PM, James Hogarth wrote:
up until I get in the office tomorrow and can pull
some logs to get a better picture but putting it out there now in case
anyone sees similar
Sin
On Fri, 21 May 2010, Benedetto Vassallo wrote:
Def. Quota Edward Simmonds :
I must be missing something, but here's what I need to do:
I need to be able to register a client with Spacewalk, assign it to
a group, and have a set of packages assigned to the group. For
example, let's say I wa
On 21 May 2010 10:45, Milan Zazrivec wrote:
> On Friday 21 May 2010 11:25:26 James Hogarth wrote:
>> On 21 May 2010 10:21, Milan Zazrivec wrote:
>> > On Friday 21 May 2010 11:05:08 James Hogarth wrote:
>> >> On 20 May 2010 10:32, James Hogarth wrote:
>> >> > On 20 May 2010 09:50, Milan Zazrivec
Def. Quota Edward Simmonds :
I must be missing something, but here's what I need to do:
I need to be able to register a client with Spacewalk, assign it to
a group, and have a set of packages assigned to the group. For
example, let's say I want all members of "Group A" to get the alpine
On Friday 21 May 2010 11:25:26 James Hogarth wrote:
> On 21 May 2010 10:21, Milan Zazrivec wrote:
> > On Friday 21 May 2010 11:05:08 James Hogarth wrote:
> >> On 20 May 2010 10:32, James Hogarth wrote:
> >> > On 20 May 2010 09:50, Milan Zazrivec wrote:
> >> >> On Wednesday 19 May 2010 23:32:06 J
On 21 May 2010 10:21, Milan Zazrivec wrote:
> On Friday 21 May 2010 11:05:08 James Hogarth wrote:
>> On 20 May 2010 10:32, James Hogarth wrote:
>> > On 20 May 2010 09:50, Milan Zazrivec wrote:
>> >> On Wednesday 19 May 2010 23:32:06 James Hogarth wrote:
>> >>> KVM host is fully updated Centos 5.
On Friday 21 May 2010 11:05:08 James Hogarth wrote:
> On 20 May 2010 10:32, James Hogarth wrote:
> > On 20 May 2010 09:50, Milan Zazrivec wrote:
> >> On Wednesday 19 May 2010 23:32:06 James Hogarth wrote:
> >>> KVM host is fully updated Centos 5.5
> >>>
> >>> Spacewalk instance is a fully update
On Fri, May 21, 2010 at 05:24:18PM +1000, McLeod, Matt wrote:
> I'm running 0.8 on CentOS 5.4 with Oracle XE. The database doesn't seem
> to have maxed out yet (it's at ~3.3GB) and I'm not getting anything that
> looks like an error message.
>
> Ever since the daily spacewalk-sync cron job update
On 20 May 2010 10:32, James Hogarth wrote:
> On 20 May 2010 09:50, Milan Zazrivec wrote:
>> On Wednesday 19 May 2010 23:32:06 James Hogarth wrote:
>>> KVM host is fully updated Centos 5.5
>>>
>>> Spacewalk instance is a fully updated spacewalk 1.0 (with cobbler
>>> 1.6.6 not 2.0.3) on centos 5.5
On 21 May 2010 08:24, McLeod, Matt wrote:
> I'm running 0.8 on CentOS 5.4 with Oracle XE. The database doesn't seem
> to have maxed out yet (it's at ~3.3GB) and I'm not getting anything that
> looks like an error message.
>
> Ever since the daily spacewalk-sync cron job updated the CentOS 5 base
On 05/20/2010 03:46 PM, James Hogarth wrote:
up until I get in the office tomorrow and can pull
some logs to get a better picture but putting it out there now in case
anyone sees similar
Since upgrading to spacewalk 1.0 it has become a much more common
occurrence to find clients on the far
I'm running 0.8 on CentOS 5.4 with Oracle XE. The database doesn't seem
to have maxed out yet (it's at ~3.3GB) and I'm not getting anything that
looks like an error message.
Ever since the daily spacewalk-sync cron job updated the CentOS 5 base
channels to 5.5 I've been seeing unexpected behavior
27 matches
Mail list logo
