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”

Terraform with OneFuse: Better Together

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”

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”

Harness the Power of vRA with the SovLabs Property Toolkit and Template Engine – Part 2

In Part 1 of this series we walked through how you can use the SovLabs Property Toolkit and Template Engine to configure vRealize Automation (vRA) for our environment input.  In this second part of the series, we’re going to walk through setting up the Application and Compliance inputs for our particular use case.  If you are starting to see smoke, don’t be alarmed. It’s just our Genie being let out of the lamp.

In Part 1, we determined that the required options for our Application input will be:

  • WordPress
  • Microsoft SQL

Determine the Outcome

In this scenario, the selection of the application will have a significant impact on the outcome. However, while we need to think about the application, we also need to look at the larger picture. What do I mean by “the bigger picture”? Well, once we figure out the desired outcome for each of these items, we need to think about how each item relates to the environment and the choices we made in Part 1.

What if the requester chooses WordPress as the application and Production as the environment?  Alternatively, what if they choose Microsoft SQL and Development? Will the outcome of the application differ based on the environment to which it is being deployed?

Some things to consider:

  1. Do the workload specs change based on the environment selection?
  2. Do development, test, and production instances have the same CPU and Memory requirements?
  3. Do any of the integrations change based on application and environment?  
  4. Do WordPress and Microsoft SQL have the same backup requirements?
    1. Does this requirement change based on which environment the workload is being deployed to?
  5. What else could affect the outcome?

To read the entire article please see the original article on the SovLabs Blog.

Infoblox, Custom Naming, and the Cost of Free Software

About the Free Custom Hostname Extension for vRealize Automation

Here at SovLabs we are always helping our audience make the decision to either “build” or “buy”, when it comes to VMware automation solutions. Recently, we have been involved in some discussions about the free Infoblox plugin for vRealize Automation. Specifically,these discussions are around how the free Infoblox plugin for vRealize Automation handles custom host naming. That discussion prompted us to consider all such customizations and the support required when when they are integrated with vRealize Automation.

Integrate with vRA
Custom Automation Considerations

There are a few issues at play here, including:

  • How do the different components of your solution work together?  
  • Was it designed wholistically or were pieces added on as you needed them?   
  • Did one source develop all of the components, or are they pulled piecemeal from multiple places?
  • If one source did all of the development – are they still available?  
  • Who is supporting the development work going forward?

Read the entire article written by Josh Andrews here on the SovLabs Blog.