Skip to content
This repository has been archived by the owner on Dec 4, 2023. It is now read-only.

v5.0.0.0
Compare
Choose a tag to compare
@JosephPJordan JosephPJordan released this 12 Apr 23:46
v5.0.0.0
a0660c1

Supported templates additions in 5.0.0.0

In addition to minor enhancements and fixes, this release contains the following:

  • Auto scale templates now automatically backup BIG-IP configuration
    All Azure auto scale templates now automatically create a UCS backup of the BIG-IP VE configuration and store it in Azure in the storage account created by the template. Backups occur once a day at 12am and 7 days of backups are saved. In the event the system needs to restore from a backup UCS file, it uses the file with the latest timestamp.

  • HA-AVSET template renamed, relocated, and updated
    The HA-AVSET template now called Failover – API, and resides in the /cluster/failover-api/ directory. For this release, the failover script was overhauled to focus on moving IP configurations based on BIG-IP virtual addresses, and not tags on public IP addresses in Azure.

  • Logging iApp template
    F5 has created an iApp for configuring logging for BIG-IP modules to be sent to a specific set of cloud analytics solutions. The iApp creates logging profiles which can be attached to the appropriate objects (virtual servers, APM policy, and so on) which results in logs being sent to the selected cloud analytics solution, Azure in this case. This iApp now loads on the BIG-IP VE as a part of the template.

Experimental template additions in 5.0.0.0

  • Learning stacks
    The experimental F5 Azure ARM templates now include an option for learning stacks. Learning stacks means that in addition to creating a new networking stack, it also creates all of the appropriate configuration for an example web service. This allows you to create a quick, working demo, or a place to get hands on learning, with a click of a button; everything is created from scratch for you.

  • Auto scale using DNS (no ALB required)
    These new experimental templates for our auto scale solutions now use a DNS request made by the client to the DNS provider (currently only BIG-IP DNS (formerly BIG-IP GTM) is supported) to direct traffic to the current BIG-IP VE (cluster) members directly, which will then process traffic to the application servers. This allows deployments without using an Azure Load Balancer (ALB), which saves money and simplifies the configuration.

  • Auto scale using BIG-IQ and scaling with PAYG instances
    These new experimental auto scale templates launch at least one BIG-IP VE Local Traffic Manager with a BYOL (bring your own license) license, but then use hourly BIG-IP VEs when auto scale events occur. The templates rely on an existing F5 BIG-IQ device with a pool of 1-4 BYOL licenses. But instead of scaling BYOL BIG-IP VE instances as our other auto scale solutions do, as traffic through the BIG-IP VE or the BIG-IP CPU utilization increases, up to 8 PAYG (pay as you go) BIG-IP VE LTM instances automatically instantiate to seamlessly handle the load. When traffic or CPU utilization decreases, the hourly BIG-IP VEs are automatically removed.

Released 4/12/18

Assets 2
Loading