Exploring the echoes reverberating through time left by the technology of yesterday as we embrace the technology of tomorrow.
In this article we are going to walk through using OneFuse to name a deployed machine in vRA8. To do this we will create a new blueprint within vRA8 and call upon the OneFuse to name it using the naming policy we created as part of “Creating a OneFuse Naming
Editor's note (2026): The methodology described in this post is what I now call Decisions as Code. Property Toolkit was the OneFuse implementation of the same idea. See "Decisions as Code" for the current framing. Introduction The OneFuse Extensibility Management Platform accelerates vRealize Automation 8 (vRA8)
In this article, I’m going to demonstrate how easy it is to install the OneFuse workflow package into vRA8. Once the workflow package is installed you will be able to take advantage of all that OneFuse has to offer within vRA8. *Note that this same workflow package will also
In this article, I’m going to walk you through how simple it is to deploy the OneFuse integration platform. The OneFuse appliance can be deployed and ready to configure in as quick as 5 minutes. Have a look at the below list of prerequisites you will need to deploy
Editor's note (2026): The methodology described in this post is what I now call Decisions as Code. Property Toolkit was the OneFuse implementation of the same idea. See "Decisions as Code" for the current framing. Introduction One of the things that we are often asked by
In this article, I am going to walk you through creating a Naming Policy within OneFuse. Before we begin, I want to go over why OneFuse Naming is a game changer for organizations. Many of you reading this may be thinking you don’t need an integration for naming. Read
In my previous article “Deploying the OneFuse Appliance”, we deployed OneFuse and was able to login to begin the configuration. In this article, we are going to configure a few useful items within the OneFuse platform that will be used when we begin to configure the modules for specific integrations.
Editor's note (2026): The methodology described in this post is what I now call Decisions as Code. Property Toolkit was the OneFuse implementation of the same idea. See "Decisions as Code" for the current framing. Introduction This post will build upon the prior post, Introducing OneFuse
You might read the title and think to yourself ''Why would I want to use vRO with Wink?" Well there are a number of reasons. I created this because being a
Over the weekend Roman, Grant, John and I released a significant update to the platypus project, which is essentially a very simple and elegant way to prov
You have read all the announcements about vSphere 6.0 Update 2 being released and now you want to upgrade. Maybe you haven’t tried out the embedded web ui
It dawned on me that you all may not be aware of the VMware Sample Exchange . The sample exchange is a place where you can go to find samples shared by man
