Thoughts on Cobbler authorization/authentication and access levels in your organization?
While things are floating across my mind...
I know I've heard mention of a SQL backend for the configuration.
That's pretty much a requirement for me as I need to duplicate the
service (2 boxes) for that disaster recovery policy. My shared storage
is AFS (mostly) which..well..likes to eat files that two servers/people
are editing at the same time. And bdb just falls on its face. Who
I'm really using Cobbler to glue together a lot of pre-existing
services: profile management, yum repos, web apps that collect/display
status information, etc. Its been fun so far...now to find more time.
Jack Neely <email@example.com>
Linux Czar, OIT Campus Linux Services
Office of Information Technology, NC State University
GPG Fingerprint: 1917 5AC1 E828 9337 7AA4 EA6B 213B 765F 3B6A 5B89
et-mgmt-tools mailing list