Versions Compared

Old Version 11

changes.mady.by.user Randa Maher

Saved on

compared with

New Version 12

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 Platform Maturity requirements to the extent possible to comply with minimum requirements requested for BeijinglBeijing.
  • 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 SDNC 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
  • Contribute CDT Tool - an APP-C Design Tool enabling VNF owners to create templates and other artifacts used by APP-C Configure actions (used to apply a post-instantiation configuration) as well as other life cycle commands.
  • Documentation updates for Beijing

...

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

The Change Management use case is workig working 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 use case at this point.

Discussions are still taking place around the manual Scaling use case; however, no definitive outcome at this stage due to lack of resources.

Minimum Viable Product

Describe the MVP for this release.

...

The long term road map is to achieve all the goals outlined in the approved project proposal; to be fully model and standards driven, be agnostics and make no assumptions about the network. Support configuration and lifecyle management of VNF/VNFC in a generic fashion so that on-boarding any new VNF/VNFC is just a matter of configuration and data. Additional long term goal is to align to the controller architecture Longer term items include:

  • Automated scaling
  • Support beyond Openstack and move to an adaptor type architecture so that multiple types of clouds can be supported with little effort
  • Align to the controller architecture proposed as part of ONAP by the architecture team.

...

Release Deliverables

Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.

Deliverable NameDeliverable Description Deliverable Location
"App-c Image" Docker ContainerExecutable Docker images available on nexus3
Java Source CodeThe Java code for the main App-c components. appc Git repository
Deployment ScriptsLinux shell scripts and Maven pom files used to generate the Docker containers. appc/deployment Git repository
Directed Graph Xml Files (DGs)Xml files define the directed graphs which are installed to database during startup and are used to determine actions taken by app-c appc/deployment Git repository
Yang Model Files Yang files are used to define the... appc Git repository
Property Files Property files are used to define values that may need to be changed depending on the environment app-c is run in. appc Git repository

Sub-Components

CDT toolan APP-C Design Tool enabling VNF owners to create templates and other artifacts used by APP-C Configure actions (used to apply a post-instantiation configuration) as well as other life cycle commandsappc/cdt Git repository (NEW)


Sub-Components

List all sub-components part of this release.
Activities related to sub-components must List all sub-components part of this release.
Activities related to sub-components must be in sync with the overall 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 depend on.

APPC interacts and has dependencies depends on the the following components as part of the general ONAP architectarchitecture:

  • 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 APPC currently must align on ODL version. 
  • AAF - AAF is used for authentication of APIsAAF is used for authentication of APIs
  • MultiVIM - APPC can access Openstack via MultiVIM or CPD-PAL. MultiVIM is optional for APPC at this stage.

For the Beijing release, APPC has dependencies on the following two projects to deliver updated componentsthree projects for specific deliverables:

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

...

Anyone reading this section should have a good understanding of all the interacting modules.

For details on the APPC architecture, refer to the APPC User Guide.

Image Added

Platform Maturity

Refering to CII Badging Security Program and Platform Maturity Requirements, fill out the table below by indicating the actual level , the targeted level for the current release and the evidences on how you plan to achieve the targeted level.

AreaActual LevelTargeted Level for current ReleaseHow, EvidencesComments
Performance0TBD0Awaiting guidance from Benchmark subcommittee
  • 0 -- none
  • 1 – baseline performance criteria identified and measured
  • 2 & 3 – performance improvement plans created & implemented
Stability0

1

APPC will do a 72 hr soak test

We assume integration team will do a 72 hour soak test at the platform 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

1

Clarification was provided by Jason Hunt that Level 1 is  manual failure detection and recovery within a single site.

APPC leverages CCSDK/SDNC distributions of OpenDaylight and DB. We will work closely with CCSDK/SDNC team to leverage what they are doing and not duplicate effort.

CCSDK indicates Level 2 support, so Level 2 will be a stretch goal for APPC at this stage until we have a better understanding of dependency.

  • 0 – none
  • 1 – manual failure and recovery (< 30 minutes)
  • 2 – automated detection and recovery (single site)
  • 3 – automated detection and recovery (geo redundancy)
Security01We will target 50% Sonar coverage for Beijing and  completing complete the Passing badge Survey.
  • 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

APPC uses ODL distribution from CCSDK project.

Scaling is a function of ODL capabilities - adding nodes to an existing cluster or adding a new cluster. capabilities - APPC can be scaled either by adding additional OpenDaylight containers and/or database containers, or by deploying multiple instances of APPC cluster.

  • 0 – no ability to scale
  • 1 – single site horizontal scaling
  • 2 – geographic scaling
  • 3 – scaling across multiple ONAP instances
Manageability11APPC supports/integrates EELF.
  • 1 – single logging system across components; instantiation in < 1 hour
  • 2 – ability to upgrade a single component; tracing across components; externalized configuration management
Usability11Documentation is already available on readthedocs. It will be updated for Beijing as needed.
  • 1 – user guide; deployment documentation; API documentation
  • 2 – UI consistency; usability testing; tutorial documentation

...

Prior to the delivery date, it is a good practice to organize an API review with the API consumers.

API NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI Definition link (i.e.swagger)
SDCREST APICurrently Available, but needs to be updated to use onap.orgTBDLink toward the detailed API description
AAIREST APICurrently AvailableCurrently Available
CCSDKOpenDayLight, SLI
, and AAI Client
, and AAI Client
TBD
SDNCMariaDB docker
TBD
DMaaPAPI  to publish/subscribe to  events sent for VNF/VM action requests.Currently AvailableCurrently AvailableDMaaP API
AAFApplication Authorization FrameworkTBDTBD


  • API Outgoing Dependencies

...

NameDescriptionVersion
ODLOpenDaylight controller platform?Nitrogen
Docker Docker container host1.12
MariaDB MariaDB-server Docker container data base container (provided by SDNC) TBD ?

In case there are specific dependencies  (Centos 7 vs Ubuntu 16. Etc.) list them as well.

...

Risk identifiedMitigation PlanContingency Plan

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

Accept riskNone
AAF scoping delivery of AAF-91 into Beijingin time to allow APPC to complete and test their work
Turn AAF off




  • Resources

Fill out the Resources Committed to the Release centralized page.

...