1. 22 Sep, 2010 1 commit
  2. 16 Sep, 2010 1 commit
  3. 15 Sep, 2010 4 commits
  4. 13 Sep, 2010 3 commits
  5. 09 Sep, 2010 4 commits
  6. 08 Sep, 2010 3 commits
  7. 07 Sep, 2010 1 commit
  8. 04 Sep, 2010 2 commits
  9. 03 Sep, 2010 3 commits
    • Weibin Sun's avatar
      Move code in apcon_clilib.pm into snmpit_apcon.pm as internal functions.... · cecf1f9e
      Weibin Sun authored
      Move code in apcon_clilib.pm into snmpit_apcon.pm as internal functions. Merging finished. apcon_clilib.pm not deleted for reference.
    • Ryan Jackson's avatar
      Fix typo in help text · 852ddff5
      Ryan Jackson authored
    • Ryan Jackson's avatar
      XML-RPC: Run frisbeelauncher as root for subboss · 59857b38
      Ryan Jackson authored
      Subbosses authenticate to the XML-RPC server as elabman, which means the
      resulting server process runs as the elabman user.  Unfortunately, this
      doesn't work well when the subboss wants to launch a frisbeed for an
      image for which elabman doesn't have read permission (like images under
      To fix this, a setuid wrapper script is run instead of trying to run
      frisbeelauncher directly.  This script makes sure the calling user is
      elabman, and then becomes root and execs frisbee_launcher.
  10. 02 Sep, 2010 2 commits
  11. 01 Sep, 2010 4 commits
    • Weibin Sun's avatar
    • Weibin Sun's avatar
      snmpit_apcon.pm: a device package for Apcon switch. Codes are not tested yet.... · 622fd73d
      Weibin Sun authored
      snmpit_apcon.pm: a device package for Apcon switch. Codes are not tested yet. All public functions for a device package are implemented. Some functions are not supported on Apcon. They are just placeholders for future fake output.  apcon_clilib.pm: function naming rules are changed for integration.
    • Robert Ricci's avatar
      Fix for parallelized snmpit stack · 645a8bd3
      Robert Ricci authored
      The parallelization code in the stack module puts the devices in
      child processes, which means that when they lookup their allowed
      VLAN ranges, they can no longer update the value in the parent
      stack object (which is in a different process). So, we have to do
      it here too.
    • Robert Ricci's avatar
      Fix for some really stupid Cisco behavior · a8a32a62
      Robert Ricci authored
      Some Ciscos limit the number of trunks on which you can configure
      'extended range' VLANs (above 1k). This includes clearing them from
      the trunk (eg. you don't actually have to be *using* them to get
      this error). So, as a workaround, if the stack is not conifgured
      to use VLANs over 1k, don't clear this range when cleaning out
      trunk ports.
  12. 31 Aug, 2010 3 commits
  13. 27 Aug, 2010 2 commits
  14. 26 Aug, 2010 2 commits
  15. 24 Aug, 2010 2 commits
    • Robert Ricci's avatar
      Revert "Minor comment fix" · 997fa581
      Robert Ricci authored
      This reverts commit a31f1a5b.
    • Leigh B Stoller's avatar
      Add the ability to "fix" VMs to other nodes in the topology. Prior to · 0e5290ab
      Leigh B Stoller authored
      this, you could fix a VM to specific physical node, but not to another
      node in the topology. This change allows you to do something like the
      set n1 [$ns node]
      set n2 [$ns node]
      set n3 [$ns node]
      set v1 [$ns node]
      set v2 [$ns node]
      set v3 [$ns node]
      tb-set-hardware $v1 pcvm
      tb-set-hardware $v2 pcvm
      tb-set-hardware $v3 pcvm
      # Fix the VMs to other nodes in the topology.
      tb-fix-node $v1 $n1
      tb-fix-node $v2 $n2
      tb-fix-node $v3 $n3
      # This mix requires vlan encap all around
      tb-set-vlink-emulation "vlan"
      # A link between the two phys nodes.
      set link0 [$ns duplex-link $n1 $n2 100Mb 0ms DropTail]
      # A link between the two VMs.
      set link1 [$ns duplex-link $v1 $v2 10Mb 0ms DropTail]
      # A lan of three physical nodes.
      set lan0 [$ns make-lan "$n1 $n2 $n3" 100Mb 0ms]
      # A lan of three VMs
      set lan1 [$ns make-lan "$v1 $v2 $v3" 10Mb 0ms]
      # Lets mix things up.
      set link2 [$ns duplex-link $n1 $v2 10Mb 0ms DropTail]
      set lan2 [$ns make-lan "$n1 $v2 $n3" 10Mb 0ms]
      tb-set-node-os $n1 FEDORA8-OVZ-STD
      tb-set-node-os $n2 FEDORA8-OVZ-STD
      tb-set-node-os $n3 FEDORA8-OVZ-STD
      tb-set-node-os $v1 OPENVZ-STD
      tb-set-node-os $v2 OPENVZ-STD
      tb-set-node-os $v3 OPENVZ-STD
  16. 20 Aug, 2010 1 commit
  17. 19 Aug, 2010 2 commits