[: Re: [Infrastructures] how to build an internal (local) file structure?]

[Rudy Gevaert]

[I have some questions at the bottom of my mail]

On Thursday 24 March 2005 20:28, dsr-infra@tao.merseine.nu wrote:
> So, you might want:
>
> /COMPANY/MACHINECLASS/bin|etc|lib|var
>
> And you might, potentially, want a particular MACHINECLASS to be
> "standard" or "common", put it on every machine, and keep things
> there that every machine will need.


I think one should make the difference between machine class and
architecture.

I see it like this (or rather a way to do it would be):

company/
`-- apps
    |-- app1_v1
    |   |-- bin.i386
    |   |-- bin.sparc
    |   |-- etc
    |   |-- lib.i386
    |   |-- lib.sparc
    |   |-- sbin.i386
    |   |-- sbin.sparc
    |   |-- share
    |   `-- src
    |-- app1_v2
    `-- app2_v1


Here you keep all application dependant files in a directory.  Also
you can keep several versions of an application.  Per version
configuration files and shareable files are the same for all
architectures

I would then suggest setting up 'farm link' per machine class.

Links for a i386 machine would be:

/bin/app1 -> /company/apps/app1_v2/bin.i386/app1
/etc/app1/ -> /company/apps/app1_v2/etc/

If you have several machine classes you can set them up according to
your needs.


I do have some questions:

- AFS seems a very good way to set up the fileserver put everything in
  /afs/comanpy.com/  

- what with NFS?  It isn't good practice to mount NFS shares on top of
  each other. It is clear that you can't keep /company on one machine
  for ever.  

- do mount the whole /company on each machine?  With AFS you can set
  up the right rights.  But NFS is trickier.

- how do implement the symlink farm?  CFengine seems good to me.  

Thank you for your time,

Rudy