.webp)
Hardware requirements
Below you can see hardware requirement table depending on user quantity:
|
Role |
CPU |
RAM, GB |
HD, GB |
HDD/SSD |
Azure VM |
|
|
“Small” typical for <100 licenses |
||||||
|
1 |
mngr |
8 |
16 |
512 |
ssd |
Standard_F8s_v2 (8 CPU 16 RAM) |
|
2 |
exec |
4 |
8 |
256 |
ssd |
F-Series v2 F4s_v2 (4 CPU 8 RAM) |
|
“Medium” typical for 100-500 licenses |
||||||
|
1 |
mngr |
8 |
16 |
512 |
ssd |
Standard_F8s_v2 (8 CPU 16 RAM) |
|
2 |
exec |
4 |
8 |
256 |
ssd |
F-Series v2 F4s_v2 (4 CPU 8 RAM) |
|
3 |
gpdb |
4 |
16 |
512 |
ssd |
Standard D4s_v3 (4 CPU 16 RAM) |
|
“Large” typical for 500-3,000 licenses |
||||||
|
1 |
mngr |
4 |
8 |
512 |
ssd |
Standard_F4s_v2 (4 CPU 8 RAM) |
|
2 |
exec |
4 |
8 |
256 |
ssd |
F-Series v2 F4s_v2 (4 CPU 8 RAM) |
|
3 |
gpdb |
4 |
16 |
512 |
ssd 2300 IOPS |
Standard_D4s_v3 (4 CPU 16 RAM) |
|
4 |
mdbsh |
4 |
16 |
512 |
ssd 2300 IOPS |
Standard_D4s_v3 (4 CPU 16 RAM) |
|
5 |
hbase |
4 |
8 |
512 |
ssd 2300 IOPS |
Standard_F4s_v2 (4 CPU 16 RAM) |
|
6 |
app |
2 |
8 |
256 |
ssd |
Standard_D2_v3 (4 CPU 16 RAM) |
|
“Extra Large” typical for 3,000-10,000 licenses. For 10,000+ deployments the parameters below should be adjusted based on the project specifics |
||||||
|
1 |
mngr |
4 |
16 |
512 |
ssd |
Standard_F4s_v2 (4 CPU 8 RAM) |
|
2 |
exec |
8 |
16 |
256 |
ssd |
F-Series v2 F4s_v2 (8 CPU 16 RAM) |
|
3 |
gpdb |
8 |
32 |
5120 |
ssd 7500 IOPS |
Standard_D8_v4 (8 CPU 32 RAM) |
|
4 |
mdbsh |
8 |
32 |
5120 |
ssd 7500 IOPS |
Standard_D8_v4 (8 CPU 32 RAM) |
|
5 |
hbase |
8 |
32 |
512 |
ssd 7500 IOPS |
F-Series v2 F8s_v2 (8 CPU 32 RAM) |
|
6 |
app |
8 |
16 |
256 |
ssd |
F-Series v2 F4s_v2 (8 CPU 16 RAM |
|
7 |
rmq |
4 |
16 |
512 |
ssd 5200 IOPS |
Standard_D2_v3 (8 CPU 16 RAM) |
Software requirements
Supported OS:
- Ubuntu Linux (18.04 LTS);
- CentOS Linux (7.6);
- Other Linux distribution (approve required).
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