1. 15 May, 2015 2 commits
    • Leigh B Stoller's avatar
    • Leigh B Stoller's avatar
      Directory based image paths. · 3a21f39e
      Leigh B Stoller authored
      Soon, we will have images with both full images and deltas, for the same
      image version. To make this possible, the image path will now be a
      directory instead of a file, and all of the versions (ndz,sig,sha1,delta)
      files will reside in the directory.
      A new config variable IMAGEDIRECTORIES turns this on, there is also a check
      for the ImageDiretories feature. This is applied only when a brand new
      image is created; a clone version of the image inherits the path it started
      with. Yes, you can have a mix of directory based and file based image
      When it is time to convert all images over, there is a script called
      imagetodir that will go through all image descriptors, create the
      directory, move/rename all the files, and update the descriptors.
      Ultimately, we will not support file based image paths.
      I also added versioning to the image metadata descriptors so that going
      forward, old clients can handle a descriptor from a new server.
  2. 13 May, 2015 2 commits
  3. 08 May, 2015 1 commit
  4. 06 May, 2015 1 commit
    • David Johnson's avatar
      Bug Fix: make port lookup distinguish logical/physical wires. · 8e1064ae
      David Johnson authored
      The stuff in db/Port.pm (Port::LookupByIface) wasn't handling the MLE
      case where there are two wires table entries for physical wires with a
      logical wire implemented by them; for my experiment, when snmpit was
      trying to create the physical vlans on the apcon, it would grab the
      logical wire instead of the physical one as it populated the Port
      objects, and that screwed vlan creation up (the member port for the
      physical layer 1 vlan gets labeled with a switch WIRE_END instead of
      node -- which is correct for the logical wire, but not the physical).
      So, I changed the query to check that wires.logical ==
      interfaces.logical ; see the code.  This is a limited fix, maybe --
      maybe that method should really do more verification to make sure it's
      grabbed the correct wires table entry -- but since we only have 2 layers
      it's plenty good for now.
  5. 04 May, 2015 1 commit
  6. 30 Apr, 2015 1 commit
  7. 26 Apr, 2015 1 commit
  8. 24 Apr, 2015 1 commit
  9. 06 Apr, 2015 1 commit
  10. 27 Mar, 2015 1 commit
  11. 24 Mar, 2015 1 commit
  12. 23 Mar, 2015 1 commit
  13. 19 Mar, 2015 1 commit
  14. 15 Mar, 2015 3 commits
  15. 13 Mar, 2015 3 commits
    • Jonathon Duerig's avatar
    • Gary Wong's avatar
    • Leigh B Stoller's avatar
      Checkpoint various changes. · 0d09773b
      Leigh B Stoller authored
      * Various UI tweaks for profile versioning.
      * Roll out profile versioning for all users.
      * Disable/Hide publishing for now.
      * Move profile/version URLs into a modal that is invoked by a new Share
        button, that explains things a little better.
      * Unify profile permissions between APT/Cloudlab. Users now see just two
        choices; project or anyone, where anyone includes guest users in the APT
        interface, for now.
      * Get rid of "List on the front page" checkbox, all public profiles will be
        listed, but red-dot can still set that bit.
      * Return the publicURL dynamically in the status blob, and set/show the
        sliver info button as soon as we get it.
      * Console password support; if the aggregate returns the console password,
        add an item to the context menu to show it.
      * Other stuff.
  16. 12 Mar, 2015 1 commit
  17. 11 Mar, 2015 2 commits
  18. 10 Mar, 2015 5 commits
  19. 05 Mar, 2015 1 commit
  20. 25 Feb, 2015 1 commit
  21. 04 Feb, 2015 3 commits
  22. 31 Jan, 2015 1 commit
  23. 28 Jan, 2015 1 commit
    • Mike Hibler's avatar
      Implement "plan 1" for dataset sharing: "ephemeral RO snapshots". · 7aefdaa1
      Mike Hibler authored
      You can now simultaneously RW and RO map a dataset because all the RO
      mappings use copies (clones) of a snapshot. Only a single RW mapping
      of course.
      When the RW mapping swaps out it automatically creates a new snapshot.
      So there is currently no user control over when a version of the dataset
      is "published", it just happens everytime you swapout an experiment with
      a RW mapping.
      A new RW mapping does not affect current RO mappings of course as they
      continue to use whatever snapshot they were created with. New RO mappings
      with get the most recent snapshot, which we currently track in the DB via
      the per-lease attribute "last_snapshot".
      You can also now declare a lease to be "exclusive use" by setting the
      "exclusive_use" lease attribute (via modlease). This means that it follows
      the old semantics of only one mapping at a time, whether it be RO or RW.
      This is an alternative to the "simultaneous_ro_datasets" sitevar which
      enforces the old behavior globally. Primarily, I put this attribute in to
      prevent an unexpected failure in the snapshot/clone path from wreaking
      havoc over time. I don't know if there is any value in exposing this to
      the user.
  24. 27 Jan, 2015 2 commits
  25. 26 Jan, 2015 2 commits