In this article, we are going to create a vRA8 blueprint that utilizes 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 article on using intelligent placement decisions and dynamic assignments within OneFuse as well as using vRA to drive network placement with OneFuse using vRA network profiles and constraint tags.Continue reading “vRA8 with OneFuse: IPAM Integration”
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.Continue reading “Creating a OneFuse Active Directory Policy”
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 blueprint that we created in the article “vRA8 with OneFuse: IPAM integration”.
By the end of this article, we will have a blueprint that leverages OneFuse to generate a name, assign Network/IP Address as well as create DNS records for the deployed machine. Although these examples are simple and static, they are setting the foundation for future articles where we will dive into creating more flexible and dynamic blueprints.Continue reading “vRA8 with OneFuse: DNS Integration”
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.Continue reading “Creating a OneFuse DNS Policy”
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.Continue reading “Installing the OneFuse Workflow Package into vRA8”
In the “Getting Started with the OneFuse Property Toolkit” article we looked at ways the property toolkit can be leveraged to help standardize configurations across platforms. We also look at a few of the capabilities that it offers. In this article we are going to look at some of the ways the Property Toolkit can be utilized within vRA8.Continue reading “vRA with OneFuse: Property Toolkit”
The OneFuse Property Toolkit is the Swiss army knife of the OneFuse Platform
The OneFuse Property Toolkit is the Swiss army knife of the OneFuse Platform. It can be used in many different ways to assist you in meeting your automation needs. It can be used to simplify configurations, define business logic as configuration, build simple logic or tackle the most complex problems. In its simplest form its meta-data that can be used as a reference offering simple name value pairs that can be used as a reference for decision making. In its most powerful form it can contain logic, decision trees, platform abstractions, and much more.Continue reading “Getting Started with OneFuse Property Toolkit”
If you have read some of my other articles you have heard me mention the OneFuse Terraform provider, but only that it has one. Well in this article we are going to dive right in and take a first hand look at how awesome it really is.
For those of you that know me, you probably know I’m a long time die hard vRA fanboy going all the way back to before it was vRA in the DynamicOps days. Well I’m still a bit of a vRA fanboy, but I’m really in love with Terraform. Not just Terraform, but Terraform with OneFuse.Continue reading “Terraform with OneFuse: Better Together”
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 Policy ”.
By the end of this article we will have created a blueprint that will deploy a vSphere machine that is named using the OneFuse Naming module. While this will be a simple example we will build upon this in later articles to showcase the advanced capabilities offered by OneFuse as a platform.Continue reading “vRA8 with OneFuse: Custom Naming”
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 allows for the use of more than one provider in the environment, it also allows for easy migration from one IPAM provider to another.Continue reading “Creating a OneFuse IPAM Policy”