1. 08 Aug, 2016 1 commit
  2. 06 Aug, 2016 1 commit
  3. 04 Aug, 2016 1 commit
  4. 03 Aug, 2016 4 commits
    • David Johnson's avatar
      Fix findcnet for newer udev reliable fixed device names. · bbb4ebe0
      David Johnson authored
      In the latest udev world, udev generates predictable device names using
      firmware info and/or pci buss info (i.e., eno1 or enps4f0).  So, we now
      try to run dhclient only on real ethernet devices (i.e., eth*, en*,
      sl*).  There are other kinds of ethernet devices (i.e. wireless, wl*,
      ww*) or virtual devices, but we don't care about finding the control net
      on those.  Might need to add another device name prefix for PV devices
      in Xen guests... we'll see.
      bbb4ebe0
    • David Johnson's avatar
      Workaround dhclient/resolvconf problem in Ubuntu 16. · c2bd98f6
      David Johnson authored
      This replaces the first attempt, which just masked the race condition,
      since I didn't understand what tmcc bossinfo was really doing.  This
      appears to fix it satisfactorily for now; it doesn't seem that we will
      run into the case where the file exists but has no nameserver.
      
        resolvconf on Linux also breaks DNS momentarily via dhclient exit
        hook, or something.  On Ubuntu 16, resolvconf is setup to run via
        dhclient enter hook (the hook redefines make_resolv_conf, which
        dhclient-script eventually executes prior to the exit hook execution).
        For whatever reason, though, sometimes when our exit hook (this
        script) runs, /etc/resolv.conf is a dangling symlink.  I was not able
        to find the source of the asynch behavior, so I can't say for sure.
        But sethostname.dhclient is an immediate casualty, because it calls
        tmcc bossinfo(), and the tmcc binary attempts to use res_init and read
        the resolver and use that as boss.  If there is no /etc/resolv.conf
        (or it is a broken symlink into /run, as it is on resolvconf systems
        before resolvconf runs for the first time on boot), res_init will
        return localhost, and there is no way for us in tmcc to know that is
        inappropriate (taking the res_init resolver might not be the best
        choice, but we do not dare to add a special-case rejection of
        localhost in tmcc).
      c2bd98f6
    • Mike Hibler's avatar
      Update pubsub port for KEEPALIVE fixes. · a3ea0297
      Mike Hibler authored
      a3ea0297
    • Leigh B Stoller's avatar
  5. 02 Aug, 2016 1 commit
  6. 01 Aug, 2016 1 commit
    • Leigh B Stoller's avatar
      Small DB changes for supporting secure transfer of datasets between · 43c7c976
      Leigh B Stoller authored
      clusters using credentials to provide permission to access the datasets.
      
      * Add authority_urn to the images table, which is the urn of the origin
        dataset (similar to the slice urn, the Portal mints a credential in
        its namespace, so that the Portal always has permission to do anything
        it wants to the dataset at the remote cluster).
      
      * Add slot to the apt_datasets table to store a credential from the
        cluster where the dataset lives. This credential gives the owner
        permission to download the dataset, which the portal will delegate to
        any cluster that might need to get that dataset.
      43c7c976
  7. 29 Jul, 2016 8 commits
  8. 28 Jul, 2016 5 commits
  9. 27 Jul, 2016 1 commit
  10. 26 Jul, 2016 4 commits
  11. 22 Jul, 2016 5 commits
  12. 21 Jul, 2016 8 commits