Now, a virtual instance of the controller is created. In the example, the step is only for the first one, the other two is created in the same way. Here, you should only be careful about choosing the appropriate IP address, which must fall within the sub-range created above.
Finally, these assigned controllers assign floating IP addresses that provide access to these instances from an external network. Again for the purpose of this work, it is sufficient to give only one example.
As can be seen from the previous examples, the names of some Salt modules for OpenStack services have an ‘-ng’ extension. This means that the original modules for these services have been expanded with new functionality, and these extensions have been added to this extension.
The base modules in the Salt did not include some disk image management, firewall rules, and instance creation. A specific description of the modifications in the modules is beyond the scope of this work, however their source codes are contained in the electronic attachment.
Running and Results
Finally, make sure that the ‘controller.sls’ file is in the correct directory for the Salt formula, the pillar file is assigned to the minion that will include this role, and all the expanded modules are in the directory for the custom modules. After that, it is enough for Saltmaster to run a command to synchronize all the modules and the role, an order for syncing the pillar and the end of the command to apply the avinetworks status to a particular minion.
Salt then writes the result of all the steps that have been taken. In the case of some unsuccessful ones, it is necessary to reveal the cause of the cause and make changes leading to correction. If is an error-free statement, it means that the VNF has managed to deploy properly.
All created components can be found in the Horizon graphical interface or in the help list command line. A record of successful deployment can be found in Appendix H. Now you can open the web interface of one of the controllers to make sure it is running it happened without any problems. If the form for setting the output is displayed as in figure no. 4.3, this service is functional and ready to use. Then you can proceed according to the instructions for adding and setting up services to load-balancing.
The result of this example is the functional formula and pillar for the orchestra Salt, helped which can be automated by installing a single instance of a three-instance Avi Vantage software load balancer, including all necessary dependencies in the OpenStack environment, by calling a single command.
This example is also to demonstrate a more general procedure for creating VNF for orchestras. Independently of the chosen platform, VNF or orchestra, it is always necessary get familiar with the manual installation of the selected VNF and then try to transform these manual actions to the selected rule, the templates for Tacker, blueprints for Cloudify, salt formula, or any other regulations for other orchestras.
The aim of the thesis was to introduce the possibilities of virtualization of network devices and services, to explore tools for its testing and development, to evaluate their advantages and disadvantages, to present the NFV framework, to describe its architecture, to analyze specific software that can be used, including comparison and practical to show how automated virtual network services are deployed.
The beginning of the work was devoted to the possibilities of virtualization, while supporting technologies such as namespaces, SDNs or Open vSwitch were also described during the work.
As a tool for testing and development, the Mininet, a virtual network built on the Linux hypervisor with Open vSwitch, and finally a professional Junosphere network virtualization service was described.
The NFV framework chapter describes its advantages over the physical network solution, and its components were disassembled. Then, some software vendors were chosen to serve for the implementation of these components, and these were characterized, described, and compared.
A practical example contained a simple design of a specific implementation of a private cloud solution using a NFV. OpenStack, OpenContrail and SaltStack were selected for him. There was also a brief comparison of the virtual network solution Neutron and OpenContrail.
The main theme of the practical example was the creation of a prescription for the Salt orchestrater to help deploy a virtual network service, namely the Avi Vantage load balancer.
This policy has been successfully tested on a real-life environment running on the OpenContact cloud platform with OpenContrail’s network solution. The results are included in the annex to this paper.
In conclusion, it can be said that the work has been accomplished. The theoretical part contains a rich description and comparison of the virtualization technologies of the computer network that are currently being used and still being developed. The final practical example is also functional as well as two minor practical examples of using the Minnet and creating a virtual network on a hypervisor in Linux.