Page Comparison

Agenda Topics:

SO Honolulu release.

• SO Sub-Component Module Refactoring
• Image Added
  • Seshu proposed the above SO component refactoring architecture at the ONAP Architecture sub-committee on January 12th 2021
  • The SO team discussed how to achieve this during Honolulu
  • Two steps are identified:
    • 1st steps:
      • Separate the components on needed basis from the SO Core components
      • for the components on need basis, we will have:
        • a separate project per component
        • a separate repo per component
        • a separate / independent Jenkins jobs per component
      • The Ericsson team volunteered for ETSI NFVO, SOL003 Adapter and SO Monitoring/Maintenance to achieve the 1st steps
      • Other ONAP participating companies handle other optional sub-component refactoring
      • CNFO would be a good example, according to Seshu
    • 2nd steps:
      • Once the core components and optional components are ready (i.e., successfully crated projects, repos, Jenkins, build), those components need to be integrated into SO
      • Currently, we are going to use OOM
      • Seshu is looking for its volunteers
      • The team expects Seshu to create Epic(s) for this (including the 1st steps) with high-level description / design, the participating companies will add their design into the Epics and create user stories
      • Then, the team will have a review meeting, with additional input from the OOM team
      • Then, the team will decide who is doing what for the 2nd steps

• Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key SO-3432

   (SO does not update ipv4-oam-address in AAI)
  • Konrad Bańka , could you please add more details here?

H release:

Image Added PDF

Project Status in Honolulu Release

Honolulu Impact View per Component

New:

H release M1 Criteria