If number was positive, was converting to "(N)" for some reason.
Parens don't compare well with integers...

Also don't need "bc" just to compute abs(), just use "tr" to remove '-'.

Also adjust the max offset a smidge to 5ms, 1ms is a bit tight.

This allows nodes in GENI slices to retrieve information about their
sliver and slice via tmcc (or equivalent client-side support).  The
set of queries available and their names were agreed upon in GEC 17
sessions and subsequent discussions.

we update last_ext_act, since this is how idle determines staleness.
Not sure this is the best approach though.

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

We map them to their "formerly known as" ad names.

We currrently have a few cases where a slice record exists, but
no sliver, and so Renew was failing. Since we store all of the
expiration in the slice record, we do not actually need to have
an aggregate, so remove the check.

Usage: setexpiration [-f] [-m <time> | -M] [-e <datetime> | -E] [-i | -I] <slice>
Options:
  -f      - Force operation even it makes no sense.
  -m      - Max increment time for a renew. In minutes.
            Use zero to allow anything. Use "null" to clear.
            Use "NN days" or "NN hours" also.
  -M      - Clear max increment time for a renew.
  -e      - Termination date; sliver may not be renewed past this
            date. Use standard date format (YYYY-MM-DD HH:MM:SS)
  -E      - Clear max termination date.
  -i      - Set 'idle ignore'; no idle checks or email.
  -I      - Turn idle checks back on.

to normal newnode mode.

The GPO purchased racks all look the same so we can add the new
nodes statically from the XML file that HP sends us.

Well, for the UEN rack and other privately purchased racks, we do not
have any of that info, and so we have to figure things out ourselves.
We could use the standard newnode route without modification, but that
is a realy pain, say on a 33 node rack where the nodes land in any
order and you have no idea what the corresponding ilo is.

So I whacked this script to run from a data file we generate, which
contains the two bits of info from the top of the node (ilo passwd and
the ilo hostname), and the IPs we want to assign to the node and the
corresponding ilo.

So after turning all the nodes on and they checkin as usual, we run
this script with the -r option, which looks at the dhcpd.lease file to
find out what IP is which ILO, and the it asks each ilo via XMLRPC for
its hosts daya, which includes the ethernet MACs. I use that to find
the corresponding node in the leases file. Now I reorder the new_nodes
table so that pc1 is at the bottom and pcNN is at the top.

Now go back to the web interface and add all of the nodes.

Then run this script again (no -r), which will create all of the
management interfaces in the DB, reset the ilo, and then do the
normal initilo stuff for each node (boot order, password change, ssh
keys, etc).

Presto, done.

I figure out how to get the switches to do ssh login, so not
you can just do "sudo ssh procurve1" instead of telnet.

from control node.

fumbles around in an infinite loop.

work fine when the nodes are behaving themselves.

1) geni_update_users: Takes a slice credential and a keys argument. Can
  only be invoked when the sliver is in the started/geni_ready state.
  Moves the slice to the geni_updating_users state until all of the
  nodes have completed the update, at which time the sliver moves back
  to started/geni_ready.

2) geni_updating_users_cancel: We can assume that some nodes will be whacky
  and will not perform the update when told to. This cancels the
  update and moves the sliver back to started/geni_ready.

A couple of notes:

* The current emulab node update time is about three minutes; the
  sliver is in this new state for that time and cannot be restarted or
  stopped. It can of course be deleted.

* Should we allow restart while in the updating phase? We could, but
  then I need more bookkeeping.

* Some nodes might not be running the watch dog, or might not even be
  an emulab image, so the operation will never end, not until
  canceled. I could add a timeout, but that will require a monitor or
  adding DB state to store the start time.

continual retries that annoy people.

Kirk Webb authored Aug 06, 2013 and Kirk Webb committed Aug 06, 2013

Users want to make images derived from standard ones that support blockstores,
so let's make that possible.

Tweaks to prevent adding vlan 1 to the trunk allowed list.

We should only ever do this implicitly if the last vlan in the allowed list
is removed.