GitLab

Add Liberty support.

Add keystone v3 support.  Now you can choose which version of keystone
to run... all combinations tested exception Juno with v3.

Make node type and link speed configurable.

Make token and session timeouts much longer by default (so people don't
get logged out so quickly), but also configurable.

Keystone is now served by WSGI through Apache on Kilo and Liberty.

Memcached keystone token caching is disabled for now; it causes
intermittent problems; so using SQL for now.

Add localhost to /etc/hosts file.  This doesn't cause problems anymore,
if it ever did.

We now use the `openstack' CLI command for >= Kilo, instead of the
per-service client CLI tools.

Stick with ovs agent even in Liberty -- even though the default is now
linuxbridge, it seems.

In general, get rid of nearly all the rest of the cat <<EOF ... EOF
stuff and replace it with crudini --set/--del.  A touch slower, but much
cleaner.

Also in general, improve the Kilo support so that it more closely
matches the docs.

If you instantiate a portal expt on Emulab (where you might have a real
account), the swapper is you, not geniuser.  So, check geniuser via
geni-get slice_urn success/failure.

Also, adds a geni-lib script that generates an rspec instead of printing
it (although print still works at portal) and generates input for
CM::AddNodes() when requested.  This generator is stateful; it tries
to avoid generating new nodes with previously-used IPs or client_ids;
thus it is a separate object.  It is designed so that it can be imported
into a script, and the importing script can look for special
DYNSLICE_GENERATOR variables to use its rspec foo to create a slice and
add nodes in some semantic way.

We want to use only local AM tmcd info in this case...

(Of course this will suffer from the problem of the limited tmcd buffer
for getmanifest.)

This is the fallback if we don't get an encrypted passwd from the
manifest.

Quit trying to apt-get packages if they're installed, unless the
user selects the new DO_APT_UPGRADE option.  Always install was nice
in the beginning, but it is no longer the best use case, and it can
cause uncertainty when failures happen (i.e., if new versions of
packages get installed that the scripts can't handle).  So now there
are three apt options in the scripts and in the geni-lib script:

DO_APT_UPDATE -- updates the apt cache (often hard to do pkg
  install/upgrade if the cache is out of date); defaults to 1
DO_APT_INSTALL -- if this is set 0, we don't install *anything*
  other than critical deps (think python-m2crypto); defaults to 1
DO_APT_UPGRADE -- if this is set 1, we always run apt-get install
  to either install and/or upgrade OpenStack packages and deps.
  The big change is that this now defaults to 0 -- so packages are
  not upgraded from their current versions if they exist.

Not sure why I did this... hopefully it still works for Juno this
way.

Hm, I have no idea why this is happening again, but whatever.
I previously fixed it on x86_64, now on aarch64.  Strange...

Mostly, we keep trying to start the app until it succeeds.  It seems
that the server needs some time to get started before it's safe to
start up the app.  Could be as long as 5-6 seconds.  We (and openstack)
can't do anything if the app isn't running in the server.

There's a fallback to this too -- if for whatever reason, we don't get
a password, we generate a random one and email it to the user.  Not
perfect, but still better than letting a null passwd through.

Also, on x86_64, make sure ubuntu user is in the VM image passwd
file, so that our fixed passwd is meaningful.

So far only have to handle utopic.

This allows us to operate on images with the openstack packages
installed, but services disabled to speed up boot.

This is really, really ugly.  So, keystone and nova don't offer us a way to
upload keypairs on behalf of another user.  Recall, we're using the adminapi
account to do all this setup, because we don't know the admin password.  So,
the below code adds all the keys as 'adminapi', then we dump the sql, do some
sed magic on it to get rid of the primary key and change the user_id to the
real admin user_id, then we insert those rows, then we cleanup the lint.  By
doing it this way, we eliminate our dependency on the SQL format and column
names and semantics.  We make two assumptions: 1) that there is only one field
that has integer values, and 2) the only field that is an exception to #1 is
called 'deleted' and we just set those all to 0 after we jack the whacked sql
in.  Ugh, it's worse than I hoped, but whatever.

This is one of the sickest one-liners I've ever come up with, but it
works like a charm!

SDN controllers think they're king, right?  Why should the admin be able
to insert custom rules?  Well, this is why.  Oh wait, it's just that I
don't have a northbound interface or whatever.  Let me just implement
one of those for this plugin instead!

It only mattered if the package install failed to start the service.
It seems like that was actually a possibility, although nondeterministic
from my perspective...

Can't suck up all the disk with these...

(Also, had never committed the manifest getter support programs.)

The lack of this in the distro packages (bugfix) triggers another bug
and crashes part of ceilometer, so just write this file if it's not
there.

Switch to using the newer messagingv2 notification_driver (I note
they've updated the Juno docs to use this too, so maybe it was available
then and the docs just weren't updated).

Handle a few Kilo-new config file things.  They didn't seem to be
hurting anything to do it the Juno way, but now it's "correct".

Make sure to add the glance registry, not just the api, for images.

We download the latest versions, and edit them.  However, the online
versions have bugs in the pipeline configuration, and the default
pipeline config no longer supports keystone auth through the proxy
server.  I don't know why, it means their online setup docs result in
non-working configurations, but whatever.

So, always set the pipeline now, and make sure it has keystoneauth.