1. 06 Mar, 2019 1 commit
  2. 01 Mar, 2019 2 commits
  3. 27 Feb, 2019 1 commit
  4. 19 Feb, 2019 3 commits
  5. 15 Feb, 2019 3 commits
  6. 13 Feb, 2019 1 commit
  7. 12 Feb, 2019 2 commits
    • Leigh B Stoller's avatar
      Fixes to previous revision. · 74e3d7c0
      Leigh B Stoller authored
    • Leigh B Stoller's avatar
      Recovery mode: · bde6c94d
      Leigh B Stoller authored
      * Add a new Portal context menu option to nodes, to boot into "recovery"
        mode, which will be a Linux MFS (rather then the FreeBSD MFS, which
        99% of user will not know what to do with).
      * Plumb all through to the Geni RPC interface, which invokes node_admin
        with a new option, to use the recovery mfs nodetype attribute.
      * recoverymfs_osid is a distinct osid from adminmfs_osid, we use that in
        the CM to add an Emulab name space attribute to the manifest, that
        tells the Portal that a node supports recovery mode (and thus gets a
        context menu option).
      * Add an inrecovery flag to the sliver status blob, which the Portal
        uses to determine that a node is currently in recovery mode, so that
        we can indicate that in the topology and list tabs.
  8. 11 Feb, 2019 2 commits
  9. 08 Feb, 2019 4 commits
    • Leigh B Stoller's avatar
      Changes to the snapshot modal as discussed on 1/21/2019: · 1de19201
      Leigh B Stoller authored
      * When the profile is script based, we cannot update the profile code,
        so do not show any choices (radios), proceed as image only.
      * Remove the "new profile" (3rd) option, it appears that no one at the
        meeting knew what that was about, so clearly mere users won't. Simplify!
      * Rearrange the options (whole disk, account), together at the bottom.
      * Swap the description and the image name inputs.
      * Cleanup the help popovers and impl.
    • Leigh B Stoller's avatar
      Another set of changes for new geni-lib parameters. · 59259db3
      Leigh B Stoller authored
      * Use an emulabfeature to control what projects use the new ppwizard and
        geni-lib code. The feature is applied to the profile's project, since
        who is instantiating and what project it is instantiated into, does
        not really matter, the incompatible changes are also associated with
        the profile.
      * Run both versions of the ppwizard side by side, and flip between them
        when the user is using the profile picker.
      * The new version of geni-lib is /usr/testbed/opsdir/lib/geni-lib.new,
        we tell the genilab jail to use that directory when on the new path.
      * All of this is temporary.
    • Leigh B Stoller's avatar
      Checkpoint new geni-lib param code, working on making it selectable · dedc6495
      Leigh B Stoller authored
      via emulab features, for testing.
    • Leigh B Stoller's avatar
      Fix to Jacks constraint stuff: · 3c5e82d6
      Leigh B Stoller authored
      Problem: A user with a reservation at one cluster, was trying to start
      an experiment at a different cluster. But after selecting the other
      cluster and clicking next, that selection was being reset to the cluster
      with the reservation, as part of our overly helpful cluster picker code,
      which is fired off in a callback from Jacks.
      Question: Why is that happening when clicking next, to go from the
      Finalize step to the Schedule step, thus silently resetting the user's
      Reason: There is a call to SwitchJacks("small") to make sure that the
      small version of the topo was visible, in case the user goes back to the
      finalize step. Not sure why ... but in any event, every call to
      SwitchJacks(large|small) results in Jacks firing that callback, and
      resetting the user's cluster choice.
      Solution: Null out the callback when calling SwitchJacks().
      There is probably a better solution to this, perhaps as part of a code
      reorg on the entire instantiate page, which has grown many appendages
      over time.
  10. 07 Feb, 2019 1 commit
  11. 04 Feb, 2019 1 commit
  12. 01 Feb, 2019 3 commits
  13. 07 Jan, 2019 1 commit
  14. 02 Jan, 2019 1 commit
  15. 13 Dec, 2018 1 commit
  16. 12 Dec, 2018 3 commits
  17. 06 Dec, 2018 4 commits
  18. 30 Nov, 2018 1 commit
  19. 28 Nov, 2018 2 commits
  20. 27 Nov, 2018 1 commit
  21. 14 Nov, 2018 2 commits