Step-by-step process to launch Klera on Google cloud platform, starting with instance launch.
Klera Production System Specifications
To allow user select a particular configuration in a private cloud. The hardware requirement is as follows:-
Base Platform - 250 users/node, 5% concurrency
Cores |
RAM |
HDD |
8 cores hyper-threaded (16 threads) |
64GB |
Enterprise grade SSD for Klera installation – Total 1TB in Raid 5 configuration |
Base Platform with AI/ML/Python support - 250 users/node, 5% concurrency
Cores |
RAM |
HDD |
16 cores hyper-threaded (32 threads) |
128GB |
Enterprise grade SSD for Klera installation – Total 1.6TB in Raid 5 configuration |
- In the Google Cloud console, go to the VM instances Go to VM instances
- Select your project and click Continue
- Click Create instance.
- Specify a Name for your VM. For more information, see Resource naming convention.
- Optional: Change the Zone for this VM. Compute Engine randomizes the list of zones within each region to encourage use across multiple zones.
- Select a Machine configuration for your VM.
- In the Boot disk section, click Change, and then do the following:-
- On the Public images tab, choose the following:
- Operating system
- OS version
- Boot disk type
- Boot disk size
Instance type
RAM
CPU
Disk
OS
n2-standard- 16
64.0 GiB
16 vCPUs
SSD Persistent disk 1 TB
1. RHEL 7.9
(For SAP with HA)
2. Windows
n2-standard-32
128.0 GiB
32 vCPUs
SSD Persistent disk 1.6 TB
Documentation: https://cloud.google.com/compute/docs/general-purpose-machines#n2-standardGiven N2 series, all workloads that can take advantage of the higher clock frequency are a good choice for this series. These workloads can get higher per-thread performance while benefiting from all the flexibility that the general-purpose machine family offers.
Please note, OEL 7.6 is not available Google marketplace
- Optional: For advanced configuration options, click Show advanced configuration.
- To confirm your boot disk options, click Select.
- On the Public images tab, choose the following:
- In the Firewall section, to permit HTTP or HTTPS traffic to the VM, select Allow HTTP traffic or Allow HTTPS traffic. When you select one of these, Compute Engine adds a network tag to your VM, which associates the firewall rule with the VM. For more details on VPC, click here .
Then, Compute Engine creates the corresponding ingress firewall rule that allows all incoming traffic on tcp:80 (HTTP) or tcp:443 (HTTPS).
- Firewall rules are defined at the network level, and only apply to the network where they are created; however, the name you choose for each of them must be unique to the project.
- Define the Protocols and ports to which the rule applies:
- Select tcp to include the TCP protocol and destination ports. Enter all or a comma-delimited list of destination ports
- These rules specify which incoming network traffic is delivered to your instance.
Klera Service
Hosting Port
Klera UI Service
18080
Klera Content Viewer
18089
Account Management
48444
File Hosting Server
48446
SSH / RDP
22 / 3389
SMTP
465 / 587
- To a public SSH key to instance metadata at the same time using the Cloud console, expand the networking, disks, security, management, sole tenancy section, and do the following:
- Expand the Security section.
- Select Add manually generated SSH keys.
- Click Add item.
- Add your public key in the text box. The key must be in one of the following formats:
- Format for a key without an expiration time: KEY_VALUE USERNAME
- Format for a key with an expiration time:
KEY_VALUE google-ssh {"userName":"USERNAME","expireOn":"EXPIRE_TIME"}
- Replace the following:-
• KEY_VALUE: public SSH key value
• USERNAME: username for the SSH key, specified when the key was created
• EXPIRE_TIME: time the key expires, in ISO 8601 format. For example:2021-12-04T20:12:00+0000
- Expand the Security section.
- To create and start the VM, click Create.
- A virtual machine (VM) instance requires a fixed external IP address that does not change, you can obtain a static external IP address. You can promote an ephemeral external IP address.
If your instance has an ephemeral external IP address and you want to permanently assign the IP to your project, promote the ephemeral external IP address to a static external IP address.
Promoting an ephemeral external IP address to reserved does not cause Google Cloud to drop packets sent to the instance.
Install Klera
Please follow the below process to install Klera on Windows/Linux system
Click here for Windows based deployment
Click here for Linux based deployment
For more assistance, please reach out to support@klera.io