Versions Compared

Key

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

...

  • Pairwise/integration testing notes are tracked on the paiwise wiki page: Pairwise Testing - Amsterdam
  •  APPC changes to support MultiVIM - AAI query (APPC-185)
    • Being worked by Ryan and should be done by end of week 9-8-17 - working with Jim Forsyth from AAI
    • AAI team working through some issues with their master branch, but also anticipate being ready by end of week.
  • ODL upgrade (APPC-91)
    • Looking code for end of week, draft gerrit submit made, working through some failing junits.
  • CSIT
    • APPC-118 - Aaron working on this
    • APPC-113, 119, 120 - Phil
    • Story for the LCM Restart - VM and VNF - created APPC-192 and APPC-193
  • Sprint 2- stories in question - code contribution confirmed, stories and sprint closed
  • Spritn 3 - started - ends 9/15
  • Sonar - coverage up to 24% - up 6% since last meeting. 

...

  • Contributors for Beijing
    • Following three folks from TechM added for Beijing - Welcome!
      • Atul Shegokar 
      • Sanchita Pathak
      • Shubhada Vaze
    • Resources and Repositories wiki updated/cleanded up for Beijing
  • F2F Santa Clara notes
  • Carrier Grade Requirements..
    • Levels mentioned at last meeting are documented here:Platform Maturity Requirements (fka aka Carrier Grade)
    • Initial assessment for APPC was based on the survey team responded to from Jason Hunt. APPC ranked as follows:
      • Performance: 0
      • Stability: 0 
      • Resiliency: 1
      • Security: 0
      • Scalability: 1
      • Manageability: 2 
    • Results of assessment shared at F2F based on responding projects (~15 of them)

...

  • Stretch goals were presented during F2F for above categories that team will need to assess for feasibility based on effort and resources. The minimum level requested for Beijing noted in parenthesis.
    • Performance: 1 (1 for closed-loop projects; 0 for remaining)
    • Stability: 2 (1)
    • Resiliency: 3 - for run time project  (2 for run time projects)
    • Security: 2 (1)
    • Scalability: 1 (1)
    • Manageability: 2 (1)

  • Junit coverage
    • Patrick is working to add junit to the adapter code.
    • Randa will create an Epic (done: 
      Jira
      serverONAP JIRA
      serverId425b2b0a-557c-3c0c-b515-579789cceedb
      keyAPPC-342
      ) and team members can create stories under this epic to document which module they will work on so we don't have duplicated effort.
  • Project Meetings:
    • Takamune Cho will host the 12/20 meeting.
    • 12/27 meeting will be canceled


12/20/17 - APPC Project Weekly Minutes

Agenda:

  • ONAP logging framework discussion
  • Beijing Release join effort


ParticipantsPatrick Brady, Ryan Young, Scott SeaboltTakamune Cho

Note: Due to LF's Zoom room had a technical issue. We used Taka's private zoom room to alternatively open the meeting. Therefore, some contributors were not able to join. The agenda above will be continuously discussing after holiday.  next week 12/27/2017 weekly meeting will be cancelled. Happy Holidays!!