GitLab

generalize this.

bit in doaccounts.

for a while). I am still not using the actual rspec definition yet, still
using my adhoc one.

vlans.

By default, limit plab node types to pc850 and pc2400c2 since they
won't boot on pc3000s and pc600 are not well tested.

Checkpoint working swapin of experiments using multiple federated nodes with vlans between them. Now I need to figure out how to swap the experiment out

handle local nodes -- to assign_wrapper and ptopgen, they're pretty
much the same.  If the "dedicated_widearea" node_type_attribute is
set for nodes of class pcRemote, we treat remote nodes like locals.
I stuck with using a node_type_attribute for this, but it makes fast
queries ugly.  I believe node_type_attributes are better than adding
yet another bit to the node_types table, but others may feel
differently.

another bit (/etc/emulab/isremded) that controls whether remote nodes are
fully reserved to a single experiment (should behave just like local
nodes, except they talk to Emulab like remote nodes).  Corresponding
changes in the rc scripts...

evproxy, we assume "event-server", which doesn't work so well on remote
nodes.  So, look for an eventserver file in any of the standard client
side locations (i.e., /etc/emulab); else, assume "event-server" and
extract the domain from bossname.

Currently nodereboot in libreboot essentially ignores the waittime
arg because it forks and calls node_reboot to do the real work, but
doesn't pass on the waittime to it.  Fix this by adding a "-W"
option to node_reboot in order to specify the waittime.

Use this to extend the waittime for a PLC node to come up from 6 minutes to 10.

 * when creating an image from a node, make sure the new image
   gets the MBR version used by the existing image
 * when loading a single-partition image that requires a different
   MBR, invalidate all other existing partition ("invalidate" in the
   sense that we remove any partitions table entries, we don't do anything
   to the disk)

make sure colocate factor does not end up null

do what the comments say it should do.  I'm not convinced that this is the
right thing to do in terms of what we claim to support in the wireless
tutorial... but it will stop the odd interface_settings dup key
insert errors that wireless users occasionally generates.

Add code to tell linux to re-read the partition table after we've modified it, since it won't do it until the next reboot otherwise