1. 14 Dec, 2010 1 commit
  2. 09 Dec, 2010 1 commit
  3. 07 Dec, 2010 1 commit
  4. 29 Nov, 2010 1 commit
  5. 02 Nov, 2010 1 commit
  6. 28 Oct, 2010 1 commit
  7. 22 Oct, 2010 2 commits
  8. 20 Oct, 2010 1 commit
  9. 19 Oct, 2010 3 commits
  10. 18 Oct, 2010 1 commit
  11. 14 Oct, 2010 1 commit
  12. 12 Oct, 2010 1 commit
  13. 08 Oct, 2010 1 commit
  14. 04 Oct, 2010 1 commit
  15. 22 Sep, 2010 1 commit
  16. 21 Sep, 2010 2 commits
  17. 13 Sep, 2010 1 commit
  18. 09 Sep, 2010 1 commit
  19. 08 Sep, 2010 1 commit
  20. 07 Sep, 2010 1 commit
  21. 30 Aug, 2010 1 commit
  22. 26 Aug, 2010 1 commit
  23. 24 Aug, 2010 1 commit
    • 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
      following:
      
      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
      0e5290ab
  24. 20 Aug, 2010 1 commit
  25. 12 Aug, 2010 1 commit
  26. 09 Aug, 2010 2 commits
  27. 05 Aug, 2010 1 commit
  28. 03 Aug, 2010 4 commits
  29. 02 Aug, 2010 1 commit
  30. 30 Jul, 2010 1 commit
  31. 29 Jul, 2010 2 commits
    • Tarun Prabhu's avatar
      Annotations work - well, ok, they haven't been rigorously tested yet, but I... · be04644b
      Tarun Prabhu authored
      Annotations work - well, ok, they haven't been rigorously tested yet, but I think they'll hold up. The only thing that is almost certainly broken is the conversion from links with multiple interfaces into the "node + point-to-point" links that assign knows how to deal with.
      
      Mapper now has a flag to determine whether to output the text format or rspec. rspec outputs are named *.ptop.xml and *.vtop.xml for the advertisement and request respectively.
      be04644b
    • Tarun Prabhu's avatar
      Add extension and vclass support. It should be working correctly now. There's... · 34d18441
      Tarun Prabhu authored
      Add extension and vclass support. It should be working correctly now. There's a lot of ugliness w.r.t. hardware types and sliver types, while dealing with switches, nodes and vclasses. I have tried to hide most of it in rspec_parser_v2.cc and rspec_parser_helper.cc.
      34d18441