trema 0.1.3

data/features/example.learning_switch.feature

@@ -0,0 +1,39 @@
+Feature: control one openflow switch using learning-switch controller
+
+  As a Trema user
+  I want to control one openflow switch using learning-switch controller
+  So that I can send and receive packets
+
+
+  Scenario: Send and receive packets
+    Given I try trema run "learning_switch" example with following configuration (backgrounded):
+      """
+      vswitch("learning") { datapath_id "0xabc" }
+
+      vhost("host1")
+      vhost("host2")
+
+      link "learning", "host1"
+      link "learning", "host2"
+      """
+    When I send 1 packet from host1 to host2
+      And I try to run "./trema show_stats host1 --tx" (log = "host1.learning_switch.log")
+      And I try to run "./trema show_stats host2 --rx" (log = "host2.learning_switch.log")
+    Then the content of "host1.learning_switch.log" and "host2.learning_switch.log" should be identical
+
+
+  Scenario: Send and receive packets (in Ruby)
+    Given I try trema run "learning-switch.rb" example with following configuration (backgrounded):
+      """
+      vswitch("learning") { datapath_id "0xabc" }
+
+      vhost("host1")
+      vhost("host2")
+
+      link "learning", "host1"
+      link "learning", "host2"
+      """
+    When I send 1 packet from host1 to host2
+      And I try to run "./trema show_stats host1 --tx" (log = "host1.LearningSwitch.log")
+      And I try to run "./trema show_stats host2 --rx" (log = "host2.LearningSwitch.log")
+    Then the content of "host1.LearningSwitch.log" and "host2.LearningSwitch.log" should be identical

data/features/example.list_switches.feature

@@ -0,0 +1,38 @@
+Feature: Get the list of openflow switches with list_switches
+
+  As a Trema user
+  I want to get the list of openflow switches
+  So that I can check how many switches are connected to my controller
+
+
+  Scenario: Get the list of openflow switches
+    Given I try trema run "./objects/examples/list_switches/list_switches" with following configuration (backgrounded):
+      """
+      vswitch { datapath_id "0x1" }
+      vswitch { datapath_id "0x2" }
+      vswitch { datapath_id "0x3" }
+      vswitch { datapath_id "0x4" }
+      """
+      And wait until "list_switches" is up
+      And *** sleep 2 ***
+      And I terminated all trema services
+    Then the output should include:
+      """
+      switches = 0x1, 0x2, 0x3, 0x4
+      """
+
+  Scenario: Get the list of openflow switches (in Ruby)
+    Given I try trema run "./src/examples/list_switches/list-switches.rb" with following configuration (backgrounded):
+      """
+      vswitch { datapath_id "0x1" }
+      vswitch { datapath_id "0x2" }
+      vswitch { datapath_id "0x3" }
+      vswitch { datapath_id "0x4" }
+      """
+      And wait until "ListSwitches" is up
+      And *** sleep 2 ***
+      And I terminated all trema services
+    Then the output should include:
+      """
+      switches = 0x1, 0x2, 0x3, 0x4
+      """

data/features/example.message.echo_reply.feature

@@ -0,0 +1,26 @@
+Feature: Send echo reply messages
+
+  As a Trema user
+  I want to send echo reply messages to openflow switches
+  Because I want to reply to echo requests from openflow switches
+
+
+  Scenario: Send echo reply x 10
+    When I try trema run "./objects/examples/openflow_message/echo_reply 10" with following configuration (backgrounded):
+      """
+      vswitch("echo_reply") { datapath_id "0xabc" }
+      """
+      And wait until "echo_reply" is up
+      And *** sleep 2 ***
+    Then the log file "openflowd.echo_reply.log" should include "received: OFPT_ECHO_REPLY" x 10
+
+
+   Scenario: Send echo reply x 10 in Ruby
+    When I try trema run "./src/examples/openflow_message/echo-reply.rb 0xabc, 10" with following configuration (backgrounded):
+      """
+      vswitch("echo-reply") { datapath_id "0xabc" }
+      """
+      And wait until "EchoReplyController" is up
+      And *** sleep 2 ***
+    Then the log file "openflowd.echo-reply.log" should include "received: OFPT_ECHO_REPLY" x 10
+

data/features/example.message.echo_request.feature

@@ -0,0 +1,25 @@
+Feature: Send echo request messages
+
+  As a Trema user
+  I want to send echo request messages to openflow switches
+  So that I can receive echo reply messages from openflow switches
+
+
+  Scenario: Send echo request x 10
+    When I try trema run "./objects/examples/openflow_message/echo_request 10" with following configuration (backgrounded):
+      """
+      vswitch("echo_request") { datapath_id "0xabc" }
+      """
+      And wait until "echo_request" is up
+      And *** sleep 2 ***
+    Then the log file "openflowd.echo_request.log" should include "received: OFPT_ECHO_REQUEST" x 10
+
+
+  Scenario: Send echo request x 10 in Ruby
+    When I try trema run "./src/examples/openflow_message/echo-request.rb 0xabc, 10" with following configuration (backgrounded):
+      """
+      vswitch("echo-request") { datapath_id "0xabc" }
+      """
+      And wait until "EchoRequestController" is up
+      And *** sleep 2 ***
+    Then the log file "openflowd.echo-request.log" should include "received: OFPT_ECHO_REQUEST" x 10

data/features/example.message.features_request.feature

@@ -0,0 +1,84 @@
+Feature: Send a features request message
+
+  As a Trema user
+  I want to send a features request message to openflow switches
+  So that I can get the list of switch features
+
+
+  Scenario: Send a features request 
+    When I try trema run "./objects/examples/openflow_message/features_request" with following configuration (backgrounded):
+      """
+      vswitch( "features_request" ) { datapath_id "0xabc" }
+      """
+      And wait until "features_request" is up
+      And I terminated all trema services
+    Then the output should include:
+    """
+    datapath_id: 0xabc
+    n_buffers: 256
+    n_tables: 1
+    capabilities:
+      OFPC_FLOW_STATS
+      OFPC_TABLE_STATS
+      OFPC_PORT_STATS
+      OFPC_ARP_MATCH_IP
+    actions:
+      OFPAT_OUTPUT
+      OFPAT_SET_VLAN_VID
+      OFPAT_SET_VLAN_PCP
+      OFPAT_STRIP_VLAN
+      OFPAT_SET_DL_SRC
+      OFPAT_SET_DL_DST
+      OFPAT_SET_NW_SRC
+      OFPAT_SET_NW_DST
+      OFPAT_SET_NW_TOS
+      OFPAT_SET_TP_SRC
+      OFPAT_SET_TP_DST
+    port_no: 65534
+      name = vsw_0xabc
+      config = 0x1
+      state = 0x1
+      curr = 0x82
+      advertised = 0
+      supported = 0
+      peer = 0
+    """
+
+  Scenario: Send a features request in Ruby 
+    When I try trema run "./src/examples/openflow_message/features-request.rb" with following configuration (backgrounded):
+      """
+      vswitch( "features-request" ) { datapath_id "0xabc" }
+      """
+      And wait until "FeaturesRequestController" is up
+      And I terminated all trema services
+    Then the output should include:
+    """
+    datapath_id: 0xabc
+    n_buffers: 256
+    n_tables: 1
+    capabilities:
+      OFPC_FLOW_STATS
+      OFPC_TABLE_STATS
+      OFPC_PORT_STATS
+      OFPC_ARP_MATCH_IP
+    actions:
+      OFPAT_OUTPUT
+      OFPAT_SET_VLAN_VID
+      OFPAT_SET_VLAN_PCP
+      OFPAT_STRIP_VLAN
+      OFPAT_SET_DL_SRC
+      OFPAT_SET_DL_DST
+      OFPAT_SET_NW_SRC
+      OFPAT_SET_NW_DST
+      OFPAT_SET_NW_TOS
+      OFPAT_SET_TP_SRC
+      OFPAT_SET_TP_DST
+    port_no: 65534
+      name = vsw_0xabc
+      config = 0x1
+      state = 0x1
+      curr = 0x82
+      advertised = 0x0
+      supported = 0x0
+      peer = 0x0
+    """

data/features/example.message.hello.feature

@@ -0,0 +1,25 @@
+Feature: Send hello messages
+
+  As a Trema user
+  I want to send hello messages to openflow switches
+  So that I can start transactions with switches
+
+
+  Scenario: Hello trema
+    When I try trema run "./objects/examples/openflow_message/hello 10" with following configuration (backgrounded):
+      """
+      vswitch("hello") { datapath_id "0xabc" }
+      """
+      And wait until "hello" is up
+      And I terminated all trema services
+    Then the log file "openflowd.hello.log" should include "received: OFPT_HELLO" x 11
+
+
+  Scenario: Hello trema in Ruby
+    When I try trema run "./src/examples/openflow_message/hello.rb 0xabc, 10" with following configuration (backgrounded):
+      """
+      vswitch("hello-r") { datapath_id "0xabc" }
+      """
+      And wait until "HelloController" is up
+      And I terminated all trema services
+    Then the log file "openflowd.hello-r.log" should include "received: OFPT_HELLO" x 11

data/features/example.message.set_config.feature

@@ -0,0 +1,27 @@
+Feature: Send set config messages
+
+  As a Trema user
+  I want to send set config messages to openflow switches
+  So that I can set configuration parameters of openflow switches
+
+
+  Scenario: set config x 10
+    When I try trema run "./objects/examples/openflow_message/set_config 10" with following configuration (backgrounded):
+      """
+      vswitch("set_config") { datapath_id "0xabc" }
+      """
+      And wait until "set_config" is up
+      And *** sleep 2 ***
+      And I terminated all trema services
+    Then the log file "openflowd.set_config.log" should include "received: OFPT_SET_CONFIG" x 11
+
+
+  Scenario: set config x 10 in Ruby
+    When I try trema run "./src/examples/openflow_message/set-config.rb 0xabc, 10" with following configuration (backgrounded):
+      """
+      vswitch("set-config") { datapath_id "0xabc" }
+      """
+      And wait until "SetConfigController" is up
+      And *** sleep 2 ***
+      And I terminated all trema services
+    Then the log file "openflowd.set-config.log" should include "received: OFPT_SET_CONFIG" x 11

data/features/example.multi_learning_switch.feature

@@ -0,0 +1,135 @@
+Feature: control multiple openflow switches using multi learning switch controller
+
+  As a Trema user
+  I want to control multiple openflow switches using multi learning switch controller
+  So that I can send and receive packets
+
+
+  Scenario: Send and receive packets
+    Given I try trema run "./objects/examples/multi_learning_switch/multi_learning_switch" with following configuration (backgrounded):
+      """
+      vswitch("multi_learning1") { datapath_id "0x1" }
+      vswitch("multi_learning2") { datapath_id "0x2" }
+      vswitch("multi_learning3") { datapath_id "0x3" }
+      vswitch("multi_learning4") { datapath_id "0x4" }
+
+      vhost("host1")
+      vhost("host2")
+      vhost("host3")
+      vhost("host4")
+
+      link "multi_learning1", "host1"
+      link "multi_learning2", "host2"
+      link "multi_learning3", "host3"
+      link "multi_learning4", "host4"
+      link "multi_learning1", "multi_learning2"
+      link "multi_learning2", "multi_learning3"
+      link "multi_learning3", "multi_learning4"
+      """
+      And wait until "multi_learning_switch" is up
+      And *** sleep 1 ***
+
+    When I send 2 packets from host1 to host2
+    Then the total number of tx packets should be:
+      | host1 | host2 | host3 | host4 |
+      |     2 |     0 |     0 |     0 |
+    And the total number of rx packets should be:
+      | host1 | host2 | host3 | host4 |
+      |     0 |     2 |     0 |     0 |
+
+    When I send 3 packets from host3 to host4
+    Then the total number of tx packets should be:
+      | host1 | host2 | host3 | host4 |
+      |     2 |     0 |     3 |     0 |
+    And the total number of rx packets should be:
+      | host1 | host2 | host3 | host4 |
+      |     0 |     2 |     0 |     3 |
+
+    When I send 2 packets from host4 to host1
+    Then the total number of tx packets should be:
+      | host1 | host2 | host3 | host4 |
+      |     2 |     0 |     3 |     2 |
+    And the total number of rx packets should be:
+      | host1 | host2 | host3 | host4 |
+      |     2 |     2 |     0 |     3 |
+
+    When I send 4 packets from host2 to host3
+    Then the total number of tx packets should be:
+      | host1 | host2 | host3 | host4 |
+      |     2 |     4 |     3 |     2 |
+    And the total number of rx packets should be:
+      | host1 | host2 | host3 | host4 |
+      |     2 |     2 |     4 |     3 |
+
+    When I send 1 packets from host1 to host4
+    Then the total number of tx packets should be:
+      | host1 | host2 | host3 | host4 |
+      |     3 |     4 |     3 |     2 |
+     And the total number of rx packets should be:
+      | host1 | host2 | host3 | host4 |
+      |     2 |     2 |     4 |     4 |
+
+
+  Scenario: Send and receive packets
+    Given I try trema run "./src/examples/multi_learning_switch/multi-learning-switch.rb" with following configuration (backgrounded):
+      """
+      vswitch("multi_learning1") { datapath_id "0x1" }
+      vswitch("multi_learning2") { datapath_id "0x2" }
+      vswitch("multi_learning3") { datapath_id "0x3" }
+      vswitch("multi_learning4") { datapath_id "0x4" }
+
+      vhost("host1")
+      vhost("host2")
+      vhost("host3")
+      vhost("host4")
+
+      link "multi_learning1", "host1"
+      link "multi_learning2", "host2"
+      link "multi_learning3", "host3"
+      link "multi_learning4", "host4"
+      link "multi_learning1", "multi_learning2"
+      link "multi_learning2", "multi_learning3"
+      link "multi_learning3", "multi_learning4"
+      """
+      And wait until "MultiLearningSwitch" is up
+      And *** sleep 1 ***
+
+    When I send 2 packets from host1 to host2
+    Then the total number of tx packets should be:
+      | host1 | host2 | host3 | host4 |
+      |     2 |     0 |     0 |     0 |
+    And the total number of rx packets should be:
+      | host1 | host2 | host3 | host4 |
+      |     0 |     2 |     0 |     0 |
+
+    When I send 3 packets from host3 to host4
+    Then the total number of tx packets should be:
+      | host1 | host2 | host3 | host4 |
+      |     2 |     0 |     3 |     0 |
+    And the total number of rx packets should be:
+      | host1 | host2 | host3 | host4 |
+      |     0 |     2 |     0 |     3 |
+
+    When I send 2 packets from host4 to host1
+    Then the total number of tx packets should be:
+      | host1 | host2 | host3 | host4 |
+      |     2 |     0 |     3 |     2 |
+    And the total number of rx packets should be:
+      | host1 | host2 | host3 | host4 |
+      |     2 |     2 |     0 |     3 |
+
+    When I send 4 packets from host2 to host3
+    Then the total number of tx packets should be:
+      | host1 | host2 | host3 | host4 |
+      |     2 |     4 |     3 |     2 |
+    And the total number of rx packets should be:
+      | host1 | host2 | host3 | host4 |
+      |     2 |     2 |     4 |     3 |
+
+    When I send 1 packets from host1 to host4
+    Then the total number of tx packets should be:
+      | host1 | host2 | host3 | host4 |
+      |     3 |     4 |     3 |     2 |
+     And the total number of rx packets should be:
+      | host1 | host2 | host3 | host4 |
+      |     2 |     2 |     4 |     4 |

data/features/example.packetin_filter_config.feature

@@ -0,0 +1,91 @@
+Feature: Packet-In filter configuration example
+
+  As a Trema user
+  I want to configure packetin_filter
+  So that I can configuration filters of packetin_filter
+
+
+  Scenario: add filter
+    When I try trema run "./objects/examples/dumper/dumper" with following configuration (backgrounded):
+      """
+      event :port_status => "dumper", :packet_in => "filter", :state_notify => "dumper"
+      filter :lldp => "dumper", :packet_in => "dumper"
+      """
+      And wait until "dumper" is up
+      And *** sleep 2 ***
+      And I try to run "TREMA_HOME=`pwd` ./objects/examples/packetin_filter_config/add_filter"
+    Then the output should include:
+      """
+      A packetin filter was added ( match = [wildcards = 0xc, in_port = 1, dl_src = 00:00:00:00:00:00, dl_dst = 00:00:00:00:00:00, dl_vlan = 65535, dl_vlan_pcp = 0, dl_type = 0x800, nw_tos = 0, nw_proto = 10, nw_src = 10.0.0.1/32, nw_dst = 10.0.0.2/32, tp_src = 1024, tp_dst = 2048], service_name = dumper ).
+      """
+
+  Scenario: dump filter
+    When I try trema run "./objects/examples/dumper/dumper" with following configuration (backgrounded):
+      """
+      event :port_status => "dumper", :packet_in => "filter", :state_notify => "dumper"
+      filter :lldp => "dumper", :packet_in => "dumper"
+      """
+      And wait until "dumper" is up
+      And *** sleep 2 ***
+      And I try to run "TREMA_HOME=`pwd` ./objects/examples/packetin_filter_config/dump_filter"
+    Then the output should include:
+      """
+      2 packetin filters found ( match = [wildcards = 0x3fffff, in_port = 0, dl_src = 00:00:00:00:00:00, dl_dst = 00:00:00:00:00:00, dl_vlan = 0, dl_vlan_pcp = 0, dl_type = 0, nw_tos = 0, nw_proto = 0, nw_src = 0.0.0.0/0, nw_dst = 0.0.0.0/0, tp_src = 0, tp_dst = 0], service_name = dumper, strict = false ).
+      [#0] match = [wildcards = 0x3fffef, in_port = 0, dl_src = 00:00:00:00:00:00, dl_dst = 00:00:00:00:00:00, dl_vlan = 0, dl_vlan_pcp = 0, dl_type = 0x88cc, nw_tos = 0, nw_proto = 0, nw_src = 0.0.0.0/0, nw_dst = 0.0.0.0/0, tp_src = 0, tp_dst = 0], priority = 32768, service_name = dumper.
+      [#1] match = [wildcards = 0x3fffff, in_port = 0, dl_src = 00:00:00:00:00:00, dl_dst = 00:00:00:00:00:00, dl_vlan = 0, dl_vlan_pcp = 0, dl_type = 0, nw_tos = 0, nw_proto = 0, nw_src = 0.0.0.0/0, nw_dst = 0.0.0.0/0, tp_src = 0, tp_dst = 0], priority = 0, service_name = dumper.
+      """
+
+  Scenario: dump filter strict
+    When I try trema run "./objects/examples/dumper/dumper" with following configuration (backgrounded):
+      """
+      event :port_status => "dumper", :packet_in => "filter", :state_notify => "dumper"
+      filter :lldp => "dumper", :packet_in => "dumper"
+      """
+      And wait until "dumper" is up
+      And *** sleep 2 ***
+      And I try to run "TREMA_HOME=`pwd` ./objects/examples/packetin_filter_config/dump_filter_strict"
+    Then the output should include:
+      """
+      0 packetin filter found ( match = [wildcards = 0xc, in_port = 1, dl_src = 00:00:00:00:00:00, dl_dst = 00:00:00:00:00:00, dl_vlan = 65535, dl_vlan_pcp = 0, dl_type = 0x800, nw_tos = 0, nw_proto = 10, nw_src = 10.0.0.1/32, nw_dst = 10.0.0.2/32, tp_src = 1024, tp_dst = 2048], service_name = dumper, strict = true ).
+      """
+      And I try to run "TREMA_HOME=`pwd` ./objects/examples/packetin_filter_config/add_filter"
+      And I try to run "TREMA_HOME=`pwd` ./objects/examples/packetin_filter_config/dump_filter_strict"
+    Then the output should include:
+      """
+      1 packetin filter found ( match = [wildcards = 0xc, in_port = 1, dl_src = 00:00:00:00:00:00, dl_dst = 00:00:00:00:00:00, dl_vlan = 65535, dl_vlan_pcp = 0, dl_type = 0x800, nw_tos = 0, nw_proto = 10, nw_src = 10.0.0.1/32, nw_dst = 10.0.0.2/32, tp_src = 1024, tp_dst = 2048], service_name = dumper, strict = true ).
+      [#0] match = [wildcards = 0xc, in_port = 1, dl_src = 00:00:00:00:00:00, dl_dst = 00:00:00:00:00:00, dl_vlan = 65535, dl_vlan_pcp = 0, dl_type = 0x800, nw_tos = 0, nw_proto = 10, nw_src = 10.0.0.1/32, nw_dst = 10.0.0.2/32, tp_src = 1024, tp_dst = 2048], priority = 65535, service_name = dumper.
+      """
+
+  Scenario: delete filter strict
+    When I try trema run "./objects/examples/dumper/dumper" with following configuration (backgrounded):
+      """
+      event :port_status => "dumper", :packet_in => "filter", :state_notify => "dumper"
+      filter :lldp => "dumper", :packet_in => "dumper"
+      """
+      And wait until "dumper" is up
+      And *** sleep 2 ***
+      And I try to run "TREMA_HOME=`pwd` ./objects/examples/packetin_filter_config/delete_filter_strict"
+    Then the output should include:
+      """
+      0 packetin filter was deleted ( match = [wildcards = 0xc, in_port = 1, dl_src = 00:00:00:00:00:00, dl_dst = 00:00:00:00:00:00, dl_vlan = 65535, dl_vlan_pcp = 0, dl_type = 0x800, nw_tos = 0, nw_proto = 10, nw_src = 10.0.0.1/32, nw_dst = 10.0.0.2/32, tp_src = 1024, tp_dst = 2048], service_name = dumper, strict = true ).
+      """
+      And I try to run "TREMA_HOME=`pwd` ./objects/examples/packetin_filter_config/add_filter"
+      And I try to run "TREMA_HOME=`pwd` ./objects/examples/packetin_filter_config/delete_filter_strict"
+    Then the output should include:
+      """
+      1 packetin filter was deleted ( match = [wildcards = 0xc, in_port = 1, dl_src = 00:00:00:00:00:00, dl_dst = 00:00:00:00:00:00, dl_vlan = 65535, dl_vlan_pcp = 0, dl_type = 0x800, nw_tos = 0, nw_proto = 10, nw_src = 10.0.0.1/32, nw_dst = 10.0.0.2/32, tp_src = 1024, tp_dst = 2048], service_name = dumper, strict = true ).
+      """
+
+  Scenario: delete filter
+    When I try trema run "./objects/examples/dumper/dumper" with following configuration (backgrounded):
+      """
+      event :port_status => "dumper", :packet_in => "filter", :state_notify => "dumper"
+      filter :lldp => "dumper", :packet_in => "dumper"
+      """
+      And wait until "dumper" is up
+      And *** sleep 2 ***
+      And I try to run "TREMA_HOME=`pwd` ./objects/examples/packetin_filter_config/delete_filter"
+    Then the output should include:
+      """
+      2 packetin filters were deleted ( match = [wildcards = 0x3fffff, in_port = 0, dl_src = 00:00:00:00:00:00, dl_dst = 00:00:00:00:00:00, dl_vlan = 0, dl_vlan_pcp = 0, dl_type = 0, nw_tos = 0, nw_proto = 0, nw_src = 0.0.0.0/0, nw_dst = 0.0.0.0/0, tp_src = 0, tp_dst = 0], service_name = dumper, strict = false ).
+      """