Login | Register
My pages Projects Community openCollabNet

Discussions > dev > New Directions for Current

Project highlights: Stable Version: 1.6.1, Development Version: 1.7.6

Discussion topic

2020-04-07: This site is going to be decommissioned and shut down on 2020-07-01. Please copy and archive any data you wish to keep before that date.

Hide all messages in topic

All messages in topic

New Directions for Current


Author theslack
Full name Jack Neely
Date 2005-07-20 15:01:45 PDT
Message Folks,

First off I am working on getting a 1.6.1 version out the door
hopefully this week. This will include some minor bug fixes that have
been in Issuezilla.

I am going to start focusing Current in a slightly different
direction. I've talked to Hunter a lot about this and I've got some
thoughts outlined in my blog (http://linuxczar.blogspot.com). Up
until now I have been pretty much aiming at making Current an
RHN-alike. RHN is basically the only example I have to follow.
However, I think that is the wrong direction for the project.

I have been searching and thinking about what I call an Advanced
Management System. A system that is to administrating Linux machines
as Up2date/Yum is to deploying updated packages. With RHN running
up2date and managing RPMs is most of the functionality. I do not
believe Current should focus so heavily on installing package foo on
machine bar. Rather, you want to make machine bar be a workstation or
NFS server, or some other task. The idea is to create a system that
can manage thousands of Linux machines remotely. This aims to replace
the cron jobs or cfengine stuff that every site has.

See the blog for a good bit of thinking.

The first steps to this goal is to add support for Yum's repository
format. Current still maintains knowledge of the packages in the
channels to support the RHN API and to provide additional
functionality down the road. An Agent needs to be written that runs
on Yum clients, logs into Current, polls for information, etc. Of
course, this takes us very quickly to Actions which will probably be
based off the RHN Action API.

I invite you folks to question my sanity. :-)

Jack Neely
Messages per page: