...

• Upgrade of ODL to Fluorine SR2 (CCSDK dependency)
• Platform Maturity (i.e., S3P items)  https://wiki.onap.org/display/DW/Dublin+Release+Platform+Maturity
  
  •  Green color → Target level ( details see Platform Maturity below)
  • Performance:  Level 1, Level 2 (Stretch)
    
    • Level 1: baseline performance criteria identified and measured  (such as response time, transaction/message rate, latency, footprint, etc. to be defined on per component)
    • Level 2: performance improvement plan created 
    • unzip feature.zip during building docker.
    • Remove un-used bundles from CCSDK’s odlsli - depends on CCSDK
  • Stability: Level 1 (remain test coverage 50%)
    
    • Level 1: 72 hour component-level soak test (random test transactions with 80% code coverage; steady load)
    • Level 2: 72 hour platform-level soak test (random test transactions with 80% code coverage; steady load)
    • Configuration Enhancement https://wiki.onap.org/display/DW/APPC+Configuration+Enhancement - Stretch goal
  • Resiliency: Level 2
    
    • Level 2: support automated failure detection & rerouting 
      • within a single geographic site
      • stateless components: establish baseline measure of failed requests for a component failure within a site 
      • stateful components: establish baseline of data loss for a component failure within a site
    • OOM: move to variable for database’s user/password
    • CSIT OOM - Integration team
  • Security: Level 1, level 2 (Stretch)
    • Level 1: CII Passing badge
      • Including no critical and high known vulnerabilities > 60 days old
    • Level 2: CII Silver badge, plus:
      • All internal/external system communications shall be able to be encrypted: there is http internal connection between CDT and APPC, we need to find the resource to migrate from http to https.
      • All internal/external service calls shall have common role-based access control and authorization using CADI framework.
  • Scalability: Level 1
    
    • Level 1: supports single site horizontal scale out and scale in, independent of other component
    • APPC does not support dynamic cluster configuration in k8s only support static cluster configuration
    • Clustering env with downstream: netconf,  ansible
    • Using Alpine linux distribution docker image as base.
  • Manageability: Level1, Level 2 (Stretch)
    
    • Level 2:
      • A component can be independently upgraded without impacting operation interacting components
      • Component configuration to be externalized in a common fashion across ONAP projects
      • All application logging to adhere to ONAP Application Logging Specification v1.2
      • Implement guidelines for a minimal container footprint - See this presentation and follow the Container Image Minimization Guidelines
  • Usability: Level 1
    • Level 1:
      • User guide created
      • Deployment documentation
      • API documentation
      • Adherence to coding guidelines

...

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

...

Indicate where your project fit within the ONAP Archiecture diagram Dublin+Architecture.

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

...

Platform Maturity

Refering to to CII Badging Security Program and Platform Maturity Requirements S3P, 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.

...

• Resources

Fill out the Resources Committed to the Release centralized page.

• Release Milestone

...