VMware Hands-on Labs - HOL-1883-02-HBD


Lab Overview - HOL-1883-02-HBD - VMware Cloud Provider Program - Tools and Offerings

Lab Guidance


Note: It will take more than 90 minutes to complete this lab. You should expect to only finish 2-3 of the modules during your time.  The modules are independent of each other so you can start at the beginning of any module and proceed from there. You can use the Table of Contents to access any module of your choosing.

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

Audience for this lab:

The primary audience for this lab is VMware Cloud Provider administrators or anyone interested in learning how vCloud Director works with some of the other product offerings in the VMware product catalog.

VMware Cloud Provider solutions, offered through the VMware Cloud Provider Program (formerly known as vCloud Air Network), enable rapid and cost effective delivery of hybrid cloud services that customers increasingly demand. Whether infrastructure-as-a-service, disaster recovery or desktop-as-a-service, service providers can benefit from decreased time to market, reduced capital investments and lower development costs to stay competitive in the cloud computing market.

In this lab, we will explore vCloud Director interoperability with NSX, vSAN, vRealize Operations, vRealize Log Insight, vCloud Availability, and Usage Meter.

Lab Module List:

 Lab Captains:

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 have a localized manual deployed with your lab, you may utilize this document to help guide you 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 tab to the Right of the Main Console.
  2. A particular lab may have additional consoles found on separate tabs in the upper left. 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 your work must be done during the lab session.  But you can click the EXTEND to increase your time.  If you are at a VMware event, you can extend your lab time twice, 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.

 

 

Alternate Methods of Keyboard Data Entry

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

 

 

Click and Drag Lab Manual Content Into Console Active Window

You can also click and drag text and Command Line Interface (CLI) commands directly from 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 indicating that Windows is not activated.  

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

Rest assured, VMware and the Hands-on Labs are in full compliance with Microsoft licensing requirements.  The lab that you are using is a self-contained pod and does not have 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 you to start. If you see anything other than "Ready", please wait a few minutes.  If after 5 minutes your lab has not changed to "Ready", please ask for assistance.

 

Module 1 - NSX with vCloud Director (30 Minutes)

Introduction


NSX and vCloud Director

vCloud Director is reliant on NSX for things like VXLAN and Edge deployments. But you can do more with NSX and vCD, including Distributed Firewall management and Distributed Logical Routing. This module includes:

NSX Basics with vCloud Director - Learn some of the basics of how NSX is used with vCloud Director

Distributed Firewall Management - Manage Distributed Firewall throught the vCloud Director interface

Distributed Logical Routing - Manage Distributed Logical Routing through the vCloud Director interface


NSX Basics with vCloud Director


This section shows how vCloud Director works with NSX to provide networking and security in a multi-tenant environment.

Providing infrastructure-as-a-service (IaaS) services involves more than providing just compute and storage resources. It involves providing agile networking capabilities and services that are easy to consume. NSX Manager virtualizes networks and security to create efficient, agile, extensible logical constructs that scale requirements and meet the performance of virtualized data centers. vCloud Director supports different types of networks:

These networks enable end users to self-provision separate L2 network segments, define custom L3 Internet protocol (IP) policies, and configure networking services such as dynamic host configuration protocol (DHCP), NAT, and firewalls.

Let us explore what this looks like in vCloud Director.


 

Manage the Edge

First, we will take a look at what this looked like in previous versions of vCD and compare it to the new interface.

 

  1. In the vCD Admin interface, select Manage & Monitor
  2. Click on the Organization VDCs
  3. Double click on T2-OVDC

 

 

Edge Gateways

 

  1. Select the Edge Gateways tab
  2. Select the T2-ESG within the Edge Gateways tab
  3. Click the Actions button and a menu will open
  4. Note the Convert to Advanced Gateway option, but DO NOT select it
  5. Click on Edge Gateway Services...

 

 

Available Edge Services

 

  1. Note the tabs that are available at the top.  These are the options that have traditionally been available for management through the vCD interface.
  2. Click Cancel to close the pop-up window

 

 

Select T1-OVDC Organization VDC

 

  1. Next, let us take a look at the new interface by going back to the System tab
  2. Double click on T1-OVDC

 

 

Open Edge Gateway Services

 

  1. Select the Edge Gateways tab
  2. Select the T1-ESG within the Edge Gateways tab
  3. Click the Actions button and a menu will open
  4. Note the Convert to Advanced Gateway option is grayed out.  This Edge Gateway has been upgraded
  5. Click on Edge Gateway Services...

 

 

HTML5 Interface

 

A new tab opens up within the browser.  As you can see, we are in the process of migrating to an HTML5 interface.

  1. Note the new configuration options that are available at the top that can now be managed through the vCD interface.  Feel free to click on some of the new features, like SSL VPN-Plus, Certificates, Grouping Objects, Statistics, and Edge Settings. Even the Routing option has changed. In the past, only static routes were available. Now we can configure dynamic routing protocols like OSPF and BGP. This particular Edge is configured for BGP. Take a look at the configuration.
  2. Close the browser tab when you are finished.

Next, we will take a look at the HTML5 Tenant Interface.

 

 

HTML5 Tenant Interface

 

From the open Chrome browser:

  1. Click the Customize and Control button to the right of the address bar
  2. Select New incognito window

 

  1. Click the vCD - Tenant1 folder in the bookmarks bar and select vCD - T1 HTML5
  2. Type in the user name of t1admin
  3. Type in a password of VMware1!
  4. Click Login

 

 

Tenant Networking

 

  1. Click on the Network section
  2. Click on Edge Gateways

If you select the T1-ESG and click Configure Services, you will see a similar screen to what we saw before when managing vCD from the classic Flex interface.

The Security section is where you can manage the Distributed Firewall, which is covered in the next section.

When you're done, close the Incognito window.

 

Distributed Firewall Management


This section shows how to manage NSX Distributed Firewall in vCloud Director.


 

Manage Firewall

 

  1. Go back to the vCD Admin interface and the T1 Administration tab
  2. Click on Virtual Datacenters
  3. Select T1-OVDC
  4. Click on the Actions button
  5. Select Manage Firewall...

 

 

Distributed Firewall

 

A new tab will open up in the browser with the new HTML5 interface

  1. We can now manage (add/change/remove) Distributed Firewall rules and settings through vCD
  2. Close the browser tab when you're finished

 

 

HTML5 Tenant Interface

 

From the open Chrome browser:

  1. Click the Customize and Control button to the right of the address bar
  2. Select New incognito window

 

  1. Click the vCD - Tenant1 folder in the bookmarks bar and select vCD - T1 HTML5
  2. Type in the user name of t1admin
  3. Type in a password of VMware1!
  4. Click Login

 

 

Tenant Security

 

  1. Click on the Network section
  2. Click on Security
  3. Select Security Services for T1-OVDC
  4. Click Configure Services

 

 

 

Manage Distributed Firewall

 

The Distributed Firewall management page looks the same as it did as an HTML5 popout in the class Flex interface. The Distributed Firewall section shows you the rules that are defined. The Grouping Objects section allows you to create logical groups of objects. The Secutiy Tags section allows you to create Security Tags and apply them to objects.

 

 

Add a New Rule

 

  1. Click the + button to add a new rule
  2. Click the Name field to name your new rule
  3. Hover over Source and click the + icon to add a new source

 

 

Define the Rule

 

Click the Browse objects of type dropdown menu. Traditional firewalls base rules on IP addresses and/or ranges. Notice that the NSX Distributed Firewall can base rules not only on IP Sets, but also on objects visible to the vCD tenant.

 

  1. Select Virtual Machines
  2. Click T1-tclinux-01a on the left side
  3. Click the right arrow
  4. Click Keep

 

You can set Destination in a similar manner to setting Source. If you click on the Service section, you'll see there are a number of pre-defined services to pick from. You can filter by typing in the Filter section above the list of services (try "ICMP Echo" as an example - note that it is case sensitive). Then you can pick Action, Direction, Packet Type, and where to apply the rule.

When you're done setting the rule the way you want, you can save or discard changes by clicking on the link in the yellow bar.

Play with the rules. When you're done, close the Distributed Firewall management window and close the incognito window.

 

Distributed Logical Router


This section shows how to manage Distributed Logical Router in vCloud Director.

The DLR is optimised for forwarding in the logical space between VMs, on VXLAN-backed or VLAN-backed portgroups.

The DLR has the following properties:

Keep in mind the following caveats:

The DLR’s design at a high level is analogous to a modular router chassis, in the following ways:

Distributed Routing in vCloud Director is enabled on the Edge Services Gateway in the Org VDC. This allows DLR services for all networks connected to the Edge Services Gateway.


 

Enable Distributed Routing

 

In the vCloud Director Admin interface:

  1. Go to the T1-OVDC
  2. Click on the Edge Gateways tab
  3. Right-click on the T1-ESG
  4. Select Enable Distributed Routing

 

Click Yes on the popup window.

 

  1. Wait for the Status to go green again.
  2. Then notice the green checkmark in the Distributed Routing column.

 

Conclusion


You should now have a better understanding of NSX and how to use it with vCloud Director.


 

You've finished Module 1

Congratulations on completing Module 1.

If you are looking for additional information on NSX in a service provider environment using vCloud Director, take a look at the Network and Security section of the vCloud Architecture Toolkit for Service Providers (vCAT-SP):

Proceed to any module below which interests you most.

 

 

 

How to End Lab

 

To end your lab click on the END button.  

 

Module 2 - vSAN and vCloud Director (30 minutes)

Introduction


vSAN and vCloud Director

vSAN is radically simple, enterprise-class software-defined storage powering VMware hyper-converged infrastructure. It allows Service Providers to offer tiered storage options to their customers, either using vSAN as an additional tier to existing storage, or by simply offering multiple storage profiles on vSAN as the sole storage solution. This module includes:

Introduction to vSAN - Learn some of the basics of vSAN and how it can be used with vCloud Director

Storage Profiles - Create a vSAN Storage Profile and map it through to an Organization VDC in vCloud Director


Introduction to vSAN


This section will go over an introduction to VMware vSAN (formerly Virtual SAN).


 

Virtual SAN Overview

Object-based storage is considered a leading technology for hybrid cloud deployments because many of its most prominent features, such as massive scalability, geographic independence, and multi-tenancy, have proven ideal for cloud storage. vSAN is a hyper-converged, software-defined storage solution that stores and manages data in the form of storage objects. Similar to vSphere, vSAN can leverage commodity physical servers and locally-attached flash devices and/or hard disks. vSAN is also completely integrated into the VMware stack, so it works seamlessly with advanced availability features such as VMware vSphere vMotion, VMware vSphere High Availability (HA), VMware vSphere Distributed Resource Scheduler (DRS), and VMware vSphere Fault Tolerance (FT).

 

 

Use Cases

Cloud service offerings can utilize either traditional infrastructure (servers with legacy storage), or hyper-converged platforms such as vSAN. A hyper-converged platform is a platform that combines compute, storage, networking, and virtualization resources and management, enabling scale-out consumption. The tight integration of vSAN with VMware vSphere enables VMware Cloud Providers to host public or private cloud offerings and easily utilize vSAN as the underlying storage infrastructure.The customers of service providers that leverage vSAN primarily run mission-critical workloads in which stability, reliability, and predictability are extremely important. Many traditional infrastructures, over time, hinder the ability of VMware Cloud Providers to remain competitive in such a price-sensitive market.  vSAN enables VMware Cloud Providers launching new offerings to avoid the large capital expenditures typically associated with legacy storage arrays. VMware Cloud Providers who offer consumers hybrid cloud-based virtualized solutions, such as vSphere as a Service, Desktop as a Service, Tier 1 applications, and Database as a Service, are ideal candidates for vSAN.  Additionally, VMware Cloud Providers can leverage vSAN as the storage infrastructure for their VMware vCloud Director cloud offering.

 

 

vSAN with vCloud Director

 

vSAN can be used as storage in Management Clusters, Tenant Clusters, as the only storage option, or as a tiered storage option with existing non-vSAN storage. vSAN can even be used for storage tiering when it is the only storage (using different storage policies).

 

 

vSAN Configurations

vSAN is available in two configurations, hybrid and all-flash. Both configurations have a caching tier and a capacity tier. The total storage of the vSAN datastore is the sum of capacity of all the disks in the capacity tier.

Hybrid Configuration

The hybrid configuration for vSAN uses magnetic disks for the capacity layer and flash memory devices for the cache layer. This option is ideal for workloads that have average storage performance requirements.

All-Flash Configuration

The all-flash configuration for vSAN uses flash devices for both capacity and caching. This option is available for workloads with high storage performance requirements. The all-flash configuration also allows for more advanced storage technologies, like de-duplication, compression, and erasure-coding (similar to RAID levels 5/6 on traditional storage).

 

 

Storage Policies

When vSAN is enabled on a cluster, a single vSAN datastore is made available to all the hosts in the cluster. A default vSAN Storage Policy is created to define how VMs are stored on the vSAN datastore. Because vSAN is object-based storage, multiple storage policies can be used to change the way different VMs are stored on the vSAN datastore. When vSAN is used with vCloud Director, the different storage policies can be presented to vCloud Director VDCs to allow storage tiering options to the vCD tenants.

 

 

 

 

Log in to vSphere Web Client

If it's not already open, launch the Chrome browser from the Windows Quick Launch taskbar.

 

Log in to the vSphere Web Client as:

User name: administrator@vsphere.local

Password: VMware1!

 

 

 

 

Go to Hosts and Clusters

 

If you're not already in the Hosts and Clusters view, click on the Home icon (1) and select Hosts and Clusters (2).

 

 

 

vSAN Cluster

 

Select the RegionA01-COMP01 (1) cluster and go to the Configure tab (2).

 

 

 

vSAN Settings

 

Under Virtual SAN, select General.

Here we can see that Virtual SAN is turned ON. We can also see that Deduplication and compression is Enabled.

 

 

 

Monitor vSAN

 

Click the Monitor tab (1) and select Virtual SAN (2). Note: You may need to click the double-down arrow (3) to see it.

By clicking on the different options on the left (4), you can see how vSAN is running.

 

 

vSAN Capacity

 

Click on the Capacity tab to see our overall capacity as well as how well Deduplication and Compression are working.

 

 

Storage Profiles


This section will focus on using vSAN Storage Policies in vSphere and in vCloud Director.


 

Policies and Profiles

 

Click on the Home icon (1) and select Policies and Profiles (2).

 

 

 

VM Storage Policies

 

Click on VM Storage Policies.

 Here we can see what storage policies have been defined in this environment. Note that there are two different policies for vSAN. The first is the Virtual SAN Default Storage Policy. This policy was automatically created when vSAN was enabled on the cluster. This policy shows the default settings for vSAN. The second is the vSAN HOL Policy. This policy was created for the HOL environment. It is configured for no redundancy.

 

 

Create a New Policy

 

Click the Create a New Policy icon. A new window will pop up.

 

 

 

Name the Policy

 

Name the new policy User Policy 1 (1). Click the Next button (2).

 

 

Policy Structure

Read about the Policy Structure. Click the Next button when done.

 

 

Common Rules

Leave the box unchecked and click the Next button.

 

 

Rule Set 1

 

Leave the box checked and click the <Select provider> dropdown menu and select VSAN.

Note: If VSAN doesn't show up in the Storage Type dropdown, you may need to refresh the storage providers. Cancel creating a new policy and go through the following steps.

 

 

Click the Home dropdown menu and select Storage.

 

  1. Click the vCenter server
  2. Click the Configure tab
  3. Click the Storage Providers section
  4. Click the icon to Rescan storage providers
  5. Click the Back button to go back to Policies.
  6. Go back a few pages to Create a New Policy.

 

 

Set vSAN Storage Policies

 

Click the <Add rule> dropdown to go through each of the different settings to see what options are available for vSAN storage policies.

 

Click on the ( i ) icon for more details on each setting. If you want to have more than one rule associated with your policy, click the <Add rule> dropdown menu to select the next rule. When you're done setting the rules you want, click the Next button.

 

 

Storage Compatibility

 

The Storage Compatibility page shows which datastores are compatible with the policies you selected. Since you set the policy to use vSAN rules, the vSAN datastore should be the only one that shows up as compatible. Click the Next button, and then the Finish button on the next screen.

Note: if you don't see the VSAN datastore show up as compatible, you won't be able to use this policy in vCD. Go back and simplify your rules to make the lab environment compatilble (use default settings or simply remove rules - a policy with a single rule of Force Provisioning set to Yes will work).

 

 

Launch vCloud Director Admin portal

 

In the Chrome web browser, click the vCD - Admin shortcut on the Bookmark bar.

 

 

Log in to vCloud Director

 

Log in to vCloud Director as:

User name: administrator
Password: VMware1!

 

 

Manage & Monitor

 

Click the Manage & Monitor tab.

 

 

Go to the Gold PVDC

 

Click on the Provider VDCs (1). Then click on the Gold-PVDC (2) row to highlight it. Then mouse over the Gold-PVDC (3) again and click on the hyperlink.

 

 

Gold PVDC Storage Policies

 

Click on the Storage Policies tab.

 

 

Add a Storage Policy to the PVDC

 

Click the green plus icon to add a new Storage Policy. A new window will pop up.

 

 

Add User Policy 1 to the PVDC

 

Click User Policy 1 (1), click the Add button (2), then click OK (3).

Note: it may take a few minutes for the new policy to show up. If the policy isn't there when you get to this screen, wait a minute and click the refresh icon (4). Keep doing this until the new policy shows up. If it never shows up, go back to the vSphere Web Client, edit the policy and make sure it shows Compatible storage. If it doesn't show compatible storage, it won't show up in vCD as an available storage policy.

 

 

Organization VDCs

 

Click on Organization VDCs.

 

 

Open the T1 Org VDC

 

Click the T1-OVDC row to highlight it, then mouse over T1-OVDC and click the link to open the T1 Organization VDC.

 

 

T1-OVDC Storage Policies

 

Click the Storage Policies tab to view the storage policies associated with the Organization VDC.

 

 

Add a Storage Policy to the OVDC

 

Click the green plus sign to add new storage policies to the Organization VDC. A new window will pop up.

 

 

Add User Policy 1 to the OVDC

 

Click User Policy 1 (1), click the Add button (2), then click OK (3).

Now the new User Policy 1 storage policy is available to Tenant 1 users in the Gold PVDC.

 

Conclusion


You should now have a better understanding of vSAN and how to use it with vCloud Director for creating tiered storage profiles.


 

You've finished Module 2

Congratulations on completing Module 2.

If you are looking for additional information on vSAN in a service provider environment, take a look at the Storage and Availability section of the vCloud Architecture Toolkit for Service Providers (vCAT-SP):

Proceed to any module below which interests you most.

 

 

 

How to End Lab

 

To end your lab click on the END button.  

 

Module 3 - vRealize Operations with vCloud Director (45 minutes)

Introduction


vRealize Operations and vCloud Director

VMware vRealize Operations delivers intelligent operations management across the physical, virtual, and cloud infrastructure, enabling the VMware Cloud Provider to efficiently operate a cloud platform and meet required customer service level agreements (SLAs).

vRealize Operations correlates data from applications to storage in a unified easy-to-use management tool that provides control over performance, capacity, and configuration, with predictive analytics driving proactive action policy-based automation.

This module includes:

vRealize Operations Overview - Learn some of the basics of vRealize Operations and how it can be used with vCloud Director

Custom Reports for Tenants - Learn how to use reports to easily provide vROps information to tenants

Custom Dashboards for Tenants - Learn how to provide tenants access to vROps dashboards.


vRealize Operations Overview


This lesson will cover a general overview of vRealize Operations for VMware Cloud Partners.


 

vRealize Operations Overview

vRealize Operations is the key component of a VMware Cloud Provider service offering. It provides a simplified yet extensible approach to operations management of the cloud infrastructure.

vRealize Operations collects and analyzes information from multiple data sources and uses advanced analytics algorithms to learn and recognize the normal behavior of every object it monitors. Through dashboard views and reports, users are able to view details so they can make informed decisions in the following areas:

vRealize Operations uses management packs to collect, analyze, and present data from many VMware and third-party data sources, thereby providing a holistic view of a service providers cloud infrastructure and tenant-specific workloads.

 

 

Deployment Model Considerations

 

Multiple deployment models are available when deploying a vCloud, depending on the manner in which resources are provided and who consumes them. These are:

 

 

Launch Chome Browser

 

If it's not already open, launch the Chrome browser from the Windows Quick Launch taskbar.

 

 

Open vRealize Operations

 

Click the vRealize Operations shortcut on the bookmarks bar.

 

 

Log in to vRealize Operations

 

Log in to vRealize Operations as:

User name: admin
Password: VMware1!

 

 

Home Dashboard

 

When you first log in, you will see a dashboard named Home. This is a good dashboard to look at first as it shows a high-level overview of how well everying in the environment is running.

 

 

Dashboard List

 

You can access more dashboards by clicking on the Dashboard tab at the top and then clicking the All Dashboards dropdown menu and selecting another dashboard. When it is first installed, vRealize Operations only has its built-in dashboards and vSphere dashboards. When Management Packs are installed in vRealize Operations, they install an adapter to allow vRealize Operations to collect metrics from that source. They also install some pre-built dashboards to allow you to easily make use of the new metrics. Notice this lab environment has dashboards for NSX, vSAN, and vCloud Director. You can also build custom dashboards, like the vCD Tenant dashboard we built in this lab. Click around and look at some of the different dashboards.

The Dashboard section is also where you can view and create dashboards and reports. You can define custom alerts and notifications. You can also create custom profiles, Super Metrics, and define profiles.

Later in this module we'll show how to create custom reports and dashboards.

 

 

Navigation

 

When you're on the Home section, you can see other sections of vRealize Operations across the top. As you click on different sections across the top, the content in the left-hand navigation pane changes. Click on the the Alerts tab at the top of the bar to see the Alerts section.

 

 

Alerts

 

The Alerts section shows all alerts on objects in the vRealize Operations environment. You can filter the results (1) to find things faster, cancel alerts, suspend alerts, take ownership, release ownership, or group alerts (2). Clicking an alert will take you to a screen with more details on the alert (3).

Click the Environment icon (4) at the top of the navigation bar to go to the Environment section.

 

 

Environment

 

In the Environment section of vRealize Operations, you can see Groups, Applications, and Inventory Trees. You can create custom groups and you can click on different inventory trees to see data being collected by different adapters. The most familiar inventory tree for vSphere administrators is the vSphere Hosts and Clusters tree. Click on vSphere Hosts and Clusters.

 

 

vSphere Hosts and Clusters

 

Click the arrows (1) to expand vSphere World down to see the clusters. Click on the RegionA01-COMP01 cluster (2).

 

 

Cluster details

 

In the main window, you'll see a summary of the cluster. This is similar to the Home tab we saw earlier, but it is just showing information for the cluster. You can click on different tabs across the top of the window to see more details and analysis of how things are running in the cluster. Click the more link to show advanced tabs.

 

 

Analysis

 

Click the Analysis tab to see a breakdown of how the cluster is running. Click through each of the different sub-tabs (Workload, Anomalies, Faults, Capacity Remaining, Time Remaining) to see different analytic breakdowns of the cluster.

 

 

Back to Environment

 

Click the back button in the UI (not the browser back button) to go back to the Environment section.

 

 

vCloud Provider Tree

 

Click the arrow (1) next to Management Pack for vCloud Director to expand it. Click on vCloud Provider (2) to see all objects being brought in by the vCloud Director Management Pack.

 

 

vCloud Provider

 

Click the arrow next to vCloud World (1) to expand and keep clicking arrows to expand the environment. Similar to the vSphere Web Client, whatever you select in the left-hand navigation pane is what you'll see details for in the main window. Click around to see different analytic details about the vCloud Director environment with regards to Provider side resources.

 

 

Back to Environment

 

Click the back button in the UI (not the browser back button) to go back to the Environment section.

 

 

vCloud Tenant Tree

 

Click on the vCloud Tenant tree.

 

 

vCloud Tenant

 

Click the arrow next to vCloud World (1) to expand and keep clicking arrows to expand the environment. Similar to the vSphere Web Client, whatever you select in the left-hand navigation pane is what you'll see details for in the main window. Click around to see different analytic details about the vCloud Director Tenant envrionment.

 

 

Administration

 

Click the Administration tab at the top of the screen.

The Administration section is where you go to add new Management Packs (Solutions), define policies, and configure access control, among other things.

By default, vRealize Operations only collects data from vCenter. You can add Management Packs to vRealize Operations to collect metrics from other sources, like applications, storage devices, and network devices. To add a new Management Pack, you go to Solutions and click the green + icon. Once the .pak file is uploaded, you can then configure the solution for collection. Take a look at some of the solutions we have installed in this lab.

 

Custom Reports for Tenants


While admins will definitely appreciate using vRealize Operations for operations management, many VMware Cloud Partners are looking for ways to add value to their service offerings. Possibly the easiest way to use vRealize Operations to provide added value to tenants in a multi-tenant environment is building custom reports for tenants.

What makes it easy is that you can create a single custom report that can be used on each individual tenant, giving each tenant the perception that they have their own custom report. In this section of the lab, we will create a custom report and run it on different tenants.


 

Reports

 

Click the Dashboards tab (1) at the top of the screen and then the Reports link (2) in the left-hand navigation bar. There are a number of existing built-in reports you can use, if you like. But most of the built-in reports are limited in scope, focusing on a small set of metrics. You would have to run multiple reports to see all the metrics you want to see. However, you can build a custom report to be able to show multiple metrics in a single report.

 

 

Custom Reports

Creating custom reports usually involves some trial and error to decide which Views and metrics you want to show up in your report. To simplify this process for the lab, we pre-built a custom report that can be used for vCD tenants.

Search for "vcd" in the filter (1).

 

To create a new custom report, you would click the green + icon. But for this lab, we will edit the pre-built report. Click the report named vCD Tenant Summary (2) and then click the pencil icon (3) to edit the report.

 

 

Name and Description

 

Click the Name and Description link.

When you build a new custom report, this is the first screen you see. You would just give your report a name and description. Then you would go to Views and Dashboards to define the content of the report.

 

 

Views and Dashboards

 

Click on Views and Dashboards.

Views and Dashboards is where you decide what Views to include in your report. Views are used by both Dashboards and Reports to provide a visual representation of metric data. There are a number of built-in Views in vRealize Operations. If you can't find a View that shows what you want, you can built a custom View by clicking the green + icon. Views can be configured to show any metrics that vRealize Operations is collecting on any objects that vRealize Operations has in inventory.

We have already selected some Views for the vCD Tenant Summary Report.

 

 

Formats

 

Click the Formats section to decide which output formats you want the report to use.

 

 

Layout Options

 

Click the Layout Options section. You can check the boxes to include a Cover Page, a Table of Contents, and a Footer. We will keep things simple for the lab, so leave them unchecked. Click the Cancel button.

 

 

 

Run Report

 

Run the report by clicking on the Run Report icon.

 

 

Select an Object

 

When you run a report, you can select what part of the environment you want to run the report against. Click the dropdown menu and select vCloud Tenant (1). In a multi-tenant environment, you can run the same report on different tenants and each report will only have the information for each respective tenant in it.

Click the arrows (2) to expand vCloud World and vcd-01a. Select T1 (3) and click OK (4).

Go through the same steps to run the report for T2.

 

 

Generated Reports

 

Click the Generated Reports link or tab to see the reports that have been generated.

 

 

Viewing Reports

 

It may take a few minutes for the report to run and show up in the Generated Reports list. Once the report shows up, you can click on one of the links in the Download section to download and view the report.

Download the PDFs for T1 and T2 and see how they only show information for the VMs for each tenant.

 

Click the downloaded file links at the bottom of the Chrome window to view the files.

 

 

Scheduling Reports

 

Go back to the vRealize Operations tab in the browser. Click on the Report Templates tab. Click the gear icon. Note that you can schedule reports.

Reports can be scheduled to run on a recurring basis (daily, weekly, monthly). You can also configure the scheduled report to be sent to an email address.

The scheduling window is too big to show properly in the HOL environment, so don't actually click the Schedule report link. If you accidentally click it, just click the X in the upper right-hand corner to close the scheduling window.

 

 

Reports for Multi-tenancy

Now you've seen that you can build a custom report that can be run on different tenants. Because scheduling allows you to send the report via email, you can configure a scheduled report to send each tenant a copy of the report for their portion of the environment. This is an easy way to add value for tenants with vRealize Operations.

 

Dashboards for vCloud Director Tenants


Having vRealize Operations email reports to tenants is an easy way to add value. But what if a tenant wants to be able to log in to see how their environment is running in real time? While vRealize Operations is not built for multi-tenancy, there is a way to use role-based access control and custom groups to allow a tenant to log in to see their environment. There is a whitepaper on the vCloud Architecture Toolkit for Service Providers (vCAT-SP) that shows how to do this. This portion of the lab is based on that paper.


 

Open an Incognito Window

 

Open an Incognito Window in Chrome by clicking the icon in the upper right-hand corner and selecting New incognito window.

 

 

Open vRealize Operations

 

In the new Incognito window, click the vRealize Operations shortcut in the bookmarks bar. Log in as:

User name: t1admin
Password: VMware1!

 

 

Custom Dashboard

 

Click on the Dashbord tab and then click the vCD Tenant dashboard in the left-hand navigation. Notice that the Object List only shows VMs associated with Tenant 1 (the vApp VMs and Edge Gateways). Click on an object to see its workload populate the Workload window. If you want, you can scroll down to the Metrics section and double-click on a metric in the Metric Picker to see it in the Metric Chart.

It took a lot of work to make this happen. We had to create a custom dashboard, a custom group for objects that belong toTenant1, create a custom role for tenants, create a login for Tenant1 and assign the role to them. We also had to remove all the dashboards from the Everyone group and create new Admin and Tenant groups. It also took a lot of work playing with the permissions to limit what tenants can see. While this method is functional, it's a lot of work and not something you would want to do for every tenant.

Let's look at an easier way to provide vROps information to vCD tenants. Close the Incognito window.

 

 

 

vRealize Operations Manager Tenant App for vCloud Director

 

  1. Open a new tab
  2. Click on the vROps vCD Tenant UI bookmark

If you're still logged in to vRealize Operations as Admin, it should automatically log you in. If not, log in with:

User name: admin

Password: VMware1!

 

 

Tenant App Admin

 

In order to use the Tenant App, you need to install the latest version of the vCloud Director Management Pack in the Solutions section of vRealize Operations. You will also deploy an OVF for the Tenant App appliance. When you first deploy the Tenant App appliance, you'll need to log in as the vRealize Operations administrator to configure access for tenants. You can also use this interface as a much easier way to get a quick view of how things are running in the vCloud Director environment.

 

 

Configure Tenant Access

 

Click Organizations in the left-hand navigation window. Notice that T1 and T2 already have 1 user created. We created these users for the lab. Normally, when you first log in, there will be zero users (like the Public Organization). To create users, click the user icon.

 

You can add users by clicking the + USER link or you can import users from LDAP by clicking the IMPORT link.

Notice that the user for T1 is t1appuser. Let's log in to see what they can see. Click the DONE button.

 

 

Log Out of Admin

 

In the upper right-hand corner, click on admin (1) and select Log out (2).

 

 

Log in as Tenant 1

 

Log in as:

User name: t1appuser
Password: VMware1!

Click around and play with the Tenant App.

 

Tenant App Plugin


One more thing you can do with the vRealize Operations Tenant App for vCloud Director is publish the Tenant App data into the vCloud Director user interface as a plugin.


 

vCloud Director Login

 

  1. Open a new tab in the browser
  2. Click on the vCD - Tenant1 folder in the bookmarks bar and select vCD - T1 HTML5
  3. Log in as t1admin (password VMware1! )
  4. Click the Log In button

 

 

Initial Tenant UI

 

Notice when you first log in, you only see the default Compute, Network, and Administration options in the left-hand navigation bar.

 

 

SSH to the Tenant App

 

In the taskbar, click the shortcut for PuTTY

 

Scroll down and double-click on tenant-app-01a.corp.local (or select it and click Load, then Open)

It should log in as root. If you need to, enter the password VMware1!

 

 

Install the Plugin

 

Type the following commands:

cd /opt/vmware/plugin

python publish.py -H vcd-01a.corp.local -u 'administrator@system' -p 'VMware1!'

Hint: you can select the commands above and drag and drop them into the PuTTY window in the lab.

 

Note: you may see errors about certificate verification. Those can be ignored.

If it says "published Successfully", you're finished. If not, double-check that you typed the command correctly (try copying and pasting from the manual).

Close the PuTTY window when you're done.

 

 

Reload the Tenant UI

 

Click the Reload icon in the browser window to reload the page

 

 

Operations Manager

 

Notice the new Operations Manager option in the left-hand navigation bar. Click on it to see the Tenant App information in the main screen. Click the Organization button to see the details on the T1 Organization. You can always click on the Home icon at the top to come back to the main page. Scoll down and click on the different objects to navigate the Tenant App in the vCD UI.

 

Conclusion


You should now have a better understanding of vRealize Operations and how you can use it for better operations management as well as adding value to a vCloud Director multi-tenant environment.


 

You've finished Module 3

Congratulations on completing  Module 3.

If you are looking for additional information on vRealize Operations, try one of these:

Proceed to any module below which interests you most.

 

 

 

How to End Lab

 

To end your lab click on the END button.  

 

Module 4 - vRealize Log Insight and vCloud Director (30 minutes)

Introduction


vRealize Log Insight and vCloud Director

VMware vRealize Log Insight gives administrators the ability to consolidate logs, monitor and troubleshoot vSphere and third-party infrastructure, and perform security auditing, compliance testing, log querying, aggregation, correlation, and retention. The vRealize Log Insight virtual appliance includes a syslog server, log consolidation tool, and log analysis tool that will work for any type of device that can send syslog data. vRealize Log Insight administrators can also create custom dashboards based on saved queries that can be exported, shared, and integrated with vCenter Server and VMware vRealize Operations Manager to provide a uniform approach to dashboard monitoring and operational management.

This module includes:

vRealize Log Insight Overview - Learn some of the basics of vRealize Log Insight.

Configuring for vCloud Director - Learn how to configure the vCloud Director Agent in Log Insight

Viewing vCloud Director Log Data - Learn how to view vCloud Director logging data in both the dashboards and Interactive Analytics.


vRealize Log Insight Overview


This lesson will cover an overview of Log Insight and how vCloud Service Providers may benefit from it.


 

Launch Chome Browser

 

If it's not already open, launch the Chrome browser from the Windows Quick Launch taskbar.

 

 

Open vRealize Log Insight

 

Click the vRealize Operations shortcut on the bookmarks bar. Login as:

User name: admin
Password: VMware1!

 

 

 

Navigation

 

When you first log in to vRealize Log Insight, you'll see Dashboards (1) and Interactive Analytics (2) at the top of the window. There's a left-hand navigation pane (3) to help navigate each section. Administration can be accessed in the upper right-hand corner (4).

 

 

Dashboards

 

Dashboards are a quick way to see a graphic representation of the logging data being received by vRealize Log Insight. Some dashboards are built-in (General and vSphere) and some are added by Content Packs. You can even build your own custom dashboards. Click through some of the dashboards to see what kind of logging data we have in the lab (many of the widgets may be empty due to the fact that this is a closed lab environment and there isn't much activity).

 

 

Interactive Analytics

 

Click on the Interactive Analytics tab at the top of the window.

Interactive Analytics is where you can search against all logging data being received by vRealize Log Insight. You can create simply search (1) using alpha-numeric seach strings (things like hostname, IP address, error name or number, etc.). You can add filters (2) to better narrow the search. You can change the timeframe of your search (3). As your search narrows, you can try filtering futher by clicking on the links in the events (4) or by seeing what fields (5) are coming back.

Try searching for some logging data. Some good things to look for might be "error" or "192.168.110.10". If you don't get any results, try changing the time to "All time".

 

 

Doing More with Queries

 

If you create a query that you'd like to use in the future, you can save it by clicking the star icon (1).

You can also use queries to populate charts and graphs in your own custom dashboards (2).

If you'd like to create an alert based on certain logging data, you can click the bell icon (3).

The last icon (4) lets you export or share the query.

 

 

Administration

 

To access the Administration section, click on the three lines in the upper right-hand corner and select Administration.

The Administration section allows you to do things like see status of the vRealize Operations cluster, configure access control, configure agents, etc.

 

 

Content Packs

 

To access the Content Packs section, click on the three lines in the upper right-hand corner and select Content Packs.

The Content Packs section allows you to add new content packs and update existing content packs using the Content Pack Marketplace (this lab doesn't have access to the Internet, so you won't be able to see the Content Pack Marketplace). You can also see which Content Packs are already installed. If you download a Content Pack from the VMware Solution Exchange website, you can import it using the Import Content Pack link at the bottom of the left-hand navigation pane.

 

Configuring for vCloud Director


This section will show how to configure vRealize Log Insight for use with vCloud Director.


 

vCloud Director Content Pack

 

In the Content Pack section, click on the vCloud Director content pack. This is where you can see general information about the content pack. Click the gear icon in the upper right-hand corner and select Setup Instructions...

 

 

Setup Instructions

 

The Setup Instructions explain how to configure the vCloud Director Log Insight Agent (recommended). You can also configure the Log4J Appender using the instructions from the KB article referenced. Click OK when you're done reading.

 

 

Go To Administration

 

Click on the three lines in the upper right-hand corner and select Administration.

 

 

Administration > Agents

 

Click on Agents (1) in the left-hand navigation pane. Then click the All Agents dropdown menu (2) and select vCloud Director Cell Servers (3).

 

 

vCloud Director Agent Settings

 

The vCloud Director Cell Server agent has default settings configured for collecting the right log files from a vCloud Director Cell Server. It needs a filter to know which server(s) to apply those settings to. For our lab, we configured the IP address (1).

When the Log Insight server starts receiving data from the agent, it will show up as an active agent (2).

 

 

Save Agent

 

Scroll down to see the agent settings. Once a change has been made to the filter (like adding an IP address), you can click the Save Agent Group button (1).

Once the agent has been configured, download the Log Insight Agent (2).

Once the agent is downloaded, you can copy it over to your vCloud Director server(s) and install it. Sometimes it takes some work to get the agent working properly. In our lab environment, we had to make changes to the port and ssl settings for the agent to work properly. Those changes were made directly on the vCloud Director server by modifying the .ini file the agent uses.

 

Viewing vCloud Director Log Data


Once the vCloud Director Agent is configured properly and it sending data to Log Insight, you should start to see vCloud Director logging data show up in Interactive Analytics and Dashboards.


 

Interactive Analytics

 

Click on the Interactive Analytics (1) tab and search for the IP address of the vCloud Director server (2):
192.168.110.40

If you don't see any events, you may need to change the time range (3).

 

 

vCloud Director Dashboards

 

Click on the Dashboards (1) tab and select the VMware - vCloud Director (2) dashboards. Click through the different dashboards to see what they look like.

If you don't see any data, you may need to change the time range (3).

Bonus: if you want, you can go to vCloud Director in another browser tab and deploy a new VM or  vApp in T1. Then come back to Log Insight and see what kind of logging data you get.

 

Conclusion


You should now be familiar with the basics of vRealize Log Insight and how to configure it to collect logging data from vCloud Director.


 

You've finished Module 4

Congratulations on completing  Module 4.

If you are looking for additional information on using vRealize Log Insight in a service provider environment, try this whitepaper on architecting a vRealize Log Insight Solution from the vCloud Architecture Toolkit for Service Providers (vCAT-SP):

Proceed to any module below which interests you most.

 

 

 

How to End Lab

 

To end your lab click on the END button.  

 

Module 5 - Usage Meter (30 minutes)

Introduction


Usage Meter is used by VMware Cloud Partners to meter usage of VMware products for monthly billing. This module will show how to configure and use Usage Meter.


Configuration


This lesson will show how to configure Usage Meter to start collecting usage metrics.


 

Assumptions

Usage Meter is distributed as an .ova file, which is a complete virtual machine, or virtual appliance. In this lab, we have already created an IP pool in vCenter,  deployed the Usage Meter virtual appliance, and gone through the initial configuration. We'll go through the steps to configure it after initial deployment of the Usage Meter appliance.

 

 

Log in to vSphere Web Client

If it's not already open, launch the Chrome browser from the Windows Quick Launch taskbar.

 

Log in to the vSphere Web Client as:

User name: administrator@vsphere.local

Password: VMware1!

 

 

 

 

Go to Hosts and Clusters

 

If you're not already in the Hosts and Clusters view, click on the Home icon (1) and select Hosts and Clusters (2). Expand the RegionA01-MGMT01 cluster by clicking on the arrow to the left of it (3).

 

 

 

Open Usage Meter Console

 

Click the usage-01a virtual machine in the left-hand navigation bar (1), then click the console image in the main screen (2) to launch the virtual machine console in a new browser tab.

 

 

Usage Meter Console

 

Note that when you first deploy Usage Meter, you need to log in to the console as root (using the password set during .ova deployment) and run the webpass command to set the password for the web interface. This has already been done for this deployment. You can close the browser tab.

 

 

Log in to Usage Meter

 

Open a new browser tab (1) and click on the vCloud Usage Meter shortcut (2) in the bookmarks bar. Log in (3) as:

User name: admin

Password: VMware1!

 

 

 

Provider Information

 

1. Click the Provider tab.

On initial set up, you need to fill in all fields in the Provider tab (all fields are required) and click Save. This has already been done for the lab.

2. Click the Email tab.

 

 

SMTP Settings

 

A valid SMTP server must be configured and a successful test email needs to be sent before Usage Meter will let you save the Email information. When a successful test email has been sent, you'll see a message near the top of the screen (1). Once the Email section is saved, Usage Meter unlocks the rest of the tabs in the interface. This has already been done for the lab.

Click the Proxy tab (2).

 

 

Proxy Server

 

Depending on the environment, you may need to configure Proxy settings. This is not needed for the lab.

Click the Email Alerts tab.

 

 

Email Alerts

 

Once the SMTP server is successfully configured, you can configure email alerts to notify you of successful and/or failed collections. This is not needed for the lab, so we'll leave it blank.

Click the Products tab.

 

 

Products

 

On initial setup, the Products tab is empty. Note that we have already added all the products for the lab. Typically, you would add vCenter Servers first. If an instance of vRealize Operations is configured to talk to that vCenter Server, the vRealize Operations server information will automatically populate (you would still need to Edit it to accept the certificate). The rest of the products (NSX, vCloud Director, etc.) would need to be added manually. Note that this lab has vCenter Server, vRealize Operations Manager, NSX Manager, and vCloud Director already configured.

Click the Reports tab.

 

 

Reports

 

The Reports section allows you to change the per-VM memory cap and state whether NSX and vRealize Operations should be reported as standalone products instead of being part of a bundle. We will leave these at their default settings.

Click the Collections tab.

 

 

Collections

 

The Collections tab lets you set the minute of the hour when the hourly collections should start. The default setting is 5 minutes past the hour. We will leave the default setting.

Click the API tab.

 

 

API

 

The API tab lets you configure tokens for API use. We are not using the API in this lab.

Click the LDAP tab.

 

 

LDAP

 

The LDAP section lets you configure LDAP authentication for Usage Meter. We are not using LDAP in this lab.

Click the Licenses link near the top of the window.

 

 

Licenses

 

If your vCenter Server(s) are managing licenses for clusters of different uses, you can define which license keys are used for which purposes. You can set them as Demo, Perpetual, or VCPP (1). In this lab, we only have one license key, which is set to VCPP. The License Sets tab (2) allows you to group licenses into sets that are meaningful for reporting purposes. Since we only have one license key, we don't need to do that for this lab.

Click the Automatic Reporting link (3) near the top of the window.

 

 

Automatic Reporting

 

Starting with Usage Meter 3.6, usage reports are automatically generated and sent to VMware. You can also configure vCloud Usage Meter to generate and send reporting sets to yourself, an aggregator, or elsewhere. We will not configure any additional reports in this lab.

Click the Monitor link near the top of the window.

 

 

Monitor

 

The Monitor section shows successes and failures of collection cycles. If any failures occur, they will show up with a link to show more information on the failure.

 

End-User Reporting


End-User Reporting is necessary to properly map VMware Cloud Partner customers to VMware field team resources. This way VMware Field teams can recognize revenue being generated by VMware Cloud Partners. The End-User data is not shared with anyone. It is used on the back-end within VMware to pay VMware Field teams. The only information needed is the customer name, the country, and the postal code.


 

Customers

 

In the Usage Meter web interface, click on the Customers link near the top of the window.

Note that some customers are already defined. These customers have been automatically pulled from vCloud Director. Also note that they're missing Country and Postal Code. You can edit the existing customers, or you can create new customers. You'll need to create new customers if you're not using vCloud Director.

 

 

Edit Existing Customers

 

To edit existing customers, select the checkbox next to the customer name and click the Edit button.

Uncheck the Restricted box, add the Country and Postal Code (use any Country and Postal Code you want to for this lab) and click the Save button.

 

 

Add New Customers

To add a new customer, click the Add button. In a real deployment, you'd use actual customer data, but for the lab purposes, we'll just make it up.

  1. Add the customer Name - Rainpole
  2. Select a Country - pick a Country
  3. Add a Postal Code - 12345
  4. Click the Save button

 

 

 

Rules

 

Rules are the way to map VMs to customers. It is important to note that VMs can only be mapped to one customer at a time. To access the Rules, click the Rules link near the top of the Window.

 

 

Create a Rule

 

To create a rule, select a customer in the Customer dropdown menu. Then go through the Rule Creator and vSphere Inventory to define the rule. Now we'll create a rule mapping a single VM to the Rainpole tenant.

  1. Click on the Customer dropdown menu and select Rainpole.
  2. Set Object Type to VM.
  3. In vSphere Inventory, scroll down and click on util-01a.
  4. The Value field should auto-populate.
  5. Click the Create button.

 

 

Rules List

Click on the Rules List tab to see the rule.

 

 

Reports


Montly Reporting is how VMware Cloud Partners are able to show their montly usage.


 

Reports

 

Click the Reports link near the top of the window. The two most popular reports are the Monthly Usage report and the Customer Montly Usage report.

 

 

Select Monthly Usage Report

 

Click the Report dropdown menu and select Monthly Usage Report (1). Click the Browse button (2).

This report shows usage of bundles and individual products.

Note: due to the nature of the lab not running constantly, like a production environment would, the report may not show much usage. If you run the report for July 2017, you should see a good example of what the report should look like.

 

 

Select Customer Monthly Usage

 

Click the Report dropdown menu and select Customer Monthly Usage (1). Click the Browse button (2).

This report shows a breakdown of customer usage based on the rules configured. Note that the numbers may be different from the Monthly Usage Report because the customer rules typically don't cover all the VMs running in the environment. Also note that the Rainpole user might not show up because the Usage Meter collection cycle probably hasn't run yet since the Rainpole user was configured.

 

Conclusion


You should now have an understanding of how to configure Usage Meter properly for monthly billing.


 

You've finished Module 5

Congratulations on completing  Module 5.

If you are looking for additional information on Usage Meter, go to:

https://www.vmware.com/products/vcloud-usage-meter.html  

Proceed to any module below which interests you most.

 

 

 

How to End Lab

 

To end your lab click on the END button.  

 

Module 6 - vCloud Availability (30 Minutes)

vCloud Availability for vCloud Director


vCloud Availability enables service providers to deliver true Disaster Recovery as a Service, with a focus on streamlining and automating the replication and recovery process.

vCloud Availability for vCloud Director enables service providers to offer simple, cost-effective cloud-based disaster recovery services that seamlessly support their customers’ vSphere environments. This solution is designed expressly for service providers to be easy to operate, to foster customer adoption and growth with a radically simple on-premises installation process, and to enable further monetization of existing vCloud Director multi-tenant cloud environments.


 

vCloud Availability Architecture

 

VMware vSphere Replication is the underlying replication technology that is used by vCloud Availability for vCloud Director. vSphere Replication provides a hypervisor-based, asynchronous replication of virtual machines, independent from the underlying storage hardware, which is essential for replications to and from the public cloud with disparate hardware used.

The vSphere Replication Agent is built into the VMware ESXiTM hypervisor, and with the help of the vSCSI filter, tracks block changes to virtual disks (VMDKs) of running virtual machines. Depending on the required RPO, the hypervisor then transmits the changed blocks in regular intervals to the target environment.

 

 

vCloud Availability Portal

 

The vCloud Availability for vCloud Director portal is a virtual appliance that provides a graphical user interface for tenants to manage their replications when they have no access to their on- premises vSphere Web Client user interface.

 

 

vCloud Availability Hands-On

This module utilizes interactive simulations to show how to:

 

Hands-on Labs Interactive Simulation: vCloud Availability for vCloud Director


The interactive simulation will allow you to experience steps which are too time-consuming or resource intensive to do live in the lab environment.

  1. Use the links below to open the interactive simulations. It will open in a new browser window or tab.
  2. When finished, click the “Return to the lab” link to continue with this lab.

Set up vSphere Replication: http://docs.hol.vmware.com/hol-isim/HOL-2018/hol-1883-01-vspherereplication.htm

Run a Test: http://docs.hol.vmware.com/hol-isim/HOL-2018/hol-1883-01-runtest.htm

Failover: http://docs.hol.vmware.com/hol-isim/HOL-2018/hol-1883-01-failover.htm

Reverse/Failback: http://docs.hol.vmware.com/hol-isim/HOL-2018/hol-1883-01-failback.htm

 


Conclusion


You should now have an understanding of how to configure and use vSphere Replication with vCloud Availability.


 

You've finished Module 6

Congratulations on completing  Module 6.

If you are looking for additional information on vCloud Availability, go to:

https://cloudsolutions.vmware.com/products/vcloud-availability

Proceed to any module below which interests you most.

 

 

 

How to End Lab

 

To end your lab click on the END button.  

 

Conclusion

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

Lab SKU: HOL-1883-02-HBD

Version: 20180406-145050