IPAM Provider (Google Cloud Platform) (16.3+)
Beginning with release 16.3, Avi Vantage has integration with Google Cloud Platform (GCP) for providing IPAM services to applications running on instances in GCP.
See also: Service Discovery Using IPAM and DNS
Prerequisites for GCP IPAM
For details setting up Avi Controller and Service Engines instances on GCP, refer to Example Configuration of Avi Controller and SE Instances on GCP.
To use GCP as the IPAM provider, all the Avi Controller and Service Engine instances must run in Google Cloud. The cloud type selected within Avi should be Linux Server Cloud. Configuration steps for setting up a Linux Server Cloud are provided in Installing Avi Vantage for a Linux Server Cloud.
Note: GCP uses a /32-based interface IP configuration. To enable support for this, perform the below steps from the Avi Controller CLI after completing the configuration of Linux Server Cloud, and reload all the Service Engines for the configuration to take effect.
configure serviceengineproperties se_runtime_properties se_handle_interface_routes service_ip_subnets subnet/mask save save
The **service_ip_subnets **configuration optimizes the Docker routes on the Service Engines. If VIP allocation is done from multiple subnets, specify all of them.
Configuration of GCP IPAM
- Navigate to Templates -> Profiles -> IPAM/DNS Profiles and click Create.
- Provide the IPAM profile name, and select Google Cloud Platform IPAM.
- If auto-allocation of IP address for virtual services is required, select “Add Network” and then select the desired networks. For detailed steps on how to configure networks for auto-allocation, refer to VIP Allocation Using IPAM or DNS.
Note that only Avi Vantage’s allocation method is supported for GCP IPAM type, and no DNS provider is available. GCP profile information — i.e., project, zone, network, and subnets — are automatically detected.
- Click Save.
- Navigate to Infrastructure -> Cloud , and click on the cloud name.
- From the IPAM pulldown, select the IPAM profile that was configured above.
- Enable "Use Inband Management."
- Click Save.
The above steps complete the configuration of GCP IPAM. Virtual services can now be provisioned.
- On GCP only L3 scale out mode is supported for virtual services.
- Some of the GCP zones may require the MTU to be lowered to 1400. Use the below steps to set the MTU on the Service Engines. The MTU value will take effect after the Service Engines are rebooted once.
configure serviceengineproperties se_runtime_properties global_mtu 1400 save save
Updated: 2018-01-22 22:45:00 +0000