On Thu, Jan 13, 2011 at 10:03:40AM -0500, Matt Simmons wrote: > Andrew, > > Once you get this problem out of the way, I cannot recommend learning > how to package RPMs highly enough. I don't compile _anything_ on my > production servers anymore. I create packages on a development > server, test them on workalike servers, install the packages into an > internally-hosted repo, then use yum to install them from the repo. > > I'm not even great at it yet, but it has already saved me a ton of work.
I cannot stress enough how valuable this procedure is for ensuring repeatability of deployments and easing management nightmares. We, too, use internal repos for yum on our production systems, and have a whole host of build hosts living as VMs on Xen for creating the packages (one build host per OS flavor/bitness). For bonus flexibility, put your repos and RPM build tree on NFS shares, and your RPMs can get dropped directly into your repos if they build. Since we have dedicated built hosts for each OS variant, and a dedicated "rpmbuilder" user account we sudo to built with, .rpmmacros can be tuned to do this for you. Then all you have to do is rebuild the repo indexes and you're off to the races. This lets us confine all of our building and experiementation to one place, and ensures that we can deep as many unnecessary packages off of our production servers as possible. Gregory -- Gregory K. Ruiz-Ade <g...@unnerving.org> OpenPGP Key ID: EAF4844B keyserver: pgpkeys.mit.edu _______________________________________________ Tech mailing list Tech@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
