GitLab

page, and was immediately taken back to the new Clone image page. Thus
forcing Mike to use the new page (and help fix a silly bug). What a
plan, now I can get rid of the Classic button.

member list tab of show-project and show-group pages.

says Please Select, and there is no Clear Selection choice. I am leaving
it up to the profile to require a node type when constrained, as
discussed in the meeting today.

tell us.

table.

specific node, node types, or aggregates. Before we submit the
experiment to the target clusters, process the rspec looking for
anything that needs an accepted license, break the flow by throwing up a
modal that tells the user they need to request permission to use the
resources. This sends email to operations.

Later ... after email discussion with user, need to run a CLI command on
the boss that requires the user to accept those licenses.

	boss> wap manage_licenses require <license name> <uid>

Next page load by the user will throw them into the license accept
page.

Now we just need some licenses ....

json error format so that users get better feedback when there is a
network failure.

includes members ad switch path).

Not included anywhere right now. It will have to be conditionally
included depending on what version of PHP is in use.

The current quarterly FreeBSD port set has removed php5 requiring a
transition to php7 (7.2). php7 in turn has removed the mysql module
requiring that we switch to mysqli. Fun times.

errors or warnings on a parameter in the group.

* Do not overwrite the cluster selection(s) when the reservation info
  comes in; that takes 5-10 seconds, and if the user has already made
  the selections, leave them alone.

* More generally, we draw the cluster selectors multiple times, and we
  were losing the previous selection. Sure, if the user selects a
  cluster and the constraint checker says it is not allowed, then its
  okay to change it (might change my mind on this). But trying too hard
  is annoying.

Get rid of a bunch of debugging console prints.

when the repo changes, unless its the manage profile page and its the
profile creator (the same code is shared in different places).

understand any of the radio gear or new hardware, and its too easy to
generate bad rspecs.

The high level goal; redo all the classic image pages within the Portal
UI such that mere users never see the old crusty stale rotting pages.
Old fart admins (know any?) can still access the old pages, but I am
hoping that won't actually happen (hint, hint).

Another goal; allow editing of Geni created images (local images
only). It has always bothered me that Portal users have no way to get
info or do minor editing on Portal created images. Especially since
images are so central to everything we do. Only local images can be
edited, but in the Emulab portal, that is all images.

Mothership only for now. Lets see how much whining we get, might have to
adjust the interface a bit since Classic users are going to find
themselves in unfamiliar territory.

first one!

If there is a directory called "profiles" and there is a file in that
directory named the same as the profile, and ends in a .py (or .rspec),
then use that as the profile source code instead of toplevel profile.py.

seconds), Compare against new one, and skip updating the node popovers
and boxes is nothing has changed. On a 256 node lan, this drives one
core almost to 100% each time. Well, David's cores. My cores barely
notice it. :-)

end so that everything can run in parallel. And, so the extend
button (among others) is not locked out from working while it loads
everything.

Also, do not copy the massive idledata strings through the database
(twice). Sometimes a file is just a good idea.

image relocation.