Versions Compared


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


  • Support new LCM action Reboot and various other enhancements to existing LCM actions (Tracked under Epic: APPC-899)
  • Documentation updates (readthedocs) 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.
        • Assumption is that AAI data needed is available
      • No commitment on Controller Type since requirements are still unclear.
    • Change Management - No Commitment
    • 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)


Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.


  • 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 APIsODL API authorization
  • MultiVIM - APPC can access Openstack via MultiVIM or CPD-PAL. MultiVIM is optional for APPC at this stagestage. Support of MultiVIM is limited to the Generic_Restart actionaction only.

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
  • AAI - for named query to return the applicable data (Action: Need to discuss with AAI if they will provide named query or expand name query provided in Amsterdam.


High level architecture diagram


AreaActual LevelTargeted Level for current ReleaseHow, EvidencesComments
  • 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

Assume Integration team will address Level 2 -  72 hour test in Casablanca

  • 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


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?  Partial

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

    Unclear if we can meet Level 1 at this time based on Open Questions:

    1. How do we handle false positives and third party issues reported in NexusIQ;
      1. We will tackle Criticals first and then address mediums as time permit
    2. How do we deal with contiguously retaining no critical or high known vulnerabilities > 60 days when we are on a 6 month release cycle
    3. Addressing ALL communication has dependency on other projects, such as DMaaP, and dependency alignment does not fit schedule.

    • 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


    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




    Recommendation for Casablanca is Level 2; however, we cannot meeting 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    - There was an issue with ODL & API version - need to investigate further

    Swagger 2.0 - We dependent on what ODL Oxygen for API documentation and they dictate version of Swagger used, currently looked like v1.2

    E2E tutorial ???

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


    API 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 Available

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

    CCSDKOpenDayLight, SLI, AAI Client, dblibTBDEnd of JuneTBD
    DMaaPAPI  to publish/subscribe to  events sent for VNF/VM action requests.Will DMaaP be providing support for secure topics?TBDDMaaP API
    AAFApplication Authorization FrameworkCurrently AvailableCurrently Available


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

    Risk identifiedMitigation PlanContingency Plan
    ODL upgrade to Oxygen & DB to MariaDB - depends on CCSDK projectsCCSDK team has started work early on these two dependencies; They are currently telling us they plant o have these ready at start of Casablanca.Fall back to Nitrogen &
    MySQL (same as Beijing)SO dependency to delivery needed data to support the ScaleOut use case?
    MySQL (same as Beijing)
    SO dependency to delivery needed data to support the ScaleOut use case - need to provide vf-module-id of the vDNS scaled?
    Continue using the flow as designed in Beijing
    APPC needs data to be in AAI in order to support the ConfigScaleOut use case for retrieval of the configuration data. Either SDNC (or SO) must write this data into AAI after the instantiation event happens.
    Continue using the flow as designed in Beijing
    DMaaP support of Secure Topics?

    • Resources

    Fill out the Resources Committed to the Release centralized page.

    • Release Milestone