.webp)
Hardware requirements
Below you can see hardware requirement table depending on user quantity:
“Medium” up to 500 licenses
|
Role |
CPU |
RAM, GB |
HD, GB |
HDD/SSD |
Azure VM-v3.0 |
|
|
1 |
mngr |
8 |
16 |
512 |
ssd |
Standard_F8s_v2 |
|
2 |
exec |
4 |
8 |
256 |
hdd |
Standard_D2_v3 |
|
3 |
gpdb |
4 |
16 |
512 |
ssd |
Standard D4s_v3 |
|
Total: |
16 |
40 |
1280 |
* |
* |
|
“Large” typical for 500-1500 licenses
|
Role |
CPU |
RAM, GB |
HD, GB |
HDD/SSD |
Azure VM |
|
|
1 |
mngr |
4 |
8 |
512 |
hdd |
Standard_F4s_v2 |
|
2 |
exec |
4 |
8 |
256 |
hdd |
Standard_D2_v3 |
|
3 |
gpdb |
4 |
16 |
512 |
ssd |
Standard_D4s_v3 |
|
4 |
mdbsh |
4 |
16 |
512 |
ssd |
Standard_D4s_v3 |
|
5 |
hbase |
4 |
8 |
512 |
ssd |
Standard_F4s_v2 |
|
6 |
app |
2 |
8 |
256 |
hdd |
Standard_D2_v3 |
|
Total: |
22 |
64 |
2560 |
* |
* |
|
“Extra Large” more then 1500 licenses.
For 1500+ deployments the parameters below should be adjusted based on the project specifics
|
Role |
CPU |
RAM, GB |
HD, GB |
HDD/SSD |
Azure VM-v3.0 |
|
|
1 |
front |
4 |
8 |
128 |
hdd |
Standard_A4_v2 |
|
2 |
mngr |
4 |
8 |
256 |
hdd |
Standard_D2_v3 |
|
3 |
mdbsh00 |
8 |
28 |
512 |
ssd |
Standard_DS4_v2 |
|
4 |
mdbsh01 |
8 |
28 |
512 |
ssd |
Standard DS4 v2 |
|
5 |
rmq |
2 |
8 |
512 |
hdd |
Standard_D2_v3 |
|
6 |
gdpb |
8 |
32 |
512 |
ssd |
Standard_D8s_v3 |
|
7 |
hbase |
4 |
8 |
512 |
ssd |
Standard_F4s_v2 |
|
8 |
app |
4 |
14 |
256 |
hdd |
Standard_D3_v2 |
|
9 |
exec01 |
4 |
8 |
256 |
hdd |
Standard_D2_v3 |
|
10 |
exec02 |
4 |
8 |
256 |
hdd |
Standard D2 v3 |
|
Total: |
50 |
150 |
3712 |
* |
* |
|
Software requirements
Supported OS:
- Ubuntu Linux (18.04 LTS);
- CentOS Linux (7.6);
- Other Linux distribution (approve required).
Network configuration:
- Each server must have a unique hostname
Necessary packages:
- wget;
- jq (1.5 and newer);
- unzip;
- curl;
- moreutils;
- realpath (coreutils in case of CentOS);
- docker (16 and newer);
- docker-compose (1.23 and newer);
- pass;
- gnupg2.
Next web-resources should be accessible on the servers where Yva platform will be installed:
- OS repository with direct or cached proxy access;
- https://download.docker.com - for latest Docker release installation;
- https://github.com/docker - for docker-compose installation;
- Yva docker repository https://cr1.yva.ai - for Yva services files deployment;
- https://release.yva.ai/ - for installation scripts obtaining;
- https://releases.hashicorp.com/ - for latest Consul release installation;
- https://weumanaged178.blob.core.windows.net/8842d41c76a74015bddbb85ce6f5dd54-9pcoc3hbq4//docker/registry - for cr1 configuration files obtaining;
- https://registry-1.docker.io/v2 - for additional docker components
Firewall rules should allow data transmission using next ports:
- 443, 80, 8080, 8888 - frontend and routers
- 32768-61000 - docker
- 8500, 8600, 8300 - consul
- 53 - int-dns
- 5672, 15672, 4369, 5671, 25672 - RabbitMQ