GitLab

hopefully understand as First and Last name!

The new -b option gives you a string with the current status of a
port (ie. if it's enabled, and which VLAN it's in). After getting
this string, you can then modify the port (change its VLAN, enable it,
whatever). Then, when you're done, you can pass the string -b gave you
back into snmpit with -B, and it should restore the original status
of the port.

Make sure to put the status string in single quotes when you pass it
on the command line. It contains some stuff that the shell won't like,
such as semicolons.

out.

event.

to digest-slothd

released. Not sure if the other keys need to be done, but does not
appear to matter.

This is a local hack for now.

Fix a couple of things I missed in my last checkin.

	* event/program-agent/program-agent.c: Setup of the user
	environment variables wasn't ordered correctly.

	* event/sched/event-sched.c, event/sched/rpc.h,
	event/sched/rpc.cc: Setup the expected user environment variables,
	just like in program-agent.

	* event/sched/simulator-agent.cc: Rename the old feedback data so
	we don't lose it in case the vnode remapping modify fails.

	* xmlrpc/emulabserver.py.in: Add virt_user_environment table data
	to the result of the experiment.metadata method, so the
	event-scheduler can get it.

again...

Checkin some changes related to experiment automation and vnode feedback:

	* configure, configure.in: Add sensors/canaryd/feedbacklogs
	template.

	* db/libdb.pm.in, db/xmlconvert.in: Add "virt_user_environment"
	table that holds environment variable names and values.

	* event/lib/event.c: Allocate memory of the right size for
	event_notifications.

	* event/program-agent/GNUmakefile.in: Add version.c file and
	add install targets for the man page.

	* event/program-agent/program-agent.8: Man page describing the
	program-agent daemon.

	* event/program-agent/program-agent.c: Add a bunch of convenience
	features: let the user specify the working directory for commands;
	save output to separate files on every invocation of an agent; let
	the user specify a timeout for a command; make the set of
	environment variables sane and add vars given in the NS file in
	the opt array; a "status" file containing process information is
	written out when children are collected.  Internal changes: child
	processes are collected immediately, instead of waiting for the
	next START event, so we can send back COMPLETE events; the daemon
	now runs with a real-time priority, to increase the chances of
	receiving events.

	* event/proxy/evproxy.c: Made it bidirectional so the
	program-agent's COMPLETE events make it back to the scheduler.

	* event/sched/error-record.c: Change the default log directory.

	* event/sched/event-sched.h, event/sched/event-sched.c: Setup an
	environment similar to a program-agent to run the user's log
	digester.

	* event/sched/node-agent.cc: Add a handler for the SNAPSHOT event
	that runs create_image for the node.

	* event/sched/simulator-agent.h, event/sched/simulator-agent.cc:
	Let the user specify a "DIGESTER" script that digests the log
	files into a summary of the results.  Add event handler for
	remapping a vnode experiment.

	* event/sched/timeline-agent.c: Accept the RUN event as well as
	the START event.

	* os/GNUmakefile.in: Install the install-tarfile.1 man page.

	* os/install-tarfile: Automatically chown/chgrp any files that do
	not have valid user or group IDs, the new owner will be the user
	that swapped in the experiment.  Include the install directory in
	the DB file.  Add a "list" mode that just dumps what files have
	been installed and where.  Add a "force" option so the user can
	forcefully install the file, even though the DB says its already
	there.

	* os/install-tarfile.1: Man page describing the install-tarfile
	tool.

	* os/syncd/GNUmakefile.in: Install man pages on ops.

	* sensors/canaryd/GNUmakefile.in: Link canaryd statically and
	install "feedbacklogs" tool.

	* sensors/canaryd/canaryd.c: Dump dummynet pipe data.

	* sensors/canaryd/canarydEvents.c: Log errors.

	* sensors/canaryd/feedbacklogs.in: Tool used to generate feedback
	data from canaryd log files.

	* sensors/slothd/GNUmakefile.in: Install digest-slothd on ops.

	* sensors/slothd/digest-slothd: Fix some bugs and write out an
	"alert" file with all the nodes/links that were overloaded.

	* tbsetup/os_load.in, tbsetup/libosload.pm.in: Add "waitmode"
	argument that lets you specify that you want to wait for the disk
	to finish loading and/or wait for the node to come back up in the
	new OS.

	* tbsetup/power.in: Remove debugging printf.

	* tbsetup/ns2ir/node.tcl, tbsetup/ns2ir/program.tcl,
	tbsetup/ns2ir/sequence.tcl, tbsetup/ns2ir/sim.tcl.in: Fix some
	quoting problems with event-sequences.  Add -expected-exit-code
	and -tag options to the "$program run" event.  Add -digester to
	the "$ns report" event that lets the user specify a program to run
	to digest the log files.

	* tbsetup/ns2ir/tb_compat.tcl.in: Change the initial scaling
	factor for feedback nodes to 1%, instead of 100%.

	* tmcd/tmcd.c, tmcd/common/libtmcc.pm: Add "userenv" command that
	returns the values in "virt_user_environment".  Return new program
	agent fields: dir, timeout, and expected_exit_code.

	* tmcd/common/GNUmakefile.in: Install rc.canaryd.

	* tmcd/common/bootvnodes: Add hack to boost the program-agents to
	a real-time priority, they can't do it from inside the jail.

	* tmcd/common/rc.canaryd: Rc script for canaryd.

	* tmcd/common/watchdog: Don't fail outright if there is a bad line
	in the battery.log

	* tmcd/common/rc.progagent: Append "userenv" data to the
	program-agent config file.

	* utils/GNUmakefile.in: Install loghole and its man page on ops.

	* utils/loghole.1: Document "clean" command and the change in
	loghole directories.

	* utils/loghole.in: Add "clean" command and parallelization.

	* xmlrpc/emulabserver.py.in: Add "virt_user_environment" table.
	Order the eventlist by "idx" and time, needed for sequences.  And
	removed unnecessary nologin checks.

"programs" command.

expected_exit_code) that get used by the newer program agent.  Add
virt_user_environment table that stores user config data for an
experiment.

vmc-client.c .

Hope to do this someday soon...

node) brings up a context menu that allows you to 1) Cancel the
current drag operation for that robot, 2) bring up the Emulab shownode
page in another window, and 3) set the orientation for the robot using
a popup dialog input box. This allowed me to clean up some of the
table handling code, and fix a glitch whereby a value left inside a
cell being edited caused the a cancel drag operation to immediately
start a new one.

into a single larger one.

create "delta" images based on the hash signatures that can be computed
by imagehash for an image.

To be used as a backup for NFS.

* Add nodeinfo backend page for the tracker applet to query for info about
  the nodes, including what type, what size, fixed/mobile, allocated etc.
  This is so we can draw the dots in the right scale, and make sure that
  fixed motes cannot be dragged around in the applet.

* Clean up a bunch of hardwired constants, mostly related to the size
  of the dots, and the font size (which determines where labels get
  drawn.

* And then I noticed the oddity resulting from having a robot that is 10.5
  inches long, but sweeps a diameter of 14 inches. The dot we draw is in
  scale (10.5in), but when I changed it to draw a 14in scale dot, that
  looked all wrong. So, there are actually two sizes now; the size of
  the robot, and the radius of the circle it sweeps (which is critical
  for determining obstacle avoidance). Still, this is confusing cause the
  user will place a robot near an obstacle (not overlapping) but will be
  told there is overlap cause the bubble around the robot is bigger then
  the dot. Not sure what to do about that. I could draw a large bubble
  around the robots but that is going to increase the clutter quite a bit.

current robot location (or its destination if the other robot is
moving or being dragged to a new location).

Oh, I should mention that to make the calculation easier, I am
treating robots as rectangles not circles. This is not ideal, but I
was not sure how to calculate overlap of two circles in a reasonably
efficient manner. I'm sure a high school student can tell me though.

browser.

fully contained within at least one camera (not the entire robot).

magical (atleast on OS X it is).

prepending zeros on times like "11:8:59".  Change the "baseurl"
parameter to "floorurl", since "baseurl" seems magical (atleast on OS
X it is).