Deployment using OVA file - Rocky9

Deployment VeridiumID Using OVA File – Rocky 9

As part of your deployment resources, VeridiumID provides an “out-of-the-box” OVA image. This image (available through the Veridium Sales Engineering team or Professional Services) can be used for Proof-of-Concept (PoC) or Production environments.

Before proceeding, ensure you have already imported the OVA (see the section on “How to Import an OVA File”). After import, begin the setup and installation. Make sure your server has a Fully Qualified Domain Name (FQDN) in DNS (and ideally a correct PTR record).

1. Virtual Console Setup

Connect to the VM’s console, authenticate, then change default credentials, hostname and IP address:

Default login credentials:
- Username: rocky
- Password: VeridiumID123!
Change the password:
CODE
```
passwd
```
View current network configuration:
CODE
```
sudo ifconfig
```
Use Network Manager TUI for static IP/hostname setup:
CODE
```
sudo nmtui
```
Set a static IP and appropriate hostname from the interface.

Reboot the VM (you can use sudo reboot or reboot via VMware tools).

Configure NTP/Time sync (Chrony):

CODE

sudo systemctl status chronyd  
sudo systemctl enable chronyd  
sudo systemctl start chronyd  
sudo chronyc -a sources  
sudo timedatectl list-timezones | grep Europe/Bucharest  
sudo timedatectl set-timezone Europe/Bucharest

If no NTP server is available, a manual date set is possible.

Verify the timezone and local zone are correctly defined:
CODE
```
sudo timedatectl
```

2. Run Veridium installation

In order to continue with the deployemnt, see VeridiumID server On prem Deployment using VeridiumInstaller.

Go directly to 2.3 Run the Veridium Installer

Run the installer with parameters identifying Web and Persistence nodes:

CODE

./veridium-installer.sh -w <web_nodes_IPs> -p <persistence_nodes_IPs>

Example:

CODE

./veridium-installer.sh -w 10.10.10.11,10.10.10.12 -p 10.10.10.21,10.10.10.22,10.10.10.23

This launches the interactive configuration wizard.