1. 21 Jan, 2016 3 commits
  2. 11 Jan, 2016 1 commit
  3. 01 Jan, 2016 1 commit
  4. 17 Dec, 2015 1 commit
  5. 15 Dec, 2015 1 commit
  6. 08 Dec, 2015 4 commits
  7. 07 Dec, 2015 1 commit
  8. 04 Dec, 2015 1 commit
  9. 02 Dec, 2015 1 commit
  10. 30 Nov, 2015 1 commit
  11. 16 Nov, 2015 4 commits
  12. 10 Nov, 2015 2 commits
  13. 09 Nov, 2015 1 commit
    • Mike Hibler's avatar
      Two semi-related exports_setup changes. · 622e2187
      Mike Hibler authored
      1. Don't stat all exported mountpoints from boss to see if they exist.
         Not only is this wrong from boss (a mount may be valid, but not yet
         exported) it also makes the automounter work its butt off as we might
         stat hundreds or thousands of directories across NFS. The original
         purpose of this was to keep mountd from freaking out when presented
         with a non-existent directory. Since mountd freaking out is about as
         rare as the sun rising in the east, we keep this check but do it on
         the proxy (ops) side instead.
      2. Have exports_setup (boss) generate a list of directories that it should
         be able to mount. This goes in /usr/testbed/etc/validmounts.txt and will
         be used by autofs (I hope) to narrow down the wildcarded "/users/*"
         and "/proj/*" mounts to those that might actually work. Right now you
         can "ls /users/WtF" and it will try to mount it from ops and take 4
         seconds to timeout and fail.
  14. 05 Nov, 2015 1 commit
  15. 02 Nov, 2015 2 commits
    • Kirk Webb's avatar
      Add horrible hack to snmpit_h3c module to cope with submodules · 5a2b215f
      Kirk Webb authored
      The Emulab DB and codebase cannot currently cope with switch submodules.
      Hack around this in the Comware module by using the ifindex as the
      port number when the submodule ID is non-zero.  So gross, but no less
      arbitrary than some other translation from submodule and port to unique
    • Kirk Webb's avatar
      Incorporate Comware v5 support from Keith Sklower · 8881dd48
      Kirk Webb authored
      Also includes cutover to ifDescr parsing instead of using static module
      offsets (which are unreliable in Comware 7).  This allowed me to get rid
      of the awful per-switch module offset hack I added.
      Includes some cleanup and minor bug fixes too.
  16. 29 Oct, 2015 2 commits
    • Kirk Webb's avatar
      snmpit_force10: Enable various OF goodies on created instances. · 4e6f1b2c
      Kirk Webb authored
      L2 and L3 flow maps (hardware-assisted matching and forwarding),
      learning bridge assisted flows (hardware also, I think), and multiple
      forwarding tables.
      Default flows go into the "acl" table, which is carved up between various
      switch functions, and I believe is software-based (docs are vague).
    • Kirk Webb's avatar
      Add support for OpenFlow to Force10 snmpit module. · 84c3cfb2
      Kirk Webb authored
      Adding this support required a change to the createVlan() API call,
      which is why this commit touches so many modules. Optional/supplementary
      arguments to createVlan() are now passed as a fourth hash reference
      This supplementary hash is used to inform device modules that a vlan to
      be created is to be associated with an OpenFlow instance.  Only the
      snmpit_force10 makes use of this information at this time. FTOS requires
      that openflow-enabled vlans be declared as such at creation time. However,
      snmpit's default control flow creates vlans first, then associates them
      with OF instances (if requested).  This is why the supplementary argument
      (OF hint) to createVlan() is needed here.
      OpenFlow configuration actions must all be performed via the
      existing Expect-based CLI interface to FTOS. Yuck.
  17. 22 Oct, 2015 2 commits
    • Kirk Webb's avatar
      Disable OpenFlow when removing stale vlans in SyncVlansFromTables() · fee57b6e
      Kirk Webb authored
      If OF is specified for a vlan, and the sync operation is going to
      remove it because it is stale, try to disable OF before removal.
    • Kirk Webb's avatar
      Rework how OpenFlow setup is handled on the front-end · cda9ed7a
      Kirk Webb authored
      Previously OF would be setup after vlan creation, but before checking to
      see if all switches in scope actually support it.  This would lead to
      failures where the vlan was created and logged in the DB, but snmpit
      failed to setup OF, and so exit with a failure.  This in turn causes
      swap-in to fail, and leaves stale state on the switches and in the DB.
      Now when OF is requested for a vlan in an experiment, we first check
      to see if it is supported, then proceed.  We error out early before
      any OF-enabled vlan is created.
  18. 19 Oct, 2015 4 commits
  19. 15 Oct, 2015 2 commits
  20. 12 Oct, 2015 1 commit
  21. 09 Oct, 2015 1 commit
  22. 05 Oct, 2015 2 commits
    • Mike Hibler's avatar
      Fix more issues with reverse (aka, "show most recent") option. · 7ad2db71
      Mike Hibler authored
      If both -r and -n (number of records) was given (i.e., as called via the
      web page), then we were still fetching the oldest N records but then
      presenting those most recent first. Not real useful. Now we use sub-query fu
      to fetch the most recent N records but still keep those in oldest-to-newest
      order for processing.
      Also, removed two-field-order-by hack as sorting on just the timestamp now
      seems to use the index and no longer does a filesort.
      Don't generate summary info when the -x (history index) option is given.
    • Leigh B Stoller's avatar
      Fix to previous revision. · 85ee474d
      Leigh B Stoller authored
  23. 25 Sep, 2015 1 commit
    • Leigh B Stoller's avatar
      Fix error in duplex link vtop generation, that has been there since at · 543184c7
      Leigh B Stoller authored
      least 2009; change min to max of the bw/rbw values, since the link has to
      satisfy the direction with the higher bandwidth not the lower bandwidth. We
      probably don't run into this very often since people do not often do
      asymmetric links like 100Mb/155Mb, on nodes that have both 1Gb and 100Mb
      Also through in some warning code to catch this before it gets to snmpit,
      which fails when you try to set a 100Mb interface to 1Gb. This might turn
      into a fatal error later.