An overview of integrating F5, Cisco ACI, VMware, Infoblox and application configuration

The ability to deploy and manage applications is a critical function to any IT organization and the integration of application services is becoming increasingly complex. F5’s BIG-IP application delivery controller platform is the gold standard to provide these application services, providing packet and session security and manipulation to fit any enterprise environment. However, a number of additional dependencies still require attention, such as IP allocation, network provisioning, domain name services, virtual machine management, etc. — all as separate tasks.

Automating these F5 configurations is a straightforward process via the F5 iControl API. However, this is only one piece of an overall solution when deploying an application. The goal is to orchestrate the F5 configuration with the other components as an overall workflow. A typical example of this would be integrating F5, Cisco ACI, VMware, Infoblox and application configuration all together in an orchestrated fashion.

Cisco CloudCenter (formerly CliQr) is an application-focused cloud management platform that allows provisioning of infrastructure for on-premise data center, private or public cloud environments. Cisco CloudCenter is a solution that allows the orchestration of the separate infrastructure tasks into a single workflow easily. It allows easy orchestration of infrastructure that even allows current automations to be integrated to ensure previous work done is not wasted. CloudCenter also has built in plugins for OEMs such as Cisco and VMware to avoid starting from scratch.

In the workflow above, we demonstrate the steps to automate F5 virtual server configuration using Cisco CloudCenter. Also shown is how to fit the F5 solution into an overall application focused workflow involving infrastructure components such as Cisco ACI, VMware and Infoblox. Click here to view a short demonstration video.

Interested in hearing more? Check out some of my other blog posts or reach out to WWT directly.

Author’s note: A special thanks to Mark Wall for his technical contributions to this post. Check out his author bio to learn more about his expertise.

Leave a Reply

Your email address will not be published. Required fields are marked *

  1. JaimeWrave says:

    Good post! I read your blog often and you always post excellent content. I posted this article on Facebook and my followers like it. Thanks for writing this!

  2. Blake Parker says:

    Hey Joe, are the scripts in this demo available on github?

    1. Joe Weber says:

      Hey Blake, thanks for taking the time to read the blog and watch the demo video. The integration is part of our Integration Services that can be tailored to our customers use case. I will reach out to you via email to see how we can help you with your use case.