GitLab

with no other stuff on page. Notes:

* I added a new building called MEB-ROBOTS cause otherwise it would
  show up on the wireless maps since floormap gets all the floors for
  a building. Need to add type tags someplace, but not sure where yet

* I committed Russ' initial jpeg image to use in the floorimages
  table. Russ can replace that when he generates a better looking
  version.

* I linked the robots map in from the node status page ...

version of database-fill.sql

More sockets and integration

* Always run assign_wrapper using -t mode. This just runs the top file
  stuff, and writes the min/max nodes into the DB.

* Then look at the security level for the experiment, and if orange or
  red, create a parallel elabinelab experiment to run it in. This is a
  completely new experiement in addition to the original. The two
  experiments are linked with some DB state so we know what experiment
  to fire off inside the inner elab. I am using a template NS file and
  passing in the number of nodes computed in the previous step above.
  The template includes the firewall rules.

  This is quote hokey. It should be more invisible to the user.

  I have not dealt with yellow (just a firewall).

* I added some stats code so that we update the experiement_stats
  record with the elabinelab status and security level.

* Cleanup how errors were handled and get rid of silly duplicated
  code.

utility functions, which do the obvious stuff.

Command line tools for the robot protocol:

	* configure, configure.in: Add the robots GNUmakefiles.

	* robots/mtp/GNUmakefile.in: Add command line tools: mtp_send and
	mtp_recv.

	* robots/mtp/mtp.c: Make readall return an error if all of the
	data wasn't read instead of making the caller check.  Free the
	buffer allocated in mtp_send_packet.  Add an mtp_free_packet.

	* robots/mtp/mtp_recv.c: Faux receiver of mtp packets, it doesn't
	actually follow the protocol, it just prints out whatever it
	receives.

	* robots/mtp/mtp_send.c: Command line tool for sending mtp
	packets.

are setup with static routing/ifconfig by adding proper goo to rc.conf.
Previously, I was asking outer boss on each bootup, but this approach is
unworkable in a firewalled setting.

  utility script to wait for them to reboot and reach PXEWAIT. This
  indicates inner emulab is raelly ready

* When an inner experiment is defined (elabinelab_eid in experiments
  table) fire that experiment off by doing an ssh into inner boss. I
  am currently doing this with -w (wait mode) but eventually will need
  to do it async for experiments in which the control net is turned
  off. Also, not actually swapping experiment in yet since multicast
  and frisbee are still broken inside.

* Add -k mode for cleaning up. The intent of this is to avoid power
  cycling all the nodes cause outer elab cannot reboot or ipod them.
  Goes like this:

  * Clear the inner_elab_role for experiment's nodes from the reserved
    table.

  * Clear def_boot_osid,next_boot_osid,temp_boot_osid for nodes. This
    is bogus cause os_select whines about doing this, but the point is
    to make sure that all nodes will go into PXEWAIT when they reboot.
    We could have them go into MFS, but thats bound to cause problems
    if inner elab has a lot of nodes (remember, cannot trust what is
    on disk). This needs more thought.

  * Regen and restart outer dhcpd. Nodes will become part of outer
    emulab on next boot cycle.

  * SSH into inner boss and kill inner DHCPD so that there will not be
    any DHCPD responses on inner control network.

  * SSH into inner boss and have it reboot all inner nodes.

  * Wait for node to reach PXEWAIT.

  The above needs more thought wrt firewalled experiments and isolated
  control network.

* Kill off some old MFS copy code since we now get those direct from
  website.

that the firewall rules are preventing essential communication and causing the
failure, so don't retry.

We should probably only do this if the user has specified additional
firewall rules.  But right now, I may screw up the default rules too!

Made a pass over the mtp directory:

	* GNUmakerules: Add a "check" target that runs the executables
	listed in the "TESTS" variable.

	* robots/GNUmakefile.in: Add "mtp" to the list of SUBDIRS.

	* robots/mtp/GNUmakefile.in: Testbed-friendly makefile.

	* robots/mtp/mtp.h, robots/mtp.c: Tweaks and bug fixes.

	* robots/mtp/mtp_test.c: Test case for mtp stuff.

the inner boss/ops setup (route to outer boss, ifconfig of inner
control network). At some point drop this entire script and just use
the XMLRPC interface to tell outer emulab that inner boss/ops have
rebooted and are ready.

of virt_nodes table.

	tb-set-security-level Green|Yellow|Orange:Red

Also add a template elabinelab.ns file.

of virt_nodes table.

of virt_nodes table.

option. New code there coordinates (I hope) the reboot, dhcpd config
regen, and experiment teardown, in the hopes of avoiding numerous
power cycles.

cleanup that the code copies various bits to the reserved table.

(real reboot, not bootinfo requery) nodes. I'm using this to move
nodes in PXEWAIT back to outer emulab, thereby avoiding power cycle of
all inner testnodes.

emulab by waiting for them to reach PXEWAIT. At that point, the inner
emulab is ready to go and we can launch an experiment.

Minor additions to support node mobility events:

	* lib/libtb/tbdefs.h, lib/libtb/tbdefs.c, sql/database-fill.sql:
	Add SETDEST as an event type and NODE as an object type.

	* tbsetup/ns2ir/node.tcl:
	Add location (X_, Y_, Z_) and orientation attributes for mobile
	nodes.

	* tbsetup/ns2ir/sim.tcl:
	Add a "setdest" event for node types that lets the user move a
	mobile node.

snmpitDoIt(), or zeros and/or empty strings look like failure.

returning 0.

trunk.

every new user during a elabinelab setup. Save it all for the end.