The following operating systems are supported out-of-the-box:
The EVA ICS installer prepares the system automatically, installing required packages. The only necessary pre-installed packages is “curl” to download and start the installation.
For a single node, which is going to host a HMI application, type:
sudo -s # the installer script requires root privileges curl https://pub.bma.ai/eva4/install | sh /dev/stdin -a --hmi
If this is a secondary node and no web services / HTTP API are required, omit the “–hmi” argument.
As the installer script always installs at least the minimal list of required system packages, it must be executed under root.
The installer automatically prepares the system, installs the latest EVA ICS distribution to /opt/eva4 (default) folder and sets up Python virtual environment in /opt/eva4/venv (for mode >= 1).
By adding “-h” or “–help” argument, the full list of the installer arguments can be obtained. Let us review the primary ones:
–hmi automatically setups authentication and web HMI services.
–mode prepares the system, by installing additional packages:
0 installs the minimal list of required packages
1 installs Python and eva-shell
2 all of the above, plus C and C++ compilers, plus development headers
3 all of the above, plus Rust compiler and additional development headers
The compilers and the development headers can be used to add custom Python modules into venv.
–prepare-only allows to install additional compilers / headers, without installing EVA ICS. Can be executed after the installation at any time.
Startup and watchdog options can be configured by editing configuration files in /opt/eva4/etc folder (create them from provided examples if missing).
Additional configuration can be performed by editing Registry database keys.
Read more in configuring documentation section.
If the automatic startup has been set up, EVA ICS node is started automatically either by Systemd or by OpenRC (Alpine). To start/stop the node server manually, use either “/opt/eva4/sbin/eva-control” script or eva-shell.
An optional Python virtual environment can be configured using the command:
or by editing “eva/config/python-venv” registry key in eva-shell or in other tools.
To rebuild the virtual environment from scratch, completely delete /opt/eva4/venv folder or call the above command with -S argument.
To update a local node, use the command:
eva update # or /opt/eva4/bin/eva-cloud-manager node update
If any remote nodes are connected with replication services and configured as managed (admin key is set), they can be updated using cloud-update feature:
eva cloud update # or /opt/eva4/bin/eva-cloud-manager cloud update
After being started, the cloud-update firstly gathers facts about the available nodes and after offers the update plan, which must be additionally confirmed.
Remote nodes are always updated to the same version, which the management node has got.