Demo Lab Guide Network Function Virtualization

Transcription

1 Demo Lab Guide Network Function Virtualization (HOL) Hands-On Lab Guide Deploying Virtualized IP Multimedia Subsystems in an OpenStack Environment Product Domain: Network Author: NFV Product Engineering Version: 1.01 Date: 24/03/ Dell Demo Center Dell Inc., 2016

2 Table of Contents 1 Product Overview Lab Preparation Considerations and Caveats Introduction Lab Topology and Essential Information Lab Addressing and Login Details NFV Virtual IP Mutlimedia Subsystem Pre-configured VNF Components Pre-configured vims deployment Pre-configured Network Visualization Tool Pre-configured Client and Stress Test tool Execution time of scripts Termination Scripts Lab User Interactions Cacti Network Monitoring Stress Testing Scaling OpenStack Dashboard Logs Summary Dell Demo Center Dell Inc., 2016

3 1 Product Overview This document compliments a virtual lab consisting of key design considerations to implement Network Functions Virtualization Infrastructure (NFVI), which is purpose built to accommodate service provider level requirements set forth by the provider s / partners technical staff and Dell Inc. technical architects and engineers. The NFVI considered here is for lab purposes only and does not reflect a production implementation supporting Virtual Network Functions (VNF). Also, please consider these software components may span multiple geographic locations and incorporate many forms of COTS compute, network, and storage. Note: Gain expertise and terminology understanding by viewing this group specification document: ETSI NFV v1.1.1: Network Functions Virtualization (NFV); Use Cases Network Functions Virtualization Infrastructure (NFVi) is an enhanced common infrastructure framework. It s comprised of next generation distributed compute architectures and services delivery mechanisms such as Software Defined Networks (SDN), public & private cloud infrastructure, northbound APIs, southbound APIs, transport, and services-oriented technologies. Distributed operating systems paired with commercially available computing elements (COTS) offers Cloud Communications Service Providers an alternative to acquiring traditional stand-alone infrastructure hardware and/or software serving a specific function (i.e. Load Balancer, Firewall, Intrusion Detection, Customer Premise Equipment, etc.). Consolidating proprietary network equipment hardware into high volume servers, commoditized switching, and storage provides significant benefit towards operations and accelerated services delivery. NFVi systems termed here encompasses foundational components such as; servers, storage, networking, infrastructure management (VIM), and sub-system components to deliver an end-to-end solutions framework. Openly delivered architectures are constructed by Dell in collaboration with its partners in the form of disaggregated building blocks predominantly delivered by provider s requirements. Each element is specifically selected and optimized to deliver carrier-grade 3 Dell Demo Center Dell Inc., 2016

4 resiliency, delivered in a highly available format, configured using PowerEdge C/M/R-Series Servers, Dell Networking S/Z-Series switching products, and logically connected using Openstack as the key distribution platform offered in a variety of sub-system architectures. Note: For any NFV related queries of opportunities please reach out to ASK_NFV_PLM@dell.com 1.1 Lab Preparation Considerations and Caveats It is in your best interests to ensure the demo environment you will be demonstrating is clean & tidy before you begin. For this reason we would recommend, where possible, you log in to your demo at least 15 minutes prior to delivery and check the following; 1. Familiarize yourself with the environment during this time and check any specific features you are expecting to demo. 2. Most importantly, be crystal clear with yourself on what it is you plan to show. A full demo of every feature described below (with questions) can take several hours. If you only have a short time slot be sure to focus on the key points that address the customer s pain points and will drive value home to them. 3. Ensure that you have scheduled the demo for sufficient time so as not to have the demo end before you are finished with the customer. Any other guidance on how the user should prepare for the lab can be added here. If there are limitation or something the user should be aware of call out also. 4 Dell Demo Center Dell Inc., 2016

5 2 Introduction In this lab, you will gain technical exposure to the following: Using open source Fuel to simplify OpenStack deployment OpenStack consisting of three controllers and two compute nodes Understanding the essential concepts of virtualized infrastructure management (VIM) Demonstrating key NFV concepts using OpenStack as a platform to build and support computing, networking, and storage infrastructure Applying your knowledge and executing an automated script, which to deploys a simple Reference Virtual Network Function (VNF), Working knowledge of an open source IP Multimedia Subsystem Validating end-to-end functionality with client communication software Note: In this lab, you are expected to have a basic understanding of Dell systems infrastructure. Because this NFV system is virtualized, the physical aspects of networking and servers is out of scope. Please refer to other demos.dell.com lab demonstrations, which may focus on hardware/product specifics. 5 Dell Demo Center Dell Inc., 2016

6 2.1 Lab Topology and Essential Information 6 Dell Demo Center Dell Inc., 2016

7 2.1.1 Lab Addressing and Login Details Element IP Method UserID Password Comments Fuel /24 ssh admin admin Deploys Openstack Cloud Horizon /24 http, ssh admin admin Openstack UI Jump /24 screenconnect demouser password Jump Server controller-1 / node ssh root r00tme controller node controller-2 / node ssh root r00tme controller node controller-3 / node ssh root r00tme controller node compute-1 / node ssh root r00tme compute node compute-2 / node ssh root r00tme compute node ALL vims Machines Varies QEMU Console root root123 all the vims instances 7 Dell Demo Center Dell Inc., 2016

8 3 NFV Virtual IP Mutlimedia Subsystem The lab delivers key business and technical benefits of Dell NFV Platform. To demonstrate the core capabilities of Dell NFV Platform we will now deploy the vims on top of Dell NFV Platform. Dell NFV Platform supports following feature related to vims: - Automated Deployment - High Availability - Automated user provisioning - Service Monitoring - Automated Scaling - Load Balancing - SIPp stress testing - User registration and call setup using sip clients i.e. Zoiper, Xlite. - Sip Call - Text Messaging - Conference Call - Call Hold - Call Forwarding - Call Recording - Video Calling - Stress testing using SIPp as a tester tool. - Cacti for the monitoring purpose of load on different nodes. - Web RTC - Scaling up automatically when loads reaches a maximum threshold - Scaling down - Load balancing 8 Dell Demo Center Dell Inc., 2016

9 3.1 Pre-configured VNF Components The lab focuses on key technical NFV concepts using an open-source vims system, which is considered a reference VNF. To demonstrate the core capabilities of vims, we will pre-deploy the vims on an Openstack platform. Here is a list of the core topics covered during the lab: - vims deployment in HA - User provisioning - Cacti monitoring - User registration and call setup using sip clients i.e. zoiper, Xlite. 3.2 Pre-configured vims deployment The virtual IP media system is already configured, however, here are the pre-executed scripts that were constructed to build the environment. By running these scripts prior to lab deployment, you gain roughly minutes of time to complete the entire buildout of the vims environment. 1. Extract the vims.tar.gz using the command: cd / tar -zxvf vims-demo.tar.gz 2. Change the current directory to the vims directory by running the command cd /vims 3. Start deploying the vims by entering the following command: 9 Dell Demo Center Dell Inc., 2016

10 3.3 Pre-configured Network Visualization Tool To get SNMP visualization an open source software cacti is used. To install Cacti the following steps are to be followed 1. Enter the vims directory by entering the command: cd /vims 2. Enter the command to spawn the cacti node python Cacti.py 3. Look up the Cacti node IP from Openstack Horizon or Use the IP provided in the end of script. 4. Open the web browser and type ip>/cacti 5. Login using the credentials, Username = admin, Password = admin 6. Go to devices and enter the IP of sprout node in the field Hostname 7. Graphs can be viewed on the top "graphs" tab. 10 Dell Demo Center Dell Inc., 2016

11 3.4 Pre-configured Client and Stress Test tool Note: Part of this HOL also included the creation of additional scripts to setup open-source IMS clients and stress test tools. Portions of these elements will be visited in the lab user interaction section later, but here are the pre-executed steps to automatically bring up the client side tools: 1. To create the users, run the following script: python user_create.py 2. Enter the no of users you want to create: To register user in vims install soft sip clients i.e. zoiper, Xlite etc. 4. Create an account in the zoiper/xlite 5. Use the credentials given in the sip users.txt file on desktop to register users. 6. Open the Zoiper client go to settings and click on create account: 11 Dell Demo Center Dell Inc., 2016

12 7. Choose the account type SIP from the options 8. Copy the credentials from the file sip users.txt. E.g. username= password = 7kkzTyGW 9. In the outbound proxy option use the <bono-0 floating ip address>: Click on next and check the box of skip auto detection 11. Go to settings and click on preferences as shown in below figure. 12. Enter the authentication username from the file sip users.txt. 13. Click on register to register the user 14. Same are the steps for any soft client you use. 3.5 Execution time of scripts Depending upon the computational power, all the four scripts have variant execution time. Approximate time of completion is stated below: - Initial deploy scripts takes 45 minutes - User Create script takes 120 minutes (for 100,000 users) - Scale-up takes 30 minutes - Scale-down takes 10 minutes - vims termination script takes 10 minutes - Stress test script takes 15 minutes - Cacti script takes 10 minutes 12 Dell Demo Center Dell Inc., 2016

13 3.6 Termination Scripts 1. To terminate, go to vims directory and enter the command python Remove.py 2. To stop the stress test, go to vims directory and enter the command python Remove_test.py Note: Provide the no of test nodes you want to remove = 2 3. To terminate Cacti enter the command python Remove_cacti.py 13 Dell Demo Center Dell Inc., 2016

14 4 Lab User Interactions This section includes instructions that the lab user will type/execute. This includes the stress testing and the scale out on the existing environment. Viewing the various dashboards like Cacti and Horizon. 4.1 Cacti Network Monitoring 1. Open the web browser and type 2. Login using the credentials Username = admin Password = admin 3. Graphs can be viewed on the top "graphs" tab. 4.2 Stress Testing To start the stress test, enter the command python tester.py Note: Enter the no. of nodes to spawn =3 14 Dell Demo Center Dell Inc., 2016

15 4.3 Scaling The vims will scale up and down automatically on reaching the threshold. Threshold is configured in terms of CPU usage, Memory Usage and Number of Call Another stack named scale will be created in scale up process. To view the Scale up/down progress ssh into control node and enter the following commands cd /vims vi scale_progress 4.4 OpenStack Dashboard To view OpenStack horizon/dashboard use the following IP in the address bar - Login using the credentials Username = admin Password = admin 4.5 Logs All the scripts generate logs during execution. To see the logs generated during the execution of scripts, go into the /vims/logs/ directory. It contains a total of 2 files for each script; one file is for activity log i.e the total flow of script in which it deploys vims components and the second is error log in case if any error occurs during the execution of script. 15 Dell Demo Center Dell Inc., 2016

16 5 Summary In this document we have successfully deployed and validated the working and deployment of Clearwater vims using a representative sample of NFV Infrastructure, all of which are Dell NFV capable solutions. After the complete deployment we were able validate the sip call using Clearwater vims and its monitoring using Cacti. We have also used SIPp as a stress test to bench mark and validate the automatic scale up and down the vims Note:- Feedback on the demonstration and the guide would be greatly appreciated. Any feature or enhancements you would like to see to either please the Demo Center team and we will provide the feedback to the NFV Product team. 16 Dell Demo Center Dell Inc., 2016

17 17 Dell Demo Center Dell Inc., 2016