The following diagram illustrates the overall Architecture Process. It shows the basic stages of a release, going from M0 (release kickoff), to M2/M3 (API Freeze) and to code delivery in M4.Components. ONAP defined a new release process, based on the agile ONAP Streamlining evolution. It simplified ONAP release process, by having only:
- Kick Off
- Release Candidate
- Sign Off
The previous M0 (release kickoff), M2, M3 (API freeze) and M4 (code freeze) processes are merged and will be handled between Kick Off and Release Candidate in an agile manner, as the following:
- Marketing release Kick Off, RC and Sign Off dates are set by Release manager and TSC
- Each PTL determines their project agile cycle(s) based on their features
- PTLs/Feature owners work with ARCCOM/SECCOM/TSC/Release Manager/OOM/INT and DOC
- Each agile iteration/sprint is reviewed / approved by the project team (and ARCCOM/SECCOM/INT/TSC/Release Manager/TSC as needed)
- priorities, guidance, standards, security...
- The review outcome is used to determine what the next steps until RC
There are It illustrates 5 stages that the Architecture teams are concerned with, the Functional Architecture requirements, to component architecture reviews and architecture improvements.
...
FUNCTIONAL ARCHITECTURE - The functional architecture is the high-level architecture overview diagram for all of ONAP. This was the Functional Architecture diagram on May 16, 2019April 2024:
COMPONENT ARCHITECTURE - The component architecture are the platform components. Examples of platform components are SO, A&AI, CCSDK, SDN-C. Each release there may be architecture impacts from the platform components
...