Hol 1983 01 HBD - PDF - en

HOL-1983-01-HBD
Table of Contents
Lab Overview - HOL-1983-01-HBD - VMware Cloud Provider Program - vCloud Director
for Service Providers ......................................................................................................... 2
Lab Guidance .......................................................................................................... 3
Module 1 - Introduction to vCloud Director (30 minutes) .................................................. 9
Introduction........................................................................................................... 10
Introduction to vCloud Director ............................................................................. 11
Mapping vSphere Resources to vCloud Director.................................................... 16
vCloud Director Networking with NSX ................................................................... 46
Conclusion............................................................................................................. 58
Module 2 - vCloud Director Consumption (30 minutes) .................................................. 59
Introduction........................................................................................................... 60
Multi-tenancy in vCloud Director ........................................................................... 61
Creating a vApp .................................................................................................... 74
Deploy vApp from Catalog .................................................................................... 84
Conclusion............................................................................................................. 92
Module 3 - What’s New in vCloud Director 9.1 (60 minutes)........................................... 93
Introduction........................................................................................................... 94
What's New in vCD v9.1 ........................................................................................ 95
Enhanced User Interface ..................................................................................... 104
Configuring Multisite ........................................................................................... 125
vRealize Orchestrator Integration ....................................................................... 139
Conclusion........................................................................................................... 155
HOL-1983-01-HBD Page 1
HOL-1983-01-HBD
Lab Overview -
HOL-1983-01-HBD -
VMware Cloud Provider
Program - vCloud Director
for Service Providers
HOL-1983-01-HBD
Lab Guidance
Note: 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 users.
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 from an administrative perspective as well as
from a user perspective.
Lab Module List:
• Module 1 - Introduction to vCloud Director (30 minutes) (Basic) This module

will provide an overview of vCloud Director, its use cases and various objects
involved.
• Module 2 - vCloud Director Consumption (30 minutes) (Basic) This module
will illustrate multi-tenancy within vCD and step you through creating vApps and
catalog deployment.
• Module 3 - What's New in vCloud Director 9.1 (60 minutes) (Basic) This
module introduces vCloud Director 9.1 and explores the enhanced HTML5 user
interface and new features.
Lab Captain:
• Eric Stine, Staff Systems Engineer, USA
This lab manual can be downloaded from the Hands-on Labs Document site found here:
http://docs.hol.vmware.com
HOL-1983-01-HBD
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.
HOL-1983-01-HBD
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.
HOL-1983-01-HBD
Click once in active console window
In this example, you will use the Online Keyboard to enter the "@" sign used in email
addresses. The "@" sign is Shift-2 on US keyboard layouts.
1. Click once in the active console window.

2. Click on the Shift key.
Click on the @ key
1. Click on the "@ key".
Notice the @ sign entered in the active console window.
HOL-1983-01-HBD
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
HOL-1983-01-HBD
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.
HOL-1983-01-HBD
Module 1 - Introduction to
vCloud Director (30
minutes)
HOL-1983-01-HBD
Introduction
This Module contains the following lessons:
• Introduction to vCloud Director

• Mapping vSphere Resources to vCloud Director
• vCloud Director Networking with NSX
HOL-1983-01-HBD
Introduction to vCloud Director

VMware vCloud Director enables VMware Cloud Providers to build differentiated cloud
services that are inherently hybrid-aware and ideal for enterprise-class organizations. It
is available through the VMware Cloud Provider Program.
vCloud Director Login
If you have not already done so, log in to vCloud Director
1. Open Chrome by double clicking the icon on the desktop or by clicking the button
on the taskbar
2. Select the vCDa-Admin bookmark link from the vCD-Admin folder in the
bookmark toolbar. This will bring you to the vCloud Director login screen
3. Enter user name Administrator
4. Enter password VMware1!
5. Click Login
Note: if you get a message asking to open vmware-csd.exe, click Cancel.
HOL-1983-01-HBD
Complete Software-Defined Services as Virtual Data

Centers
VMware vCloud Director is a software product that provides the ability to build secure,
multi-tenant clouds by pooling virtual infrastructure resources into virtual datacenters
and exposing them to users through Web-based portals and programmatic interfaces as
a fully-automated, catalog-based service.
Terminology and Architecture Overview
vSphere Resources
vCloud Director relies on vSphere resources to provide CPU and memory to run virtual
machines. In addition, vSphere datastores provide storage for virtual machine files and
other files necessary for virtual machine operations. vCloud Director also utilizes
vSphere distributed switches and vSphere port groups to support virtual machine
networking. You can use these underlying vSphere resources to create cloud resources.
Cloud Resources
Cloud resources are an abstraction of their underlying vSphere resources. They provide
the compute and memory resources for vCloud Director virtual machines and vApps. A
vApp is a virtual system that contains one or more individual virtual machines, along
with parameters that define operational details. Cloud resources also provide access to
storage and network connectivity. Cloud resources include provider and organization
virtual datacenters, external networks, organization virtual datacenter networks, and
network pools. Before you can add cloud resources to vCloud Director, you must add
vSphere resources.
Provider Virtual Datacenters
A provider virtual datacenter combines the compute and memory resources of a single
vCenter Server resource pool with the storage resources of one or more datastores
available to that resource pool. You can create multiple provider virtual datacenters for
users in different geographic locations or business units, or for users with different
performance requirements.
Organizations
vCloud Director supports multi-tenancy through the use of organizations. An

organization is a unit of administration for a collection of users, groups, and computing
resources. Users authenticate at the organization level, supplying credentials
established by an organization administrator when the user was created or imported.
System administrators create and provision organizations, while organization
administrators manage organization users, groups, and catalogs.
Organization Virtual Datacenters
HOL-1983-01-HBD
An organization virtual datacenter provides resources to an organization and is

partitioned from a provider virtual datacenter. Organization virtual datacenters provide
an environment where virtual systems can be stored, deployed, and operated. They also
provide storage for virtual media, such as floppy disks and CD ROMs. A single
organization can have multiple organization virtual datacenters.
Exploring vCloud Director
When you first log in to vCloud Director, you start in the Home portion of the System
tab. Note the Guided Tasks section with a number of links to help give shortcuts to
common tasks. There is also a Guided Tasks section below that has links to take you
directly to whatever section of vCloud Director you may want to go. In order to show
how to navigate the user interface, we won't use those shortcuts right now.
1. Click on the Manage & Monitor button
View Organizations
HOL-1983-01-HBD
Within Organizations, There are 2 tenants listed, Tenant 1 (T1) and Tenant 2 (T2).
There is also a Public tenant. The Public tenant contains templates that both tenants
can access.
Open the T1 Tenant
1. Double Click on the Org name T1 to open a new tab within the Admin interface
2. In the T1 Org click on the Open hyperlink within T1-vApp1
HOL-1983-01-HBD
View vApp Architecture
Note the workloads T1-tclinux-01a and T1-tclinux-02a that are running for T1
(Tenant 1). Also, take note of the internal network T1-vApp1-net that these workloads
are connected to. T1-vApp1-net is also routed out to the external T1-OrgNet-Rtd
network.
You can go back to the System tab and open up T2 (Tenant 2), then Open the
T2-vApp1. Note the single workload in Tenant 2 as well as different network segments
as compared to what we viewed in Tenant 1.
HOL-1983-01-HBD
Mapping vSphere Resources to vCloud

Director
A new tenant has just signed up with your service. They have requested that they want
to put their workloads in a Pay-As-You-Go resource. We will need to create a new
Provider VDC and Org VDC for this Pay-As-You-Go service. Let us walk through the steps
to get the resources in place and then setup the new Tenant 3 with their new service.
Create a New Environment for Tenant3
1. Click on the System tab to return to the Admin Manage & Monitor page.
HOL-1983-01-HBD
Setup a Bronze Provider VDC
1. Ensure you are on the Manage & Monitor view

2. Choose Provider VDCs
3. Click on the green Plus button to create a new Provider VDC
HOL-1983-01-HBD
Name the New Provider VDC
Because we already have Gold and Silver PVDCs, we will name this one Bronze (we
already have a Bronze Resource Pool to map it to in the next step).
1. Type Bronze-PVDC into the Name field

2. Verify there is a checkmark in the Enabled box
3. Click Next
HOL-1983-01-HBD
Select Resource Pool
It is generally considered best practice to map Provider VDCs to Clusters in vSphere, but
you can map them to Resource Pools as well. Due to the limited resources within this lab
environment, we are mapping PVDCs to Resource Pools.
1. Select the vCenter instance named vcsa-01a

2. Select the Resource Pool named Bronze
3. Click on the Next
HOL-1983-01-HBD
Add a Storage Policy
vCloud Director uses storage from vSphere by mapping storage policies to PVDCs. If you
want to map specific storage to specific PVDCs, you would create a storage policy in
vSphere that uses that storage. In this screen, you see what storage policies we already
have defined in vSphere.
1. Select one of the storage policies - pick one other than *(Any)
2. Click on the Add button
3. Click on Next
HOL-1983-01-HBD
Configure VXLAN Network Pool
You can create specific VXLAN Network Pools for PVDCs ahead of time, or you can just
let vCloud Director create the VXLAN Network Pool for you. For this lab, we're going to
let vCloud Director create a VXLAN Network Pool for us.
Click Next.
HOL-1983-01-HBD
Select Virtual Hardware Version
You can define the highest virtual hardware version you want to be supported by the
PVDC. This is useful if you have different or older versions of ESXi running on the hosts
providing resources to the PVDC. For this lab, we will leave it at Hardware Version 13.
Click Next.
HOL-1983-01-HBD
Review Ready to Complete
Review the Ready to Complete page and click Finish.
Verify Bronze-PVDC Creation
HOL-1983-01-HBD
Verify the Bronze-PVDC has been created and the status has a green checkmark. Let us
continue the setup and create a new Org for Tenant 3.
Setup a New Tenant3 Organization
1. Select Organizations
2. Click on the New Organization... button (Green Plus sign)
HOL-1983-01-HBD
Name T3 Organization
1. In the Organization name field, type in T3

2. Type Tenant3 in the Organization full name field
3. Click Next
HOL-1983-01-HBD
LDAP Options
Verify Do not use LDAP is selected and Click Next
HOL-1983-01-HBD
Add Local User
1. Click on the Add... button

2. Type in t3admin in the User name field
3. Type in VMware1! into the Password fields
4. Ensure that there is a checkmark in the Enable box
5. Choose Organization Administrator from the dropdown menu
6. Click on OK
HOL-1983-01-HBD
Verify Account Creation
Verify the t3admin account has been created and click Next
HOL-1983-01-HBD
Catalog Options
In a traditional deployment of vCloud Director, you may want to allow tenants to

publish, share, or subscribe to catalogs. For this tenant, we will leave these unchecked.
Click Next
HOL-1983-01-HBD
Email Preferences
Normally, you would probably want to configure email settings and notifications for your
tenants. For this lab, however, we will not.
Click Next
HOL-1983-01-HBD
Policies
Normally, when you create Organizations, you would configure lease times and quota
limits based on your requirements. For this lab, we will leave the defaults.
Click Next
HOL-1983-01-HBD
Review Ready to Complete
Review the Ready to Complete screen and click Finish
Verify T3 Creation
Verify that Tenant3 (T3) is now listed in Organizations
HOL-1983-01-HBD
Setup Organization VDC for Tenant3 and Pay-As-You-Go

Allocation Model
1. Click on Organization VDCs

2. Click on New Organization VDC... (Green Plus button)
HOL-1983-01-HBD
Select Organization
1. Select T3 from the Organization list

2. Click Next
HOL-1983-01-HBD
Select Provider VDC
1. Select Bronze-PVDC from the list

2. Click Next
HOL-1983-01-HBD
Select Allocation Model
Read the descriptions of the different Allocation Models to understand what options are
available for Organization VDCs.
1. Select Pay-As-You-Go as the Allocation Model.

2. Click Next.
HOL-1983-01-HBD
Configure Pay-As-You-Go Model
Normally, based on your own requirements, you would configure quotas and limits when
you create Organization VDCs. For this lab, however, we will leave the default settings.
Keep the defaults and click Next
HOL-1983-01-HBD
Storage Allocation
1. Select the storage policy (it should be the same one you selected when creating
the PVDC)
3. Place a checkmark in the Enable thin provisioning box
4. Click Next
HOL-1983-01-HBD
Network Pool Selection
1. Choose Bronze-PVDC-VXLAN-NP from the Network pool dropdown

2. Click Next
HOL-1983-01-HBD
Configure Edge Gateway
1. Place a check in the box to create a new edge gateway

2. Type in T3-ESG for the name
3. Read through the different options you have when creating an Edge Gateway
through vCloud Director. Leave the default settings.
4. Click Next
HOL-1983-01-HBD
Configure External Networks
1. Select External_Network
3. Click Next
HOL-1983-01-HBD
Configure Default Gateway
1. Select External_Network
2. Select 192.168.100.1
3. Place a checkmark in the Use default gateway for DNS Relay box
4. Click Next
HOL-1983-01-HBD
Create Organization VDC Network
1. Place a checkmark in the Create a network for this virtual datacenter...

box
2. Type in T3-OrgNet-Ext for the Network name
3. You can share Organization VDC Networks with other Organization VDCs that this
Organization has access to. This is useful for allowing network connectivity
between VMs running in different Organization VDCs. For this lab, we will leave
the box unchecked.
4. Enter 192.168.200.1 for the Gateway address
5. Enter a subnet mask of 255.255.255.0
6. Click Next
HOL-1983-01-HBD
Enter Name for Organization VDC
1. Type in T3-OVDC into the Name field

2. Click Next
HOL-1983-01-HBD
Review and Finish
Verify the information in the Ready to Complete screen. Click Finish
Verify T3-OVDC Creation
We have just successfully created a new Bronze resource for Tenant3 with a Pay-As-You-
Go allocation model (note: it may take a few minutes to create the new OVDC). The
t3admin can now review the VMware vCloud Director User's Guide, which will provide
information about managing organizations, catalogs, vApps, and virtual machines. In
the next lesson, we will explore vCloud Director Networking with NSX.
HOL-1983-01-HBD
vCloud Director Networking with NSX

This module provides an overview of the networking and security aspects of VMware
vCloud Director, and explains the types of networks and network pools with NSX that
are available in vCloud Director.
Providing Infrastructure-as-a-Service (IaaS) 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:
• vApp network
• External network
• Organization VDC network
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.
HOL-1983-01-HBD
vCD Networking with NSX
Earlier in this module, we showed the vApp networking. In vCloud Director, you can
create a vApp Network within the vApp. You can also create Org Networks in the Org
VDCs. In the image above you can see a vApp network (T1-vApp1-Net) and an Org
network (T1-OrgNet-Rtd). When these virtual networks are created in vCloud Director,
NSX automatically deploys VXLANs for those networks. Notice the firewall icon
connecting the vApp network to the Org network. When vApp networks are connected
to external networks in vCloud Director, NSX automatically deploys an Edge to provide
routing between the two networks (as well as Firewall, NAT, and DHCP services to the
vApp network).
HOL-1983-01-HBD
Manage the Edge
In addition to the Edges that automatically get deployed with vApps, you can also
deploy Edge Services Gateways in the Org VDC to provide Edge services to the Org VDC
networks. 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
HOL-1983-01-HBD
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...
HOL-1983-01-HBD
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
HOL-1983-01-HBD
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
HOL-1983-01-HBD
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
◦ Note the Convert to Advanced Gateway option is no longer there. This
Edge Gateway has already been upgraded.
4. Click on Edge Gateway Services...
HOL-1983-01-HBD
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 Distributed Logical Router.
Distributed Logical Router
The DLR is optimized for forwarding in the logical space between VMs, on VXLAN-backed
or VLAN-backed portgroups.
The DLR has the following properties:
• High performance, low overhead first-hop routing

• Scales linearly with the number of hosts
• Supports 8-way ECMP on uplink
• Up to 1,000 DLR instances per host
HOL-1983-01-HBD
• Up to 999 logical interfaces (LIFs) on each DLR (8 x uplink + 991 internal) + 1 x

management
• Up to 10,000 LIFs per host distributed across all DLR instances (not enforced by
NSX Manager)
Keep in mind the following caveats:
• Cannot connect more than one DLR to any given VLAN or VXLAN.
• Cannot run more than one routing protocol on each DLR.
• If OSPF is used, cannot run it on more than one DLR uplink.
• To route between VXLAN and VLAN, the transport zone must span single DVS.
The DLR’s design at a high level is analogous to a modular router chassis, in the
following ways:
• ESXi hosts are like line cards:

◦ They have ports with connected end stations (VMs).
◦ This is where the forwarding decisions are made.
• The DLR Control VM is like a Route Processor Engine:

◦ It runs dynamic routing protocols to exchange routing information with the
rest of the network.
◦ It computes forwarding tables for “line cards” based on the configuration
of interfaces, static routes, and dynamic routing information.
◦ It programs these forwarding tables into the “line cards” (via the Controller
Cluster, to enable scale and resiliency).
• The physical network connecting ESXi hosts together is like a backplane:

◦ It carries VLAN-encapsulated or VXLAN-encapsulated data between the
“line cards.”
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.
HOL-1983-01-HBD
Enable Distributed Routing
1. Click on the Edge Gateways tab

2. Right-click on the T1-ESG
3. Select Enable Distributed Routing
Click Yes on the popup window.
1. Wait for the Status to go green again.
HOL-1983-01-HBD
2. Then notice the green checkmark in the Distributed Routing column.
Next, we will take a look at the Distributed Firewall.
Distributed Firewall
NSX Distributed Firewall is a hypervisor kernel-embedded firewall that provides visibility

and control for virtualized workloads and networks. In a traditional vSphere deployment
with NSX, you can create access control policies based on VMware vCenter objects like
datacenters and clusters, virtual machine names and tags, network constructs such as
IP/VLAN/VXLAN addresses, as well as user group identity from Active Directory.
However, when used only with vCenter, the NSX Distributed Firewall is typically used in
a dedicated (or single-tenant) deployment. When used with vCloud Director, each
tenant has control of their own firewall rules and can create access control policies
based on objects they have visibility to through vCloud Director (like OVDCs, OVDC
Networks, VMs, etc.)
Consistent access control policy is now enforced when a virtual machine gets vMotioned
across physical hosts without the need to rewrite firewall rules. Since Distributed
Firewall is hypervisor-embedded, it delivers close to line rate throughput to enable
higher workload consolidation on physical servers. The distributed nature of the firewall
provides a scale-out architecture that automatically extends firewall capacity when
additional hosts are added to a datacenter.
Manage Firewall
1. Go back to the T1 Administration tab

2. Click on Virtual Datacenters
3. Select T1-OVDC
HOL-1983-01-HBD
4. Click on the Actions button

5. Select Manage Firewall...
Distributed Firewall Rules
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. Play with creating rules or editing the Source or Destination of the default rule to
see what objects are available for firewall rules.
3. Close the browser tab when you're finished
HOL-1983-01-HBD
Conclusion
In this Module, we stepped through a basic Introduction to vCloud Director.
We then walked through setting up a New Organization with a Pay-As-You-Go
Allocation Model. We then looked at managing vCloud Director Networking
with NSX.
You've finished Module 1
Congratulations on completing Module 1.
For more information on vCloud Director, click the following link:
• https://www.vmware.com/products/vcloud-director.html
Proceed to any module below which interests you most.
• Module 2 - vCloud Director Consumption (30 minutes) (Basic)

• Module 3 - What's New in vCloud Director 9.1 (60 minutes) (Basic)
How to End Lab
To end your lab click on the END button.
HOL-1983-01-HBD
Module 2 - vCloud
Director Consumption (30
minutes)
HOL-1983-01-HBD
Introduction
• Multi-tenancy in vCloud Director

• Create a vApp Within a Tenant
• Deploy a vApp from a Catalog to a Tenant
HOL-1983-01-HBD
Multi-tenancy in vCloud Director

vCloud Director categorizes users into organizations that can represent any policy
group, such as a business unit, division, or company. Each will have isolated virtual
resources, independent role based authentication and specific policy controls. These
features enable secure and robust multi-tenancy and safe sharing of infrastructure
resources. vCloud Director supports multi-tenancy through the use of organizations. We
will continue and illustrate Multi-tenancy in vCloud Director.
vCloud Director Login
If you have not already done so, log in to vCloud Director
1. Open Chrome by double clicking the icon on the desktop or by clicking the button
on the taskbar
2. Select the vCDa-Admin bookmark link from the vCD-Admin folder in the
bookmark toolbar. This will bring you to the vCloud Director login screen
5. Click Login
HOL-1983-01-HBD
Navigate to Organizations
1. Click on Manage & Monitor

2. Click Organizations
We can see we have two tenants listed, T1 and T2. Next, we will log into these
environments to help us illustrate multi-tenancy.
Login as Different Tenants
From the open Chrome browser:
HOL-1983-01-HBD
1. Click the Customize and Control button to the right of the address bar
2. Select New incognito window
Log into vCD - Tenant1
1. Click the vCD - Tenant1 folder in the bookmarks bar and select vCD - T1 Flex
2. Type in the user name of t1admin
3. Type in a password of VMware1!
4. Click Login
HOL-1983-01-HBD
Note: if you get a message saying vCloud Director requires Adobe Flash Player, click the
link (1) and click Allow (2). If you get a message asking to open vmware-csd.exe, click
Cancel.
HOL-1983-01-HBD
Open T1-vApp
1. Click on Open hyperlink to view the vApp Diagram of T1-vApp1
HOL-1983-01-HBD
Tenant 1 Workloads
Take note of the workloads that are running in Tenant1. There are two virtual machines
connected to the T1-vApp1-net, which is the internal network for this vApp. The
T1-vApp1-net network is then connected to an external network named T1-OrgNet-Rtd.
Let us compare this to Tenant2 to further illustrate multi-tenancy in vCloud Director.
Log out of Tenant 1.
HOL-1983-01-HBD
We will now login as Tenant2 admin
4. Click Login
HOL-1983-01-HBD
Open T2-vApp
1. Click on Open hyperlink to view the vApp Diagram of T2-vApp1
HOL-1983-01-HBD
Tenant2 Workload
Take note of the single workload that is running in Tenant2. The single virtual machine
is connected directly to an external network named T2-OrgNet-Ext. The T2 Organization
Network is isolated from the networks we viewed in Tenant1.
Now let us take a look at how vCloud Director works with NSX to automatically deploy
the networking components needed to keep the tenant networking separate.
HOL-1983-01-HBD
Open New Window
1. Click the Customize and Control button to the right of the address bar
2. Select New window
Note: Make sure you select "New window". DO NOT open a new Incognito window (or
you might get weird flash errors in the next section).
Open Region A vCenter Bookmark
1. Click on vSphere Client in the bookmark bar

2. Select the RegionA vCenter bookmark
Note: if you get a message asking to open vmware-cip-launcher.exe, click Cancel.
HOL-1983-01-HBD
Administrator Login
Log in to the vSphere Web Client as:
User name: administrator@vsphere.local
Password: VMware1!
Note: it may take a few minutes
Navigate to Network & Security
1. Hover over or click the Home dropdown

2. Select Networking & Security
HOL-1983-01-HBD
Transport Zones
1. Select Installation and Upgrade

2. Select the Logical Network Preparation tab
3. Select the Transport Zones button
4. vCloud Director used NSX to automatically create transport zones for the PVDCs.
Logical Switches
1. Select Logical Switches

2. vCloud Director used NSX to create separate logical switches (VXLANs) for each
virtual network deployed.
HOL-1983-01-HBD
NSX Edges
1. Select NSX Edges

2. vCloud Director used NSX to automatically deploy these appliances. T1-ESG and
T1-vApp1-net were deployed for Tenant1. T2-ESG was deployed for Tenant2.
Close browser windows
1. Right-click on each one of the browser windows and

2. Select Close window
HOL-1983-01-HBD
Creating a vApp
In this lesson, we will build a new vApp in vCloud Director. The purpose of this activity is
to show you how to deploy virtual machines.
Log into Tenant1
1. Open the Chrome browser

5. Click Login
HOL-1983-01-HBD
Note: if you get a message saying vCloud Director requires Adobe Flash Player, click the
link (1) and click Allow (2). If you get a message asking to open vmware-csd.exe, click
Cancel.
HOL-1983-01-HBD
Build New vApp
Click the Build New vApp option
HOL-1983-01-HBD
Name New vApp
1. Type in T1-Build-New-vApp in the Name field

2. Click Next
HOL-1983-01-HBD
Add Virtual Machines
1. Choose the Public Catalogs from the dropdown. We have 3 base virtual
machine builds to choose from.
2. Choose the tclinux-base virtual machine
4. Click Next
HOL-1983-01-HBD
Select Storage Policies
We will keep the default Storage Policy. Click Next
HOL-1983-01-HBD
Configure Virtual Machines
1. Choose T1-OrgNet-Rtd from the Network dropdown

2. Choose Static - IP Pool from the IP Assignment dropdown
3. Click Next
HOL-1983-01-HBD
Configure Networking
1. Place a checkmark in the box to Fence vApp. This will allow identical VMs in
different vApps to be powered on without MAC and IP conflicts.
2. Click Next
HOL-1983-01-HBD
Review and Finish
Review the Ready to Complete page and click Finish
HOL-1983-01-HBD
Verify New vApp
The newly created vApp will eventually have a status of Stopped. Feel free to click on
the Open hyperlink for this new vApp to view the vApp Diagram and other settings.
Let us take a look at deploying a vApp from a catalog in the next lesson.
HOL-1983-01-HBD
Deploy vApp from Catalog

Let us now learn how to build a new vApp in vCloud Director from an existing catalog.
Add vApp from Catalog
1. In the same Tenant1 administration page, Click the Home button

2. Click Add vApp from Catalog
HOL-1983-01-HBD
Select vApp Template
1. Choose Public Catalogs from the dropdown

2. Select the tclinux-base golden image
3. Click Next
HOL-1983-01-HBD
Name the New vApp
1. Type T1-Catalog-vApp for the Name

2. Click Next
HOL-1983-01-HBD
Select Storage Policy
1. Choose the vSAN HOL Policy from the Storage Policy dropdown
2. Click Next
HOL-1983-01-HBD
Configure Networking
1. Connect NIC 0 by choosing the T1-OrgNet-Rtd network from the Networks

dropdown
2. Click Next
HOL-1983-01-HBD
Customize Hardware
Click Next
HOL-1983-01-HBD
Review and Finish
1. Place a checkmark in the Power on vApp after this wizard is finished

2. Click Finish
Verify New vApp
HOL-1983-01-HBD
After a few minutes, the newly created vApp that we deployed from the catalog will
have a status of Running. Feel free to click on the Open hyperlink to view the vApp
Diagram and other settings.
HOL-1983-01-HBD
Conclusion
In this Module, you learned how vCloud Director builds out a Multi-tenant
service. We created a new vApp as well as deployed a vApp from a Catalog.
• Module 1 - Introduction to vCloud Director (30 minutes) (Basic)

• Module 3 - What's New in vCloud Director 9.1 (60 minutes) (Basic)
How to End Lab
HOL-1983-01-HBD
Module 3 - What’s New in

vCloud Director 9.1 (60
minutes)
HOL-1983-01-HBD
Introduction
• What's New in vCD v9.1

• Enhanced User Interface
• Configuring Multisite
• vRealize Orchestrator Integration
HOL-1983-01-HBD
What's New in vCD v9.1

The release of vCloud Director v9.1 introduced some new features to the platform. Let's
go through them.
Overview
VMware vCloud Director (vCD) is the central Cloud Management and Orchestration
platform within the VMware Cloud Provider Platform, enabling Service Providers to
orchestrate the provisioning of software defined, modular, and ready for consumption
Virtual Data Centers in a matter of minutes.
Version 9.1 of vCD adds features that leverage the features of server virtualization
capabilities of VMware vSphere and the Software Defined Data Center (SDDC)
functionality to offer Service Providers with a powerful platform for delivering
Infrastructure as a Service (IaaS) solutions.
vCloud Director 9.1 features include:
• HTML 5 Tenant and Administration Portals

• User Interface Extensibility
• Orchestration Services
• Python SDK and CLI
• Multi-Site View
• SR-IOV (Single-Root Input/Output Virtualization)
• FIPS Mode
HOL-1983-01-HBD
• Standalone VMRC
Enhanced Tenant Portal
With the vCloud Director 9.1 release, a new enhanced tenant portal view has been
included. This gives consumers of the IaaS cloud offering access to a new dashboard,
with vAPP and catalog management capabilities. This enhanced portal provides native
OVF/OVA upload and download built-in without the need for browser extensions. The
final feature of the enhanced tenant portal is the stand alone VMRC for console access,
which replaces the current Client Integration plugin, greatly enhancing the tenant/
consumer experience of the IaaS offering.
VMware vCloud Director 9.1 includes a dedicated HTML 5 provider portal where
administrators of the IaaS environment can manage all the system resources and
configurations of vCloud Director from an easy to access web portal. In previous
versions of vCD, the provider portal was provided using Flex within a web browser. This
could become problematic and was not suitable for long term management of a cloud
platform. The HTML 5 Provider Portal is easily adoptable due to its consistency with web
standards. In this release a new organization management provides further tenant
administration capabilities. The FLEX administrator portal is still available for in-depth
configuration requirements.
HOL-1983-01-HBD
Standalone VMRC
VMware vCloud Director provides the capabilities to access virtual machine consoles
from within the tenant and provider portals. This allows the user or the administrator of
the service the ability to manage and control the virtual machine guest operating
system. In vCloud Director 9.0, the tenant portal supports HTML VM console with built-in
support from modern browsers. vCloud Director 9.1 now adds support for standalone
VMware Remote Console. Standalone VMRC provides more functions such as broader
keyboard input types. This significantly improves access to the Virtual Machine consoles
and gives greater flexibility over accessing the Virtual Machines. Please note that
vSphere Client Integration Plugin is not supported on HTML5 tenant portal.
HOL-1983-01-HBD
User Interface Extensibility
VMware vCloud Director 9.1 includes the capability to allow a Cloud Provider to extend
the Tenant Portal with third party plugins with a pluggable framework. As an example,
this allows a service provider to build into the IaaS offering the ability to create tickets
on demand from consumers using the offering. UI extensibility SDK and documentation
will be published so that ISVs, cloud providers or system integrators can integrate third
party UIs into vCloud Director. In the screen shot below you can see an example how a
ticketing system developed in-house by the cloud provider can be incorporated into the
single pane of glass with the vCloud Director tenant portal.
If you would like to see this feature in action, the vRealize Operations module in
HOL-1983-02 walks you adding the vRealize Operations Tenant App plug-in to vCloud
Director.
HOL-1983-01-HBD
Multi-site Management View
This aggregate view provides a view of the entire cloud environment, with intuitive
navigation across sites as well as virtual data centers. Built into this view is a new
enhanced search allowing for service providers to easily find objects and resources,
providing improved cloud resource navigation, and giving a quick glimpse into the state
of the cloud environment.
We will walk through how a tenant can add a secondary Organization VDC later in this
module.
Extensibility
VMware vCloud Director 9.1 new features provide greater focus on the devops
requirements of a service provider. A service provider can now rapidly deploy IT services
HOL-1983-01-HBD
with SDK and programmatic interfaces, attracting tenant programmers to build custom
experiences for users, while retaining control and preserve compliance with an open and
consistent environment.
Some examples of vCloud Director's greater extensibility include the new Python SDK
and CLI, updated vRealize Orchestrator plug-in, and Container Service Extension.
Python SDK and CLI
VMware vCloud Director 9.1 now includes SDK automation with Python. The vCloud
Director Command Line Interface (CLI) allows system administrators and tenants to
perform operations from the command line with full support for the Service Provider
administrators and the tenant operations from consumers of the IaaS offering. The
following URLs can be used to retrieve sample scripts and examples:
• Python SDK https://vmware.github.io/pyvcloud/

• vCloud Director CLI https://vmware.github.io/vcd-cli/
The new vcd-cli allows systems administrators and tenants to perform operations from
the command line with full support for service provider and tenant operations. This
provides simplified vCD integration, while offering operational convenience through
automation. An Open source SDK and CLI have been designed to quickly incorporate
contributions and fixes from VMware and other third-party vendors.

HOL-1983-01-HBD
Container Service Extension
The container-service-extension (CSE) is an add-on to VMware vCloud Director that

helps tenants work with Kubernetes clusters.
CSE enables Kubernetes as a service on vCloud Director (vCD) installations. CSE is

based on VM templates that are automatically generated during the installation process,
or anytime thereafter. vCD tenants can then request fully functional Kubernetes clusters
that CSE instantiate on the tenant VDC from the templates, customized based on the
tenant preferences.
More information can be found here:

https://vmware.github.io/container-service-extension/
vRealize Orchestrator Plug-In for vCloud Director
Cloud Providers can leverage the library of pre-designed vRO workflows to build and
deploy custom vCD workflows (both SP and tenant facing) that automate and
orchestrate many of the SP admin and tenant tasks in vCD (such vRO workflows can be

HOL-1983-01-HBD
executed in the security context of a given user, either CSP or tenant level). Enabling
access to vCD tasks through vRO workflows makes the platform more appealing and
flexible, by providing more automation and orchestration options into the VMware
Cloud Platform.
The VMware vRealize Orchestrator plug-in for vCloud Director 9.1 release runs on
VMware vRealize Orchestrator 7.x. The plug-in is compatible with VMware vCloud
Director 9.1 and introduces various new workflows designed to cover the NSX-based
networking components that are available in vCloud Director. With these workflows, you
can manage first-entity networking configuration objects, such as Firewall, NAT, DHCP
pools, DHCP bindings, and Certificates. You can create, edit, or delete instances of these
objects. The plug-in also includes workflows for managing advanced gateways and
legacy gateways.
Service Integration

HOL-1983-01-HBD
vCloud Director 9.1 Service Integration empowers administrators to quickly allow

administrators to create workflows using vRealize Orchestrator which can then be easily
published within vCloud Director. When workflows are designed the designer can create
any parameters that are needed to run the workflow and vCloud Director will natively
render these to the service consumer. This can be a simple input box for data input or
complex scenarios like presenting a list of virtual machines.
We will walk through adding a new service later in this module.

HOL-1983-01-HBD
Enhanced User Interface

One of the biggest new features in vCloud Director v9.1 is the new HTML5 Tenant UI.
Let's take a look at it.
1. If you haven't already done so, launch Chrome from the shortcut on the desktop
or in the taskbar.
2. Click the vCD - Tenant1 folder in the bookmarks bar and select vCD - T1
HTML5
5. Click Login

HOL-1983-01-HBD
New User Interface
1. Note how the new HTML5 Tenant UI differs from the older Flex UI. You can switch
between Datacenters, Libraries, and Administration using the drop-down menu
off of the three lines at the top (sometimes called the "hamburger menu") (1). By
default, you start in the Datacenters section with Virtual Machines highlighted.
Notice how you can now navigate between vApps, Virtual Machines, Network,
Edges, and Security all from the left-hand navigation bar (2). In the main window,
if you click the dropdown menu for "Look in", you'll see that you can switch
between All VMs, Standalone VMs (default), and VMs in vApps (3). Toggle through
the different options.
Note that we don't have any Standalone VMs yet. Click the CREATE VM button (4) to
create a new standalone VM.

HOL-1983-01-HBD
Create a VM
1. Name the VM
2. Pick the T1-OVDC virtual datacenter
3. Scroll down and pick the tclinux-base template
4. Click OK

HOL-1983-01-HBD
Notice that the VM creation process is much more simplified than in the old Flex UI. Wait
a few minutes while your new VM is being created (the status will change from Busy to
Powered On when finished).
Interact with the VM
Once the VM is created, you can work with it in the new UI.

HOL-1983-01-HBD
1. Click on the POWER and MORE dropdown links to see the familiar options for
managing a virtual machine.
2. Click on the monitor icon to launch the console to the VM in a new window. Close
the window when you're done.
3. Click the Details link to see more details on the virtual machine.
Virtual Machine Details
In the Virtual Machine Details window, you'll see the basic information of the VM in the
main window. You can make changes to the VM in the Hardware, Guest OS
Customization, and Advanced sections.
If you have configured the optional metrics database for vCloud Director, you will see a
new Monitoring Chart option. Click on the Monitoring Chart section.

HOL-1983-01-HBD
Monitoring Chart
The Monitoring Chart pulls data from the metrics database. You can click the Metric
dropdown menu to look at the different metrics available.
Note: Since you just created this VM, you probably won't have much in your charts. Over
time, the charts will show more data (based on the resource utilization of the VM). After
a few minutes, you should be able to see something in the cpu.usage.average and
mem.usage.average charts.
Another option to look at metrics is by using vRealize Operations, which now has a
Tenant App that allows publishing metrics from vRealize Operations in the vCD UI using
a plugin. That scenario is shown in the companion lab to this one, HOL-1883-02-HBD -
VMware Cloud Provider Program - Tools and Offerings.

HOL-1983-01-HBD
Add vApp from OVF
In previous versions of vCloud Director, to get an OVF/OVA deployed required deploying

it in vCenter, then importing it into vCloud Director. In the new HTML5 interface, we can
directly import an OVA/OVF into a vApp (or directly add to a catalog).
1. Select vApps from the left-hand navigation bar. This is where you can create and
manage vApps instead of managing individual virtual machines.
2. Click the Add vApp from OVF.

HOL-1983-01-HBD
Create vApp from OVF

HOL-1983-01-HBD
1. Click the Upload Button

2. Select the photon-custom OVA in the Downloads folder
3. Click the Open button
4. Click the Next button. Click the Next button again on the Review Details screen.

HOL-1983-01-HBD
Accept the EULA

HOL-1983-01-HBD
1. Scroll down to the bottom of the EULA

2. Check the box to agree to the EULA
3. Click the Next button. Click Next on the Select vApp Name page to accept the
default name.

HOL-1983-01-HBD
Configure Resources
1. Set the Storage Policy to vSAN HOL Policy

2. Click the Next button

HOL-1983-01-HBD
Configure Networking and Customize Hardware

HOL-1983-01-HBD

HOL-1983-01-HBD

HOL-1983-01-HBD
Leave the Configure Networking and Customize Hardware pages on their default
settings and click Next on each page. Click Finish on the Ready to Complete page.

HOL-1983-01-HBD
See the new vApp
It may take a couple minutes to finish creating, but it will eventually show as Stopped.
You successfully created a vApp from an OVA.

HOL-1983-01-HBD
Networking
1. Click on Network in the left-hand navigation bar to view a list of Org VDC
Networks.
2. Click on the T1-OrgNet-Rtd Org VDC Network to see details of the network.
3. Note the Add and Delete buttons that allow you to add and delete Org VDC
Networks.

HOL-1983-01-HBD
Edges
1. Click on Edges in the left-hand navigation bar to list the Edges.

2. Click on the T1-ESG to see details on the Edge.
3. Note that the Convert to Advanced is grayed out. That's because this Edge has
already been converted to Advanced.
4. Click the Configure Services button to see the Edge configuration pop-up
window. Click around and look all the configuration options available. Close the
pop-up by clicking the X in the upper right-hand corner when done.

HOL-1983-01-HBD
Security
1. Click on Security in the left-hand navigation bar.

2. Click on Security Services for T1-OVDC.
3. Click the Configure Services button to see the configuration pop-up window for
the NSX Distributed Firewall settings for the Org VDC. Click around and play with
the settings. Close the pop-up by clicking the X in the upper right-hand corner
when done.

HOL-1983-01-HBD
Libraries
1. Click on the three lines at the top (hamburger menu) and select Libraries.
The Libraries section is where you can access vApp Templates, the Media library,
Catalogs, and Service Libraries. Service Libraries are a new feature in vCloud Director
9.1 and will be covered in more detail in another section.
Administration
1. Click on the three lines at the top (hamburger menu) and select Administration.
The Administration section is where you configure the Multisite feature in vCloud
Director v9.1. The federation between sites has has to be done using the vCloud APIs
before you can configure Multisite in the tenant UI. Once federation has been
completed, you would first Export from one vCloud Director instance, then you would
Create on another instance and import the exported data from the original instance.
This would effectively pair Org-A at Site A with Org-B at Site B, for example.

HOL-1983-01-HBD
Configuring Multisite
Multisite in vCloud Director allows a tenant that has access to multiple OVDCs in
separate vCloud Director instances to view and manage those OVDCs through a single
interface. Some API configuration needs to be done ahead of time by the vCloud
Director Administrator. Then the user will be able to configure multisite on their own in
the new HTML 5 Tenant UI. In this lab, the API steps have already been done. Now we'll
go through the steps the user can do to configure multisite.
Administration
You should already be logged in to the T1 Org on vcd-01a as t1admin and in the
Administration section.

HOL-1983-01-HBD
Log in to vCD-01b
1. Open a new tab in the browser

2. Click on the vCD - Tenant1 folder in the bookmarks bar and click on the vCD -
Site B - HTML 5 link
3. Log in as t1admin
4. Password is VMware1!
5. Click the Login button

HOL-1983-01-HBD
Go to Administration in vCD-01b
Click the three lines near the top of the screen (hamburger menu) and select
Administration

HOL-1983-01-HBD
Export Local Association Data for Site B
1. Click the Export Local Association Data button on vcd-01b.corp.local

2. Note that it downloads assoc_data.xml
3. Switch back to the first tab in the browser to go back to vcd-01a.corp.local
Note: if you see a message asking if you want to keep the file, select Keep

HOL-1983-01-HBD
Create New Organization Association on Site A

HOL-1983-01-HBD
Click the Create New Organization Association button on vcd-01a.corp.local

HOL-1983-01-HBD
1. Click the blue Upload button

2. Select the assoc_data.xml file
Click Next

HOL-1983-01-HBD
Click Submit
Click Finish
Export Local Association Data for Site A
1. Click the Export Local Association Data button on vcd-01a.corp.local

2. Note that it downloads assoc_data (1).xml

HOL-1983-01-HBD
3. Switch back to the second tab in the browser to go back to vcd-01b.corp.local
Note: if you see a message asking if you want to keep the file, select Keep
Create New Organization Association on Site B

HOL-1983-01-HBD
Click the Create New Organization Association button on vcd-01b.corp.local

HOL-1983-01-HBD
1. Click the blue Upload button

2. Select the assoc_data (1).xml file
Click Next

HOL-1983-01-HBD
Click Submit
Click Finish

HOL-1983-01-HBD
Look at Both Sites in One View
1. Close the second browser tab to go back to vcd-01a.corp.local

2. Click the three lines near the top of the screen (hamburger menu) and select
Datacenters
3. Scroll down to see SiteB-T1-OVDC

HOL-1983-01-HBD
Note: it may take a few minutes for SiteB-T1-OVDC to show up. You may need to refresh
the browser window a few times.

HOL-1983-01-HBD
vRealize Orchestrator Integration

Another new feature in vCloud Director is the Service Library, which allows you to
import and execute workflows from vRealize Orchestrator.
Log in as Administrator
1. You should already have a browser window open. If not, open Chrome by double
clicking the icon on the desktop or by clicking the button on the taskbar
2. Select the vCDa-Provider bookmark link from the vCD-Admin folder in the
bookmark toolbar. This will bring you to the vCloud Director Service Provider
Admin Portal login screen
5. Click Login

HOL-1983-01-HBD
Content Libraries
Click the three lines near the top (hamburger menu) and select Content Libraries
Service Library
Notice that there is only one workflow in the Service Library. Now we will go through the
steps to add a new workflow.

HOL-1983-01-HBD
Service Management - Service Categories
In order to add vRealize Orchestrator (vRO) workflows to vCloud Director. You first need
to add a vRO server and create Service Categories.
1. Click on Service Management in the left-hand navigation bar. Note that a vRO
server has already been added.
2. Click on Service Categories. Note that we already have two categories. Let's add
a new one.
3. Click the + to add a new category

HOL-1983-01-HBD
New Service Category
1. Name the new category Email

2. Type Email in the Description field
3. Click the Upload button to import an image

HOL-1983-01-HBD
Upload Image
Service Categories require an image to associate with. You can create your own image
file or download images from the web. Always check licensing rights for images
downloaded from the web (a good place to start is to search for "free icons"). The
maximum image size allowed is 100x100 pixels. We have already downloaded an image
for you titled email.png.
1. Select email.png

HOL-1983-01-HBD
Save the New Service Category
Click the Save button to save the new category

HOL-1983-01-HBD
Import a Workflow

HOL-1983-01-HBD
1. Click Service Library in the left-hand navigation bar

2. Click the Import button
3. Select Email
4. Click Next

HOL-1983-01-HBD
5. Select vro-01a.corp.local
6. Click Next
7. Click the arrow next to vCD Test Workflows to expand the folder
8. Select Send email to administrator@corp.local
9. Click Next
Click Done

HOL-1983-01-HBD
Manage Workflow
Notice the new workflow is now visible in the Service Library. Click the Manage link to
configure it.

HOL-1983-01-HBD
Select Publish Workflow
1. Select Publish to Service Providers

2. Select Publish to Tenants
3. Note that there is an option to publish to all tenants. In this case, we're only going
to publish to T1. Check the box for T1.
4. Click Save
Test the workflow

HOL-1983-01-HBD
Click the Execute link to run the workflow
1. Enter a subject
2. Enter content for the email
3. Click Finish
Click the Recent Tasks button to see if it was a success. You should see something like
this:
Close the Recent Tasks window when you're done (click the X in the upper right-hand
corner or click OK).

HOL-1983-01-HBD
Check Publishing to Tenant

HOL-1983-01-HBD
1. Click the Customize and Control button in Chrome and select New
incognitow window
2. Click the vCD - Tenant 1 folder and select vCD - T1 HTML 5 (not shown in
image above)
3. Log in as t1admin
4. Password is VMware1!
5. Click Login
6. Click the three lines near the top (hamburger menu) and select Libraries
7. Click on Service Library in the left-hand navigation bar
8. See the new workflow. Feel free to Execute and send an email, if you want to.
Note: At GA, vCloud Director 9.1 did not have the proper permissions available to allow
tenants to execute workflows. However, it can be fixed using the APIs (which is what
was done in this lab).

HOL-1983-01-HBD
Extra Credit: Create Your Own Workflow and Import it
Note: you should only do this step if you have spare time and are familiar with vRealize
Orchestrator.
This section of the lab used a very simple workflow to show the process of of importing,
publishing, and executing vRO workflows in vCloud Director. If you are familiar with
vRealize Orchestrator and want to play with your own workflows, you can launch the
vROWorkflowDesigner from the Windows Start Menu.
User Name: administrator@vsphere.local

Password: VMware1!
If you are not familiar with vRealize Orchestrator, you should probably take the separate
Hands-On Lab that focuses on it before you try to create your own workflows and import
them in to vCloud Director. It is also important to note that vCloud Director can only
work with certain input types. Check the documentation for more details.
From the vCloud Director 9.1 Release Notes:

HOL-1983-01-HBD
vCloud Director 9.1 supports only the following input parameters of vRealize
Orchestrator workflows:
• boolean
• sdkObject
• secureString
• number
• mimeAttachment
• properties
• date
• composite
• regex
• encryptedString
• array

HOL-1983-01-HBD
Conclusion
In this Module, we covered some of the new features in vCloud Director 9.1.
We then walked through the new HTML 5 user interface.
• Module 1 - Introduction to vCloud Director (30 minutes) (Basic)

• Module 2 - vCloud Director Consumption (30 minutes) (Basic)
How to End Lab

HOL-1983-01-HBD
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-1983-01-HBD
Version: 20181104-123440

Hol 1983 01 HBD - PDF - en

Încărcat de

Informații document

Titlu original

Drepturi de autor

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Hol 1983 01 HBD - PDF - en

Încărcat de

Drepturi de autor:

HOL-1983-01-HBD

Audience for this lab:

Lab Module List:

• Module 1 - Introduction to vCloud Director (30 minutes) (Basic) This module

• Eric Stine, Staff Systems Engineer, USA

Location of the Main Console

Alternate Methods of Keyboard Data Entry

Click and Drag Lab Manual Content Into Console Active

Accessing the Online International Keyboard

Click once in active console window

1. Click once in the active console window.

Click on the @ key

1. Click on the "@ key".

Notice the @ sign entered in the active console window.

Activation Prompt or Watermark

This cosmetic issue has no effect on your lab.

Look at the lower right portion of the screen

• Introduction to vCloud Director

Introduction to vCloud Director

vCloud Director Login

If you have not already done so, log in to vCloud Director

Note: if you get a message asking to open vmware-csd.exe, click Cancel.

Complete Software-Defined Services as Virtual Data

Terminology and Architecture Overview

Provider Virtual Datacenters

vCloud Director supports multi-tenancy through the use of organizations. An

Organization Virtual Datacenters

An organization virtual datacenter provides resources to an organization and is

Exploring vCloud Director

1. Click on the Manage & Monitor button

Open the T1 Tenant

View vApp Architecture

Mapping vSphere Resources to vCloud

Create a New Environment for Tenant3

Setup a Bronze Provider VDC

1. Ensure you are on the Manage & Monitor view

Name the New Provider VDC

1. Type Bronze-PVDC into the Name field

Select Resource Pool

1. Select the vCenter instance named vcsa-01a

Add a Storage Policy

Configure VXLAN Network Pool

Select Virtual Hardware Version

Review Ready to Complete

Review the Ready to Complete page and click Finish.

Verify Bronze-PVDC Creation

Setup a New Tenant3 Organization

1. In the Organization name field, type in T3

Verify Do not use LDAP is selected and Click Next

Add Local User

1. Click on the Add... button

Verify Account Creation

In a traditional deployment of vCloud Director, you may want to allow tenants to

Review Ready to Complete

Review the Ready to Complete screen and click Finish

Verify that Tenant3 (T3) is now listed in Organizations

Setup Organization VDC for Tenant3 and Pay-As-You-Go

1. Click on Organization VDCs

1. Select T3 from the Organization list

Select Provider VDC

1. Select Bronze-PVDC from the list

Select Allocation Model

1. Select Pay-As-You-Go as the Allocation Model.

Configure Pay-As-You-Go Model

Keep the defaults and click Next

Network Pool Selection