[Yum] "Approval" process for automated Yum updates

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 2004-06-22 at 13:25, Alan Sparks wrote:
> Does anyone know of any projects to "semi-automate" network Yum
> updates?  I mean "semi" in terms of approvals.
> 
> I have local rsyncs of updates, as well as my own local repositories. 
> I'd like to automate Yum updates across the network, but I'd like to not
> have the updates applied unless they are "approved" first.
> 
> I'd like to see a means where the headers are not seen by the machines
> unless some manual intervention occurs.  Optimally, I'd like to create
> groups of machines (production, development, test) and be able to
> release the files to the population in a controlled fashion.
> 
> I suppose it could be done by separating the rsync repositories from my
> "live" ones, and moving/symlinking and yum-arch'ing the "approved"
> updates to the "live" repositories.  Just wondering if anyone knew of
> better ways.

yum-arch takes a -x to exclude things.
you could implement it that way.

but you'd be best off maintaining two repos, one as final, one as
testing, then using a cgi as your baseurl.

it could redirect cleanly to the right one.

-sv



[Index of Archives]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux