Versions Compared

Old Version 81

changes.mady.by.user Randa Maher

Saved on

compared with

New Version 82

changes.mady.by.user Randa Maher

Saved on

Key

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

...


6/19/17 - APPC Project Kick-Off

...

  • Preliminary view of scope for Beijing
    • Additional LCM action support: Quiesce, AttachVolume, Reboot, Query, DetachVolume, Software upgrade
    • Configuration Design Tool (CDT) UI
    • Change org.openecomp to org.onap
    • ODL upgrade to Nitrogen (driven by CCDSK updates/dependency)
    • Change DB to MariaDB (driven by SDNC dependency)
    • Support Configure action (fix bugs from Amsterdam)
    • Security - AAF integration

      • Planning to submit a feature request to AAF for improvement of design to eliminate need to update ODL jars when filter changes are need.  This will also benefit SNDC, who uses APPC filters

      • Meeting planned with AAF team on 12/7/17.
    • Increase code coverage to 50%
    • Geo-red support; fail over support
      • Need to review non-functional requirements to see where we comply and where we don't
    • Support integration with SO…?? - this is TBD at this stage..
      • This is dependent on how ready SO is to work with us. From our side, it's a testing effort for the actions supported.
      • Needs further investigaton
  • APPC Beijing contributors?
    • Need contributors from Amsterdam to confirm if they will continue to participate in Beijing. An email was sent out asking for folks to confirm by 12/12/17. A lack of response will be interpreted as not part of Beijing.
    • For participants that were not formally part of the Amsterdam release, please send email to Randa if you would like to be a contributor in Beijing. We need folks that are willing to do development and testing
  • Upcoming releases - key dates
    • Amsterdam Patch (release onap-1.0.1)
      • 12/21 - Readiness Checkpoint, which entails
        • 1) Review all High, Highest Defects committed in Amsterdam since Nov 16
        • 2) Review remaining defects to be included in Amsterdam Maintenance Release
      • 1/18 - Signoff
    • Beijing Release (Release Calendar: https://wiki.onap.org/display/DW/Release+Planning#ReleasePlanning-ONAPBeijingReleasePlanning
      • 1/8 - Project Planning closure
      • 1/18 - M1 review
        • Must be completed for M1
          • Release Planning Template, filled out by 1/8
          • Release Planning Checklist: To be filled out by Jan 17
      • 4/5 - Code Freeze
      • 5/24 - Signoff
  • Projects in Beijing release: 
  • JIRA Management
    • If you port a defect fix back to Amsterdam - make sure Amsterdam AND Beijing are listed in Fix Version field.
    • When you submit Gerrit, move your JIRA ticket to Submitted, when changed is Merged, move your JIRA ticke to Delivered.
    • If you opened the Jira, you can close it once your changed is merged. If you did not open the ticket, reassign ticket to originator for closure (ticket should be in Delivered state when you assign back to originator)
    • Randa will try to create a quick cheat-sheet for reference.
  • Lab needs for Beijing - review with team; need for geo-red
  • Key changes with Beijing
    • Being proposed: All code contributions need to be accompanied with juni
  • Vacations in Dec/Meeting plans
    • Patrick out after 12/19 until 1/2
    • Skip out after 12/13 until 1/2
    • Randa out after 12/15 until 1/2
    • Meeting for 12/20 & 12/27 will most likely be canceled.
  • CSIT for R1 and R2
    • CSIT will run on snapshot for Amsterdam; running them on released version does not make sence.
    • CSIT will run on also run on Beijing (Master)

12/13/17 - APPC Project Weekly Minutes

Agenda:

  • Contributors for Beijing
  • F2F Santa Clara
  • Carrier Grade Requirements
  • Next two weeks

Participants: Randa Maher, Aaron Hay, Patrick Brady, Ryan Young, Skip Wonnell, Shubhada Vaze, Veer Rajasekar, Ramu N

Action Items:

  • Need to follow-up to make sure we don't have any overlap between CDT APPC tool and the "VNF SDK Design Studio" mentioned in the SD-WAN slides.

Notes:

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

Image Added

  • Stretch goals were presented during F2F for above categories that team will need to assess for feasibility based on effort and resources
    • Performance: 1
    • Stability: 2
    • Resiliency: 3 - for run time project
    • Security: 2
    • Scalability: 1
    • Manageability: 2 
  • 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