VMworld is often used to share what we’ve been up to since this time last year and to set the technology bar for things to come. I can’t help but feel there’s something different about this one. The mood this year is reminiscent of the early VMworld’s I attended as a customer. I was eager to get into the middle of all the action and VMworld set the tone for what that would be. They were simpler times then, but the energy was contagious and the technology fundamentally changed the landscape. If you’re attending VMworld in Vegas or Barcelona this year, be ready to experience a renewed energy, strategy and in-your-face innovations (for a lack of better words).…
Oh my how time flies. It was just about 6 months ago that I was blogging about the release of vRA 7.2 and all the awesomeness within. Since then, VMware’s Cloud Management Business Unit has been hard at work developing, testing, tweaking and innovating towards the next big release. Today, I’m happy to announce the general availability of vRealize Automation 7.3. It’s an incremental release (i.e. a “dot” release), but don’t be fooled. Here you’ll learn just how much “umph” a .1 can have.
This release continues the trend of delivering awesome innovations, improved user experience, and greater / deeper integration into the ecosystem its managing.…
The IaaS Fabric is made up of all the infrastructure components that are configured to provide aggregate resources to provisioned machines and applications. This is represented by several logical constructs that are configured to identify and collect private and public cloud resources (Endpoints), aggregate those resources into manageable segments (Fabric Groups), and sub-allocate hybrid resources (Reservations) to the consumers (Business Groups).
In this chapter, we’ll walk through the end-to-end details of building out the IaaS Fabric — on vSphere — to support machine provisioning.
- Configure Roles and Permissions
- Add (vSphere) IaaS Endpoint
- Add vRO IaaS Endpoint
- Create a Fabric Group
- Create a Custom Group
- Create Machine Prefixes
- Create (2x) Business Groups
- Create External Network Profiles
- Create (2x) resource Reservations
vRealize Automation 7.2 added native support for Microsoft Azure as a cloud Endpoint. This allows customers to quickly add their subscribed Azure resources to vRA for management and consumption. Azure is the latest addition to the list of native IaaS Endpoints, but the integration takes a different approach from the traditional IaaS Endpoints. For starters, Azure integration is built entirely on vRA’s native extensibility platform vs. the traditional [.net] engine. Likewise, the Azure endpoint is added to vRA as an extensibility endpoint, unlike most other native endpoints that are configured in the Infrastructure section.
Behind the scenes, vRA heavily leverages vRealize Orchestrator (vRO) and a set of OOTB workflows to orchestrate various Azure functions. …
Welcome to the vRealize Automation 7.2 Detailed Implementation VIDEO Guide. This is a collection of all the videos making up the full vRealize Automation 7.2 Detailed Implementation Guide.
The guide (and these videos) was put together to help you deploy and configure a highly-available, production-worthy vRealize Automation 7.2 distributed environment, complete with SDDC integration (e.g. VSAN, NSX), extensibility examples and ecosystem integrations. The design assumes VMware NSX will provide the load balancing capabilities and includes details on deploying and configuring NSX from from scratch to deliver these capabilities.
Be sure to refer back to the full guide for detailed configuration steps or more info on any given topic.…
Next we’ll be configuring load balancing and high availability policies for the distributed components. An NSX Edge Service Gateway (ESG) will be providing the load balancing and availability services to vRA as an infrastructure service. vRA supports In-Line and One-Arm load balancing policies. This implementation will be based on an In-Line configuration, where the vRA nodes and the load balancer VIPs are on the same subnet.
(If you do not plan on using NSX for HA services, you can skip this configuration)
The vRA Load Balancing Guide provides additional details and load balancing guidelines for NSX, F5, and NetScaler.
The Deployment Wizard is invoked by logging into the primary VA’s Virtual Appliance Management Interface (VAMI) using the configured root account. Once logged in, the admin is immediately presented with the new Deployment Wizard UI. The wizard will provide a choice of a minimal (POC, small) or enterprise (HA, distributed) deployment then, based on the desired deployment type, will walk you through a series of configuration details needed for the various working parts of vRA, including all the windows-based IaaS components and dependencies. For HA deployments, all the core components are automatically clustered and made highly-available based on these inputs.
In both Minimal and Enterprise deployments, the IaaS components (Manager Service, Web Service, DEMs, and Agents) are automatically pushed to available windows IaaS servers made available to the installer thanks to the management agent.…