1. 06 Jun, 2016 5 commits
  2. 01 Jun, 2016 2 commits
    • Leigh B Stoller's avatar
      Kill debugging print. · 4224fc30
      Leigh B Stoller authored
      4224fc30
    • Leigh B Stoller's avatar
      Several sets of changes scattered across all these files. · 0f4a4dfb
      Leigh B Stoller authored
      * More on issue #54; watch for openstack experiments and try to download
        the new openstack stats file via the fast XMLRPC path. Show this as a
        text blob in a new tab on the status page, still need to graph the data.
        The apt_daemon handles the periodic request for the data (every 10
        minutes), which we store in the apt_instances table.
      
      * Addition for Rob on the admin extend page; Add a "more info" button that
        sends the contents of the text box as an email message requesting more
        info and stores that in the ongoing interaction log. Responses from the
        user are not stored though, might look at that someday.
      
      * Another addition for Rob; on the extensions list page, also show expired,
        locked down experiments. Note the sorting; at the top of the list are
        actual extension request (status='ready') while the bottom of the list
        are status='expired'.
      
      * Add a "graphs" tab to the status page, which shows the same idle stats
        graphs that were added to the admin extend page. Most of this change is
        refactoring the code and sharing it between the two pages.
      0f4a4dfb
  3. 25 May, 2016 1 commit
  4. 20 May, 2016 1 commit
  5. 03 May, 2016 1 commit
  6. 27 Apr, 2016 2 commits
  7. 25 Apr, 2016 2 commits
  8. 19 Apr, 2016 1 commit
  9. 14 Apr, 2016 1 commit
  10. 12 Apr, 2016 1 commit
  11. 06 Apr, 2016 1 commit
  12. 29 Mar, 2016 1 commit
  13. 26 Mar, 2016 2 commits
  14. 01 Mar, 2016 1 commit
    • Leigh B Stoller's avatar
      Some tweaks to credential handling: · 3ebffb34
      Leigh B Stoller authored
      1) Anytime we need to generate a slice credential, and the slice has
         expired, bump the slice expiration so we can create a valid credential
         and then reset the expiration. Consider if the slice expires but we
         missed it and its still active; we gotta be able to control it.
      
      2) From the beginning, we have done almost all RPC operations as the
         creator of the experiment. Made sense when the portal interface was not
         project aware, but now other users in the project can see and mess with
         experiments in their project. But we are still doing all the RPC
         operations as the creator of the experiment, which will need to change
         at some point, but in the short term I am seeing a lot of credential
         errors caused by an expired speaks-for credential for that creator (if
         they have not logged into the portal in a while). When this happens,
         lets generate a plain slice credential, issued to the SA, so that we can
         complete the operation. Eventually we have to make the backend project
         aware, and issue the operations as the web user doing the driving.
         Maybe as part of the larger portalization project.
      3ebffb34
  15. 25 Feb, 2016 1 commit
  16. 24 Feb, 2016 1 commit
  17. 17 Feb, 2016 1 commit
  18. 05 Feb, 2016 1 commit
  19. 27 Jan, 2016 1 commit
  20. 06 Jan, 2016 3 commits
    • Leigh B Stoller's avatar
      0bff7406
    • Leigh B Stoller's avatar
      When terminating an experiment, it is not an error if the slice is already · 5b2cf1c4
      Leigh B Stoller authored
      gone at the remote cluster.
      5b2cf1c4
    • Leigh B Stoller's avatar
      Add linktest support to the portal. Work in progress. · 2ed46ed2
      Leigh B 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
  21. 04 Jan, 2016 1 commit
  22. 22 Dec, 2015 1 commit
  23. 08 Dec, 2015 1 commit
  24. 01 Dec, 2015 1 commit
    • Leigh B Stoller's avatar
      Add support for cancelation; stopping an experiment setup early, instead of · 32c3d934
      Leigh B Stoller authored
      waiting till it finished setting up (or fails). This is really nice when a
      1000 node experiment has gone awry and it is pointless to wait for it to
      finish. When we do this, we mark the instance as canceled in the DB, and
      then wait for create_instance() to notice it. When it does, it stops
      waiting and invokes terminate with a new cancel option at the backend.
      32c3d934
  25. 05 Nov, 2015 1 commit
  26. 15 Oct, 2015 1 commit
    • Leigh B Stoller's avatar
      Two unrelated changes. · 6762e839
      Leigh B Stoller authored
      1. Use information from sliverstatus to indicate that nodes have startup
         execution services running, and then tell then when they have finished,
         and they exited with non-zero status, indicate that they failed. We also
         hold saying the "ready" in the upper panel until all the services have
         exited, we say "booted" instead, and also say that nodes are running
         startup services.
      
      2. For snapshot, when we know an image has to be copied back to its origin
         cluster, tell the web interface, so that we can add another step to the
         imaging modal ("copying"). We know the copy is done when the origin
         cluster has posted the new image data to the IMS, so we do an additional
         poll in the backend waiting for the image server to get the data, and
         then we mark the image as ready for use.
      6762e839
  27. 08 Oct, 2015 2 commits
  28. 07 Oct, 2015 1 commit
  29. 22 Sep, 2015 1 commit