Page Comparison

• APPC Meeting Minutes - (Jan'19 - )
• APPC Meeting Minutes - (Jan'19 - )
• APPC Meeting Minutes - (Jan'19 - )

1/2/19 - APPC Project Weekly Minute

...

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

1/16/19 - APPC Project Weekly Minute

Participants:Takamune Cho,  Patrick Brady,  APPC Meeting Minutes - (Jan'19 - ),Ramya Balaji, Joss Armstrong, Fari Behi, J Hartley, Lathishbabu Ganesan

Agenda

• Casablanca Mtn Release status
• Dublin release plan

Action item

• Casablanca Mtn Release: 1.4.4 Released
• Traffic Migration Demo by Orange team
• Dublin Planning: (draft)
• ODL upgrade: Fluorine SR2 – APPC-1277
• S3P https://wiki.onap.org/pages/viewpage.action?pageId=16003367, https://wiki.onap.org/display/DW/Dublin+Release+Platform+Maturity
• Performance:
• Level 1: baseline performance criteria identified and measured  (such as response time, transaction/message rate, latency, footprint, etc. to be defined on per component) – Joss APPC-1311
• Level 2: performance improvement plan created  - Joss APPC-1311
• APPC Pre-install appc features during docker build. – APPC- 1322 Patrick
• Remove un-used bundles from CCSDK’s odlsli – CCSDK- 944 Taka
• Stability:
• Configuration Enhancement https://wiki.onap.org/display/DW/APPC+Configuration+Enhancement - Stretch
• 80% test coverage??
• Resiliency:

• 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
• 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 (low priority by TSC)
  • Level 2:
    • API Documentation
      • All new API’s must adhere to the ONAP API Common Versioning Strategy and Documentation Guidelines - Taka
      • All existing APIs must be documented in Swagger 2.0

• OOM: move to variable for database’s user/password – Aaron APPC-?
• CSIT OOM – by INT team
• 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.
• Stretch goal: Project Level 2
• Scalability:
• Level 1: supports single site horizontal scale out and scale in, independent of other components.
• Clustering env with downstream: netconf,APPC-1258 (Arron) ansible (Orange team?).
• Manageability:

• logging Enhancement https://wiki.onap.org/pages/viewpage.action?pageId=28378955 ( low priority by TSC)
• Usability:

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

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