OpenStack Neutron LbaaS integration with physical F5 in OpenContrail SDN
Republished from TCP Cloud on request from the project authors, Radovan Gibala and Filip Kolar at F5.
In this blog we would like to show how to integrate physical F5 under OpenContrail SDN and cre...
Published Dec 03, 2015
Version 1.0Chase_Abbott
Employee
Joined September 17, 2008
Chase_Abbott
Employee
Joined September 17, 2008
Chase_Abbott
Dec 04, 2015Employee
Hi Zdenda; We do have a lot of orchestration methods, only because as we release new ways to manage BIG-IP, we don't want to remove support for older methods for people who have large automation and scripted deployments. As you're already aware, our big push is the iControl REST method because we can integrate easier to existing customer automation tools already using REST API's for other products. Related to OpenStack, when we move to more advanced deployment scenarios, there's an expectation that people are using more advanced methods to deploy, maintain, and monitor BIG-IP deployments. In these situations larger automation tools would live outside the Neutron network stack and would encapsulate the entire Openstack/F5/OpenContrail deployment. In this case, we'd expect you to use independent scripts using REST API to add value to the dynamic management of Openstack. However, if using rapid deployment scenarios, this can be cumbersome and most of the time people are not creating as complex network stacks for Openstack. In those situations, we'd recommend managing the BIG-IP as you're already doing. Feel free to ask a larger open-ended question in our Q&A module and let me know so we can discuss further with a wider audience.
Best regards,
-Chase Abbott