{"id":9768,"date":"2016-02-10T12:50:45","date_gmt":"2016-02-10T10:50:45","guid":{"rendered":"https:\/\/blog.zhaw.ch\/icclab\/?p=9768"},"modified":"2016-12-12T11:24:04","modified_gmt":"2016-12-12T09:24:04","slug":"service-function-chaining-using-the-sdk4sdn","status":"publish","type":"post","link":"https:\/\/blog.zhaw.ch\/icclab\/service-function-chaining-using-the-sdk4sdn\/","title":{"rendered":"Service Function Chaining using the SDK4SDN"},"content":{"rendered":"

Last week in Athens we integrated the SDK4SDN aka Netfloc in the T-Nova<\/a> Pilot testbed in order to showcase service function chaining using two endpoints and two VNFs (Virtual Network Functions).<\/p>\n

NETwork FLOws for Clouds (Netfloc) is an open source SDK for datacenter network programming developed in the ICCLab SDN initiative. It is comprised of set of tools and libraries that interoperate with the OpenDaylight controller. Netfloc exposes REST API abstractions and Java interfaces for network programmers to enable optimal integration in cloud datacenters and fully SDN-enabled end-to-end management of OpenFlow enabled switches.<\/p>\n

<\/p>\n

The PoP consisted of three OpenStack nodes (Juno), one node reserved for the SDN controller (the SDK) and one physical switch, Figure 1.<\/p>\n

\"sdk_testbed_demokritos\"<\/a><\/p>\n

Figure 1. Pilot testbed setup used for the SFC<\/p>\n

The SDK4SDN has been implemented in Java programming language and it is currently integrated as a holistic component that includes a Lithium<\/a> release\u00a0of the OpenDaylight controller. It has been to date tested and supported using OpenStack Kilo (in the ZHAW SDN testbed) and OpenStack Juno (in the Demokritos<\/a> testbed).<\/p>\n

To use SDK4SDN, the network needs to be fully SDN enabled through the OVS switches. The network interfaces of the switch should be connected to all of the other nodes.<\/p>\n

Firewall Configuration of Neutron Node<\/strong><\/p>\n

The default SFC implementation requires disabling iptables rules that would prevent non-standard forwarding to OpenStack instances and avoid\u00a0dropping the packets that are transmitted by Nova instances. Nova-compute was prevented from creating the iptables rules by configuring the Noop driver<\/a>\u00a0in the\u00a0\/etc\/neutron\/plugins\/ml2\/ml2_conf.ini <\/em>file on\u00a0<\/em>the control and the\u00a0\/etc\/nova\/nova.conf<\/em>\u00a0file in the compute nodes.<\/p>\n

Deployment and Installation<\/strong><\/p>\n

The SDK4SDN can only detect OVS topology. A Physical switch that supports OVS is for example the Pica8 switch in OVS mode.\u00a0The OVS configuration on the compute nodes has to be setup such that the switches are connected in layer 2 domain. For each compute node, an OVS port was configured that bridges the physical interfaces. Note that if a compute host has a single physical interface, then the IPs on that interface need to be attached to the internal interface of the OVS bridge.<\/p>\n

The OpenDaylight controller needs to be reachable via ports TCP 6640 and TCP 6633 from every OVS and also reachable via HTTP from an Orchestrator on the Northbound in order to accept the SFC instructions via REST calls.<\/p>\n

The steps in order to setup the environment are the following:<\/p>\n

    \n
  1. Login to all OpenStack nodes, the switch and ODL node as root <\/em><\/li>\n
  2. Download the SDK4SDN form the GitHub page<\/a>\u00a0and compile the code using: mvn clean install<\/em><\/li>\n
  3. Configure the OVSs on each of the nodes to connect to the IP of the Open Daylight controller as well as set up the ODL as manager on port 6640:<\/li>\n<\/ol>\n
    ovs-vsctl set-manager tcp:Controller_IP:6640\r\novs-vsctl set-contorller tcp:Controller_IP:6633\r\n<\/code><\/pre>\n
    With these basic steps the SDK is ready to be started as long as we have the environment prepared for this. To make sure all the state is clear before running the SDK, the following steps and checkups are required:<\/p>\n