GitLab

versions of the image (metadata URLs), so that the caller can build
the entire history of the image locally. Necessary for deltas.

in the metadata; need to make sure that if the metadata url is for the
non-version specific, then so is the spew url inside the metadata.

>= 2, return lba size info.

Soon, we will have images with both full images and deltas, for the same
image version. To make this possible, the image path will now be a
directory instead of a file, and all of the versions (ndz,sig,sha1,delta)
files will reside in the directory.

A new config variable IMAGEDIRECTORIES turns this on, there is also a check
for the ImageDiretories feature. This is applied only when a brand new
image is created; a clone version of the image inherits the path it started
with. Yes, you can have a mix of directory based and file based image
descriptors.

When it is time to convert all images over, there is a script called
imagetodir that will go through all image descriptors, create the
directory, move/rename all the files, and update the descriptors.
Ultimately, we will not support file based image paths.

I also added versioning to the image metadata descriptors so that going
forward, old clients can handle a descriptor from a new server.

1. Fixes to allow specific versions of images to be exported; the existing
   path was reverting back to the highest numbered version. So far this has
   not come up, but will with APT and Cloud.

2. Add version argument to image_metadata.php, mostly as a convenience. So
   rather then using the version specific uuid, you can use the image uuid,
   with a version argument. This is actually more sensible, except for one
   important fact; it is not possible to locate a deleted image this way,
   since the image descriptor is gone (only the version descriptors are in
   the DB).

   But I went ahead and did it cause there is still some question as to
   whether we care about being able to export a deleted image. We do not
   expose these URLs at this time, but you can use one.

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).

image_metadata.php will return an Emulab style image descriptor in XML
format. A remote emulab, given an image URL, will grab this XML
description and use it to create a local descriptor. Inside the
descriptor is an additional URL that is used to download ndz file.

The dumpdescriptor script is now web accessible, and takes a new -e
(export) option that adds the extra URL and other bits that are needed
to import the descriptor and the image.

On the Show Image page, show the metadata URL, which is suitable for
using in an NS file or an rspec (when that code is committed).

image_permissions stores access info for images. You can share an
image with a user or a group (project), and you can specify write
access to allow updating the image in place. Note that write access
does not allow the descriptor to be modified, only the image itself.
Well, that is how it will be after Mike changes mfrisbeed.

The front end script to modify permissions is grantimage:

	boss> grantimage -u stoller -w tbres,myimage
	boss> grantimage -u stoller -w tbres,myimage

which grants write access to stoller. Or:

	boss> grantimage -g testbed,testbed tbres,myimage

which grants access to the testbed project. Notice that you can
specify subgroups this way.

	boss> grantimage -l tbres,myimage

will give you a list of current permissions. To revoke, just add -r
option:

	boss> grantimage -g testbed,testbed -r tbres,myimage

Who is allowed to grant access to an image? 1) An adminstrator of
course, 2) the image creator, and 3) any group_root in the group that
the image belongs to. Being granted access to use an image does not
confer permission to grant access to others.

One last task; while the web interface displays the permissions, there
is no web interface to modify the permissions; users will still have
to ask us for now.

For the backend script to properly grok it, we must set wholedisk=1 and
loadpart=<which ever partN_osid is defined>.

Anal alert: output the attributes in sorted order, cuz that is the kinda
guy I am.

this got dropped, but I guess we do not make these very often. But I
need it to work for the new version of load-descriptors on a new
installation.

that the web interfaces feeds to backend/newosid and newimageid.
The idea is to use this to dump and load the base IDs on a
new emulab installation.