GitLab

obscure errors since we allow the path to be set to null. Setting the
path to null via the web page is probably not a good idea, but I just
did that by accident and noticed what happened ...

too!

and the different names we put into /etc/hosts

acually do it now.

reason for adding this is that it gets in the way of the 'full'
testsuite tests. Also, it may be used at sites (like gatech), that
aren't using a subdomain for their emulab, and thus can't set up
names for one.

command line.

addition to physcial ones.

Change the testsuite to use this option, so that 'full' mode can be
used on widearea nodes.

Also, allow the testsuite to match against node classes in addition
to types.

experiment. Here is mail to tbops:

* Moved the working directory for experiment setup/swap/end to a new
  directory located on boss instead of over NFS to /proj/$pid/$eid. This
  new location is /usr/testbed/expwork/$pid/$eid.

* Changed the name of the directories we create in /usr/testbed/expinfo to
  $pid-$eid.$index where $index is a new autoincrement field in the DB
  table. I really hated the names that were created before.

* Changed where logs are written from /tmp to the new location in
  /usr/testbed/expwork/$pid/$eid.

Okay, why.

* We no longer operate on NFS mounted directories that might hang. Its
  easier to catch the situation where a copy of the log file over at the
  end of experiment creation fails cause of an NFS problem.

* We no longer have user writable files that are inputs to other parts of
  the system (like top and ptop files).  Not that a user would be bad, but
  it closes a hole.

* We no longer copy user writable files from /proj to boss where we might
  fill up an important filesystem cause the user put a .ndz file in the the
  working directory. Not that a user would be bad, but it closes a hole.

* Its easier to save all the log files this way, for each swap in and
  out.

* Removing a directory over NFS is a royal irritant when someone is CD'ed
  into that directory or looking at a file on the other side (the astute
  observer will peg this as the reason I went down this idiotic path in the
  first place!).

* About 6 other reasons that I can no longer remember. Seriously, I really
  had more reasons I can no longer remember! :-)

in PHP. The astute observer will notice the web pages seem a little
faster now ...

Based on testing, this limit should never be exceeded using NetBuild.

eventsys_start: set both project and group GID, don't consider emulab-ops

on boss are the best 'documentation' of the firewall rules. Update
setup-network.txt to reflect this.

Also fixed up some stuff in setup-network.txt that we listed as
alternate, untried, configurations. In fact, we use them now, and
they are the recommended way to do things.

after forking

is installed on ops. Makes the use of SFS more explicit, which is
good.

Minor bugfix to make sure guids are always positive
(so regexp in php doesn't reject it.)

dead before it flows 32 bits.

Changed /tmp file saving to be based on a randomly generated number,
not UID. This way, POSTing NSFiles from netbuild doesnt require being logged
in (since Macs dont seem to want to send the appropriate login cookies
along for the Java POST.) This should fix the Mac OS X problem.

Maintained backward compatability with old methods.

the drivers loaded)  This leaves all unused interfaces "UP" but with no
inet info, hope this is ok...

look polka-dotted.

rc.ifc uses it unconditionally so it needs to exist.

home without worrying about ssl/capserv/acl stuff.

instead of links to the pid directory, just point to the top level
project directory. Its all there anyway. Ditto for groups. Note, this
has the nice side effect that /proj/.sfs exists everywhere, and so the
certprog returns good info no matter where you are!

prevents us from running the testsuite if we are just using the
prebuilt assign binary.