1. Introduction
The sizing requirements of the OneFirewall Alliance solution, depending on the Service Level Agreement (SLA) and the log throughput, are summarized in the following table:
In the next sections we explore the different installation types by OFA configuration, providing a typical sizing example for a cloud provider (GCP) along with indicative infrastructure costs.
2. P-Micro
The P-Micro sizing solution targets a testing environment, enabling the installation of the OneFirewall solution on a single VM.Requirements and Costs
For Compute Engine (CE) or Google Kubernetes Engine (GKE), the system or Kubernetes user must be able to independently configure the environment (
sudoers privileges or unrestricted RBAC management).
3. P-0 (ProdSmall)
Requirements and Costs
Compute Engine or GKE users must have privileges to configure the environment (
sudoers or unrestricted RBAC), and IAM rules for ingress and external load balancer 443.
4. P-1 (ProdMedium)
Requirements and Costs
Users must be able to configure the environment independently (
sudoers or unrestricted RBAC), and manage IAM rules for ingress and external load balancer 443.
5. P-2 (ProdEnterprise)
Requirements and Costs
For Compute Engine or GKE, users must have
sudoers or unrestricted RBAC access, and appropriate IAM rules for ingress and external Load Balancer 443.