I am busy changing the world

If you're working in the telco industry, you may realize an exciting race what is happening. It's the NFV Orchestration and Management (MANO) system. The origin of that is ETSI's work on the NFV MANO specification . After ETSI released the spec, many organizations have been trying to implement its own NFV MANO system including OpenStack Tacker , OPNFV , ONAP , and ETSI itself also adopted an open source project called Open Source MANO (OSM). I will explore a tool called VNF Descriptor Generator of OSM in this blog post. What is VNF Descriptor Generator? It's a web interface that helps you to generate VNF and NS Descriptor packages ready for launch (onboarding). By filling out all the information of your VNFs in the web form, the tool will provide you a VNFD package and an NSD package for you to download. This helps you to avoid typos and misconfiguration when you have to prepare the package manually. 1. In your OSM web interface, go to launchpad, VNF Descriptor g...

So I just updated the OpenWRT VNFM management driver of OpenStack Tacker to support more services like DHCP, DNS, and QoS ( the code is under review now ). But, if you are so eager to try, here is how: 1. Download the custom image of OpenWRT from here  (because the default OpenWRT image doesn't have qos-scripts installed). 2. Upload that image to your OpenStack instance: openstack image create OpenWRT --disk-format qcow2 \                                --container-format bare \                                --file /path_to_image/openwrt.img \                                --public 3. Use this VNFD template to generate VNF: Note : Use this at your own risk. References: [0] https://wiki.openwrt.org/doc/howto/obtain.firmwa...

The OpenWRT management driver of Tacker VNFM currently only supports the firewall and network service. That raises a need to update that driver so that we can deploy more network services as VNF using OpenWRT. So to achieve the goal of this blog post, I have to do as follow: 1. Update the OpenWRT VNFM management driver . I just submitted a blueprint on launchpad to work on it. Hopefully, it will be approved soon: Blueprint:  https://blueprints.launchpad.net/tacker/+spec/advanced-openwrt-driver Code review: https://review.openstack.org/#/c/540310/2 Here is a quick change: modify this file  /opt/stack/tacker/tacker/vnfm/mgmt_drivers/openwrt/openwrt.py at line 94                 KNOWN_SERVICES = ('firewall', 'network')  to                 KNOWN_SERVICES = ('firewall', 'network', 'dnsmasq')  2. Use this VNFD template to deploy the DHCP and DNS services on Tacker Notice: I d...

The opensource project for router OpenWRT is quite powerful which can be used to deploy as VNF in OpenStack Tacker. Here is a sample of VNF template (VNFD) which will be used to deploy NAT service in Tacker using OpenWRT. Basically, the VNF will apply 2 NAT rules: 1. Redirect all requests to port 80 of any clients on the 'wan' interface of the OpenWRT to port 80 of the client with IP address 192.168.16.235 which is linked to the 'lan' interface. 2. Redirect all requests to port 22001 of any client on the wan interface to port 22 of  any clients on the 'lan' interface of the VNF. Note: Please read the official OpenStack documentation on how to deploy the VNF. Referecences: [0] https://docs.openstack.org/tacker/latest/install/deploy_openwrt.html [1] https://wiki.openwrt.org/doc/uci/firewall