GitLab

working on getting a feeling of whether or not it's feasible to
implement assign in Comet. I think if it is, it would be a huge win in
terms of maintainability and extensibility.

So far, it's looking very promising. I'm struggling a bit with the
syntax, and the lack of an API reference. But, once I figure out how
to do what I need, it's making a lot of sense.

All this program does so far is try to respect the number of slots on
physical nodes - ie. not assign more than one vnode to a pnode, but it
can do arbitrary numbers instead of just 1.

It does not read top/ptop files, doesn't know about types, doesn't try
to minimize any score, doesn't do features/desires, doesn't know about
links at all, etc. Like I said, it's the beginnings of a toy program.

It looks to me like what we're going to end up doing is writing a
program to produce Comet programs. One of the cool things about this
is that it means we can leave out any constraints, etc. that are not
relevant to the particular mapping problem at hand. And, it should
make it easy for us to plug in other search techniques (ie. write the
obvious ones for certain pathological cases, like snakes and
trees.)

Fix up autoswap units in advanced form.

Add note about updating the node/ssh_pubkey sitevar.

With some work, we might be able to further reduce the image size.

Create a hosts file containing entries for boss and ops
for plab slivers and put it into the rootball.  This
will (hopefully) avoid flakiness due to flaky DNS servers.

files are being added to the archive at the correct places, but it
seems to work.

the experiment from ops' db to boss'.  File names are stored in the
accessed_files table and are associated with the experiment via the
fs_resources table.

into the main NS files via the "source" command.

Bump the plab rootball version up.

The revived Plab interface is here!

Lots of updates to the plab backend, including improved plab <-> elab node
id translation and update handling.  Includes support for the current PLC
API, and the new pl_conf node manager interface API.  Several more db library
routines were ported from the perl library to the python one to support the
new code (mostly the node_id tracking stuff).  Fixes to the client side and
also a rootball creation cleanup (binaries removed from the CVS repo).

There are also enhancements to the experiment view page for experiments
including plab nodes: site and widearea hostname are now displayed along
with the other node information.

Note that the way setup timeout for vnodes is calculated has been changed a
bit.  Instead of using a hardwired base timeout, the base timeout is now
based on the reload_waittime database field, which comes from the 'OS'
(e.g., FBSD-JAIL, RHL-PLAB) the vnode runs.

The default max duration for a plab slice created through the plab_ez interface
is set to 1 year, and linktest is currently disabled and hidden through
the ez interface.

There is still work to do, but this checkin brings with it a functional
plab portal!

archive!

studly users in the testbed project on the mainsite.

experiment, still likely to change.

Doh!  sshtb needs to exit with the status of the child process when
trying sshv2 and able to connect.

be muncged to work on older perl we use on boss.

(this was done quite a while back in our running MFS, just commiting
the change now so it doesn't get lost)

Remove the hardwired "-1" from an invocation of sshtb

change, and for now is only active at Utah.

the emulab-ops project only, so that we can more easily take nodes out
of the general pool, but still be able to use them.  This slot
actually takes a pid, so we could potentially use it more generally
for reserving nodes to particular projects, but I am not sure that is
the best approach yet.

 * remove db/entropy files to avoid sharing entropy
 * move update of locate DB to the end
slicefix:
 * update /entropy file where it exists in attempt to give every
   node a fresh burst of entropy

Add a note about /root/.ssh/config on boss and ops.

Added instructions for creating a passphraseless v2 RSA keypair for root
on boss, and explained where it needed to be added (on ops, boss and images).
Also described how to set Procotol 2 as the default everywhere possible.
THere is also a note about old user images and compatibility.

Update SSH_ARGS to remove "Protocol 1" specification.  Everyone needs to
reconfig their object trees!

significance (an audit file under Linux that was several MB)

can run.