...

...

• Support new LCM action Reboot and various other enhancements to existing LCM actions (Tracked under Epic: APPC-899)
• Documentation updates for Casablanca, such as, but not limited to:
  
  • LCM API Guide
  • Release Notes
• Code Coverage for CDT (Javascript) - TBD, no commitment at this stage
  
• Use Cases
  • ConfigScaleOut - Partially supported
    
    • Support Retrieval of configuration data from AAI instead of having SO pass configuration data in payload - (investigate if we can we reuse the named query)
      • Dependency on SO to pass the vf-module-id of the vDNS instance that must be added.
        
    • No commitment on Controller Type since requirements are still unclear.
      
  • Change Management - No Commitment based on support from ATT resources
  • 5G/PNF - No Commitment (although APPC is listed as an impacted component, there does not appear to be any immediate requirement for Casablanca. Items noted are longer road map items)
    

Use Cases

Describe the use case this release is targeted for (better if reference to customer use case).

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

APPC SO will contribute partially to the following use cases as part of the functional requirements.

• Scaling Use Case - 
  
  • APPC SO will support retrieving the data to be configured from AAI. This however has a dependency on SO to  pass the vf-module-id of the vDNS that was instantiated..
  • Discussions around how Controller Type will be handled are still too vague and unclear, so no commitment can be made to support this. APPC will continue to support APPC and SDNC via the Client Library as was done in Beijing.

Minimum Viable Product

...

• CCVPN Use Case
  • Support the Cross Domain Cross Llink Virtual Private Network between 2 ONAP instances.
• HPA extension for the other existing usecases
• PNF resources orchestration 
  
  

Minimum Viable Product

Same as was defined for Beijing with the adding of CDT.

...

...

...

Sub-Components

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

List the other ONAP projects you depend on.

APPC depends on the the following components as part of the general ONAP architecture:

• 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. (Currently we have no use case for this, although supported)
• 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 APIs
• MultiVIM - APPC can access Openstack via MultiVIM or CPD-PAL. MultiVIM is optional for APPC at this stage. Support of MultiVIM is limited to the Generic_Restart action

For the Casablanca release, APPC has dependencies on the following three projects for specific deliverables:

• CCSDK - - Oxygen ODL & MariaDB plus Galera
• SO - for scale out scenario to deliver the correct data to retrieve AAI information

Architecture

High level architecture diagram

At that stage within the Release, the team is expected to provide more Architecture details describing how the functional modules are interacting.

Indicate where your project fit within the ONAP Archiecture diagram.

Block and sequence diagrams showing relation within the project as well as relation with external components are expected.

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 Removed

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.

...

• 0 -- none
• 1 – baseline performance criteria identified and measured
• 2 & 3 – performance improvement plans created & implemented

...

1 - project team

2 - Integration team

Integration team did a 72 hour test in Beijing

...

1 - project team

2 - Integration team

...

• 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

...

2

In Casablanca we will address Resiliency at the DB level since that was a constrain in Beijing. this will be possible with the move to Maria DB w/Galera

...

• 0 – none
• 1 – manual failure and recovery (< 30 minutes)
• 2 – automated detection and recovery (single site)
• 3 – automated detection and recovery (geo redundancy)

...

1?

Level 1 definitions in Casablanca where changed.

...

• 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

...

• 0 – no ability to scale
• 1 – single site horizontal scaling
• 2 – geographic scaling
• 3 – scaling across multiple ONAP instances

...

1

Recommendation for Casablanca is Level 2; however, Level 2 requirements are unclear and cannot be committed to.

...

• 1 – single logging system across components; instantiation in < 1 hour
• 2 – ability to upgrade a single component; tracing across components; externalized configuration management

...

1

For Level 2

All new API’s must adhere to the ONAP API Common Versioning Strategy and Documentation Guidelines;  ?? Does this apply to Reboot?

Swagger 2.0? - dependent on what Oxygen supports

E2E tutorial ???

...

• 1 – user guide; deployment documentation; API documentation
• 2 – UI consistency; usability testing; tutorial documentation

• API Incoming Dependencies

List the API this project is expecting from other projects.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.

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

API Name

...

Currently Available

Needs further discussion: New Customer query to retrieve data for ScaleOut or does APPC need to build the query??

...

• API Outgoing Dependencies

API this project is delivering to other projects.

API Name

...

Link toward the detailed API description

https://onap.readthedocs.io/en/latest/submodules/appc.git/docs/APPC%20LCM%20API%20Guide/APPC%20LCM%20API%20Guide.htmll

• Third Party Products Dependencies

Third Party Products mean products that are mandatory to provide services for your components. Development of new functionality in third party product may or not be expected.
List the Third Party Products (OpenStack, ODL, RabbitMQ, ElasticSearch,Crystal Reports, ...).

Name

...

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

Sub-Components

NA

ONAP Dependencies

List the API this release is expecting from other releases. Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.

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

API Outgoing Dependencies

API this release is delivering to other releases.

Architecture

High level architecture diagram

At that stage within the Release, the team is expected to provide more Architecture details describing how the functional modules are interacting.

Indicate where your project fit within the ONAP Archiecture diagram.

Block and sequence diagrams showing relation within the project as well as relation with external components are expected.

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

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

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.

• Testing and Integration Plans

...

...

List the risks identified for this release along with the plan to prevent the risk to occur (mitigation) and the plan of action in the case the risk would materialized (contingency).

...

.

• Resources

Fill out the Resources Committed to the Release centralized page.

• Release Milestone

...

Documentation updates planned for Beijing release are tracked under Documentation Epic: APPCSO-993675

Other Information

• Vendor Neutral

...