In this article, we are going to create a vRA8 blueprint that uses the OneFuse IPAM module to provide IPAM integration for provisioned workloads. We won’t just be supplying IP information to vRA8 in this example, OneFuse will determine the network placement as well. We will have a future
Overview This article will cover the method of creating OneFuse IPAM Policies using templated properties driven by OneFuse Static Property Sets (SPS). Considerations Simplifying the OneFuse Platform to use a single IPAM Policy is one method of calling a specified network driven by other properties from the request inputs. This
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. Leverage Property Toolkit capabilities for vRealize Automation 8 with OneFuse as
Overview Follow the below steps to reset the password for the admin account in the OneFuse Appliance Considerations This can also be done for local accounts created in the OneFuse Appliance Procedure Reset the password via SSH * SSH to your OneFuse instance * Run the following command /opt/cloudbolt/manage.py
Overview To assist with troubleshooting efforts, the full logs may need to be exported and viewed. This article will cover the path to the OneFuse Platform Job Logs. Considerations SSH or WinSCP * WinSCP Latest Download: https://winscp.net/eng/download.php Procedure SSH or SCP to the following locations Log
OneFuse IPAM policies have some special qualities that make managing IPAM integrations very easy, flexible, and portable. IPAM policies in OneFuse define the network or networks they represent abstracted from the actual IPAM provider. This offers many benefits over network definitions that are tightly tied to a specific provider. This
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
