View release notes for v3.11.0

experimental/autoscale/waf/via-lb/existing-stack/payg/README.md

@@ -73,7 +73,7 @@ The following table lists the versions of BIG-IP that have been tested and valid
 
 | BIG-IP Version | Build | Solution | Status | Notes |
 | --- | --- | --- | --- | --- |
-| 15.1.2 | 0.0.9 | Standalone, Failover, Autoscale | |
+| 15.1.2.1 | 0.0.10 | Standalone, Failover, Autoscale | |
 | 14.1.3 | 0.0.7 | Standalone, Failover, Autoscale | |
 | 13.1.3 | 0.0.4 | Standalone, Failover, Autoscale | F5 CFE requires BIG-IP 14.1 or later |
 | 12.1.5 | 0.0.2 | Standalone, Failover, Autoscale | Not Validated | F5 CFE requires BIG-IP 14.1 or later |
@@ -116,7 +116,7 @@ After completing the prerequisites, edit the YAML file.  You must replace the fo
 | imageName | Yes | BIG-IP image name. |
 | instanceType | Yes | Instance type assigned to BIG-IP, for example 'n1-standard-4'. |
 | bigIpModules | No | Enter a comma-separated list of modules and provisioning level, for example 'ltm:nominal' or 'ltm:nominal,asm:nominal'. |
-| serviceAccount | Yes | Enter the Google service account to use for autoscale API calls, for example 'username@projectname.iam.gserviceaccount.com'. |
+| serviceAccount | Yes | Enter the Google service account to use for autoscale API calls, for example 'username@projectname.iam.serviceaccount.com'. Please note that this service account is necessary for one BIG-IP to communicate with the other, so the permissions should include access to the storage bucket. Refer [here](https://clouddocs.f5.com/products/extensions/f5-cloud-failover/latest/userguide/gcp.html#create-and-assign-an-iam-role) for instructions on how to create the IAM service account with sufficient access. |
 | targetSize | Yes | Enter the number of instances to start. |
 | minReplicas | Yes | Enter the minimum number of instances autoscale policy will scale down to. |
 | maxReplicas | Yes | Enter the maximum number of instances autoscale policy will allow. |

experimental/autoscale/waf/via-lb/existing-stack/payg/f5-payg-autoscale-bigip-waf.py.schema

@@ -53,7 +53,7 @@ properties:
     type: string
     default: ltm:nominal
   serviceAccount:
-    description: Enter the Google service account to use for autoscale API calls, for example 'username@projectname.iam.gserviceaccount.com'.
+    description: Enter the Google service account to use for autoscale API calls, for example 'username@projectname.iam.serviceaccount.com'. Please note that this service account is necessary for one BIG-IP to communicate with the other, so the permissions should include access to the storage bucket. Refer [here](https://clouddocs.f5.com/products/extensions/f5-cloud-failover/latest/userguide/gcp.html#create-and-assign-an-iam-role) for instructions on how to create the IAM service account with sufficient access.
     type: string
   targetSize:
     description: Enter the number of instances to start.

experimental/autoscale/waf/via-lb/existing-stack/payg/f5-payg-autoscale-bigip-waf.yaml

@@ -1,6 +1,6 @@
 # Copyright 2019 F5 Networks All rights reserved.
 #
-# Version 3.10.0
+# Version 3.11.0
 ## note deployment name can not excede 23 charactors.
 
 imports:
@@ -18,19 +18,17 @@ resources:
    ### Specify the name of the subnet to use for management traffic, for example 'my-management-subnetwork'.
    mgmtSubnet: <management subnet>
    ### BIG-IP image, valid choices include:
-   # f5-bigip-15-1-2-0-0-9-payg-best-10gbps-201110230057
-    # f5-bigip-15-1-2-0-0-9-payg-best-1gbps-201110230057
-    # f5-bigip-15-1-2-0-0-9-payg-best-200mbps-201110230057
-    # f5-bigip-15-1-2-0-0-9-payg-best-25mbps-201110230057
-    # f5-bigip-15-1-2-0-0-9-payg-best-5gbps-201110230057
-      # f5-bigip-15-1-2-0-0-9-payg-adv-waf-1gbps-201110230057
-      # f5-bigip-15-1-2-0-0-9-payg-adv-waf-200mbps-201110230057
-      # f5-bigip-15-1-2-0-0-9-payg-adv-waf-25mbps-201110230057
-      # f5-bigip-15-1-2-0-0-9-payg-hp-adv-waf-16vcpu-201110230057
-      # f5-bigip-15-1-2-0-0-9-payg-hp-adv-waf-8vcpu-201110230057
-      # f5-bigip-15-1-2-0-0-9-payg-hp-ltm-16vcpu-201110225418
-      # f5-bigip-15-1-2-0-0-9-payg-pve-adv-waf-200mbps-201110225902
-      # f5-bigip-15-1-2-0-0-9-payg-pve-adv-waf-25mbps-201110225902
+   # f5-bigip-15-1-2-1-0-0-10-payg-best-10gbps-210115161130
+    # f5-bigip-15-1-2-1-0-0-10-payg-best-1gbps-210115161130
+    # f5-bigip-15-1-2-1-0-0-10-payg-best-200mbps-210115161130
+    # f5-bigip-15-1-2-1-0-0-10-payg-best-25mbps-210115161130
+    # f5-bigip-15-1-2-1-0-0-10-payg-best-5gbps-210115161130
+      # f5-bigip-15-1-2-1-0-0-10-payg-hp-ltm-16vcpu-210115160742
+      # f5-bigip-15-1-2-1-0-0-10-payg-awf-plus-3gbps-210115161130
+      # f5-bigip-15-1-2-1-0-0-10-payg-awf-plus-200mbps-210115161130
+      # f5-bigip-15-1-2-1-0-0-10-payg-awf-plus-25mbps-210115161130
+      # f5-bigip-15-1-2-1-0-0-10-payg-pve-awf-plus-200mbps-10115161026
+      # f5-bigip-15-1-2-1-0-0-10-payg-pve-awf-plus-25mbps-10115161026
    imageName: <image>
    ### Instance type assigned to BIG-IP, for example 'n1-standard-4'.
    instanceType: n1-standard-4

experimental/standalone/1nic/learning-stack/byol/README.md

@@ -68,7 +68,7 @@ The following table lists the versions of BIG-IP that have been tested and valid
 
 | BIG-IP Version | Build | Solution | Status | Notes |
 | --- | --- | --- | --- | --- |
-| 15.1.2 | 0.0.9 | Standalone, Failover, Autoscale | |
+| 15.1.2.1 | 0.0.10 | Standalone, Failover, Autoscale | |
 | 14.1.3 | 0.0.7 | Standalone, Failover, Autoscale | |
 | 13.1.3 | 0.0.4 | Standalone, Failover, Autoscale | F5 CFE requires BIG-IP 14.1 or later |
 | 12.1.5 | 0.0.2 | Standalone, Failover, Autoscale | Not Validated | F5 CFE requires BIG-IP 14.1 or later |

experimental/standalone/1nic/learning-stack/byol/f5-learning-stack-byol-1nic-bigip.yaml

@@ -1,6 +1,6 @@
 # Copyright 2019 F5 Networks All rights reserved.
 #
-# Version 3.10.0
+# Version 3.11.0
 
 imports:
 - path: f5-full-stack-byol-1nic-bigip.py
@@ -14,10 +14,10 @@ resources:
    licenseKey1: <lic key>
    ### BIG-IP image, valid choices include:
 
-    # f5-bigip-15-1-2-0-0-9-byol-all-modules-1boot-loc-201110225902
-    # f5-bigip-15-1-2-0-0-9-byol-all-modules-2boot-loc-201110230057
-    # f5-bigip-15-1-2-0-0-9-byol-ltm-1boot-loc-201110225242
-    # f5-bigip-15-1-2-0-0-9-byol-ltm-2boot-loc-201110225418
+    # f5-bigip-15-1-2-1-0-0-10-byol-all-modules-1boot-loc-0115161026
+    # f5-bigip-15-1-2-1-0-0-10-byol-all-modules-2boot-loc-0115161130
+    # f5-bigip-15-1-2-1-0-0-10-byol-ltm-1boot-loc-210115160621
+    # f5-bigip-15-1-2-1-0-0-10-byol-ltm-2boot-loc-210115160742
    imageName: <image>
    ### Instance type assigned to the BIG-IP, for example 'n1-standard-4'.
    instanceType: n1-standard-4

supported/failover/same-net/via-api/2nic/existing-stack/byol/README.md

@@ -21,7 +21,7 @@
 
 ## Introduction
 
-This solution uses a Google Deployment Manager (GDM) Template to launch two BIG-IP VEs in an Active/Standby configuration with network failover enabled (the template also supports [multiple traffic groups](#traffic-group-configuration) which enables Active/Active deployments) in a Google Virtual Private Cloud, using BYOL (bring your own license) (utility) licensing.
+This solution uses a Google Deployment Manager (GDM) Template to launch two BIG-IP VEs in an Active/Standby configuration with network failover enabled (the template also supports [multiple traffic groups](#traffic-group-configuration)) in a Google Virtual Private Cloud, using BYOL (bring your own license) (utility) licensing.
 Traffic flows from the BIG-IP VE(s) to the application servers. Each BIG-IP VE has 2 network interfaces (NICs), one for management, one for external traffic, and one for internal traffic.
  **Networking Stack Type:** This template deploys into an existing networking stack; so the networking infrastructure MUST be available prior to deploying. See the [Template Parameters Section](#template-parameters) for required networking objects.
 
@@ -74,7 +74,7 @@ The following table lists the versions of BIG-IP that have been tested and valid
 
 | BIG-IP Version | Build | Solution | Status | Notes |
 | --- | --- | --- | --- | --- |
-| 15.1.2 | 0.0.9 | Standalone, Failover, Autoscale | |
+| 15.1.2.1 | 0.0.10 | Standalone, Failover, Autoscale | |
 | 14.1.3 | 0.0.7 | Standalone, Failover, Autoscale | |
 | 13.1.3 | 0.0.4 | Standalone, Failover, Autoscale | F5 CFE requires BIG-IP 14.1 or later |
 | 12.1.5 | 0.0.2 | Standalone, Failover, Autoscale | Not Validated | F5 CFE requires BIG-IP 14.1 or later |
@@ -114,7 +114,7 @@ After completing the prerequisites, edit the YAML file.  You must replace the fo
 | availabilityZone2 | Yes | Enter the availability zone where you want to deploy the second BIG-IP VE instance, for example 'us-west1-b'. |
 | mgmtNetwork | Yes | Specify the name of the network to use for management traffic, for example 'my-management-network'. |
 | mgmtSubnet | Yes | Specify the name of the subnet to use for management traffic, for example 'my-management-subnetwork'. |
-| restrictedSrcAddress | Yes | This field restricts management access to a specific network or address. Enter an IP address or address range in CIDR notation separated by a space. For example, '10.0.0.0/0'. |
+| restrictedSrcAddress | Yes | This field restricts management access to specific networks or addresses. Enter an IP address or address range in CIDR notation separated by a space.  **IMPORTANT** This solution requires your Management's subnet at a minimum in order for the peers to cluster.  For example, '10.0.11.0/24 55.55.55.55/32' where 10.0.11.0/24 is your local management subnet and 55.55.55.55/32 is a specific address (ex. orchestration host/desktop/etc.). |
 | network1 | Yes | Specify the Network name for BIG-IP application traffic, for example 'my-application-network'. |
 | network1SharedVpc | No | If using a shared VPC, specify the name of the host project to use for management traffic. Leave default value of None when not using shared VPC. **Note** template does not create firewall policy for shared VPC. Create policy on shared VPC within in host project to allow appropriate traffic. |
 | subnet1 | Yes | Specify the subnet of the Network that the BIG-IP should use for application traffic, for example 'my-application-subnetwork'. |
@@ -129,7 +129,7 @@ After completing the prerequisites, edit the YAML file.  You must replace the fo
 | ntpServer | No | (Optional) List NTP servers separated by a space, for example 'pool.ntp.org'. The default is 'time.google.com'. |
 | timezone | No | (Optional) Enter the Olson timezone string from /usr/share/zoneinfo. The default is 'UTC'. See the TZ column here (https://en.wikipedia.org/wiki/List_of_tz_database_time_zones) for legal values. For example, 'US/Eastern'. |
 | bigIpModules | No | Enter a comma-separated list of modules and provisioning level, for example 'ltm:nominal' or 'ltm:nominal,asm:nominal'. |
-| serviceAccount | Yes | Enter the Google service account to use for autoscale API calls, for example 'username@projectname.iam.serviceaccount.com'. |
+| serviceAccount | Yes | Enter the Google service account to use for autoscale API calls, for example 'username@projectname.iam.serviceaccount.com'. Please note that this service account is necessary for one BIG-IP to communicate with the other, so the permissions should include access to the storage bucket. Refer [here](https://clouddocs.f5.com/products/extensions/f5-cloud-failover/latest/userguide/gcp.html#create-and-assign-an-iam-role) for instructions on how to create the IAM service account with sufficient access. |
 | allowUsageAnalytics | Yes | This deployment can send anonymous statistics to F5 to help us determine how to improve our solutions. If you enter **no** statistics are not sent. |
 | allowPhoneHome | No | This deployment can provide F5 with high-level device use information to optimize development resources. If you select **no** the information is not sent. |
 | logLevel | No | (Optional) Log setting, used to set log level on scripts used during deployment. Acceptable values are - error, warn, info, verbose, debug, silly. The default is 'info'. |