Esta stablishing Service Func ncti tion Ch Chaining Arc rchite - - PowerPoint PPT Presentation

▶
esta stablishing service func ncti tion ch chaining
SMART_READER_LITE
LIVE PREVIEW

Esta stablishing Service Func ncti tion Ch Chaining Arc rchite - - PowerPoint PPT Presentation

Aug 20, 2023 242 likes •648 views

Esta stablishing Service Func ncti tion Ch Chaining Arc rchite tecture on on OpenStack for for Inte ternet t VNF Use-case A A joint research ch & PoC oC activit itie ies among AP APAC(Asia ia-Pacif ific ic) ) Telc lco Se

slide-1
SLIDE 1

Esta stablishing Service Func ncti tion Ch Chaining Arc rchite tecture on

  • n OpenStack for

for Inte ternet t VNF Use-case

A A joint research ch & PoC

  • C activit

itie ies among AP APAC(Asia ia-Pacif ific ic) ) Telc lco Se Serv rvic ice Pro rovid ider

Lab Cloud & Node Platform Infrastructure Research & Standardization TELKOM – Divisi Digital Service (n.k.a Media & Digital Department)

Ibrahim Zein Abdillah

(900058) – Eng. 2 Service Control

Restu Nursobah

Research Assistant

&

slide-2
SLIDE 2

About Us

Ibrahim Zein Abdillah

29 years old

Restu Nursobah

23 years old Employment Record :

  • (2014 – Present) PT. Telekomunikasi Indonesia, Tbk.
  • Eng. 2 Service Control – DDS/MDD (2017 – Present)
  • Eng. 3 Service Control – IDeC/DDS (2014 - 2017)
  • (2012-2013) PT. Huawei Services
  • OSS Competence Center Engineer (2013)
  • NOC SLM Carrier And Roaming Engineer (2012 – 2013)

Employment Record :

  • (2019 – Present) Lab. CNP (Cloud & Node Platform) – Telkom DDS
  • Research Assistant (2019 – Present)
  • (2018) Telkom DDS - Student Internship Program
  • Lab CNP-IRS Telkom DDS Intern (2019)

Bachelor of Engineering (B.Eng.), Telecommunication & Multimedia – Electrical Engineering [2018 – 2012]

Education : Education :

Bachelor of Engineering (B.Eng.), Telecommunication Engineering [2015 – 2019]

Award :

  • ASEAN Outstanding Engineering Award [2018]
  • Top 5 Best Employee Telkom Group BP V [2019]

Certification : Certification :

ibrahim.zein@telkom.co.id ibrahimza27@gmail.com Ibrahim-zein-abdillah restunursobah restu.nursobah@gmail.com

slide-3
SLIDE 3

Outline

  • 1. Overview
  • 2. Implementation
  • 3. Progress &

Results

A brief overview of NFV; Network acceleration technology; SFC; SPP; & ATII-WP4 Network topology; SFC on OVS, OVS-DPDK & SPP Progress & results; Working Project timeline

slide-4
SLIDE 4
  • 1. Overview

A brief overview of:

  • NFV (Network Function Virtualization),
  • Network acceleration technology,
  • SFC (Service Function Chaining),
  • SPP (Soft Patch Panel),
  • ATII-WP4 (APAC Telco Innovation Initiative –

Working Project 4)

slide-5
SLIDE 5

NFV (Network Function Virtualization)

NFV (Network function virtualization) is a concept or principle of separating network functions from the hardware they run on by using virtual hardware abstraction. This aims to transform the way that network operators architect networks by evolving standard IT virtualisation technology to consolidate many network equipment types onto industry standard high volume servers, switches and storage, which could be located in Datacentres, Network Nodes and in the end user premises.

source: ETSI

  • NFVI: Network Fuction Virtualization

Infrastructure

  • VNF: Virtualized Network Function
  • NFV-MANO: NFV Management &

Orchestration

slide-6
SLIDE 6

NFV Deployment Model

source: materi NFV Cisco & Ericsson VNF Virtualization Hardware TCO & Risk

slide-7
SLIDE 7

NFV Driver & Challenges

source: sdxcentral

slide-8
SLIDE 8

Network Acceleration Technology

OVS

(Open vSwitch)

PCI-Passtrough OVS-DPDK

(OVS – Data Plane Development Kit)

SR-IOV

(Single-Root I/O Virtualization)

Kernel space User space VNF (s)

vnic vnic vnic vnic vnic

VNF A VNF B VNF (s) VNF A VNF B

vnic

OVS Network Card Network Card Network Card Network Card Network Card OVS- DPDK

VF

Kernel space User space User space User space Kernel space Kernel space

VF PF PF Driver

  • Regular OVS traffic
  • Kernel interrupts & memory copy
  • Bypass kernel
  • Direct passtrough from NIC to vNIC
  • Dedicated NIC to vNIC mapping
  • Bypass kernel
  • DPDK traffic
  • Poll mode driver
  • Bypass kernel
  • Direct passtrough from vNIC to VF
  • Dedicated NIC for multiple vNIC(s)

DHA (Direct Hardware Access) vSwitch

Flex exibility Perf rformance Cost Cost Ef Efficien ency

slide-9
SLIDE 9

SFC (Service Function Chaining)

source: sdxcentral

Network service chaining, also known as service function chaining (SFC) is a capability that uses software-defined networking (SDN) capabilities to create a service chain of connected network services (such as L4-7 like firewalls, network address translation [NAT], intrusion protection) and connects them in a virtual chain. Network service chaining capabilities mean that a large number of virtual network functions can be connected together in an NFV

  • environment. Because it’s done in software using virtual circuits, these connections can be set up and torn down as needed with

service chain provisioning through the NFV orchestration layer.

slide-10
SLIDE 10

SPP (Soft Patch Panel)

  • Flexibility of configuration and Performance of

processing are the key requirements for virtual switching function for service chaining. It's difficult to satisfy both of them.

  • SPP(Soft Patch Panel) is a new technology to meet

both of requirements with Intel DPDK.

source: NTT, ATII

slide-11
SLIDE 11

ATII - WP4

Pr Proj

  • ject

The heme Me Member WP1 High value-added network services NTT Telkom WP2 Server platform virtualization Telkom NTT WP3 Flexible access network virtualization NTT Telkom VNPT WP4 vSwitch for service function chaining NTT Telkom VNPT WP5 Ensuring the reliability of ICT equipment by reducing lightning malfunction NTT Telkom

  • NTT and Telkom Indonesia established ATII in April 2017, to promote

the creation of new network services considering social problems in the APAC region and to promote technical studies.

  • ATII has extended to three operators structure with VNPT’s joining.

source: ATII Asia Pacific Telecommunication Innovation Initiative Working Project 4

slide-12
SLIDE 12
  • 2. Implementation
  • SFC research topology (virtualized internet access

service use case)

  • SFC implementation on OpenStack with OVS
  • SFC implementation on OpenStack with OVS-DPDK
  • SFC implementation on OpenStack with SPP
slide-13
SLIDE 13

(virtualized internet access service use case)

Instances/ VM in Openstack:

client : Ubuntu Server 16.04 + LXDE, iperf, traceroute server : Ubuntu Server 16.04, iperf, traceroute, nginx ntopng : Ubuntu Server 18.04, ntopng

Client-3 (iPerf) vDPI-1 (ntopng) vDPI-2 (ntopng-2) Server (iPerf Server)

ens6 ens3 ens3 IP: 192.168.0.99 IP: 192.168.0.101 IP: 192.168.0.100

Client-1 (iPerf) Client-2 (iPerf)

ens3 IP: 192.168.0.97 ens3 IP: 192.168.0.28 ens3 IP: 192.168.0.31

SFC research topology

slide-14
SLIDE 14

Neutron Port

Source : https://docs.openstack.org/newton/networking-guide/config-sfc.html

SFC Implementation on Openstack with OVS

slide-15
SLIDE 15

enable_plugin networking-sfc <GITURL> [GITREF] Example : enable_plugin networking-sfc https://opendev.org/openstack/networking-sfc stable/queens NETWORKING_SFC_DIR="$DEST/networking-sfc" NEUTRON_FLOWCLASSIFIER_PLUGIN="networking_sfc.services.flowclassifier.plugin.FlowClassifierPlugin" NEUTRON_SFC_PLUGIN="networking_sfc.services.sfc.plugin.SfcPlugin" NEUTRON_FLOWCLASSIFIER_DRIVERS="ovs" NEUTRON_SFC_DRIVERS="ovs"

SFC SFC Insta nstala latio ion in n Ope penstack - Usi Using ng loc

  • cal.con
  • nf

Source : https://opendev.org/openstack/networking-sfc/src/branch/master/devstack

SFC Implementation on Openstack with OVS (2)

slide-16
SLIDE 16

1.

  • 1. Insta

stall pyth python-networking-sfc fc First Step install python-networking-sfc, use command: $ pip install -c --user https://opendev.org/openstack/requirements/raw/branch/master/upper-constraints.txt?h=stable/queens networking-sfc==6.0.0 Make sure the networking sfc version matches the openstack version used, for example here we use the version 6 (Queens)

SFC SFC Insta nstala latio ion in n Ope penstack - Manu anual

2.

  • 2. Co

Conf nfigure neu neutro ron.conf Enable the service plugins in neutron-server by adding them in neutron.conf $ sudo nano /etc/neutron/neutron.conf add syntax flow_classifier and sfc on service_plugins service_plugins = flow_classifier,sfc [sfc] drivers = ovs [flowclassifier] drivers = ovs

Source : https://docs.openstack.org/networking-sfc/queens/install/index.html

SFC Implementation on Openstack with OVS (3)

slide-17
SLIDE 17

SFC Implementation on Openstack with OVS (4)

3.

  • 3. Co

Conf nfigure ml ml2_conf. f.ini enable the networking-sfc extension in the Open vSwitch agent. The configuration file name can change, the default one is /etc/neutron/plugins/ml2/ml2_conf.ini [agent] extensions = sfc

SFC SFC Insta nstala latio ion n in n Ope penstack - Manu anual

4.

  • 4. Res

estart an and d upda pdate da data tabase set setup After all done, you can run some command $ systemctl restart devstack@q-svc

  • r

$ systemctl restart neutron-server $ systemctl restart devstack@q-agt

  • r

$ systemctl restart neutron-openvswitch-agent $ neutron-db-manage --subproject networking-sfc upgrade head

Source : https://docs.openstack.org/networking-sfc/queens/install/index.html

slide-18
SLIDE 18

SFC Implementation on Openstack with OVS (5)

Serv Servic ice e Cha Chain in

Client-3 (iPerf-3) vDPI-1 (ntopng) vDPI-2 (ntopng-2) Server (iPerf Server)

ens6 ens3 ens3 IP: 192.168.0.99 IP: 192.168.0.101 IP: 192.168.0.100

ingress ingress egress egress

ntopng ntopng-2

Client-1 (iPerf-1) Client-2 (iPerf-2)

ens3 IP: 192.168.0.97 ens3 IP: 192.168.0.28 ens3 IP: 192.168.0.31

Service Chain 1 Service Chain 3 Service Chain 2 sfc-client sfc-client-2 sfc-client-3 sfc-server

slide-19
SLIDE 19

Client-3 (iPerf-3)

SFC Implementation on Openstack with OVS (6)

Cr Create Por Port Pa Pair ir

vDPI-1 (ntopng) vDPI-2 (ntopng-2) Server (iPerf Server)

ens6 ens3 ens3 IP: 192.168.0.99 IP: 192.168.0.101 IP: 192.168.0.100

ingress ingress egress egress

ppntopng ppntopng-2

Client-1 (iPerf-1) Client-2 (iPerf-2)

ens3 IP: 192.168.0.97 ens3 IP: 192.168.0.28 ens3 IP: 192.168.0.31

#po #port pai pair $ openstack sfc port pair create --ingress (port) --egress (port) na name_port_pair

slide-20
SLIDE 20

Client-3 (iPerf-3)

SFC Implementation on Openstack with OVS (7)

Cr Create Por Port Pa Pair ir Gr Group

  • up

vDPI-1 (ntopng) vDPI-2 (ntopng-2) Server (iPerf Server)

ens6 ens3 ens3 IP: 192.168.0.99 IP: 192.168.0.101 IP: 192.168.0.100

ingress ingress egress egress

ppgntopng ppgntopng-2

Client-1 (iPerf-1) Client-2 (iPerf-2)

ens3 IP: 192.168.0.97 ens3 IP: 192.168.0.28 ens3 IP: 192.168.0.31

#po #port pai pair gr group $ openstack sfc port pair group create --port-pair (port_pair_1) --port-pair (port_pair_n) na name_port rt_pair_gro roup

slide-21
SLIDE 21

Client-3 (iPerf-3)

SFC Implementation on Openstack with OVS (8)

Cr Create Fl Flow

  • w Cl

Clas assif sifie ier r for for Serv Service Ch Chain 1

vDPI-1 (ntopng) vDPI-2 (ntopng-2) Server (iPerf Server)

ens6 ens3 ens3 IP: 192.168.0.99 IP: 192.168.0.101 IP: 192.168.0.100

Client-1 (iPerf-1) Client-2 (iPerf-2)

ens3 IP: 192.168.0.97 ens3 IP: 192.168.0.28 ens3 IP: 192.168.0.31

#f #flow clas classifi fier $ openstack sfc flow classifier create --ethertype IPv4 --source-ip-prefix 192.168.0.97/32 --destination-ip-prefix 192.168.0.101/32 --logical- source-port sfc-client --logical-destination-port sfc-server fcn cnto topng

slide-22
SLIDE 22

Client-3 (iPerf-3)

SFC Implementation on Openstack with OVS (9)

Cr Create Fl Flow Cl Clas assif ifie ier r for for Serv Service Ch Chain 2

vDPI-1 (ntopng) vDPI-2 (ntopng-2) Server (iPerf Server)

ens6 ens3 ens3 IP: 192.168.0.99 IP: 192.168.0.101 IP: 192.168.0.100

Client-1 (iPerf-1) Client-2 (iPerf-2)

ens3 IP: 192.168.0.97 ens3 IP: 192.168.0.28 ens3 IP: 192.168.0.31

#f #flow clas classifi fier $ openstack sfc flow classifier create --ethertype IPv4 --source-ip-prefix 192.168.0.97/32 --destination-ip-prefix 192.168.0.101/32 --logical- source-port sfc-client-2 --logical-destination-port sfc-server fcn cntopng-2

slide-23
SLIDE 23

Client-3 (iPerf-3)

SFC Implementation on Openstack with OVS (10)

Cr Create Fl Flow

  • w Cl

Clas assif sifie ier r for for Serv Service Ch Chain 3

vDPI-1 (ntopng) vDPI-2 (ntopng-2) Server (iPerf Server)

ens6 ens3 ens3 IP: 192.168.0.99 IP: 192.168.0.101 IP: 192.168.0.100

Client-1 (iPerf-1) Client-2 (iPerf-2)

ens3 IP: 192.168.0.97 ens3 IP: 192.168.0.28 ens3 IP: 192.168.0.31

#f #flow clas classifi fier $ openstack sfc flow classifier create --ethertype IPv4 --source-ip-prefix 192.168.0.97/32 --destination-ip-prefix 192.168.0.101/32 --logical- source-port sfc-client-3 --logical-destination-port sfc-server fcn cntopng-3

slide-24
SLIDE 24

Client-3 (iPerf-3)

SFC Implementation on Openstack with OVS (11)

Cr Create Por

  • rt Chain

Chain for for Servic ervice e Chain Chain 1

vDPI-1 (ntopng) vDPI-2 (ntopng-2) Server (iPerf Server)

ens6 ens3 ens3 IP: 192.168.0.99 IP: 192.168.0.101 IP: 192.168.0.100

Client-1 (iPerf-1) Client-2 (iPerf-2)

ens3 IP: 192.168.0.97 ens3 IP: 192.168.0.28 ens3 IP: 192.168.0.31

#po #port ch chai aining $ openstack sfc port chain create --port-pair-group ppgntopng --flow-classifier fcntopng pcn pcntopng

slide-25
SLIDE 25

Client-3 (iPerf-3)

SFC Implementation on Openstack with OVS (12)

Cr Create Por Port Cha Chain in for for Serv Servic ice e Cha Chain in 2

vDPI-1 (ntopng) vDPI-2 (ntopng-2) Server (iPerf Server)

ens6 ens3 ens3 IP: 192.168.0.99 IP: 192.168.0.101 IP: 192.168.0.100

Client-1 (iPerf-1) Client-2 (iPerf-2)

ens3 IP: 192.168.0.97 ens3 IP: 192.168.0.28 ens3 IP: 192.168.0.31

#po #port ch chai aining $ openstack sfc port chain create --port-pair-group ppgntopng-2 --flow-classifier fcntopng pc pcnto topng-2

slide-26
SLIDE 26

Client-3 (iPerf-3)

SFC Implementation on Openstack with OVS (13)

Cr Create Por Port Cha Chain in for for Servic Service e Cha Chain in 3

vDPI-1 (ntopng) vDPI-2 (ntopng-2) Server (iPerf Server)

ens6 ens3 ens3 IP: 192.168.0.99 IP: 192.168.0.101 IP: 192.168.0.100

Client-1 (iPerf-1) Client-2 (iPerf-2)

ens3 IP: 192.168.0.97 ens3 IP: 192.168.0.28 ens3 IP: 192.168.0.31

#po #port ch chai aining $ openstack sfc port chain create --port-pair-group ppgntopng --port-pair-group ppgntopng-2 --flow- classifier fcntopng pcn pcnto topng-3

slide-27
SLIDE 27

vDPI Setup

slide-28
SLIDE 28
  • Opendev respository ovs-dpdk

https://opendev.org/x/networking-ovs-dpdk

  • Installation :

https://opendev.org/x/networking-ovs- dpdk/src/branch/master/doc/source/installation.rst

  • Sample local.conf for deployment :

https://opendev.org/x/networking-ovs- dpdk/src/branch/master/doc/source/_downloads/

  • Getting started with Openstack and OVS-DPDK using Ubuntu :

https://opendev.org/x/networking-ovs- dpdk/src/branch/master/doc/source/getstarted/devstack/ubuntu .rst

SFC Implementation on Openstack with OVS-DPDK

slide-29
SLIDE 29
  • Opendev respository networking-spp :

https://opendev.org/x/networking-spp

  • Installation :

https://opendev.org/x/networking-spp/src/branch/master/doc/source/installation.rst

SFC Implementation on Openstack with SPP

slide-30
SLIDE 30
  • 3. Progress & Results
  • Research progress report
  • Working project timeline
slide-31
SLIDE 31

Progress and Result : SFC on OVS

1. Function Test:

a) Traffic Flow for Service Chain 1: Client-1 → vDPI-1 → Server b) Traffic Flow for Service Chain 2: Client-2 → vDPI-2 → Server c) Traffic Flow for Service Chain 3: Client-3 → vDPI-1 → vDPI-2 → Server

2. Througput Test:

a) Througput Test Without Service Chain : Client-1 → Server b) Througput Test for Service Chain 1: Client-1 → vDPI-1 → Server c) Througput Test for Service Chain 2: Client-2 → vDPI-2 → Server d) Througput Test for Service Chain 3: Client-3 → vDPI-1 → vDPI-2 → Server

Targ Target Te Test

slide-32
SLIDE 32

Research Progress Report

Servic Service e Cha Chain in

Client-3 (iPerf-3) vDPI-1 (ntopng) vDPI-2 (ntopng-2) Server (iPerf Server)

ens6 ens3 ens3 IP: 192.168.0.99 IP: 192.168.0.101 IP: 192.168.0.100

Client-1 (iPerf-1) Client-2 (iPerf-2)

ens3 IP: 192.168.0.97 ens3 IP: 192.168.0.28 ens3 IP: 192.168.0.31

Service Chain 1 Service Chain 3 Service Chain 2

slide-33
SLIDE 33

Client-3 (iPerf-3)

Research Progress Report (2)

Withou

  • ut Servic

Service e Cha Chain in

vDPI-1 (ntopng) vDPI-2 (ntopng-2) Server (iPerf Server)

ens6 ens3 ens3 IP: 192.168.0.99 IP: 192.168.0.101 IP: 192.168.0.100

Client-1 (iPerf-1) Client-2 (iPerf-2)

ens3 IP: 192.168.0.97 ens3 IP: 192.168.0.28 ens3 IP: 192.168.0.31

slide-34
SLIDE 34

Client-3 (iPerf-3)

Research Progress Report (3)

Servic Service e Cha Chain in 1

vDPI-1 (ntopng) vDPI-2 (ntopng-2) Server (iPerf Server)

ens6 ens3 ens3 IP: 192.168.0.99 IP: 192.168.0.101 IP: 192.168.0.100

Client-1 (iPerf-1) Client-2 (iPerf-2)

ens3 IP: 192.168.0.97 ens3 IP: 192.168.0.28 ens3 IP: 192.168.0.31

slide-35
SLIDE 35

Client-3 (iPerf-3)

Research Progress Report (4)

Servic Service e Cha Chain in 2

vDPI-1 (ntopng) vDPI-2 (ntopng-2) Server (iPerf Server)

ens6 ens3 ens3 IP: 192.168.0.99 IP: 192.168.0.101 IP: 192.168.0.100

Client-1 (iPerf-1) Client-2 (iPerf-2)

ens3 IP: 192.168.0.97 ens3 IP: 192.168.0.28 ens3 IP: 192.168.0.31

slide-36
SLIDE 36

Client-3 (iPerf-3)

Research Progress Report (5)

Servic Service e Cha Chain in 3

vDPI-1 (ntopng) vDPI-2 (ntopng-2) Server (iPerf Server)

ens6 ens3 ens3 IP: 192.168.0.99 IP: 192.168.0.101 IP: 192.168.0.100

Client-1 (iPerf-1) Client-2 (iPerf-2)

ens3 IP: 192.168.0.97 ens3 IP: 192.168.0.28 ens3 IP: 192.168.0.31

slide-37
SLIDE 37

Conclusion : SFC on OvS

1. Function Test: a) Traffic Flow for Service Chain 1: Client-1 → vDPI-1 → Server = OK b) Traffic Flow for Service Chain 2: Client-2 → vDPI-2 → Server = OK c) Traffic Flow for Service Chain 3: Client-3 → vDPI-1 → vDPI-2 → Server = OK 2. Througput Test: a) Througput Test Without Service Chain : Client-1 → Server = 16,4 Gbps b) Througput Test for Service Chain 1: Client-1 → vDPI-1 → Server = 2,75 Gbps c) Througput Test for Service Chain 2: Client-2 → vDPI-2 → Server = 2,20 Gbps d) Througput Test for Service Chain 3: Client-3 → vDPI-1 → vDPI-2 → Server = 2,11 Gbps Res Result ult

slide-38
SLIDE 38

Working Project Timeline

Working Project Establishment : Defining Use Case SFC Research Topology SFC Implementation

  • n Openstack

with OVS SFC Openstack OVS Test SFC Implementation on Openstack with OVS- DPDK SFC Openstack OVS-DPDK Test SFC Implementation

  • n Openstack

with SPP SFC Openstack SPP Test

Okto Oktober Sept September Agu Agustus Jun uni No November De Desember Juli Juli

source: ATII –WP4

slide-39
SLIDE 39

source: NTT

vSwitch & Network Acceleration Comparison

slide-40
SLIDE 40

Thank you!