1. 01 Mar, 2017 3 commits
  2. 28 Feb, 2017 1 commit
  3. 25 Jan, 2017 1 commit
  4. 09 Jan, 2017 1 commit
  5. 29 Nov, 2016 1 commit
    • Leigh B Stoller's avatar
      Fix two small problems with Addnode/Deletenode. · fd9bd976
      Leigh B Stoller authored
      1. Do not start a second copy of the event scheduler. This is the cause
         of all the slurm error messages on the APT cluster. Clearly this was
         wrong for DeleteNode(). AddNode is still open for debate, but at
         least now the error mail will stop.
      2. Do not reset the startstatus either, this was causing web interface
         to think startup services were running, when in fact they are not
         since the other nodes are not rebooted. In the classic interface,
         node reboot does not change the startstatus either, so lets mirror
         that in the Geni interface.
  6. 07 Nov, 2016 1 commit
    • Leigh B Stoller's avatar
      Some work on restarting (rebooting) nodes. Presently, there is a bit of · 18cdfa8b
      Leigh B Stoller authored
      an inconsistency in SliverAction(); when operating on the entire slice
      we do the whole thing in the background, returning (almost) immediately.
      Which makes sense, we expect the caller to poll for status after.
      But when operating on a subset of slivers (nodes), we do it
      synchronously, which means the caller is left waiting until we get
      through rebooting all the nodes. As David pointed out, when rebooting
      nodes in the openstack profile, this can take a long time as the VMs are
      torn down. This leaves the user looking at a spinner modal for a long
      time, which is not a nice UI feature.
      So I added a local option to do slivers in the background, and return
      immediately. I am doing the for restart and reload at the moment since
      that is primarily what we use from the Portal.
      Note that this has to push out to all clusters.
  7. 02 Nov, 2016 1 commit
  8. 10 Oct, 2016 1 commit
    • Leigh B Stoller's avatar
      Address linktest problems reported by Mike in issue #160: · e7422d49
      Leigh B Stoller authored
      1. Changes to gentopofile to not put in linktest info for links and lan
         with only one member.
      2. Fix to the CM for deletenode of a node that has tagged links.
      3. Fixes to the status web page for deletenode; we were installing the
         linktest event handlers multiple times.
      4. Pass through -N argument to linktest from the CM, when the experiment
         has NFS mounts turned off, so that we use loghole to gather the data
         files (instead of via NFS).
      This closes issues #160.
  9. 06 Oct, 2016 1 commit
  10. 26 Sep, 2016 1 commit
  11. 29 Aug, 2016 2 commits
  12. 20 Jul, 2016 1 commit
  13. 11 Jul, 2016 1 commit
  14. 18 May, 2016 1 commit
  15. 04 May, 2016 1 commit
  16. 06 Apr, 2016 1 commit
  17. 08 Mar, 2016 1 commit
  18. 25 Feb, 2016 1 commit
  19. 22 Feb, 2016 1 commit
  20. 27 Jan, 2016 1 commit
    • Leigh B Stoller's avatar
      Anytime the state for a slice or sliver changes, inject a geni style event · bc8afd40
      Leigh B Stoller authored
      into the local event stream. These events are different then normal emulab
      events in that the SITE is set to the URN of the aggregate, and there is
      json representation of the slice/sliver status. There are other fields as
      well that are not in normal emulab events. These events can mix okay with
      emulab events on the local boss, nothing will care about them. But they
      will get forwarded to pubsubd at the portal if CLUSTER_PORTAL is set in the
      defs file.
  21. 06 Jan, 2016 2 commits
    • Leigh B Stoller's avatar
      Nuts, my approach for catching early linktest errors is not going to work · 1f145671
      Leigh B Stoller authored
      all the time, so bail on that and fallback to reporting errors solely
      though the spew log(s).
    • Leigh B Stoller's avatar
      Export linktest via the CM API. · 58640e2c
      Leigh B Stoller authored
      * Three actions are exported; start, stop, and status. The last is cause we
        have to poll to determine when linktest has actually finished or stopped.
        I hate all this polling.
      * For start, linktest can be performed synchronously, which is fine on a
        small experiment, but in general you want to use the async option and
        check back later. When using async, we return the spewlog URL to the
        caller so that linktest can be monitored.
      * A couple of minor changes to linktest itself for using a spew log.
      * Some simple test rspecs and a linktest.py driver.
  22. 15 Dec, 2015 1 commit
  23. 08 Dec, 2015 1 commit
  24. 01 Dec, 2015 1 commit
    • Leigh B Stoller's avatar
      Add cancel support. The idea is that a DeleteSlice() with our internal · 5bd9ad1a
      Leigh B Stoller authored
      cancel option, will stop a CreateSliver() in its tracks. We stop the
      monitor, then cleanup the slice. I also added an optimization for tearing
      down large numbers of VMs on shared nodes, previously we were doing them
      one at a time. Note that only the Portal is going to use this option, since
      it loosely depends on code in the XEN clientside (described in another
  25. 10 Nov, 2015 1 commit
  26. 15 Oct, 2015 1 commit
  27. 12 Oct, 2015 2 commits
  28. 06 Oct, 2015 2 commits
  29. 24 Sep, 2015 1 commit
    • Leigh B Stoller's avatar
      Add AddNodes and DeleteNodes, which are convenience functions for the HPC · c3339c9d
      Leigh B Stoller authored
      AddNodes($slice_urn, $credentials, $nodes):
      The "nodes" argument is a hash that looks like:
        {"node45" : {"diskimage" : "urn...",
                     "startup"   : "/bin/echo",
                     "tarballs"  : ["tarball1", "tarball2", ...],
                     "lans"      : ["lan1", "lan2", ...]
                     "node"      : "pc189"},
         "nodeXX" : {...}}
      DeleteNodes($slice_urn, $credentials, $nodes):
      The "nodes" argument is a list like:
        ["node45", ...]
      Any node can be deleted, but it is not yet clear what happens if all the
      nodes of a lan are removed. I probably need to do some work there, but
      David can start with this.
  30. 14 Sep, 2015 1 commit
  31. 31 Aug, 2015 1 commit
  32. 21 Aug, 2015 1 commit
  33. 29 Jul, 2015 1 commit
  34. 13 Jul, 2015 1 commit