1. 04 Feb, 2019 1 commit
  2. 04 Jun, 2018 1 commit
    • David Johnson's avatar
      Docker server-side core, esp new libimageops support for Docker images. · 66366489
      David Johnson authored
      The docker VM server-side goo is mostly identical to Xen, with slightly
      different handling for parent images.  We also support loading external
      Docker images (i.e. those without a real imageid in our DB; in that
      case, user has to set a specific stub image, and some extra per-vnode
      metadata (a URI that points to a Docker registry/image repo/tag);
      the Docker clientside handles the rest.
      
      Emulab Docker images map to a Emulab imageid:version pretty seamlessly.
      For instance, the Emulab `emulab-ops/docker-foo-bar:1` image would map
      to `<local-registry-URI>/emulab-ops/emulab-ops/docker-foo-bar:1`; the
      mapping is `<local-registry-URI>/pid/gid/imagename:version`.  Docker
      repository names are lowercase-only, so we handle that for the user; but
      I would prefer that users use lowercase Emulab imagenames for all Docker
      images; that will help us.  That is not enforced in the code; it will
      appear in the documentation, and we'll see.
      
      Full Docker imaging relies on several other libraries
      (https://gitlab.flux.utah.edu/emulab/pydockerauth,
      https://gitlab.flux.utah.edu/emulab/docker-registry-py).  Each
      Emulab-based cluster must currently run its own private registry to
      support image loading/capture (note however that if capture is
      unnecessary, users can use the external images path instead).  The
      pydockerauth library is a JWT token server that runs out of boss's
      Apache and implements authn/authz for the per-Emulab Docker registry
      (probably running on ops, but could be anywhere) that stores images and
      arbitrates upload/download access.  For instance, nodes in an experiment
      securely pull images using their pid/eid eventkey; and the pydockerauth
      emulab authz module knows what images the node is allowed to pull
      (i.e. sched_reloads, the current image the node is running, etc).  Real
      users can also pull images via user/pass, or bogus user/pass + Emulab
      SSL cert.  GENI credential-based authn/z was way too much work, sadly.
      There are other auth/z paths (i.e. for admins, temp tokens for secure
      operations) as well.
      
      As far as Docker image distribution in the federation, we use the same
      model as for regular ndz images.  Remote images are pulled in to the
      local cluster's Docker registry on-demand from their source cluster via
      admin token auth (note that all clusters in the federation have
      read-only access to the entire registries of any other cluster in the
      federation, so they can pull images).  Emulab imageid handling is the
      same as the existing ndz case.  For instance, image versions are lazily
      imported, on-demand; local version numbers may not match the remote
      image source cluster's version numbers.  This will potentially be a
      bigger problem in the Docker universe; Docker users expect to be able to
      reference any image version at any time anywhere.  But that is of course
      handleable with some ex post facto synchronization flag day, at least
      for the Docker images.
      
      The big new thing supporting native Docker image usage is the guts of a
      refactor of the utils/image* scripts into a new library, libimageops;
      this is necessary to support Docker images, which are stored in their
      own registry using their own custom protocols, so not amenable to our
      file-based storage.  Note: the utils/image* scripts currently call out
      to libimageops *only if* the image format is docker; all other images
      continue on the old paths in utils/image*, which all still remain
      intact, or minorly-changed to support libimageops.
      
      libimageops->New is the factory-style mechanism to get a libimageops
      that works for your image format or node type.  Once you have a
      libimageops instance, you can invoke normal image logical operations
      (CreateImage, ImageValidate, ImageRelease, et al).  I didn't do every
      single operation (for instance, I haven't yet dealt with image_import
      beyond essentially generalizing DownLoadImage by image format).
      Finally, each libimageops is stateless; another design would have been
      some statefulness for more complicated operations.   You will see that
      CreateImage, for instance, is written in a helper-subclass style that
      blurs some statefulness; however, it was the best match for the existing
      body of code.  We can revisit that later if the current argument-passing
      convention isn't loved.
      
      There are a couple outstanding issues.  Part of the security model here
      is that some utils/image* scripts are setuid, so direct libimageops
      library calls are not possible from a non-setuid context for some
      operations.  This is non-trivial to resolve, and might not be worthwhile
      to resolve any time soon.  Also, some of the scripts write meaningful,
      traditional content to stdout/stderr, and this creates a tension for
      direct library calls that is not entirely resolved yet.  Not hard, just
      only partly resolved.
      
      Note that tbsetup/libimageops_ndz.pm.in is still incomplete; it needs
      imagevalidate support.  Thus, I have not even featurized this yet; I
      will get to that as I have cycles.
      66366489
  3. 13 Dec, 2017 1 commit
  4. 06 Oct, 2017 1 commit
  5. 05 Oct, 2017 1 commit
  6. 24 Jul, 2017 1 commit
  7. 05 Jun, 2017 1 commit
    • Leigh Stoller's avatar
      Working on issue #269 ... · ad2a3e70
      Leigh Stoller authored
      Add new script to "deprecate" images:
      
      	boss> wap deprecate_image
      	Usage: deprecate_image [-e|-w] <image> [warning message to users]
      	Options:
      	       -e     Use of image is an error; default is warning
      	       -w     Use of image is a warning
      
      When an image is deprecated with just warnings, new classic experiments
      generate warnings in the output. Swapping in an experiment also
      generates warnings in the output, but also sends email to the user.
      When the image set for error, both new experiment and swapin will fail
      with prejudice.
      
      Same deal on the Geni path; we generate warnings/errors and send email.
      Errors are reflected back in the Portal interface.
      
      At the moment the image server knows nothing about deprecated images, so
      the Portal constraint checker will not be bothered nor tell the user
      until later when the cluster throws an error. As a result, when we
      deprecate an image, we need to do it on all clusters. Needs to think
      about this a bit more.
      ad2a3e70
  8. 14 Mar, 2017 2 commits
    • Leigh Stoller's avatar
      Minor cleanup and fixes: · ad48bbdb
      Leigh Stoller authored
      1. Small bits of cleanup to remove hardwired paths and test for images
         that live in /usr/testbed and need special handling.
      
      2. Make sure that the image directory exists in /proj when taking a
         snapshot of a system image that lives in /usr/testbed since that is
         were we always write new images.
      
      3. When deleting an image, remove the DB state for the highest numbered
         version if it never came ready/released.
      ad48bbdb
    • Leigh Stoller's avatar
      Remove test for deleted from NewVersion(), turns out that a quirk of how · 7c345c85
      Leigh Stoller authored
      I implemented versioning for images make this test the wrong thing to
      do. I need to come back and change this, but its not a big deal right
      now.
      7c345c85
  9. 09 Mar, 2017 2 commits
  10. 07 Mar, 2017 1 commit
  11. 06 Mar, 2017 1 commit
  12. 01 Mar, 2017 1 commit
  13. 21 Feb, 2017 1 commit
  14. 07 Feb, 2017 1 commit
  15. 25 Jan, 2017 1 commit
  16. 03 Jan, 2017 1 commit
  17. 17 Oct, 2016 1 commit
  18. 12 Oct, 2016 1 commit
  19. 06 Oct, 2016 1 commit
  20. 29 Aug, 2016 2 commits
  21. 20 Jul, 2016 1 commit
  22. 22 Mar, 2016 2 commits
  23. 21 Mar, 2016 2 commits
  24. 20 Mar, 2016 1 commit
  25. 10 Nov, 2015 1 commit
  26. 02 Nov, 2015 1 commit
  27. 30 Oct, 2015 1 commit
  28. 03 Sep, 2015 1 commit
  29. 25 Aug, 2015 1 commit
    • Leigh Stoller's avatar
      Add a new table image_boot_status to record boot success/failure each time · 4fa9d2ea
      Leigh Stoller authored
      an image is loaded on a node. We want to know both success and failure over
      time so that we can determine when a image works or does not work on a
      particular node/type. This is primarily for the image tracker to determine
      what images work on what node types, but might be useful for in other
      situations. I realize this duplicates some info we already have in the
      image_history table, but that does not record failure, only success, and it
      mostly concerned with who is using what images.
      4fa9d2ea
  30. 21 Aug, 2015 1 commit
  31. 26 Jun, 2015 1 commit
  32. 25 Jun, 2015 1 commit
  33. 24 Jun, 2015 1 commit
  34. 19 Jun, 2015 1 commit
  35. 29 May, 2015 1 commit