Stand alone server solution
To process packets from 10,000 terminals, the minimum requirement is:
˗ Processor – at least 8 threads (server);
˗ Memory – minimum 64 GB;
˗ Disk space – 2TB SSD for DBMS, 1TB HDD for storing xml files. In case of deployment on a hardware server – RAID10;
- The presence of an SSD for the database with the number of objects from 1000 is strictly recommended;
- When configuring devices to send data frequently (one point every 1-5 seconds), hardware requirements may increase (frequent writing/reading of data to the database, CPU/RAM load when recalculating raw data, load when receiving points, etc. ).
Data storage period on the server:
raw - up to 3-4 months (can be restored upon request) (storage period depends on disk space);
aggregated - unlimited.
When connecting more than 5,000 objects, it is optimal to use a separate database server with an SSD for the DBMS.
This installation excludes the use of PTM, Video, Logistics modules.
To use the PTM and Logistics modules, it is recommended to use a separate Oracle Linux server.
To use the Video module, you must use an additional Windows Server.
Separate DBMS server
- OS - Oracle Linux 8.x;
˗ Processor – from 8 threads (server);
˗ Memory – from 64 GB;
˗ Disk space – from 2TB SSD for DBMS;
- The presence of an SSD with the number of objects from 1000 is strictly recommended;
- Availability of a direct connection (local network) with the application server.
Separate Server for PTM and Logistics
- Includes similar requirements to the basic server + 30% capacity, configurations with 3000+ objects are discussed separately.
Video Server
OS - Windows Server 2016 or later
˗ Processor – from 16 threads (server);
˗ Memory – from 128 GB;
˗ Disk space – from 3 TB. (the amount of disk space affects the volume of stored video files)
- Broadband network access (the server processes video streams).
System structure
The Pilot system is installed on the Oracle Linux 8 (64-bit) operating system. The system can be deployed in a virtual environment with network port forwarding.
The PILOT system includes:
˗ Nginx.
˗ PostgreSQL 16;
˗ PHP v.8 + php-fpm;
˗ Redis;
˗ Memcache;
˗ SocketProxy server + Device communicator
as well as dependencies, libraries for the operation of the above components and standard OS administration and monitoring tools.
System options:
Working – a separate Linux installation with full parameters.
Test – separate installation (installed optionally), up to 100 objects, with parameters:
˗ Processor – at least 4 threads;
˗ Memory – at least 4 GB;
˗ Disk space – 200 GB.
Backup Requirements
Database backup is carried out using DBMS. It is necessary to have 1TB of “slow” disk space to store backups on physical equipment other than the one where “PILOT” is deployed.
Copying source data (xml files) requires 500 GB of “slow” disk space. During system operation, the amount of disk space occupied by backup copies can be increased.
With large volumes of data, a large number of objects and a high frequency of sending data, the requirements may increase.
External resources
For the server:
Geocoding
If internal geocoding is not configured, then we use global one and need access to global.pilot-gps.com (208.76.249.186) via the http protocol and port 80 and 443.
Routing
If local routing is not configured, then we use global routing and need access to global.pilot-gps.com (208.76.249.186) via the http protocol and port 5000.
Logistics
If the local logistics algorithm is not configured, we use the global one and need access to vroom.pilot-gps.com (208.76.249.186) via the http protocol and port 3000.
Updates
To download updates, you need access from the server to gitlab.pilot-gps.com via the ssh protocol and port 22122.
For operating system updates
Access to any resources must be open via the https protocol, since Oracle Linux is updated using the nearest available mirror, the host is searched dynamically.
Alternatively, system administrators must configure the server to update from an internal source (local repository or proxy).
For clients
If a local Tile server is not configured, then to receive tiles, client workstations must have access via http and https protocols to the following resources:
Conditions for server installation
At the time of server installation, the server must be connected to the Internet without any restrictions.
Access to the server can be limited only after installation of all necessary components has been completed.
Terms of server technical support
To provide technical support for the server, access via SSH is required. If you do not have access via SSH, technical support cannot be provided.
Update order
The system is updated from the repository http://gitlab.pilot-gps.com/. The update process requires access to the operating system repositories. Access to the repositories is provided via the Internet.
Lack of Internet access when updating components will stop the update process.