Training videos

The ODA Canvas training series explains the Canvas and how to build ODA Components that run on it. Each video has chapters, a full transcript, and links to the documentation it covers. The videos are on the Inside Telco Architecture YouTube channel, with captions.

Part 1 · 14:53Introduction to the ODA CanvasThe ODA Canvas is the execution platform for TM Forum Open Digital Architecture (ODA) Components, with an open-source reference implementation. This first video in the ODA Canvas training series explains why the Canvas exists, from TM Forum's frameworks and Open APIs to the ODA Component and Canvas standards.Part 2 · 9:30How do I buy or build an ODA Canvas?There is no separate standard for the ODA Canvas itself. The standard is the ODA Component specification: a Canvas is any platform that reads a component's specification and meets its requirements. This second video in the ODA Canvas training series explains the three ways to get one: public cloud offerings, rolling your own from the open-source reference implementation, or assembling vendor and open-source operators, and mixing and matching all three.Part 3 · 8:45Authentication and Authorization in the ODA CanvasAn ODA Component doesn't implement identity management. It declares the roles it supports, and the ODA Canvas configures them in one shared identity platform, such as Keycloak, Microsoft Entra ID or another identity platform. This third video in the ODA Canvas training series explains how that works.Part 4 · 13:53The AI-Native ODA CanvasAI agents are fast becoming the way service providers deliver intelligent, autonomous services, but wiring each agent directly to its favourite model provider brings lock-in, hidden costs and inconsistent guardrails at enterprise scale. This fourth video in the ODA Canvas training series explains the AI-Native ODA Canvas: agents packaged as ODA Components that declare the tools and models they need, with governed access granted by the Canvas.Part 5 · 9:44Observability in the ODA CanvasTraditionally, every application arrives with its own monitoring agents and dashboards, and operations teams spend weeks wiring each one into their tools. An ODA Component is different: it declares its metrics API in its specification, and the ODA Canvas configures the observability platform for it automatically, using open standards (OpenMetrics for metrics, OpenTelemetry for traces), so any compliant platform can be used. This fifth video in the ODA Canvas training series explains how.Part 7 · 11:27The ODA Agent Skills MarketplaceAI software engineering agents are only as good as the context they are given and the process they follow. TM Forum's Open Digital Architecture already holds that context in its Open APIs, ODA Component specifications and use cases. The ODA Agent Skills Marketplace packages it as an agent-friendly knowledge base, with Agent Skills that use it across the whole software delivery lifecycle, from requirements to operations.

More parts are in production, including carbon-aware software. They will appear here when they are published.