1. 26 Dec, 2017 1 commit
  2. 28 Nov, 2017 1 commit
  3. 27 Nov, 2017 1 commit
  4. 08 Aug, 2017 1 commit
  5. 18 May, 2017 1 commit
  6. 17 May, 2017 1 commit
  7. 05 May, 2017 1 commit
  8. 17 Apr, 2017 1 commit
    • Leigh B Stoller's avatar
      rspecs are so passe ... · 7c38809d
      Leigh B Stoller authored
      Redo the rspectogenilib converter with the goal of supporting both
      translation *and* regression testing. A new library is responsible for
      taking the output of libXML and creating a data structure representing
      the rspec. While this is being done, we look for any constructs or
      attributes we cannot handle with geni-lib and report that as an error;
      we are not going to convert an rspec unless we can do it correctly. and
      Regression testing is done with another part of this library, that knows
      how to compare each element of two rspecs. Basically start at the root
      and compare all the way down, failing if the two "parses" of the XML are
      not equal at any level.
      rspectogenilib now has an option that does regression testing by running
      the new geni-lib and comparing the resulting rspec against the original.
      On the UI side, there is a new button on existing rspec based
      profiles (currently only for admin and studs) called "Convert to
      geni-lib" that runs the converter to convert the profile to geni-lib.
      The user does not have to accept the new script of course.
      However, a converted profile is marked in the database, and the user can
      still use Jacks on it, we just run rspectogenilib geni-lib again on the
      new rspec. If the user edits the geni-lib, we switch back to normal
      geni-lib (clear the flag) when the new version is saved, and Jacks is
      once again read-only. This is explained in the UI, and is one of the
      things people need to give comment on.
      There is also a mode on the Create Profile page for converting new rspec
      based profiles to geni-lib, but that is fully turned off for now, we can
      get to that later.
  9. 30 Mar, 2017 2 commits
  10. 24 Mar, 2017 1 commit
    • Leigh B Stoller's avatar
      Profile changes: · 33b569e8
      Leigh B Stoller authored
      1. Finally, ajaxify the manage profile page. I never got around to doing
         this, and it made doing the thing I really wanted to do easier,
      2. Add a checkbox modal to ask the user if any accounts have been added,
         when doing initial clone of an experiment. We already did this with
         snapshot on the status page, but as above, it was going to be
         annoying to add to this page without reworking it.
      3. Improvements to repo-based profiles; when a push hook is executed, we
         were already updating the Repository Panel and the branch/tag list,
         but I wasn't updating the source code in the web page. Now we do that.
  11. 22 Mar, 2017 2 commits
  12. 20 Mar, 2017 2 commits
    • Leigh B Stoller's avatar
      Remove debugging code. · 298fec34
      Leigh B Stoller authored
    • Leigh B Stoller's avatar
      Support for push webhooks for repo-based profiles: · 10e12b53
      Leigh B Stoller authored
      We are running another apache server on boss, on port 51369, which
      invokes a backend perl script that maps the URL path argument to the
      profile, and then calls out to manage_profile to pull from the
      repository and update the profile to reflect the new HEAD branch.
      Using mod_rewrite in the apache config to restrict URLs to exactly
      the one URL that is accepted, modulo the value of the secret token.
      I had to refactor a bunch of code in manage_profile to make it easier to
      add a new entrypoint for modification from a git repo. This needed to be
      done for a long time, I had never cleaned up the original profile
      creation code.
      On the edit profile web page, there is a new row in the Repository panel
      providing the Push URL, and an explanatory help modal.
      There is a new slow polling timer that looks for a change to the repo
      hash and causes the web page to update in place from the repo, as when a
      push hook is invoked and changes the repo.
  13. 14 Mar, 2017 1 commit
  14. 02 Mar, 2017 1 commit
  15. 01 Mar, 2017 1 commit
  16. 03 Feb, 2017 1 commit
  17. 25 Jan, 2017 1 commit
  18. 28 Dec, 2016 1 commit
  19. 12 Nov, 2016 1 commit
    • Leigh B Stoller's avatar
      Bring the cluster monitor "inhouse", rather then depending on the jfed · d7c4230e
      Leigh B Stoller authored
      monitoring system.
      New portal_monitor daemon does a GetVersion/ListResources call at each
      of the clusters every five minutes, and updates the new table in the
      DB called apt_aggregate_status. We calculate free/inuse counts for
      physical nodes and a free count for VMs. Failure to contact the
      aggregate for more then 10 minutes sets the aggregate as down, since
      from our perspective if we cannot get to it, the cluster is down.
      Unlike the jfed monitoring system, we are not going to try to
      instantiate a new experiment or ssh into it. Wait and see if that is
      necessary in our context.
      On the instantiate page, generate a json structure for each cluster,
      similar the one described in issue #172 by Keith. This way we can easily
      switch the existing code over to this new system, but fail back to the
      old mechanism if this turn out to be a bust.
      Some other related changes to how we hand cluster into the several web
  20. 03 Nov, 2016 1 commit
  21. 21 Oct, 2016 1 commit
  22. 20 Oct, 2016 1 commit
  23. 11 May, 2016 1 commit
  24. 03 May, 2016 1 commit
  25. 26 Mar, 2016 1 commit
  26. 21 Dec, 2015 1 commit
  27. 08 Dec, 2015 1 commit
    • Kirk Webb's avatar
      Batch of changes that creates a PhantomNet portal branding. · ba49a457
      Kirk Webb authored
      Also includes some PhantomNet-specific restrictions (e.g. only
      allows use of the main Utah Emulab testbed  aggregate).
      This excercise stretched the limits of what we can reasonably do
      before introducing real per-testbed branding/policy mechanisms to
      the php/web front-end.  My changes ain't exactly pretty...
      Please take care when adding any testbed-specific changes to the
      code.  There are three flavors now to consider in the logic.
  28. 04 Dec, 2015 1 commit
  29. 02 Dec, 2015 1 commit
  30. 01 Dec, 2015 1 commit
  31. 10 Nov, 2015 1 commit
  32. 22 Sep, 2015 2 commits
  33. 17 Sep, 2015 2 commits
  34. 14 Sep, 2015 1 commit
  35. 10 Sep, 2015 1 commit