1. 27 Jan, 2016 5 commits
  2. 26 Jan, 2016 2 commits
  3. 22 Jan, 2016 2 commits
  4. 21 Jan, 2016 6 commits
  5. 20 Jan, 2016 2 commits
  6. 15 Jan, 2016 1 commit
  7. 14 Jan, 2016 6 commits
  8. 12 Jan, 2016 1 commit
  9. 11 Jan, 2016 1 commit
  10. 09 Jan, 2016 4 commits
  11. 08 Jan, 2016 2 commits
  12. 06 Jan, 2016 8 commits
    • Leigh Stoller's avatar
      Nuts, my approach for catching early linktest errors is not going to work · 1f145671
      Leigh Stoller authored
      all the time, so bail on that and fallback to reporting errors solely
      though the spew log(s).
      1f145671
    • Leigh Stoller's avatar
      0bff7406
    • Leigh Stoller's avatar
      Minor bug fix; restore the progress bar. · 6d14d4e7
      Leigh Stoller authored
      6d14d4e7
    • Leigh Stoller's avatar
      3980979d
    • Leigh Stoller's avatar
      When terminating an experiment, it is not an error if the slice is already · 5b2cf1c4
      Leigh Stoller authored
      gone at the remote cluster.
      5b2cf1c4
    • Leigh Stoller's avatar
      Add linktest support to the portal. Work in progress. · 2ed46ed2
      Leigh Stoller authored
      * A new Start Linktest button is in the bottom right of the topology tab.
      
      * When started, we create a new tab to display the linktest output
        (currently the unmodified output from Classic emulab linktest). The state
        of the experiment is change to linktest to prevent further action on the
        experiment, except of course for stop linktest.
      
      * When linktest is running, there is a Stop Linktest button in the upper
        collapse panel. This will stop linktest in its tracks, but the tabs
        remain. When you kill a linktest tab while linktest is running, linktest
        continues running, you have to use the Stop button.
      
      * I have added a small help document to the templates directory that the
        user is shown when they click on the ? mark in the linktest modal.
        Written in markdown format, it is a culling of text from the Emulab wiki
        linktest page.
      
      Caveats:
      
      * Because of polling, there is a short (5-15 seconds) delay before the
        experiment is returned to the ready state. Not much to do about this in a
        polling world. Wouldn't callbacks be nice?
      
      * Linktest can be used on a multisite topology, although cross site links
        cannot be tested at this point. Links/Lans that are contained entirely to
        one site or the other are testable though. We build a new tab for each
        site to spew the linktest output.
      2ed46ed2
    • Leigh Stoller's avatar
      Minor bug fix. · f7f97d7f
      Leigh Stoller authored
      f7f97d7f
    • Leigh Stoller's avatar
      Export linktest via the CM API. · 58640e2c
      Leigh 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.
      58640e2c