Vra7

Upgrading your vRealize Automation instance has some times been a painful exercise. But this was in the early days after VMware purchased the product from DynamicOps. It’s taken a while, but the upgrade process has improved for each and every version, in my opinion, and 7.5 is no exception. If you’re on a previous version, here is a quick rundown on the upgrade process from 7.4 to 7.5. Note: As always, please read the the official upgrade documentation. It includes prerequisites and steps that should always be followed. https://docs.vmware.com/en/vRealize-Automation/7.5/vrealize-automation-7172732to75upgrading.pdf ...

Preventing blueprint sprawl should be a consideration if you’re building out a new cloud through vRealize Automation. Too many blueprints and your users will be confused by the offerings and the more blueprints, the more maintenance needed to manage them. We’ve had custom methods for managing sprawl up until vRA 7.3 was released. Now we have some slick new methods right out of the box to cut down on the number of blueprints in use. These new out of the box configurations are called Component Profiles. ...

vRealize Automation version 7.3 dropped a few weeks ago and you’re really excited about the new improvements that have been made with the platform. Release Notes for version 7.3 You’ve gone through the upgrade process which is constantly improving I might add but once you log in you find out that your endpoints that you spent so much time building are now missing. Kind of like the ones in my screenshot below. ...

vRA is great at deploying servers in an automated fashion, but to really use the built in functionality for an organization some additional information should be requested to properly place the workloads in the environment. This post covers how to ask users for the correct information to properly determine the placement location of new server workloads. Cluster Placement The first placement decision that needs to be made is which cluster the workload should be placed on. This can be done with reservations and reservation policies but often comes with some blueprint sprawl. We’d like to be able to ask the requester which environment the workload should be placed on. To specify a cluster (which could include a cluster on a different vCenter or datacenter) we’ll modify an xml document stored in the IaaS Server(s) which will describe our datacenters. In my example I’ve got two clusters in a single vCenter named “Management” and “Workload”. My clusters are shown below. ...

vRealize Code Stream is a tool that is used to operationalize infrastructure code blueprints for release management. Code Stream plugs into vRealize Automation and includes a testing framework though Jenkins and vRealize Orchestrator as well as using JFrog Artifactory and Xenon for storing artifacts. This post is used to organize several blog posts on helping you to get started with vRealize Code Stream and Houdini. Setting up Code Stream and Jenkins Setting up Code Stream and Artifactory Installing vRealize Code Stream for IT DevOps Configuring Endpoints for vRealize Code Stream for IT DevOps Using vRealize Code Stream for IT DevOps Unit Testing with vRealize Code Stream for IT DevOps Official Documentation: vRealize Code Stream Information Center VMware vRealize Code Stream Management Pack for IT DevOps Installation Guide

In previous posts we covered how to install, configure and setup vRealize Code Stream Management Pack for IT DevOps (code named Houdini) so that we could get to this point. During this post we’ll take one of our vRA blueprints in the development instance and move it to the production instance. Let’s get started. To set the stage, here is my development instance where I have several blueprints at my disposal. Some of them even work! (That was a joke) For this exercise, I want to move the “Server2016” catalog from my development instance to my production instance because I have it working perfectly with my vSphere environment. ...

In the previous post we covered the architecture and setup of the vRealize Code Stream Management Pack for IT DevOps (also known as Houdini). In this post we’ll cover how we need to setup Houdini’s endpoints so that we can use them to release our blueprints or workflows to other instances. Remote Content Server Endpoint Setup To setup our endpoints we can use nicely packaged blueprints right in vRA. It’s pretty nice that our setup deployed some blueprints for us to use, right in the default tenant of our vRA server. Login to the vRA default tenant with your Houdini Administrator that you setup in part 1. Then go to the catalog and request the “Add Remote Content Endpoint” under the “Administration” service. A remote content server (RCS) is a vRA appliance that will cache your packages. It’s a pretty useful thing to have if you’ve got vRA appliances in different sites and you need to move vSphere VMs or other large objects over a WAN. Future releases can be copied from the remote content server instead of always copying from the source. ...

Deploying blueprints in vRealize Automation is one thing, but with all things as code, we need to be able to move this work from our test instances to development and production instances. It’s pretty important to be sure that the code being moved to a new instance is identical. We don’t want to have a user re-create the blueprints or workflows because it’s prone to user error. Luckily for us, we have a solution. VMware has the vRealize Code Stream Management Pack for IT DevOps which I though about nicknaming vRCSMPITDO but that didn’t really roll off the tongue. VMware previously nicknamed this product “Houdini” so for the purposes of this post, we’ll use that too! This article will kick off a few more posts on using the product but for now we’ll focus on installing it. ...

As of vRealize Automation 7.2, you can now deploy workloads to Microsoft Azure through vRA’s native capabilities. Don’t get too excited here though since the process for adding an endpoint is much different than it is for other endpoints such as vSphere or AWS. The process for Azure in vRA 7 is to leverage objects in vRealize Orchestrator to do the heavy lifting. If you know things like resource mappings and vRO objects, you can do very similar tasks in the tool. ...

If you’re trying to get started with vRealize Automation and don’t know where to get started, you’re in luck. Pluralsight has just released my course on “Getting Started with vRealize Automation 7”, which will give you a great leg up on your new skills. In this course you’ll learn to install the solution, configure the basics, connect it to your vSphere environment and publish your first blueprints. The course will explain why you’d want to go down the path of using vRA 7 in the first place and how to use the solution. ...