Private Cloud Deployment
GMetri can run a dedicated cluster in the AWS/GCP/Azure region of your choice to make sure you internal compliance needs are met. Please note that you need to be subscribed to an enterprise tier license to request this chargeable feature. Contact us to know more.
Does GMetri support on-premise deployments/Are there additional costs for the same?
There are cases where security policies demand an on-premise deployment of cloud services (firewalled zone).
For such cases, at an additional cost, GMetri supports on-premise deployments.
Additional Costs
There will be a one-time cost that can be determined if you contact us with the following details:
The hardware configuration of the servers on which this service is to be deployed.
Whether you use a cloud service provider like Google Cloud/AWS/Azure/Others or if you manage, provision your own servers and server racks (bare-metal).
The general practice followed to (remotely) access the servers.
The protocol to open certain network ports for the servers.
There may be additional SLA charges as needed.
These costs are in addition to the standard Enterprise Tier annual/monthly license cost you would incur even without the on-Prem deployment.
The option to deploy on-premise is available with the Enterprise Tier License only.
Which network ports needs to open for a private cloud deployment?
Ideally, within the cluster, communication needs to be open - i.e. all cluster nodes should be able to contact all ports of all other cluster nodes.
However in case a list of open ports is required, you can use the following list:
Deployment Types and Hardware Requirements
Private Cloud Deployment (firewalled zone)
The GMETRI platform deploys as a Kubernetes cluster.
Below are the hardware and network requirements to set up a Kubernetes cluster in a private cloud that supports the GMetri platform.
Server Requirements
The following table lists the minimum requirements setting up a High Availability (HA) cluster:
On Cloud (AWS/GCP/Azure)
Bare Metal (HA Setup)
Full network connectivity between all systems in the cluster
Ability to configure open ports on these systems
Failure resilience for production servers: 1 for master nodes and 1 for worker nodes separately. The resilience is of (n-1)/2 nodes per node-type where n is the number of nodes.
Single Rack-server/Desktop Deployment
We ideally recommend that GMetri is deployed on a cluster setup in a private cloud consisting of a minimum of 3 servers. However, in cases where that is not possible, GMetri can also be deployed on a single rack-server or a desktop.
Hardware Requirements
The following are the recommended hardware requirements for such a deployment:
Keep in mind that this is not a HA (High Availability) setup. This means that any hardware failure could lead to permanent loss of data. In cases where data resiliency is critical, we recommend a cluster setup.
Other Requirements
Operating System Requirements
The Operating System used will depend completely on the flavour of Kubernetes deployed. Examples are RancherOS, Ubuntu, CoreOS etc.
Preferred OS
For Bare Metal deployment: Ubuntu 18+
Partitioning
Ensure that there is no swap partition.
Network Requirements
Network Response Time
Within the cluster, ideally communication needs to be open - i.e. all cluster nodes should be able to contact all ports of all other cluster nodes.
In case a list of specific ports is needed, refer to this here.
Internet Connectivity Requirement During updates and initial installation, internet connectivity is needed. For usual operations, internet connectivity isn’t required.
Example Rack Server/Desktop Tower configuration
An example of a single rack server or a desktop tower to support the above deployment would be the following:
An example of a single rack server or a desktop tower to support the above deployment would be the following:
4 or 6 such servers/desktop towers are required to form a cluster as mentioned above.
For any other queries, write to support@gmetri.com
Last updated