1. Problem Statement
Do we need to add another state “Maintenance” as part Project Component Lifecycle (Maintenance)?
What is the difference from the Archived state?
2. Definition
ONAP Core Component (MVP-Minimum Vital Product): An ONAP component is identified as ONAP Core Component if this component is impacting the ONAP deployment and/or Onboarding, Instantiation, Run-Time, etc. and can not be replaced by another non-ONAP systems, components.
Maintenance: Project(s) or sub-project(s) is no more part of any official release, but some parts might still be consumed indirectly by other project teams or some functionalities are still needed but no alternative has been implemented yet.
These Project(s) or sub-project(s) are no more subject to non-functional compliances. The level of support will be dependent on the ONAP Community willingness to contribute, fast response time is not guaranteed.
Transition from Maintenance to Incubation/Mature: A maintenance project can be moved to “Incubation” or “Mature if there is a new interest from the ONAP Community including PTL responsibility and committers engagement, reviewed and approved by the ONAP TSC. The project will be still part of OOM deployment and High Priority bugs might be fixed to unblock the current and/or maintained releases
Transition from Maintenance to Archived: A maintenance project can be moved to “Archived" if the project is no more critical for the ONAP Platform (Deployment, Onboarding, Instanstiation, Run-Time) or has any dependecy to any ONAP component.
Transition from “Incubation/Mature/Core” to Maintenance
ONAP SECCOM requirement for all projects in “Maintenance”:
- Any critical, severe or high vulnerability found in the code written by the project team MUST be fixed within 60 days or prior to the inclusion of the project in a new release, whichever occurs first.
Archived:
Project can reach Archived state for multiple reasons. Either project has successfully been completed and its artifacts provide business values, or project has been cancelled for unforeseen reasons (no value anymore, technical, etc.). Project in any state can be Archived through a Termination Review. |
3. Projects currently under Maintenance:
- AAF, APPC, AAI/ESR, MUSIC, Logging incl. Pomba
- Currently Archived: DCAE-D SDC plugin, AAI/Sparky, OOF/FGPS, DCAE/PNDA and
- sdc/dcae-d/ci
- sdc/dcae-d/dt
- sdc/dcae-d/dt-be-main
- sdc/dcae-d/dt-be-property
- sdc/dcae-d/fe
- sdc/dcae-d/rule-engine
- sdc/dcae-d/tosca-lab
<Add gerrit query to identify all the repositories that have been archived - Read only access>
4. What are the steps to move a project under 'Maintenance'
What has been done i.e. Logging incl. Pomba
#1 Final call to the ONAP Community
#2 Review what is used by the Community and the dependencies to other components
Maintain the repositories that are necessary for the ONAP Components:
https://gerrit.onap.org/r/gitweb?p=logging-analytics.git;a=tree;f=pylog;hb=HEAD
#3 Identify potential remaining committers to maintain the remaining repositories: 2 committers for Java Libraries and 1 Committer for Python library
#4 Archive the repositories that are no more in used + check if any impact on OOM/Integration (CIST)/DOC projects
#5 Update the ”Resources and Repositories” wiki page - https://wiki.onap.org/display/DW/Resources+and+Repositories#ResourcesandRepositories-LoggingEnhancements
#6 Update the Architecture diagrams and references
Next steps:
#7 Remove Jenkins jobs
#8 Inform Steven Winslow and disable all the scans (Sonar, FOSSology, NexusIQ) on the unmaintained logging repos
#9 Identify an alternative path i.e. SDTOUT ((REQ-374) for log collection
#9 Move Logging to Project State: Archived following the Termination Review process (incl. Clean-up of other wiki pages, RDT, JIRA, mailing lists, calendars, etc.)