* Make user privs work across remote clusters (including stitching). I
  took a severe shortcut on this; I do not expect the Cloudlab portal
  will ever talk to anything but an Emulab based aggregate, so I just
  added the priv indicator to the user keys array we send over. If I am
  ever proved wrong on this, I will come out of retirement and fix
  it (for a nominal fee of course).

* Do not show the root password for the console to users with user
  privs.

* Make sure users with user privs cannot start experiments.

* Do show the user trust values on the user dashboard membership tab.

* Update tmcd to use the new privs slot in the nonlocal_user_accounts
  table.

This closes issue #309.

1. Get this working on the NS conversion path.

2. Add support for additional firewall rules along the path,
   the CM never had support for firewall rules.

3. Set the security_level to zapdisk when firewalling is on.

days is iptables vlan based firewalls.

best_effort. When given, do not set uselinkdelay in the CM. This is a
first commit, this will change slightly in subsequent commit.

Add new script to "deprecate" images:

	boss> wap deprecate_image
	Usage: deprecate_image [-e|-w] <image> [warning message to users]
	Options:
	       -e     Use of image is an error; default is warning
	       -w     Use of image is a warning

When an image is deprecated with just warnings, new classic experiments
generate warnings in the output. Swapping in an experiment also
generates warnings in the output, but also sends email to the user.
When the image set for error, both new experiment and swapin will fail
with prejudice.

Same deal on the Geni path; we generate warnings/errors and send email.
Errors are reflected back in the Portal interface.

At the moment the image server knows nothing about deprecated images, so
the Portal constraint checker will not be bothered nor tell the user
until later when the cluster throws an error. As a result, when we
deprecate an image, we need to do it on all clusters. Needs to think
about this a bit more.

give me everything. But do not allow for XEN vms, since that would not
make any sense.

user (read: Mike) so the user (Uh, Mike) does not get all wigged out
about not being able to use the nodes he (Mike?) want to use.

This closes issue #222.

can delete, and to delete individual versions of images.

expt_expires slot in the experiments table whenever we set the slice
expiration time. In addition, do this in GetTicket() so that the
mapper sees the proper expiration time; we do not set the slice
expiration until the ticket is redeemed, and this throws off admission
control.

check before register/unregister sliver.

Add a comment about rwclone.

switch to the other path (generating a wrapper script) instead of
throwing an error back to the user. I meant to do this a few years
back, guess I forgot.

needed to do that.

that they can be displayed and accounted.

a user error, although manifesting as DBQuery error (duplicate key) is
not exactly friendly.

1. Changes to gentopofile to not put in linktest info for links and lan
   with only one member.

2. Fix to the CM for deletenode of a node that has tagged links.

3. Fixes to the status web page for deletenode; we were installing the
   linktest event handlers multiple times.

4. Pass through -N argument to linktest from the CM, when the experiment
   has NFS mounts turned off, so that we use loghole to gather the data
   files (instead of via NFS).

This closes issues #160.

OSinfo and Image into a single object for the benefit of the perl
code. The database tables have not changed though.

true *snmpit*, all others are imposters and have been shot.

The snmpit_test directory moved to snmpit. snmpit_old is gone.

nodes in the topology. Instead of binding with a component_id, implement
new variant of the "relation" element, called "instantiate_on" that
specifies the client_id of the parent node. This becomes the "fixed"
slot of the virt_nodes table entry for the Xen VM.

  <services>
    <emulab:program-agent name="prog0"
         command="/bin/ls -lt &gt;&amp; /tmp/foo"
         onexpstart="true"/>
  </services>

Much like a normal "execute" service, these are event agents instead
of boot commands (which run on every boot of the node). When onexpstart
is true, the command is run at event time=0 only. All program agents
are set up to respond to tevc commands like program agents in an classic
Emulab experiment.

not happy with that part yet.

requested expiration, no need to do anything, including the permission
checks.

the value of sitevar protogeni/default_osname when no OS is specified.
For Phantomnet, Kirk needs the type specific default OS used instead.

end node shaping (and the delay agent) on.