Advanced VNF based on OpenWRT in Tacker

Abstract: By leveraging Network Function Virtualization (NFV), the communications service providers (CSPs) can provide a virtual customer premises equipment (vCPE) solution where multiple network services and functions are virtualized and run on the common hardware platform with lower costs than of physical hardware appliances. However, in the OpenStack Tacker-based vCPE system, the network services based on the OpenWrt image only enable the Firewall and Router. In this paper, we further develop the advanced OpenWrt-based network services such as Dynamic Host Configuration Protocol (DHCP), Domain Name System (DNS), Quality of service (QoS).


Full paper: [Link]


Trinh Nguyen, Tri-Hai Nguyen, Myungsik Yoo, “Developing the VNFs for the vCPE system using OpenWrt”, The 28th Joint Conference on Communications and Information (JCCI 2018), 2-4 May 2018, Hidden Bay Hotel, Jeonnam, ROK.

VyOS-based VNF

Abstract: Network Function Virtualization (NFV) is a new concept that is shifting network functions from dedicated hardware appliances to software running on commodity hardware. By levering NFV, A communications service provider or CSP can provide a virtual customer Premises Equipment (vCPE) solution which is a method to deliver network services to enterprises by using software rather than dedicated hardware appliances. However, the minimum types of VNF are currently supported in the existing open-source NFV vCPE projects. Therefore, we propose a customized VyOS image that can be deployed as the VNF in NFV vCPE system with multi-function supported. The experiment is conducted in a Tacker-based vCPE system to show the feasibility of the provided VyOS image.


Reference: Tri-Hai Nguyen, Myungsik Yoo, “A Comprehensive NFV vCPE System with VyOS-based VNF”,  2018 KICS Summer Joint Conference, 20-22 June 2018, Jeju-do, ROK. [Link]

Developing the Python Libs in DevStack

In Devstack, the Python packages/libs, e.g., python-tackerclient [1], tacker-horizon [2], are not easy to develop because normally they will be installed under python’s site-packages. Therefore, to easy for developing, we can install from the local environment and work on it:

1. Clone the repo of the project:

cd /opt/stack/
git clone git:// -b <branch>

2. Install:

cd python-tackerclient
sudo pip install -U -e .

3. Make changes.

Note: You need restart Apache server to work with tacker-horizon

sudo systemctl restart apache2

Customize the OpenWRT 15.05.1 for OpenStack Tacker

The OpenWRT is modified based on KVM OpenWRT 15.05.1 to be suitable for OpenStack Tacker.
The procedure is following as below:

cd ~
wget \
-O openwrt-x86-kvm_guest-combined-ext4.img.gz
gunzip openwrt-x86-kvm_guest-combined-ext4.img.gz

mkdir -p imgroot

sudo kpartx -av openwrt-x86-kvm_guest-combined-ext4.img

# Replace the loopXp2 with the result of above command, e.g., loop0p2
sudo mount -o loop /dev/mapper/loopXp2 imgroot
sudo chroot imgroot /bin/ash

# Set password of this image to blank, type follow command and then enter two times

# Set DHCP for the network of OpenWRT so that the VNF can be ping
uci set network.lan.proto=dhcp; uci commit

sudo umount imgroot
sudo kpartx -dv openwrt-x86-kvm_guest-combined-ext4.img

A customized OpenWRT 15.05.1 that can be deployed as VNFs including Firewall, Router, NAT, DHCP, DNS, or QoS VNFs in OpenStack Tacker.


Getting started with contributing to OpenStack; Do’s and Don’ts

OpenStack Sydney: The talk describes the structure of most open source communities, governance, and how members of the community communicate. The talk describes the first 5 things that every newcomer to OpenStack should follow. Reviewing code is an important aspect of community participation and we describe how to do good code reviews.

Read More

NFV Management and Orchestration with Tacker

This post shows a brief look at the NFV MANO framework developed by ETSI and creation of a simple vIDS network service using Tacker.

NFV MANO for Telco

Traditionally those network functions were a collection of vertically-integrated bare metal appliances that took a long time to commission and had to be over-provisioned to cope with the peak-hour demand. Visualizing them would have made it possible to achieve quicker time-to-market, elasticity to cope with a changing network demand and hardware/software disaggregation.

Read More