GitLab

deletes an image.

import new versions of images).

experiments. Lockdown is implemented at the portal and at the backend
cluster (ignore by cm and sa daemons). At present, the only policy is
that admin extensions longer then 14 days, set the lockdown.

Change the From: header to "Geni Operations".

actually being done.

1. Add warning 1 hour before expiration, even for "short lived"
   slivers.

2. Auto-delete orphaned cartificates.

3. Try to destroy locked/expired slices before send email about them.

When a new sliver is created, they are given a relatively short
lifetime. This is the value of protogeni/initial_sliver_lifetime and
defaults to six hours.

A user may renew a sliver for up to the number of days in
protogeni/max_sliver_lifetime (defaults to 90 days), except in Utah
where it is 5 days (Emulab, Utah Rack, Utah DDC Rack).

The CM daemon idle code looks for idle slivers. An idle sliver is one
in which 50% of the physical nodes have been idle for three hours.
(protogeni/idlecheck_threshold). At this point an email message is
sent to the sliver creator.

If the sitevar protogeni/idlecheck_norenew is set, then the email
threatens to mark the sliver as unrenewable if it stays idle. Then, at
2 * protogeni/idlecheck_threshold, if the sliver is still idle, the
sliver is marked as unrenewable. No matter what the user does at this
point, he will not be able to renew the sliver and it will expire out
normally.

If protogeni/idlecheck_norenew is no set, behaviour remains as it is
now; a followup message is sent every 24 hours.

There is a new backend script called "setexpiration" that allows an
aggregate admin person to override the settings on a per-slice basis
so that users who have a need for a long running sliver do not have to
continually renew and/or bypas the max_sliver_lifetime setting. For
example:

boss> wap setexpiration -e YYYY-MM-DD mysliceurn

will extend the termination date to the given date. To restore the
default behavour:

boss> wap setexpiration -E mysliceurn

Note that idle checks are still made. To turn off idle checks for
a slice:

boss> wap setexpiration -i mysliceurn

To turn then back on:

boss> wap setexpiration -I mysliceurn

normal experiments. I could have rolled this into the existing code,
but that would have been very unpleasant.

Currently, checks every 15 minutes, using the same idle threshold as
idlemail, but sends email only once every 24 hours. There are two
site variables:

  protogeni/idlecheck		- enable/disable PG idle checks.
  protogeni/idlecheck_terminate - enable/disable termination on idle.

Both start as zero when the site variables are added.

DB objects we use in the libraries. We hang onto those objects forever
in the expire daemon, but they are stale in the case of shared vlans
which are being messed with elsewhere.

Rather then track down all the caching bugs, I changed the expire
daemon to call the existing cleanupslice script, avoiding all cache
problems.

This commit is intended to makes the license status of Emulab and
ProtoGENI source files more clear.  It replaces license symbols like
"EMULAB-COPYRIGHT" and "GENIPUBLIC-COPYRIGHT" with {{{ }}}-delimited
blocks that contain actual license statements.

This change was driven by the fact that today, most people acquire and
track Emulab and ProtoGENI sources via git.

Before the Emulab source code was kept in git, the Flux Research Group
at the University of Utah would roll distributions by making tar
files.  As part of that process, the Flux Group would replace the
license symbols in the source files with actual license statements.

When the Flux Group moved to git, people outside of the group started
to see the source files with the "unexpanded" symbols.  This meant
that people acquired source files without actual license statements in
them.  All the relevant files had Utah *copyright* statements in them,
but without the expanded *license* statements, the licensing status of
the source files was unclear.

This commit is intended to clear up that confusion.

Most Utah-copyrighted files in the Emulab source tree are distributed
under the terms of the Affero GNU General Public License, version 3
(AGPLv3).

Most Utah-copyrighted files related to ProtoGENI are distributed under
the terms of the GENI Public License, which is a BSD-like open-source
license.

Some Utah-copyrighted files in the Emulab source tree are distributed
under the terms of the GNU Lesser General Public License, version 2.1
(LGPL).

go in before Monday. Once a CM updates to stable, it will start
sending aggregate/manifest history records to the ClearingHouse, which
will store all records for all CMs. The CM actually goes back and sends
all the records from the beginning of time; hopefully there will not
be any serious problems with the very early records at the early CMs.

Still to be done, is an interface at the CH to export the records to
someone with a proper credential. But that can wait till next week.

over and over. Add a flag to geni_slices, to indicate the slice is
down.

of time that slivers are allowed to hang out without being renewed.

starting any one of our scripts can take a second or two. That time is
spent including and compiling 10000s of thousands of lines of perl
code, both from our libraries and from the perl libraries.

Mostly this is just a maintenance thing; we just never thought about
it much and we have a lot more code these days.

So I have done two things.

1) I have used SelfLoader() on some of our biggest perl modules.
   SelfLoader delays compilation until code is used. This is not as
   good as AutoLoader() though, and so I did it with just a few 
   modules (the biggest ones).

2) Mostly I reorganized things:

  a) Split libdb into an EmulabConstants module and all the rest of
     the code, which is slowly getting phased out.

  b) Move little things around to avoid including libdb or Experiment
     (the biggest files).

  c) Change "use foo" in many places to a "require foo" in the
     function that actually uses that module. This was really a big
     win cause we have dozens of cases where we would include a
     module, but use it in only one place and typically not all.

Most things are now starting up in 1/3 the time. I am hoping this will
help to reduce the load spiking we see on boss, and also help with the
upcoming Geni tutorial (which kill boss last time).

no corresponding entries in the other tables. Not supposed to happen,
but it does and I want to see if I can catch what is going on.