臺灣博碩士論文加值系統

隨著網路越來越發達，使用者對服務的需求遽增，傳統的網路架構在雲端資料中心成為了瓶頸，網路服務提供商(Internet service provider, ISP)為了解決問題，提出了網路功能虛擬化(Network Function Virtualization, NFV)技術，其概念是將以往的網路設備虛擬化成軟體(Virtual Network Function, VNF)，且能運行在通用伺服器上，讓部署網路服務時，可以更快速、更有彈性，在維運方面也更加簡單，有效降低成本。然而，相關理論與研究持續地發表，卻鮮有公開的NFV系統被提出，使得相關議題難以被驗證與測試，若要深入研究網路功能虛擬化技術，一個完整的NFV系統是必要的。

本論文基於OpenStack雲端作業系統與其子計畫Tacker，實作出一NFV系統。此系統提供網頁介面，管理者與使用者能透過網頁快速部署、管理與設定VNF，減少繁複操作，並提供Auto Scaling的機制，系統會根據VNF狀態而自動增減VNF，維持服務品質。此外，我們也實作了三種VNF，包含防火牆、負載平衡與網頁伺服器等，除了可以用來驗證NFV的系統完整性，也讓系統能提供基本的服務，並透過SDN/OpenFlow實現網路功能串聯(Service Function Chaining, SFC)，可以根據用戶的需求串聯各種VNF，讓系統能提供更多樣化的服務。

除了實作出NFV系統之外，我們也開發出能改進此系統效能的演算法。Placement演算法計算出一連串較佳的VNF擺放位置，讓使用者在存取VNF服務時，能降低延遲的時間；Scaling演算法提供更有效率的Auto Scaling機制，根據不同的使用情況來增減VNF的數量。最後，我們建立虛擬的環境對演算法做測試，其實驗結果顯示出Placement演算法根據情況的不同下，能降低約13-45\%存取VNF的延遲時間，而在Scaling演算法實驗的部分，則顯示出此方法能夠有效率地根據VNF的情況對VNF做增減、控制服務的延遲時間，以及彈性使用系統的資源。

As the network technology advances, the related service demands has increased dramatically. The traditional network architecture becomes a bottleneck in data centers. Many Internet Service Providers (ISP) provide network function virtualization (NFV) to resolve this problem. It exploits the virtual network function (VNF), virtualized from physical network devices, to reach the efficacy and flexibility. In addition, while deploying network services, it can be run on universal servers, which are easy to maintain and have lower cost. Although the related idea has been studied for some time, there are very few public NFV systems available to justify the feasibility of NFV. In order to gain a deeper understanding of NFV, it is necessary to construct a complete NFV system.

In this thesis, based on the OpenStack, a cloud operating system, and Tacker, a subproject of OpenStack, we implement an NFV system. Our system provides a web interface simplifying redundant operations such that managers and users can fast deploy, organize and set up VNF. It also provides the auto-scaling mechanism to keep service quality according to VNF status. Besides, we built three types of VNF including firewall, load balancer, and web server for chaining. It can help validate the NFV system, provide the basic services, and then realize service function chaining (SFC) through SDN/OpenFlow. Based on users' demand, the system can provide different services via chaining varieties of VNFs.

In addition to implementing an NFV system, we also developed two algorithms to improve the performance of the system. The placement algorithm determines a better location of a chain, which consists of several VNFs, to lower latency during accessing the chain. The scaling algorithm provides an efficient auto-scaling mechanism to deploy and remove VNFs according to the condition of resources avaliable. We also construct a virtual environment to test our algorithms. The results show that the placement algorithm reduces about 13-45\% latency while accessing VNFs in different scenarios. Our scaling algorithm can efficiently deploy and remove VNFs according to the condition of VNFs, effectively control the latency of VNFs and flexibly utilize the system resources.

1 Introduction 1
2 Background 5
2.1 Network Function Virtualization . . . . . . . . . . . . . . . . . . . . . . . 5
2.2 Software Defi ned Network . . . . . . . . . . . . . . . . . . . . . . . . . .. 7
2.2.1 OpenFlow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.2.2 OpenDaylight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.3 Service Function Chaining . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.4 OpenStack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3 System Architecture 17
3.1 OpenStack Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.2 Tacker Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.2.1 OpenStack Nova . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.2.2 Virtual Network Function . . . . . . . . . . . . . . . . . . . . . . . 21
3.2.3 Virtual Network Function Description . . . . . . . . . . . . . . . . 22
3.2.4 Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
3.2.5 Service Function Chaining . . . . . . . . . . . . . . . . . . . . . . . 25
3.2.6 Virtual Network Function Management . . . . . . . . . . . . . . . . 27
3.2.7 OpenStack Horizon . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.3 System Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.3.1 Update Virtual Network Function Description . . . . . . . . . . . . 33
3.3.2 Deploy Virtual Network Function . . . . . . . . . . . . . . . . . . . 34
3.3.3 Update Virutal Network Function Confi guration . . . . . . . . . .. 35
3.3.4 Auto Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4 Algorithms 38
4.1 Placement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4.2 Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
5 Experiment & Evaluation 43
5.1 Placement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
5.2 Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
6 Conclusion 50

[1] “ETSI.” http://www.etsi.org.
[2] J. Matías, J. Garay, N. Toledo, J. Unzilla, and E. Jacob, “Toward an SDN-enabled
NFV architecture.,” IEEE Communications Magazine, vol. 53, no. 4, pp. 187–193,
2015.
[3] P. Demestichas, A. Georgakopoulos, D. Karvounas, K. Tsagkaris, V. Stavroulaki,
J. Lu, C. Xiong, and J. Yao, “5G on the Horizon: Key Challenges for the Radio-
Access Network,” Vehicular Technology Magazine, IEEE, vol. 8, no. 3, pp. 47–53,
2013.
[4] J. Batalle, J. F. Riera, E. Escalona, and J. A. Garcia-Espin, “On the Implementation
of NFV over an OpenFlow Infrastructure: Routing Function Virtualization.,” in
SDN4FNS, pp. 1–6, IEEE, 2013.
[5] N. McKeown, T. Anderson, H. Balakrishnan, G. Parulkar, L. Peterson, J. Rexford,
S. Shenker, and J. Turner, “OpenFlow: Enabling Innovation in Campus Networks,”
SIGCOMM Comput. Commun. Rev., vol. 38, pp. 69–74, Mar. 2008.
[6] “Open Networking Foundation.” https://www.opennetworking.org.
[7] S. Jain, A. Kumar, S. Mandal, J. Ong, L. Poutievski, A. Singh, S. Venkata, J. Wan-
derer, J. Zhou, M. Zhu, J. Zolla, U. Hölzle, S. Stuart, and A. Vahdat, “B4: expe-
rience with a globally-deployed software defi ned wan,” in Proceedings of the ACM
SIGCOMM 2013 conference on SIGCOMM, SIGCOMM ’13, (New York, NY, USA),
pp. 3–14, ACM, 2013.
[8] “Internet Engineering Task Force.” https://www.ietf.org.
[9] S. Ma, B. Wang, X. Zhang, and X. Gao, “PDNI: A Distributed Framework for NFV
Infrastructure,” in Parallel Architectures, Algorithms and Programming (PAAP),
2015 Seventh International Symposium on, pp. 34–40, IEEE, 2015.
[10] R. V. Rosa, M. A. Silva Santos, and C. Esteve Rothenberg, “Md2-nfv: The case for
multi-domain distributed network functions virtualization,” in Networked Systems
(NetSys), 2015 International Conference and Workshops on, pp. 1–5, IEEE, 2015.
[11] “OpenStack.” https://wiki.openstack.org/wiki/Main_Page.
[12] “OpenStack Tacker.” https://wiki.openstack.org/wiki/Tacker.
[13] “ONOS: Open Network Operating System.” http://onosproject.org/.
[14] “Ryu.” https://osrg.github.io/ryu/.
[15] “Floodlight.” http://www.projectfloodlight.org/floodlight/.
[16] “OpenDaylight.” https://www.opendaylight.org/.
[17] “Kernel-based Virtual Machine.” http://www.linux-kvm.org/page/Main_Page.
[18] “OpenvSwitch.” http://openvswitch.org/.
[19] “Python Django.” https://www.djangoproject.com/.
[20] T. Berger, “Analysis of Current VPN Technologies.,” in ARES, pp. 108–115, IEEE
Computer Society, 2006.
[21] “VMware Workstation.” https://www.vmware.com/.
[22] “Apache ApacheBench.” https://httpd.apache.org/docs/2.4/programs/ab.html.