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.

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.

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.  

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.

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.

1. Click on the "@ key".

Notice the @ sign entered in the active console window.

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.  

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.

VMware Cloud Assembly: Automation and configuration of cloud services. Orchestrates infrastructure and application delivery across hybrid and multi-cloud environments.

VMware Service Broker:  A unified catalog across a multi-cloud environment that allows end users to request infrastructure and application services in a policy-based self-service manner. Aggregates content from multiple resources and platforms, including VMware Cloud Assembly, vRealize Orchestrator and native public clouds, into a common product catalog. Provides flexible, policy-based guardrails for governance.

VMware Code Stream:  Automates the application and infrastructure delivery process with release pipeline management, including visibility and analytics into active pipelines and their status for troubleshooting. Allows DevOps teams to leverage existing tools and processes with out-of-the-box integrations.

VMware vRealize Orchestrator: A workflow engine that allows users to create and manage workflows.  

VMware vRealize Suite Lifecycle Manager:  Automated deployment and lifecycle management, including configuration, upgrades and patching of vRealize Suite.

In this section, we learned about a few of the most exciting features of vRealize Automation 8.1.

Move onto the next lesson where we will step through the new concepts introduced in vRealize Automation 8.1 to simplify the IT service delivery through a modern architecture.

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

In this lesson we will start by logging into vRealize Automation.

From within the Chrome web browser:

1. Click vRealize Automation from the bookmarks bar.

At the Workspace ONE login screen:

1. Enter holadmin into the username field.
2. Enter VMware1! into the password field.
3. Click Sign In.

Please launch the Cloud Assembly Service.

From within the Cloud Services Console, under My Services:

1. Click the Cloud Assembly service.

In this lesson, we will explore the new vRealize Automation feature that allows administrators the ability to create Resource Limits for Cloud Zones. Using Cloud Assembly, we will discover where we can configure Resource Limits and where, once configured, we can view them.

We can see that when logging into vRealize Automation, the Deployments tab is selected by default.

1. In the upper portion of the screen, Click the Infrastructure tab.

1. In the navigation pane on the left, click Projects.
2. In the Projects frame, locate the HOL Project.
3. Click OPEN on the tile.

1. From the HOL Project project, Click Provisioning tab.
2. Find the Cloud Zones assigned to the HOL Project project and Click Private Cloud / ...

1. Review the settings for the Cloud Zone, including the limits for Instances, Memory, CPU and Storage(vSphere ONLY).
2. Click Cancel to close the Edit Cloud Zone dialog.

1. In the navigation pane on the left, click Cloud Zones.
2. Find the Cloud Zone tiles in the main frame. Find the tile for Private Cloud / RegionA01.
3. Click OPEN to view the settings for Private Cloud / RegionA01.

1. Click the Projects tab for Private Cloud / RegionA01.

We can see that this page displays the Resource Limits for each Project that utilizes this Cloud Zone

1. When finished reviewing the Resource Limits, Click Cancel to close the Private Cloud / RegionA01 Cloud Zone

In this lesson we explored Resource Limits, a new feature introduced in vRealize Automation 8.1. We learned that these limits are configured when we add a Cloud Zone to a Project. We also learned that we can view which Projects are consuming which Cloud Zones and if there are any associated Resource Limits from within the Cloud Zones pages.

In the next lesson of this module, we will look at the ability for administrators to present Custom Resources for end user consumption.

Open a custom resource to review the details.

1. CLICK the Design tab to open the Design console
2. CLICK Custom Resources in the left column
3. CLICK Add an AD user to open the Custom Resource

We can now explore the configuration of the Custom Resource Add an AD user and review the details below:

1. Resource Type - This is the name of the resource type displayed in the blueprint palette
2. External Type - This is the object type in vRealize Orchestrator
3. Activate - This must be enabled for the Custom Resource to be available for use
4. Scope - Allows for a Custom Resource to be available to all or specific Projects

Continue to explore the additional settings for Custom Resource Add an AD user by scrolling down and review the details below:

1. Create - This is where an administrator would select the vRealize Orchestrator workflow that will be used to create the custom object
2. Update - This is where an administrator would select the vRealize Orchestrator workflow that will be used to modify or update and existing custom object
3. Destroy - This is where an administrator would select the vRealize Orchestrator workflow that will be used to delete/destroy the custom object
4. Additional Day-2 actions - Administrators can provide additional functionality around the custom object. Some examples would be: Reset AD User Password, Unlock AD User Account, and more
5. CLICK CANCEL to exit the Custom Resource

In this lesson we explored Custom Resources, a new feature introduced in vRealize Automation 8.1. We learned that we can create Custom Resources under the Design tab. The Custom Resource feature extends the capability of vRealize Automation to create and manage external objects within vRealize Automation through both Cloud Assembly and Service Broker. A Custom Resource maps vRealize Orchestrator object types into vRealize Automation and uses vRealize Orchestrator workflows to ensure the object can be created, updated and destroyed.

In the next lesson of this module, we will look at the ability for administrators to design Custom Resource Actions.

1. From Cloud Assembly, CLICK the Design tab
2. CLICK Resource Actions
3. CLICK vSphere VM vMotion to open the configuration of the Resource Action

Browse the configuration and review the settings highlighted below:

1. Display name - Will be displayed to the user in the action menu of a resource
2. Activate - Must be enabled for the action to be available to users
3. Scope - This field shows the projects that the action will be made available to (This setting cannot be modified once the action is created)
4. Resource Type - This field shows the resource type that the action will be applicable to (This setting cannot be modified once the action is created)
5. Workflow - This field shows the vRealize Orchestrator workflow that will be used by the Resource Action

In the Property Binding section, we are able to use vRealize Orchestrator actions to select the values for the custom Resource Action inputs using information about the resource itself that is passed from vRealize Automation.

1. Workflow input - This is a list of the inputs for the workflow defined in the previous section
2. Binding action - This is where the vRealize Orchestrator action is selected to retrieve the necessary information to fill the Workflow Input
3. Binding Action Input - This is where any inputs for the binding action are populated with values retrieved from the vRealize Automation request.

1. CLICK Cancel

1. CLICK the Deployments tab to return to the manage deployments screen
2. CLICK the vSphere Ubuntu deployment to open and view

1. CLICK the Ubuntu machine from the deployment canvas
2. CLICK Actions to view the available actions
3. Note the availability of the Move VM custom Resource Action
4. CLICK CLOSE to exit the deployment

In this lesson we explored custom Resource Actions, a new feature introduced in vRealize Automation 8.1. We learned that we can create Resource Actions under the Design tab. The Resource Actions are based on vRealize Orchestrator workflows and can greatly enhance the self-service Day 2 operations for end users.

In the next lesson, we will look at the ability for administrators to assign pricing to existing and future deployments.

1. In the upper portion of the screen Click the Infrastructure tab.
2. Click Pricing Cards to view the available Pricing Cards
3. Locate the HOL Pricing Card
4. Click OPEN to review the current settings

Review the settings for this Pricing Card

1. Name - Assign a name for the Pricing Card
2. Description - Helps others understand the purpose of the Pricing Card
3. Currency - Shows the selected currency for the Pricing Card
4. Default for unassigned project - Administrators can set a Pricing Card to be the default for ALL Projects without a specified Pricing Card
5. Overview - Quick review of the pricing that has been assigned to this Pricing Card

1. Click the Pricing tab

We can click to expand and review each of the sections in the Pricing Card to view the properties available.

1. Basic Charges - CPU, Memory, Storage are all available to assign a price
2. Guest OSes - Assign a price for specific Guest OSes to account for licensing costs
3. Tags - Assign a price based on Tags assigned to the resource
4. Custom Properties - Assign a price based on vSphere Custom Properties
5. Overall Charges - Assign a one-time or recurring price to cover assorted infrastructure costs
6. When finished, Click Cancel when you have finished reviewing the pricing card

1. In the upper right corner, click the 9 squares button to open the navigation menu
2. Click  Service Broker to navigate to the Service Broker console to view pricing

1. Locate the Ubuntu 18 Catalog Item
2. Click REQUEST

1. In the Deployment Name field type HOL Deployment
2. Click the CALCULATE button at the bottom left of the page

1. Click Details to open a detailed list of the charges

We can see the Price of the components and how they align with the Pricing Card we reviewed.

1. Click the CLOSE button to exit the Daily Price Estimate details
2. Click the CANCEL button to cancel the deployment

In this lesson we explored the Pricing Card feature which is new in vRealize Automation 8.1. We learned that we can assign an uplift to a number of deployment attributes, that are based on the vRealize Operations cost metrics using pricing cards. Finally we reviewed how, at request time, a Service Broker User can obtain an understanding of the daily price of a deployment

In the next lesson, we will look at some of the new features in the Service Broker console.

For the next few lessons, we will explore new features in Service Broker. If you have not already opened Service Broker, please follow the steps below.

1. In the upper right corner, click the 9 squares button to open the navigation menu
2. Click the Service Broker button to open the Service Broker console

From the Service Broker interface

1. Click the Content & Policies tab
2. In the left navigation pane, click Definitions under Policies
3. Click the policy definition Azure approval

Review the details of the approval policy definition

1. Scope - The scope of an Approval Policy can be an Org or a Project. Notice that HOL Project is defined as our scope for this policy
2. Deployment criteria - An administrator can define criteria to match specific deployments. Feel free to explore the options available
3. Approver mode - An administrator can define whether a request requires the approval of any one approver or all approvers
4. Approvers - At least one approver must be defined.

Continue to review the Approval details

1. Auto expiry decision - An administrator can define how we want the approval to proceed upon expiration
2. Auto expiry trigger - The number of days the approvers have to respond before the Auto action is triggered. The value can be set up to 7 days.
3. Actions - An administrator can select one or more actions that this policy applies to. The actions include deployment and component level actions.
4. Click the CANCEL button to exit the policy

In this lesson, we explored an Approval Policy. Through the use of Approval Policies, administrators can hold a request for provisioning or Resource Actions until it has been reviewed by approver(s). This can ensure that resources are being utilized optimally and prevent possible impact to workload.

In the next lesson, we will explore Code Stream Pipelines as Catalog Items.

1. In the upper right corner click the 9 squares button to open the navigation menu
2. Click the Code Stream button to open the Code Stream console

1. In the left navigation pane, click Pipelines to view existing Pipelines
2. Find the Base Configuration Pipeline and click ACTIONS to view the available actions for the Pipeline
3. Click Release

On the Base Configuration tile:

1. Confirm the Pipeline status is set to Enabled & Released

1. In the upper right corner, click the 9 squares button to open the navigation menu
2. Click the Service Broker button to open the Service Broker console

1. Click the Content & Policies tab
2. In the left navigation pane, click the Content Sources button
3. Click the NEW button to create a new content source

1. Click Code Stream Pipeline content source

1. In the Name field type: HOL-Code-Stream
2. In the Source Project select: Lab Automation Project
3. Click VALIDATE to ensure that at least 1 item is found
4. Click CREATE & IMPORT to complete the new content source creation

1. In the left navigation pane, click Content Sharing
2. Select the Project Lab Automation Project
3. Click ADD ITEMS

1. Click the drop down and select ALL CONTENT
2. Check the box beside Base Configuration pipeline to add it to the project
3. Click SAVE

1. Click the navigation tab for Catalog near the top of the screen
2. Find the Base Configuration catalog item is available for request. You may click REQUEST to view the form, but please do not execute the request as it will impair functionality of the lab.

In this lesson, we walked through the process of releasing a Code Stream pipeline to Service Broker, creating a content source for Code Stream Pipelines and importing the Code Stream Pipeline as a Catalog Item.

In the next lesson, we will explore Marketplace OVAs as Catalog Items.

1. Click the Content & Policies tab
2. In the left navigation pane, click the Content Sources button
3. Click the NEW button to create a new content source

1. Click Marketplace VM Templates - OVA content source

1. Type a name for the new content source, for example: Marketplace-OVA
2. Select the Source Project HOL-MyVMware
3. Click VALIDATE to ensure that at least 1 item is found
4. Click CREATE & IMPORT to complete the new content source creation

Please launch the vRealize Orchestrator Service.

1. In the upper right corner, click the 9 squares button to open the navigation menu
2. Click the Orchestrator button to open the vRealize Orchestrator console

1. Click Workflows under Library in the left column
2. Switch to Tree-View by clicking the appropriate button

1. In the left column, explore the tree view, using the > to expand folders to view the contents

1. Expand  Workflows > HOL > 2121-04
2. Click the Workflow New User Request to load the workflow into the main frame
3. Click the Version History tab

1. Select the version to Diff against
2. Scroll through the code to review the differences between selected versions in the DIFF Code view
3. Click the DIFF VISUALLY button to switch to Visual Versioning

1. Click each of the tabs of the Workflow to review the differences visually

1. In the Tree-View, expand Library > vCenter > Virtual Machine Management > Basic
2. Click the Get virtual machines by name workflow
3. Click the Schema tab

1. Click unpack vm arrays on the canvas
2. Click the RED box next to item3 (unpack vm arrays) to set a Breakpoint
3. Click DEBUG to execute the workflow

1. At the Search Criteria field, type Ubuntu
2. Click the RUN button

1. Notice that the workflow pauses at your Breakpoint and waits for your input before proceeding
2. You can now diagnose issues at specific points within your Workflow by using the Continue, Step Into, Step Over or Step Return
3. At the top of the workflow, you will find the Cancel Run button
4. You can explore the variable contents in the Lower pane by clicking Variables and expanding the variable of your choice
5. Click the CONTINUE button to continue moving through the Workflow

1. Click the CLOSE button to return to the Workflow view

1. Expand the left navigation pane by clicking the >> button

1. Click the button at the top of the left column to expand the menu

1. Click Actions to load the library of Actions

1. In the Filter dialog, type getVmByName
2. Click on the action that is returned to open it

1. Review the configuration of the Action by clicking the tabs at the top
2. Click DEBUG

1. In the Name field, enter ubuntu-002
2. Click RUN

1. Explore the results of the execution in the Results/Inputs dialog
2. Click Close to exit the Action

In this lesson, we explored several new features of vRealize Orchestrator. We learned how we can explore the Workflows using a Tree-View instead of the Card or List View. We discovered how, with integrating versioning with GIT, we can compare versions using a text or visual DIFF. Finally we learned how to debug Workflows and actions.

With these new features, administrators will be able to quickly create new content to help automate all the things they need.

Congratulations on completing the lab module.

From here you can:

1. Click to advance to the next page and continue with the next lab module
2. Open the TABLE OF CONTENTS to jump to any module or lesson in this lab manual
3. Click on the END button if you are done with the lab for now and want to exit