on 31-May-2018 04:00
BIG-IP Cloud Edition is designed to enable easy to use and fast self-serve deployments of application services in private and public clouds. BIG-IP Cloud Edition is a solution composed of BIG-IP Per-App VEs and BIG-IQ CM 6.0. It's designed to deliver the same consistent industry leading intelligent traffic management (F5 Local Traffic Manager – LTM) and advanced web application firewall (Advanced WAF) services. For more information on BIG-IP Cloud Edition Components please read K3341282 on AskF5.
In this FAQ you'll find a growing list of frequently asked questions about the BIG-IP Cloud Edition. Please provide feedback in this discussion thread.
|BIG-IP Per App VE||BIG-IP VE (Standard|
|# of Applications Supported||1 Virtual IP & 3 Virtual Servers||Skys the Limit|
|BIG-IP Services Available||
||All Application Services|
|Throughput Per Instance||25Mbps, 200Mbps||25Mbps, 200Mbps, 1GB, 3GB, 5GB, 10GB, High Peformance|
|Licensing Models||Subscription, Enterprise License Agreement, Perpetual||Subscription, Enterprise License Agreement, Perpetual, Pay-As-You-Go|
This FAQ doesn't talk about High-Availability in the cloud from what I can see. For the per App VE, how would we achieve HA across Availability Zones in AWS, for example? Would we need to purchase two in that case?
The BIG-IQ is HA and if using VMWare, the tier 1 L4 traffic distribution is a BIG-IP HA pair (AWS uses ELB for tier 1). But the Per App VE is more of a stateless BIG-IP instance designed to pull full configuration from BIG-IQ as it's horizontally scaled out.
The service scaling group contains the requirements for auto-scale such as throughput, CPU, memory thresholds and will dynamically update the tier 1 traffic distribution of the new Per App VEs. In this case, a service scaling group would always start with 2 Per App VE's and maybe scale out to 4 or 5 depending on your requirements. Once the load normalized, it would then scale back to the original two Per App VEs.
Because it's dynamically creating BIG-IP's as needed, all redundancy is controlled by BIG-IQ's configurations and the tier 1 traffic distrubtion.
This is designed for those less-stateful applications that don't need the dedicated BIG-IP HA pairs deployed in the cloud (but BIG-IQ could manage both).
What are the other options apart from BIG IQ 6.0 to manage the Auto scaling in AWS if we want to use two active F5s at a time and scaling it by further two and so on?
You can create your service scaling group with 2 BIG-IPs initially and set the scaling rules to add additional BIG-IPs depending on crossing thresholds (CPU, Memory, throughput, ...).
Check below links for more information:
@Roman: Thanks for sharing the links! Can we achieve this (Auto-scaling) without BIG-IQ? Any other way where we can manage the configuration without the use of Big-IQ?
@ChetanAr to deploy BIG-IP Auto Scaling in AWS, you can use the F5 CFT available on F5 Neworks GitHub
You may also have a look at AS3.
Thanks Roman! Can we auto-scale LTM same way we are doing BIP-IP VE? If yes, which model will work well: subscription or BYOL?
Thanks Roman! Apologies for the delay. I'm now testing the deployment of BIG IQ 6.0.1 for its various features.
The images are the same between the per-app VE and the standard VE. Software licensing determines Per App VE or standard BIG-IP VE functionality. You can deploy manually a BIG-IP in Hyper-V and apply the per-app VE license.
If you are talking about Auto-Scaling, there are no plans to support Hyper-V at the moment. Service Scaling Groups are only supported in VMware, AWS and Azure at the moment.
Thanks & Regards,