Versions Compared

Old Version 86

changes.mady.by.user Randa Maher

Saved on

compared with

New Version 87

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

...

    • CDT Tool - an APP-C Design Tool enabling VNF owners to create templates and other artifacts for APP-C Configure command (used to apply a post-instantiation configuration) as well as other life cycle commands. Missing piece of functionality for Test Action
    • Documentation updates for Beijing
    • On-going requirements discussion during Beijing to fleshout requirement for vDNS scaling use case for Casablanca…  Pam/Brian/Paul/etc..


01/17/18 - APPC Project Weekly Minutes

Agenda:

  • Resiliency Testing (Sharon)
  • 72 hr test planning (Scott)
  • Code Coverage
  • CDT repo
  • Manual Scaling
  • AAF
  • Review JIRA - housekeeping items
  • Misc - FOSS & Commit Process

Participants: Randa Maher, Aaron Hay, Patrick Brady, Scott Seabolt, Herb Patten, James MacNider, Ryan Young, Sharon Chisholm, Veer Rajasekar, Hector Anapan-Lavalle, Gervais-Martial Ngueko, Shubhada Vaze, Skip Wonnell, Takamune Cho

Actions:

  • Takamune Cho to create a story for backlog to track the changes needed to replace usage of powermock with mockito.
  • Patrick Brady to request new repo for CDT tool - appc/cdt

Notes:

  • Resiliency Testing (Sharon)
    • Sharon shared details on what SDNC is doing to meet the Resiliency testing recuirement for Level 2 (automated failover - single  site) - see slides
    • SDNC is leveraging  Kubernetes and OOM to address resiliency requirements
    • Advantage of using Kubernetes (vs. cluster capabiity of ODL) is that Kubernetes capability to recover a failed node
    • Healthcheck currently is at the pod level to determine if failover will be done or not. Sharon will confirm this.
    • Aaron Hay is the prime for the APPC Resiliency Epic (APPC-414)
    • APPC and SDNC teams will work closely together since there is a lot of synergy to be realized due to similar architectures & dependencies.
  • 72 hr test planning (Scott)
  • Code Coverage
    • Patrick provided a demo on using Junit and Mockito so that everyone can contribute to this requirements.
    • Slides and recording have been posted to wiki: Code Coverage
    • The Epic to track code coverage contributions is APPC-342
    • There are still ~20K lines of code without coverage; select the module you want to work on and created a story under APPC-342 so that folks know what you're working on and don't duplicate. You can follow Patrick's example (APPC-369)
    • You can use this link to determine the code that still needs coverage: SONAR Coverage
    • Taka will add a story to the backlog to replace powermock with Mockito. This is a backlog item at this point; I think we can get to the 50% with the current set of uncovered lines.
  • CDT repo
    • Patrick will request a new repo for the CDT tool: appc/cdt
    • Instruction for requesting new repo are here: Resources and Repositories
    • CDT tool is still missing "Test Action" command to be fully functional - working with AT&T Dev team to see if we can get this contributed in time for Beijing. 
    • Prime for this Epic (APPC-187) are Skip Wonnell and Patrick Brady
  • Manual Scaling
    • Awaiting confirmation of 2 additional resources from AT&T to commit supporting manual configscaleout.
    • If resources are confirmed, we will add this to our scope for Beijing. Note that this is "Manual", not Auto Scaling (ie closed loop)
  • AAF
    • Ryan Young is prime for driving this story: APPC-404
    • We need to secure AAF team's delivery plan for AAF-91 before we can finalize APPC plans for APPC support of AAF.
    • Ryan Young will work with Jonathan Gathman and Sai Gandham from AAF team to coordinate.
    • We need AAF team to deliver their story with sufficient time allowed for APPC to complete their work (develop & test)
  • Security - CII  Passing Badge
  • Review JIRA - housekeeping items
    • We did not get to this topic, we will cover next meeting....
  • Misc - FOSS & Commit Process
  • Ansible code (DG/Adapter)
    • SDNC project has a need for this capability; the current plan is for them to clone this code into CCDSK for Beijing to support their Change Management use case.
    • However since this is common functionality, the proposal is to move this to CCSDK project long term. APPC will not do anything with this in Beijing, but something that needs to be addressed in Cassablanca.