Both options we've looked at and unfortunately, cannot use due to security restrictions. Instead of cfengine we use Cendura Cohesion ( recently aquired by CA ) for our configuration management. Right now I'm only dealing with RHEL systems but we have a mix of RHEL, AIX, Windows and some Solaris and Cohesion had agents for all of those. I haven't heard of puppet, so I'll take a look at that. Alot of the difficulty in our situation stems from the multiple tiers that are unable to communicate with each other, thus resulting in having multiple servers of any type ( ie - 2 DNS servers per tier, 1 yum repos per tier, a kickstart server per tier), none of which are able to use a centrally managed machine to replicate from for all of their configs and ata. Add ontop of that the fact that many of these tiers have no internet access and you only see the tip of the iceberg. The config RPMs were considered because they're easy to generate out of our SVS and easy enough to replicate to the kickstart/yum repos in each tier manually. I'm also trying to get webjob ( http://webjob.sourceforge.net ) implemented as a tool for RPM installation and other adminstrative tasks, but that's a whole other battle. Again, I appreciate everyone's input on this. -- sh -----Original Message----- From: rpm-list-bounces@xxxxxxxxxx [mailto:rpm-list-bounces@xxxxxxxxxx] On Behalf Of Tim Mooney Sent: Thursday, November 15, 2007 1:59 PM To: RPM Package Manager Subject: Re: RPM - Preventing uninstall and file conflicts. In regard to: Re: RPM - Preventing uninstall and file conflicts., Paul...: > On Nov 14, 2007 1:22 PM, Hajducko, Steven > <steven.hajducko@xxxxxxxxxxxxxxxxxx> wrote: >> > >> >> What we'd like to do is create RPM's for each set of tier >> configuration files. So I'd like to have my >> 'configs-web-production-1.0.0' RPM with /etc/hosts.allow, /etc/hosts, >> etc and then we simply install the correct tier RPM for any given >> system, depending on which tier the system resides in. As a side note, all these systems are either RHEL3 or RHEL4. > > I've been there too, and asked a lot of questions, eventually gave up > trying to replace config files like that. I got a lot of suggestions. > Maybe the best was to set up a CVS server and have systems update > those config files against it. But I didn't do it because it's easier > to just re-make the RPMS I need and distribute them than it is to hack > up a config rpm. Using a repository and a pull mechanism will work, but you might have better luck using a host configuration management system. The one that's probably the most well-known is cfengine, but I would suggest you have a look at some of the other options, especially puppet. Since all the systems are RHEL, you may also want to consider Red Hat Network. There's an option available for it (I think it's the "Management" entitlement) that allows some host configuration management functionality. Tim -- Tim Mooney mooney@xxxxxxxxxxxxxxxxxxxxxxxxx Information Technology Services (701) 231-1076 (Voice) Room 242-J6, IACC Building (701) 231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
