Onteon Control Center - Installation¶

Simple Installation¶

Download the suitable Onteon Control Center Installation package.

If you downloaded installation package, untar it and run:

sudo ./install.bash

Installation contains everything that Onteon Control Center needs to work.

Installation script will:

• install Onteon Control Center as a system service.
• create (if not exist) user that runs Onteon Control Center.
• clean the installation files.
• start Onteon Control Center.

For more advanced installation, read Advanced Installation Chapter.

Advanced Installation¶

Download the suitable Onteon Control Center Installation package.

If you downloaded installation package, untar it.

Help¶

To get list of installation parameters, run sudo ./install.bash --help.

Onteon Control Center installation script.

Optional arguments:
  --cluster-base-url cluster_base_url - list of all Control Center node addresses.
  --ip-address ip_address - ip address of Onteon Control Center.
  --fqdn fqnd - fqdn server name of Onteon Control Center.
  --do-not-start - do not start Control Center after the installation. By default it is false.
  --user user - linux user. If specified user does not exist it will be created. Default user is 'onteon'.
  --group group - linux group. If specified group does not exist it will be created. Default group is 'onteon'.
  --installation-dir path - installation path. By default it is /usr/local/bin.
  --zone-id zone_id - id of the Control Center's zone. Default zone id is '000000000000000000000000'.
  --zone-name zone_name - name of the Control Center's zone. Default zone name is '000000000000000000000000'.
  --node-id zone_id - id of the Control Center.
  --node-name zone_name - name of the Control Center.

Scaling¶

If you are going to install multiply instances of Onteon Control Center, you need to use --cluster-base-url parameter.

Instances need to be installed with --cluster-base-url parameter.

sudo ./install.bash \
  --cluster-base-url http://<primary-instance-ip-address>:7020/_by_name/core-microservice

resourceManager:
  version: 1.11.0
  isActive: true
  isBackwardCompatibilityToOCC1: false
  localStoreDbUri: http://localhost:7022
  startupOccApiToken: a9f3c2e8b47d6a1f09ce5d24b8a7e3f2
  startupOccServerTrustChainPathToFile: tls/server-trusts/occ/server-trusts.crt
  register:
    urls:
    - http://<primary-instance-ip-address>:7021/_by_name/core-microservice/v1/occManagerHandler/registerNodeManagerOccController
    - http://127.0.0.1:7021/_by_name/core-microservice/v1/occManagerHandler/registerNodeManagerOccController
    - http://<next-instance-ip-address>:7021/_by_name/core-microservice/v1/occManagerHandler/registerNodeManagerOccController
    - http://<next-instance-ip-address>:7021/_by_name/core-microservice/v1/occManagerHandler/registerNodeManagerOccController

This configuration ensures that if there is no connection to the primary Onteon Control Center instance, current instance will connect to the second one, if not then to the third one and so on.

Manual Installation¶

Production ready¶

For production environment we highly recommend to create a cluster with minimum two nodes.

Download¶

Download suitable Onteon Control Center version.

Extract¶

Unpack downloaded archive on every OS which will run Control Center's node.

Start¶

Start running Control Center with only one node with the command shown below.

./start/start.sh

Logs¶

You can find Onteon Control Center logs in onteon-control-center/log/node-manager directory.

Additionally, you can find Onteon Control Center's microservice's logs in the onteon-control-center/log/app/<app-name>/<app-version>/<app-id>/<instance-id> directories.

Here onteon-control-center/log/node-manager/start.out you can find start logs.

Firewall Ports¶

7019/tcp - External Edge Balancer HTTPS port.

7020/tcp - External Edge Balancer HTTP port.