Manageability (New)

Level Definitions

(Dublin updates in red)

Level 1:
- All ONAP components will use a single logging system.
- Instantiation of a simple ONAP system should be accomplished in <1 hour with a minimal footprint
Level 2:
- A component can be independently upgraded (for bug fixes only) without impacting the operation of interacting components
- Component configuration to be externalized in a common fashion across ONAP projects
- All application logging to adhere to ONAP Application Logging Specification v1.2
- Implement guidelines for a minimal container footprint
Level 3
- Transaction tracing across components

All Projects: Level 2
- New projects should adhere to v1.2
- Existing projects have stretch goal for v1.2
Stretch Goal: Level 3
Note: some work will be done in Dublin to test/prep for a release upgrade strategy. This will include common upgrade support capability (ex: Cassandra upgrade) as well as guidelines/requirements for projects to be able to do in-place major/minor upgrades.

Please refer to the Logging Enhancements Project documentation for guidance on implementing logging, including the Logging Developer Guide.
- For transaction tracing, the Logging Spec v1.2 supports MDCs and Markers. In the future, a service mesh could support this.
- Portal will do the example for other projects.
Independent bug fix upgrades can be accomplished with OOM and helm charts (helm upgrade).
Configuration can be externalized into Helm charts via the OOM project. See OOM Configuration Management.
See this presentation and follow the Container Image Minimization Guidelines

CIA, OOM and Logging Enhancement teams.