Versions Compared

Key

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

...

Project NameEnter the name of the project
Target Release NameCasablanca Release
Project Lifecycle StateIncubation. Refer to ONAP Charter, section 3.3 Project Lifecycle for further information
Participating Company (Alphabetical Order)Amdocs,  ATAT&T, Bell Canada,  China China Mobile, Huawei, Intel, Nokia, Orange, Tech Mahindra, VDF, ZTE

Scope

What is this release trying to address?

...

  • Platform Maturity (i.e., S3P items)
    • Resiliency
      • Level 2 - regression from Beijing, plug close gap on DB resiliency.
      • DB Resiliency was a limitation in Beijing due to the Active/Standby nature of MySQL. MariaDB w/Galera provides an active-active clustered configuration, which will support local fail-over.
    • Scalability
      • Level 1 will be a regression run on Dublin release - anticipate this to be test only
    • Stability
      • Level 1 will be a regression run on Dublin release - anticipate this to be test only
      • Level 2 requirement is expected to be covered by the Integration team.
    • Security
      • Level 1 definition has changed in Dublin. Not clear we are achieve Level 1
      • Address outstanding items related to CII Passing Badge:
        • Clearing Critical and Medium Nexus IQ Security alerts to the extent possible
        • Addressing 2 other security related items from Passing Badge related to encryption
      • Secure DMaaP topics (Dependency on DMaaP project) - Stretch Goal, not currently committed for Dublin
        • DMaaP indicated delivery would be Sept, plus
        • DMaaP story is still not written to enable APPC to assess impact at this stage.
  • Documentation updates for Dublin, such as, but not limited to:
    • LCM API Guide improvements
    • Developer guide
    • Release Notes
  • Code Coverage for UI of the Monitoring Pages(Javascript) - TBD, no commitment at this stage

Use Cases and Functional Requirements

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

...

  • VNFM SOL003 adapter support : Resources commitment from Ericsson
  • SOL005 adapter support : Resources from Verizon (under discussion).
  • CCVPN extension : Resources commitment from CMCC, VDF, ZTE.
  • Change Management Extension : Commitment based on support from ATT resources.
  • PNF extension : Resource commitment from Nokia.
  • BBS : Resources under discussion.
  • HPA extension for the other existing usecases : Support from Intel
  • Support Multi Cloud for cloud agnostic orchestration : Support from Intel and VMware.
  • 5G Support 
  • Removal of Manual interventions (Under discussion)

Minimum Viable Product

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

Functionalities

List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.

...

  • Align to the controller architecture proposed as part of ONAP by the architecture team.
  • Work with SDNC team to converge on a single controller design tool
  • Support different types of clouds, currently only support Openstackworking through Multi cloud;

Release Deliverables

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

...