Versions Compared

Old Version 128

changes.mady.by.user Randa Maher

Saved on

compared with

New Version 129

changes.mady.by.user Randa Maher

Saved on

Key

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

...

Participants: Randa Maher; Scott Seabolt; Patrick Brady; ry303t; Takamune Cho; Aaron Hay; Veer Rajasekhar; Vidhya Nerella; Ramya Balaji; Samuli Silvius; Shubhada Vaze; Starge??
Recording: APPC Weekly Project Call 4-25-18.mp4

Actions from last meeting:

  • Scott Seabolt & Aaron Hay to work together to pull together some lab diagrams for WindRiver lab setup for APPC usage (clustered vs non-clustered environments)
    • Update: 2-21-18: Information started to be populated here: APPC WindRiver Lab
    • Update: 3/21/18: Pending; however, note that all IP info is provided on wiki, diagram will be added later as time permits give other higher priority items.
    • Update: 4/25/18: CLOSED. APPC WindRiver Lab
  • Patrick Brady to provide a knowledge share on the changes that upgrade to Nitrogen brings to APPC once he is done with the ODL upgrade.
  • Randa Maher setup call to discuss testing in WindRiver APPC dev lab after we get Beijing successfully deployed.
  • Update: 3/28/18: Discussions started, but until we have a working Beijing environment
  • Update: 4/11/18: In-Progress
    • Update: 4/18/18: Team is still working through APPC w/Nitrogen stability; need to get past the issue with Request Handler not coming up.
      Until that's resolved, little testing can be done.
    • Update: 4/25/18: Still working through some blocking issues .(see APPC-859)
  • ry303t to investigate security vulnerabilty reported againt org.glassfish.grizzly, which is pulled in by CDP-PAL.
    • Update: 4/18/18: No update today, have more urgent items around AAF integration feature that still needs to be completed.
    • Update: 4/25/18: Pending; working higher priority items at the moment.
  • Takamune Chowill follow-up with Dan on SDNC project to see if he was able to successfully upgrade EELF. APPC has issues with version incompatibility with logback & sl4j and ODL. (related to APPC-784)
    • Update: 4/25/18: Query sent, no response yet
  • Blockers:
    • APPC Event Listener issue (APPC-859) blocking testing…
  • Pending items
  • AAF integration - documentation
    • Need final testing, and
    • Documentation on how to configure
    • Need to close out risk: Beijing Risks
  • Security items - what you got left Taka?
  • APPC-705  -httpclient-osgi : 4.3.3 -  can this be closed?
  • How about this one? org.apache.httpcomponents : httpclient : 4.5.2
    • APPC-706 - jackson-core : 2.3.2 - can this be closed?
  • Provide list of ODL plugins used by APPC (question raised by Andrej Zá?Zán)

      New Actions Items:

      Agenda & Notes:

        • Update: 4/25/18: odl.yangtools, odl.mdsal, broker-mdsal, odl.mdsal.model, odl.mdsal.features, odl.controller.mdsal, odl.mdsal.yang.binding, odl.controller.config.api, odl.ietf-inet-types, odl.ietf-yang-types, odl.yang.jmx.generator,  odl.sal.api.gen.plugin, odl.commons.opendaylight, odl.karaf.empty.distro, odl.sal.core.api

      New Actions Items:

      Agenda & Notes:

      • Blockers:
        • APPC Event Listener issue (APPC-859) blocking testing…this is the highest priority item that needs to be addressed at the moment.
          • Workaround is to fall back to http dmaap adapter, which seems to be working. Further testing taking place today.
      • Pending items
        • AAF integration
        • Security items - what you got left Taka?
          • APPC-705  -httpclient-osgi : 4.3.3 -  can this be closed?  CLOSED
          • How about this one? org.apache.httpcomponents : httpclient : 4.5.2  Covered by APPC-702 and listed on wiki security checklist
          • APPC-706 - jackson-core : 2.3.2 - can this be closed? CLOSED
          • APPC-784 - logback issue - Pending
            • We tried upgrade to 1.2.0 and that broke APPC functionality; there is not enough time to troubleshoot this in Beijing and needs to be moved to Casablanca for resoltuion.
            • Taka to create storiy in R3.
          • APPC-841- org.glassfish.grizzly : grizzly-http : 2.3.28 - Pending
        • Heat deployment to support CDT (Aaron)
          • Also - Is CDT going to be an issue with OOM deployment due to current constraint in Environments.ts?
      • Testing
        • CDT testing
        • ScaleOut testing
        • Resiliency tests
        • CDT (Aaron)
          • Action: JIRA will be created by Aaron for heat deployment of CDT and submit change
          • Also - Is CDT going to be an issue with OOM deployment due to current constraint in Environments.ts? - Aaron validate that it deploys correctly with OOM and he validated that he can access teh login page - issue will be when you try to save to APPC, since they use teh host url that you're on and that's what they try to connect to.... Need to do more testing in our cluster environment.
      • Testing
        • CDT testing
          • APPC-860 - Needs to Default to http for connecting to APPC REST services - Fix submitted
          • Need someone to focus on artifacts needed for ConfigScaleOut (Ramya or Vidhya?)
            • Vidhya will look further into this.
        • ScaleOut testing - Vidhya will investigate what artifacts are needed; testing can be done via apidoc. We also still need to get VNF data populated into AAI
        • Resiliency tests
          • Two of the tests passed, still waiting to complete the scaling test case, waiting an OOM defect to be fixed related ot MD-SAL storage clearing.
        • Generic_restart via multivim for regression - what are we missing?
          • Patrick will create a defect to track this - JIRA opened: APPC-863
      • Defects:
        • APPC-307 - can we close this one ? (Scott) - Scott will retest
        • APPC-857 -  ccsdk-dgbuilder container failed - we need to fix this  (Patrick)
          • The issue appears to be that the paths for DG Builder have changed to ccsdk instead of sdnc.  We will update our APPC docker-compose.yml file to reflect the updated paths.
        • APPC-858 - merge change - Done
      • Documentation:
      • RC0 - still need to close out remaining items.
      • RC1 -

      Integration

      RC0

      Avril 19, 2018

      Release Candidate 0

      RCs are to ensure proper alignment and execution on End 2 End Release Test Cases and End 2 End functional Test Cases.

      Project Team focused its effort on:

      1. supporting integration testing
      2. closing high priority defects
      3. supporting Documentation team


      RC1

      May 3, 2018

      Release Candidate 1


      RC2

      May 17, 2018

      Release Candidate 2

      Sign-Off

      Release Delivery

      May 24, 2018

      Beijing Release Sign-Off

      https://wiki.onap.org/display/DW/Release+Planning#ReleasePlanning-CasablancaRelease>

      • Misc
        • OOM failing healthcheck: https://jira.onap.org/browse/OOM-992
          • Update from Aaron:" I was able to verify that OOM health check is good for APPC. The OOM team mentioned that they have some resource issues in Tlab and that could be the reason for the failure being shown there"