Developing and deploying NFV solutions with OpenStack, Kubernetes and Docker
This document explains the deployment of virtualized network functions in a private cloud through ONAP, together with the architecture used, the machines employed and the software required. ONAP (Open Networking Automation Platform) is an open source project of the Linux Foundation, which provides a...
| Autor: | |
|---|---|
| Formato: | tesis de maestría |
| Fecha de publicación: | 2019 |
| País: | España |
| Recursos: | Universitat Politècnica de Catalunya (UPC) |
| Repositorio: | UPCommons. Portal del coneixement obert de la UPC |
| Idioma: | inglés |
| OAI Identifier: | oai:upcommons.upc.edu:2117/168800 |
| Acesso em linha: | https://hdl.handle.net/2117/168800 |
| Access Level: | acceso abierto |
| Palavra-chave: | Cloud computing NFV OpenStack ONAP Kubernetes Docker Computació en núvol Comunicacions òptiques Àrees temàtiques de la UPC::Enginyeria de la telecomunicació |
| Resumo: | This document explains the deployment of virtualized network functions in a private cloud through ONAP, together with the architecture used, the machines employed and the software required. ONAP (Open Networking Automation Platform) is an open source project of the Linux Foundation, which provides a platform for real - time orchestration and automation of physical and virtual network functions.ONAP allows designing, orchest rating and managing all the elements related to virtualized network functions. In order to deploy ONAP, we acquired and installed a cloud infrastructure from scratch following the latest market best practices, which included setting up the servers and ne twork devices, configuring their NICs and installing all the software required: OpenStack, ONAP, etc. Moreover, these software solutions also have to be properly configured and installed, something that will be clarified in this paper along with the conf iguration of the cloud network. ONAP, being a novel solution, is not fully developed. Meaning it has presented many challenges and setbacks we have had to overcome in order to deploy it successfully in our environment. The final goal of this project is to create an environment in a private cloud with working virtualized network functions and to serve as a guide for other people who desire to deploy ONAP, overcoming all the obstacles we had to face and providing solutions, or at least, alternatives to th e plethora of issues they might stumble across, just as we did. Everything discussed in this document can be replicated in environments of greater scope than the ones defined in the paper, to the point that what is explained can even be applied in produc tion scenarios by telephone operators. |
|---|