In the one and only place where EFS 3 currently has a chance of being
used, I have NFSv4 on my radar screen a bit sooner the I had planned,
so I've been doing some work to get the test.efs and boot.efs
environments updated/upgraded. You may have noticed (or not) that
recent commits to efs-utils, for example. Most of that work was to
make it possible to use Debian for the core servers, since we need
more of them in the NFSv4/OpenAFS configuration. I wanted to use
Debian for the simple reason that it has a MUCH smaller memory
footprint than RHEL, and that is now possible for at least test.efs.
The NFSv4/OpenAFS test.efs setup requires a separate VM for each of
the 3 test cells (a.foo, b.foo and p.foo), as well as the 2 VMs that
run the actual test suite. That means you need to run 5 VMs as once,
and 3 of them can now be Debian (although I don't have the OpenAFS
stuff quite done yet -- that's a WIP). Now, the important thing to
point out is that if you have a test.efs environment, you need to
either (a) rebuild your core servers as Debian hosts, or (b) be
prepared to support using a non-Debian core server(s) yourself. IOW,
I am dropping support for non-Debian core, simply because I am not
using them.
I have also successfully run the test suite on the following
platforms, and for each of them, I have a separate pair of VMs:
x86-64.rhel.5
x86-64.rhel.6
x86-64.debian.6.0
x86-64.ubuntu.10.04
x86-64.ubuntu.11.10
It is my intention to ensure that all updates to efs/core/master run
successfully on all 5 of those, going forward. I have not had time
(nor is it a priority) to redo the FreeBSD client, so that is
considered stale at this point (I don't think anyone other than me
every built one anyway).
The boot.efs environment is about to undergo massive changes as well.
I am dropping the use of the efs/core/bootstrap release entirely, and
building all of efs-core, efs-perl and efs-deploy directly into
/usr/efs for use during the bootstrap process. I am changing that
process to include the setup/bootstrap of efs/deploy-site, and the
intention is to set the environment up so that post-bootstrap, you can
start building the content of /efs/dist from scratch. In particular,
I intend to bootstrap the cpan2efs setup so that you can immediately
start building all the CPAN dependencies needed by EFS.
The purpose of doing this is to deal with the fact that the
downloadable content on ftp.openefs.org is VERY stale. We haven't
updated any of that in well over a year and a half (Fall of 2010 was
the last time I was building things on Jerry's boot.efs environment,
which was where ALL of that content came from). As soon as I have my
new boot.efs setup functioning, I intend to start building content for
all 5 of those platforms, as well. Note that when I start doing this,
we will need to make sure that Jerry's environment is setup to NOT
upload, as the upload/download stuff is not designed for multiple
sources (it can and should be, but that's a separate issue). Right
now, you can run "efs_download_content" and you get a lot of very out
of date software. Once I get this up and running, I'll be
maintaining that content using all the new automation I've written.
cpan2efs is done, and working beautifully (I am only about 6 hours
behind the leading edge of CPAN :-), and I have designs for gnu2efs
and apache2efs, among others.
The driver behind this is that NFSv4 and Kerberos support are now a
much higher priority, due to the fact that I've discovered how
impossible it will be to scale the group management in the NFSv3
environment where I am currently building EFS 3. If you think things
were bad an ML/BAC, well... My current environment makes that mess
look downright gorgeous.
When I did the bulk of the OpenAFS support, I also layed the
groundwork for NFSv4, with a lot of code blocks that just do:
die qq{NFSv4 is not yet supported!!\n};
My goal is to get test.efs setup so that you can run the NFSv3, NFSv4
and OpenAFS tests using the same setup (in fact, you already get
/etc/efs/test-nfs.conf and /etc/efs/test-afs.conf when you build
efst01), and once that is stable for the NFSv4 and OpenAFS cases,
revisit boot.efs, and get that extended to support both as well.
Bottom line (if you read this far): if you have a test.efs or boot.efs
setup, you are going to need to rebuild it from scratch in the near
future if you want to continue using it, as the old config will no
longer be supported.
_______________________________________________
EFS-dev mailing list
[email protected]
http://mailman.openefs.org/mailman/listinfo/efs-dev
