Uploaded image for project: 'Release Requirements'
  1. Release Requirements
  2. REQ-388

Interactive documentation aligned with a deployment

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: High High
    • Honolulu Release
    • None
    • None
    • Interactive documentation aligned with a deployment
    • Requirement (DEPRECATED)
    • 0
    • Not required
    • De-Scoped
    • S
    • Green
    • GO
    • Green
    • GO
    • Green
    • GO
    • Red

       Description of Use Case / Requirement:

       

      Executive Summary - ONAP documentation is static and does not provide a dynamic way to jump into all the ONAP Kubernetes components and to get all relevant information based on a real deployment

       
      A prototype has been demonstrated during the virtual F2F event in April

       

      Owners (one of these should be the Assignee - use @ notation):

      eric.debeau

      Link to HLD/LLD (if any):

      no HLD

       

      Dependency Relationships with Other Projects:

       OOM

      Project Impact (Test Only (TO), Code (C)):

      Doc only, possible code impact witth OOM

      Support Status for each Affected Project (Supported (S); Partially Supported (P); Not Supported (N)):

      Note: for any affected projects labeled 'P' or 'N', please document the resulting gaps.

       

      Integration Leads (use @ notation): 

       No integration

      Company Engagement: 

       Orange

            eric.debeau eric.debeau
            eric.debeau eric.debeau
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: