vRealize Automation is a highly complex enterprise automation framework. Once implemented, vRealize Automation offers substantial opportunity for the enterprise to reduce the complexity of their IT environment, streamlining IT processes, and delivering a DevOps-ready automation platform. Getting there, however, can prove to be difficult, highly complex, time-consuming, and expensive. Has your organization licensed vRealize Automation, but your implementation is stalled or going far slower than anticipated? Both are common scenarios, and both drastically reduce (eliminate?) the potential ROI that vRealize Automation promises and can deliver.
To help any enterprise organization get their vRealize Automation deployment headed in the right direction, here we offer up six solutions for jumpstarting your vRealize Automation deployment. These solutions are functions within the SovLabs Plugin for vRealize Automation 7.x.
Six Solutions for Jumpstarting Your vRealize Automation Deployment
1. Config AD — Using the SovLabs Active Directory module, you can update an Active Directory configuration to create and remove a “build” OU with a templated name. When you do this, a template is added to the final OU name. A build “OU” is used during provisioning, and the virtual machine will be moved to the final OU when provisioning is completed.
2. BaaS 1 — Configure a vRealize Automation blueprint to leverage the SovLabs Backup plugin, including dynamically selecting the correct backup vendor for the environment. Our Backup-as-a-Service modules offer support for Cohesity, Rubrik, and Veeam BaaS solutions.
3. Custom Naming Apply — View the Custom Naming property group for a defined Naming Standard and apply it to a desired blueprint.
4. Custom Naming Selection — View a Custom Naming property definition used to define the name in the Naming Standard.
5. Custom Naming Sequence — View a Naming Sequence including the unique key and current name database. View a Naming Sequence, highlight the unique key definition, current and next assigned values.
6. Custom Naming Standard — View a Naming Standard including the name template and selected Naming Sequence. View a Naming Standard, highlights the template definition, associated Naming Sequence(s) and Naming Validator(s).
The Alternative Is More Custom Code
These six solutions are a start, but they address some of the most common requirements for getting early value and ROI out of your vRealize Automation deployment. The alternative is to spec, create, and support your own custom, home grown solutions. While custom code can get you just about any solution you want, it takes time, usually about twice as much time as you anticipate.
Request a custom demo of the SovLabs Plugin for vRealize Automation.