Casablanca (R3) Doc Work Plan

This page lists all documentation-related projects that have been proposed as part of the Beijing release

Initiative

Description

Status / Meeting Notes

Priority

Project Lead(s)

JIRA Issue(s)

Initiative

Description

Status / Meeting Notes

Priority

Project Lead(s)

JIRA Issue(s)

Casablanca Project-level Updates

Creating or updating project-level documentation for Release 3

  

Phasing / Prioritization - what's ready now

  • New content for Casablanca

  • Review recent content additions / JIRA doc board for any updates

Required

All Projects

 

DOC-197: Work related to creating or updating documentation for Release 2 Closed

 

 

 

 

 

 

 

 

 

 

 

Interfaces

API - Structure & Tool Chain

  • Use of Swagger spec
    Define best way to represent/visualize - RsT may not be best?

  • Containers

  • Kubernetes

 

ONAP API Recommendations-draft 6 April-2018.pptm

High

@Andy Mayer

@Former user (Deleted)

@Dana Bobko

@René ROBERT

DOC-227: API - Structure & Tool ChainClosed

API - Differentiation

  • REST APIs

  • HealthCheck APIs

  • Components APIs (eg Java class API)

 

High

@René ROBERT

@Eric Debeau

DOC-200: Differentiate API Documentation Closed

OpenStack Interfaces

Strategic view of where and why OpenStack API's are used in ONAP, interface definitions and expectations; AA&I, DCAE (gathering information from the platform), Multi-VIM, APP-C, and SDN-C (asking the platform to do things/put itself in a certain state).

On hold - Dave Neary moved to new role

Multi-VIM owner going foward?

Medium

Multi-VIM @lixinh

OOM @David S

DOC-202: Create a document: HOWTO: Deploy an ONAP SDNC Instance on OpenstackClosedDOC-211: Add details to openstack installation in docClosed

 

 

 

 

 

 

 

 

 

ONAP for Newcomers

 

"Welcome to ONAP" Flows and Text

Convert existing component level diagrams to high level flows and text. Include high level Architecture, as well as as typical use cases such as:  VNF Onboarding, Fault management, and Capacity management.

 

One example is Istio's Concepts page: https://istio.io/docs/concepts/

 

Onboarding Documentation needed (Pawel):

  1. Types of licenses: universal, unique and one time

  2. License term: fixed term, perpetual, unlimited

  3. Onboarding procedure: manual or network package

  4. How to delete objects created (i.e. VSP)?

Populate remaining generic flows (Gil)

Architecture sub-team including E2E views? (Chris D)

High

@Paweł Pawlak 

@Gil Bullard

@Rich Bennett

@RAMANJANEYUL AKULA

DOC-224: Welcome to ONAP Flows & TextClosed

ONAP "Light" for SEs, Architects

ONAP "Light" version (non-coding) targeted for SEs, architects on how to use the platform

  1. Install ONAP on their local cloud environment

  2. Run Health Check

  3. Run three Use cases:  vFW, vDNS, vCPE

Documentation - Put each step into context, both what and why 

High

@Eric Debeau

DOC-225: ONAP "Light" for new SEs and ArchitectsClosed

Wiki "Sandbox"

"Sandbox" for developers to actually interact with the code

  • Install on laptops, pre-configured environment

  • Allow for coding, build and compile

  • Default IDEs

  • Does not impact live Master Branch

  • Available for hackathon


Documentation;  Need tutorial materials (videos, text, flows?)

Victor:  Technically possible to point the vagrant-onap tool to an existing OpenStack Deployment [1].  Vagrant-onap tool has helped us to collect some disperse bash instructions in a single place. No feedback yet from PTLs or developers about the missing pieces except for SDC. This tool has been suffered many changes lately and I haven’t been able to test all of them so maybe it’s just matter to do few adjustments.

  • Need OpenStack deployment (Windriver?)

  • Functionality limited to single component(s)

  • Users download from Integration folder

 

[1] http://onap.readthedocs.io/en/latest/submodules/integration.git/bootstrap/vagrant-onap/doc/source/features/openstack.html

High

@Victor Morales (lead)

@Helen Chen (support)

DOC-226: ONAP "Sandbox" for new DevelopersClosed

 

 

 

 

VNF Reference list

Documentation and ongoing repository for integration tested VNFs (i.e. certified by ONAP for third party providers)

  • Integration Team provides list of reference VNFs

  • Need to establish template 


Future:  Establish VNF "App Store" (VNF SDK project drives ?)

 

 

 

 

List of tested VNFs through Casablanca

Coordinate population of VNF templates (Helen)

Higher

Integration @Helen Chen

DOC-232: List of Beijing VNFsClosed

How / where to publish

Publish in RTD under "Use Cases"

Higher

LF @Lisa Caywood ?

DOC-233: VNF PublishingClosed

 

 

 

 

 

Migrate Seed Documentation from Wiki





Migration Process / Issues

 

 

@Anuj Kapoor

DOC-179: Migrate Release Controlled Wiki ContentClosed

Setting Up ONAP

Complete OOM documentation

Remove HEAT documentation?

Higher

@Eric Debeau ?

 

Integrating with ONAP

 

Higher

 

 

Using ONAP

Migrate remaining wiki documentation

Higher

SDC, Policy, CLAMP, VID

@gg2147@att.com

 

Architecture

 

Higher

Architecture / All Projects

 

Documenting ONAP

 

Higher

@gg2147@att.com

 

Developing ONAP

 

Higher

All Projects

 

Glossary

 

Low

Modeling, Architecture

 

 

 

 

ONAP Health & Maturity

 

Daily / Frequent Health Tests

  1. Daily health test results deployed by OOM and Heat

  2. Daily test results for vFW / vLB / vCPE

  3. Nexus tags for above two tests results: repo and docker images (for people to easily get a stable ONAP code in their local env.)

Medium

Integration @Helen Chen

@Sastry Isukapalli

 

Maturity

  1. Granularity

  • E2E

  • Project level

    2. Maturity requirement: performance, resilience, etc.  
    3. Different tools: JProfile, Chaos Monkey, etc.

Medium

Integration @Helen Chen

 

URL

testresults.onap.org      

Medium

LF

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Doc Tool Chain / Utilities

Automation/Verification

  • Doc8+/- Coala Code Policies

  • Spelling

  • Grammar

  • Editorial / Usability

  • Sphinx directives

  • Integrity of Glossary/Info Model

  • Integrity of sphinx toctree

  • Integrity of external references

  • Acceptable file types

  • CI/CD repo integration

Dev Edit RST File - Unit Test - Gerrit - Code Review/Verify Job - Gerrit Human Review - Daily CSIT - Release Integration Test

 

Higher

@Rich Bennett

LF @Amar Kapadia ?

DOC-234: Automation / VerificationClosed

RTD Feedback

  • JIRA project to report an error

  • Wiki or stack overflow Q&A

  • Simple, more accessible link tool for editing RTD pages

 

Medium

@Rich Bennett ?

LF @Amar Kapadia ?

DOC-228: RTD FeedbackClosed

Wiki Feedback
Establish new structure and process for:

  •     Discussion forum

  •     Submitting suggestions / feedback with existing content

 

Medium

@Rich Bennett ?

LF @Amar Kapadia ?

@Lisa Caywood ?

DOC-230: Wiki FeedbackClosed

LF Tool Chain Documentation

  •     Gerrit guide

  •     Guidelines (Builds, etc.)

  •     Utilities:  Jenkins, Conversion tools (e.g. LF Pandocs)

 

Lower

LF @Thanh Ha

DOC-229: LF Tool Chain DocumentationClosed

 

 

 

 

 

 

PROCESS ISSUES

 

 

 

 

 

Branching Guidelines

Specify how and when to branch documentation for Casablanca

 

 

@Gildas Lanilis Gmail

 

https://lf-onap.atlassian.net/browse/DOC-235

VNF Certification

How and when to document:

1. Certified VNFs (when that happens)

2. Certified Platform elements

 

 

VVP

https://lf-onap.atlassian.net/browse/DOC-236

Videos

Managing and tracking what and where videos are being posted

 

 

@Lisa Caywood

@gg2147@att.com

https://lf-onap.atlassian.net/browse/DOC-237

Wiki vs Readthedocs

How to best communicate guidelines on what content should be where

 

@Thanh Ha

@gg2147@att.com

https://lf-onap.atlassian.net/browse/DOC-238