Interoperability: Empowering Multi-Vendor CD in...

### Overview This presentation examines the historical challenges and ongoing solutions for multi-vendor continuous delivery (CD) interoperability, tracing its origins from telecom initiatives within Linux Foundation Networking (LFN) to current standards work within the Continuous Delivery Foundation (CDF). Speakers Fatih Degirmenci and Andrea Frittoli illustrate how the disaggregation of hardware and software (such as virtual and cloud-native network functions) led to multi-vendor software delivery friction, ultimately necessitating standardized event formats rather than bespoke point-to-point integrations.

### Key Topics - **Evolution from OPNFV and Cross-Community CI**: In projects like OPNFV (later relaunched as Anuket), integration teams combined diverse upstream platforms (OpenStack, OpenDaylight, ONAP, etc.). As the telecom industry shifted toward disaggregated VNFs and CNFs, communications service providers (CSPs) faced increasing complexity trying to manage disparate vendor pipelines, leading to initiatives like Cross-Community CI in 2017 and multi-community practitioner workshops in 2018. - **Integration vs. Interoperability**: Modern CI/CD toolchains employ distinct tools across SCM, static analysis, building, testing, deployment, and monitoring. Ad-hoc point-to-point integrations require organizations to shoulder high maintenance costs, endure data loss from incompatible data models, face scalability hurdles across departments, and suffer vendor lock-in. Interoperability addresses this through standardized APIs and consistent data models. - **CD Events Specification**: Born out of the CDF Interoperability Special Interest Group, the CDEvents project defines a common specification for continuous delivery events to enable loose coupling, unified observability, and end-to-end pipeline automation.

### Technical Details - **Event Buckets**: CDEvents organizes event types into distinct categories spanning the software delivery lifecycle: - *Pipeline Orchestration*: Triggers and signals for tasks and pipeline runs (e.g., Jenkins, Tekton). - *Software Configuration Management (SCM)*: Standardized webhooks for repository events across platforms like GitHub, GitLab, and Gerrit. - *Continuous Integration (CI)*: Build and artifact metadata, including provenance and Software Bill of Materials (SBOM) data. - *Testing*: Execution records for unit, integration, and security/vulnerability scans to enforce policy gates before deployment. - *Continuous Deployment and Continuous Operations*: Rollout and runtime operations tracking. - **Transport and Protocols**: CDEvents builds on the CNCF CloudEvents standard, enabling message transport over multiple protocols including HTTP, MQTT, Kafka, NATS, and WebSockets. - **Tooling and Community Integrations**: CDEvents provides SDKs in Go, Java, and Python (with .NET and JavaScript planned). Implementations and adoption efforts include plugins or RFCs across Jenkins, Tekton, Spinnaker, Testkube, Harbor, Argo, and Flux, alongside collaborations with OpenTelemetry, the CNCF TAG App Delivery, the Open Mainframe Project, and the Value Stream Management Consortium.

### Takeaways - Standardized event schemas provide a single "evidence store" that enables end-to-end pipeline observability, automated policy enforcement, and supply chain security auditing without tight tool coupling. - Point-to-point custom integrations or localized GitOps implementations do not fundamentally solve ecosystem-level interoperability across multiple vendors. - Telecom operators and network communities are urged to engage early with the CDEvents project (such as via the 5G Super Blueprint) while the specification is still evolving toward version 1.0, ensuring domain-specific requirements are incorporated before standards stabilize.