CI/CD Hub The CI/CD Hub is a reference deployment of a best practice suite of Continuous Integration and Continuous Delivery (CI/CD) tools. These collectively providing an infrastructure for Assembly and Resource package and descriptor development, release and distribution management. It leverages common, open source, third party tools augmenting Telco Network Cloud Orchestration (TNC-O) specific tools to enable an integration with one or more TNC-O instances as part of a holistic CI/CD environment. »

Introduction This section introduces the deployment architecture and main configuration options for Telco Network Cloud Orchestration (TNC-O) for a typical CI/CD configuration. It is expected that multiple ALMs will be deployed to automate the various tasks for each stage of the CI/CD process. Each set of LMs are coordinated around a repository of artifacts representing the external resources under management. The picture below shows a typical deployment. See here for more information on a typical TNC-O CI/CD process. »

Telco Network Cloud Orchestration (TNC-O) uses a number of terms which have very specific meaning in its context. In some cases these terms are used in other products or industries to mean slightly different things. It is important that the user understand these terms in the context of TNC-O Assembly Assembly is a definition of a service and may comprise of one or more resources and/or other assemblies. It is defined in an Assembly Descriptor and can be instantiated as an Assembly Instance. »

ICP Pre-Install Considerations This section details topics that should be considered when installing the CI/CD Hub and/or Telco Network Cloud Orchestration (TNC-O) to ICP. Helm Install the Helm client using the ICP instructions. Pod Security Policy If you are installing CI/CD Hub or Telco Network Cloud Orchestration (TNC-O) on ICP, you should do so in a namespace that is bound to a less restrictive Pod Security Policy. We recommend creating a new namespace and binding it to an existing policy called ibm-anyuid-psp. »

Overview Telco Network Cloud Orchestration (TNC-O) software application is deployed as separated distinct component sets which can be considered in two groups; Core TNC-O consisting of a number of microservices Dependencies: Foundation functionality consisting of industry standard third party implementations Message Bus Data Persistence Authentication Server TNC-O Core Microservices The TNC-O microservices are namely: User Interface Host for TNC-O User Interface. API Gateway A gateway for the full set of published TNC-O APIs used by the TNC-O User Interface and available for use by any number of configured Client applications. »

Component State Model Assemblies and resources have a predefined state model (comparable to TOSCA) as defined in the diagram below. Components flow through this state model by performing lifecycle transitions. Resources can define which transitions they support (in their descriptors) but an assembly will always transition through In addition to the five transitions shown below, resources can implement the Integrity transition, representing a functional “smoke test” which is performed prior to the resource becoming Active and after the Start Lifecycle Transition »

LMCTL is a command-line client for the Telco Network Cloud Orchestration (TNC-O) that provides commands for interacting with TNC-O environments. It includes an opinionated pattern for managing service designs during the CI/CD lifecycle as projects, to produce packages suitable for release into production. Please use version 2.5.0 of the LMCTL documentation with 2.2.0 of TNC-O. lmctl - TNC-O version compatibility: TNC-O Version lmctl Version 2. »

Sizing guideline for ICP This guideline is for hardware requirements of installing Lifecycle Manager on top of IBM Cloud Private Then, download the Telco Network Cloud Orchestration (TNC-O) sizing guideline from the attachment of this page. You will need Microsoft Excel to open this file. Put your ICP cluster hardware details, and the desired number of resources you plan for TNC-O (assuming standard daily lifecycle actions). Make sure there’s enough hardware resources for your case. »