In this article we are going to walk through using OneFuse to generate a name for use in a Terraform configuration. To do this we will create a new Terraform configuration that uses the OneFuse provider data source and resource for the naming policy we created as part of Creating
In this article we are going to create a vRA8 blueprint that uses the OneFuse Active Directory module to provide AD integration for provisioned workloads. We will use the Active Directory (AD) policy that we created in the “Creating a OneFuse Active Directory Policy” article. I will also be leveraging
In this article we are going to add OneFuse DNS support to a vRA8 blueprint. If you have been following my previous articles you probably have an idea of how this is going to work. We are going to build upon the examples from previous articles by leveraging the same
The OneFuse Active Directory (AD) module offers features for placing deployed computer objects into the appropriate Active Directory (AD) organizational units (OU). This includes support for pre-build organization units (OU), final Organizational Unit placement, as well as placement of computer objects into Active Directory (AD) security groups. Active Directory (AD)
Automating the creation of DNS records is becoming increasingly more important in the enterprise. One bad record or typo can cause outages or mission critical services. In this article, I’m going to walk through creating a DNS Policy in OneFuse using Infoblox as a DNS provider. OneFuse DNS Features
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
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
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
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.
