Page Comparison

...

1/2/19 - APPC Project Weekly Minute

Participants:Takamune Cho,  Patrick Brady,  Aaron Hay,Ramya Balaji , J ,  Lathishbabu Ganesan

Agenda

• Casablanca Mtn Release status
• Dublin release plan

Action item

• Casablanca Mtn Release: CCSDK new image, DMaap issue
• Traffic Migration Demo by Orange team (they are in Paris, waiting their response)
• Dublin Planning: (draft)
• ODL upgrade: Fluorine SR2 (Patrick)
• S3P https://wiki.onap.org/pages/viewpage.action?pageId=16003367, https://wiki.onap.org/display/DW/Dublin+Release+Platform+Maturity
  Brown→ Jason's goal
• Performance: Level 2
• 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. - (Patrick)
• Remove un-used bundles from CCSDK’s odlsli - (Taka)
• Stability: Level 2
• 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 - (Ramya)
• 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 - (Aaron)
  • CSIT OOM (Integration)
• Security:
  
  • 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 authorization.
  • Desired expectation is full CII badging silver level, if not 75% towards that.
• 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(Aaron), ansible (Asking Orange team),  -
• Manageability: 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 - Taka will check
• Usability: Level 2
  • Level 2:
    • API Documentation
      • All new API’s must adhere to the ONAP API Common Versioning Strategy and Documentation Guidelines
      • All existing APIs must be documented in Swagger 2.0

• Use Case: https://wiki.onap.org/display/DW/Dublin+Release+Requirements
• E2E automation / closed loop
• Change Management (CM) (Orange)
• Controller Design Studio
• Design time: CDT/CDS GUI integration (TechM)

Misc:

Please Join RocketChat if you want to collaborate online. You need to be added to the group chat, but you need to create a username in RocketChat first,otherwise we can't add you. http://onap-integration.eastus.cloudapp.azure.com:3000/group/onap-appc

INT: http://onap-integration.eastus.cloudapp.azure.com:3000/group/onap-integration

NO Recording for this meeting, since ONAP 4 room has been occupied by F2F event in Paris.