GitLab

profile deletion.

image versions at the clusters.

to the web UI.

can delete, and to delete individual versions of images.

versions of the image, which is certain contexts is needed.

the version does not have to be the head version; any version can
now be deleted. We mark the DB row as deleted and delete the image
file when the purge option is given (which is most of the time).

long and the RPC will timeout. This is actually harmless, since
the termination at the cluster eventually finishes and we will
notice that from the daemon.

temporary value array instead of the image hash. I do not think
anything actually calls for that internal array.

Hussam found the answer at:
   http://northernmost.org/blog/gre-tunnels-and-ufw/index.html

node pool.

This is only done for shared nodes right now.

See emulab-devel issue 227 for details.

Also, on a "reset" clean out the correct BDB files. It has been
a long time since they used ".db" as the suffix. Now there are
".pag" and ".dir" files. We haven't noticed because we don't really
use the "reset" operation. The prepare script just removes
everything in /var/emulab/db.

generate a top level element in the emulab namespace that lists the
nodes that cat be reserved (physical node types with at least one
actual node in the database). Change portal_monitor to look for and
use this element when processing the advertisement.

from being deleted. If a profile cannot be deleted, then the images
it references cannot be deleted either.

initial import of an image, Normally this is done in create_image, but
need to do it here as well.

Probably some perl way to avoid this, but life is short.

we have to look in that DB, not the geni-cm database.

user right after create.