Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Improve the lifecycle management of software modules / projects.

Knowledge about: Release → Docker Container / Version → Repository / Version → Project 

Current Situation

  • A deployable ONAP release consists of 'maintained' an 'unmaintained' software modules (used to build the docker container).
  • Only 'projects' are managed in the release process
  • But a 'project' consists of 1-n repositories. Repositories are not managed in the release process.
    • If a project is (un)maintained, are all repositories (un)maintained?
  • Only 'maintained' projects are managed in the release process.
  • But "unmaintained" software modules (docker container) are added to the list of deployed software modules in the end of the release process (oom)
  • Unmaintained, but deployed projects (not repositories!) of the 'Istanbul' release are:
    • Application Authorization Framework AAF
    • Application Controller APPC
    • External API
    • External System Register ESR
    • Logging
    • MUSIC
    • Portal
    • Virtual Infrastructure Deployment VID
  • The management of 'release participation' is limited (projects, not repositories), distributed (relmgr, oom, sec, doc) and is not done in a collaborative, end-to-end manner
  • Information about the lifecycle state of projects and repositories and their release participation is distributed, manually maintained and not in sync (GIT:active|readonly, INFO.YAML, WIKI:release participation, WIKI:project lifecycle state, WIKI:documentation, ...)

...