Also create var/emulab/boot in the guest -- this should make it possible
to boot any fedora-like guest image, even if it hasn't been emulabized.
However, we need to also add support for the debian way of configuring
interfaces...

Clean up a couple of minor inconsistancies in the modules concerning
printing ports not in the wires table and make sure utterances like
"wap snmpit -i Nortel10 4/4" work properly.

- Keep from looping forever if we don't get loadinfo data
- Fix zapsuperblocks; make it use files under /sys instead of calling
  /sbin/fdisk (I long ago gave up trying to make rc.frisbee compatible
  with both FreeBSD and Linux).

Added code to create www/crossdomain.xml and www/protogeni/crossdomain.xml. The former allows flash clients to use the latter. The latter allows flash clients to access the xmlrpc interface if they hail from boss, ops or *.protogeni.net

Whenever making an xmlrpc call to a new site, make sure to check the protogeni/crossdomain.xml (if it exists) rather than the root crossdomain.xml

ever use one of the pseudo partitions linux creates when it sees a bsd
disklabel.

(slices suck!)

post facto.

because we (vnode_setup) needs to go out to the nodes and run vnodesetup
to trigger the reload, but os_setup needs to setup the reload.  So for
now, os_setup sets up the reload but does not wait nor reboot the vnode;
vnode_setup does that like normal.  Probably there are going to be timeout
problems, but it's good enough for my needs right now.

EXT4 directory added

EXT4 directory added.

EXT4 specific changes done.

Added EXT4 specific directives

EXT4 support for imagezip

ext4 filesystem support for imagezip

Changed flag output to attributes in ptop case to conform with Tarun's changes from a few months ago.

will get worked out better after the latest checkpoint :-).

the tb-set-node-os command with a second optional argument; if that is
present, the first arg is the child OS and the second is the parent OS.
We add some new features in ptopgen (OS-parentOSname-childOSname) based
off a new table that maps which child OSes can run on which parents, and
the right desires get added to match.  We setup the reloads in os_setup
along with the parents.  Also needed a new opmode, RELOAD-PCVM, to handle
all this.

For now, users only have to specify that their images can run on pcvms, a
special hack for which type the images can run on.  This makes sense in
general since there is no point conditionalizing childOS loading on
hardware type at the moment, but rather on parentOS.  Hopefully this stuff
wiill mostly work on shared nodes too, although we'll have to be more
aggressive on the client side garbage collecting old frisbee'd images for
long-lived shared hosts.

I only made these changes in libvtop, so assign_wrapper folks are left in
the dark.

Currently, the client side supports frisbee.  Only in openvz for now, and
this probably breaks libvnode_xen.pm.  Also in here are some openvz
improvements, like ability to sniff out which network is the public
control net, and which is the fake virtual control net.

done with a fake lan node in the rspec, but this is clearly (clear to
me at least) the wrong way to do this. But nececcary for the moment.

change pretty soon, but for the moment it allows me to create lans on
remote testbeds.

a ticket.