VMware Hands-on Labs - HOL-1890-01-CHG


Lab Overview - HOL-1890-01-CHG - vRealize Automation Challenge Lab

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.

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


 

VMware Technology Network (VMTN)

For additional hints and to discuss the challenges presented in the lab further, be sure to visit the VMware Technology Netowork (VMTN) Community Pages:

https://communities.vmware.com/community/vmtn/challenge-lab/vrealize-operations

 

 

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 - Introduction (30 minutes)

Overview of vRealize Automation Challenge Lab


First day on the job as a cloud administrator? No problem. Start here.

This vRealize Automation Challenge asks you to put on your thinking cap to save the day! Each module places you in a different fictional scenario to fix common vRealize Automation administrative and integration problems. Have you ever had an entitlement issue with users? How about a mysterious request that is not functioning properly? In this lab, you will learn to solve these and more.

As you walk into a tall glass building, you glance at your watch: 9:00AM. It's the beginning of another workday at one of the most desirable businesses in the year 2096: Rainpole Enterprise Inc.

Rainpole Enterprise Inc. is a global IT services company that offers various IT services to organizations across the globe. They've recently adopted VMware's Software Defined Datacenter approach to modernizing their datacenter. This is inline with their vision of transforming the way they run their businesses. Any of their customers can now request any service that is provided by Rainpole Enterprise Inc. through their self-service portal like an App Store. But Rainpole Enterprise Inc technology isn't magic. No, its' datacenter in the gleaming building you just entered is powered by vRealize Automation.

As the largest and most trusted global IT services company, Rainpole Enterprise Inc.'s highest priorities are the reliability and stability of its operations. That responsibility rests on the shoulders of both you and your colleagues.

The following modules will test your mettle in order to keep the services operations running smoothly. This lab is best suited for those with some vRealize Automation experience, or who have already taken labs such as HOL-1821-USE-1: vRealize Automation 7 Basics or HOL-1821-USE-2: vRealize Automation 7 Advance. This lab includes over two hours of content, so you might not be able to complete it all in one sitting. Because the vRealize Automation Challenge lab requires troubleshooting, your completion time could vary. We provide optional hints along the "way," as well as providing the Challenges' final solutions.

We recommend that you start with Module 1 and then proceed to the rest of the modules. But if you are feeling rather confident today, you can skip right ahead to modules that interest you more.

This Module contains the following lessons:


Troubleshooting tools available



 

Open the vRealize Automation Web Page

 

On the desktop, click on the Chrome browser desktop shortcut. Locate the bookmark vRealize Automation. Click on it.

 

 

Login to vRealize Automation

 

Fill in the login form with the following details:

  1. Username: cloudadmin
  2. Password: VMware1!
  3. Click Sign in button

Note: The user cloudadmin has been assigned with vRealize Automation roles of Infrastructure and Tenant administrator. This grants them access to the Infrastructure tab which allows the user to look at troubleshooting information like logs and events details. For more information on vRealize Automation roles, feel free to read up more here. (opens in a new window)

Note: Also, the domain that will be used for this lab is corp.local, you should not need to change the domain selection unless prompted to do so.

 

 

Viewing Recent Events

 

To be able to view a list of recent activities on vRealize Automation:

  1. Click on Infrastructure tab
  2. You will be presented with a list of recent events that has occurred.

NOTE: This view will give you some information required to start investigating where an issue derived from. The logs displayed here are limited to IaaS related activities.

 

 

Locating Logs View

 

Sometimes, you might need to view detailed information from the logs. You can do so by navigating to the log details:

  1. Click on Monitoring

Note: You will access the menu by clicking on Infrastructure > Monitoring (as shown from the previous step). Same as the Recent Events view, the logs displayed have a limited coverage of the normal logs and the audit logs from IaaS (.Net) components only. 

 

 

Access the Logs View

 

To access the logs view:

  1. Click on Log
  2. You will be presented with detailed log information (What you see from your lab might differ from the screen capture shown)

NOTE: You can use this view to retrieve more detailed information which can help you troubleshoot IaaS provisioning issues.

 

 

Open the Log Insight Web Page

 

Another great tool that you can use is vRealize Log Insight with vRealize Automation Content Pack. This lab has already been configured to send all vRealize Automation and vRealize Orchestrator logs to vRealize Log Insight.

If you already have Chrome open, you can launch into vRealize Log Insight by opening another browser tab. Or in a new browser window, locate the bookmark vRealize Log Insight and click to open it.

Additional Info: The vRealize Automation 7.2 content pack for Log Insight provides you with important information across all components of your vRealize Automation 7.2 environment. This includes a consolidated summary of log events across all vRealize Automation components of the environment including vRealize Automation VA, vRealize Automation IaaS components and VMware Identity Manager (vIDM).

 

 

Login to vRealize Log Insight

 

Fill in the login form with the following details:

  1. Username: admin
  2. Password: VMware1!
  3. Click Login button

 

 

Locating vRealize Automation Content Dashboards

 

In order to look at the vRealize Automation Content Dashboard:

Click on VMware - vRA 7

Additional Info: You can see both VMware - Orchestrator - 7.0.1+ and VMware - vRA 7 content packs which are available to use for troubleshooting.

 

 

Accessing vRealize Automation Content Dashboards

 

You can use the tabs along the left side to deep dive into dashboards that can help you identify and troubleshoot problems.

  1. Choose a dashboard by clicking on it.
  2. Dashboard will be populated automatically for the time range selected at the top of the Dashboards page.
  3. Highlight the date selection option at top of page for predefined and custom date ranges; default is last 5 minutes. Change this to Latest Hour of Data.

 

 

Querying Log Insight for specific vRealize Automation log entries

 

You can also leverage the Interactive Analytics feature to search for specific log entries that you want to discover for more information.

  1. Click on Interactive Analytics
  2. Create your own search queries or filters
  3. Log Insight will present the log details based on your queries or filters
  4. Search here for a specific string value, not just fields. (i.e. you can use open text search to search for "error" or "404")

 

 

vRealize Content Dashboards Explained

 

Each content dashboard is focused on the specific vRealize Automation components. Selecting a dashboard will provide more detailed information.

 

 

vRA Content Dashboard: General Problems

 

  1. The General - Problems Content Pack will present dashboards detailing the most common problems within a vRealize Automation environment.
  2. Scroll to the bottom.
  3. Predefined Alert Queries have been created that will allow you to click and run against the environment to look for potential issues. Depending on how your environment is configured, some of these alerts may not be valuable for you. For those that are, it would be recommended for you to create Log Insight alerts so that you could be notified when there are issues within the environment.
  4. Provisioning Failure Queries are additional predefined dashboard filters based on common known issues collected by VMware.
  5. Each filter under both Alert Queries and Provisioning Failure Queries contain an informational dialog window indicated by the "i" icon.
  6. Selecting the Information Dialog will show you tasks or knowledge base articles for these common problems. These steps can be followed to resolve issues that may be identified within your environment.

 

Module 2 -Cloud Administration, Basic Challenge (30 minutes)

Some users are not receiving email notifications


You receive a call from the Development Manager. He claims that before he went on vacation, he used to get email notifications when he and his team would provision VMs. Now that he has returned from PTO, these notifications are no longer being received when performing tasks within vRealize Automation.


 

Open Chrome Browser from the Windows Desktop

 

Open Chrome, or open a new tab if you already have it open.

  1. Click on the Chrome Icon on the Windows desktop.

 

 

Login to the Roundcube Webmail Portal

 

  1. Open the Roundcube Webmail Portal from the link in the favorite bookmarks bar.
  2. Login as the Development Manager.

Note: If the favorite link fails to open the Roundcube Webmail Portal, try using the url: https://mail.rainpole.com/mail.

 

 

Validate Inbox

 

Verify that the Development Manager is not receiving email notifications from the vRealize Automation Portal (cloudadmin@rainpole.com). (For this scenario, the inbox will be empty.)

 

 

Login to the vRealize Automation Portal

 

Open a new tab and launch the vRealize Automation Portal link from the favorite bookmarks bar.

NOTE: If you are already logged into the vRealize Automation portal, ensure to log out, and re-log in as the Development Manager.

For this challenge:

  1. Log into vRA as the Development Manager.

 

 

Request to Provision a Virtual Machine

 

  1. Browse the Service Catalog.
  2. Request a Virtual Machine from the Windows Server 2012 catalog item.
  3. Accept defaults.
  4. Click Submit.

 

 

Validate the lack of Emails

 

Return to the RoundCube WebMail Client and verify that the Development Manager is not receiving email notifications. (Again, for this scenario, the inbox will be empty.)

 

 

Return to the vRealize Automation Portal

 

Return to the vRealize Automation Portal.

 

For this challenge:

  1. Determine why the Development Manager is not receiving notification emails.  

 

Need hints?

View Hint #1 (Hint will open in a new browser window)

View Hint #2

You can also view hints on the VMware Technology Network Communities here:

https://communities.vmware.com/docs/DOC-37016

Go to the next page to see the solution.

 

 

Solution #1

 

It turns out that the Development Manager had disabled email notifications before he went on PTO. Now that he has returned, he forgot to re-enable it.

Enable Email Notifications:

While logged into the vRealize Automation Portal as the Development Manager (devmgr), do the following:

  1. Click on Preferences (located in the top right corner of the portal UI), locate Email in the Notifications Section. Place a check under Enabled.
  2. Apply, then Close.

 

 

Solution #2

 

Alternatively: Another possibility of why email notifications could have suddenly stopped, may be due to Suspended Notification Scenarios. These scenarios are configured by the Tenant Administrator and not the Business Group Manager. To validate these notification scenario statuses, you will need to change the logon of vRealize Automation portal to the Tenant Administrator (CloudAdmin).

To check and determine if the scenarios have been suspended, do the following:

  1. Log out of the vRealize Automation portal and log back in as the Tenant Administrator.
  1. Click on the Administration tab, then navigate to Notifications (located from the left menu).
  2. Select Scenarios from the left menu. Choose the green Activate button along the top to active the scenarios.
  3. On the right, verify that all scenarios are listed as Active.

 

 

Validate email notifications

 

  1. Log out of the vRealize Automation Portal, and log back in as the Development Manager.
  1. Return to the Service Catalog and request another VM from the previously mentioned catalog item Windows Server 2012. Again, accept defaults. Note: The deployment will fail, this is by design for a later challenge.  
  2. Log back into the Roundcube Webmail Client as the Development Manager and validate that notifications are filling the user's inbox. It may take a few minutes before emails start to propagate within the inbox.

 

 

Conclusion

This lesson was designed to demonstrate how to correct problems with users' email by checking the email preferences and enable notification scenarios.

Before proceeding to the next lesson, log out of the vRealize Automation Portal.

 

The Infrastructure Architect is not able to find vCenter templates when designing their blueprints


The server team has created a new Windows 2012 virtual machine (base-w12-patched) with all of the latest patches. It has been uploaded, and converted into a virtual machine template in the vSphere environment. Unfortunately, the Infrastructure Architect cannot seem to locate the template to add it to the Windows 2012- Patch blueprint.


 

Login to the vRealize Automation Portal

 

Log into the vRealize Automation Portal as the Infrastructure Architect.

 

 

Validate the missing template

 

Within vRealize Automation, navigate to Blueprints.

  1. Click the Design tab, then select Blueprints.
  2. Edit the Windows Server 2012 - Patched blueprint.
  3. Click on the Windows2012 Virtual Machine Object within the blueprint canvas.
  4. Select Build Information.
  5. Under Clone from: attempt to select the newly patched template base-w12-patched.
  6. You should notice it is missing.

 

 

Log into vCenter

 

  1. Open another tab, and select RegionA > RegionA vCenter from the favorites bar. This should open a link to the vcsa-01a.corp.local web client.
  2. Log in using the following credentials.

 

 

Validate the Template

 

Validate that the virtual machine template (base-w12-patched) is on the ESX host (esx-03a.corp.local).

 

 

Corrective Action

 

For this challenge:

The template must belong to a compute resource that is part of a reservation. Unfortunately, the template was placed on a host that is not part of the payload cluster being consumed by vRealize Automation.

 

Need hints?

View Hint #1 (Hint will open in a new browser window)

View Hint #2 (Hint will open in a new browser window)

View Hint #3

You can also view hints on the VMware Technology Network Communities here:

https://communities.vmware.com/docs/DOC-37016

Continue to the next page to display the solution.

 

 

Solution: Part 1

 

To resolve, you must first start your within vCenter.

  1. Return to the VMware vSphere Web Client and Log back if needed using Username: Corp\Administrator, Password: VMware1!
  2. Move (drag and drop) the esx host (esx-03a.corp.local) into the payload cluster (RegionA01-COMP01).

 

 

Solution: Part 1 - Alternative

 

An alternative solution would be to unregister/reregister the template to a host already in the payload cluster.

Within the VMware vSphere Web Client, you would need to unregister/reregister the template from the ESX host: esx-03a.corp.local to another ESX Host within the RegionA01-COMP01 Cluster.

 

 

Solution: Part 2

 

Once the host has been migrated to the cluster, as theFabric Administrator (cloudadmin) perform the following steps within the vRealize Automation Portal:

Username: cloudadmin

Password: VMware1!

  1. Click on Infrastructure -> Compute Resources -> Compute Resources
  2. Mouse over the RegionA01-COMP01 Compute Resources arrow, and perform a Data Collection.

 

 

Solution: Part 3

 

  1. Select Request Now under the Inventory Section.
  2. Click OK.

 

 

Solution: Part 4

 

  1. When the Data Collection has been completed (this may take approx. 5 minutes), navigate to Blueprints.
  2. Choose the Design tab, then click Blueprints.
  3. Edit the Windows Server 2012 - Patched blueprint.
  4. Click on the Windows2012 Virtual Machine Object within the blueprint canvas.
  5. Select Build Information.
  6. Under Clone from:, change the template from base-w12-02 to the newly patched template base-w12-patched.
  7. Click OK.
  8. Save the blueprint, then Click Finish.

The new template has now been implemented and is ready for use by all entitled users to the blueprint.

 

 

Solution: Part 5

 

This can be validated by logging out and logging back in as the Development Manager and requesting a new virtual machine from the catalog item Windows Server 2012 - Patched.

NOTE: This request will fail. This is as designed, as you will investigate why during the next lesson.

 

 

Conclusion

Any vRA user that is entitled to the Windows Server 2012 - Patched blueprint should now be allowed to request a newly provisioned virtual machine using the new patched virtual machine template.

This lesson was designed to test your ability to consume, update, and manage blueprint resources within vRealize Automation.

Please log out of the vRealize Automation Portal for the next lesson.

 

Requesting a Catalog Item fails


The new Windows patch blueprint has been updated, you have communicated the change to the business groups and have requested the Development team to start provisioning. Unfortunately though, when the Development Manager attempted to request the new patched VM from the service catalog, it failed. (See previous Lesson: The Infrastructure Architect is not able to find vCenter templates when designing their blueprints.)


 

Login to the vRealize Automation Portal

 

If not already logged into the vRealize Automation Portal launch the link from the favorite bookmarks bar and log in as the Development Manager.

 

For this challenge:

  1. Open the details of the request and investigate why the request failed.

 

 

Request Validation

 

NOTE: If you skipped the previous lesson, as the Development Manager, make a request of the Windows Server 2012 - Patched catalog item from the Service Catalog.

  1. Navigate over to the Requests tab and wait for the request to fail.
  2. NOTE: The Request Numbering may differ slightly from the manual to actual in the lab.

NOTE: You can click the refresh icon located at the bottom of the page to reload the data of the Requests tab.

 

 

View Failed Status

 

View the details of the request to attempt to determine the cause of the problem. Ensure to read the entire contents of the error message.

  1. Under the Status section, click on View Details
  2. You can read the full details of why the request failed

 

 

View error within Log Insight

 

It is possible to utilize Log Insight to investigate this error.

  1. Open Log Insight in a new tab. (Not shown in screengrab)
  2. Log into the Log Insight Portal using username admin and password VMware1!.
  3. Select the VMware - vRA 7 custom dashboards.
  4. Choose General - Problems.
  5. Hover over the vRA error events by error message and you can see the error why the provisioning request failed.

Continuing to the next screen will display the solution to the lesson.

You can also view hints on the VMware Technology Network Communities here:

https://communities.vmware.com/docs/DOC-37016

 

 

Solution

 

There will likely be times where the Business Group Reservations may run out of resources. When this occurs the Fabric Administrator will need to add additional compute resources to the reservation and resize it. For this scenario, we need to expand the storage reservation to resolve the Development Manager's issue.

  1. Log into vRealize Automation as cloudadmin.
  2. Click Infrastructure -> Reservations -> Reservations
  3. Select and edit the Development Sandbox reservation.
  4. Choose the Resources tab.
  5. Click the pencil icon next to the datastore and change the storage reservation to 50GB. Click OK.
  6. (Optional) Change the Memory Reservation to 15GB.
  7. Click OK to save the reservation change.
  8. Log out and log back in as the Development Manager.
  9. Reattempt to deploy the Windows 2012 - Patched Catalog Item.

NOTE: A problem was identified during the lab review with the Windows Server 2012 - Patched blueprint. This catalog item will not provision properly as built. The result will end in failure. Click here for a workaround to provision a VM from the Windows Server 2012 - Patched catalog item. 

 

 

Conclusion

This lesson demonstrates the responsibilities of the Fabric Administrator, and what can happen when a reservation runs out of capacity.  

Ensure to log out before continuing onto the next lesson.

 

Some users are not able to manage provisioned VMs


You've received a complaint from the Development Manager that he is unable to perform tasks within the vRealize Automation portal. He states that provisioning new VMs hang on "In Progress" and eventually fail. Additionally, he states that he can no longer perform day 2 operations, such as powering on and off virtual machines.


 

Launch the Module 2 startup script

 

For this lesson, we have to prep the lab environment to demonstrate the issue. Minimize the browser to expose the desktop.

  1. Open the Scripts folder located on the Control Center Desktop.
  2. Right click the file labeled "Start Module 2" and select to Run with Powershell.
  3. Press Enter when the script is Ready.

 

 

Login to the vRealize Automation Portal

 

Maximize the Chrome Browser to display the vRealize Automation Portal. Log into the portal as the Development Manager.

The below is a list of credentials that can be used for this lab.

 

For this challenge:

The Development Manager is unable to provision a new virtual machine. The deployment hangs on "In Progress." The problem seems very peculiar as no error message is presented to the enduser.

  1. Investigate why the virtual machine fails to deploy.
  2. Attempt to perform day 2 actions, such as Power On or Power Off on the managed VM: dev-003. Determine why these actions do not perform their respective tasks.

 

 

 

Validate a Virtual Machine Request

 

As the Development Manager, request a virtual machine. The Requests tab will reflect that the virtual machine provisioning is In Progress but no virtual machine will be deployed.

Note: The Request number may be different than the number listed in the example.

 

 

Validate Day 2 Operations: Part 1

 

  1. Navigate to the Items tab.
  2. Choose Machines on the left.
  3. Click on the dev-003 virtual machine.

 

 

Validate Day 2 Operations: Part 2

 

Attempt to Power On or any of the other Day 2 Actions.

 

 

Validate Day 2 Operations: Part 3

 

The actions will queue successfully, but will not actually process.

 

 

Validate with Log Insight: Hint

 

Using the vRA Content Pack within Log Insight, the Alert Queries can show problems within the environment.

Open Log Insight in a new tab.

  1. Click the Dashboards
  2. Select the General - Problems dashboard.
  3. Scroll down and view the various dashboards.
  4. Each dashboard will show various problems within the environment.

 

 

Validate with Log Insight: Hint

 

Double clicking on an error that is reported in one of the previous Content Pack dashboards will open the details of the error in Interactive Analytics. This view will allow you to see the detail of the vRealize Automation logs. These content packs and logs could assist in troubleshooting the various issues that may arise with vRA.

Note: If you double-clicked on the IaaS stopped services by Service Content Pack dashboard from the previous step, you would see this Interactive Analytics lod details.  

You can also view hints on the VMware Technology Network Communities here:

https://communities.vmware.com/docs/DOC-37016

Continuing to the next screen will display the solution to the lesson.

 

 

Solution

 

When the IaaS Manager Service (VMware vCloud Automation Center Service) is not running, the vRealize Automation Portal will attempt to function until the service can be restarted. No error message or indication is given which causes this particular problem to be an elusive mystery. However, simple troubleshooting can help to quickly identify and resolve this issue.

To identify the problem, follow these steps:

  1. Log into the vRealize Automation Portal as cloudadmin
  2. Navigate to Infrastructure -> Monitoring -> Log
  3. An error should be displayed within the logs that reads; "Could not connect to the Manager Service. The service might be offline or restarting. If this error persists, verify that the Manager Service.exe is running."
  4. There should also be a yellow banner at the top of the page that informs you the Manager Service is not running.

To resolve the problem:

  1. Launch a Remote Desktop Connection (RDP) to the IaaS Manager (iaas-01a.corp.local). (Note: There is an RDP icon linked to this server on the desktop.)
  2. Log in using -- Username: corp\administrator, Password: VMware1!
  3. Launch the services control panel (services.msc)
  4. Check the VMware vCloud Automation Center Service is currently stopped.
  5. Start the service and log out of the IaaS Manager virtual machine.
  6. Attempt to perform Day 2 operations (Power Off/On) on a virtual machine (use dev-003 in the Items tab).
  7. Reattempt to provision a VM from the catalog as the Development Manager.

The previous actions that were hung "In Progress" should restart and finish successfully.

Note: A problem was identified during the lab review with the Windows Server 2012 - Patched blueprint. This catalog item will not provision properly as built. The result will end in failure. The other catalog items will provision successfully. Click here if you would like a workaround to provision a VM from the Windows Server 2012 - Patched catalog item. 

 

 

Conclusion

This particular problem seems elusive, however, this lesson demonstrates what occurs and how you can troubleshoot the environment when the IaaS Manager Service is stopped.

 

Log out of the vRealize Automation Portal for the next lesson.

 

The Development Manager is unable to create Blueprints


A new project has been announced and the Development Manager is going to need the ability to create XaaS and Software blueprints.


 

Login to the vRealize Automation Portal

 

Log into the vRealize Automation Portal.

 

For this challenge:

The Development Manager needs to create blueprints for the Development Business Group. However, the Development Manager cannot access the Blueprint canvas. The tab is missing.

  1. Investigate why the blueprint canvas is missing and fix.
  2. Ensure that the Development Manager has the ability to create service blueprints.

 

Need hints?

View Hint (Hint will open in a new browser window)

 You can also view hints on the VMware Technology Network Communities here:

https://communities.vmware.com/docs/DOC-37016

Continuing on will display the solution to this lesson.

 

 

Solution

 

  1. Log into the vRealize Automation portal as the CloudAdmin
  2. Click Administration -> Users & Groups -> Directory Users and Groups
  3. Search for the Development Manager (devmgr)
  4. (Action not shown) Select the Development Manager user to edit the profile.
  5. Under Add Roles To This User, locate Infrastructure Architect and XaaS Architect and select them.
  6. Click Finish to save these role privileges to the Development Manager.
  7. Log out and log back in as the Development Manager.
  8. The Development Manager now has the ability to create blueprints and service blueprints.

 

 

Conclusion

By default, the Business Group roles; Business Group Manager, Support User, and User Roles, do not have the privileges needed to build or create Blueprints. This lesson demonstrates how to provide the privilege of creating Blueprints for the Development Manager.

Before moving onto the next Module, destroy any VMs that have been provisioned by both the Dev Manager and the Dev User. Log out of the vRealize Automation Portal.

 

Cannot add or sync new users to the vRA Portal


New team members have been hired and brought in to work with the Development Business Group. Unfortunately, the Development Manager cannot find them to add them to the Business Group as Support Users. This means the new team and its' members can not access the vRA environment.


 

Active Directory Users were precreated

 

The Active Directory administrator has notified you that he has created three new users and placed them in an AD Security Group.

For this challenge, the users and their respective accounts have already been created.

Users were created in OU=RainPole, DC=Corp, DC=Local

The AD Security Group ("Rebels") was precreated in OU=Users,DC=Corp,DC=Local.

 

 

Attempt to add new users to Business Group

Open Chrome Browser from the Windows Desktop

 

Open Chrome, or open a new tab if you already have it open.

  1. Click on the Chrome Icon on the Windows desktop.

 

 

Solution

 

The Identity Manager was configured to search for users within a specific OU. In this challenge scenario, that is the Users OU within Active Directory (OU=Users,DC=Corp,DC=Local). Unfortunately, our users were created within the RainPole OU. Because of this, the Identity source in vRA cannot locate the new users. To fix this we need to add the users OU to the Identity Source Configuration.

Add the Users OU to the Identity Source:

  1. Log out and log back in as the Tenant Administrator.
  2. Navigate to the Administration tab.
  3. Select Directories Management from the menu on the left.
  4. Click Directories on that same menu.
  5. Choose the corp.local directory.

 

Once the Active Directory settings are shown, scroll down. Take note that the Base DN field is the starting point for where vRA will search for users. However, instead of changing the Base DN, we will add the OU Location in the Active Director settings.

 

Scroll back up to the top of the Active Directory settings. Click on Sync Settings.

 

  1. Click on Groups.
  2. Ensure that Sync nested group members is checked.
  3. In the Specify the groups DNs field, enter the OU for the location of the AD Security Group Rebels.
  4. Click Find Groups.

 

  1. Do not check Select All. Choosing this option will select all groups within the Users OU. This may not be necessary in your environment as it may sync groups that may not be needed.
  2. Instead click the button to Select specific groups within the OU.

 

Scroll down and select the Rebels security group in the list.

Click Save.

 

You can now see that the Rebels Security Group has been mapped to the Identity Source.

Click Save & Sync. Then choose to Sync Directory.

The vRA Identity Manager will start to sync the users and groups with Active Directory which will allow vRA to see the new users that were created.

 

As the Tenant Administrator, you can validate that vRA can now see the new users by performing a search in the Directory Users & Groups.

To perform the search, do the following:

  1. Click back on the Administration menu item on the left hand menu.
  2. Select Users & Groups from the same menu.
  3. Then choose Directory Users and Groups in the same menu once more.

 

  1. In the top right hand corner, you can enter the user account of one of the new users to search for.
  2. For this scenario, we can search for hsolo, lskywalker, and lorgana and see each account discovered.

At this point, the Development Manager can log back into the vRA environment and add his new users to the Development Business Group.

 

 

Conclusion

This lesson was designed to demonstrate how the vRealize Identity Manager syncs with the Active Directory Identity Source.

As we have demonstrated, if the Base DN is mapped to a specific OU for users, it will ignore security groups within that OU unless the groups are specified in the groups settings. An alternative solution would have been to add the Rainpole OU to the Users Settings within the Active Directory settings.

Before proceeding to the next lesson, log out of the vRealize Automation Portal.

 

Module 3 - Cloud Extensibility, Basic Challenge (45 Minutes)

Workflows are seen running multiple times instead of just once


You are sitting in your office, reading vRealize Automation - Lifecycle Extensibility (opens in a new window), when you decide to double check on a recent enhancement done by your extended team of Integration Engineers. You want to make sure that they are in line with best practices.


 

Launch vRealize Orchestrator Client

 

To launch vRealize Orchestrator:

  1. Locate the vRealize Orchestrator Client shortcut on your Main Console desktop
  2. Double click or hit Enter to launch it

 

 

Login to vRealize Orchestrator

 

To login to vRealize Orchestrator:

  1. Ensure that the Host name is vra-01a.corp.local:443
  2. User name: administrator@vsphere.local
  3. Password: VMware1!
  4. Click Login

 

 

Switching to Design mode in vRealize Orchestrator

 

Once vRealize Orchestrator client has been successfully launched, you need to switch to Design mode:

  1. Click on the dropdown list and select Design

 

 

Exploring vRealize Orchestrator workflow

 

Rainpole's team of integration engineers have built a workflow that will add a computer account into your organization Active Directory Organizational Unit after a virtual machine request has been made through vRealize Automation. To find out more about what the workflow operates:

  1. Expand the HOL-1890 folder
  2. Click on the workflow Add a computer in an OU
  3. Click on Schema to show details on the execution steps in the workflow

NOTE: Do not close or exit from the vRealize Orchestrator Client, just minimize it from the desktop.

 

 

Open Chrome Browser from Windows Quick Launch Task Bar

 

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

 

 

Launch vRealize Automation

 

Click on the vRealize Automation bookmark

 

 

Log into vRealize Automation

 

  1. User Name: cloudadmin
  2. Password: VMware1!
  3. Click on Sign in button

 

 

Accessing Administration options

 

Click on the Administration tab

 

 

Click on Events

 

Click on Events

 

 

Accessing subscriptions created

 

  1. Click on Subscriptions
  2. Select the Add a computer in an OU subscription
  3. Click Publish

NOTE: This step activates the workflow subscription that will invoke the vRealize Orchestrator workflow Add a computer in an OU which you previously saw in the vRealize Orchestrator client.

 

 

Login to vRealize Automation as Dev User

 

NOTE: Log out of vRealize Automation as cloudadmin first before proceeding to login as devuser.

  1. User Name: devuser
  2. Password: VMware1!
  3. Click on Sign in button

 

 

Select catalog item

 

  1. Click on Catalog tab
  2. Request for a Windows Server 2012 catalog item

 

 

Submit a Request

 

1. Click on Windows2012

2. Click Submit

 

 

Request Submission status

 

A request acknowledgement will be displayed once you have submitted the request form.

  1. Click OK

 

 

Viewing the workflow run in vRealize Orchestrator

 

  1. Expand the workflow Add a computer in an OU to view the workflow execution history.

NOTE: It may take a few moments before the errors start to generate.

 

 

Challenge!

For this challenge:

  1. You are to investigate why did the workflow run multiple times, instead of just once
  2. Fix the issue so that the Add a computer in an OU workflow is only invoked once during a the VMPSMasterWorkflow32.BuildingMachine phase for a vRealize Automation request for a Virtual Machine.
  3. This workflow should only be invoked during the PRE state phase of VMPSMasterWorkflow32.BuildingMachine

You may now proceed to do your troubleshooting.

Note: Once you are done troubleshooting, you need to login to vRealize Automation as devuser and request for Windows Server 2012 catalog item in order to test out the result of your troubleshooting efforts.

Need hints?

View Hint #1

View Hint #2

You can also view hints on the VMware Technology Network Communities here:

https://communities.vmware.com/docs/DOC-37017

Proceed to next page only when you are ready to see the solution.

 

 

Use the vRA Content Pack in Log Insight to view the error

 

The vRA Content Pack in Log Insight provides easy views and access into Event Broker log events, errors, and logs. Log Insight can be launched from the Log Insight bookmark at the top of the browser.

  1. Click Dashboard.
  2. Select the vRA - Event Broker dashboard.
  3. Scroll through the page to see the various dashboards.
  4. You can view detailed Interactive Analytics by clicking on any of these dashboards.

 

 

vRA - Event Broker Interactive Analytics

 

The Interactive Analytics provides a detailed view into the Event Broker Logs. The log shows that the workflow is being called during every stage of the provisioning lifecycle.

 

 

Solution

 

Many times, when setting up subscription events, workflows do not run or behave as they should if:

  1. Subscription events do not have conditions setup
  2. Conditions defined are not correctly configured
  3. Workflows that was developed has errors

To solve this challenge:

  1. Login to vRealize Automation as cloudadmin
  2. Click on Adminstration -> Events -> Subscriptions
  3. Edit Add a computer in an OU subscription
  4. Click Next
  5. Select Run based on conditions
  6. Select All of the following to match against ALL conditions in the subscription
  7. Select Data -> Lifecycle state -> Lifecycle state name from the menu
  8. Select Equals as the Operator
  9. In the 3rd dropdown, select Constant -> VMPSMasterWorkflow32.BuildingMachine
  10. Click Add Expression to add another expression
  11. Select Data -> Machine -> Machine type
  12. Select Equals as the Operator
  13. For the value, choose Constant -> Virtual Machine
  14. Click Add Expression to add one more expression
  15. Select Data -> Lifecycle state -> State phase
  16. Select Equals as the Operator
  17. For the value, choose Constant -> PRE
  18. Click Finish

You can now login to vRealize Automation as devuser and request for the Windows Server 2012 catalog item, and the workflow should only be invoked once during the pre-stage of BuildingMachine.

NOTE: The VM request may fail due to lack of resources. This is an expected behavior.

 

 

Review

 

Now that we have completed your first vRealize Automation Challenge on Extensibility. Let's take a moment to review what we have done here.

In vRealize Automation 7, we introduced Event Broker, an event driven extensibility engine which provides UI-driven options for lifecycle automation. Event broker and a library of existing workflows and partner provided plug-ins on the VMware Solutions Exchange helps VMware accelerate the process of integrating multi-vendor tools into your vRealize Automation blueprints.

In this challenge, you were tasked to look into how we can automatically add a provisioned VM into an Active Directory Organizational Unit (OU). We had the workflow that was built in vRealize Orchestrator and setup an event broker subscription in vRealize Automation to trigger the workflow during the appropriate lifecycle state of the machine request.

However, based on the behaviour of how this event triggered, it seems that the workflow was executed at every state of the machine lifecycle. What you can see from the screen capture, is the ability for us to define conditions that trigger workflows at the correct lifecycle state. This allows us to filter events even further, e.g subscribing to events only from a certain part of the lifecycle or only for a certain type of objects. But the original subscription's conditions were setup to run for all events during a machine provisioning state, this explains why the workflow was being executed multiple times.

In order for us to properly define workflow subscriptions, we need to provide conditions to filter events.

Please proceed to next page.

 

 

Conclusion

 

To correct this mistake, we have to define a few conditions:

  1. We need to setup a filter to only subscribe to events that are at the Building Machine state. This will help to ensure that the workflow is only triggered at the correct lifecycle state
  2. Once we have define which state this subscription is listening on, we are able to decide whether to execute workflows during the PRE or POST stage of the lifecycle state
  3. Lastly, we want to also provide details on the object type this subscription is listening on, in this case, a Virtual Machine.

With these conditions setup in the subscription, the workflow will only be triggered during the PRE stage of the Building Machine phase and only on Virtual Machine objects.

 

 

Congratulations!

Your new knowledge of how to setup Lifecycle extensibility in vRealize Automation will come in handy when you have such similar requirements in future.

Onwards and upwards, are you ready for more extensibility challenge?

 

Workflows are not being triggered when they are supposed to


Just when you are about to take a breather from the previous challenge, you received a complaint about a newly integrated workflow that allows users to change a machine's admin/root password during the request submission, is not working! It is up to you now, to save the day with this new challenge!


 

Launch vRealize Orchestrator Client

 

Note: If you still have your vRealize Orchestrator Client minimized on your desktop, please restore the window and you may proceed to the next step here. Else please follow the instructions as shown.

To launch vRealize Orchestrator:

  1. Locate the vRealize Orchestrator Client shortcut on your Main Console desktop
  2. Double click or hit Enter to launch it

 

 

Login to vRealize Orchestrator

 

To login to vRealize Orchestrator:

  1. Ensure that the Host name is vra-01a.corp.local:443
  2. User name: administrator@vsphere.local
  3. Password: VMware1!
  4. Click Login

 

 

Switching to Design mode in vRealize Orchestrator

 

Once vRealize Orchestrator client has been successfully launched, you need to switch to Design mode:

  1. Click on the dropdown list and select Design

 

 

Exploring vRealize Orchestrator workflow

 

One of your integration engineers have built a workflow that will allow the user to change the admin/root password when they are submitting a request through vRealize Automation. To find out more about what the workflow operates:

  1. Expand the HOL-1890 folder
  2. Click on the workflow Change admin password
  3. Click on Schema to show details on the execution steps in the workflow

NOTE: Do not close or exit from the vRealize Orchestrator Client, just minimize it from the desktop.

 

 

Open Chrome Browser from Windows Quick Launch Task Bar

 

NOTE: If you already have Chrome launched, and logged into vRealize Automation, you may skip this step and proceed by clicking here.

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

 

 

Launch vRealize Automation

 

Click on the vRealize Automation bookmark

 

 

Log into vRealize Automation

 

NOTE: If you are not logged in as cloudadmin user, please Log out of vRealize Automation first before proceeding to login as cloudadmin. If you are already logged in as cloudadmin user, please proceed to next step.

  1. User Name: cloudadmin
  2. Password: VMware1!
  3. Click on Sign in button

 

 

Accessing Administration options

 

Click on the Administration tab

 

 

Click on Events

 

Click on Events

 

 

Accessing subscriptions created

 

  1. Click on Subscriptions
  2. Select the Set Admin Password subscription
  3. Click Publish

NOTE: This step activates the workflow subscription that will invoke the vRealize Orchestrator workflow Change admin password which you previously saw in the vRealize Orchestrator client.

 

 

Login to vRealize Automation as Dev User

 

NOTE: Log out of vRealize Automation as cloudadmin first before proceeding to login as devuser.

  1. User Name: devuser
  2. Password: VMware1!
  3. Click on Sign in button

 

 

Select catalog item

 

  1. Click on Catalog tab
  2. Request for a CentOS 6.6 catalog item

 

 

Submit a Request

 

1. Click on CentOS_6.6

  1. Click on CentOS_6.6
  2. Change the admin password (e.g. VMware2!)
  3. Click Submit

 

 

Request Submission status

 

A request acknowledgement will be displayed once you have submitted the request form.

  1. Click OK

 

 

Monitoring the progress of request

 

You can monitor the progress of your request:

  1. Click on Requests
  2. Wait for your request to update its Status from In Progress to Successful
  3. You can hit the Refresh button to get an update of the status

This usually takes 2-5 mins to complete.

 

 

Viewing the workflow run in vRealize Orchestrator

 

  1. Expand the workflow Change admin password to view the workflow execution history.

 

 

Challenge!

For this challenge:

  1. You are to investigate why the workflow did not run at all even though an event subscription has been created
  2. Fix the issue where the Change admin password workflow was not invoked during the VMPSMasterWorkflow32.MachineProvisioned phase for a vRealize Automation request for a Virtual Machine.
  3. This workflow should be invoked during the POST state phase of VMPSMasterWorkflow32.MachineProvisioned

You may now proceed to do your troubleshooting.

Need hints?

View Hint #1

View Hint #2

You can also view hints on the VMware Technology Network Communities here:

https://communities.vmware.com/docs/DOC-37017

Proceed to next page when you are ready to view the solution.

 

 

Solution

 

Many a times, when setting up subscription events, workflows do not run or behave as they should if:

  1. Subscription events do not have conditions setup
  2. Conditions defined are not correctly configured
  3. Workflows that was developed has errors

To solve this challenge:

  1. Login to vRealize Automation as cloudadmin
  2. Click on Adminstration -> Events -> Subscriptions
  3. Edit Set Admin Password subscription
  4. Click Next
  5. Select the last condition Data -> Machine -> Machine type
  6. For the value, change to Constant -> Virtual Machine
  7. Click Finish

You can now login to vRealize Automation as devuser and request for CentOS 6.6 catalog item, and the workflow will be invoked during the post-stage of MachineProvisioned.

 

 

Review

 

Let's take a minute to review how the Event Broker subscription was setup before you attempted to fix it.

Based on the subscription that was setup (as shown in the screen capture), the conditions that was defined will only trigger the subscription when:

  1. The request is in the Machine Provisioned state
  2. It is in the POST stage of the Machine Provisioned state
  3. It will only be triggered if the object type is a Cloud Machine

The first 2 conditions are defined correctly, however the type of object that we want to filter this event against is incorrect. This should be set as Virtual Machine object type, instead of Cloud Machine. This is the reason why, when we requested for the catalog item CentOS 6.6, the event was not even triggered.

 

 

Good job!

You deserve a pat on the shoulder for making it this far into the challenge! You are now much more confident in setting up event subscription conditions or filters to accurately trigger workflows during the proper lifecycle state of a machine request.

Good job!

Please proceed to next page

 

Assigning a new workflow as an action that could be triggered by user


One of your clients has requested a custom action that allows them to migrate their virtual machines from one ESXi host to another. Your integration engineer has implemented  a custom workflow in vRealize Orchestrator to accomplish this task, and it’s up to you to make this action available to your vRealize Automation users.


 

Launch vRealize Orchestrator Client

 

Note: If you still have your vRealize Orchestrator Client minimized on your desktop, please restore the window and you may proceed to the next step here. Else please follow the instructions as shown.

To launch vRealize Orchestrator:

  1. Locate the vRealize Orchestrator Client shortcut on your Main Console desktop
  2. Double click or hit Enter to launch it

 

 

Login to vRealize Orchestrator

 

To login to vRealize Orchestrator:

  1. Ensure that the Host name is vra-01a.corp.local:443
  2. User name: administrator@vsphere.local
  3. Password: VMware1!
  4. Click Login

 

 

Switching to Design mode in vRealize Orchestrator

 

Once vRealize Orchestrator client has been successfully launched, you need to switch to Design mode:

  1. Click on the dropdown list and select Design

 

 

Exploring vRealize Orchestrator workflow

 

One of your integration engineer have built a workflow that will allow the user to change the admin/root password when they are submitting a request through vRealize Automation. To find out more about what the workflow operates:

  1. Expand the HOL-1890 folder
  2. Click on the workflow Migrate virtual machine
  3. Click on Schema to show details on the execution steps in the workflow

NOTE: Do not close or exit from the vRealize Orchestrator Client, just minimize it from the desktop.

 

 

Adding a custom action into vRealize Automation

 

Your users want an action that allows them to migrate their virtual machine from one host to another. Your integration engineers have already built that workflow for you.

It is up to you now, to make it happen for your users.

 

 

Challenge!

For this challenge:

  1. You are to take the workflow Migrate virtual machine that has been built by your integration engineers and map it into a resource action in vRealize Automation
  2. You are then required to only entitle this resource action to the "Development Services" entitlements in vRealize Automation

You may now proceed to do your troubleshooting.

Need hints?

View Hint #1

View Hint #2

View Hint #3

You can also view hints on the VMware Technology Network Communities here:

https://communities.vmware.com/docs/DOC-37017

Proceed to next page when you are ready to view the solution.

 

 

Solution

 

To solve this challenge:

  1. Login to vRealize Automation as cloudadmin
  2. Navigate to Design -> XaaS -> Resource Actions
  3. Click on New to create a new resource action
  4. Select Orchestrator -> HOL-1890 -> Migrate virtual machine
  5. Click Next
  6. Leave everything as default and click Next
  7. Check Hide catalog request information page and click Next
  8. Leave the form as default and click Finish (You can modify the form if you know what you doing)
  9. Click Publish to publish your newly created resource action Migrate virtual machine
  10. Navigate to Administration -> Catalog Management -> Entitlements
  11. Edit the Development Services entitlement
  12. Click Next
  13. Click on the plus icon next to Entitled Actions
  14. In the Name search field, type in Migrate virtual machine
  15. Check the box next to Migrate virtual machine
  16. Click OK
  17. Click Finish

You can log into vRealize Automation as devuser, browse to any Machines under Items, and you will be able to see a new resource action Migrate virtual machine. Try it!

 

Module 4 - Cloud Administration, Advanced Challenge (45 Minutes)

Some users noticed that they are not entitled to perform certain actions on their VMs


Just as you are about to have a short coffee break, you get another complain from a user that he is not able to launch a remote console from vRealize Automation into his virtual machine. Well, with great power, comes great responsibility. And off you go to investigate further.


 

Open Chrome Browser from Windows Quick Launch Task Bar

 

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

 

 

Launch vRealize Automation

 

Click on the vRealize Automation bookmark

 

 

Login to vRealize Automation as Dev User

 

  1. User Name: devuser
  2. Password: VMware1!
  3. Click on Sign in button

 

 

View Items

 

  1. Click on Items
  2. Click on Deployments
  3. Expand the deployment Windows Server 2012-17208475 to reveal components (NOTE: The Deployment name may be different than the image displayed.)
  4. Click on the machine name to find out more information

 

 

Your Challenge!

 

Your user (devuser) is having issues trying to launch a remote console connection to access his virtual machine operating system. From the above, it seems that it is missing from his list of available actions.

For this challenge:

  1. You are to investigate why the user (devuser) is not able to see Connect to remote console action when viewing his virtual machine details
  2. Provide a way for the user to be able to access his virtual machine operating system from vRealize Automation

You may now proceed to do your troubleshooting.

Need a hint?

View Hint #1

View Hint #2

You can also view hints on the VMware Technology Network Communities here:

https://communities.vmware.com/docs/DOC-37018

Proceed to next page when you are ready to view the solution.

 

 

Solution

 

vRealize Automation allows you to have very granular entitlement policies to control and govern the types of actions or activities users are able to perform. In this challenge, users do not have the entitlement to perform remote console connection to their virtual machines.

To solve this challenge:

  1. Login to vRealize Automation as cloudadmin
  2. Navigate to Administration -> Catalog Management -> Entitlements
  3. Edit the Development Services entitlement
  4. Click Next
  5. Click on the plus icon next to Entitled Actions
  6. Search for connect to remote console under Name field.
  7. Check the box next to "Connect to remote console"
  8. Click OK
  9. Click Finish

Now you can log in as devuser, and you will see that Connect to remote console action will appear when viewing a machine's available list of actions.

 

Importing new content into catalog


One of your service architects has exported a blueprint that he wants you to publish into vRealize Automation. He has sent you the exported zip package that you can readily import into vRealize Automation without asking you to manually recreate the blueprint from scratch. How thoughtful! It is up to you now to as a vRealize Automation guru to complete this challenge. Are you up for it?


 

Launch Windows Explorer

 

  1. Click on the Windows Explorer icon on the Windows Quick Launch Task Bar.

 

 

Open HOL-1890 folder

 

  1. Click on Local Disk (C:)
  2. Double click on HOL-1890

 

 

Explore the vRA-BP-Import folder

 

  1. Double click on vRA-BP-Import folder

 

 

Import content into vRealize Automation

 

Your service architect has kindly exported the blueprint (CentOS-Base-vRA-Blueprint.zip) from a test environment and placed it into a folder that you see now.

For this challenge:

  1. You are to import the blueprint package (CentOS-Base-vRA-Blueprint.zip) into vRealize Automation
  2. Once your blueprint has been imported, you are to map the correct vSphere template for the blueprint according to the operating system
  3. Ensure that the blueprint is published
  4. Add this blueprint as a catalog item to Infrastructure service category

You may now proceed to do your troubleshooting.

Need a hint?

View Hint #1

View Hint #2

You can also view hints on the VMware Technology Network Communities here:

https://communities.vmware.com/docs/DOC-37018

Proceed to next page when you are ready to view the solution.

 

 

Solution - Import content from CloudClient

 

vRealize Automation allows you to easily import and export content by using vRealize CloudClient. It is a command line interface to provide an easy way for administrators to perform tasks.

To solve this challenge:

  1. Double click CloudClient shortcut from Main Console desktop
  2. CloudClient will automatically log you into vRealize Automation
  3. Type in this command once you have successfully logged into CloudClient
vra content import --path C:\HOL-1890\vRA-BP-Import\CentOS-Base-vRA-Blueprint.zip --precheck WARN --resolution OVERWRITE --dry-run no
  1. You should see that the import task has been completed successfully

Proceed to next step

 

 

Solution - Verifying imported content

 

You can now log in back to vRealize Automation as cloudadmin to view the imported blueprint.

  1. Click on Design
  2. Click on Blueprints
  3. You should see a new blueprint named CentOS Base
  4. Ensure that the blueprint is Published

Your next steps would be to entitle users to request for this blueprint.

Please proceed to next step.

 

 

Solution - Customizing content catalog

 

  1. Select Administration -> Catalog Management
  2. Click on Catalog Items
  3. Select CentOS Base
  4. Click Configure

Please proceed to next steps

 

 

Solution - Customizing content

 

  1. Scroll down to the bottom of the page by clicking on the arrow down
  2. Click on the dropdown list under Service
  3. Select Infrastructure
  4. Optional: You may browse to C:\hol\vRA Icons and upload a new icon to be assigned to this catalog item
  5. Click OK

You are now be able to request for this catalog item when you login as devuser.

 

Unable to manage existing virtual machines in vRealize Automation portal


You walk into office today, and were approached by one of your clients saying that he could not see one of his virtual machine when he is logged into vRealize Automation. Upon further clarification, you realized that this machine was provisioned before Rainpole Enterprise Inc implemented vRealize Automation. Your client is now requesting that you somehow make the existing VM available in vRealize Automation to manage as he does with his other VMs.


 

Open Chrome Browser from Windows Quick Launch Task Bar

 

NOTE: If you already have Chrome launched, you may skip this step and proceed by clicking here.

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

 

 

Open the vSphere Web Client

 

Click on the bookmark Region A > RegionA vCenter

 

 

Login to vSphere Web Client

 

Select Use Windows session authentication and click Login (Note: - May Take a few mins to login in this lab environment)

 

 

Host and Cluster view

 

  1. Navigate to the Hosts and Clusters view

 

 

Locate the VM to be imported

 

Your user (devuser) is requesting for you to import the virtual machine (import-01) into vRealize Automation. This will allow your users to be able to manage all their machines directly from vRealize Automation.

For this challenge:

  1. You have to import virtual machine (import-01) into vRealize Automation as a managed machine
  2. This machine belongs to the Development Business group
  3. It is mapped to a converged blueprint called Dev-CentOS
  4. And the component machine to be used is CentOS
  5. You have to ensure that after the import, ownership of the imported machine is assigned to devuser@corp.local

You may now proceed to do your troubleshooting.

Need a hint?

View Hint #1

View Hint #2

You can also view hints on the VMware Technology Network Communities here:

https://communities.vmware.com/docs/DOC-37018

Proceed to next page when you are ready to view the solution.

 

 

Solution - Create New Import Job

 

vRealize Automation allows you to perform bulk imports of existing virtual machines to be managed by vRealize Automation by uploading a CSV file. In order to make this process much easier, you can generate a CSV file from vRealize Automation by doing so:

NOTE: We have already a working CSV file generated for you that is located in C:\HOL-1890\BulkExport.csv

If you want to find out how to generate your own CSV file for bulk importing virtual machines, you can find out more information here. (opens in a new window)

Log into the vRealize Automation portal as the Cloud Admin:

  1. Navigate to Infrastructure -> Administration
  2. Click on Bulk Imports
  3. Click New

Please proceed to next step

 

 

Solution - Submit CSV

 

  1. Give your import task a name (e.g. Bulk Import 01)
  2. Browse the CSV file that was created (C:\HOL-1890\BulkExport.csv)
  3. Check Ignore managed machines
  4. Click OK

Additional Info: To find out more about what each check boxes do, you can mouse over to the information icon next to it, or you can read more here. (opens in a new window)

 

 

Solution - Check Import status

 

  1. You can check the status of the request here
  2. You can also refresh the status
  3. Click the arrow to scroll to the right (the status column is the far right most column) and view more information of the import task

Only proceed when Status is Completed

 

 

Solution - Import Verification

 

In order to verify that the machine has been imported successfully and assigned to the correct owner:

  1. Click on Infrastructure
  2. Click on Managed Machines
  3. You will see that the virtual machine (import-01) has been successfully imported from vCenter into vRealize Automation and assigned to devuser@corp.local

NOTE: Alternatively, you can login as devuser and you will see import-01 VM in the Items tab

For more information on Bulk Importing virtual machines into vRealize automation, please refer to this document here.

 

VMs fail to complete provisioning


A new script (date.cmd) has been added to the Windows 2012 Blueprint. It is called by the Guest Agent (gugent) within the OS during the time of provisioning. Unfortunately, it seems that the VM deployment is hanging during VM provisioning. It seems that the script is not being triggered during provisioning causing the VM to hang. Since the deployment cannot complete, the provisioning times out and destroys the VM.


 

Launch vRealize Automation

 

Click on the vRealize Automation bookmark

 

 

Login to vRealize Automation as Dev User

 

  1. User Name: devuser
  2. Password: VMware1!
  3. Click on Sign in button

 

 

Request a VM

 

  1. Click on Catalog
  2. Select the Windows Server 2012 Catalog Item and choose Request

 

Choose Submit

 

  1. Click on Requests
  2. View the status of the VM as it deploys.

 

 

Your Challenge!

 

The VM (dev-005) will reside in this state until the provision times out and vRA destroys the VM and cleans up the provisioning.

Log into vCenter by clicking on the link in RegionA -> RegionA vCenter

For this challenge:

  1. You will need to log into the provision VM (dev-005) within vCenter and investigate why the script is not being triggered.

You may now proceed to do your troubleshooting.

Need hints?

View Hint #1 (Hint will open in a new browser window)

View Hint #2 (Hint will open in a new browser window)

You can also view hints on the VMware Technology Network Communities here:

https://communities.vmware.com/docs/DOC-37018

Go to the next page to see the solution.

 

 

Solution

 

The problem that we have run into is that the Guest Agent is not communicating with the IaaS Manager Server.

From this screen, you can see that there is a problem with the SSL certificate.

 

Woah! The SSL certificate is missing. No wonder the VM cannot kick off the script. We will need to fix this in the template. Unfortunately, this VM will need to timeout and be destroyed.

Close the console window to the VM (dev-005) that we are provisioning.

Power on the base-w12-01 template and open a console to it.

 

To reinstall the SSL certificate we will need to rerun the Gugent Preparation script (prepare_vra_template.ps1). The script can be downloaded from the vra software repository. This repository can be located at https://vra-01a.corp.local/software.

For this challenge, the script has been downloaded and staged at C:\HOL-1890. Navigate to this folder using the Windows File Explorer and launch the script: prepare_vra_template.ps1. This step is performed by right clicking the script and choosing Run with Powershell. The powershell script has been modified to run without needing input.

However, if you elect to download and run this script manually, you will need to input the following information:

Once the script has been run, shutdown the virtual machine.

 

Take a new snapshot of the virtual machine for the blueprint.

Our example snapshot was named Fixed Cert.

 

After the snapshot has been created, a Data Collection needs to be performed so that vRA can utilize the new snapshot in the blueprint.

To perform the data collection:

  1. Log out of the vRealize Automation portal and log back in as the Tenant Administrator.
  2. Navigate to the Infrastructure tab, then Compute Resources > Compute Resources on the menu on the left.
  3. Hover over the Triangle to the right of the Compute Resource REGIONA01-COMP01 and select Data Collection from the menu that appears.
  4. In the Data Collection window, locate the Inventory section and select Request Now to start off a data collection.
  5. You can check the status of the data collection by choosing Refresh at the bottom of the window.
  6. When the process has completed, the status will change to Succeeded.

 

The snapshot will need to be replaced in the Blueprint so that the template VM has the proper SSL Cert.

  1. Naviagte to the Design tab.
  2. Select Blueprints in the menu on the left.
  3. Locate the Windows Server 2012 blueprint. Select it.
  4. Click on Edit in the toolbar.

 

  1. In the Blueprint Design Canvas, click on the Windows VM component.
  2. Select Build Information from the menu.
  3. Choose the pulldown for Clone from snapshot:

 

Choose the new snapshot Fixed Cert from the dropdown.

Click Save and then Finish to save the changes to the Blueprint.

 

Log out of the vRealize Automation portal and log back in as the Development User.

Reattempt to deploy a new Windows 2012 VM.

 

You can check the status of the deployment by clicking on the Request tab.

 

You can Refresh the page using the Refresh button at the bottom of the window.

After a few minutes, you will see that the VM deploys properly.

 

 

Conclusion

This lesson was designed to demonstrate how the trust between the vRA Guest Agent (gugent) in the provisioned VM and the IaaS Manager server. When the trust is compromised, you will not be able to trigger scripts within the provision VM using the Guest Agent.

Before proceeding to the next lesson, log out of the vRealize Automation Portal.

 

Collecting log bundles for support


Uh-Oh. Unfortunately, you ran into an issue and needed to call Global Support Services (GSS). It happens to us all. GSS has requested a log bundle for further troubleshooting into your issue. However, after uploading the logs to GSS, they informed you that the bundle was missing logs from the IaaS Server in the log bundle.


 

Launch the Module 4a startup script

 

For this lesson, we have to prepare the lab environment to demonstrate the issue. Minimize the browser to expose the desktop.

  1. Open the Scripts folder located on the Control Center Desktop.
  2. Right click the file labeled "Start Module 4a" and select to Run with Powershell.
  3. Press Enter when the script is Ready.

 

 

Login to the vRealize Automation Virtual Appliance Management Interface (VAMI)

 

Open the chrome browser and enter the URL (http://vra-01a.corp.local:5480) for the vRA VAMI.

The below is a list of credentials that can be used for this lab.

 

 

Validate the Log Bundle

 

Request a log bundle.

  1. Navigate to the Cluster tab.
  2. Click on Create Support Bundle to download a log bundle.

 

Click on Collected bundles... to download the log bundle.

 

Using Windows File Explorer, navigate to the Downloads folder and extract the log bundle.

Once extracted, open the Environment.html file.

 

The Environment.html file will show you the status of the Log Bundle. The red banner over the IAAS server indicates that the logs were not collected.

 

 

Challenge!

For this challenge:

  1. You are to investigate why the IAAS logs are missing from the log bundle.
  2. Fix the issue so that the Log Bundle will collect all logs.

You may now proceed to do your troubleshooting.

Need hints?

View Hint (Hint will open in a new window)

You can also view hints on the VMware Technology Network Communities here:

https://communities.vmware.com/docs/DOC-37018

Proceed to next page only when you are ready to see the solution.

 

 

Solution

 

Without connectivity, IaaS components will not have their logs collected. The connection that is needed for the logs to be collected is the VMware vCloud Automation Center Management Agent service. The service must be installed and running.

Corrective Action:

  1. Using the Remote Desktop shortcut (iaas-01a.rdp) on the desktop, remote into the IaaS Server.
  2. Press Win+R on the keyboard to open the Run window. Type in services.msc to launch the Services Control Panel.
  3. Locate the service: VMware vCloud Automation Center Management Agent.
  4. Select the service and click Start.

Once the service has started, reattempt to Collect a Log Bundle from the vRA VAMI.

 

 

Conclusion

The Management agent is used for vRA to communicate between each of the components within the environment. This is demonstrated primarily during the initial installation of vRA. By stopping the Management Agent or by uninstalling it, the vRA VAMI will no longer be able to communicate to each of the other vRA components to collect logs when they are needed.

 

Module 5 - Cloud Extensibility, Advanced Challenge (45 Minutes)

Introduction


We tip our hat to you if you can resolve this module's challenge around fixing vRealize Automation's cloud extensibility issues. You will be faced with integration issues between vRealize Automation's Event Broker and vRealize Orchestrator workflows.

This Module contains the following lessons:


 

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 you lab has not changed to "Ready", please ask for assistance.

 

Provisioning process is not stopping when an event broker error occurs


You have just recently implemented a use case where a user's request for a virtual machine would have its snapshot taken as a post provisioning task. This actual workflow was created by the integration engineers, while you are responsible for integrating that workflow into vRealize Automation using Event Broker.

Just as you are about to sit back and relax for the day, you got a user running up to you saying his machines that he requested for from vRealize Automation have got no snapshots! You immediately got to work and decided to research and investigate more.

After reading more on vRealize Automation 7's Event Broker functionality here and here you decided to fix it on your own.


 

Launch vRealize Orchestrator Client

 

Note: If you still have your vRealize Orchestrator Client minimized on your desktop, please restore the window and you may proceed to the next step here. Else please follow the instructions as shown.

To launch vRealize Orchestrator:

  1. Locate the vRealize Orchestrator Client shortcut on your Main Console desktop
  2. Double click or hit Enter to launch it

 

 

Login to vRealize Orchestrator

 

To login to vRealize Orchestrator:

  1. Ensure that the Host name is vra-01a.corp.local:443
  2. User name: administrator@vsphere.local
  3. Password: VMware1!
  4. Click Login

 

 

Switching to Design mode in vRealize Orchestrator

 

Once vRealize Orchestrator client has been successfully launched, you need to switch to Design mode:

  1. Click on the dropdown list and select Design

 

 

Exploring vRealize Orchestrator workflow

 

One of your integration engineers has built a workflow that automatically takes a snapshot of a virtual machine after it has been provisioned by vRealize Automation. To find out more about what the workflow operates:

  1. Expand the HOL-1890 folder
  2. Click on the workflow Create a snapshot
  3. Click on Schema to show details on the execution steps in the workflow

NOTE: Do not close or exit from the vRealize Orchestrator Client, just minimize it from the desktop.

 

 

Open Chrome Browser from Windows Quick Launch Task Bar

 

NOTE: If you already have Chrome launched, and logged into vRealize Automation, you may skip this step and proceed by clicking here.

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

 

 

Launch vRealize Automation

 

Click on the vRealize Automation bookmark

 

 

Log into vRealize Automation

 

NOTE: If you are not logged in as cloudadmin user, please Log out of vRealize Automation first before proceeding to login as cloudadmin. If you are already logged in as cloudadmin user, please proceed to next step.

  1. User Name: cloudadmin
  2. Password: VMware1!
  3. Click on Sign in button

 

 

Viewing Administration options

 

Click on the Administration tab

 

 

Click on Events

 

Click on Events

 

 

Viewing Subscriptions

 

  1. Click on Subscriptions
  2. Click on the description text highlighted beside Create a post provisioning snapshot
  3. Click Publish
  4. Make sure that the Status of the subscription is marked as Published and NOT Draft

NOTE: This step activates the workflow subscription that will invoke the vRealize Orchestrator workflow Create a snapshot which you previously saw in the vRealize Orchestrator client.

 

 

Viewing Subscriptions

 

  1. Click on Subscriptions
  2. Click on the description text highlighted beside Set Admin Password
  3. Click Publish
  4. Make sure that the Status of the subscription is marked as Published and NOT Draft

 

 

Login to vRealize Automation as Dev User

 

NOTE: Log out of vRealize Automation as cloudadmin first before proceeding to login as devuser.

  1. User Name: devuser
  2. Password: VMware1!
  3. Click on Sign in button

 

 

Select catalog item

 

  1. Click on Catalog tab
  2. Request for a CentOS 6.6 catalog item

 

 

Submit a Request

 

  1. Click on CentOS_6.6
  2. Set admin password to VMware1!
  3. Confirm the password to VMware1!
  4. Click Submit

 

 

Request Submission status

 

A request acknowledgement will be displayed once you have submitted the request form.

  1. Click OK

 

 

Monitoring the progress of request

 

You can monitor the progress of your request:

  1. Click on Requests
  2. Wait for your request to update its Status from In Progress to Successful or Failed
  3. You can hit the Refresh button to get an update of the status

This usually takes several mins to complete.

 

 

Viewing Items

 

  1. Click on Items
  2. Click on Deployments
  3. Expand the deployment as shown to reveal components
  4. Click on the machine name to view details

 

 

Viewing Machine Details

 

  1. Click on Snapshots

You see that there is no snapshot available. Why would that be? Let's have a look at the workflow run from vRealize Orchestrator.

Please proceed to next step.

 

 

Viewing the workflow run in vRealize Orchestrator

 

NOTE: Please restore your vRealize Orchestrator window if it was minimized previously.

  1. Expand the workflow Create a snapshot to view the workflow execution history
  2. Click on the execution details to find out if the workflow ran successfully or failed

NOTE: This should not happen, if the workflow failed, the provisioning task should also fail. Instead what you are seeing is that vRealize Automation marked the provisioning as Successful

 

 

View the Workflow using the vRA Content Pack in Log Insight

 

The workflow request can be view within the Event Broker Dashboard in Log Insight. Open the Log Insight portal in a new tab from the link in the browser's Bookmark Favorites.

  1. Click on Dashboards
  2. Select the vRA - Event Broker dashboard.
  3. Scroll down to find the vRO workflow runs over time and double-click to enter the Interactive Analytics.

 

 

View the Workflow using the vRA Content Pack in Log Insight

 

The logs show that the Create a snapshot workflow failed.

 

 

Challenge!

For this challenge:

  1. You are to investigate why did the provisioning task completed even though the Create a snapshot workflow failed
  2. Fix the issue where if the workflow Create a snapshot failed, the provisioning task should fail too

You may now proceed to do your troubleshooting.

Need a hint?

View Hint #1

View Hint #2

You can also view hints on the VMware Technology Network Communities here:

https://communities.vmware.com/docs/DOC-37019

Proceed to next page when you are ready to view the solution.

 

 

Solution - Let's investigate on the subscription

 

Before we go into the actual solution, let's have a look at how the subscription was setup again.

 

 

Solution - Blocking Task

 

  1. Click on Details
  2. It seems like this subscription was not flagged as a Blocking task

You must be wondering, what does Blocking mean?

In some scenarios, we need to influence the provisioning process depending on the output of the workflow that is being triggered. To do this, we introduce the concept of blocking subscriptions. In a typical subscription without blocking enabled, events are delivered asynchronously. We often refer to this as a "fire and forget" mode of delivery. Which means once a workflow has fired an event, it continues to run and does not keep track of whether the event was picked up successfully or if the something needed to happen to the workflow.

Blocking subscriptions are different in that they actually pause the the current workflow until they have been fully processed. This allows feedback to be sent to the workflow like throwing an exception during error. Since our workflow here is suppose to cause the provisioning to fail if the vRealize Orchestrator workflow fails, blocking subscriptions will allow us to do just that!

Please proceed to next page.

 

 

Solution - Unpublished the current subscription

 

Note: You would need to be logged in as cloudadmin in order to administer subscriptions.

After navigating to Administration -> Events -> Subscriptions

  1. Click on Published
  2. Click Unpublish

 

 

Solution - Create a new subscription

 

Once you have unpublished Create a post provisioning snapshot

  1. Click New

 

 

Solution - Define Event Topic

 

  1. Click Machine provisioning
  2. Click Next

 

 

Solution - Lifecycle State Name Condition

 

  1. Select Run based on conditions
  2. Select All of the following to match against ALL conditions in the subscription
  3. Select Data -> Lifecycle state -> Lifecycle state name from the menu
  4. Select Equals as the Operator
  5. Select Constant -> VMPSMasterWorkflow32.MachineProvisioned
  6. Click Add Expression to add another expression

Proceed to next page

 

 

Solution - Lifecycle State Phase Condition

 

  1. Select Data -> Lifecycle state -> State phase
  2. If you are not able to see State Phase to be selected, you need to click on the horizontal scrollbar to see the vertical scrollbar
  3. Select Equals as the Operator
  4. For the value, choose Constant -> PRE

Afterwards, Click Add Expression to add another expression

Proceed to next page

 

 

Solution - Machine Type Conditions

 

  1. Select Data -> Machine -> Machine type
  2. Select Equals as the Operator
  3. For the value, choose Constant -> Virtual Machine
  4. Click Next

 

 

Solution - Select a workflow

 

  1. Under Select a Workflow, choose Orchestrator -> HOL-1890 -> Create a snapshot workflow
  2. Click Next

 

 

Solution - Subscription Details

 

  1. Name your new subscription (can be any name you like)
  2. Check Blocking
  3. Type in 1 for Priority
  4. Click Finish

Note: Priority allows you to define the order in which blocking subscriptions run. If an event topic has multiple blocking workflow subscriptions with the same priority, the subscriptions are then processed in alphabetical order based on the subscription name. You can also specify a Timeout value to determine how long should a workflow be running before it is failed.

 

 

Solution - Publish the subscription

 

  1. Click on Draft
  2. Click Publish

You can now request for a new catalog item, and if the workflow fails, the provisioning will be marked as failed too.

For more information about blocking subscription, you can read in details over here. (open in new window)

 

 

Solution - Request for a new catalog item

 

Log out as cloudadmin and log in as devuser to request for a new catalog item.

  1. Click on Catalog
  2. Click Request for CentOS 6.6

 

 

Solution - Fill in request details

 

  1. Click on CentOS_6.6
  2. Fill in admin password (e.g. VMware2!)
  3. Click Submit

 

 

Solution - Check Request progress

 

You can monitor the progress of your request:

  1. Click on Requests
  2. Wait for your request to update its Status from In Progress to Failed
  3. You can hit the Refresh button to get an update of the status

This usually takes 2-5 mins to complete.

 

 

Solution - Verifying vRO workflow

 

You can now maximize or restore your vRealize Orchestrator client to check on the workflow run progress too.

You should see that the vRealize Orchestrator workflow (Create a snapshot) has failed.

Proceed to next page

 

 

Solution - Verifying vRA provisioning status

 

You can restore your Chrome browser and vRealize Automation tab (Ensure you are logged in as devuser)

  1. You will see that the provisioning request will Fail
  2. You have the option to click on the request number to view the error exception that has been passed from vRealize Orchestrator, to vRealize Automation.

 

 

Review

Now that you have solved this challenge, let us review what we have accomplish so far.

We have learnt that in order for us to wait for the result of an Orchestrator workflow before proceeding on with the provisioning process, we need to create a blocking task subscription. Event Broker allows the triggering of a blocking task, which can stop a given workflow and hand information off to an external system, or pause to wait for a response from the external system. Based on the response, Event Broker can determine how to proceed with the provisioning request.

In this challenge, we needed a way for us to stop the provisioning request should the vRealize Orchestrator workflow failed to take a snapshot of the VM. By setting up a blocking task subscription, now Event Broker will wait for the response or outcome of the vRealize Orchestrator workflow before deciding to proceed or fail the workflow.

Please proceed to next page.

 

 

Congratulations!

You have now fully grasped the how to apply Event Broker to enhance lifecycle automation with vRealize Automation. Hopefully this challenge will give you much more ideas on how you can apply these concepts to your vRealize Automation projects.

Here are some additional readings on Event Broker that you will find useful:

 

 

Conclusion

Another round of Congratulations goes out to you! As a vRA Administrator, you have been very successful maneuvering through the various scenarios and applying the appropriate solutions. You have successfully completed all challenges within the vRealize Automation Challenge Lab. You may end the lab.

 

Post provisioning task extensibility


Alright, you've solved the previous challenge and now your event broker subscriptions are working properly. However, there's still something wrong with the workflow. The integration engineer that built the workflow, unfortunately, is on vacation and you should probably wait for him to come back and fix it.

However, your boss is pressuring you to get this fixed as soon as you can since you are the VMware expert within Rainpole Enterprise Inc. And without a doubt, you are going to take a look at the problem.

NOTE: Do not attempt this challenge if you have not completed "Provisioning process is not stopping when an event broker error occurs" challenge.


 

Launch vRealize Orchestrator Client

 

Note: If you still have your vRealize Orchestrator Client minimized on your desktop, please restore the window and you may proceed to the next step here. Else please follow the instructions as shown.

To launch vRealize Orchestrator:

  1. Locate the vRealize Orchestrator Client shortcut on your Main Console desktop
  2. Double click or hit Enter to launch it

 

 

Login to vRealize Orchestrator

 

To login to vRealize Orchestrator:

  1. Ensure that the Host name is vra-01a.corp.local:443
  2. User name: administrator@vsphere.local
  3. Password: VMware1!
  4. Click Login

 

 

Switching to Design mode in vRealize Orchestrator

 

Once vRealize Orchestrator client has been successfully launched, you need to switch to Design mode:

  1. Click on the dropdown list and select Design

 

 

Exploring vRealize Orchestrator workflow

 

You know from previous challenge that the workflow does not work properly, therefore you are to investigate what went wrong:

  1. Expand the HOL-1890 folder
  2. Expand Create a snapshot
  3. Click on the execution history to view details of the workflow task
  4. Click on Logs to show the error log of the workflow execution

For this challenge:

  1. You are to investigate and identify what is wrong with the workflow
  2. Fix the workflow so that after the machine has been provisioned from vRealize Automation, a snapshot will be taken from the virtual machine

You may now proceed to do your troubleshooting.

Need a hint?

View Hint #1

View Hint #2

You can also view hints on the VMware Technology Network Communities here:

https://communities.vmware.com/docs/DOC-37019

 

 

View the workflow in Log Insight

 

You can view the details from going to the Interactive Analytics of the vRA Content Pack dashboard vRO Workflows Over Time. This dashboard view will show each workflow, which can display the results of whether it completed or failed.

 

Proceed to next page when you are ready to view the solution.

 

 

Solution

 

In this particular challenge, it seems that when we are getting the virtual machine object from vRealize Automation using a scriptable task, we failed to pass this object to the next workflow task, which requires an input type of virtual machine in order to create a snapshot.

To solve this challenge:

  1. Login to vRealize Orchestrator as administrator@corp.local
  2. Switch to Design Mode
  3. Navigate to Orchestrator -> HOL-1890 -> Create a snapshot
  4. Edit the workflow
  5. Click on Schema
  6. Edit the Scriptable task
  7. Click on Visual Binding
  8. Drag vcVM from Scriptable task to vcVM of Out Attributes (see above)
  9. Click Close
  10. Click Save and Close
  11. Click Continue anyway

You may now login as devuser to request for a new virtual machine and the workflow should now be able to take a proper snapshot once the machine have been provisioned.

 

Appendix

Module 2: Cloud Administration, Basic Challenge


The following pages contain hints and workarounds for Module 2: Cloud Administration, Basic Challenge.


 

Module 2, First Challenge, Hint #2

The Development Manager, as well as all individual users within a Business Group, has the ability to set their email preferences for their own individual accounts. These settings are not managed by the Tenant Administrator -- rather the individual user has control over this preference.

Click here to return.

 

 

Module 2, Second Challenge, Hint #3

The host that the template was placed on has resources that are not being consumed by vRealize Automation. You should look at moving the template or host into resources that are being consumed by vRealize Automation.

Click here to return.

 

 

Module 2, Fourth Challenge, Blueprint Workaround - Part 1

 

To be able to provision a virtual machine from the catalog item Windows Server 2012 - Patched, we need to remove the customizationspec configuration within the blueprint.

Log out of the vRealize Automation Portal and log back in as the Tenant Administrator (cloudadmin).

  1. Select Design > Blueprints
  2. Click on the Windows Server 2012 - Patched blueprint to edit.

 

 

Module 2, Fourth Challenge, Blueprint Workaround - Part 2

 

  1. In the Design Canvas, click on the vSphere Machine Object called Windows2012.
  2. Then select the Build Information tab.
  3. Locate the CustomizationSpec at the bottom. Remove the entry labeled Windows 2012.
  4. Click Save. Click Finish.

 

 

Module 2, Fourth Challenge, Blueprint Workaround - Part 3

 

Log out of the vRealize Automation Portal and log back in as the Development Manager (devmgr).

  1. Open the Catalog tab.
  2. Select the Windows Server 2012 - Patched catalog item by clicking Request.
  3. Accept all defaults and provision a VM by clicking Submit. (not pictured)

At this point, the virtual machine should provision normally and successfully complete.

Click here to return.

 

Module 3: Cloud Extensibility, Basic Challenge


The following pages contain hints for Module 3: Cloud Extensibility, Basic Challenge.


 

Module 3, First Challenge, Hint 1

There is nothing wrong with the vRealize Orchestrator workflow "Add a computer in an OU".

You might want to try looking elsewhere.

Click here to return.

 

 

Module 3, First Challenge, Hint 2

You might want to look into the "Add a computer in an OU" event subscription.

Do the conditions makes sense to you?

Click here to return.

 

 

Module 3, Second Challenge, Hint 1

If you are trying to troubleshoot the vRealize Orchestrator workflow "Change admin password". You should trust your integration engineers more, look elsewhere.

Click here to return.

 

 

Module 3, Second Challenge, Hint 2

Look more carefully into the conditions of the event subscription, do you see something amiss?

Click here to return.

 

 

Module 3, Third Challenge, Hint 1

You might want to log in as cloudadmin into vRealize Automation and navigate to Design -> XaaS -> Resource Actions.

Click here to return.

 

 

Module 3, Third Challenge, Hint 2

Remember to check the mapping of the vRealize Orchestrator input parameter, to the vRealize Automation object when you are creating the resource action.

Click here to return.

 

 

Module 3, Third Challenge, Hint 3

You are almost there. But do not forget to publish the resource actions that you just created.

And also remember that you also need to entitle the "Development Services" entitlement to the action.

Click here to return.

 

Module 4: Cloud Administration, Advanced Challenge


The following pages contain hints for Module 4: Cloud Administration, Advanced Challenge.


 

Module 4, First Challenge, Hint 1

Only a user with the tenant admin role can make grant permissions to resource actions. You might want to log in as cloudadmin since this account holds the tenant admin role.

Click here to return.

 

 

Module 4, First Challenge, Hint 2

Are you looking at vRealize Automation entitlements? If you are not, you might want to go there and have a look.

Click here to return.

 

 

Module 4, Second Challenge, Hint 1

 

Have you heard of vRealize CloudClient? That is a tool you might want to check out. There is a CloudClient shortcut located on the Main Console desktop.

Click here to return.

 

 

Module 4, Second Challenge, Hint 2

Not seeing the catalog item appear? Have you published the blueprint after you imported? What about assigning the catalog item to a service?

Click here to return.

 

 

Module 4, Third Challenge, Hint 1

Lost? You can have a look at the documentation here.

Click here to return.

 

 

Module 4, Third Challenge, Hint 2

 

Still struggling with creating the csv file? We already have one pre-generated for you. You can locate the CSV at C:\HOL-1890\BulkExport.csv

You can open the CSV file and have a look at the format and details of the CSV like VM name, Owner.

Click here to return.

 

Module 5: Cloud Extensibility, Advanced Challenge


The following pages contain hints for Module 5: Cloud Extensibility, Advanced Challenge.


 

Module 5, First Challenge, Hint 1

Do not troubleshoot the workflow, you are supposed to ensure that if the workflow fails, the provisioning process should fail as well.

Click here to return.

 

 

Module 5, First Challenge, Hint 2

Try looking into defining an event broker subscription as blocking. You can find more documentation help here.

Click here to return.

 

 

Module 5, Second Challenge, Hint 1

You do not need to modify any of the javascript.

Click here to return.

 

 

Module 5, Second Challenge, Hint 2

Try looking into the Visual Bindings of the "Scriptable Task" within the workflow. You might find something out of place.

Click here to return.

 

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-1890-01-CHG

Version: 20180202-123519