GitLab

Initially intended for debugging, but now its more useful. :-)

the timeline.

Especially libvnode_docker::analyzeImageWithBusyboxCommand, which runs
the busybox-static binary from the root context in the container with
the given command (and extra container run API configuration).

(Instead of only supporting an image from an external repo as the base.)

to terminate experiments.

was not quite right and the graphs were messed up.

users on the local cluster).

expire, now that we store that info in the history table.

XML size on really big lans. I do not expect this to be used very often,
but it is handy. On the geni-lib side:

class setProperties(object):
    """Added to a Link or LAN object, this extension tells Emulab based
    clusters to set the symmetrical properties of the entire link/lan to
    the desired characteristics (bandwidth, latency, plr). This produces
    more efficient XML then setting a property on every source/destination
    pair, especially on a very large lan. Bandwidth is in Kbps, latency in
    milliseconds, plr a floating point number between 0 and 1. Use keyword
    based arguments, all arguments are optional:

        link.setProperties(bandwidth=100000, latency=10, plr=0.5)

    """

is off, this is just the control net interface (xenbr0). But when
XENVIFROUTING is on, we want to listen on the control net bridge plus
all of the container vifs. Since these are not created until the
container is started, we have to call restartDHCP from emulab-cnet (we
were already doing that), and now we also call reconfigDHCP() when the
contain is destroyed so that interface list is correct (note that DHCPD
does not seem to care if an interface dissappears, or even if an
interface does not exist when starting.

The main point here, is that on shared nodes we have to restrict the
number of interfaces that DHCPd listens on (or even looks at) since it
can be 100s, and dhcpd was taking well over a minute to start up each
time.

Aside; minor change to not look at the IP config for bridges, just the
mac. Takes to long when there are 100s of bridges.

rewrite the interface list in /etc/defaults/isc-dhcp-server. We do
not need to restart DHCP, it does not mind that the vif is gone.

since the vif foes not exist yet, and we call restartDHCP() again in
emulab-cnet after the container and vif exist. In fact, no point in
restarting DHCP when removing an entry, since by that time the vif is
gone and dhcpd does not seem to mind that anyway.

1. Show current reservations on the admin extend page (if any) for the
   user who started the experiment.

2. Add a reservation history page, to see historical reservations for a
   user.

3. Changes to the reservation listing page.

4. And then the main content of this commit is that for the pages above,
   show the experiment usage history for the project and the user who
   created the reservation. This takes the form of a time line of
   allocation changes so that we can graph node usage against the
   reservation bounds, to show graphically how well utilized the
   reservation is.

1. Return current set of reservations (if any) for a user when getting
   the max extension (piggy backing on the call to reduce overhead).

2. Add RPC to get the reservation history for a user (all past
   reservations that were approved).

   Aside; the reservation_history table was not being updated properly,
   only expired reservations were saved, not deleted (but used)
   reservations, so we lost a lot of history. We could regen some of it
   from the history tables I added at the Portal for Dmitry, but not
   sure it is worth the trouble.

3. And then the main content of this commit is that for both of the
   lists above, also return the experiment usage history for the project
   an dthe user who created the reservation. This takes the form of a
   time line of allocation changes so that we can graph node usage
   against the reservation bounds, to show graphically how well utilized
   the reservation is.

that backend processes in flight do not get killed in their tracks. This
might not work right, but elabinelab testing does not tell me much, lets
see how it goes.

within a project with reservations active during an experiment.

experiment.

connect two ports. It appears that letting port alarms pile up causes
the CLI to hang every now and then for a really long time. Thats my
theory, I have at least two data points to prove it.

in the tables.

caution.

need uid_idx and pid_idx. Also store the cancel date.

Fix bug; we were not storing a history entry for deleted reservations,
so we lost all those entries even though they were reservations that
were used.

to /home (does not copy from /users), and back to /users when toggling
off.