GitLab

project permission. By default you get a summary of all the free nodes
you can use in all your project memberships, which is not too
useful. It would be more useful to see what types you can use by
project, since that is how permission is granted and how experiments
are created. So, when you are a member of more than one project,
display a list of those projects along the top so you can see the list
on a per-project basis.

More generally, if you are an admin person:

	www.emulab.net/nodecontrol_list.php3?showtype=summary&bypid=tbres

will show out the summary information for a particular project. At
some point I need to make this a subroutine that we can call from
other pages to drop in a summary table.

system as well as the summary page.

For tbres/resweb (75 nodes):

	Old time: 42 seconds.
	New time: 19 seconds.

For testbed/BigLan (600 nodes):

	Old time: 120 seconds.
	New time: 40  seconds.

So, still needs some work, but for the average case its not so bad
anymore.

I also turn on compression to level 5 by default in our sshxmlrpc.py
library, thereby overriding the user's config file for that option.

delays to get the wrong BW setting in the delays table.

You can look at the error code to figure out if it will ever be
possible to map this experiment onto the testbed.

log, and to look at the summary page when the problem is not enough
free nodes!

dequeued.

inactive experiments.

partition by bootinfo, there actually is such a partition. This avoids
one instance Mike ran into in which the node got into a reboot loop
cause bootinfo said something that was not possible. So, run fdisk and
make sure the MBR has such a slice defined. If not, stay on the CD.

CD, and for extra robstness.

doc.

the getbandwidth() call on them (which finds the closest matching
physical interface speed).

add more potential root device unit numbers (4-7)

Add a section on using link_config and the XMLRPC interface to change
links on the fly.

would be required to use delay_config or link_config. For example:

	sshxmlrpc_client.py link_config proj=testbed exp=two-wireless \
		link=lan0 "params={'a': 4}"

Note last argument, which is eval'ed into a dictionary before it is
sent across in the RPC. This is done whenever first character of the
value is a "{" ... otherwise it is treated as a literal.

or undotted notation.

very specific to wireless links in general, and to iwconfig on Redhat
9.0. It allows you to control the entire lan or an individual member
of a wireless lan via the event system. For example to change the
accesspoint of a wireless lan, you could do this:

	tevc -e foo/bar now lan0 modify accesspoint=00:09:5B:93:0B:A4

The agent deciphers the event arguments and calls iwconfig with the
appropriate as needed. Note that there are many ways to make the lan
unusable doing this, so you want to be careful. You can get the MAC
addresses from the experiment info page (tbreport).

New script called link_config, which might be badly named since it
implies generality) to front end tevc. Operates mostly like
delay_config in that it will change the physical table settings, and
optionally (-m) the virtual table entries. So,

	link_config testbed two-wireless lan0 accesspoint=00:09:5B:93:0B:A4

You can change individual members of a lan too:

	link_config -s nodew1 testbed two-wireless lan0 txpower=50

Currently no web interface; too much work. I will add an xmlrpc
interface though since that is easy to do.

wireless) nodes.

or link the interface is operating for.

tutorial is just a simple walkthough of the GUI that has the user
create a two node experiment.

the name of the lan (virt_lans table entry) so that we can tell the
client what lan an interface is for. The reason this is horrible is
cause of how we describe lans/nodes in the DB with those member and
members slots. Terrible.

ssh libraries that want kerberos.

interface, and for what.