Configuring Access to Telco Network Cloud Orchestration (TNC-O) The installation of TNC-O includes an Ingress Controller which exposes the key services externally. This needs to be configured so that access to these services will be on the required hostnames and ports. If your environment already has an Ingress Controller available, then disable the one that comes with the TNC-O installation. You can check the status of your ingress controller with: »

Configuring Sizing of Telco Network Cloud Orchestration (TNC-O) The default install of TNC-O makes use of the default settings, which will deploy the Standard flavour of TNC-O. This includes: single instance of Foundation services execution of the TNC-O configurator job to configure default settings single instance of TNC-O services, with all security features enabled Alternative Sizing Flavours The flavours directory included in the lm-helm-charts package contains helm values and other useful files for installing alternative recommended deployments of the TNC-O. »

Configuring Security in Lifecycle Manager The recommended installation of Lifecycle Manager is with security enabled. This will give the following benefits: HTTPS access to services Role-based Access Control to the Lifecycle Manager user interface Protected access to TNC-O APIs Disabling Security The easiest way to disable security during installation is by including the No Security flavour No Security Flavour Directory: no-security This flavour disables TNC-O security and is intended for development/testing purposes. »

Storage Class By default, any service requiring persistence is configured to use the default provisioner of your Kubernetes cluster. You can check your default with kubectl: kubectl get storageclass The default storage class will be shown with (default) alongside it’s name. If you have no default, you can mark an existing class as the default with: kubectl patch storageclass <your-class-name> -p '{"metadata": {"annotations":{"storageclass.kubernetes.io/is-default-class":"true"}}}' Alternatively, you may explicitly set the storage class for each service by adding storageClass fields into your custom values file. »

Telco Network Cloud Orchestration (TNC-O) makes use of LDAP as its user store for secure access. It is configured by default to connect to the OpenLDAP service which is part of installation. Is is possible to disable this installation of this OpenLDAP service, and to connect to an external LDAP implementation. This includes support for Active Directory. Configuring an External LDAP Server To use an LDAP Server other than the pre-configured OpenLDAP instance which comes as part of the TNC-O installation, follow these steps. »

The following guide explains how to prepare 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 TNC-O services can be setup to scale from the point they are installed by setting some custom helm values. Each service has configurable options for resources and autoscaling thresholds. Before running a helm install of TNC-O you can create a custom values file with content like the following for each service: »

Direct links to a logging dashboard can be enabled in the Telco Network Cloud Orchestration (TNC-O) User Interface. This is an optional feature that will generate a link to a relevant search in a logging dashboard based on any error that has occurred in an assembly instance. The link displays like this: Enabling the dashboard links during TNC-O installation Create a values YAML file the following content in order to enable the logging dashboard: configurator: loggingDashboard: enabled: true ## The domain used to connect to the logging dashboard UI endpoint: http://kibana. »