trema 0.4.7 → 0.4.8

data/features/switch_event/delete_forward_entry.feature

@@ -1,160 +0,0 @@
-Feature: Ruby methods for deleting switch event forwarding entry
-  
-  There are three Ruby methods provided for deleting switch event forwarding entries.
-  
-  * delete_forward_entry_from_all_switches
-  * delete_forward_entry_from_switch
-  * delete_forward_entry_from_switch_manager
-  
-  These methods can be used by including the Trema::SwitchEvent module
-  in user controller code. 
-  
-  * **delete_forward_entry_from_all_switches event_type, trema_name**
-  
-  This method will delete `trema_name` from all existing switches and switch manager's 
-  event forwarding entry list of the specified `event_type`.  
-  
-  * **delete_forward_entry_from_switch dpid, event_type, trema_name**
-  
-  This method will delete an entry from switch specified by `dpid`. 
-  It will delete `trema_name` from the switch's 
-  event forwarding entry list of the specified `event_type`.  
-  
-  * **delete_forward_entry_from_switch_manager event_type, trema_name**
-  
-  This method will delete `trema_name` from the switch manager's 
-  event forwarding entry list of the specified `event_type`.  
-  
-  ----
-  All the above methods take a result handler as Ruby block, but 
-  they can be omitted if checking is not necessary.
-
-  @slow_process @ruby
-  Scenario Outline: delete_forward_entry_from_all_switches event_type, trema_name
-    Given a file named "network.conf" with:
-      """
-      vswitch { datapath_id 0x1 }
-      """
-    And a file named "DeleteEntryFromAllTest.rb" with:
-      """ruby
-      class DeleteEntryFromAllTest < Controller
-        include SwitchEvent
-      
-        def start
-          @event_type = ARGV[0].delete(":").to_sym
-          @event_type_string = ":#{@event_type.to_s}"
-        end
-      
-        def switch_ready datapath_id
-          delete_forward_entry_from_all_switches @event_type, "DeleteEntryFromAllTest" do | success |
-            raise "Failed to delete forwarding entry from all switches" if not success
-            info "Successfully deleted a forwarding entry of #{@event_type_string}."
-            dump_forward_entries_from_switch datapath_id, @event_type do | success, services |
-              raise "Failed to dump forwarding entry from a switch" if not success
-              info "Dumping switch #{datapath_id.to_hex}'s forwarding entries of <event_type> : #{services.inspect}"
-            end
-            dump_forward_entries_from_switch_manager @event_type do | success, services |
-              raise "Failed to dump forwarding entry from the switch manager" if not success
-              info "Dumping switch manager's forwarding entries of #{@event_type_string} : #{services.inspect}"
-            end
-          end
-        end
-      end
-      """
-    When I successfully run `trema run "./DeleteEntryFromAllTest.rb <event_type>" -c network.conf -d`
-    And wait until "DeleteEntryFromAllTest" is up
-    And *** sleep 2 ***
-    Then the file "../../tmp/log/DeleteEntryFromAllTest.log" should contain:
-      """
-      Successfully deleted a forwarding entry of <event_type>.
-      """
-    And the file "../../tmp/log/DeleteEntryFromAllTest.log" should contain:
-      """
-      Dumping switch 0x1's forwarding entries of <event_type> : [<switch_event_list>]
-      """
-    And the file "../../tmp/log/DeleteEntryFromAllTest.log" should contain:
-      """
-      Dumping switch manager's forwarding entries of <event_type> : [<switch_manager_event_list>]
-      """
-
-    Examples: 
-      | event_type    | switch_manager_event_list | switch_event_list |
-      | :vendor       |                           |                   |
-      | :packet_in    |                           |                   |
-      | :port_status  |                           |                   |
-      | :state_notify |                           |                   |
-
-  @slow_process @ruby
-  Scenario Outline: delete_forward_entry_from_switch dpid, event_type, trema_name
-    Given a file named "network.conf" with:
-      """
-      vswitch { datapath_id 0x1 }
-      """
-    And a file named "DeleteFromSwitchDaemonTest.rb" with:
-      """ruby
-      class DeleteFromSwitchDaemonTest < Controller
-        include SwitchEvent
-      
-        def start
-          @event_type = ARGV[0].delete(":").to_sym
-          @event_type_string = ":#{@event_type.to_s}"
-        end
-      
-        def switch_ready datapath_id
-          delete_forward_entry_from_switch datapath_id, @event_type, "DeleteFromSwitchDaemonTest" do | success, services |
-            raise "Failed to delete forwarding entry from switch" if not success
-            info "Successfully deleted a forwarding entry of #{@event_type_string} from switch #{datapath_id.to_hex} : #{services.inspect}"
-          end
-        end
-      end
-      """
-    When I successfully run `trema run "./DeleteFromSwitchDaemonTest.rb <event_type>" -c network.conf -d`
-    And wait until "DeleteFromSwitchDaemonTest" is up
-    And *** sleep 1 ***
-    Then the file "../../tmp/log/DeleteFromSwitchDaemonTest.log" should contain:
-      """
-      Successfully deleted a forwarding entry of <event_type> from switch 0x1 : [<switch_event_list>]
-      """
-
-    Examples: 
-      | event_type    | switch_event_list |
-      | :vendor       |                   |
-      | :packet_in    |                   |
-      | :port_status  |                   |
-      | :state_notify |                   |
-
-  @slow_process @ruby
-  Scenario Outline: delete_forward_entry_from_switch_manager event_type, trema_name
-    Given a file named "DeleteFromSwitchManagerTest.rb" with:
-      """ruby
-      class DeleteFromSwitchManagerTest < Controller
-        include SwitchEvent
-      
-        def start
-          @event_type = ARGV[0].delete(":").to_sym
-          @event_type_string = ":#{@event_type.to_s}"
-        end
-      
-        oneshot_timer_event :test_start, 0
-        def test_start
-          delete_forward_entry_from_switch_manager @event_type, "DeleteFromSwitchManagerTest" do | success, services |
-            raise "Failed to delete forwarding entry from switch manager" if not success
-            info "Successfully deleted a forwarding entry of #{@event_type_string} from switch manager : #{services.inspect}"
-          end
-        end
-      end
-      """
-    When I successfully run `trema run "./DeleteFromSwitchManagerTest.rb <event_type>" -d`
-    And wait until "DeleteFromSwitchManagerTest" is up
-    And *** sleep 1 ***
-    Then the file "../../tmp/log/DeleteFromSwitchManagerTest.log" should contain:
-      """
-      Successfully deleted a forwarding entry of <event_type> from switch manager : [<switch_manager_event_list>]
-      """
-
-    Examples: 
-      | event_type    | switch_manager_event_list |
-      | :vendor       |                           |
-      | :packet_in    |                           |
-      | :port_status  |                           |
-      | :state_notify |                           |

data/features/switch_event/dump_forward_entries.feature

@@ -1,103 +0,0 @@
-Feature: Ruby methods for dumping switch event forwarding entry
-  
-  There are two Ruby methods provided for dumping switch event forwarding entry.
-  
-  * dump_forward_entries_from_switch
-  * dump_forward_entries_from_switch_manager
-  
-  These methods can be used by including the Trema::SwitchEvent module
-  in user controller code. 
-  
-  * **dump_forward_entries_from_switch dpid, event_type**
-  
-  This method will dump the forwarding entries of the switch specified by `dpid`. 
-  It will dump the content of the the switch's 
-  event forwarding entry list of the specified `event_type`.  
-  
-  * **dump_forward_entries_from_switch_manager event_type**
-  
-  This method will dump the content of the the switch manager's 
-  event forwarding entry list of the specified `event_type`.  
-  
-  ----
-  All the above methods take a result handler as Ruby block.
-
-  @slow_process @ruby
-  Scenario Outline: dump_forward_entries_from_switch dpid, event_type
-    Given a file named "network.conf" with:
-      """
-      vswitch { datapath_id 0x1 }
-      event :vendor => "vendor", :packet_in => "packet_in", :port_status => "port_status"
-      """
-    And a file named "DumpSwitchDaemonTest.rb" with:
-      """ruby
-      class DumpSwitchDaemonTest < Controller
-        include SwitchEvent
-      
-        def start
-          @event_type = ARGV[0].delete(":").to_sym
-          @event_type_string = ":#{@event_type.to_s}"
-        end
-      
-        def switch_ready datapath_id
-          dump_forward_entries_from_switch datapath_id, @event_type do | success, services |
-            raise "Failed to dump forwarding entry from a switch" if not success
-            info "Dumping switch #{datapath_id.to_hex}'s forwarding entries of #{@event_type_string} : #{services.inspect}"
-          end
-        end
-      end
-      """
-    When I successfully run `trema run "./DumpSwitchDaemonTest.rb <event_type>" -c network.conf -d`
-    And wait until "DumpSwitchDaemonTest" is up
-    And *** sleep 1 ***
-    Then the file "../../tmp/log/DumpSwitchDaemonTest.log" should contain:
-      """
-      Dumping switch 0x1's forwarding entries of <event_type> : [<switch_event_list>]
-      """
-
-    Examples: 
-      | event_type    | switch_event_list      |
-      | :vendor       | "vendor"               |
-      | :packet_in    | "packet_in"            |
-      | :port_status  | "port_status"          |
-      | :state_notify | "DumpSwitchDaemonTest" |
-
-  @slow_process @ruby
-  Scenario Outline: dump_forward_entries_from_switch_manager event_type
-    Given a file named "network.conf" with:
-      """
-      event :vendor => "vendor", :packet_in => "packet_in", :port_status => "port_status", :state_notify => "state_notify"
-      """
-    And a file named "DumpSwitchManagerTest.rb" with:
-      """ruby
-      class DumpSwitchManagerTest < Controller
-        include SwitchEvent
-      
-        def start
-          @event_type = ARGV[0].delete(":").to_sym
-          @event_type_string = ":#{@event_type.to_s}"
-        end
-      
-        oneshot_timer_event :test_start, 0
-        def test_start
-          dump_forward_entries_from_switch_manager @event_type do | success, services |
-            raise "Failed to dump forwarding entry from the switch manager" if not success
-            info "Dumping switch manager's forwarding entries of #{@event_type_string} : #{services.inspect}"
-          end
-        end
-      end
-      """
-    When I successfully run `trema run "./DumpSwitchManagerTest.rb <event_type>" -c network.conf -d`
-    And wait until "DumpSwitchManagerTest" is up
-    And *** sleep 1 ***
-    Then the file "../../tmp/log/DumpSwitchManagerTest.log" should contain:
-      """
-      Dumping switch manager's forwarding entries of <event_type> : [<switch_manager_event_list>]
-      """
-
-    Examples: 
-      | event_type    | switch_manager_event_list |
-      | :vendor       | "vendor"                  |
-      | :packet_in    | "packet_in"               |
-      | :port_status  | "port_status"             |
-      | :state_notify | "state_notify"            |

data/features/switch_event/set_forward_entries.feature

@@ -1,102 +0,0 @@
-Feature: Ruby methods for setting switch event forwarding entry
-  
-  There are two Ruby methods provided for setting switch event forwarding entry.
-  
-  * set_forward_entries_to_switch
-  * set_forward_entries_to_switch_manager
-  
-  These methods can be used by including the Trema::SwitchEvent module
-  in user controller code. 
-  
-  * **set_forward_entries_to_switch dpid, event_type, trema_names**
-  
-  This method will set the forwarding entries of the switch specified by `dpid`. 
-  It will replace the switch's 
-  event forwarding entry list of the specified `event_type` 
-  to Array of trema-names specified by `trema_names`. 
-    
-  
-  * **set_forward_entries_to_switch_manager event_type, trema_names**
-  
-  This method will replace the switch manager's 
-  event forwarding entry list of the specified `event_type`
-  to Array of trema-names specified by `trema_names`. 
-  
-  ----
-  All the above methods take a result handler as Ruby block, but 
-  they can be omitted if checking is not necessary.
-
-  @slow_process @ruby
-  Scenario Outline: set_forward_entries_to_switch dpid, event_type, trema_names
-    Given a file named "network.conf" with:
-      """
-      vswitch { datapath_id 0x1 }
-      """
-    And a file named "SetEntriesToSwitchDaemonTest.rb" with:
-      """ruby
-      class SetEntriesToSwitchDaemonTest < Controller
-        include SwitchEvent
-      
-        def start
-          @event_type = ARGV[0].delete(":").to_sym
-          @event_type_string = ":#{@event_type.to_s}"
-        end
-      
-        def switch_ready datapath_id
-          set_forward_entries_to_switch datapath_id, @event_type, ["SetEntriesToSwitchDaemonTest","Another"] do | success, services |
-            raise "Failed to set forwarding entry to switch" if not success
-            info "Successfully set a forwarding entries of #{@event_type_string} to switch #{datapath_id.to_hex} : #{services.inspect}"
-          end
-        end
-      end
-      """
-    When I successfully run `trema run "./SetEntriesToSwitchDaemonTest.rb <event_type>" -c network.conf -d`
-    And wait until "SetEntriesToSwitchDaemonTest" is up
-    And *** sleep 1 ***
-    Then the file "../../tmp/log/SetEntriesToSwitchDaemonTest.log" should contain:
-      """
-      Successfully set a forwarding entries of <event_type> to switch 0x1 : [<switch_event_list>]
-      """
-
-    Examples: 
-      | event_type    | switch_event_list                         |
-      | :vendor       | "SetEntriesToSwitchDaemonTest", "Another" |
-      | :packet_in    | "SetEntriesToSwitchDaemonTest", "Another" |
-      | :port_status  | "SetEntriesToSwitchDaemonTest", "Another" |
-      | :state_notify | "SetEntriesToSwitchDaemonTest", "Another" |
-
-  @slow_process @ruby
-  Scenario Outline: set_forward_entries_to_switch_manager event_type, trema_names
-    Given a file named "SetEntriesToSwitchManagerTest.rb" with:
-      """ruby
-      class SetEntriesToSwitchManagerTest < Controller
-        include SwitchEvent
-      
-        def start
-          @event_type = ARGV[0].delete(":").to_sym
-          @event_type_string = ":#{@event_type.to_s}"
-        end
-      
-        oneshot_timer_event :test_start, 0
-        def test_start
-          set_forward_entries_to_switch_manager @event_type, ["SetEntriesToSwitchManagerTest","Another"] do | success, services |
-            raise "Failed to set forwarding entry to switch manager" if not success
-            info "Successfully set a forwarding entries of #{@event_type_string} to switch manager : #{services.inspect}"
-          end
-        end
-      end
-      """
-    When I successfully run `trema run "./SetEntriesToSwitchManagerTest.rb <event_type>" -d`
-    And wait until "SetEntriesToSwitchManagerTest" is up
-    And *** sleep 1 ***
-    Then the file "../../tmp/log/SetEntriesToSwitchManagerTest.log" should contain:
-      """
-      Successfully set a forwarding entries of <event_type> to switch manager : [<switch_manager_event_list>]
-      """
-
-    Examples: 
-      | event_type    | switch_manager_event_list                  |
-      | :vendor       | "SetEntriesToSwitchManagerTest", "Another" |
-      | :packet_in    | "SetEntriesToSwitchManagerTest", "Another" |
-      | :port_status  | "SetEntriesToSwitchManagerTest", "Another" |
-      | :state_notify | "SetEntriesToSwitchManagerTest", "Another" |

data/features/trema_commands/README.md

@@ -1,8 +0,0 @@
-The `trema` command comes with several sub-commands you can use to
-run your own controllers on emulated network envrionments.
-
-For a full list of sub-commands, run the `trema` command with no arguments:
-
-```
-$ ./trema
-```

data/features/trema_commands/dump_flows.feature

@@ -1,41 +0,0 @@
-@ruby
-Feature: dump_flows command
-
-  In order to inspect all flow entries in a Trema virtual switch
-  As a developer using Trema
-  I want to execute "trema dump_flows" command
-
-  Background:
-    Given a file named "repeater_hub.conf" with:
-      """
-      vswitch("repeater_hub") { datapath_id 0xabc }
-
-      vhost("host1")
-      vhost("host2")
-      vhost("host3")
-
-      link "repeater_hub", "host1"
-      link "repeater_hub", "host2"
-      link "repeater_hub", "host3"
-      """
-    And I successfully run `trema run ../../objects/examples/repeater_hub/repeater_hub -c repeater_hub.conf -d`
-
-  @slow_process
-  Scenario: dump a flow entry
-    Given I run `trema send_packets --source host1 --dest host2`
-    And *** sleep 1 ***
-    When I run `trema dump_flows repeater_hub`
-    Then the output should contain "actions=FLOOD"
-
-  @slow_process
-  Scenario: no flow entry
-    When I run `trema dump_flows repeater_hub`
-    Then the output should not contain "actions="
-
-  Scenario: no argument
-    When I run `trema dump_flows`
-    Then the output should contain "switches is required"
-
-  Scenario: wrong switch name
-    When I run `trema dump_flows nosuchswitch`
-    Then the output should contain "No switch named `nosuchswitch` found!"

data/features/trema_commands/help.feature

@@ -1,27 +0,0 @@
-@ruby
-Feature: help command
-
-  In order to understand how to use Trema
-  As a developer using Trema
-  I want to read the help message of trema command
-
-  Scenario: List sub-commands
-    When I run `trema help`
-    Then the output should contain "dump_flows"
-     And the output should contain "help"
-     And the output should contain "kill"
-     And the output should contain "killall"
-     And the output should contain "netns"
-     And the output should contain "reset_stats"
-     And the output should contain "ruby"
-     And the output should contain "run"
-     And the output should contain "send_packets"
-     And the output should contain "show_stats"
-     And the output should contain "up"
-     And the output should contain "version"
-
-  Scenario: List global options
-    When I run `trema help`
-    Then the output should contain "--help"
-     And the output should contain "-v, --verbose"
-     And the output should contain "--version"

data/features/trema_commands/help_option.feature

@@ -1,20 +0,0 @@
-@ruby
-Feature: --help option
-
-  Use the --help option or just type trema to display the usage of trema command.
-
-  Scenario: trema --help
-    When I run `trema --help`
-    Then the output should match /^NAME/
-     And the output should match /^SYNOPSIS/
-     And the output should match /^VERSION/
-     And the output should match /^GLOBAL OPTIONS/
-     And the output should match /^COMMANDS/
-
-  Scenario: trema
-    When I run `trema`
-    Then the output should match /^NAME/
-     And the output should match /^SYNOPSIS/
-     And the output should match /^VERSION/
-     And the output should match /^GLOBAL OPTIONS/
-     And the output should match /^COMMANDS/