GitLab

to the XEN backend. Not worth describing, its terrible.

booting XEN VM, let the library function deal with that, since
there is now code in there to watch a dead control network and
retry.

1. The backend process that starts the XEN vm (xl/xm) was not happy
   with the signal mask settings. By pass that for the vnodeboot call
   so that xl/xm sees a clean mask. The sympton was processes getting
   left behind.

2. Watch for a XEN container being rebooted from inside, by waiting a
   little bit to see if comes back on its own. We used to fold right
   away, but now keep running.

of giving up.

In order to hook in via the "generic vnode" path for setting up
blockstores under FreeNAS, I've done a bit of shuffling in order to
make things more OS-independent and reusable.

* mkvnode.pl

Moved to clientside/tmcc/common.  OS-dependent bits (really only some
IPtables stuff) abstracted, and moved to tmcc/linux/libvnode.pm.

* libvnode.pm

Moved generic vnode stuff to a new module.  Moved miscellaneous
utility functions to a new module.  Left OS-specific stuff.  Not
really sure if what is left should be merged into libsetup/liblocsetup
or left here - deferring this decision for now.

* libgenvnode.pm

New module currently containing generic vnode stuff.  Currently, the
VNODE_* predicates are here.

* libutil.pm

New module containing miscellaneous utility functions (fatal,
mysystem, mysystem2, setState, etc.)

Files referencing libvnode.pm have been updated, as have the relevant
Makefiles.

Snapshots are done a little differently then openvz of course, since
there are potentially multiple disk partitions and a kernel. The basic
operation is:

1. Fire off reboot_prepare from boss. Changes to reboot_prepare result
   in the guest "halting" insted of rebooting.

2. Fire off the create-image client script, which will take imagezips
   of all of the disks (except the swap partition), and grab a copy of
   the kernel. A new xm.conf file is written, and then the directory
   is first tar'ed and then we imagezip that bundle for upload.

3. When booting a guest, we now look for guest images that are
   packaged in this way, although we still support the older method
   for backwards compatability. All of the disks are restored, and a
   new xm.conf created that points to the new kernel.

This commit is intended to makes the license status of Emulab and
ProtoGENI source files more clear.  It replaces license symbols like
"EMULAB-COPYRIGHT" and "GENIPUBLIC-COPYRIGHT" with {{{ }}}-delimited
blocks that contain actual license statements.

This change was driven by the fact that today, most people acquire and
track Emulab and ProtoGENI sources via git.

Before the Emulab source code was kept in git, the Flux Research Group
at the University of Utah would roll distributions by making tar
files.  As part of that process, the Flux Group would replace the
license symbols in the source files with actual license statements.

When the Flux Group moved to git, people outside of the group started
to see the source files with the "unexpanded" symbols.  This meant
that people acquired source files without actual license statements in
them.  All the relevant files had Utah *copyright* statements in them,
but without the expanded *license* statements, the licensing status of
the source files was unclear.

This commit is intended to clear up that confusion.

Most Utah-copyrighted files in the Emulab source tree are distributed
under the terms of the Affero GNU General Public License, version 3
(AGPLv3).

Most Utah-copyrighted files related to ProtoGENI are distributed under
the terms of the GENI Public License, which is a BSD-like open-source
license.

Some Utah-copyrighted files in the Emulab source tree are distributed
under the terms of the GNU Lesser General Public License, version 2.1
(LGPL).

For InstaGeni, need to record and be able to search for history by
control net mac address. We now record this in the node_history table,
with corresponding change to the ShowNodeHistory web page.

The backend changes required are that we 1) actually generate a mac
address for VMs and stick it into the interfaces record, 2) return
that mac from tmcd in the jailconfig, and 3) have the openvz library
create the control net interface using that mac.

On the openvz image, needed to switch to using a control network
bridge for all interfaces (not just routable ones) so that traffic
leaves the node with the correct mac.

at.

of the openvz code to handle lvm garbage collection.

managed.

* Try much harder to prevent broken VMs from getting left behind.

* Try even harder to prevent left of state (devices, volumes, etc)
  from getting left behind once a VM breaks.

* Store all the assorted bits of state we create in a file so that it
  it can be cleaned up later.

* Watch for "stale" VMs that got left behind, using the UUID, which is
  regenerated each time an experiment is swapped in. Since we now
  store all the state that was associated with the stale VM, we can
  actually tear it down later. To do this by hand:

   node> sudo /usr/local/etc/emulab/mkvnode.pl -c pcvmXXX-YYY

* Lots of changes to signal handling to avoid a common problem case;
  trying to reboot or halt a VM that is still setting up.

directory.

resource locking issue that iptables should deal with, not me!

resource that must be locked, but the version of iptables we run
on the OPENVZ images bail if the lock is taken. STUPID!

existing containter.

This makes us (closer to) consistent all around and we were populating that
latter file incorrectly anyway!  (though it only mattered with the new
sub-boss mechanism.)

can't do this on vhosts running a different distro/version from the guest.

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.