The gnu* machines are a *.boot.efs setup, and that's similar to, but very different from, *.test.efs.
The boot.efs setup has always used real NFS. When you created real volumes, you were just changing how the NFS server manages it's data locally, but that data was always served out to the other machines via NFS. What I'm changing is how we built test.efs only, so that we start using real distributed filesystems in the test suite finally. test.efs is going from nothing to using both NFS and AFS. The changes to boot.efs will be to add AFS services to the existing NFS services we've been creating up to this point. Hope that clarifies things. On Thu, Sep 30, 2010 at 10:17 AM, David A. Desrosiers < [email protected]> wrote: > On Thu, Sep 30, 2010 at 10:09 AM, Phillip Moore > <[email protected]> wrote: > > I am going to be making MAJOR changes to the test.efs environment as part > of this work, so be prepared to completely rebuild your from scratch when > this is ready in a week or two. I'm going to change the "function" names of > the various servers, and their IP addresses, which will make the existing > test.efs setups obsolete. > > If you're referring to a standalone test setup, unrelated to our own > independent VMs, then blast away... but remember, the gnu* machines > are using REAL NFS now, since I created /efs/dist and /efs/dev as > actual external storage volumes, exported via NFS... but I can blow > them away and start over from scratch to do it again as needed, of > course. > > Originally, that's what my setup started as, years ago. I was > NFS-mounting developer's $HOME into each VM (auth creds are in LDAP), > so they could build and test their projects and code in each new > distro as they became available. > > Each distro was a different incoming ssh port, so the developers could > ssh to port 12345 and get Debian 4.0, 12346 and get Debian 5.0, 12347 > and get FreeBSD 6, 12348 and get FreeBSD 7, and so on. > > The code in $HOME remained exactly the same, and their local cvs/svn > checkouts to $HOME/Projects was where they maintained and manipulated > their code. It was quick and easy to set up. > > I'm sure converting that knowledge to how we'll want to do something > similar with EFS 3.x/OpenAFS should be straightforward as well. > _______________________________________________ > EFS-dev mailing list > [email protected] > http://mailman.openefs.org/mailman/listinfo/efs-dev >
_______________________________________________ EFS-dev mailing list [email protected] http://mailman.openefs.org/mailman/listinfo/efs-dev
