Configure systems for use with Calico

Calico uses the Nova metadata service to provide metadata to VMs, without any proxying by Neutron. To make that work:

• An instance of the Nova metadata API must run on every compute node.
• must not set service_neutron_metadata_proxy or service_metadata_proxy to True. (The default False value is correct for a Calico cluster.)

In you need the following settings to configure the Neutron service.

Calico can operate either as a core plugin or as an ML2 mechanism driver. The function is the same both ways, except that floating IPs are only supported when operating as a core plugin; hence the recommended setting here.

and then the further ML2-specific configuration as covered below.

The following options in the [calico] section of /etc/neutron/neutron.conf govern how the Calico plugin/driver and DHCP agent connect to the Calico etcd datastore. You should set etcd_host to the IP of your etcd server, and etcd_port if that server is using a non-standard port. If the etcd server is TLS-secured, also set:

• etcd_ca_cert_file to a file containing data for the Certificate Authorities that you trust to sign the etcd server’s certificate.

In a multi-region deployment, [calico] openstack_region configures the name of the region that the local compute or controller node belongs to.

When specified, the value of must be a string of lower case alphanumeric characters or ‘-‘, starting and ending with an alphanumeric character, and must match the value of configured for the Felixes in the same region.