Many of you have utilized the Custom Hostname module that has been made available by Tom Bonanno here on Dailyhypervisor. Those that use have probably noticed that it is no longer maintained. This is because there are supportable modules available like the one I’m writing about now by SovLabs. The Sovlabs module offers more flexibility and is a supported product making it a best of breed solution for this task. Whats even better is their is a common framework that exists within the SovLabs platform that greatly extends the capabilities of each module. More of the framework to come. For now let’s go ahead and configure the custom hostname module.
Within the SovLabs custom naming module hostnames are broken in to two parts. A Naming Sequence and a Naming Standard.
Naming sequences are exactly exactly what they sound like. They basically define how are we going to sequence the names that are created. Sounds basic right? Well SovLabs has taken sequencing to a whole new level. Most of you are probably familiar with using a standard decimal based sequence that might look like host001, host002, and so on. SovLabs has added the ability to use HexaDecimal, Octal, and Pattern based sequences for your naming needs. Pattern based sequences are insanely powerful. Pattern naming sequences can contain Decimal, HexaDecimal, Octal, Binary, and Alpha. Below are an examples of what you can achieve with Pattern Based naming sequences:
Continue reading “vRA 7.3 – Configuring SovLabs Custom Naming Module”
In my previous article about the SovLabs plugin I covered some pre-requisites and sent you over to the SovLabs documentation to finish the installation. Once you have installed the vRO plugin using the vRO Control Center you will go to your vRO Client and see a new folder that has all the Sovlabs vRO modules.
Continue reading “vRA 7.3 – Configuring the SovLabs Plugin”
If you haven’t read Part 1 of this article you will want to go back and read it before you proceed. In part 2 we will build on the installation that we performed in part 1. Let’s just dig right in and get started.
How this integration works
Configuring the integration to use native vRA authentication requires the user to login to ServiceNow and vRA both. When the user logs into ServiceNow they are redirected to the vRA Login page and was logged in they are then redirected back to ServiceNow. This allows requests the user makes to be passed to vRA as that user. The main difference between this and the SAML (ADFS) integration is the user only need to login to vRA the very first time they use it and never again as the user is auto-magically logged in to vRA in the background using the SAML token. This is a great option for testing the integration without having to touch your Identity Management configuration.
Continue reading “vRA 7.3 – Installing and configuring vRA plugin for ITSM – ServiceNow – Part 2”
It seems like everyone these days wants to use ServiceNow as their catalog for vRA. It use to be that everyone just wanted to create or update CI records. Before I get into the weeds on how to get vRA and ServiceNow talking together I wanted to take a few minutes to discuss the integration, the pros, the cons, and it’s limitation.
Continue reading “vRA 7.3–Installing and configuring vRA plugin for ITSM–ServiceNow–Part 1”
There are lots of reasons to want to export and import blueprints from one vRA instance to another. My current motives are to move blueprints from my vRA 7.2 environment to my newly deployed vRA 7.3 environment. In vRA 7.3 their is a great new free feature available, the Code Stream Management Pack for IT Devops that is free. However if you are running a pre vRA 7.3 environment you may want to get that content from that environment backed up so you can use it in another instance. Cloud Client is a great option.
You can download Cloud CLient 4.4.0 here. Continue reading “Using the vRA Cloud Client to export and import blueprints”
There’s a known issue when you have both vRealize Automation and vRealize Business 7.x integrated when you have a newly created blueprint to deploy it may fail with an error “Cannot calculate cost. Contact your system administrator to review the vRA appliance logs.” Typically this means vRB hasn’t run a cost calculation on the new blueprint to determine the cost of the blueprint. You either have to wait up to 12 hours for the cost collection to run or you can manually force a collection by triggering a vRA Data Collection and a Cost Calculation as shown below.
Continue reading “VMware vRealize Automation – vRA7 and vRB7 – Automate Cost Calculations”
vRA has a great UI for provisioning VM’s, but with developers needing infrastructure on demand and wanting to have the ability for continuous integration. With the new and updated vRA API’s you can now easily code your own deployment scripts or recipes and integrate with your own run books and still get the the governance and lifecycle management that vRA has to offer. Continue reading “VMware vRealize Automation – vRA7 – Infrastructure as Code (IaC)”
vRA 7 introduced a number of new and very useful features such as unified blueprints, software components, event broker, and others. The event broker however has proven itself to be one of the most power new features we have seen in some time. How so you ask? Well if you have been working with vRA for any period of time you will remember the old way of triggering external workflow executions such as those run by vRO. If you have been using vRA for a really long time you will remember back before vRO when vRA wasn’t even vRA and run nothing but .Net workflows, but we won’t go back that far.
Continue reading “VMware vRealize Automation – vRA7 – The dawn of the vRealize Automation 7 Event Broker”