1. 22 Feb, 2016 10 commits
  2. 19 Feb, 2016 3 commits
  3. 17 Feb, 2016 5 commits
  4. 16 Feb, 2016 1 commit
  5. 15 Feb, 2016 1 commit
  6. 14 Feb, 2016 4 commits
  7. 12 Feb, 2016 2 commits
  8. 11 Feb, 2016 3 commits
  9. 10 Feb, 2016 3 commits
  10. 09 Feb, 2016 3 commits
    • Kirk Webb's avatar
      Extend the horrible "non-modular" hack in the Cisco snmpit module. · 0981023d
      Kirk Webb authored
      First, a "bug fix": By coincidence the snmpit Cisco module was able to
      build up the mod/port-to-ifindex mapping on newer switches where
      interface descriptions include a submodule ID (e.g.
      "GigabitEthernet1/0/1" vs. "GigabitEthernet1/1"). However, it was
      actually just grabbing the submodule ID in place of the module ID.  This
      is OK (in some loose sense) for non-modular switches where everything is
      effectivley on the same module. Not good for IOS/NX-OS switches with
      actual modules and submodule identifiers. Things would not have worked
      for these.  As a fix that retains backward compatibility, the Cisco
      snmpit module now correctly extracts the module ID, but subtracts '1'
      from it.  This allows existing installations that have zero-based module
      numbering in their database for non-modular IOS/NX-OS switches with
      submodule IDs to continue to work as is.
      The above nonsense is not what I set out to do, however, and the commit
      just gets worse. I extended the hack for non-modular switches with a mix
      of gigabit and ten gigabit to bump any ten gigabit interface port's
      module ID to "1". The existing hack already did this for non-modular
      switches with a mix of fast Ethernet and gigabit.  Absolutely horrific.
      I need a shower.
    • Mike Hibler's avatar
      Fixups for configuring FreeBSD VMs. · 83718697
      Mike Hibler authored
    • Mike Hibler's avatar
      Fix setting of console on Xen command lines. · b6b227e3
      Mike Hibler authored
      Did this in the FreeBSD version previously.
  11. 08 Feb, 2016 2 commits
  12. 05 Feb, 2016 3 commits
    • Mike Hibler's avatar
      Make "reset" operation work for blockstores. · 0b90ef4f
      Mike Hibler authored
      Reset on local/remote blockstores ensures that there is no blockstore related
      state left in the root filesystem (e.g., mounts in /etc/fstab, iSCSI config,
      LVM/ZFS state). It does this in such a way that upon reboot, all the necessary
      state is recreated.
      What this means is that you should now be able to take an image of a node
      that uses blockstores and have that image actually work on another node!
      Previously, there could/would be leftover blockstore turds that would make
      the new image fail to boot.
      Of course, this won't work until the standard images are remade and will
      then only work for those images or images derived from them.
    • Mike Hibler's avatar
      When doing a "reset", reverse the order of the scripts. · 391c5224
      Mike Hibler authored
      This is when we are cleaning up to make an image. Seems like the correct
      thing to do is process the startup scripts in reverse order like we do for
      a "shutdown". Mostly this doesn't matter, but it does matter for the
      blockstore cleanup where we need to process the remote BSes before the locals.
    • Mike Hibler's avatar
      Short-term fix to handle size vs. deltasize. · 3d9550cd
      Mike Hibler authored
      We were always setting size, even for delta images. This will have to
      be revisited when we start doing image directories where we might have
      BOTH full and delta images.