Fix example .conf files to support ruby gems installed environment.
Merge pull request #26 from y-higuchi/fix_example_conf

Fix topology's example .conf files to support ruby gems installed environment.
[sliceable_switch] Added --set_reverse_flow option

This is a option for sliceable_switch to setup going and returning
flows for IPv4 packets when the controller received packet-in.
This could reduce a number of packet-in and resolve_path,
and also is useful for accepting packets that are response to
a request packet from dynamic client tdp/udp ports like 30001.

WARN: The returning flow is modified without filter check.
      This might be harmful to user's security policy.
added mc/bc check to packet_to_set_reverse_path()
Merge pull request #27 from r-mibu/reverse

[sliceable_switch] Added --set_reverse_flow option
fixed Issue #28
Merge pull request #29 from r-mibu/rest-if-networks

fixed Issue #28
[sliceable_switch] fixed test for REST-API /networks

Fixed test(feature) for REST interface to configure networks.
In this test, all steps were done via REST API (e.g.. A created
network object was asserted with getting the object via REST API).
Now, all steps except the test target operation in a scenario
are done by accessing the slice DB directly.
This patch also includes the following:
  - added test for attachment network objects
  - changed repeated "Then" to "And"
  - fixed typos
Added an assretion to ensure the number of records
Merge pull request #30 from r-mibu/rest-if-networks

[sliceable_switch] fixed test for REST-API /networks
[sliceable_switch] fixed config.cgi to meet the API Spec

Fixed create_attachment_on_port() in config.cgi to meet the
REST-API specification [1].

"POST /networks/existing/ports/non-existing/attachments"
According to the REST-API specification [1], the response for
a POST request to create an attachment object to non-existing
port object, should be "422 Unprocessable Entity". However,
the response was "202 Accepted". Now, the response is "422
Unprocessable Entity".

This patch also includes tests of REST-API to configure ports.

[1] https://github.com/trema/apps/wiki/Sliceable-Network-Management-API#create-an-attachment-object-to-a-port-object
Merge pull request #31 from r-mibu/rest-if-ports

[sliceable_switch] fixed config.cgi to meet the API Spec
[sliceable_switch] fixed config.cgi to create wildcards properly

When the REST-API received a POST request to /filters without
wildcards, the wildcards are not created properly. The reason
is that unspecified parameters are defined as 0 at the oct()
iterpretation before set_default_filter_criteria() is called,
while wildcards are created by checking parameters are defined
or not. This patch fixed this by adding condition to the oct()
iterpretation so that unspecified parameters are kept undefined.

This patch also includes tests of REST-API to configure filters.
Merge pull request #32 from r-mibu/rest-if-filters

[sliceable_switch] fixed config.cgi to create wildcards properly
[sliceable_switch] fixed vlan_tag modification

Fixed vlan_tag modification in making path.

There was no actions to modify vlan_id in flow entries which
setup by this controller after "flow_manager support".
In a case which source port and dest port are in different
vlan_ids, some packets were sent properly from the controller
until flow entries are setup. After that, packets were sent
with mismatched vlan_id due to source port vlan_id was kept.

This patch adds a vlan_tag modification action to the flow
entry at the last switch on the path, so that user can receive
packets with correct vlan_id and the controller can use same
openflow_match. This is the same way to update vlan_tag which
sliceable_switch did before "flow_manager support".
[sliceable_switch] added vlan_mod.feature
[sliceable_switch] fixed actions to update vid
[sliceable_switch] passing in_vid instead of match.dl_type
Merge pull request #33 from r-mibu/vlan-mod

[sliceable_switch] fixed vlan_tag modification
Add transaction manager.