Versions Compared

Old Version 6

changes.mady.by.user Randa Maher

Saved on

compared with

New Version 7

changes.mady.by.user Randa Maher

Saved on

Key

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

...

  • Remove references and use of openecomp and replace  with onap 
  • Address S3P requirements to the extent possible to comply with minimum requirements requested for Beijing for areas not already at this level.
    • Notes:  
      • Compliancy for Performance Level 1 is still being investigated
      • Compliancy for Stability is assumed to be addressed by Integration team system level testing
      • Resiliency -
        • Local HA: this is a function of ODL clustering capability, so whatever is supported by ODL Nitrogen defines local HA capabilities
        • Geo-red: manual site failover only will be supported in Beijing 
  • Support AAF (Authentication and Authorization Framework) for API access
    • Dependency on AAF project to provide feature (AAF-91) to enable AAF security on the web server level (jetty level).
  • Upgrade ODL version to Nitrogen (driven by CCSDK dependency)
  • Replace MySQL with MariaDB (driven by CCSDK dependency)
  • Increase Code Coverage to 50%
  • Provide support for the following new LCM actions:
    • Following Actions in support of In-place software upgrade
      • QuiesceTraffic
      • ResumeTraffic
      • UpgradeSoftware
      • UpgradePreCheck
      • UpgradePostCheck
      • UpgradeBackup
      • UpgradeBackout
    • Additional LCM actions including:
      • ActionCancel
      • ActionStatus
      • AttachVolume
      • DetachVolume
  • CDT Tool
  • Documentation updates for Beijing

...

The use cases supported in Amsterdam release will continue to be supported as part of regression assuming all other components do likewise.

At this writing, APPC will not be contributing to any new use cases in Beijing.

The Change Management use case is working workig with SDNC for an L3 device firmware upgrade .(however, note that APPC will be adding capability to do an in-place software upgrade for a VNF)

There is no impact for APPC as part of HPA There is no impact for APPC as part of HPA use case at this point.

Discussions are still taking place around the Scaling use case; however, no definite definitive outcome yetat this stage.

Minimum Viable Product

Describe the MVP for this release.

...

Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.

ONAP Dependencies

<TO DO: Separate standard dependencies as part of ONAP architecture vs. what are the "new" functions/changes needed in support of Beijing>

List the other ONAP projects you depends depend on.

  • SDC: Rest based interface exposed by SDC. APPC receives notifications from SDC on VNF information. SDC team provides an SDC Listener, which is used by APPC.
  • AAI: APPC retrieves and updates VNF data from/to AAI.
  • DMaaP: Message bus for communication with other components in the solution (SDC, DCAE, MSO, Portal, OOM)
  • CCSDK - APPC currently gets ODL & DB package from CCSDK; CCSDK and AAPC currently must align on ODL version. 
  • AAF - AAF is used for authentication of APIsAPIs

Beijing release have dependencies on the following two projects to deliver updated components:

  • CCSDK/SDNC - Nitrogen ODL and MariaDB dockers
  • AAF - feature AAF-91 - needed to address API level security

Architecture

High level architecture diagram

...

AreaActual LevelTargeted Level for current ReleaseHow, EvidencesComments
Performance0TBD
  • 0 -- none
  • 1 – baseline performance criteria identified and measured
  • 2 & 3 – performance improvement plans created & implemented
Stability02 (assumption is that 72 hour soak test will be done by Integration team testing); not separate testing will be done at component level
  • 0 – none
  • 1 – 72 hours component level soak w/random transactions
  • 2 – 72 hours platform level soak w/random transactions
  • 3 – 6 months track record of reduced defect rate
Resiliency1

Local HA is a function provided as part of ODL clustering capabilities

For Geo-Red, we will support manual failoverfail-over


  • 0 – none
  • 1 – manual failure and recovery (< 30 minutes)
  • 2 – automated detection and recovery (single site)
  • 3 – automated detection and recovery (geo redundancy)
Security01
  • 0 – none
  • 1 – CII Passing badge + 50% Test Coverage
  • 2 – CII Silver badge; internal communication encrypted; role-based access control and authorization for all calls
  • 3 – CII Gold
Scalability11 - function of what ODL provides to add nodes, just needs to be an odd number of nodes and a manual process to update a config file (akka.com file) and restart nodes
  • 0 – no ability to scale
  • 1 – single site horizontal scaling
  • 2 – geographic scaling
  • 3 – scaling across multiple ONAP instances
Manageability11
  • 1 – single logging system across components; instantiation in < 1 hour
  • 2 – ability to upgrade a single component; tracing across components; externalized configuration management
Usability11
  • 1 – user guide; deployment documentation; API documentation
  • 2 – UI consistency; usability testing; tutorial documentation

...

Risk identifiedMitigation PlanContingency Plan

ODL upgrade to Nitrogen & DB to MariaDB - depends on CCSDK/SDNC to provide dockers

Accept riskNone
AAF scoping AAF-91 into Beijing


  • Resources

Fill out the Resources Committed to the Release centralized page.

...