1. 15 Aug, 2017 1 commit
  2. 14 Aug, 2017 2 commits
  3. 08 Aug, 2017 1 commit
    • Leigh Stoller's avatar
      Reservation system changes: · c7c93e9f
      Leigh Stoller authored
      1. Allow uuids to be used to specify reservations, change pretty much
         everything in the web interface to use uuid's so we stop exporting
         databases indexes to the client side.
      2. Change RPC path to return a blob of data when approving a
         reservation. Ditto for initial creation, so that we can see precisely
         what the local cluster has done.
      3. When a reservation is created/approved, insert an announcement in the
         announce system for that user, set to go off 24 hours ahead of
         reservation. Update that announcement when reservation is modified.
  4. 25 Jul, 2017 1 commit
    • Leigh Stoller's avatar
      Add two new options to CreateImage(): · a7a3bc78
      Leigh Stoller authored
      1. nosnapshot; create the descriptor (clone_image) but do not start the
         imaging process (create_image).
      2. mustnotexist: Must be a new image in the project or return error.
  5. 13 Jul, 2017 1 commit
  6. 12 Jul, 2017 1 commit
    • Leigh Stoller's avatar
      Improvements to the protogeni fcgid handler: · aeb3d617
      Leigh Stoller authored
      * Fix the logging that had been messed up for while; the logfile object
        was not defined in the children, needed a little reorg.
      * Add changes needed for SecureImageDownload(), which is a little
        messier with fcgid since we have to stream the image back to apache
        which means we need to reconnect the fcgid handler.
      * Add the CH module, seems to work fine.
      * Wrap the calls to cluster-wrapper.pl so that we can set an ENV
        variable indicating which module is being served, and then put this
        in the proc title; its very annoying that perl (sometime?) messes the
        with the proc title without permission from me, so I don't know what
        each server is serving since the command line options are gone.
      * Some tweaks to the apache config file.
      Note hat this is not running live yet, still just in my devel tree.
  7. 10 Jul, 2017 1 commit
    • Leigh Stoller's avatar
      Changes to InUse: · e7fad93e
      Leigh Stoller authored
      1) Include URN of pre-reserve project so that it can be mapped back to
         local project at the caller.
      2) Return freecount info as determined by Reservation->Freecount() so we
         can show adjusted numbers.
  8. 07 Jul, 2017 1 commit
    • Leigh Stoller's avatar
      Deal with user privs (issue #309): · d1516912
      Leigh Stoller authored
      * Make user privs work across remote clusters (including stitching). I
        took a severe shortcut on this; I do not expect the Cloudlab portal
        will ever talk to anything but an Emulab based aggregate, so I just
        added the priv indicator to the user keys array we send over. If I am
        ever proved wrong on this, I will come out of retirement and fix
        it (for a nominal fee of course).
      * Do not show the root password for the console to users with user
      * Make sure users with user privs cannot start experiments.
      * Do show the user trust values on the user dashboard membership tab.
      * Update tmcd to use the new privs slot in the nonlocal_user_accounts
      This closes issue #309.
  9. 06 Jul, 2017 3 commits
  10. 28 Jun, 2017 1 commit
  11. 26 Jun, 2017 1 commit
  12. 22 Jun, 2017 1 commit
  13. 21 Jun, 2017 1 commit
  14. 20 Jun, 2017 2 commits
  15. 16 Jun, 2017 1 commit
  16. 09 Jun, 2017 1 commit
  17. 07 Jun, 2017 1 commit
  18. 06 Jun, 2017 1 commit
  19. 05 Jun, 2017 3 commits
    • Leigh Stoller's avatar
      Various fixes to bitrot on the Clearing House path. · bab98782
      Leigh Stoller authored
      We have not exercised the Clearing House path in a long time, since Utah
      is the only one that exists. But is we want external sites to use their
      own Portal interface, they need to be Geni enabled too, and that means
      having a Clearing House. For these sites, we make them their own
      Clearing House (a federation of one).
      This has been testing in a couple of elabinelab setups.
    • Leigh Stoller's avatar
      Working on issue #269 ... · ad2a3e70
      Leigh Stoller authored
      Add new script to "deprecate" images:
      	boss> wap deprecate_image
      	Usage: deprecate_image [-e|-w] <image> [warning message to users]
      	       -e     Use of image is an error; default is warning
      	       -w     Use of image is a warning
      When an image is deprecated with just warnings, new classic experiments
      generate warnings in the output. Swapping in an experiment also
      generates warnings in the output, but also sends email to the user.
      When the image set for error, both new experiment and swapin will fail
      with prejudice.
      Same deal on the Geni path; we generate warnings/errors and send email.
      Errors are reflected back in the Portal interface.
      At the moment the image server knows nothing about deprecated images, so
      the Portal constraint checker will not be bothered nor tell the user
      until later when the cluster throws an error. As a result, when we
      deprecate an image, we need to do it on all clusters. Needs to think
      about this a bit more.
    • Leigh Stoller's avatar
      Fix this, not sure what I was thinking. · b7d65aa3
      Leigh Stoller authored
  20. 02 Jun, 2017 2 commits
  21. 30 May, 2017 1 commit
    • Leigh Stoller's avatar
      Rework how we store the sliver/slice status from the clusters: · e5d36e0d
      Leigh Stoller authored
      In the beginning, the number and size of experiments was small, and so
      storing the entire slice/sliver status blob as json in the web task was
      fine, even though we had to lock tables to prevent races between the
      event updates and the local polling.
      But lately the size of those json blobs is getting huge and the lock is
      bogging things down, including not being able to keep up with the number
      of events coming from all the clusters, we get really far behind.
      So I have moved the status blobs out of the per-instance web task and
      into new tables, once per slice and one per node (sliver). This keeps
      the blobs very small and thus the lock time very small. So now we can
      keep up with the event stream.
      If we grow big enough that this problem comes big enough, we can switch
      to innodb for the per-sliver table and do row locking instead of table
      locking, but I do not think that will happen
  22. 23 May, 2017 1 commit
  23. 22 May, 2017 5 commits
  24. 18 May, 2017 1 commit
  25. 16 May, 2017 1 commit
  26. 09 May, 2017 1 commit
  27. 08 May, 2017 1 commit
  28. 25 Apr, 2017 2 commits