Description of the illustration architecture-vnic.png

The image shows a diagram of a bare metal Hadoop deployment using virtual network interface cards (VNICs), with secondary VNICs used for cluster connectivity.

The image shows a Customer Datacenter alongside an Oracle Cloud Region. Within the Region is an Availability Domain, alongside an Internet / Service / NAT Gateway and an Object Storage component. A Hadoop VCN spans the Availability Domain. The Customer Datacenter connects through to the Hadoop VCN over FastConnect VCN.

Within the Availability Domain are three Fault Domains numbered 1, 2, and 3, and four Subnets spanning the three Fault Domains, labeled Hadoop Subnet, Storage Subnet, Utility Subnet, and Bastion Subnet.

Within each of the Fault Domains, the Hadoop Subnet contains a Master component (numbered 1, 2, and 3, for each Fault Domain). Two Worker components labeled Worker 1 and 4 (Fault Domain 1), Worker 2 and 5 (Fault Domain 2), and Worker 3 and 6 (Fault Domain 3) span both the Hadoop Subnet and the Storage Subnet. Each Worker component is connected to two VNICs, labeled VNIC.1 and VNIC.0. The VNIC.1 components are within the Hadoop Subnet, while the VNIC.0 components are within the Storage Subnet. Each of the VNIC.0 components connects to its own storage component.

Within Fault Domains 1 and 3, the Utility Subnet contains a Cloudera Manager / Ambari component, labeled (Backup) in Fault Domain 1 and (Primary) in Fault Domain 3. Each of these components is connected to a database, and the two databases (in the two Fault Domains) are connected to each other.

The three Fault Domains each have an Edge VM component in their Bastion Subnets.