WG06 Meeting minutes 7/11/2024

Agenda

Zoom Replay

Supports

Minutes

Introduction on the goals of the WG06

  • Share concerns & pains related to the management of the CNF using GitOps
  • Share evaluation and feeback on components related to CNF management
  • Reference implementation

1 meeting per month

The goal is to provide guidelines, recommendations and reference implementation in order to ease, secure, deploy CNF leveraging GitOps methodology.

M.Richomme is identified as WG leader but the position is open. As some WG are already lead by Orange, it would make sense to open the position to active actors such as DT or Swisscom.

Netbox Operator

Presentation of the Netbox operator initiated by Swisscom and netbox community.

Slides / NetBox Operator Assets

The goal is to allocate dynamically IP addresses and prefixes. Work is in progress to use the operator for the CNFs The operator is a young project supported by Netbox community, which is a mature project already widely used across organizations.

Thomas Morin (WG01) indicates that it would be also interesting for Sylva Management CLuster.

Day X config management

DT shared the difficulties to manage Day X configuration changes (non cloud nativeness, size of the configuration files not compatible with configmap limits, as many ways as vendors, complex middleware, poor GitOps approach on vendor side).

Swisscom indicated that they consider using SDC(Schema Driven Configuration). A demo shall be planned for next session. It is a young project open for contributions.

Artifact management

Orange mentioned that there are too ways to retrieve the OCI artifacts. Lots of time is lost just setting up the way to retrieve the artifacts and it cannot be fully automated. A standard IT way with secured registries would be nice to have (with pull from Telco centralized registry).

Swisscom has a space where the vendors have to push their artifacts. The different CSAR are retrieved automatically daily, managed then pushed into OCI registries.

Orange and Swisscom reported issues on Vendor Helm chart (ambiguous annotations) The default Helm parser is not as strict as the standard yaml parser used by Flux