Hardware Requirements
Last updated
1.2
Last updated
The hardware requirements pertain to the kubernetes based infrastructure required to house OpenG2P modules. The number of VMs and configuration are subjected to scaled down if only specific modules are being installed.
Cluster nodes
8
32 GB
128 GB
Ubuntu Server 20.04
Wireguard
4
16 GB
64 GB
1
Ubuntu Server 20.04
Cluster nodes
8
32 GB
128 GB
3
Ubuntu Server 20.04
Wireguard*
4
16 GB
64 GB
1
Ubuntu Server 20.04
Rancher*
8
32 GB
128 GB
1
Ubuntu Server 20.04
Nginx LB*
4
16 GB
64 GB
1
Ubuntu Server 20.04
NFS for Storage
4
16 GB
1 TB*
1
Ubuntu Server 20.04
* Wireguard: One VM for Wireguard is sufficient for all the environments/setups in your network. This is used to facilitate VPN access to the pilot environments.
* Rancher: One VM for Rancher is sufficient to manage all the K8s environments/setups. This is used to facilitate K8s Access Control & Management of the pilot environments.
* Nginx Loadbalancer: Nginx VMs for load balancing. These VMs are not required if using a Cloud Provider. Instead, it is recommended to use Cloud-native Load balancers.
* NFS Storage Size: This will facilitate persistent storage for components in the K8s Cluster. The actual size of storage required will vary from setup to setup. Can be computed using the .
All the machines in the same network
Public IP assigned to the Wireguard machine
The following domain names and mappings will be required. Examples:
Top level domain that points to the sandbox.
openg2p.<your domain>
uat.<your domain>
pilot.openg2p.<your domain>
"A" Record mapped to Load Balancer IP (For sandox, where loadbalancer is not present, this can be mapped directly nodes of the K8s Cluster, at least 3 nodes).
Wildcard subdomain for accessing individual components within OpenG2P sandbox.
*.openg2p.<your domain>
*.uat.<your domain>
*.pilot.openg2p.<your domain>
"CNAME" Record mapped to the domain of the above "A" record. (This is a wildcard DNS mapping)
One wildcard certificate is required at least, depending on the above domain names used. This can also be generated using Letsencrypt.
The following are the components in each K8s cluster that require persistent storage.
PostgreSQL
Database for all modules
TBD
MinIO Object Store
For storing documents
TBD
OpenSearch
For indexing service logs (And generating reports & dashboards).
TBD
Total
TBD