Standard Shapes Supported for GCP Deployment
Oracle Enterprise Communications Broker Release 5.0.0 supports deployment on Google Cloud Platform (GCP).
Communications Broker can be deployed as a virtualized Machine in GCP on an N2 Machine type, which offers a range of sizes and configurations. These machine types have been tested and validated to meet Communications Broker performance requirements. The table below highlights the supported N2 configurations.
Table 9-1 Standard Shapes Supported
| Machine Types | vCPUs | RAM (GB) | vNICs | Network Egress Bandwidth (Gbps) | Max Tx/Rx queues per VM |
|---|---|---|---|---|---|
| n2-standard-4 | 4 | 16 | 4 | 10 | 4 |
| n2-standard-8 | 8 | 32 | 8 | 16 | 8 |
| n2-standard-16 | 16 | 64 | 8 | 32 | 16 |
Note:
The limiting factor for these Machine types are the number of available VNICs and number of Forwarding cores, as the Communications Broker can run with fewer CPUs and memory.Here are few points to be noted before deploying an Communications Broker on GCP.
- Communications Broker installation is supported using Terraform scripts.
- A single s0p0 interface is sufficient to handle Communications Broker traffic.
- The run-setup command should not be performed on public cloud infrastructure.
- The default Communications Broker configurations (such as, dialing-context, policy-config, and http-server) can be loaded by executing the command spl load acli baseconfig from the ACLI. After loading, make sure to run save and activate to apply the changes.
- Communications Broker support HA on Google Cloud Platform.