Compute plane
Component of HTC Grid that executes actual workloads; can be implemented using EC2, EKS, or native Kubernetes depending on customer preferences
As defined in Building and Running an HPC Grid Using Cloud Native Services - Flamur Gogolli & Kirill Bogdanov
Where it comes up · 1
- Building and Running an HPC Grid Using Cloud Native Services - Flamur Gogolli & Kirill Bogdanov3 claims
Most important claims · 3 of 3Search all claims for “Compute plane” →
- The same logic for choosing data plane storage applies to the compute plane: EKS or Kubernetes is perhaps the most common choice because of interoperability and ability to run on-premises and on other cloud providers, but there is no one-size-fits-all solution and the list can be extended if customers want something elseBuilding and Running an HPC Grid Using Cloud Native Services - Flamur Gogolli & Kirill Bogdanov
- Future planned scaling improvements for HTC Grid include adding Karpenter for faster compute plane scaling with diverse purchasing options, scaling based directly on queue depth metrics to the cluster, and implementing more aggressive scaling algorithms to reach the required scales fasterBuilding and Running an HPC Grid Using Cloud Native Services - Flamur Gogolli & Kirill Bogdanov
- HTC Grid has three main components: a client application (REST API entry point), a control plane (fully serverless and managed services), and a compute plane (with modular variants like EC2, EKS, or Kubernetes), plus a data plane for task submission and retrievalBuilding and Running an HPC Grid Using Cloud Native Services - Flamur Gogolli & Kirill Bogdanov