Operator based Cloud Automation

OCA is operator based unified life cycle automation platform for cloud-native telco services.

Problem Statement

Currently, telecom automation is often fragmented. Either there is little automation and significant manual effort, or automation is tightly coupled to a specific service, making it difficult to scale and maintain. OCA addresses these challanges through unified, reusable operator-based approach.

Project Details

Leader : Deutsche Telekom (Patrick Derckx, Maulik Thaker)

List of people/organization interested to join:

  • Orange (E.Moniz, M.Richomme)
  • X

Constraints : * Lab connectivity : Secure a cluster to collaborate (e.g. gcp) * OCA operators are not open sourced but can be packaged and used

OCA Building Blocks

OCA Service Operator

The network Service LCM Operator is the primary orchestration component of OCAS Suite, managing the complete lifecycle of Network Services - compositions of CNFs that collectively deliver telecommunications services. It addresses the challenge of manually managing multiple CNF deployments with complex dependencies, versions, and sequencing requirements. It has built in plugin which allows easy integration to vendor operators without requiring additional development on their side.

CNF LCM Operator

The CNF Operator specializes in deploying and managing CNFs (Containerized Network Functions) using Helm charts. It manages depedencies within CNFs (with more than one helmcharts) using dependency graph and graph travercing algorithm. Even if we suggest the principle "separation of concerns" where the vendor is in charge of building software automation, this operator is the perfect fit, if your vendor does not deliver an own operator.

Inventory Operator

It eliminates the operational burden of maintaining accurate asset inventories by providing automated synchronization between OCA Suite deployments and Inventory Management Systems. The operator automatically detects deployment activities and translates them into appropriate inventory records in the form of Kubernetes manifeststhat are being reconciled by an inventory system

Hackathon Objectives

  • Test operator on different labs
  • Test inter operability with other operator
  • Have common infrastucture for collaboration