1. 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.
  2. 16 Nov, 2015 1 commit
  3. 13 Nov, 2015 2 commits
  4. 29 Oct, 2015 1 commit
  5. 28 Oct, 2015 2 commits
  6. 27 Oct, 2015 1 commit
    • Leigh B Stoller's avatar
      Add simple (initial) support passing encrypted secrets to the cluster CM, · 46757729
      Leigh B Stoller authored
      to be decrypted using the per-exp ssl keypair we create and store on the
      nodes. In this case, you can add this to your rspec in the node element.
      You can add as many as you want, use the name attribute. We generate a
      random password and encrypt the plain text:
      which becomes:
          <emulab:password name="foo" encrypted="true">-----BEGIN PKCS7-----
      -----END PKCS7-----
      which can then be decrypted using the private key to get the plaintext
  7. 25 Oct, 2015 1 commit
  8. 22 Oct, 2015 1 commit
  9. 21 Oct, 2015 1 commit
  10. 20 Oct, 2015 1 commit
  11. 19 Oct, 2015 1 commit
  12. 15 Oct, 2015 2 commits
    • Leigh B Stoller's avatar
      Remove debugging code. · 5295bf87
      Leigh B Stoller authored
    • 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.
  13. 05 Oct, 2015 1 commit
  14. 25 Sep, 2015 1 commit
  15. 24 Sep, 2015 1 commit
  16. 22 Sep, 2015 1 commit
  17. 15 Sep, 2015 1 commit
  18. 14 Sep, 2015 1 commit
  19. 08 Sep, 2015 1 commit
  20. 03 Sep, 2015 1 commit
  21. 31 Aug, 2015 2 commits
  22. 21 Aug, 2015 3 commits
  23. 12 Aug, 2015 1 commit
  24. 04 Aug, 2015 1 commit
  25. 30 Jul, 2015 1 commit
  26. 29 Jul, 2015 1 commit
  27. 27 Jul, 2015 1 commit
  28. 07 Jul, 2015 2 commits
  29. 06 Jul, 2015 1 commit
  30. 30 Jun, 2015 1 commit
  31. 25 Jun, 2015 2 commits
    • Leigh B Stoller's avatar
      Minor bug fix, some extra debugging. · 3cfa7603
      Leigh B Stoller authored
    • Leigh B Stoller's avatar
      Add new options to CreateSliver/Provision; supply an x509 certificate and · 8be26639
      Leigh B Stoller authored
      private key.
      The goal is to distribute an experiment wide certificate and private
      key. At the moment this is just a self signed x509 certificate and the
      accompanying rsa key. In PEM format. The same cert/key will be distributed
      across multiple aggregates.
      An openssh key pair can be trivially derived from the private key. Or the
      public part can be derived from the certificate. A quick google will show
      Initially, you will need to run tmcc directly to get them, using the
      geni_certificate and geni_key commands.
  32. 19 Jun, 2015 1 commit
    • Leigh B Stoller's avatar
      New support for importing image backed datasets from other clusters. This · 613d90dd
      Leigh B Stoller authored
      is just like importing images (by using a url instead of a urn), which
      makes sense since image backed datasets are just images with a flag set.
      Key differences:
      1. You cannot snapshot a new version of the dataset on a cluster it has
         been imported to. The snapshot has to be done where the dataset was
         created initially. This is slightly inconvenient and will perhaps
         confuse users, but it is far less confusing that then datasets getting
         out of sync.
      2. No image versioning of datasets. We can add that later if we want to.