GitLab

a XEN based ElabInElab with boss and ops running firewall rules based
on the ruleset we use on Utah's firewall. To turn this on, add this to
your NS file:

tb-set-elabinelab-attribute CONFIG_FIREWALL_BOSS "yep"
tb-set-elabinelab-attribute CONFIG_FIREWALL_OPS  "yep"

You do not have define both.

Watch for older Fedora 8 guest and use correct (old 32bit) kernel.

rules to ensure that the guest cannot change their assigned IP.

on modern linux, instead of our older qdisc hacks.

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).

fetching images.

Ideally, the kernel would be extracted from the image itself, but we live
in an imperfect world.

No more 768MB limit for memory.
Use FreeBSD 9 kernel if available, it is more stable with Xen.

control network, so that we can use routable IPs.

Create a swap volume for the guest. This addition is reflected in
rc.frisbee but not the linux version; looks for a disk with a dos
partition labeled as linux swap.

Look in the node attributes for additonal disk specifications and
create those disks (logical volumes). This is currently used in the
XEN elabinelab to add more disks for inner boss and ops, and look
like:

  $myboss add-attribute XEN_EXTRADISKS "disk1:10G,disk2:10G,disk3:10G"
  $myops  add-attribute XEN_EXTRADISKS "disk1:4G,disk2:10G"

It is up to the guest to do something with these, we do not partition
or label the volumes.

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.

Fix some bitrot in the Linux code: fixup /etc/fstab to have an old-style
LABEL=/ rather than a UUID.

Don't allocate more than 768MB of memory to a FreeBSD 8 vnode as it panics
otherwise.

directory.

Also, some tweaks to Ryan's state fixes.  Only run through the reload
states in vnodeCreate if we have loadinfo (i.e., we are in the PCVM_RELOAD
state machine).

In dhclient-exit-hooks we stash the vnode name in $BOOTDIR/vmname where
libsetup would expect it.

In libsetup.pm we set the event server to the physical host (based on
node names!)

In libvnode_xen.pm we reflect that these hacks are now done elsewhere!

It boots, but not all the startup scripts work right yet.

The model changed a bit after Jon did his version
(with the introduction of dynamically created vnodes on shared nodes).

This is still a work in progress.

the root fs of the vnode before it is booted. Did not want to
duplicate this code in the libraries.