Deploys BIG-IP in Azure Cloud

This Terraform module deploys N-nic F5 BIG-IP in Azure cloud,and with module count feature we can also deploy multiple instances of BIG-IP.

Prerequisites

This module is supported from Terraform 0.13 version onwards.

Below templates are tested and worked in the following version

Terraform v0.14.0

provider registry.terraform.io/hashicorp/azurerm v2.28.0
provider registry.terraform.io/hashicorp/null v2.1.2
provider registry.terraform.io/hashicorp/random v2.3.0
provider registry.terraform.io/hashicorp/template v2.1.2

!> Note: bigip-module v1.2.0 Requires azurerm > 3.0 version

Releases and Versioning

This module is supported in the following bigip and terraform version

BIGIP version	Terraform 1.X	Terraform 0.14
BIG-IP 17.x	X	X
BIG-IP 16.x	X	X
BIG-IP 15.x	X	X

Password Management

☝️	By default bigip module will have random password setting to give dynamic password generation

☝️	Users Can explicitly provide password as input to Module using optional Variable "f5_password"

☝️	To use Azure key vault password,we have to enable the variable "az_keyvault_authentication" to true and supply the variables with key_valut name,secret along with resource group name where azure key vault is defined

Depreciations

zones variable in azurerm_public_ip resource is depreciated to new variable availability_zones. Hence we need to have new input variable for our module zone assignment in public_ip resource and below is the new variable for it. We have updated our examples according to it.
```
variable availabilityZones_public_ip {
    description = "The availability zone to allocate the Public IP in. Possible values are Zone-Redundant, 1, 2, 3, and No-Zone."
    type        = string
    default     = "Zone-Redundant"
}
```

BYOL Licensing

This template uses PayGo BIG-IP image for the deployment (as default). If you would like to use BYOL licenses, then these following steps are needed:

Find available images/versions with BYOL in SKU name using Azure CLI:

> az vm image list -f BIG-IP --all

        # example output...

        {
          "offer": "f5-big-ip-byol",
          "publisher": "f5-networks",
          "sku": "f5-big-ltm-2slot-byol",
          "urn": "f5-networks:f5-big-ip-byol:f5-big-ltm-2slot-byol:15.1.201000",
          "version": "15.1.201000"
        },

In the variables.tf, modify image_name and product_name with the SKU and offer from AZ CLI results

        # BIGIP Image
        variable product_name { default = "f5-big-ip-byol" }
        variable image_name { default = "f5-big-ltm-2slot-byol" }

Add the corresponding license key in DO declaration( Declarative Onboarding ), this DO can be added in custom run-time-int script ( as given in examples section ) or POST a Declarative Onboarding declaration as given in url. (https://clouddocs.f5.com/products/extensions/f5-declarative-onboarding/latest/bigip-examples.html#standalone-declaration )
```
      "myLicense": {
      "class": "License",
      "licenseType": "regKey",
      "regKey": "${regKey}"
  },
```

Custom User data

By default custom_user_data will be null , bigip module will use default f5_onboard.tmpl file contents for initial BIGIP onboard connfiguration
If users desire custom onboard configuration,we can use this variable and pass contents of custom script to the variable to have custom onboard bigip configuration.( An example is provided in examples section )

Example 3-NIC Deployment Module usage with `custom_user_data`

module bigip {
  source                      = "F5Networks/bigip-module/azure"
  prefix                      = "bigip-azure-3nic"
  resource_group_name         = "testbigip"
  mgmt_subnet_ids             = [{"subnet_id" = "subnet_id_mgmt" , "public_ip" = true, "private_ip_primary" =  ""}]
  mgmt_securitygroup_ids      = ["securitygroup_id_mgmt"]
  external_subnet_ids         = [{"subnet_id" =  "subnet_id_external", "public_ip" = true, "private_ip_primary" = "", "private_ip_secondary" = "" }]
  external_securitygroup_ids  = ["securitygroup_id_external"]
  internal_subnet_ids         = [{"subnet_id" =  "subnet_id_internal", "public_ip"=false, "private_ip_primary" = "" }]
  internal_securitygroup_ids  = ["securitygropu_id_internal"]
  availabilityZones           =  var.availabilityZones
  availabilityZones_public_ip = var.availabilityZones_public_ip
  custom_user_data            = var.custom_user_data
}

Example Usage

We have provided some common deployment examples

!> Note: There should be one to one mapping between subnet_ids and securitygroup_ids (for example if we have 2 or more external subnet_ids,we have to give same number of external securitygroup_ids to module)

!> Note: Users can have dynamic or static private ip allocation.If primary/secondary private ip value is null it will be dynamic,else it will be static private ip allocation.

!> Note: With Static private ip allocation we can assign primary and secondary private ips for external interfaces, whereas primary private ip for management and internal interfaces.

~> WARNING If it is static private ip allocation we can't use module count,as same private ips will be tried to allocate for multiple bigip instances based on module count.

~> WARNING With Dynamic private ip allocation,we have to pass null value to primary/secondary private ip declaration and module count will be supported.

!> Note: Sometimes it is observed that the given static primary and secondary private ips may get exchanged. This is the limitation present in aws.

~>NOTE: This Module uses basic DO config to set the Users and Passwords as part of runtime-init, it does not config VLANS/SelfIPs and other configuration.

~>NOTE: If you are using custom ATC tools, don't change name of ATC tools rpm file( ex: f5-declarative-onboarding-xxxx.noarch.rpm,f5-appsvcs-xxx.noarch.rpm)

Below example snippets show how this module is called. ( Dynamic private ip allocation )

#
#Example 1-NIC Deployment Module usage
#
module bigip {
  source                      = "F5Networks/bigip-module/azure"
  prefix                      = "bigip-azure-1nic"
  resource_group_name         = "testbigip"
  mgmt_subnet_ids             = [{"subnet_id" = "subnet_id_mgmt" , "public_ip" = true,"private_ip_primary" =  ""}]
  mgmt_securitygroup_ids      = ["securitygroup_id_mgmt"]
  availabilityZones           =  var.availabilityZones
  availabilityZones_public_ip = var.availabilityZones_public_ip
}

#
#Example 2-NIC Deployment Module usage
#
module bigip {
  source                      = "F5Networks/bigip-module/azure"
  prefix                      = "bigip-azure-2nic"
  resource_group_name         = "testbigip"
  mgmt_subnet_ids             = [{"subnet_id" = "subnet_id_mgmt" , "public_ip" = true, "private_ip_primary" =  ""}]
  mgmt_securitygroup_ids      = ["securitygroup_id_mgmt"]
  external_subnet_ids         = [{"subnet_id" =  "subnet_id_external", "public_ip" = true,"private_ip_primary" = "", "private_ip_secondary" = "" }]
  external_securitygroup_ids  = ["securitygroup_id_external"]
  availabilityZones           =  var.availabilityZones
  availabilityZones_public_ip = var.availabilityZones_public_ip
}

#
#Example 3-NIC Deployment  Module usage 
#
module bigip {
  source                      = "F5Networks/bigip-module/azure"
  prefix                      = "bigip-azure-3nic"
  resource_group_name         = "testbigip"
  mgmt_subnet_ids             = [{"subnet_id" = "subnet_id_mgmt" , "public_ip" = true, "private_ip_primary" =  ""}]
  mgmt_securitygroup_ids      = ["securitygroup_id_mgmt"]
  external_subnet_ids         = [{"subnet_id" =  "subnet_id_external", "public_ip" = true, "private_ip_primary" = "", "private_ip_secondary" = "" }]
  external_securitygroup_ids  = ["securitygroup_id_external"]
  internal_subnet_ids         = [{"subnet_id" =  "subnet_id_internal", "public_ip"=false, "private_ip_primary" = "" }]
  internal_securitygroup_ids  = ["securitygropu_id_internal"]
  availabilityZones           =  var.availabilityZones
  availabilityZones_public_ip = var.availabilityZones_public_ip
}

#
#Example 4-NIC Deployment  Module usage(with 2 external public interfaces,one management and internal interface.There should be one to one mapping between subnet_ids and securitygroupids)
#
module bigip {
  source                      = "F5Networks/bigip-module/azure"
  prefix                      = "bigip-azure-4nic"
  resource_group_name         = "testbigip"
  mgmt_subnet_ids             = [{"subnet_id" = "subnet_id_mgmt" , "public_ip" = true, "private_ip_primary" =  ""}]
  mgmt_securitygroup_ids      = ["securitygroup_id_mgmt"]
  external_subnet_ids         = [{"subnet_id" = "subnet_id_external", public_ip" = true, "private_ip_primary" = "", "private_ip_secondary" = "" },{"subnet_id" = subnet_id_external2", public_ip" = true, "private_ip_primary" = "", "private_ip_secondary" = "" }]
  external_securitygroup_ids  = ["securitygroup_id_external","securitygroup_id_external"]
  internal_subnet_ids         = [{"subnet_id" =  "subnet_id_internal", "public_ip"=false, "private_ip_primary" = "" }]
  internal_securitygroup_ids  = ["securitygropu_id_internal"]
  availabilityZones           =  var.availabilityZones
  availabilityZones_public_ip = var.availabilityZones_public_ip
}

#
#Example to deploy 2 BIGIP-1 Nics using Module with module count feature
#
module bigip {
  count                       = 2
  source                      = "F5Networks/bigip-module/azure"
  prefix                      = "bigip-azure-1nic"
  resource_group_name         = "testbigip"
  mgmt_subnet_ids             = [{"subnet_id" = "subnet_id_mgmt" , "public_ip" = true,"private_ip_primary" =  ""}]
  mgmt_securitygroup_ids      = ["securitygroup_id_mgmt"]
  availabilityZones           = var.availabilityZones
  availabilityZones_public_ip = var.availabilityZones_public_ip
}

Similarly we can have N-nic deployments based on user provided subnet_ids and securitygroup_ids.
With module count, user can deploy multiple bigip instances in the azure cloud (with the default value of count being one)

Below is the example snippet for private ip allocation

#
#Example 3-NIC Deployment with static private ip allocation
#
module bigip {
  source                     = "F5Networks/bigip-module/azure"
  prefix                     = format("%s-3nic", var.prefix)
  resource_group_name        = azurerm_resource_group.rg.name
  mgmt_subnet_ids            = [{ "subnet_id" = data.azurerm_subnet.mgmt.id, "public_ip" = true, "private_ip_primary" =  "10.2.1.5"}]
  mgmt_securitygroup_ids     = [module.mgmt-network-security-group.network_security_group_id]
  external_subnet_ids        = [{ "subnet_id" = data.azurerm_subnet.external-public.id, "public_ip" = true, 
                                "private_ip_primary" = "10.2.2.40","private_ip_secondary" = "10.2.2.50" }]
  external_securitygroup_ids = [module.external-network-security-group-public.network_security_group_id]
  internal_subnet_ids        = [{ "subnet_id" = data.azurerm_subnet.internal.id, "public_ip" = false, "private_ip_primary" = "10.2.3.40"}]
  internal_securitygroup_ids = [module.internal-network-security-group.network_security_group_id]
  availabilityZones          = var.availabilityZones
  availabilityZones_public_ip = var.availabilityZones_public_ip
}

Required Input Variables

These variables must be set in the module block when using this module.

Name	Description	Type
prefix	This value is inserted in the beginning of each Azure object. Note: requires alpha-numeric without special character	`string`
resource_group_name	The name of the resource group in which the resources will be created	`string`
mgmt_subnet_ids	Map with Subnet-id and public_ip as keys for the management subnet	`List of Maps`
mgmt_securitygroup_ids	securitygroup_ids for the management interface	`List`
availabilityZones	availabilityZones	`List`
availabilityZones_public_ip	availabilityZones_public_ip	`string`

Optional Input Variables

These variables have default values and don't have to be set to use this module. You may set these variables to override their default values.

Name	Description	Type	Default
f5_username	The admin username of the F5 BIG-IP that will be deployed	`string`	bigipuser
f5_password	Password of the F5 BIG-IP that will be deployed.If this is not specified random password will get generated	`string`	""
f5_instance_type	Specifies the size of the virtual machine	`string`	Standard_DS3_v2
vm_name	Name of F5 BIGIP VM to be used, it should be unique value,default is `empty string` meaning module adds with `prefix + random_id`	`string`	""
f5_image_name	5 SKU (image) to you want to deploy. Note: The disk size of the VM will be determined based on the option you select. Important: If intending to provision multiple modules, ensure the appropriate value is selected, such as AllTwoBootLocations or AllOneBootLocation	`string`	f5-bigip-virtual-edition-200m-best-hourly
f5_version	It is set to default to use the latest software	`string`	latest
os_disk_size	The size of the Data Disk which should be created, size is in `GB`	`number`	`84`
f5_product_name	Azure BIG-IP VE Offer	`string`	f5-big-ip-best
image_publisher	Specifies product image publisher	`string`	`f5-networks`
storage_account_type	Defines the type of storage account to be created. Valid options are Standard_LRS, Standard_ZRS, Standard_GRS, Standard_RAGRS, Premium_LRS	`string`	Standard_LRS
enable_accelerated_networking	Enable accelerated networking on Network interface	`bool`	FALSE
enable_ssh_key	Enable ssh key authentication in Linux virtual Machine	`bool`	TRUE
f5_ssh_publickey	public key to be used for ssh access to the VM,managing key is out of band module, user can reference this key from azurerm_ssh_public_key	`string`	It should be used along with `enable_ssh_key` set `true`
DO_URL	URL to download the BIG-IP Declarative Onboarding module	`string`	`latest` Note: don't change name of ATC tools rpm file
AS3_URL	URL to download the BIG-IP Application Service Extension 3 (AS3) module	`string`	`latest` Note: don't change name of ATC tools rpm file
TS_URL	URL to download the BIG-IP Telemetry Streaming module	`string`	`latest` Note: don't change name of ATC tools rpm file
FAST_URL	URL to download the BIG-IP FAST module	`string`	`latest` Note: don't change name of ATC tools rpm file
CFE_URL	URL to download the BIG-IP Cloud Failover Extension module	`string`	`latest` Note: don't change name of ATC tools rpm file
INIT_URL	URL to download the BIG-IP runtime init module	`string`	`latest` Note: don't change name of ATC tools rpm file
libs_dir	Directory on the BIG-IP to download the A&O Toolchain into	`string`	/config/cloud/azure/node_modules
onboard_log	Directory on the BIG-IP to store the cloud-init logs	`string`	/var/log/startup-script.log
azure_secret_rg	The name of the resource group in which the Azure Key Vault exists	`string`	""
az_keyvault_authentication	Whether to use key vault to pass authentication	`string`	false
azure_keyvault_name	The name of the Azure Key Vault to use	`string`	""
azure_keyvault_secret_name	The name of the Azure Key Vault secret containing the password	`string`	""
external_subnet_ids	List of maps of subnetids of the virtual network where the virtual machines will reside	`List of Maps`	[{ "subnet_id" = null, "public_ip" = null,"private_ip_primary" = "", "private_ip_secondary" = "" }]
internal_subnet_ids	List of maps of subnetids of the virtual network where the virtual machines will reside	`List of Maps`	[{ "subnet_id" = null, "public_ip" = null,"private_ip_primary" = "" }]
external_securitygroup_ids	List of network Security Groupids for external network	`List`	[]
internal_securitygroup_ids	List of network Security Groupids for internal network	`List`	[]
custom_user_data	Provide a custom bash script or cloud-init script the BIG-IP will run on creation	`string`	null
user_identity	The ID of the managed user identity to assign to the BIG-IP instance	`string`	null
mgmt_enable_ip_forwarding	Enable IP forwarding on the Mgmt interfaces. To allow inline routing for backends	`string`	`false`
external_enable_ip_forwarding	Enable IP forwarding on the External interfaces. To allow inline routing for backends, this must be set to true	`string`	`true`
tags	`key:value` tags to apply to resources built by the module	`map`	{}
externalnic_failover_tags	`key:value` tags to apply to external nic resources built by the module	`map`	{}
internalnic_failover_tags	`key:value` tags to apply to external nic resources built by the module	`map`	{}
mgmt_app_securitygroup_ids	List of application Security Groupids for Mgmt network	`List`	[]
external_app_securitygroup_ids	List of application Security Groupids for external network	`List`	[]
internal_app_securitygroup_ids	List of application Security Groupids for internal network	`List`	[]
sleep_time	The number of seconds/minutes of delay to build into creation of BIG-IP VMs	`string`	300s

Output Variables

Name	Description
mgmtPublicIP	The actual ip address allocated for the resource
mgmtPublicDNS	fqdn to connect to the first vm provisioned
mgmtPort	Mgmt Port
f5_username	BIG-IP username
bigip_password	BIG-IP Password (if dynamic_password is choosen it will be random generated password or if azure_keyvault is choosen it will be key vault secret name )
public_addresses	It is List of Maps all public address assigned for External-public-primary/ External-public-secondary
private_addresses	It is List of Maps all privates address assigned for Mgmt/External-Public/External-private/Internal
bigip_instance_ids	List of BIG-IP AWS Instance IDs Created
bigip_nic_ids	List of BIG-IP network interface IDs

~ NOTE: IF you want to access External interface private IPs, you need to filter it form private_addresses map like below:

  output "external_public_primary_private_ip" {
    description = "List of BIG-IP private addresses"
    value       = flatten([for i in range(length(module.bigip.*.private_addresses)) : module.bigip.*.private_addresses[i]["public_private"]["private_ip"]])
  }

~>NOTE: A local json file will get generated which contains the DO declaration (for 1,2,3 nics as provided in the examples )

BIG-IP Automation Toolchain InSpec Profile for testing readiness of Automation Tool Chain components

After the module deployment, we can use inspec tool for verifying the Bigip connectivity along with ATC components

This InSpec profile evaluates the following:

Basic connectivity to a BIG-IP management endpoint ('bigip-connectivity')
Availability of the Declarative Onboarding (DO) service ('bigip-declarative-onboarding')
Version reported by the Declarative Onboarding (DO) service ('bigip-declarative-onboarding-version')
Availability of the Application Services (AS3) service ('bigip-application-services')
Version reported by the Application Services (AS3) service ('bigip-application-services-version')
Availability of the Telemetry Streaming (TS) service ('bigip-telemetry-streaming')
Version reported by the Telemetry Streaming (TS) service ('bigip-telemetry-streaming-version')
Availability of the Cloud Failover Extension( CFE ) service ('bigip-cloud-failover-extension')
Version reported by the Cloud Failover Extension( CFE ) service('bigip-cloud-failover-extension-version')

run inspec tests

we can either run inspec exec command or execute runtests.sh in any one of example nic folder which will run below inspec command

inspec exec inspec/bigip-ready  --input bigip_address=$BIGIP_MGMT_IP bigip_port=$BIGIP_MGMT_PORT user=$BIGIP_USER password=$BIGIP_PASSWORD do_version=$DO_VERSION as3_version=$AS3_VERSION ts_version=$TS_VERSION fast_version=$FAST_VERSION cfe_version=$CFE_VERSION

Support Information

This repository is community-supported. Follow instructions below on how to raise issues.

Filing Issues and Getting Help

If you come across a bug or other issue, use GitHub Issues to submit an issue for our team. You can also see the current known issues on that page, which are tagged with a purple Known Issue label.

Copyright

F5 Networks Contributor License Agreement

Before you start contributing to any project sponsored by F5 Networks, Inc. (F5) on GitHub, you will need to sign a Contributor License Agreement (CLA).

If you are signing as an individual, we recommend that you talk to your employer (if applicable) before signing the CLA since some employment agreements may have restrictions on your contributions to other projects. Otherwise by submitting a CLA you represent that you are legally entitled to grant the licenses recited therein.

If your employer has rights to intellectual property that you create, such as your contributions, you represent that you have received permission to make contributions on behalf of that employer, that your employer has waived such rights for your contributions, or that your employer has executed a separate CLA with F5.

If you are signing on behalf of a company, you represent that you are legally entitled to grant the license recited therein. You represent further that each employee of the entity that submits contributions is authorized to submit such contributions on behalf of the entity pursuant to the CLA.

Name		Name	Last commit message	Last commit date
Latest commit History 112 Commits
config		config
examples		examples
templates		templates
test		test
.gitignore		.gitignore
LICENSE		LICENSE
README.md		README.md
main.tf		main.tf
outputs.tf		outputs.tf
variables.tf		variables.tf

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Repository files navigation

Deploys BIG-IP in Azure Cloud

Prerequisites

Releases and Versioning

Password Management

Depreciations

BYOL Licensing

Custom User data

Example 3-NIC Deployment Module usage with `custom_user_data`

Example Usage

Below example snippets show how this module is called. ( Dynamic private ip allocation )

Below is the example snippet for private ip allocation

Required Input Variables

Optional Input Variables

Output Variables

BIG-IP Automation Toolchain InSpec Profile for testing readiness of Automation Tool Chain components

run inspec tests

Support Information

Filing Issues and Getting Help

Copyright

F5 Networks Contributor License Agreement

About

Releases 23

Packages

Contributors 5

Languages

License

F5Networks/terraform-azure-bigip-module

Folders and files

Latest commit

History

Repository files navigation

Deploys BIG-IP in Azure Cloud

Prerequisites

Releases and Versioning

Password Management

Depreciations

BYOL Licensing

Custom User data

Example 3-NIC Deployment Module usage with custom_user_data

Example Usage

Below example snippets show how this module is called. ( Dynamic private ip allocation )

Below is the example snippet for private ip allocation

Required Input Variables

Optional Input Variables

Output Variables

BIG-IP Automation Toolchain InSpec Profile for testing readiness of Automation Tool Chain components

run inspec tests

Support Information

Filing Issues and Getting Help

Copyright

F5 Networks Contributor License Agreement

About

Resources

License

Stars

Watchers

Forks

Releases 23

Packages 0

Contributors 5

Languages

Example 3-NIC Deployment Module usage with `custom_user_data`

Packages