GitLab

1) When selecting the day from the calendar, init the start time to 7am
   instead of leaving it unset. But do not do this if the hour is
   already set.

2) When using the search button, see if the reservation can be shifted
   to start at 7am. But do not pick a new slot if it can't, we want to
   give the user the earliest slot available.

only people would take the time to report things that do not work as
expected!

show the user, there was a path in which this was not happening.

1. When editing a reservation, request the forecast info specifically
   for the project the reservation is attached to. This is really
   important when looking at it as an admin, since we want to edit in
   the user's project context.

2. But to do that, we have to wait for reservation info to come back,
   and then ask for the forecast data.

3. And if the user clicks on the "Search" button before the res data
   comes back, we have to wait for it before we can search.

4. Fix the Search function; I was handling duplicates in the forecast
   data incorrectly.

the generic error code for all rspec errors, so that the Portal does
the right thing when displaying the error.

is gone but the web page has not figured it out yet.

There was a period where we didn't generate unencrypted SSL certs
for nonlocal users; create them now (and generally create any
missing unencrypted/encrypted cert for active users).

Also, now renew certs for nonlocal users.

same as 503 error code.

physical type on shared nodes so that the limits do not apply to
them (on the physical type).

1. Show the reason on the listing page, as popover in the last
   column. Makes it easier to approve directly from the listing page if
   you can see the reason.

2. Add optional approval message to pass along to the user.

Aka, add some locking, stupid!

1. Do not mark down nodes as needing to be updated, they just get stuck
   there.

2. In the CM daemon, what for slivers/aggregates that have been stuck in
   updating users for too long, and cancel the update. Typically this is
   cause a node is wedged or not participating (CORD), so again just
   cancel and reset the state.

knows to tell the user something useful.

ifaces that correspond to endpoints on nodes. Makes it easier to
do something like this, if we init the interfaces on the nodes with IP
and mask and bring it up.

	# Add a raw PC to the request and give it an interface.
	node1 = request.RawPC("node1")
	iface1 = node1.addInterface()

	# Specify the IPv4 address
	iface1.addAddress(pg.IPv4Address("192.168.1.1", "255.255.255.0"))

	# Add another raw PC to the request and give it an interface.
	node2 = request.RawPC("node2")
	iface2 = node2.addInterface()

	# Specify the IPv4 address
	iface2.addAddress(pg.IPv4Address("192.168.1.2", "255.255.255.0"))

	# Add L1 link from node1 to node2
	link1 = request.L1Link("link1")
	link1.addInterface(iface1)
	link1.addInterface(iface2)

Emulab Docker CMD and Entrypoint to runit services

See merge request !34