The OneFuse Extensibility Management Platform accelerates vRealize Automation 8 (vRA8) deployment and blueprint development of traditional IaaS workloads. Deploying OneFuse alongside vRA8 can dramatically improve time to value for traditional virtual machine workloads by providing policy-driven integrations and use-case standardization, 60% or greater reduction in the amount of custom code required to meet your requirements, and simplified user input for each of your blueprints.
While traditional machine workloads are still very important to our customers, we are also finding that other services are becoming increasingly more important. This can prove to be challenging in due to the Event Subscriptions in vRA8 are not similar across different resource types on the canvas. To write integrations that live inside of the life cycle for each individual resource type would be extremely time consuming, if not impossible.
In addition to the above challenge, quite a few of our customers have asked for the capability to submit a request to OneFuse from the vRA catalog itself, something like requesting a DNS record (via a OneFuse DNS policy) from vRA.
With the release of OneFuse 1.2, we are happy to announce the availability of OneFuse Custom Resources for vRealize Automation 8. As part of the 1.2 release we have included the ability to consume any of the OneFuse policy driven modules natively from the vRA8 canvas (note that this is a beta feature as of the time of this writing). For each of the OneFuse modules, you now have the capability to drag and drop any of the OneFuse modules directly onto the vRA blueprint canvas. The following modules are supported:
- Deployment Names (renaming deployments with OneFuse Naming policies to standardize deployment names)
- Active Directory
- Property Sets (New and Existing)
- Ansible Tower
Allowing OneFuse integrations to be consumed from the vRA canvas allows you to both leverage OneFuse to drive every other integration on the canvas (eg. providing a standardized name for S3 buckets) and to be able to offer OneFuse policies something that you can expose to users to request from the catalog. For example, if a network admin needs to install a new network device (switch/router) on the network, you can now generate a blueprint in the vRA catalog that allows the network admin to request a standardized hostname, IP address, and DNS record creation as part of a single blueprint in vRA.
In addition, every OneFuse Custom Resource is capable of leveraging the Property Toolkit to consume integrations and drive dynamic outcomes in a standardized way.
Rather than trying to explain in depth what this looks like, I picked a pretty straightforward example blueprint to showcase how OneFuse can better standardize the provisioning of an S3 bucket. In this blueprint, OneFuse is:
- Renaming the vRA Deployment Name so that it is standardized
- Generating a standardized name for the S3 bucket that is both globally unique and meaningful
- Providing centralized configurations via the Property Toolkit to drive the S3 bucket region and account defined inside of a Static Property Set.
We will be doing some deeper dives into this new feature over the coming weeks. I am really excited to see how customers adopt OneFuse Custom Resources for vRealize Automation 8 and we would be interested to hear your feedback.
Want to try out OneFuse with vRA for yourself? Check out the WWT Hands on Lab Accelerating vRealize Automation 8.x with OneFuse.