trema 0.4.7 → 0.4.8

data/features/trema_commands/kill.feature

@@ -1,56 +0,0 @@
-@ruby
-Feature: kill command
-
-  In order to test event handling or just kill unwanted processes
-  As a developer using Trema
-  I want to execute "trema kill" command
-
-  Background:
-    Given a file named "switch_monitor.conf" with:
-      """
-      vswitch { datapath_id 0x1 }
-      vswitch { datapath_id 0x2 }
-      vswitch { datapath_id 0x3 }
-
-      vhost "host1"
-      vhost "host2"
-      vhost "host3"
-
-      link "0x1", "host1"
-      link "0x2", "host2"
-      link "0x3", "host3"
-      """
-    And I successfully run `trema run ../../src/examples/switch_monitor/switch-monitor.rb -c switch_monitor.conf -d`
-
-  @slow_process
-  Scenario: kill a switch
-    When I run `trema kill 0x1`
-     And *** sleep 1 ***
-    Then the vswitch "0x1" is terminated
-
-  @slow_process
-  Scenario: kill a host
-    When I run `trema kill host1`
-     And *** sleep 1 ***
-    Then the vhost "host1" is terminated
-
-  @slow_process
-  Scenario: kill hosts
-    When I run `trema kill host1 host2`
-     And *** sleep 1 ***
-    Then the vhost "host1" is terminated
-     And the vhost "host2" is terminated
-
-  @slow_process
-  Scenario: kill a controller
-    When I run `trema kill SwitchMonitor`
-     And *** sleep 1 ***
-    Then the controller "SwitchMonitor" is terminated
-
-  Scenario: no argument
-    When I run `trema kill`
-    Then the output should contain "name is required"
-
-  Scenario: wrong name
-    When I run `trema kill nosuchname`
-    Then the output should contain "unknown name: nosuchname"

data/features/trema_commands/killall.feature

@@ -1,32 +0,0 @@
-@ruby
-Feature: killall command
-
-  In order to cleanup the previous trema session
-  As a developer using Trema
-  I want to execute "trema killall" command
-
-  @slow_process
-  Scenario: trema killall
-    Given a file named "switch_monitor.conf" with:
-      """
-      vswitch { datapath_id 0x1 }
-      vswitch { datapath_id 0x2 }
-      vswitch { datapath_id 0x3 }
-
-      vhost "host1"
-      vhost "host2"
-      vhost "host3"
-
-      link "0x1", "host1"
-      link "0x2", "host2"
-      link "0x3", "host3"
-      """
-     And I successfully run `trema run ../../objects/examples/switch_monitor/switch_monitor -c switch_monitor.conf -d`
-     And wait until "switch_monitor" is up
-    When I run `trema killall`
-     And *** sleep 1 ***
-    Then switch_manager is terminated
-     And switch is terminated
-     And phost is terminated
-     And ovs-openflowd is terminated
-     And switch_monitor is terminated

data/features/trema_commands/port_down.feature

@@ -1,71 +0,0 @@
-@ruby
-Feature: port_down command
-
-  Use this command to ensure that your controller detects network
-  topology changes i.e., failures in switches.
-
-  Trema emulated network offers a set of commands that can change the
-  status of any arbitrary switch port. The `trema port_down` is one
-  such command and its command syntax is as follows:
-
-      $ trema port_down --switch DATAPATH_ID --port PORT_NUMBER
-
-  The above command brings the switch's specified port down. By using
-  this command one can easily test the :port_status handler defined in
-  controllers.
-
-  Background:
-    Given a file named "sample.conf" with:
-    """
-    vswitch { datapath_id 0x1 }
-    vswitch { datapath_id 0x2 }
-
-    link "0x1", "0x2"
-    """
-    And a file named "port-observer.rb" with:
-    """
-    class PortObserver < Controller
-      def switch_ready dpid
-        info "Switch %#x is UP", dpid
-      end
-
-
-      def port_status dpid, message
-        if message.phy_port.down?
-          info "Port #{ message.phy_port.number } (Switch %#x) is DOWN", dpid
-        end
-      end
-    end
-    """
-
-  @slow_process
-  Scenario: trema port_down --switch 0x1 --port 1
-    Given I run `trema run ./port-observer.rb -c sample.conf` interactively
-    And I wait for output to contain "Switch 0x1 is UP"
-    When I run `trema port_down --switch 0x1 --port 1`
-    Then the output should contain "Port 1 (Switch 0x1) is DOWN" within the timeout period
-
-  @slow_process
-  Scenario: trema port_down --switch UNKNOWN --port 1 (unknown switch error)
-    Given I run `trema run ./port-observer.rb -c sample.conf -d`
-    When I run `trema port_down --switch UNKNOWN --port 1`
-    Then the output should contain "error: unknown switch: UNKNOWN"
-
-  @slow_process
-  Scenario: trema port_down --switch 0x1 --port 100 (unknown port error)
-    Given I run `trema run ./port-observer.rb -c sample.conf -d`
-    When I run `trema port_down --switch 0x1 --port 100`
-    Then the output should contain "error: ovs-ofctl: vsw_0x1: couldn't find port `100'"
-
-  @slow_process
-  Scenario: trema port_down --switch 0x1 (no --port option error)
-    Given I run `trema run ./port-observer.rb -c sample.conf -d`
-    When I run `trema port_down --switch 0x1`
-    Then the output should contain "error: --port option is mandatory"
-
-  @slow_process
-  Scenario: trema port_down --port 1 (no --switch option error)
-    Given I run `trema run ./port-observer.rb -c sample.conf -d`
-    When I run `trema port_down --port 1`
-    Then the output should contain "error: --switch option is mandatory"
-

data/features/trema_commands/port_up.feature

@@ -1,75 +0,0 @@
-@ruby
-Feature: port_up command
-
-  Use this command to ensure that your controller detects network
-  topology changes i.e., failures in switches.
-
-  Trema emulated network offers a set of commands that can change the
-  status of any arbitrary switch port. The `trema port_up` is one such
-  command and its command syntax is as follows:
-
-      $ trema port_up --switch DATAPATH_ID --port PORT_NUMBER
-
-  The above command brings the switch's specified port up. By using
-  this command one can easily test the :port_status handler defined in
-  controllers.
-
-  Background:
-    Given a file named "sample.conf" with:
-    """
-    vswitch { datapath_id 0x1 }
-    vswitch { datapath_id 0x2 }
-
-    link "0x1", "0x2"
-    """
-    And a file named "port-observer.rb" with:
-    """
-    class PortObserver < Controller
-      def switch_ready dpid
-        info "Switch %#x is UP", dpid
-      end
-
-
-      def port_status dpid, message
-        if message.phy_port.up?
-          info "Port #{ message.phy_port.number } (Switch %#x) is UP", dpid
-        elsif message.phy_port.down?
-          info "Port #{ message.phy_port.number } (Switch %#x) is DOWN", dpid
-        end
-      end
-    end
-    """
-
-  @slow_process
-  Scenario: trema port_up --switch 0x1 --port 1
-    Given I run `trema run ./port-observer.rb -c sample.conf` interactively
-    And I wait for output to contain "Switch 0x1 is UP"
-    And I run `trema port_down --switch 0x1 --port 1`
-    And I wait for output to contain "Port 1 (Switch 0x1) is DOWN"
-    When I run `trema port_up --switch 0x1 --port 1`
-    Then the output should contain "Port 1 (Switch 0x1) is UP" within the timeout period
-
-  @slow_process
-  Scenario: trema port_up --switch UNKNOWN --port 1 (unknown switch error)
-    Given I run `trema run ./port-observer.rb -c sample.conf -d`
-    When I run `trema port_up --switch UNKNOWN --port 1`
-    Then the output should contain "error: unknown switch: UNKNOWN"
-
-  @slow_process
-  Scenario: trema port_up --switch 0x1 --port 100 (unknown port error)
-    Given I run `trema run ./port-observer.rb -c sample.conf -d`
-    When I run `trema port_up --switch 0x1 --port 100`
-    Then the output should contain "error: ovs-ofctl: vsw_0x1: couldn't find port `100'"
-
-  @slow_process
-  Scenario: trema port_up --switch 0x1 (no --port option error)
-    Given I run `trema run ./port-observer.rb -c sample.conf -d`
-    When I run `trema port_up --switch 0x1`
-    Then the output should contain "error: --port option is mandatory"
-
-  @slow_process
-  Scenario: trema port_up --port 1 (no --switch option error)
-    Given I run `trema run ./port-observer.rb -c sample.conf -d`
-    When I run `trema port_up --port 1`
-    Then the output should contain "error: --switch option is mandatory"
-

data/features/trema_commands/reset_stats.feature

@@ -1,56 +0,0 @@
-@ruby
-Feature: reset_stats command
-
-  In order to reset the stats of sent/received packets
-  As a developer using Trema
-  I want to execute "trema reset_stats" command
-
-  Background:
-    Given a file named "learning_switch.conf" with:
-      """
-      vswitch { datapath_id 0xabc }
-
-      vhost("host1") { ip "192.168.0.1" }
-      vhost("host2") { ip "192.168.0.2" }
-
-      link "0xabc", "host1"
-      link "0xabc", "host2"
-      """
-    And I run `trema run ../../src/examples/learning_switch/learning-switch.rb -c learning_switch.conf -d`
-    And I run `trema send_packets --source host1 --dest host2`
-    And *** sleep 1 ***
-
-  @slow_process
-  Scenario: reset_stats host1
-    When I run `trema reset_stats host1`
-     And I run `trema show_stats host1`
-    Then the output should contain exactly "Sent packets:\n\nReceived packets:\n\n"
-
-  @slow_process
-  Scenario: reset_stats host1 host2
-    When I run `trema reset_stats host1 host2`
-     And I run `trema show_stats host1`
-    Then the output should contain exactly "Sent packets:\n\nReceived packets:\n\n"
-
-  @slow_process
-  Scenario: reset_stats host1 host2
-    When I run `trema reset_stats host1 host2`
-     And I run `trema show_stats host2`
-    Then the output should contain exactly "Sent packets:\n\nReceived packets:\n\n"
-
-  @slow_process
-  Scenario: no argument
-    When I run `trema reset_stats`
-     And I run `trema show_stats host1`
-    Then the output should contain exactly "Sent packets:\n\nReceived packets:\n\n"
-
-  @slow_process
-  Scenario: no argument
-    When I run `trema reset_stats`
-     And I run `trema show_stats host2`
-    Then the output should contain exactly "Sent packets:\n\nReceived packets:\n\n"
-
-  @slow_process
-  Scenario: wrong name
-    When I run `trema reset_stats nosuchhost`
-    Then the output should contain "unknown host: nosuchhost"

data/features/trema_commands/run.feature

@@ -1,56 +0,0 @@
-@ruby
-Feature: run command
-
-  In order to launch trema applications
-  As a developer using Trema
-  I want to use `trema run` command
-
-  Background:
-    Given a file named "network.conf" with:
-      """
-      vswitch { datapath_id 0xabc }
-      """
-
-  @slow_process
-  Scenario: trema run launches switch_manager and an application
-    When I run `trema run ../../objects/examples/dumper/dumper -c network.conf -d`
-     And wait until "dumper" is up
-    Then switch_manager is started
-     And dumper is started
-
-  @slow_process
-  Scenario: trema run launches switch_manager and an application with proper options
-    When I run `trema -v run ../../objects/examples/learning_switch/learning_switch -c network.conf -d`
-     And wait until "learning_switch" is up
-    Then the output should contain:
-     """
-     switch_manager --daemonize --port=6653 -- port_status::learning_switch packet_in::learning_switch state_notify::learning_switch vendor::learning_switch
-     """
-     And the output should contain:
-     """
-     learning_switch --name learning_switch -d
-     """
-
-  @slow_process
-  Scenario: The --port option can override the default openflow channel port
-    When I run `which trema`
-    When I run `trema -v run ../../objects/examples/learning_switch/learning_switch -c network.conf --port 6633 -d`
-     And wait until "learning_switch" is up
-    Then the output should contain:
-     """
-     switch_manager --daemonize --port=6633 -- port_status::learning_switch packet_in::learning_switch state_notify::learning_switch vendor::learning_switch
-     """
-
-  @slow_process
-  Scenario: The -p option can override the default openflow channel port
-    When I run `trema -v run ../../objects/examples/learning_switch/learning_switch -c network.conf -p 6633 -d`
-     And wait until "learning_switch" is up
-    Then the output should contain:
-     """
-     switch_manager --daemonize --port=6633 -- port_status::learning_switch packet_in::learning_switch state_notify::learning_switch vendor::learning_switch
-     """
-
-  @slow_process
-  Scenario: switch_manager is killed when trema session is closed
-    When I run `trema -v run /bin/true -c network.conf`
-    Then the output should contain "Shutting down switch_manager..."

data/features/trema_commands/send_packets.feature

@@ -1,46 +0,0 @@
-@ruby
-Feature: send_packets command
-
-  In order to send/receive packets between virtual hosts
-  As a developer using Trema
-  I want to execute "trema send_packets" command
-
-  Background:
-    Given a file named "learning_switch.conf" with:
-      """
-      vswitch("learning") { datapath_id 0xabc }
-
-      vhost("host1") { ip "192.168.0.1" }
-      vhost("host2") { ip "192.168.0.2" }
-
-      link "learning", "host1"
-      link "learning", "host2"
-      """
-    And I run `trema run ../../src/examples/learning_switch/learning-switch.rb -c learning_switch.conf -d`
-
-  @slow_process @critical
-  Scenario: Sending packets
-    When I run `trema send_packets --source host1 --dest host2 --n_pkts=2`
-     And I run `trema send_packets --source host2 --dest host1 --n_pkts=1`
-    Then the total number of tx packets should be:
-      | host1 | host2 |
-      |     2 |     1 |
-    And the total number of rx packets should be:
-      | host1 | host2 |
-      |     1 |     2 |
-
-  @slow_process
-  Scenario: unknown host error (--source)
-    When I run `trema send_packets --source NO_SUCH_HOST --dest host2`
-    Then the output should contain:
-      """
-      unknown host: NO_SUCH_HOST
-      """
-
-  @slow_process
-  Scenario: unknown host error (--dest)
-    When I run `trema send_packets --source host1 --dest NO_SUCH_HOST`
-    Then the output should contain:
-      """
-      unknown host: NO_SUCH_HOST
-      """

data/features/trema_commands/show_stats.feature

@@ -1,66 +0,0 @@
-@ruby
-Feature: show_stats command
-
-  In order to get the stats of sent/received packets
-  As a developer using Trema
-  I want to execute "trema show_stats" command
-
-  Background:
-    Given a file named "learning_switch.conf" with:
-      """
-      vswitch { datapath_id 0xabc }
-
-      vhost("host1") { ip "192.168.0.1" }
-      vhost("host2") { ip "192.168.0.2" }
-
-      link "0xabc", "host1"
-      link "0xabc", "host2"
-      """
-    And I run `trema run ../../src/examples/learning_switch/learning-switch.rb -c learning_switch.conf -d`
-
-  @slow_process
-  Scenario: show_stats hostname
-    When I run `trema send_packets --source host1 --dest host2`
-     And I run `trema show_stats host1`
-    Then the output should contain:
-      """
-      Sent packets:
-      ip_dst,tp_dst,ip_src,tp_src,n_pkts,n_octets
-      192.168.0.2,1,192.168.0.1,1,1,50
-      Received packets:
-      """
-
-  @slow_process
-  Scenario: show_stats hostname --tx
-    When I run `trema send_packets --source host1 --dest host2`
-     And I run `trema show_stats host1 --tx`
-    Then the output should contain:
-      """
-      ip_dst,tp_dst,ip_src,tp_src,n_pkts,n_octets
-      192.168.0.2,1,192.168.0.1,1,1,50
-      """
-
-  @slow_process
-  Scenario: show_stats hostname --rx
-    When I run `trema send_packets --source host1 --dest host2`
-     And *** sleep 1 ***
-     And I run `trema show_stats host2 --rx`
-    Then the output should contain:
-      """
-      ip_dst,tp_dst,ip_src,tp_src,n_pkts,n_octets
-      192.168.0.2,1,192.168.0.1,1,1,50
-      """
-
-  Scenario: argument error
-    Then I run `trema show_stats`
-    Then the output should contain:
-      """
-      host is required
-      """
-
-  Scenario: unknown host error
-    Then I run `trema show_stats NO_SUCH_HOST`
-    Then the output should contain:
-      """
-      unknown host: NO_SUCH_HOST
-      """