1. 14 Feb, 2019 1 commit
  2. 28 Jan, 2019 1 commit
  3. 22 Jan, 2019 1 commit
  4. 11 Jan, 2019 1 commit
  5. 12 Dec, 2018 1 commit
  6. 30 Jul, 2018 1 commit
  7. 16 Jul, 2018 1 commit
  8. 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
  9. 30 May, 2018 1 commit
  10. 21 May, 2018 1 commit
  11. 15 May, 2018 1 commit
  12. 19 Apr, 2018 1 commit
    • Leigh Stoller's avatar
      Minor changes to update keys: · c9faef6e
      Leigh Stoller authored
      1. Do not mark down nodes as needing to be updated, they just get stuck
         there.
      
      2. In the CM daemon, what for slivers/aggregates that have been stuck in
         updating users for too long, and cancel the update. Typically this is
         cause a node is wedged or not participating (CORD), so again just
         cancel and reset the state.
      c9faef6e
  13. 21 Nov, 2017 1 commit
  14. 20 Nov, 2017 2 commits
  15. 19 Nov, 2017 2 commits
  16. 23 Sep, 2017 1 commit
  17. 11 Sep, 2017 1 commit
  18. 30 Aug, 2017 3 commits
  19. 28 Aug, 2017 1 commit
  20. 12 Jul, 2017 1 commit
    • Leigh Stoller's avatar
      Improvements to the protogeni fcgid handler: · aeb3d617
      Leigh Stoller authored
      * Fix the logging that had been messed up for while; the logfile object
        was not defined in the children, needed a little reorg.
      
      * Add changes needed for SecureImageDownload(), which is a little
        messier with fcgid since we have to stream the image back to apache
        which means we need to reconnect the fcgid handler.
      
      * Add the CH module, seems to work fine.
      
      * Wrap the calls to cluster-wrapper.pl so that we can set an ENV
        variable indicating which module is being served, and then put this
        in the proc title; its very annoying that perl (sometime?) messes the
        with the proc title without permission from me, so I don't know what
        each server is serving since the command line options are gone.
      
      * Some tweaks to the apache config file.
      
      Note hat this is not running live yet, still just in my devel tree.
      aeb3d617
  21. 06 Jul, 2017 1 commit
  22. 06 Jun, 2017 1 commit
  23. 05 Jun, 2017 1 commit
    • Leigh Stoller's avatar
      Various fixes to bitrot on the Clearing House path. · bab98782
      Leigh Stoller authored
      We have not exercised the Clearing House path in a long time, since Utah
      is the only one that exists. But is we want external sites to use their
      own Portal interface, they need to be Geni enabled too, and that means
      having a Clearing House. For these sites, we make them their own
      Clearing House (a federation of one).
      
      This has been testing in a couple of elabinelab setups.
      bab98782
  24. 22 May, 2017 1 commit
  25. 17 Apr, 2017 1 commit
  26. 07 Mar, 2017 1 commit
  27. 25 Oct, 2016 1 commit
  28. 18 Oct, 2016 1 commit
  29. 16 Oct, 2016 1 commit
  30. 12 Oct, 2016 1 commit
  31. 06 Oct, 2016 1 commit
  32. 26 Sep, 2016 1 commit
  33. 29 Aug, 2016 4 commits