For production licenses, F5 Networks suggests using the maximum configuration limits for the BIG-IP VE system. For lab editions, required reserves can be less. For each virtual machine, the XenServer virtual machine guest environment permits a maximum of 7 virtual network adapters (1 management + 6 dataplane).
The situation is we use F5 Big-IP 1500 load balancers, however the one in our lab is an older model that only has 786MB of memory. The 1500's we use in production are the newer model's with 2GB of memory. The lab F5 does not have enough memory to install the latest software versions and in the interest of keeping the lab as close to production as possible it has meant we have not been able to apply new F5 software updates and hotfixes for some time and thus the software is several releases behind. Recently we've been experiencing some issues on our production F5's that are resolved by F5 in the latest software release. We want to apply the latest update, but in the interest of keeping the lab the same we've been looking at buying a used/refrubished F5 Big-IP 1500 from eBay but we weren't sure if we could transfer the existing licenses from our current 786MB lab system to this 'new' used F5 we buy online, and more importantly have them activated. Anyone here know if this would work or would we have to call F5?
Introduction
This repository provides the foundation for working with the F5 Modules for Ansible.The architecture of the modules makes inherent use of the BIG-IP SOAP and RESTAPIs as well as the tmsh API where required.
This repository is an incubator for Ansible modules. The modules in this repository may bebroken due to experimentation or refactoring.
If you want to download the stable modules, they are shipped with Ansibleautomatically. In-between major releases of Ansible, new stable modules can be found here.
The F5 Modules for Ansible are freely provided to the open source community for automatingBIG-IP device configurations.
Support
F5 supports the F5 modules delivered in Red Hat Ansible distributions. Please refer to the F5 Ansible Support Policy for details.
Bugs, Issues
Please file any bugs, questions, or enhancement requests by using Github Issues. For details, see Get Help.
Documentation
All documentation is available on clouddocs.f5.com.
When writing new modules, please refer to the Guidelines document.
Your ideas
What types of modules do you want created? If you have a use case and can sufficiently describe the behavior you want to see, open an issue and we will hammer out the details.
If you've got the time, consider sending an email that introduces yourself and what you do. We love hearing about how you're using the F5 Modules for Ansible.
This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work.
See License.
Contributor License Agreement
Individuals or business entities who contribute to this project must complete and submit the F5 Contributor License Agreement to [email protected] prior to their code submission being included in this project.