emulab-devel:f586ad16d24a282a75712cd49c3d86f51d33cfac commitshttps://gitlab.flux.utah.edu/emulab/emulab-devel/commits/f586ad16d24a282a75712cd49c3d86f51d33cfac2019-03-13T13:20:14Zhttps://gitlab.flux.utah.edu/emulab/emulab-devel/commit/f586ad16d24a282a75712cd49c3d86f51d33cfacA slew of image/dataset changes for secure (credentialed) images and2019-03-13T13:20:14ZLeigh B Stollerstoller@flux.utah.eduimage relocation.https://gitlab.flux.utah.edu/emulab/emulab-devel/commit/168949a947e4947991d1f8bfb785db61c2469695Minor fix for deferred aggregates, need to make sure we update the table2019-03-13T13:01:08ZLeigh B Stollerstoller@flux.utah.eduso that the scheduler will retry failed aggregates.https://gitlab.flux.utah.edu/emulab/emulab-devel/commit/ce8de4b78b6105a73efce1e807d84c33d60e08f4Bump MAXJACKSNODES back up to 300 now that the parsing issue is2019-03-13T13:00:22ZLeigh B Stollerstoller@flux.utah.eduresolved.https://gitlab.flux.utah.edu/emulab/emulab-devel/commit/aa4d2b6c212efe1fd8b9b2f857b9a84942443ecbA couple of little tweaks. Trying to catch a race ...2019-03-11T22:37:40ZLeigh B Stollerstoller@flux.utah.eduhttps://gitlab.flux.utah.edu/emulab/emulab-devel/commit/de2e02e4393653bc61749324ccadc817dabfbb46Minor fix.2019-03-11T19:32:33ZLeigh B Stollerstoller@flux.utah.eduhttps://gitlab.flux.utah.edu/emulab/emulab-devel/commit/c1e2c279caced5b33be5269d5aa9092d7befeae8Tighten up parsing of interface strings to avoid ambiguities.2019-03-11T19:19:21ZMike Hiblerhibler@cs.utah.edu
Specifically, a "node" name cannot contain a colon and "port" and
"card" must be decimal digits.https://gitlab.flux.utah.edu/emulab/emulab-devel/commit/4472cb3d3f20eb9af9e44baa4ec5a2bd4d47c10aResurrect and update the code to not show the topology when too many2019-03-11T18:45:35ZLeigh B Stollerstoller@flux.utah.edunodes causes Jacks to hang the page for minutes. The threshold is now
75 nodes until Jacks is fixed.https://gitlab.flux.utah.edu/emulab/emulab-devel/commit/3340b8121f57e809458e48bd1c2af5dfd3e18900Rest of the support for featurized permission to use aggregates.2019-03-11T18:33:39ZLeigh B Stollerstoller@flux.utah.eduhttps://gitlab.flux.utah.edu/emulab/emulab-devel/commit/3f4ac33b4493e0b7af2392b3080b1b87c9b5bddcMinor tweaks to previous revision.2019-03-11T15:36:17ZLeigh B Stollerstoller@flux.utah.eduhttps://gitlab.flux.utah.edu/emulab/emulab-devel/commit/7ab4d9b4671ef87955946bcbc2172dd9041d8210Add feature slot for use in controlling who can access an aggregate.2019-03-11T15:11:30ZLeigh B Stollerstoller@flux.utah.eduNot sure I like this approach, might revisit later.https://gitlab.flux.utah.edu/emulab/emulab-devel/commit/6a8db9e4eccc34bc56b7db4c5a1e268337f92188Changes to which aggregates users see in the Powder portal:2019-03-11T14:50:56ZLeigh B Stollerstoller@flux.utah.edu
* Add feature check that allows users to use aggregates. Used so that
not all users see the FE nodes. The same feature checks are used on
the resource availability page.
* Turn cluster selector on.
* Mess with ordering, since Emulab is not a federate in Powder,
everything else is, and we want Emulab first and Cloudlab Utah second,
and everything else after that. Silly, but I know this will change so
using brute force approach for now.https://gitlab.flux.utah.edu/emulab/emulab-devel/commit/52e9b047dedac624464cdce395d17efe18b4e5ceMinor fix.2019-03-08T17:44:15ZLeigh B Stollerstoller@flux.utah.eduhttps://gitlab.flux.utah.edu/emulab/emulab-devel/commit/94f9e14e8265520ed08c742d9f0ab710f88b5835You moron Leigh, its 2019! Not 2018!2019-03-08T16:53:38ZLeigh B Stollerstoller@flux.utah.eduhttps://gitlab.flux.utah.edu/emulab/emulab-devel/commit/7d6b128bf59530ce4fac9eacdfdd0ebd130c1367Oops, forgot to write the code for changes portal list.2019-03-08T16:28:32ZLeigh B Stollerstoller@flux.utah.eduhttps://gitlab.flux.utah.edu/emulab/emulab-devel/commit/e5dd7465944acb6df64fbd421800a8edf1e7b5f6Minor tweaks to graph formatting for Powder; only the Emulab cluster has2019-03-08T16:27:21ZLeigh B Stollerstoller@flux.utah.edu"radios" at the moment, so other cluster get a single wide graph.https://gitlab.flux.utah.edu/emulab/emulab-devel/commit/1713d7b4052919dfce141bf00d53a149daf6ab6cTurn on NewOsload and GeniOsSetup features on Powder FEs.2019-03-08T16:26:35ZLeigh B Stollerstoller@flux.utah.eduhttps://gitlab.flux.utah.edu/emulab/emulab-devel/commit/ca924150e9d35d568f47b746ff587b2cf246aa9aFix parameter problem when switching profiles, clear the arrays.2019-03-08T16:21:17ZLeigh B Stollerstoller@flux.utah.eduhttps://gitlab.flux.utah.edu/emulab/emulab-devel/commit/686d327cf7c9f50cde552038c4b59e825eda9eaaYep, a bug in previous revision.2019-03-08T13:54:28ZLeigh B Stollerstoller@flux.utah.eduhttps://gitlab.flux.utah.edu/emulab/emulab-devel/commit/94dfaad2ff4c2fb96764f92f23982fb2e93d7fc4All the empty string in elabinelab attributes.2019-03-06T21:42:58ZLeigh B Stollerstoller@flux.utah.eduhttps://gitlab.flux.utah.edu/emulab/emulab-devel/commit/7f2dc913d3e7352fe319bbc31f56e6b4ba68eea7Minor tweaks to handle setting AMD_ROOT="" for fixed endpoint elabinelab.2019-03-06T21:16:50ZLeigh B Stollerstoller@flux.utah.eduhttps://gitlab.flux.utah.edu/emulab/emulab-devel/commit/96c565f023201d83cfe9ad9e72879f409db5017bHmm, running this script with no arguments does the deed. Lets require2019-03-06T20:55:37ZLeigh B Stollerstoller@flux.utah.edusome confirmation before powering down all of Powder.https://gitlab.flux.utah.edu/emulab/emulab-devel/commit/f8d6ce3bd840eb300810fbd95fe4509a6184ce77Handle def_parentosid properly.2019-03-06T18:45:20ZLeigh B Stollerstoller@flux.utah.eduhttps://gitlab.flux.utah.edu/emulab/emulab-devel/commit/9256fdd5e3e77fd1e1b652014b91268ef7cd08c8Add option (-P) to remove sa/cm/ses authorities from CH database, when2019-03-06T17:59:08ZLeigh B Stollerstoller@flux.utah.eduusing -r to remove CA certificate.https://gitlab.flux.utah.edu/emulab/emulab-devel/commit/364a7168c1f76abd40c809704444d38b93f2f0cdDataset credential fix; need to send dataset creds to the aggregate2019-03-06T15:45:35ZLeigh B Stollerstoller@flux.utah.eduwhere they are used, not to all aggregates in a multisite experiment.https://gitlab.flux.utah.edu/emulab/emulab-devel/commit/7e178bf68a936bbba5ba475c53a2e0789354bb68Oops, left out powder_shutdown script.2019-03-06T15:41:38ZLeigh B Stollerstoller@flux.utah.eduhttps://gitlab.flux.utah.edu/emulab/emulab-devel/commit/7b7917b631f38adc367037e6fa7c7833643fe83bMinor fix.2019-03-06T15:08:06ZLeigh B Stollerstoller@flux.utah.eduhttps://gitlab.flux.utah.edu/emulab/emulab-devel/commit/db0d2d77306feb6ebe7ad7eb8372b4070a6f5934First cut at Powder Stop Button:2019-03-06T14:12:45ZLeigh B Stollerstoller@flux.utah.edu
The basic operation is that user "powdstop" in the holding project
PowderStop gets to press the stop button. And that's all! This user sees
nothing but the Stop button (and logout). We can give the password to
whoever is supposed to be able to press the button.
Once pressed, we show a list of experiments that are going to be put
into quarantine mode (with power off), and then update the list as the
experiments report back that they are successfully in quarantine mode.https://gitlab.flux.utah.edu/emulab/emulab-devel/commit/0d852349a0ff9286db7d8461656c6976c9c79fa5New script to display info about an aggregate and set/clear flags.2019-03-06T14:12:45ZLeigh B Stollerstoller@flux.utah.eduhttps://gitlab.flux.utah.edu/emulab/emulab-devel/commit/0cdc4807a5da6ab7a1de470d6ed78eb438f5af08UI changes to quarantine mode:2019-03-06T14:12:45ZLeigh B Stollerstoller@flux.utah.edu
* Remove quarantine set/clear from admin extend page, this is a bad
place for this since you do not get to see the experiment react to
it. And it duplicates what is on the status page,
* quarantine runs in the background, display info reminding admin about
that. The experiment state will change to "quarantined" once it
completes. For users, add a help button explaining what quarantined
means to them.
* Switch the Warn/Kill button to "Release" when an experiment is in
quarantine mode.https://gitlab.flux.utah.edu/emulab/emulab-devel/commit/be466a09746d22e6d1b32459ea525d6d01e3fdd1Add nolocalimages flag to per cluster flags display.2019-03-06T14:12:45ZLeigh B Stollerstoller@flux.utah.eduhttps://gitlab.flux.utah.edu/emulab/emulab-devel/commit/7cc5c5e1a4f11cfbaee4da48c176910dde2017baMinor changes to make it easier to put (portal dependent) support mail2019-03-06T14:12:45ZLeigh B Stollerstoller@flux.utah.edulinks into templates.https://gitlab.flux.utah.edu/emulab/emulab-devel/commit/e749d1c9e2614113d5be0836831886213c87af76Minor fix.2019-03-06T14:12:45ZLeigh B Stollerstoller@flux.utah.eduhttps://gitlab.flux.utah.edu/emulab/emulab-devel/commit/bc4d1802c331c8283299c1a565594437af6a9003Run Panic in the background since it can take a long time, and we do not2019-03-06T14:12:45ZLeigh B Stollerstoller@flux.utah.eduwant the web interface just sitting there. We wait a short time for the
child to catch quick errors, but rely on email notification if something
goes wrong in the backend.https://gitlab.flux.utah.edu/emulab/emulab-devel/commit/3e17cecd5a451fe045b32b6a103c0269e52e2bd2Minor tweak to error handling.2019-03-06T14:12:45ZLeigh B Stollerstoller@flux.utah.eduhttps://gitlab.flux.utah.edu/emulab/emulab-devel/commit/937d633f1beb1252174b9dca30a97d44622a7ec4CM changes to termination and panic.2019-03-06T14:12:45ZLeigh B Stollerstoller@flux.utah.edu
* For termination, added a flag to the slice that marks it for
termination. DeleteSlice sets this if the slice is
"busy" (start,restart,reload) and the "cancel" flag is provided. We
also mark the underlying experiment as canceled, to stop ossetup and
osload early. We then wait for "busy" to clear, and then kill the
slice. The new termination flag in the slice is used by the expire
daemon, in case our wait loop dies early (say, boss reboot), we can
catch the the termination there instead.
* Panic gets essentially the same changes as termination, except of
course instead of terminating, we put the underlying experiment into
panic mode.
Note that we still need to be able to lock the slice to do either
termination or panic, and so the caller has to be able to deal with
retrying if they get back a busy response. In general, we do not lock
slices for very long except during reload and restart, I am still
working on dropping the lock during those (like we already do for
Start). Disk imaging is another place we currently need to wait for,
that needs to be worked on as well.https://gitlab.flux.utah.edu/emulab/emulab-devel/commit/cf6dd622db7b4d72034812ad8fa9241038663cd2Add convenience methods, add panic/shutdown flags to status blob.2019-03-06T14:12:45ZLeigh B Stollerstoller@flux.utah.eduhttps://gitlab.flux.utah.edu/emulab/emulab-devel/commit/73391fe902468fd83045e893f045ab82f8cfe171Add some object methods specific to dealing with datasets.2019-03-06T14:12:45ZLeigh B Stollerstoller@flux.utah.eduhttps://gitlab.flux.utah.edu/emulab/emulab-devel/commit/6f7dfcfde9e1ac21490c997617091c86e6e6617bMinor fix to test that flags the node is in the recovery MFS.2019-03-06T14:12:45ZLeigh B Stollerstoller@flux.utah.eduhttps://gitlab.flux.utah.edu/emulab/emulab-devel/commit/f6d6adda49f72dfa4b0b12cdc560598ddb6216d8Add an Update() db method.2019-03-06T14:12:44ZLeigh B Stollerstoller@flux.utah.eduhttps://gitlab.flux.utah.edu/emulab/emulab-devel/commit/6e7cb2172c256fd976cf584a1de7bd893954e834Flag Panic for full debugging output.2019-03-06T14:12:44ZLeigh B Stollerstoller@flux.utah.edu