Gateway startup and stop

Gateway components are executed and stopped via scripts available in $ELTGW_ROOT/bin.

Start

The script to start the eltGW and vltGW is named startGW.sh. It is started directly from the eltGW Virtual machine either without parameter, in which case the default host vltgw will be used for the vlt gateway host, or with a parameter if another host name were used. Before launching it, a few configuration is needed for the remote execution of the vltGW gateway and for the local startup of the eltGW.

VLT gateway

To start vltGW, startGW.sh performs a remote execution of the vgw CCS environment with ssh. For this reason, a public/private RSA key pair should be generated with the following command:

ssh-keygen -t rsa.

After following the prompts, a public and private key are created. The public key should then be copied to the vltGW virtual machine with:

ssh-copy-id vgw@**vlt gateway host**

ELT gateway

To start eltGW, startGW.sh is using the nomad workload manager and the consul service registry.

Check

To check whether the vltGW is running, you should connect on the vltGW VM as vgw and execute the command: ccsPerfMon. A list of process will be returned, inMsgVGW, inScanVGW, outMsgVGW and outScanVGW shall be part of them.

To check whether the eltGW is running, you should connect on a machine that belongs to the eltGW nomad cluster and execute the command:

nomad job status evltgw

to get the job status and the id of the allocation executing the service. To access the logs of the eltGW service, you can do:

nomad alloc logs allocation id startGW.

If for any reason no allocation were created, launch:

journalctl -u nomad -f

to get log entries from the systemd journal.

Stop

The script to stop the two gateway components is stopGW.sh. It shall be located as well into $ELTGW_ROOT/bin. After completion, the vgw environment shall be stopped on the vltGW VM and the following command executed on eltGW VM:

nomad evltgw job status

shall indicate that the evltgw job is not running.