Posted on

vRA8 with OneFuse: IPAM Integration

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”
Posted on

vRA8 with OneFuse: DNS Integration

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”
Posted on

vRA8 with OneFuse: Custom Naming

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”
Posted on

Creating a OneFuse IPAM Policy

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”