Lab Overview - HOL-1786-USE-1

Table of ContentsLab Overview - HOL-1786-USE-1 - vCloud Network Functions Virtualization.....................2

Lab Guidance .......................................................................................................... 3Introduction............................................................................................................. 7

Module 1 - Getting Started (15 min) ............................................................................... 12How Fast “Fast” Really Is - From VNF to VoLTE Service Deployment? ....................13

Module 2 - TOSCA based Blueprinting & Modeling (30 minutes).....................................15Introduction........................................................................................................... 16Solution Blueprinting............................................................................................. 18

Module 3 - VoLTE Solution Deployment (30 minutes)...................................................... 28Introduction........................................................................................................... 29Solution Deployment............................................................................................. 31

Module 4 - Lifecycle Management of a VoLTE core (30 minutes) ....................................41Introduction........................................................................................................... 42Auto-Scaling ......................................................................................................... 43Retiring Applications ............................................................................................. 51

Conclusion ...................................................................................................................... 56Lab Conclusion...................................................................................................... 57

HOL-1786-USE-1

Page 1HOL-1786-USE-1

Lab Overview -HOL-1786-USE-1 - vCloud

Network FunctionsVirtualization

HOL-1786-USE-1


Lab GuidanceNote: It will take more than 90 minutes to complete this lab. You shouldexpect to only finish 2-3 of the modules during your time. The modules areindependent of each other so you can start at the beginning of any moduleand proceed from there. You can use the Table of Contents to access anymodule of your choosing.

The Table of Contents can be accessed in the upper right-hand corner of theLab Manual.

The primary objective of this lab is to introduce Network Function Virtualization (NFV)and the VMware NFV common platform solution. This includes rapid applicationdeployment, horizontal scaling of virtual network functions (VNFs), multi-vendor VNFsupport, & multi-domain support. In addition, VNF blueprinting, modeling, deployment,and service lifecycle management are critical components. This HOL will enable usersto learn 3 primary aspects of NFV as follows:

• Understand VMware’s NFV solution.• Define application blueprints by modeling VNFs.• Generate model-driven deployments of Mobility VNFs using application blueprints

and vCloud Application Director.

Lab Module List:

• Module 1 - Getting Started with Network Function Virtualization(15minutes) (Basic) In this module we will be reviewing the basics of NetworkFunction Virtualization (NFV) as well as review some recent advancement VMwarehas made in the space with some of the ecosystem partners.

• Module 2 - TOSCA Based VNF Blueprinting & Modeling(30 minutes)(Intermediate) Throughout this module we will explore the components of VNFblueprints.

• Module 3 - VoLTE Solution Deployment(30 minutes) (Intermediate) In thismodule we will deploy and configure a VNF blueprint and watch the service comeonline.

• Module 4 - Lifecycle Management of a VoLTE core(30 minutes)(Intermediate) Throughout this module we will review some of the steps requiredto manage your VoLTE service. This will include configuration for Auto-Healing,Auto-Scaling, and retirement of the application.

Lab Captains:

• Module 1 - John Avery & Kevin Tebear• Module 2 - John Avery & Kevin Tebear

HOL-1786-USE-1


• Module 3 - John Avery & Kevin Tebear• Module 4 - John Avery & Kevin Tebear

This lab manual can be downloaded from the Hands-on Labs Document site found here:

http://docs.hol.vmware.com

This lab may be available in other languages. To set your language preference and havea localized manual deployed with your lab, you may utilize this document to help guideyou through the process:

http://docs.hol.vmware.com/announcements/nee-default-language.pdf

Location of the Main Console

1. The area in the RED box contains the Main Console. The Lab Manual is on the tabto the Right of the Main Console.

2. A particular lab may have additional consoles found on separate tabs in the upperleft. You will be directed to open another specific console if needed.

3. Your lab starts with 90 minutes on the timer. The lab can not be saved. All yourwork must be done during the lab session. But you can click the EXTEND toincrease your time. If you are at a VMware event, you can extend your lab timetwice, for up to 30 minutes. Each click gives you an additional 15 minutes.Outside of VMware events, you can extend your lab time up to 9 hours and 30

minutes. Each click gives you an additional hour.

HOL-1786-USE-1


http://docs.hol.vmware.com

http://docs.hol.vmware.com/announcements/nee-default-language.pdf

Alternate Methods of Keyboard Data Entry

During this module, you will input text into the Main Console. Besides directly typing itin, there are two very helpful methods of entering data which make it easier to entercomplex data.

Click and Drag Lab Manual Content Into Console ActiveWindow

You can also click and drag text and Command Line Interface (CLI) commands directlyfrom the Lab Manual into the active window in the Main Console.

Accessing the Online International Keyboard

You can also use the Online International Keyboard found in the Main Console.

1. Click on the Keyboard Icon found on the Windows Quick Launch Task Bar.

Activation Prompt or Watermark

When you first start your lab, you may notice a watermark on the desktop indicatingthat Windows is not activated.

<div class="player-unavailable"><h1 class="message">An error occurred.</h1><div class="submessage"><ahref="http://www.youtube.com/watch?v=xS07n6GzGuo" target="_blank">Try watching this video on www.youtube.com</a>, or enableJavaScript if it is disabled in your browser.</div></div>

HOL-1786-USE-1


One of the major benefits of virtualization is that virtual machines can be moved andrun on any platform. The Hands-on Labs utilizes this benefit and we are able to run thelabs out of multiple datacenters. However, these datacenters may not have identicalprocessors, which triggers a Microsoft activation check through the Internet.

Rest assured, VMware and the Hands-on Labs are in full compliance with Microsoftlicensing requirements. The lab that you are using is a self-contained pod and does nothave full access to the Internet, which is required for Windows to verify the activation.Without full access to the Internet, this automated process fails and you see this

watermark.

This cosmetic issue has no effect on your lab.

Look at the lower right portion of the screen

Please check to see that your lab is finished all the startup routines and is ready for youto start. If you see anything other than "Ready", please wait a few minutes. If after 5minutes you lab has not changed to "Ready", please ask for assistance.

HOL-1786-USE-1


IntroductionIntroduction to NFV and Orchestration using the VMware vCloud NFV Platform

What is Network Functions Virtualization (NFV)?

With about 75 percent of x86 server workloads in enterprise IT globally beingvirtualized, adoption of virtualization is widespread. Success in Enterprise ITvirtualization has encouraged communication service providers (CSPs), who providefixed and mobile telephony to adopt these technologies to virtualize their networkservice functions.

Network Functions Virtualization (NFV) is a network architecture concept that specifieshow virtualization technologies can be used to virtualize network service functions. TheEuropean Telecommunications Standards Institute (ETSI) published specifications onNFV infrastructure to define a baseline for NFV adoption by CSPs. VMware hasdeveloped an ETSI conforming solution that CSPs can use for Carrier Grade NFV servicedelivery. Communication Service Providers can now leverage NFV to reduce CapEx andOpEx costs, while improving service agility, differentiation and opportunities formonetization.

The figure shows the ETSI NFV reference architecture.

What is the vCloud NFV platform?

VMware’s vCloud NFV is a proven Carrier Grade NFV service delivery platform. vCloudNFV’s “Common Platform” approach for Network Functions Virtualization Infrastructure

HOL-1786-USE-1


(NFVI) lifecycle management, provides a feature rich modular foundation, an industryleading operations platform and a diverse partner ecosystem, that allows serviceproviders to build their own custom NFV services delivery stack.

The vCloud NFV Common Platform approach

Nearly all virtualized network function platforms deployed today are built as virtualnetwork function (VNF) silos. In a silo architecture, the virtualized network function istightly coupled with dedicated compute and storage resources and proprietarymanagement platforms. Resources in a silo architecture model are only used for a singlenetwork function or a number of network functions built by a single vendor. Siloarchitecture models provide limited, if any, multivendor VNF support and make itdifficult to remove existing VNFs, add new vendor VNFs, or build complex serviceconstructs that require the coordinate support of multiple VNFs.

The vCloud NFV Common Platform approach gives CSPs the ability to place all VNFs on acommon platform that leverages a single shared pool of compute, storage and networkresources, supports deployment of multi-vendor VNFs and makes it easy to remove andreplace existing VNFs, or add new VNFs based on CSP service delivery requirements.The common platform model offers a more attractive economic model by leveragingshared resource pools and also decreases single vendor leverage by enabling easy VNFportability.

VMware vCloud NFV Infrastructure (NFVI) architecture

The vCloud NFV platform is a modular NFV Infrastructure (NFVI) platform. VMwaredelivers compute virtualization with vSphere, network virtualization with NSX, andsoftware defined storage with VMware Virtual SAN (VSAN). Secure multi-tenancy isenabled by a choice of Virtual Infrastructure Managers: VMware vCloud Director orVMware Integrated OpenStack. Support for Fault, Configuration, Accounting,

HOL-1786-USE-1


Performance and Security (FCAPS) is provided by VMware vRealize Operations™ andVMware vRealize Log Insight.

HOL-1786-USE-1


VMware vCloud NFV modular architecture

One of the key design concepts of vCloud NFV is helping CSPs avoid vendor lock-in. ThevCloud NFV platform supports a rich partner ecosystem of Virtual Network Functions(VNF), VNF managers (VNFM), service orchestration, service assurance, serviceoptimization and analytics vendors. Over 30 vendor platforms can be easily integratedinto the vCloud NFV platform. The figure above shows the modular approach of thevCloud NFV platform and highlights how a multi-vendor approach can be used to createa custom NFV service delivery platform to meet the diverse requirements ofCommunications Service Providers.

Demonstrating the Value of NFV

One of the key advantages of NFV is the ability for CSPs to quickly deploy services tothe market. In deploying NFV, the ability to perform application modeling, applicationblueprinting, provisioning, configuration, VNF deployment, and end-to-end serviceactivation is critical and helps with faster service deployment. This lab will demonstratethis capability. In demonstrating this capability on a carrier-grade platform for a Voiceover Long Term Evolution (VoLTE) solution, multiple VNFs are needed. These VNFs arecombined and deployed as VMs or vApps in a typical production environment. VNFswork in concert to provide a complete VoLTE solution. Taking advantage of the conceptof virtualization to abstract resources, multiple VNF functions are installed on a singlevirtual machine in this lab.

HOL-1786-USE-1


Lab Architecture

This figure illustrates the lab deployment architecture. VMware provides the NFVIplatform, which can host multi-vendor VNFs or multiple VNFs from a single vendor in thevCloud NFV environment. Gigaspaces, a VMware Partner, has provided Cloudify(http://www.getcloudify.org) as the orchestration engine in the NFVI platform. Athonet(http://www.athonet.com), a VMware partner, provided the VNFs for virtual EvolvedPacket Core (vEPC) and for virtual IP Multimedia Subsystem (vIMS), as well as the HomeSubscriber Server (HSS). The following VNFs from Athonet were deployed on theVMware infrastructure:

• vApps - vEPC: VNFs include:◦ Serving Gateway (SGW) and Packet Data Network Gateway (PGW) for the

user plane.◦ Mobility Management Entity (MME) for the control plane.◦ Policy and Charging Rules Function (PCRF) for application layer functions.

• vApps - vIMS: VNFs include:◦ Session Border Controller (SBC) and Proxy Call Session Control Function (P-

CSCF) for the signaling plane.◦ Interrogating CSCF (I-CSCF) and Serving CSCF (S-CSCF), which support

Session Initiation Protocol (SIP) as per 3GPP standards to handle mobilecall service.

◦ Media Gateway Call Function (MGCF) for connection to legacy PSTNnetworks.

• vApp HSS: The HSS was pre-deployed and pre-provisioned with subscriber data.

HOL-1786-USE-1


cme-export/hol-1786-use-1_pdf_en/(http:/www.getcloudify.org)

Module 1 - GettingStarted (15 min)

HOL-1786-USE-1


How Fast “Fast” Really Is - From VNFto VoLTE Service Deployment?One of the key advantages of NFV is the ability of communication service providers(CSPs) to quickly deploy new services. At Interop Tokyo 2016, VMware demonstrated areliable, model-driven approach for VoLTE mobile services. The demonstration includedapplication modeling, application blueprinting, provisioning, configuration, VNFdeployment, end-to-end service activation, and making live mobile calls using 4G LTEdevices, with the entire process taking less than ten minutes, start to finish. This is theindustry’s first and fastest NFV demonstration, proving that NFV is real and achievablefor telecom environments in multi-vendor ecosystems, with service provider-expectedquality of service. This demonstration is proof of VMware infrastructure platformreadiness for volume deployment in production for service providers.

To complete a voice call, at a minimum, a small cell radio access node installed at thepremises is needed to provide tower access for air interface. This is not possible due tovarious constraints in a HOL lab environment. In this module, you can watch thefollowing video that shows the entire sequence that takes place, including users makinginternal and external calls upon completion of service activation.

VMware Orchestrated VoLTE Service Delivery (Video 5:42)

VoLTE Service Deployment

In Module 2 and Module 3, you will perform all the steps as seen in this video until thesystem is ready for deployment and service activation.

<div class="player-unavailable"><h1 class="message">An error occurred.</h1><div class="submessage"><ahref="http://www.youtube.com/watch?v=8DKsMEDkFEo" target="_blank">Try watching this video on www.youtube.com</a>, or enableJavaScript if it is disabled in your browser.</div></div>

HOL-1786-USE-1


Another key advantage of NFV is the horizontal scaling capability that exists for serviceproviders. Based on service demand, service providers can scale the network by addingadditional VNF instances very quickly in an NFV environment without the need to waitfor new hardware and network setup. If service providers see a burst in traffic, new vIMSand vEPC instances can be instantiated from the blueprints and deployed using existinginfrastructure, saving on CAPEX and OPEX.

In Module 4, you will walk through the steps of not only scale-out, but also scale-in (theability to conserve capacity when not needed, a function that was infeasible intraditional telephony).

HOL-1786-USE-1


Module 2 - TOSCA basedBlueprinting & Modeling

(30 minutes)

HOL-1786-USE-1


IntroductionThis module introduces the new concepts of orchestration, blueprinting, and modelingfor NFV.

In the sphere of music, orchestration refers to the identification, organization, andinstructions necessary for a collection of musicians to produce a complex musical work.This includes the identification of the types and number of players, and their specificinstructions for playing. In computing, the metaphor stops somewhat short of providingthe actual "music" that the different components will play together. In computingterminology, orchestration refers to the number and types of components and theirinterconnections. This involves modeling specific computing platforms, networkingcomponents, software components, and the information necessary for all of these tocollaborate. After the model is defined, an orchestrator can interpret it. Beyondmodeling the computing environment and software installation tasks, an orchestrationcan define post-deployment policies and actions, which can operate on the runtimesystem that the orchestration models. For example, the orchestrator might receive CPUmetrics and add CPU capacity dynamically. Alternatively, the orchestration might defineprocesses that update software on a portion of the system.

What is TOSCA?

TOSCA (Topology Orchestration Specification for Cloud Application) is an OASISspecification that defines a language for modeling applications and associatedinfrastructure. A TOSCA model (typically rendered in YAML, a human friendly dataserialization standard for all programming languages) describes all components of asystem, along with the relationships between them in a distinctly object-orientedfashion. Each object (or node) in the model represents a thing or relationship to beorchestrated. A node can be a virtual machine, a firewall, a software program, oranything else. The nodes are described as "types" with operations and properties. Themodel is meant to be the input to an orchestrator, which can interpret it and performspecific "workflows." Cloudify is such an orchestrator. It understands an input model andthen automates the execution of workflows against it. The most fundamental workflowis "install,” which traverses the model, orders the instantiation of model components(such as a VM) by honoring defined model relationships (for example, connected-to orcontained-in), and executes associated code to render the model on its configuredtarget platform (such as VMware vCloud). Beyond being an executor of workflows,Cloudify also provides a runtime called the Cloudify Manager. The Cloudify Manager runsalongside the systems it deploys, and provides services such as metric gathering, a webUI, security, blueprint storage, auto-scaling/healing, and arbitrary automated policyexecution.

From the perspective of NFV, TOSCA and Cloudify provide an open, neutral languageand platform for describing, deploying, and managing VNF forwarding graphs or servicechains. Due to the open, unopinionated nature of the platform, TOSCA and Cloudify are

HOL-1786-USE-1


a powerful way to model and realize network applications involving virtual and non-virtual network functions and arbitrary related software in a VIM/Cloud-neutral way.

The process of TOSCA VNF blueprinting refers to the creation of a YAML descriptor andrelated artifacts. The YAML descriptor and related artifacts are together called a"blueprint." The blueprint can also reference plugins to provide multi-VIMs and othercapabilities. The YAML descriptor defines all components of an architecture, includedVMs, VNF images, network definitions and relationships, and whatever scripting or otherconfiguration is needed to prepare the system to run. Without such a model, a typicalad-hoc approach consists of a proprietary hybrid of scripts and configuration. The YAMLmodel provides a versionable artifact that describes a complex deployment.

HOL-1786-USE-1


Solution BlueprintingYou are a network engineer for Rainpole Telecom and you need to understandblueprinting and modeling for your new VoLTE service. Rainpole Telecom is currentlyutilizing Cloudify as an orchestration platform and Athonet VNFs for their VoLTE servicedelivery. Modeling is accomplished with the creation of a YAML blueprint based onTOSCA principles. As such, nodes for each automated component must be defined. Inthis module, we will deploy a blueprint model and workflow.

A typical blueprint creation workflow includes:

• Identification of all application components that the application consists of.• Identification of existing plugins that will be needed (for example, the Cloudify

vCloud plugin for creating VMs using vCloud Director).• Identification of custom workflows needed. Often, no custom workflows are

required, and only the supplied install, uninstall, scale, heal, and executeoperation are sufficient.

• Identification of custom types needed. In this lab, a custom type is used todescribe the VNFs (and their configuration).

• For each custom type, identify the operations that the type will define and/orimplement. For types that will be configured by the "install" workflow, standardlifecycle events will be implemented (such as configure, start, stop, and so on).These implementations are typically scripts (such as bash, python, ruby, and soon). Installation can also be delegated to a CM tool with its own descriptor (suchas Puppet, Ansible, Chef, Saltstack, and so on).

• Implement the various operations identified. Typically, these are scripts and caninitially be tested in isolation. For example, the configure lifecycle event mightinvoke a script to install a web server. This could be implemented as a simplescript that downloads the installation package, installs it, and performs somecustomization to a configuration file.

• Integration testing. Required workflows (at a minimum, usually "install") areinvoked on the final assembled blueprint, and iterative bug fixing is done.

The vEPC and vIMS blueprints that have been created are based on Athonet VNFscomponents, which are modeled and available based on OS and application softwarebinaries. The vEPC blueprint is based on the VNFs for the following core network nodes:MME, S-GW, P-GW, and PCRF. The vIMS blueprint is based on the SBC and I/P-CSCF VNFs.

HOL-1786-USE-1


Open Chrome Browser from Windows Quick Launch TaskBar

Click on the Chrome Icon on the Windows Quick Launch Task Bar

Upload a Blueprint

1. In the bookmark bar, click Cloudify Console.

2. After the Cloudify Console is open, you should see a list of blueprints.

3. Click Upload Blueprint.

HOL-1786-USE-1


Upload Blueprint

1. Select the blueprint to be uploaded by clicking the file icon on the right side of thewindow.

HOL-1786-USE-1


Select blueprint template

1. Select blueprint.zip.

2. Click Open.

HOL-1786-USE-1


Define blueprint

Enter the following:

1. Blueprint ID: demo_blueprint2

2. Blueprint filename: blueprint.yaml

3. Click Upload.

HOL-1786-USE-1


Successful upload

After the upload completes successfully, the demo_blueprint2 graphical view willappear.

1. Click the Blueprints tab.

HOL-1786-USE-1


New blueprint added

You will see demo_blueprint2 has been added to the list of blueprints. Let's review thecomponents that make up a blueprint.

1. Click demo_blueprint2.

Graphical view

The graphical view of the topology described in the blueprint gives a high-level view ofthe deployment model. This view shows compute-related components such as virtualmachines and the VNF (vEPC and vIMS) residents of those machines. Connected-torelationships are represented by lines. Contained-in relationships are represented bydrawing the contained component inside the container. Note the vEPC inside theepc_host as an example of a contained-in relationship.

HOL-1786-USE-1


Nodes view

1. Click the Nodes tab.

The Nodes view is list of all the nodes defined in this deployment.

HOL-1786-USE-1


Source view

1. Click the Source tab. It can take up to a minute for the Source view to build.

The main part of blueprint files is written in YAML in a declarative DSL (domain-specificlanguage). It describes the logical representation of an application, which is called atopology. In a blueprint, you describe the application’s components, how they relate toeach other, how they are installed and configured, and how they are monitored andmaintained.

Other than the YAML itself, a blueprint can comprise multiple resources such asconfiguration and installation scripts (or Puppet Manifests, Chef Recipes, and so on),code, and basically any other resource you require for running your application.

All files in the directory that contains the blueprint file are also considered part of theblueprint, and paths described in the blueprint are relative to that directory.

You can scroll through the config source view to see all the configuration parameters.

Conclusion

You should now have a firm understanding of the TOSCA blueprinting model and itscomponents as well as the role that TOSCA plays in the service lifecycle.

HOL-1786-USE-1


Now let's move to Module 3 to learn about deploying blueprints and enabling serviceactivation, which is the last step towards enabling the ability to do voice calls.

HOL-1786-USE-1


Module 3 - VoLTE SolutionDeployment (30 minutes)

HOL-1786-USE-1


IntroductionIn this module let's revisit the Network Function Virtual Infrastructure.

HOL-1786-USE-1


Network Function Virtual Infrastructure (NFVI)

The virtual infrastructure is setup in a hardware-agnostic manner, using compute andnetwork virtualization provided by the vSphere and VMware NSX platform. The VNFsoftware runs as application software, fully decoupled from the operating system. Thus,each VNF runs as a native application. The Cloudify orchestration application isdeployed as a VM. Blueprints of deployment profiles are pre-built. A specific workflowprofile is selected from the Cloudify orchestration interface. Upon uploading of theprofile, the Topology view shows the various VNF interfaces, relationships, andconnectivity. This provides a point where the users have ability to go and modify theblueprint if any changes are needed.

The system now performs automatic validation of configuration parameters, and serviceprovisioning is initiated for each vApp and VNF. Based on the properties set in theblueprint and entity relationships as defined in the blueprint, the applications areautomatically configured, network IP address assignments are done, needed OScustomization and fine tuning is completed, and VNFs are powered up automatically.First, the vIMS vApp is automatically deployed, as deployment starts. Because vEPC isdeployed on top of this, the characteristics not known before vIMS deployment are nowautomatically collected in the blueprint and fed into the vEPC system so that the rightoperational entity relationships are established dynamically. Access to the HSS and thenetwork is also programmed dynamically in the blueprint to enable VNFs to contact theHSS and register themselves as part of the service activation process. The entireprocess provides asynchronous updates at the Cloudify user interface layer, and vCloudDirector can be refreshed to see status updates.

HOL-1786-USE-1


Solution DeploymentYou are a network engineer for Rainpole Telecom and you need to understand theorchestration and deployment model for your new VoLTE service. Rainpole Telecom iscurrently utilizing Cloudify as an orchestration platform and Athonet VNFs for their VoLTEservice delivery. Modeling is accomplished by the creation of a YAML blueprint based onTOSCA principles. As such, nodes for each automated component must be defined. Inthis module, we will deploy a blueprint model and workflow. To begin this process, wemust log in to the Cloudify Console.


1. Click on the Chrome Icon on the Windows Quick Launch Task Bar

Open Cloudify

1. In the bookmark bar click Cloudify Console.2. After the Cloudify Console is open you should see a list of blueprints.3. Click the Deployments tab.

HOL-1786-USE-1


Execute workflow

1. Select Execute workflow from the demo_deployment1 blueprint.

Install

1. A new window will pop up click the drop-down and select install.

HOL-1786-USE-1


Confirm installation

1. Click Confirm.

Begin installation

You should see the task in progress, stating Install in the Action column.

Note: This process can take up to 10 minutes to complete.

Monitor progress

You can monitor the process of the install by clicking on demo_deployment1.

HOL-1786-USE-1


Task Failed

Note: If you encounter the Task failed message, the backend VMs are not turned on.To resolve this issue click on ‘vCD-Admin’ panel in your browser and follow steps54-59. Otherwise proceed to step 60 in the lab manual.

HOL-1786-USE-1


Log in to vCloud Director

1. Let's log in to vCloud Director by opening a new window in Chrome and selecting vCDAdmin from the bookmarks bar. When the vCloud Director interface opens, log in towith the following credentials:

User name: administrator

Password: VMware1!

HOL-1786-USE-1


Manage Organization VDC

1. After you have logged in, click Manage organization VDCs.

Select organization

1. Select RP-VDC by clicking on RP-VDC when the pointer turns to a hand.

Power on VM's

In the list, you will see all of the VMs that are involved in the deployment of a VoLTEservice.

HOL-1786-USE-1


1. Select vEPC-02.

2. Select Start/Poweron symbol in the action banner.

3. This will show that vEPC-02 is Powering on in the Status column.

4. Repeat the previous steps to power on vIMS-02.

HOL-1786-USE-1


Check status

Both VM’s/vApps should turn to a Running State in the Status Column

Return to Cloudify

Now lets navigate back to the Cloudify console by returning to the open tab.

Go to Deployments

1. After you are in the Cloudify Console, click the Deployments tab.

HOL-1786-USE-1


Choose deployment

1. Select demo_deployment1.

Verify completion

In the Events pane, you should see that the workflow execution is successful, alongwith green checkmarks in the Topology section.

Congratulations! You have deployed your first VoLTE service. At this point, with all greencheck marks in the Topology section, each VNF is ready to perform its assignedfunction, and the system is ready to perform call processing. You would be able to beginmaking and receiving calls.

The following figure is an example of the type of call flows that can be supported by thisdeployment.

HOL-1786-USE-1


Call flow example

HOL-1786-USE-1


Module 4 - LifecycleManagement of a VoLTE

core (30 minutes)

HOL-1786-USE-1


IntroductionLifecycle management is provided from the NFV management and orchestration (MANO)layer of the ETSI architecture. Lifecycle management is a set of functions required tomanage the instantiation, maintenance, and termination of VNFs. It includes variousfunctions like auto-scaling, self healing, VNF retirement, and day-2 operational aspects,such as patching and upgrades across the solution base. We will learn about scaling andVNF retirement in this module.

HOL-1786-USE-1


Auto-ScalingInitial deployment and service activation sets the system in motion to quickly providevalue added services to customers. One of the key advantages of NFV is the horizontalscaling capability that exists for service providers. Based on service demand, serviceproviders can scale the network by adding additional VNF instances very quickly in anNFV environment without the need to wait for new hardware and network setup. Ifservice providers see a burst in traffic, new vIMS and vEPC instances can be instantiatedfrom the blueprints and deployed using existing infrastructure, saving on CAPEX andOPEX.

As the deployment runs, it is monitored for performance. Should it be required to scaleout the deployment to handle more load (in this case more calls) then that activity canbe performed through the Cloudify Manager interface. If it is determined that theplatform is underutilized, it can also be scaled back in. In the instance of this lab, ascale-out event entails adding a vEPC and a vIMS VNF to the running deploymentservice chain. Conversely, a scale-in event reduces each of those VMs by one (assumingthere is more than one of each prior to the event being initiated).

In this module, we will walk through the steps to scale the current environment.


1. Click on the Chrome Icon on the Windows Quick Launch Task Bar

HOL-1786-USE-1


Open Cloudify

1. In the bookmark bar, click Cloudify Console.2. After the Cloudify Console is open, click the Deployments tab.

Select deployment

1. Click demo_deployment1.

HOL-1786-USE-1


Execute workflow

In the Topology tab, you will see the topology diagram.

1. Click Execute Workflow.

Start execution

1. A new window will open. Click the drop-down menu and select scale.

HOL-1786-USE-1


Scale-out

1. If you were to actually scale-out the deployment, you would enter scale_groupin the node_id field and a positive number in the delta field.

2. However, for the purposes of this lab, do not enter a value. Click Cancel.

HOL-1786-USE-1


Scale-out activity

Scale-out activity launches a workflow where Cloudify Manager contacts vCloud Directorand instantiates two new VMs, one for vEPC and one for vIMS. The remaining VMs willremain unchanged. The VMs are created and started, operating system images areinstalled, network interfaces are deployed, and applications are installed andconfigured. The two new instances would then join the pool of the original runninginstances to effectively double their pool capacities.

In the Topology view of the deployment, the green numbers increment over the vEPCand vIMS VMs.

Now let's walk through the scale-in process.

Execute workflow

In the Topology tab, you will see the topology diagram.

1. Click Execute Workflow.

HOL-1786-USE-1


Start execution

1. A new window will open. Click the drop-down menu and select scale.

HOL-1786-USE-1


Scale-in

1. If you were to actually scale-in the deployment, you would enter scale_group inthe node_id field and a negative number in the delta field.

2. However, for the purposes of this lab, do not enter a value. Click Cancel.

Scale-in activity

Scale-in activity launches a workflow where Cloudify Manager contacts vCloud Director,and one of the vIMS instances and one of the vEPC instances are unregistered from thepool, stopped, and the VMs are deleted.

In the Topology view of the deployment, the tiny green numbers decrease over thevEPC and vIMS VMs.

HOL-1786-USE-1


Conclusion

When a deployment is in production, it is rarely just deployed and left to run. Thesemanual operations display the agile nature with which this VoLTE deployment can beexpanded to accommodate additional calls and scaled back in when demand hasdecreased. By leveraging these capabilities, you can adapt the infrastructure to exactlywhat is needed and make the most efficient use of the cloud infrastructure.

HOL-1786-USE-1


Retiring ApplicationsOpen Chrome Browser from Windows Quick Launch TaskBar

1. Click on the Chrome Icon on the Windows Quick Launch Task Bar.

Open Cloudify

1. In the bookmark bar, click Cloudify Console.2. After the Cloudify Console is open, click the Deployments tab.

HOL-1786-USE-1


Execute workflow

1. Select Execute workflow from the demo_deployment1 blueprint.

Uninstall

1. A new window will open. Click the drop-down menu and select uninstall.

HOL-1786-USE-1


Confirm

1. Select Confirm.

Verify Success

After this process has been completed, all the green check marks will be removed fromthe topology, and you can see that the workflow ended successfully.

This process can take up to 10 minutes.

HOL-1786-USE-1


Start deployment removal process

Now that the uninstall has occurred, let’s retire the deployment.

1. To begin, click the Deployments tab.

Delete deployment

Now you should see a list of all deployments.

1. Click the down arrow next to Execute Workflow for demo_deployment1.

2. Click Delete.

HOL-1786-USE-1


Confirm delete

1. Select Yes.

Conclusion

You will now see that the demo_deployment1 has been removed from the list,completely removing the deployment.

Upon completion of this lab module, you have seen how to manage the lifecycle of thedeployment in the platform. You have scaled it out, scaled it back in, and finally deletedit.

HOL-1786-USE-1


Conclusion

HOL-1786-USE-1


Lab ConclusionNow that you have completed all four modules of this lab, you should have a clearerunderstanding of application modeling, application blueprinting, provisioning,configuration, VNF deployment, and end-to-end service activation, and how making livemobile calls using 4G LTE devices, can be accomplished using vCloud NFV platform.

While this deployment is focused on a VoLTE service, these steps and methods can beapplied to any VNF-based service deployment on this platform, whether it is for vEPC- orvCPE-based solutions.

HOL-1786-USE-1


ConclusionThank you for participating in the VMware Hands-on Labs. Be sure to visithttp://hol.vmware.com/ to continue your lab experience online.

Lab SKU: HOL-1786-USE-1

Version: 20170502-055027

HOL-1786-USE-1


http://hol.vmware.com/

Documents

Lab Overview - HOL-1786-USE-1