OPNFV 101: How To Get From Bare Metal to Cloud. Wenjing Chu, Dell Dan Radez, Red Hat Vinod Pandarinathan, Cisco

Transcription

1 OPNFV 101: How To Get From Bare Metal to Cloud Wenjing Chu, Dell Dan Radez, Red Hat Vinod Pandarinathan, Cisco

2 From Bare Metal to an NFV Cloud in 3 Steps 1) Create your own OPNFV pod Wenjing will present a fast paced tutorial on how to bring up an OPNFV Arno SR1 powered pod. 2) Deploy your VNFs on OPNFV Dan will show you first hand how to use Tacker to launch VNFs and chain them together. 3) Integrate virtual networking Vinod will dive deeper into Openstack Neutron/ODL and OVS, and provides hands-on tips on debugging. 11/7/15 OPNFV 101 2

3 Here is the Plan The goal is to set up an OPNFV pod in lab that can run realistic use cases We will use the latest OPNFV Arno SR1 We will use Foreman to manage and provision bare metal servers in this tutorial Deploy Openstack Juno and Opendaylight Helium Run Qtip to benchmark

4 What s in a pod? NFV/private Port 1 network for PXE boot (Admin) 1 network for Internet access (P ublic) (not shown Lights Out Manag ement, e.g. Dell idrac) 1 network (or more) for NFV dat a path: 10G or higher (Private) (non shown - additional storage network if desirable) There are other options but this is what we use/recommend Interne t/public port PXE/admin port 1 jump server 3 control nodes in HA, OR 1 for non -HA 1 or more compu te nodes

5 Config/Collect system info for YML spec NFV/private Port Interne t/public port PXE/admin port 1 jump server For each node: BIOS enable PXE boot on the admin port, and set it to be the first boot de v. Collect these: MAC of the PXE/admin port: mac_ address MAC of the LightsOut port (e.g. D ell idrac): bmc_mac IP of the LightsOut port: bmc_ip MAC of the Private/NFV port: priv ate_mac 3 control nodes in HA, OR 1 for non -HA 1 or more compu te nodes

6 Get the deployment images to your jump server Use Foreman ISO to install CentOS7 on the Foreman Jump-Server: The ISO packs the required files, including CentOS7 Or, if your jump server is already installed with CentOS7, you can download the rest from Unzip it and cd to genesis/foreman/ci Either way, you get the ci directory with deployment files and scripts

7 Edit the YML spec file Edit: opnfv_ksgen_settin gs.yml Enter the MAC and IP addresses Provide login credentials Name them One section for each control and compute node

8 Now let Foreman deploy it cd genesis/foreman/ci./deploy.sh admin_nic <interface_name> -private_nic <interface_name> - public_nic <interface_name> -base_config <full_path_to_opnfv_ksgen_settings.yml> Expect a few hours

9 Monitor progress on Foreman UI After a few minutes On the jump server cd /var/opt/opnfv/fore man_vm Run vagrant ssh

10 Also check on Opendaylight ODL runs on the first controller Point web browser to <controller1_ip>:8181/dlux/intex.html

11 Use Qtip to quickly benchmark it For example: use DPI to benchmark compute python qtip.py s compute b dpi-parallel.yaml

12 Use Qtip to quickly benchmark it

13

14 From Bare Metal to an NFV Cloud in 3 Steps 1) Create your own OPNFV pod Wenjing will present a fast paced tutorial on how to bring up an OPNFV Arno SR1 powered pod. 2) Deploy your VNFs on OPNFV Dan will show you first hand how to use Tacker to launch VNFs and chain them together. 3) Integrate virtual networking Vinod will dive deeper into Openstack Neutron/ODL and OVS, and provides hands-on tips on debugging. 11/7/15 OPNFV

15 Project Apex in Bramaputra RDO Manager based ( Triple-O driven install OpenStack centric components

16 Project Apex in Bramaputra Instack Control Node Control Node Control Node Compute Node Compute Node Compute Node Undercloud Overcloud

17 Tacker in Project Apex SFC project needed a VNFM Tacker existed as a VNF Orchestration Tool Part of the OpenStack Ecosystem Began adding SFC support to Tacker

18 Project Apex / Tacker / SFC Demo VFN Definition (yaml template) VNF Creation (launches VFN from template SFC (chains VNFs) Driver Based SDN interaction OpenDaylight NetvirtSFC OpenvSwitch + NSH support

19 From Bare Metal to an NFV Cloud in 3 Steps 1) Create your own OPNFV pod Wenjing will present a fast paced tutorial on how to bring up an OPNFV Arno SR1 powered pod. 2) Deploy your VNFs on OPNFV Dan will show you first hand how to use Tacker to launch VNFs and chain them together. 3) Integrate virtual networking Vinod will dive deeper into Openstack Neutron/ODL and OVS, and provides hands-on tips on debugging. 11/7/15 OPNFV

20 ETSI NFV Architecture - VIM Layer

21 Neutron Controller ML2 Plug-In OpenDaylight NorthBound API Layer - REST APIs OpenDaylight Neutron REST- API OVSDB Neutron Application Model Driven SAL (MDSAL) Configuration Service Inventory Service Connection Service Flow Programmer Inventory Service Connection Service Flow Programmer OVSDB South- bound Plugin OpenFlow 1.0 SB Plugin OpenFlow 1.3 SB Plugin OVSDB Protocol Library OpenFlow 1.0 Plugin OpenFlow 1.3 Plugin Bidirectional JSON- RPC Library Netty.io OpenFlow 1.0 Library java.nio.socket OpenFlow 1.0 OpenVSwitch OpenFlow 1.3 Library Netty io

22 Potential Issues seen during deployment Neutron network create fails Neutron port create fails Nova boot failure Can t Ping VM IP address

23 Are the required services are up? Check ODL server is started and responds to http requests? Check neutron-server is up and running. Check ML2 config for mechanism driver opendaylight and url/port/username/password Openvswitch service is started and opendaylight manages the bridges.

24 Check ODL server Use karaf console, and check if right features are installed. Karaf>feature:list grep openstack Karaf>feature:list grep ovs Run HTTP requests to check if the service is responding curl -u admin:admin curl -u admin:admin

25 Tracking resource status CRUD on neutron resource such as networks, ports and subnets. Neutron net- list Neutron port- list odl- 1 devstack]$ neutron port- list db19-484e- af96-56ed2c1e52dc fa:16:3e:b1:ba:82 {"subnet_id": "e340d8fd- 075a e- 43aa9782ff52", "ip_address": " c dc6- b5ab- b6fd10423bfb fa:16:3e:0d:f6:22 {"subnet_id": "e340d8fd- 075a e- 43aa9782ff52", "ip_address": " } [odl@fedora- odl- 1 devstack]$ curl - u admin:admin { "ports" : [ { "id" : "194c dc6- b5ab- b6fd10423bfb", "network_id" : "98b8fb6c- 210c- 4c54- a90f- a2fcf178c5cc", "name" : "", "admin_state_up" : true, "mac_address" : "FA:16:3E:0D:F6:22", "fixed_ips" : [ { "ip_address" : " ", "subnet_id" : "e340d8fd- 075a e- 43aa9782ff52" } ], "device_id" : "3d70cd19- a e- b0ae- da697d54763f", "device_owner" : "compute:none", "tenant_id" : "bac644a6c1e7402a86f74567ca855c0d" }, {

26 Openstack node topology Controller/Compute- 1 Fedora- odl- 1 Compute- 2 Fedora- odl- 2 VM1 addr:fa:16:3e:cd:09:76 VM1: addr:fe:16:3e:0d:f6:22 VM2: addr:fa:16:3e:83:42:3b

27 Openvswitch ovs-vsctl show -vs-vs odl- 2 devstack]$ sudo ovs- vsctl show 17074e89-2ac5-4bba- 997a- 1a5a3527cf56 Manager "tcp: :6640" is_connected: true Bridge br- int Controller "tcp: :6633" is_connected: true fail_mode: secure Port br- int Interface br- int Port "gre " Interface "gre " type: gre options: {key=flow, local_ip=" ", remote_ip=" "} Port "tap194c " Interface "tap194c " ovs_version: "2.0.1 [odl@fedora- odl- 2 devstack]$ ifconfig tap194c tap194c : flags=4163<up,broadcast,running,multicast> mtu 1500 inet6 fe80::fc16:3eff:fe0d:f622 prefixlen 64 scopeid 0x20<link> ether fe:16:3e:0d:f6:22 txqueuelen 500 (Ethernet) RX packets 77 bytes 6912 (6.7 KiB)

28 OVS-OFCTL dump-ports-desc odl- 2 devstack]$ sudo ovs- ofctl - O OpenFlow13 dump- ports- desc br- int OFPST_PORT_DESC reply (OF1.3) (xid=0x2): 1(gre ): addr:ce:49:90:8e:7b:a9 config: 0 state: 0 speed: 0 Mbps now, 0 Mbps max 2(tap194c ): addr:fe:16:3e:0d:f6:22 config: 0 state: 0 current: 10MB- FD COPPER speed: 10 Mbps now, 0 Mbps max LOCAL(br- int): addr:ea:34:e4:16:b9:4a config: 0 state: 0 speed: 0 Mbps now, 0 Mbps max

29 OVS-OFCTL dump-flows odl- 2 devstack]$ sudo ovs- ofctl - O OpenFlow13 dump- flows br- int OFPST_FLOW reply (OF1.3) (xid=0x2): cookie=0x0, duration= s, table=0, n_packets=66, n_bytes=5890, send_flow_rem in_port=2,dl_src=fa:16:3e:0d:f6:22 actions=set_field:0x1- >tun_id,goto_table:10 cookie=0x0, duration= s, table=0, n_packets=75, n_bytes=7094, send_flow_rem tun_id=0x1,in_port=1 actions=goto_table:20 cookie=0x0, duration= s, table=0, n_packets=0, n_bytes=0, send_flow_rem priority=8192,in_port=2 actions=drop cookie=0x0, duration= s, table=0, n_packets=574, n_bytes=52234, send_flow_rem dl_type=0x88cc actions=controller:56 cookie=0x0, duration= s, table=10, n_packets=0, n_bytes=0, send_flow_rem priority=8192,tun_id=0x1 actions=goto_table:20 cookie=0x0, duration= s, table=10, n_packets=20, n_bytes=1628, send_flow_rem priority=16384,tun_id=0x1,dl_dst=01:00:00:00:00:00/01:00:00:00:00:00 actions=output:1,goto_table:20 cookie=0x0, duration= s, table=10, n_packets=46, n_bytes=4262, send_flow_rem tun_id=0x1,dl_dst=fa:16:3e:cd:09:76 actions=output:1,goto_table:20 cookie=0x0, duration= s, table=10, n_packets=0, n_bytes=0, send_flow_rem tun_id=0x1,dl_dst=fa:16:3e:83:42:3b actions=output:1,goto_table:20 cookie=0x0, duration= s, table=20, n_packets=46, n_bytes=4262, send_flow_rem actions=drop cookie=0x0, duration= s, table=20, n_packets=39, n_bytes=3214, send_flow_rem priority=16384,tun_id=0x1,dl_dst=01:00:00:00:00:00/01:00:00:00:00:00 actions=output:2 cookie=0x0, duration= s, table=20, n_packets=51, n_bytes=5118, send_flow_rem tun_id=0x1,dl_dst=fa:16:3e:0d:f6:22 actions=output:2 priority=8192,tun_id=0x1

30 References 1. opendaylight- juno- openstack/ 2. openstack- integration- devstack- fedora- 20/ 3. integration- with- openstack- neutron- a- tutorial

31 Q & A