[Infrastructures] Recommended CVS heirarchy?

[Ryan Nowakowski]

--BOKacYhQ+x31HxR3
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Feb 24, 2003 at 05:24:18PM -0600, Luke A. Kanies wrote:
> On Mon, 24 Feb 2003 wcooley@nakedape.cc wrote:
>=20
> > I'm finally getting around to implementing a partial infrastructure for=
 a
> > site with two boxes and am setting up CVS.  Is there a recommended
> > heirarchy?  The repository will be chiefly local configuration files (in
> > /etc and other places) which are host-specific and scripts in /usr/loca=
l,
> > which are more or less portable (or at least, won't harm anything by be=
ing
> > on both), so I was thinking of:
> >  o common/bin, common/man, common/sbin, etc
> >  o hosts/host1/etc/foo, hosts/host2/etc/bar, etc
> >
> > Is there a recognized BCP I should follow instead?
>=20
> Well, mine's just what works for me, but I have three basic directories in
> CVS:
>=20
> filesets/
> code/
> config/
>=20
> The 'filesets' directory is where I keep the files that are to be
> downloaded to the various systems.  These would be my oracle configs, my
> motd files, my resolv.conf files, that kind of thing.  The 'filesets'
> command in ISconf 3 then just pulls these down over rsync.
>=20
> In the 'code' directory, I keep scripts; mainly locally developed perl
> modules and a unified scripts directory to copy everywhere.  These are
> separated largely for maintenance, not because they are treated
> significantly differently.
>=20
> In the 'config' directory, I currently only have my cfengine configs,
> although I'd like to move my ISconf configs in there, too, so that the
> ISconf code (which isn't updated very often) is treated separately from
> the ISconf config info (which changes very often; my types file is beyond
> 450 versions now).

We have a similar hierarchy except we don't separate our filesets from
code or config.  Here's my top level:

application/
domain/
model/
common/
host/
platform/

=46rom there, application is just like Luke's.  All our separate domains
are under the domain module for organizational purposes.  The 'common'
module is mainly just the isconf code itself.  Under 'host' we have any
host specific configs.  Under 'model' we have configs that are hardware
specific.  Our 'platform' module is stuff that is OS specific (we run
Solaris Sparc and Solaris Intel).

- Ryan

--BOKacYhQ+x31HxR3
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)

iD8DBQE+W7Aq6ZA8+1/wXqMRAiKiAJ9CeGFhRgWxYcBGiuimHeLjqq+RogCgoOqb
R6aBr92bNlrrvxEjH9y9WyM=
=Zk2q
-----END PGP SIGNATURE-----

--BOKacYhQ+x31HxR3--