...

• 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 Same as was defined for Beijing with the adding of CDT.

...

...

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

...

• 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.

• Testing and Integration Plans

...

• 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

...