Skip to content

VTC usage

Configuration

The primary configuration file is located at /etc/dvn-ng/config.json.

Configuration options are described in cli-args.md and can also be shown using vtc_ng -h

Registration

On first-time use of a VTC, you must register with a Controller. The key and pin values will be unique to each VTC and can be viewed in Orchestrator in the VTC > Utilities > Show Key/PIN modal.

Registration example:

vtc-ng --key=abcd1234abcd1234 --pin=12345 --registrationHostname=corp01.dispersivecloud.com --registrationPort=49012

After registration, the file vtc_config.jsec should be created in /etc/dvn-ng/. After this one-time registration the vtc can be run without the registration arguments.

Log files

The VTC logs are in JSON format and are written to /etc/dvn-ng/vtc_master.log. If the log file exceeds 64 MB, it will automatically be rotated into compressed archive file with the format e.g.:

vtc_master-2024-02-23T21-53-16.833.log.gz

Systemd unit

The default method of running the VTC application after initial registration is via systemctl. This will run the application in the background and will automatically restart the VTC if necessary.

  • To get the current status of the application, run systemctl status dvn-vtc-ng
  • To enable automatic startup of the VTC, run systemctl enable dvn-vtc-ng
  • To start or stop the VTC, run systemctl start dvn-vtc-ng or systemctl stop dvn-vtc-ng

VTC certificate file

The file at /etc/dvn-ng/certificates/controller.cert is used to specify the root CA cert to trust when when connecting to a Controller. The cert that is provided with the application is the default Dispersive root CA.

In order to support a different root cert, you can replace the controller.cert file with the public component of the root certificate that was used to sign the Controller's TLS certificates.