SCIENTIFIC-LINUX-USERS Archives

April 2005

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Bly, MJ (Martin)" <[log in to unmask]>
Reply To:
Bly, MJ (Martin)
Date:
Fri, 29 Apr 2005 08:37:57 +0100
Content-Type:
text/plain
Parts/Attachments:
text/plain (67 lines)
Some of my colleagues have developed a system called yumit - uses the o/p from yum and a mysql database to keep track of what's needed on our systems at any given time.  

C.f: http://www-staff.esc.rl.ac.uk/Romain/yumit/

We have 600+ systems monitored this way.

Martin. 

-----Original Message-----
From: [log in to unmask] [mailto:[log in to unmask]] On Behalf Of Michael Mansour
Sent: Friday, April 29, 2005 12:54 AM
To: Connie Sieh
Cc: Todd Blake; [log in to unmask]
Subject: Re: yum vs. up2date?


Hi Connie,

> > Hi Connie,
> > 
> > > > root@radon# up2date -l
> > > > 
> > > > Fetching Obsoletes list for channel: scientific-base...
> > > > 
> > > > Fetching Obsoletes list for channel: scientific-errata...
> > > > 
> > > > Fetching rpm headers... ########################################
> > > > 
> > > > Name                                    Version        Rel
> > > > ----------------------------------------------------------
> > > > cvs                                     1.11.17        7.RHEL4       
   i386
> > > > devhelp                                 0.9.2          2.4.4         
   i386
> > > > mozilla-nspr                            1.7.7          1.4.2             i
> > > >
> > > 
> > > We  only made this to work for the case were up2date got turned on
> > > by default to handle the "automatic" update.  We did not want it 
> > > trying to contact redhat.
> > > 
> > > -Connie Sieh
> > 
> > I'm starting to look at:
> > 
> > http://current.tigris.org/
> > 
> > which seems to make use of up2date but without the restrictions of 
> > using the RHN network. It seems to facilitate my need to update 
> > multiple systems.
> 
> What feature do you need?

I need a way where I can "view" or know about the updates required on each of my servers, like a "snapshot view" of current states of all servers.

I run various SL and FC machines. At the moment, I have yum repos setup on all these machines, and as they differ by distribution, so do the repos they check. For example, the repos I use are SL, Dag, ATrpms, Freshrpms and these differ for SL3, SL4, FC1, FC2, FC3. Although my intention is to abandon FC releases altogether and move them all to SL, while I organise this I still have to keep them up-to-date.

Currently I run a "yum check-update" each night on each server, and have that output emailed to me each day, which I go through each morning. So in addition to the multiple repos, I receive a considerable  amount of emails which I go through. And because the output of "yum check-update" also produces a list of updated packages I don't care about, I'd also like a way to monitor if particular packages have been updated on particular servers which have those packages installed.

There currently doesn't seem to be any easy way to do this.

I have used up2date and RHN before and it's pretty good, but limited to RHN (even when making you own up2date server).

"current" seems to be the answer for me, although not meeting every single requirement I have above, would seem to be better than the method I have now.

Michael.

ATOM RSS1 RSS2