...

...

• Upgrade of ODL to Fluorine SR2 (CCSDK dependency)
• Platform Maturity (i.e., S3P items)  https://wikilf-onap.onapatlassian.orgnet/wiki/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://wikilf-onap.onapatlassian.orgnet/wiki/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:
    Absolute Minimum expectation:
  • CII badging passing level
  Continuously retaining no critical or Level 1, level 2 (Stretch)
  • Level 1: CII Passing badge
    • Including no critical and high known vulnerabilities > 60 days old
  All communication
  • 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
  .
  • Desired expectation is full CII badging silver level, if not 75% towards that.
  Scalability: Level 1
  
  • Level 1
    • 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 (PartialStretch)
    
    • 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

• Documentation updates (readthedocs) for Dublin, such as, but not limited to:
  
  • LCM API Guide
  • Release Notes
  • CDT GUI Guide
• Code Coverage for CDT (Javascript) - TBD, no commitment at this stage
  
• Use Cases
  • Closed Loop / E2E AutomationIntegrate automation test
    
  • Change Management - APPC will continue supporting it.
    
    

...

APPC will contribute partially to the following use cases as part of the functional requirements.

• Closed Loop / E2E AutomationIntegrate automation test
  
• Change Management (will be done by Orange team)
  

...

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.

Area	Actual Level	Targeted Level for current Release	How, Evidences	Comments
Performance	0	1 or 2 - Stretch goal	Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key APPC-1310 APPC performance testing
Stability	1 - project team 2 - Integration team	1 - project team but we may not reach 80% code coverage 2 - Integration team Assume Integration team will address Level 2 -  72 hour test in Dublin		*current (1/1113/19) code coverage is 67.5%9% Level 0: none beyond release requirements Level 1: 72 hour component-level soak test (random test transactions with 80% code coverage; steady load)
Resiliency	2	2
Security	1	Minimum Expectation	Absolute Minimum expectation: CII badging passing level Continuously retaining no critical or high known vulnerabilities > 60 days old All communication shall be able to be encrypted and have common role-based access control and authorization1, 2 (partial, please see the comments)		there is http internal connection between CDT and APPC, we need to find the resource to migrate from http to https.
Scalability	1	1
Manageability	1	1, 2(partial, please see the comments, APPC will comply two items on level 2)		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
Usability	1	1		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;   - There was an issue with ODL & API version - need to investigate further TBD - Swagger 2.0 - We dependent on what ODL Fluroine Fluorine for API documentation and they dictate version of Swagger used, currently looked like

...

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

• API Outgoing Dependencies

...

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

• Resources

Fill out the Resources Committed to the Release centralized page.

• Release Milestone

...

• Documentation, Training

• Highlight the team contributions to the specific document related to he the project (Config guide, installation guide...).
• Highlight the team contributions to the overall Release Documentation and training asset
• High level list of documentation, training and tutorials necessary to understand the release capabilities, configuration and operation.
• Documentation includes items such as:
  • Installation instructions
  • Configuration instructions
  • Developer guide
  • End User guide
  • Admin guide
  • ...

Documentation updates planned for Dublin release are tracked under Documentation Epic:

...