The document describes steps for demonstrating the deployment of a VNF using openMANO on a remote pool of NFV compute nodes. Key steps include: 1. Modifying the gateway VM configuration and creating images of the VNF VMs to point to a remote openVIM. 2. Running scripts from the openMANO VM to clean the database, rebuild the environment pointing to the remote openVIM, and copy over the new VM images. 3. Deploying the VNF scenario from openMANO-GUI or via CLI and validating the deployment points to the remote resources. 4. Generating traffic between VNF VMs to test near line-rate 10Gbps performance

1. openMANO
demonstration/practical in
remote pool of servers
10 Jun 2015
ANTONIO LÓPEZ GRACIA
antonio.lopezgracia@telefonica.com
PABLO MONTES MORENO
pablo.montesmoreno@telefonica.com
Network Virtualisation – GCTO Unit

2. 2openMANO demonstration in remote pool of servers
 Purpose of the hands on session: to deploy the developed VNF on a remote
pool of NFV compute nodes to achieve maximum and deterministic
performance
 The openMANO that resides in a VM in the development workstation will
be modified to point to a remote openvim
 The remote openvim will deploy the VNF in a remote pool of NFV
compute nodes
 The VNF developed locally will achieve maximum performance (near 10
Gbps) without further changes

3. 3openMANO demonstration in remote pool of servers
OpenMANO-GUI
OpenMANO
OpenVIM
Workstation 1
OpenMANO-GUI
OpenMANO
OpenVIM
Workstation N
…

4. 4openMANO demonstration in remote pool of servers
…OpenMANO-GUI
OpenMANO
OpenVIM
Workstation 1
OpenMANO-GUI
OpenMANO
OpenVIM
Workstation N

5. 5
openMANO demonstration in remote pool of servers
OpenVIM
OpenFlow Switch
NFV Pool of servers…OpenMANO-GUI
OpenMANO
OpenVIM
Workstation 1
OpenMANO-GUI
OpenMANO
OpenVIM
Workstation N

6. 6openMANO demonstration in remote pool of servers
10.10.10.2/24
10.10.10.1/24
10.10.20.1/24
10.10.20.2/24
gateway
192.168.100.2/24
163.117.172.x/24
DHCP IP belonging to
the university lab.
One per gateway.
Bridge to provide
connectivity to lab
network
192.168.100.3/24
192.168.100.4/24
192.168.100.1/24
Gateway VM

7. 7openMANO demonstration in remote pool of servers
10.10.10.2/24
10.10.10.1/24
10.10.20.1/24
10.10.20.2/24
gateway
192.168.100.2/24
10.95.87.[190-229]/24
Static IP to remote pool.
One per gateway.
Bridge to provide
connectivity
192.168.100.3/24
192.168.100.4/24
192.168.100.1/24
Gateway VM

8. 8Hands on session: steps
1. Log into the gateway using virt-manager @host and change the gateway
network configuration to assign a static IP address –assigned by the instructor-
from Telefonica NFV Reference Lab
1. @VM gateway: ifconfig eth0 (get the IP address of eth0 interface)
2. @host: ssh dpdk@<gateway IP address>
3. @VM gateway: vi /etc/sysconfig/network-scripts/ifcfg-eth0
• Comment the following:
#BOOTPROTO=dhcp
• Uncomment the following:
BOOTPROTO=static
IPADDR=<IP address assigned by the instructor>
NETMASK=255.255.255.128
GATEWAY=10.95.87.129
DNS1=10.95.121.180
2. Shutdown the VMs of the VNF. From openMANO VM:
@VM openmano: $ openvim vm-list
@VM openmano: $ openvim vm-shutdown –f
# check status and wait until all VMs are shutdown (INACTIVE)
@VM openmano: $ openvim vm-list

9. 9Hands on session: steps
3. Create images of the modified VMs:
@VM openmano: $ openvim vm-createImage <VM gateway-name> my_gateway
@VM openmano: $ openvim vm-createImage <VM l3fwd-name> my_l3fwd
@VM openmano: $ openvim image-list my_l3forward -v
@VM openmano: $ openvim image-list my_gateway -v
4. From openmano VM execute the following to automatically clean the
openmano DDBB and rebuild the environment pointing to a remote openvim
located in the lab Telefonica IP 10.95.87.240
@host: $ ./route_tid.sh
@VM openmano: $ source ./training-change2server.sh 10.95.87.240
5. @host: Follow the screen instructions to copy remotely the new images
6. Verify the new environment: check created VNFs, image paths, scenarios
@VM openmano: $ less yamls/server/gateway.yaml
@VM openmano: $ less yamls/server/l3forward.yaml
@VM openmano: $ openmano vnf-list
@VM openmano: $ openmano vnf-list gateway -v
@VM openmano: $ openmano vnf-list l3forward -v
@VM openmano: $ openmano scenario-list

10. 10Hands on session: steps
7. Wait until the instructor allows you to continue
8. From openmano-GUI deploy again the VNF by pressing “Deploy”
From the GUI you will be able to watch the progress of the deployment
As an alternative, you can deploy the scenario by using
@VM openmano: $ openmano scenario-deploy dpdk_training dpdk_training
9. Log into the gateway twice, to get two terminals tabs connected:
@VM openmano: $ ssh dpdk@<IP assigned by the instructor>
@VM openmano: $ ssh dpdk@<IP assigned by the instructor>
10. From the gateway use one terminal tab to connect to the traffic source
and another to the traffic sink, and maximize both tabs:
@VM gateway: connect to source: $ ssh dpdk@192.168.100.2
@VM gateway: connect to sink: $ ssh dpdk@192.168.100.4
11. Launch pktgen both in the source and the sink by doing:
@VM source: $ ./pktgen.sh
@VM sink: $ ./pktgen.sh

11. 11Hands on session: steps
12. Start the sending of traffic. On the source pktgen VM
@VM source: > start 0
13. Check in the traffic sink the received traffic data rate. It should be very
close to the maximum line data rate, 10 Gbps.
14. Stop pktgen in both the source and the sink
@VM source: > quit
@VM sink: > quit
15. DO NOT FORGET: from openMANO GUI delete the scenario instance by
pressing “Delete”. This is needed to free the resources in the remote pool so
other scenarios can be deployed
As an alternative, you can delete the scenario instance by using from openMANO:
@VM openmano: $ openmano instance-scenario-list
@VM openmano: $ openmano instance-scenario-delete dpdk_training