...

...

• (S3P:security) Buscontroller integration for dynamic topic provisioning and AAF based role setting.  **Has dependency on DMaaP project for BusController delivery
• (S3P:Performance) Performance optimization
  • VESCollector
  • TCA (new TCA service independent of CDAP will be contributed for R3).
• VES 6.0 upgrade support (Updated  07/31/18 - VES 7.0.1 will be supported in R3 and will replace 6.0 originally planned) 
  • Primarily VES Collector updates for new domains and transformation (Security requirement for mutual TLS needs further clarification)
• DCAE onboarding tool (dcae_cli) enhancement and environment support
• (S3P: Maintainability) Logging format compliance
• (S3P: Resiliency) Multi-site support   **Has dependency on OOM Team
• (S3P: Security) Securing api/interface and authorization via AAF (Need further clarification/support from Security/AAF team -  1) CADI library not available for Python 2) Consistent solution for AAF integration not identified (security proposal has many items WIP) 3) Process of AAF certificate distribution in K8S for components not defined and esp for components interfacing with external to ONAP)
• Following R2 items (descoped due to time/resource constraint) will be continued to enhanced for platform integration/S3P needs

...

DCAE will provide support for the following use cases, currently planning on test support with no code changes expected:

• • vFW
  • vDNS
  • vVoLTE
  • Residential Broadband vCPE
  • OSAM/PNF
  • CCVPN (with certain enhancement with data collection through Restconf API from SOTN Controller - as stretch goal but under discussion) 

DCAE will support the following functional requirements listed on the Casablanca Release Requirements page: 

• • 5G/PNF
         Partial Commit - Support for new collector and services for processing highvolume RAN measurement and bulk data file processing
  • Scaling - Test only (No additional development expected from DCAE to support this requirement)

...

Sub-components are repositories and are consolidated in a single centralized place. Edit the Resouce and Repositories in the centralized page.

...

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.

...

• • Resources

Fill out the Resources Committed to the Release centralized page.

• • Release Milestone

The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.

...