Indeed. Perhaps I can explain a bit better. Current has nothing to do with the CentOS/RedHat/ForPay whatever. I don't care how you get or make your packages and Current does not help you violate your licenses with Red Hat / RHN.
But, CentOS + Yum is a good example. Most any RPM based distribution can do automated package deployment with Yum. It is indeed a great tool. But its time to step beyond what Yum does. * Many organizations maintain RPMs that can't be distributed. Licensing concerns, config files, hard coded passwords, or whatever the reason. The only way to provide access controls with Yum is to use apache's allow/deny rules. Not very flexible. RHN/Up2date employ strong authentication which needs to be brought to the open source community so that anyone may use those features. Current can bring those features to Yum. * So you have CentOS deployed and updating from your local Yum repository/server. How do you manage that? Do you grep the apache/ftp logs to check the number of clients you have, what clients were not able to run updates, or maintain any kind of statistics? Current is poised to bring these features to the open source community. * Scalability. You seem to have some familiarity with RHN and you probably know that it doesn't scale to large institutions well at all. I have several plans that I hope will make Current much more scalable. Features to allow management or software acquisition personnel to monitor usage. Features that allow an administrator to be only see and work with their machines but not take away access to all the advanced features as RHN does. How would it benefit you to be able to modify the Yum configuration, available repositories, and installed package sets without having to login to each server and manually make changes or run a hacked up script? Jack On 9/12/06, ltbarcly <[EMAIL PROTECTED]> wrote: > > I was a little harsh there, sorry ! > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears -~----------~----~----~----~------~----~------~--~---
