multiple desires for each vnode.

into assign.

server.

entry to database-migrate.sql that I forgot with my last commit.

but it's per node, not per type. Will initially be used to store
inforomation about planetlab nodes.

node_types table. This should make it easier to assign last mile
types to widearea nodes since a given type can now have as many
subtypes as you like.

Also add cpu_usage and mem_usage to the experiments table. The
user will be able to specify these in the NS file. Currently a
tinyint, where the default is zero, which means ignore.

that should be associated with a node when it is put into the ptop
file.

as an admin if you go to a users moduserinfo page. I'll be using this
to flag accounts frozen due to email problems.

have to change to an int format to save space. I'll probably make some
changes to the migrate code later, but I want to get the DB changes
checked in.

       control_iface join with node_types, since new nodes have more
       than just expt and ctrl interfaces (ixps). The control_net slot
       is bogus anyway. Note that 'jail' is a placeholder for later.
       A 'fake' interface is not to be confused with veth interfaces; it
       is a psuedo interface like that found between an ixp and the host.

       alter table interfaces add \
		role enum('ctrl', 'expt', 'jail', 'fake', 'other') \
		NOT NULL default 'other' after iface;

(soon to be working) sync server. When non-null (set by parser) that
node will start a sync server and other nodes will know to use it.
Returned by tmcd of course.

not have to wait 3 minutes for it to finish before he can watch his
experiment swapin fail for some other reason.

I adopted the same pid mechanism as in eventsys_control.in, which uses
a slot in the experiments table.

Running "prerender" puts the render into the background and stores
the pid. Running "prerender -r" kills a running prerender and removes
the existing info from the DB.

Fixed the problem with swapmod not restoring the old vis; swapmod now
kills any running prerender, and restarts one if the swapmod fails
(the prerun of the new NS file starts up another prerender in the
background).

Add setpriority() call in prerender to nice it and children to 15.

doing the boss-install, to remove confusion about a possible circular
dependancy.

       being used in an experiment (node, virthost, delaynode,
       simnode). This is for helping to simplify the swapmod code
       support in assign, and to eventually fix the delaynode problem.

final time, so that we can see how long things take. As per Jay's
request.

the node was temporarily given while it's configuring.

iface names

to the new_interfaces table.

which features and their weights can be placed, per node type.
ptopgen now includes these features in the ptop files it generates.

in the experiment_resources table as a BLOB. The advantages are no
more special directory and permission problems, and an archive of
pretty pictures of experiments (including per-modified experiments).

experiment_resources in revision 1.143.

when acting as a host for jails.

easier to chain back through the swapmod incarnations of an experiment,
without going through query hell, and is very useful in summary stats
page for calculating the usage across swapmods.

Note that the lastrsrc field of the experiments table can now go.

a null field is part of a primary key, there are no collisions. So
table_name "foo" and column_name NULL can have multiple rows, which is
bad.)

Also updated some state timeouts.

experiments are operated on by people other than the original creator.
The uid is currently a text field, but will need to change at some
point.

update V3 nodes to V4 CDs, and the new image. By inserting an entry
into this table, the node will update its image the next time it
reboots and checks in for instructions. The actual instructions are
hardwired in the web still, but this allows Dave to schedule updates
as needed. Eventually, the instructions will be part of the DB state
as well, but this works.

jail, to be added as an alias on the control network interface on the
phys node. There is no need for this to be in another table at this
point. Eventually, vnodes will be dynamic anyway, and a number of
things will change, including this.

will be the case for a trivial link with no underlying physical iface.

are packed 1) Add trivial_ok flag to virt_lans table. Global to the
lan or link, allow nodes in the lan or link to be colocated on the
same phys node. Perhaps make it per-node at some point. 2) Add
multiplex_factor to the experiments table to allow user to override
the multiplex_factor that is contained in the node_types table. Make
per type at some point.