On Tue, Apr 10, 2001 at 08:46:10AM -0600, Tony Seward wrote:
> On Tue, 10 Apr 2001, Chris Petro wrote:
> > On Tue, Apr 10, 2001 at 09:18:57AM +0300, Pekka Savola wrote:
> > > On Mon, 9 Apr 2001, Chris Petro wrote:
> > > > Like many medium to large installations, we have some process in
> > > > place to "roll" (i.e. install and configure) machines in an
> > > > automatic or semi-automatic process. Currently we use a combination
> > > > of kickstart and "clustering" scripts to do this. The biggest
> > > > problem we face going forward is organizing and maintaining
> > > > this kickstart system across multiple versions. For security
> > > > and auditing purposes, we would like to have some mechanism in
> > > > place that only installs minimal packages on each machine, with
> > > > different packages--based on cluster or "profile"--placed on
> > > > specific machines.
> > > You could accomplish the "profiles" by creating a group in comps file,
> > > like:
> > > 1 Custom Package 1 {
> > > xxx
> > > yyy
> > > zzz
> > > }
> > > And then in ks.cfg, add:
> > > %packages
> > > @ Custom Package 1
> > No, you can't.
> Yes, you can.
Go back and re-read what I wrote. That doesn't do it.
Using the comps file allows you to choose *different* packages for install,
but must be specified in the ks.config file. What I am going to acheive
is the ability to install different versions as well as different
packages from the same "repository".
This simplifies *many* things, at the cost of some complexity in
the software.
It eliminates dinking around with DHCP configuration files to point to
different ks.config files. It eliminates having to propigate and
syncronize new RPMs across multiple repositories, it provides the
ability to change control the configuration files so you can roll
back to a previous version of the installation set etc.
> > How do I install one version of package <x> on one cluster, and version
> > <y> on another?
> You have different distribution roots on different NFS server exports.
> There may be less space consuming ways. Maybe symlinks in the exported
> directories that point to the pertinent RPM in another directory. Just off
> the top of my head.
Not acceptable. Entirely too maintenance intensive.
> > Then we're probably going to wind up ditching Redhat for something
> > that can support them.
>
> If I'm not mistaken, LVM is in the 2.4 kernel which will be in the next
> release. If you are not that patient, try the beta with updates from
> rawhide. Last I heard reiserfs was not going to be in the RH distro until
> it stabalized to Red Hat's satisfaction. I did, howeverer, find reiserfs.o
> in the kernel I installed from RH's latest beta. Others have had good
> results with XFS. In any case, why not just make a kernel RPM with whatever
> you want included and set up your own RH-based in-house distribution?
It's not the support in the kernel I'm worried about--that I know how to
do, it's the ability to specify the FS on install (i.e. install to a
ReiserFS root partition).
--
Share and Enjoy.
_______________________________________________
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-devel-list
