Deploying Contrail Multicloud with Contrail Command
The Infrastructure: Multicloud tab was removed from Contrail Command in Contrail Networking Releases 1912.L1 and 2008. The Infrastructure: Multicloud tab remains available in all other Contrail Networking Release 19 releases and Contrail Networking Release 20 releases through Release 2005.
All functionality provided within the Infrastructure: Multicloud tab in Contrail Command is available for evaluation purposes only. This functionality is not intended for deployment in production networks.
You can provision Contrail Multicloud with the Contrail Command UI.
Contrail supports provisioning of Microsoft Azure, Amazon Web Services (AWS), and Google Cloud Platform (GCP).
Multicloud gateway (MC-GW) node interconnects different Virtual Private Cloud (VPC)/Virtual Networks (VNets) in cloud. Additionally, MC-GW extends on-premise resources to cloud.
This topic provides steps to configure Microsoft Azure, Amazon Web Services (AWS), and Google Cloud Platform (GCP) with the Contrail Command UI.
Prerequisites:
Contrail Multicloud is currently supported for deployments using Kubernetes as the orchestration platform only. See Installing Standalone Kubernetes Contrail Cluster using the Contrail Command UI.
All the on-premise nodes except the management IPs must have private IPs.
It is recommended to add static routes on all the control nodes towards the private subnets on the cloud.
Control nodes and compute nodes must be on the same subnet and MC-GW must be on a different subnet.
MC-GW node must be provisioned on RHEL 7.7.
Compute nodes on the public cloud must be provisioned on RHEL 7.7.
Instance type:
Azure—Standard_F2.
AWS—c4.xlarge or t2.xlarge.
Google Cloud Platform(GCP)—n1-standard-2
Red Hat subscription with enabled packages must be available for on-premise MC-GW nodes.
Time must be synchronized on all the nodes with NTP.
contrail-command node must have connectivity to ToRs.
You must enable NETCONF on ToRs connected to the on-premise MC-GW nodes.
You must configure IPTABLES on the on-premise MC-GW nodes with INPUT and FORWARD and default ACCEPT policy.
For Azure deployment, you must have subscription and resource group.
For details, refer to Creating a Resource Group.
For provisioning Microsoft Azure with Contrail Command, you must have Azure account. For details, refer to https://docs.microsoft.com/en-us/learn/modules/create-an-azure-account/.
For provisioning Amazon Web Services (AWS) with Contrail Command, you must have AWS account. For details, refer to https://aws.amazon.com/premiumsupport/knowledge-center/create-and-activate-aws-account/.
For provisioning Google Cloud Platform (GCP) with Contrail Command, you must have a GCP account. For details, see Creating and managing service accounts within the Cloud Identity and Access Management documentation for GCP.
Sample Topology:

Deploying Microsoft Azure with Contrail Command
To provision Microsoft Azure:
Deploying Amazon Web Services with Contrail Command
To provision Amazon Web Services (AWS):
Deploying Google Cloud Platform (GCP) with Contrail Command
Starting with Contrail Networking Release 1911, you can provision Google Cloud Platform (GCP) cloud networks within Contrail Command.
To provision Google Cloud Platform (GCP):