Aviatrix Oracle Cloud (OCI) Transit Network Setup

In the previous blog post, we performed the initial OCI on-boarding. Now here we will show how to build a transit network in OCI as some architects referred to as Hub and Spoke network architecture. This is the common cloud architecture that Aviatrix provide across all major Clouds such as AWS, Azure and GCP. This common cloud architecture provide consistent operational tools and visibility into different Cloud Networks.

Business Requirement to connect GCP and OCI

Our objective is to build the following topology where we have same common transit architecture deployed in GCP as well as OCI. The business requirement is to connect to GCP to utilize ML/Analytics tools that are not available in OCI. The GCP transit is already built using Aviatrix technology and we will focus on building the OCI transit network and then connecting it GCP with encrypted transit peering via Aviatrix Controller.

Multi-Cloud Common Architecture in GCP and OCI

Aviatrix Transit Gateway Deployment in OCI

As first step, we logged into the controller and launched the workflow to deploy the Aviatrix Transit VCN Gateway (OCI calls VPC as VCN: Virtual Cloud Network). The VCNs were build in the previous blog here.

Notice the easy of deploying it in the region on your choice with the size that your business require. Also notice that Public Subnet was automatically created by Aviatrix and one does not need to worry about creating it from scratch.

Launch Aviatrix Gateway (AVX-Transit-GW) in OCI VCN

Once you hut create button, the Aviatrix Controller will communicate with the OCI and will deploy the Aviatrix Gateway. Following output shows the process of creating this transit gateway.

Aviatrix Controller Output to deploy Transit Gateway

[21:42:57] Starting to create OCI GW OCI-Transit-GW-Ashburn.
[21:42:58] Connected to Oracle OCI.
[21:42:58] Deploying virtual machine…
[21:44:32] Deploy virtual machine done.
[21:44:32] Configure virtual machine.
[21:44:33] License check is complete.
[21:44:33] Added GW info to Database.
[21:44:35] OCI-Transit-GW-Ashburn AVX SQS Queue created.
[21:44:35] Create message queue done.
[21:44:35] Initializing GW…..
[21:45:06] Copy configuration to GW OCI-Transit-GW-Ashburn done.
[21:45:06] Copy new software to GW OCI-Transit-GW-Ashburn done.
[21:45:06] Copy /etc/cloudx/cloudx_code_file.json.enc to GW OCI-Transit-GW-Ashburn done.
[21:45:06] Copy /etc/cloudx/cloudx_code_key_file.txt to GW OCI-Transit-GW-Ashburn done.
[21:45:06] Copy scripts to GW OCI-Transit-GW-Ashburn done.
[21:45:06] Copy sdk to GW OCI-Transit-GW-Ashburn done.
[21:45:06] Copy libraries to GW OCI-Transit-GW-Ashburn done.
[21:45:06] Installing software ….
[21:45:06] Issuing certificates….
[21:45:06] Issue certificates done
[21:45:15] GW software started.
[21:45:29] Software Installation done.

You can now login to OCI console and notice the instance deployed in the Finance Compartment or department

Aviatrix Transit Gateway Deployed in OCI

Following output shows the type of instance and bunch of other information directly gathered from the OCI console.

Instance Information
Availability Domain: RGRl:US-ASHBURN-AD-2
Image: Published Image: aviatrix_gateway_0415_1017_20190820
Fault Domain: FAULT-DOMAIN-2
OCID: ...dsmskaShowCopy
Region: iad
Launched: Thu, 17 Oct 2019 04:43:00 UTC
Shape: VM.Standard2.2
Compartment: shahzadali (root)/Finance-Compartment
Virtual Cloud Network: OCI-Transit-VCN-Ashburn
Launch Mode: NATIVE
Maintenance Reboot: -
Primary VNIC Information
Private IP Address: 10.111.0.2
Internal FQDN: av-gw-oci-transit-gw-ashburn...ShowCopy
Public IP Address: 150.136.206.183
Subnet: OCI-Transit-VCN-Ashburn-public-subnet
Network Security Groups: aviatrix-security-group
This instance's traffic is controlled by its firewall rules in addition to the associated Subnet's security lists and the VNIC's network security groups.
Launch Options
NIC Attachment Type: VFIO
Firmware: UEFI_64
Remote Data Volume: PARAVIRTUALIZED
Boot Volume Type: PARAVIRTUALIZED

Important point we would like to highlight that in order to get all that information, one does not really need to login to OCI console. All this information is also available from the Aviatrix Controller UI itself. This is great operational benefit because now operators don’t need to worry about learning different clouds and their constructs.

Aviatrix Spoke VCN Deployment in OCI


Aviatrix Spoke Gateway Deployment in OCI

[21:58:12] Starting to create OCI GW OCI-Spoke-GW1-Ashburn.
[21:58:12] Connected to Oracle OCI.
[21:58:12] Deploying virtual machine…
[21:59:46] Deploy virtual machine done.
[21:59:46] Configure virtual machine.
[21:59:47] License check is complete.
[21:59:47] Added GW info to Database.
[21:59:49] OCI-Spoke-GW1-Ashburn AVX SQS Queue created.
[21:59:49] Create message queue done.
[21:59:49] Initializing GW…..
[22:00:20] Copy configuration to GW OCI-Spoke-GW1-Ashburn done.
[22:00:20] Copy new software to GW OCI-Spoke-GW1-Ashburn done.
[22:00:20] Copy /etc/cloudx/cloudx_code_file.json.enc to GW OCI-Spoke-GW1-Ashburn done.
[22:00:20] Copy /etc/cloudx/cloudx_code_key_file.txt to GW OCI-Spoke-GW1-Ashburn done.
[22:00:20] Copy scripts to GW OCI-Spoke-GW1-Ashburn done.
[22:00:20] Copy sdk to GW OCI-Spoke-GW1-Ashburn done.
[22:00:20] Copy libraries to GW OCI-Spoke-GW1-Ashburn done.
[22:00:20] Installing software ….
[22:00:21] Issuing certificates….
[22:00:21] Issue certificates done
[22:00:28] GW software started.
[22:00:42] Software Installation done.

Enable ActiveMesh For Aviatrix OCI Transit and Spoke Gateways

AVX-CTRL –> Gateway –> Enable ActiveMesh Mode Info

Connect AVX-Spoke GW to AVX-Transit GW

Aviatrix Transit VPC and Transit GW Routing Tables

The OCI Transit VPC Route Table is Empty because all routing is done by the Transit-GW

Aviatrix Spoke VPC and Spoke GW Routing Tables

Transit GW Peering between GCP-Transit-GW and OCI-Transit-GW


After about a minutes the transit peering comes UP

Test Topology

(10.76.1.2) gcp-vm–>gcp-spoke–gcp-transit-gw—–>oci-transit-gw–>oci-spoke–>oci-vm (10.112.128.2)

Traceroute from GCP Test VM to OCI-Test VM
Ping from GCP Test VM to OCI-Test VM

Conclusion

Aviatrix allows a common topology across multiple clouds. This makes the enterprise network and security deployments seamless. There are no surprises and IT admins does not need to know the underlying artifacts of various clouds.

Advertisements
Featured

Network Joints

Networking and Networks have transformed over period of time. Enterprises have realized that public cloud is the strategic direction for their IT infrastructure and applications. The service providers like Amazon, Google and Microsoft are extremely efficient at providing networking, security, compute and storage capabilities in their respective public cloud such as AWS, GCP and Azure.

“All Clouds are not created equally”. In order to get the best of each and every cloud, there is a need to create seamless joints between those clouds which should, like human body joints, work in conjunction with each others. They should work in harmony, in an orchestrated fashion. This joining and marriage has given birth to a new Networking Architecture, what we call “Multi-Cloud” today.