The open source HashiCorp Vault is used to securely store configuration data for Telco Network Cloud Orchestration (TNC-O). It is exposed on an ingress port as host vault.lm Vault has a GUI which can be used to alter the data held. This GUI is protected by a Vault Token with the token allocated to vault during the installation at which time the time-to-live for the token is also set. On expiry, this key will need to be changed or reset to its current value to maintain access to vault for both users and the set of TNC-O microservices. »

Introduction Telco Network Cloud Orchestration (TNC-O) can communicate with a number of Resource Managers (RM) when executing the set of tasks of an intent. This communication is through the OSSLM API. There are three timers and three associated timer configurations values which govern this relationship. alm.http.clientReadTimeout alm.daytona.resource-manager.default-timeout-duration alm.daytona.resource-manager.polling-interval Setting Default Setting Description alm.http.clientReadTimeout 30s Defaulting to 30 seconds, clientReadTimeout represents the time that the Intent Engine will wait for a response to the task execution request from the RM alm. »

Enabling the dashboard links for a running TNC-O Add the following to the nimrod secret in vault: "alm.nimrod.loggingDashboard.application": "kibana", "alm.nimrod.loggingDashboard.enabled": "true", "alm.nimrod.loggingDashboard.endpoint": "http://kibana.lm:31001", "alm.nimrod.loggingDashboard.kibana.index": "lm-logs" Create an index in Kibana named lm-logs Delete the Nimrod pod kubectl delete pod <nimrod pod id>> »

Pre-requisites To follow this guide you will need: an existing installation of the Telco Network Cloud Orchestration (TNC-O) Vault Many of the applications installed as part of the Lifecycle Manager load configuration from a configuration repository service. Vault is the chosen storage mechanism for any secure config required by the microservices. It is an industry standard approach to storing sensitive information and stores all secure config in a highly encrypted format. »

The following guide explains how to upgrade a running Telco Network Cloud Orchestration (TNC-O) to scale with CPU usage. Pre-requisites: The Kubernetes metrics server must be running in your Kubernetes environment for scaling of TNC-O to work. Configure TNC-O Existing installations of TNC-O can be scaled by adding an Horizontal Pod Autoscaler via kubectl. For each service that you want to scale do the following: Ensure that the service has resources set, you can do this by running: kubectl describe deployment <service name> If the deployment has resources set then you will see the following: »