GitLab

descriptor). Stash the current typelist into the descriptor being cloned,
just before cloning (safety measure, until I fix the image update path).

existing image in emulab-ops. This is a last resort, as we do store a copy
of the typelist in the descriptor for just this purpose, but stuff happens.

version number.

	usage: runsonxen [-p <parent>] <imageid>
	usage: runsonxen -a [-p <parent>]
	usage: runsonxen -c <imageid>
	Options:
	 -n      - Impotent mode
	 -c      - Clear XEN parent settings completely
	 -a      - Operate on all current XEN capable images
	 -p      - Set default parent; currently XEN43-64-STD

Mark image update time when importing; more important to know
when the image was brought in then when it was updated on the
remote site.

e.G. the following assign violations gave just 'Not enough bandwdith' as the 0 always matched.
Now we match with any number 1-9

   BEST SCORE:  50.5 in 0 iters and 0.008631 seconds
  unassigned:  0
  pnode_load:  26
  no_connect:  0
  link_users:  0
  bandwidth:   0
  desires:     0
  vclass:      0
  delay:       0
  trivial mix: 0
  subnodes:    0
  max_types:   0
  endpoints:   0

out the group changes. This is the wrong way to do this, but a real
fix will wait until I have to deal with it in CloudLab.

much quicker.

But remain backwards compat with existing certificates and credentials.

Mail now comes from gitlab@flux.utah.edu so that replies go to Leigh's
new comment ingesting mechanism. Mail now goes to an address defined in
a hash in this file (could also be in the config file) depending on the
label attached to the issue.

Eventually I am going to turn this off for all projects.

pseudo user and prepend the From address on the email to comment

into a gitlab issue comment. The wrinkle is in how we map the email
address into a gitlab user. We have to search the user DB looking for
a match against the username or email. You can guess what is going to
happen, eh?

I tested it with this data file:

	From: Leigh Stoller <lbstoller@gmail.com>
	To: lbstoller@gmail.com
	Subject: gitlab issue: [emulab/emulab-devel] issue #10

	This is another comment.

running it like this:

	gitlab> cat foo.txt | email2issue -c /git/gitmaild.conf

and it add a new comment to:

	#10

port problem on ops.

used to manage local blockstores (datasets). A cheesy iframe hack is used
to embed the APT pages (slick new interface) inside the antique Emulab
interface.

Currently the only hooks from the admin drop down menu, since there is some
additional work before we let users see it.

function has been moved into manage_instance and its associated library
(APT_Instance). Lots of cleanup of the code and more use of webtasks to
communicate with the web server.

scripts. Also add a describe method.

In order to create a dataset, the caller must either be a local user, or
have an extra credential that grants the "blockstores" priv.

Like slivers, datasets are currently created in the holding project and
group corresponding the SA and subauthority.

Eventually need to add sharing control (say, to make a dataset globally
read only), but that does not exist in the backend yet.

the backend cluster.