TABLE OF CONTENTS
Short Explanation
Table: Maintained Repositories
- Containing documentation repositories for the upcoming release
- Table handled commonly by the ONAP projects and the Documentation team.
- In the column header you find the responsibility for this column (DOC|PROJECT).
Table: Non-Relevant Repositories
- Containing documentation repositories no longer relevant for the upcoming release
Maintained Repositories Table
| # | Project Name (common abbreviation of the project or subcommittee) Responsibility: | Repository Name (contains documentation to be published with the upcoming release) Responsibility: | ReadTheDocs Link (link pointing to RTD 'latest' main index.rst; main title used in index.rst) Responsibility: | Repository Status (new | changed | remove ; status of documentation; needed to e.g. identify changes in the intersphinx linking) Responsibility: | Documentation Owner(s) (responsible for documentation in this repo; please use @ notation for the name) ( see also History of PTL ) Responsibility: | Documentation available: (relevant for new repos which are participating the first time)
Responsibility: | Documentation available:
Responsibility: |
|---|---|---|---|---|---|---|---|
| M? | M? | M? | M? | M? | M? | RC0 | |
| 01 | AAI | aai/aai-common | AAI Documentation Repository | no PTL since 2022-12-02 |
|
| |
| 02 | AAI | aai/sparky-be | Sparky - Inventory UI Service | no PTL since 2022-12-02 |
|
| |
| 03 | CCSDK | ccsdk/apps | CCSDK APPS DOCUMENTATION REPOSITORY |
|
| ||
| 04 | CCSDK | ccsdk/cds | CONTROLLER DESIGN STUDIO (CDS) |
|
| ||
| 05 | CCSDK | ccsdk/distribution | Common Controller Software Development Kit |
|
| ||
| 06 | CCSDK | ccsdk/features | SDN-R Online help |
|
| ||
| 07 | CCSDK | ccsdk/oran | ccsdk/oran |
|
| ||
| 08 | CLI | cli | ONAP CLI |
|
| ||
| 09 | CPS | cps | CPS Documentation |
|
| ||
| 10 | CPS | cps/cps-temporal | CPS Temporal | According to Toine Siebelink the project is no longer maintained. To be removed? |
|
| |
| 11 | CPS | cps/ncmp-dmi-plugin | DMI-Plugin Documentation |
|
| ||
| 12 | DCAE | dcaegen2 | Data Collection Analytics and Events (DCAE) | no PTL since 2022-12-01 |
|
| |
| 13 | DMAAP | dmaap/buscontroller | dmaap/buscontroller |
|
| ||
| 14 | DMAAP | dmaap/datarouter | DMaaP Data Router |
|
| ||
| 15 | DMAAP | dmaap/messagerouter/messageservice | dmaap/message router(MR) |
|
| ||
| 16 | DOC ArchSubCom | doc | Open Network Automation Platform |
|
| ||
| 17 | HOLMES | holmes/engine-management | Holmes |
|
| ||
| 18 | HOLMES | holmes/rule-management | Holmes |
|
| ||
| 19 | INTEGRATION | integration | INTEGRATION | no PTL since 2022-06-30 |
|
| |
| 20 | MODELING | modeling/etsicatalog | Etsicatalog Project |
|
| ||
| 21 | MODELING | modeling/modelspec | Model Specifications |
| |||
| 22 | MSB | msb/apigateway | MSB(Microservices Bus) |
|
| ||
| 23 | MSB | msb/swagger-sdk | Swagger SDK |
|
| ||
| 24 | MULTICLOUD | multicloud/framework | MultiCloud Architecture | no PTL since 2023-04-24 |
|
| |
| 25 | MULTICLOUD | multicloud/k8s | MultiCloud Kubernetes Plugin | no PTL since 2023-04-24 |
|
| |
| 26 | OOM | oom | OOM Documentation Repository | no PTL since 2022-04-01 |
|
| |
| 27 | OOF | optf/has | Optimization Framework: Homing and Allocation | no PTL since 2022-10-07 |
|
| |
| 28 | OOF | optf/osdf | Optimization Framework: Optimization Service Design Framework (OSDF) | no PTL since 2022-10-07 |
|
| |
| 29 | POLICY | policy/parent | Policy Framework Architecture |
|
| ||
| 30 | Portal-NG | portal-ng | Portal-NG | Georg Schweflinghaus |
|
| |
| 31 | SECCom | osa | ONAP Security |
|
| ||
| 32 | SDC | sdc | SDC Documentation | stepping down as PTL after Montreal release |
|
| |
| 33 | SDNC | sdnc/oam | Network Controller (SDNC) |
|
| ||
| 34 | SO | so | ONAP SO |
|
| ||
| 35 | UUI | usecase-ui | Usecase-UI(Use Case User Interface) |
|
| ||
| 36 | VFC | vfc/nfvo/lcm | VF-C(Virtual Function Controller) | no PTL since 22-12-05 |
|
| |
| 37 | VNFSDK | vnfsdk/model | VNFSDK Documentation |
|
|
Non-Relevant Repositories Table
| # | Project Name (common abbreviation of the project or subcommittee) Responsibility: | Repository Name (contains documentation to be published with the upcoming release) Responsibility: | ReadTheDocs Link (link pointing to RTD 'latest' main index.rst; main title used in index.rst) Responsibility: | Repository Status (new | changed | remove ; status of documentation; needed to e.g. identify changes in the intersphinx linking) Responsibility: | Documentation Owner(s) (responsible for documentation in this repo; please use @ notation for the name) Responsibility: | Documentation available: (relevant for new repos which are participating the first time)
Responsibility: | Documentation available:
Responsibility: |
|---|---|---|---|---|---|---|---|
| M2 | M2 | M2 | M2 | M2 | M4 | RC0 | |
| 00 | |||||||
| 00 | |||||||
| 00 |
Notes for "Maintained Repositories"
In the table "Maintained Repositories" please check/update:
Project Name: Use the common abbreviation of the project or subcommittee.
Repository Name: Containing documentation to be published with the release (one per line)
ReadTheDocs Link: Link pointing to RTD 'latest' main index.rst. Main title used in index.rst.
Repository Status: Please note if the repository is new, has changed or must be removed. For new documents, at a minimum create a placeholder document (e.g., document with the correct file name and a title, or an outline), and commit to the repo. This is important for the doc team to check whether i.e. the linking works or not.
Documentation Owner(s): Please name responsible persons for documentation in this repo. Please use @ notation (e.g. David McBride for the name)