character from , to ; (yes, very important change, I know).

directives in the node attributes, and use those to create the
additional file systems. This is not actually XEN specific, but just
where it currently gets used.

possible for Xen to give the guest a disk device to use for swap.
This code could be a lot better!

an assigned routable IP. Checks no longer necessary since we are open
source now.

Made the following changes to the clientside code to support Linux
firewalls:

- Made os_fwconfig_line() actually do something.
- getfwconfig() adds an 'IPS' hash to the fwinfo hash.  This contains
  the IP address for each host, much like how the 'MACS' hash contains
  the MAC address for each host.  This is needed because ebtables (which
  is needed for ARP proxying) doesn't resolve hostnames.

Rules are stored in firewall/iptables-fw-rules.  Syntax is similar to
fw-rules, but without the rule number (since iptables doesn't use rule
numbers).  These should be equivalent to our ipfw-based rules, but I
haven't tested every case yet to confirm this.  I'm sure some changes
will be necessary.

your NS file:

	$node0 add-attribute jailip 155.98.36.229
	$node0 add-attribute jailipmask 255.255.252.0

to override the default jail ip assignment. Use this carefully of
course since there is no checking yet.

You can also do something like this:

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

which will add these extra disks to your xen containers. Note that
this requires clientside changes from another commit to be installed
in the XEN image.

up a container using a routable IP.

Make sure that the name of the updated branch and the hash of the
changeset are displayed in the subject line, as in gitmail.

client side. These are not environment variables, these are just key
value pairs that the clientside boot can look for.

There is no make target to install this, but I wanted to get this script
"on the record."

of the openvz code to handle lvm garbage collection.

otherwise the client has no way to determine what to do, when the boot
does not involve a reload. The image must of course already exist on
the host.