Page Comparison

Meeting Dates

• APPC Meeting Minutes
• 6/21/17 - APPC Project Weekly Minutes
• APPC Model Driven Approach - PMiller 6-22-17.mp4
• APPC Meeting Minutes

• APPC Meeting Minutes

• APPC Meeting Minutes

• 07/06/17 - APPC Restart Overview slides
• APPC Meeting Minutes
• APPC Meeting Minutes
• APPC Meeting Minutes
• APPC Meeting Minutes
• APPC Meeting Minutes
• 08/11/17 - APPC/CDP-PAL/MultVIM - Touch Base 1
• APPC Meeting Minutes
• APPC Meeting Minutes
• APPC Meeting Minutes
• APPC Meeting Minutes
• APPC Meeting Minutes
• APPC Meeting Minutes
• APPC Meeting Minutes

• 09/13/17 - APPC Project Weekly Minutes

• APPC Meeting Minutes
• 09/20/17 - APPC Project Weekly Minutes
• APPC Meeting Minutes
• APPC Meeting Minutes
• APPC Meeting Minutes

• APPC Meeting Minutes

• APPC Meeting Minutes
• APPC Meeting Minutes
• APPC Meeting Minutes
• APPC Meeting Minutes
• APPC Meeting Minutes
• APPC Meeting Minutes
• APPC Meeting Minutes
• APPC Meeting Minutes
• APPC Meeting Minutes
• APPC Meeting Minutes
• 02/12/18 - Scale Out dependency and cross product coordination - Continued

• 02/13/18 - Scale Out dependency and cross product coordination - VID to SO Controller Type- round 2

• 02/14/18 - APPC Project Weekly Minutes
• APPC Meeting Minutes
• APPC Meeting Minutes
• APPC Meeting Minutes
• APPC Meeting Minutes
• APPC Meeting Minutes

• APPC Meeting Minutes

• APPC Meeting Minutes
• APPC Meeting Minutes
• APPC Meeting Minutes

6/19/17 - APPC Project Kick-Off

Meeting: APPC Project Kick-Off

Date: 6-19-17

Participants:

• RANDA MAHER <rx196w@us.att.com>;
• MACNIDER, JAMES <james.macnider@amdocs.com>;
• SULLIVAN, JOEY <joey.sullivan@amdocs.com>;
• Skip Wonnell <skip@att.com>;
• BRADY, PATRICK D <pb071s@att.com>;
• SHARMA, RAHUL <Rahul.Sharma2@amdocs.com>;
• Mark Runnels <runnels@att.com>;
• SEABOLT, SCOTT <js9808@att.com>;
• MILLER, PAUL <pm3608@att.com>;
• SOLORZANO, DEE ANN <ds4681@att.com>;
• Eric Debeau <eric.debeau@orange.com>;
• YOUNG, LISA C <ly3793@att.com>;
• KLEIN, REUBEN <rk1518@att.com>;
• ANAPAN-LAVALLE, HECTOR A <ha076r@att.com>;
• Avi Chapnick <avich@amdocs.com>;
• VELARDO, PAT <pv1753@att.com>;
• Marcus Williams <marcus.williams@intel.com>
• SULLIVAN, JOEY joey.sullivan@amdocs.com

Agenda & Notes:

• Introductions
• Define what role each member will play (architect, developer, tester, etc,,,)
• Refer to  "APPC Team for Release 1"section below
• Decide on date/time for weekly meeting
• Proposed: Wed @ 11AM EST -
• Decision: go for this slot and adjust if it doesn't work
• Determine agenda for this weekly meeting
• Reuben and Ave to re-align on APPC Project proposal as identified on the wiki.
• Review release schedule
• https://wiki.onap.org/display/DW/Release+Planning
• Upcoming Milestone - M1, due 6/29
• Must have Epics/Stories defined for release 1.
• Start discussing potential scope for release 1
• Scope: https://wiki.onap.org/pages/viewpage.action?pageId=3246996
• Use Cases: Any impact?
• vCPE: https://wiki.onap.org/display/DW/Use+Case%3A+Residential+Broadband+vCPE?src=contextnavpagetreemode
• Use case still under discussion
• Here is an opportunity to show how to manage components that are not MANO compliant
• Need to define an alternative with APPC
• VoLTE: https://wiki.onap.org/pages/viewpage.action?pageId=3246140&src=contextnavpagetreemode
• As currently defined, there is no APPC impact.
• APPC and VF-C both are part of architecture; currently no plans to separate
• VoLTE is where APPC is most experienced
• vIMS & vEPC are ETSI MANO devices; we need a plan on how to handle MANO devices
• VF-C exposes a NB API
• Chef and Ansible adapters got merged this weekend; opens up the SB side

Decisions/Working agreements:

• Weekly call to be held on Wednesdays at 11AM EST initially; will adjust as needed if this time is problematic. With folks on Pacific Coast (PST), France, and Belgium, and India, this is the most accommodating for majority.
• Participant must participate as a contributor and gain some expertise before they can be nominated for Committer status.
  • Per input from Marcus, this does not appear to be aligned with ONAP TSC charter, so I'm scratching this.
    

Action Items

• Schedule call for Wed., setup zoom invite.
• For this Wednesday's team call, 6/21/17, agenda will be to realign on the APPC project proposal. Reuben and Avi to present.
• Owner: Randa/Catherine
• Status: Done.
• Schedule a call for Thurs, 6/22/17.
• Agenda for this call: Paul will present current capabilities of APPC..
• Owner; Randa
• Status: Done, call scheduled for 6/22/17 at 12PM EST for APPC Project team.
• Follow-up with Piyush, Marcus, Alexis, Rashmi on participation.
• Owner: Randa/Catherine
• Status: In-Progress

APPC Team for Release 1

6/21/17 APPC Project Weekly Minutes

Agenda

• Reviewing the APPC Project scope to realign on what was proposed/approved: https://wiki.onap.org/pages/viewpage.action?pageId=3246996
• Presented by Reuben Klein and Avi Chapnick, who were the primary authors of this proposal initially.

Plan for next meeting

• There were a lot of questions at this meeting about what APPC was, how it fit into the overall architecture, so plan for next week is to provide knowledge sharing session on current capabilities of APPC.

Notes around today's discussion.

• Today there are two Application Controller designs
  • VF-C

• Collection of OPEN-O orchestrators, more dependent on VNFC for doing many of its actions.
• APPC
  • Manages lifecycle actions through a set of commands, you have a model and inventory VNF/VNFC instances; the approach is to support different flavors of VNFs without having to ask for vendor support (no need to provide a VNF manager, just provide a model), utilize Nefconf, Chef, Ansible plug-ins.
  • When we say "model" in context of APP-C, what are we talking about?
    • APPC is agnostic, APPC is all about how we can generalize VNF management - the concept of APPC.
    • We want to take all of the management capabilities and express them as a model and policy.
    • MANO looks at each vendor system in isolation, we want to build an inter-vendor solution, build models on demand.
    • We have a series of Yang for components and some on services
      • SDC provides TOSCA model for dependency order. We want to add to these capabilities.
    • We want to get to a common set of APIs so that operations teams don't have to worry about the underlying mechanism.
    • APPC does not instantiate, this is done by SO. Once instantiated, APPC's job is to configure, manage state, and respond to actions triggered by Policy.  Such as the case of closed loop corrective actions (Eg. Restart).  APPC manages the lifecycle of VNFs.
    • Collectors are not in the scope of APPC. ONAP is an integrated system, APPC plugs into this overall system.  DCAE local is doing the analytics collection.
    • The concept of APPC is entirely independent of the client that calls it on the NB side; APPC is to create implementation of LCM and not assume.
    • There is an VNF SDK & modeling project, how do we connect with those projects? How are the dots connected? Further investigation needed.
• What would participants like to hear about in these weekly meetings.
  
  • Participants would like to learn more about APPC and how it interacts with other parts of the stack.
  • Interactions with APPC and instantiation with respect to Policy.
  • Use cases around service chaining.

06/28/17 - APPC Project Weekly Minutes

Agenda

• Recap last meeting
• Review Resources updated here: https://wiki.onap.org/display/DW/Resources+and+Repositories 
• Review Release Schedule - make sure all are aligned
• Key milestones to keep in mind can be found here: https://wiki.onap.org/display/DW/Release+Planning

• Logistics/housekeeping
• Jira APPC project & board
• https://jira.onap.org/secure/RapidBoard.jspa?rapidView=17&view=planning.nodetail&epics=visible
• Communication:
• Email: use onap-discuss with [appc] tag in subject line
• Any other options ?
• Miinutes will be kept here:
• https://wiki.onap.org/display/DW/APPC+Meeting+Minutes
• Review Use cases & Brainstorm on what we want to achieve in Release 1
• Use Case: VoLTE:  https://wiki.onap.org/pages/viewpage.action?pageId=6593603
• Use Case: Residentail Broadband vCPE: https://wiki.onap.org/pages/viewpage.action?pageId=3246168
• Use Case: vFW / vDNS: https://wiki.onap.org/pages/viewpage.action?pageId=3246170
• Other topics/dependencies
• MultiVIM
• OOM/Common Controller SDK  ?
• SDC ?

Action Items:

• Alex to get details on VNF planned for vCPE use case
• Setup call with SO & APPC teams…
• Setup call with MutiVIM team - lead Xinhui Li

Notes:

• Resources review
• Have not heard back from 1 committer; will leave him on list for now
• Sharon Chisholm will be contributing to the project, focusing on resiliency
• VoLTE Use Case
• Current approved use case does not include APPC
• There is an alternate VoLTE use case that was proposed by Gil Bullard, but marked Obsoleted.
• What are we committing for Release 1?
• Need to work out the combined architecture
• vCPE Use Case
• APPC will be contributing to the vCPE use case in the closed loop flow for VM Restart; important to note that this is VM level and not VNF level restart
• Some of the VMs selected are optimized for hardware platforms
• Some of the VNFs being used are coming from Intel, need to see if they are compatible with APPC [however, if we stiff to VM level Restart, this is not an issue for vCPE use case]
• Can use Ansible, need Ansible server and write the playbook…
• vFW / vDN Use Case
• Regression test; need to ensure these work with all the new added code..
• MultiVIM
• Separate session to be scheduled to discuss CDP-PAL

07/03/17 - APPC/SDC Discussions

Agenda

• Review of Residential Broadband vCPE with the SDC team

Attendees: Eric Lebeau, Michael Lando, Eden Rozin, Catherine Lefèvre

Key Notes

• Review of "Onboarding of infrastructure VNFs" flow
• There is already an existing APPC/SDC interface but the content is not yet really used by APPC
• The content is based on TOSCA format
• Another integration point is foreseen between SDC & APPC as part of ONAP R1:
  Currently artifacts are uploaded manually. The goal is to upload automatically.

Action Items:

• Eden will review this flow (DCAE Telemetry) as well as the second integration point (upload automatically the artifacts) with Hector Anapan by 7/10.
  
  

07/05/17 - APPC Project Weekly Minutes

Agenda

• Review items from checklist
• SDNC upgrade to Carbon - APPC impact
• Scope for Release 1
• Work needed specifically to support vCPE use case
  • VM level restart
• What areas are folks interested in ?
• Agree on sprint cadence and goals
  • July
  • Aug
  • Sept (code freeze 9/14)
• Labs
• Documentation

Participants:

Notes:

• Review items from checklist

• All contributors and committers should familiarize themselves with:
• Code Coverage and Static Code Analysis
• Free and Open Source Software
• Commit Messages
• Code Review
• Development Practices

• Release 1 key goals
1. Consume all the code contributions, large part coming end of July. Deliver on the model driven design and additional features
2. Support VM Restart for vCPE use case
3. Support vDNS/vFW

• Scope for Release 1 - specifics
• Consume all code contributions [stories in backlog - need to update/complete adding stories - Action: Randa to update]

• • Upgrade to Carbon to stay aligned with SDNC
    • Need to validate/confirm with Dan Timoney from SDNC team that this is indeed the plan for R1
    • If so, Need to raise as a risk for APPC - could have multiple side effects that could impact timeline.
    • Drop date date for ODL Docker needed from SDNC would be 8/4
    • Working to get confirmation from Dan

• • Support vCPE Use Case for VM level restart
    • Need DG for VM Restart
      • What is needed to make this work… ?
    • How do we test -
    • • Will we depend on Integration team to validate, or
      • Can we connect Integration lab to our APPC in  TLAB?

• • • Action: Need details on the vCPE - are they running on hardware or Openstack?  -  schedule call for Monday w/Vimal & Brian -
      
      • Randa following up to see if we can setup a review on Monday at 11AM EST if that works.

• • Integration with MultiVIM
    • Discussion taking place with MultiVIM team to see how APPC is impacted by this change.
    • Meeting planned for tomorrow (Thurs @11AM EST; working to get CDP-PAL SME to present CDP-PAL, Scott will provide flow sample for APPC.
    • Demo proposal - VM/VNF restart of vDNS/vFW via MultiVIM ?   Need to discuss in more detail

• • Integration with OOM
    • Per Catherine, Objectives for release 1 based on OOM call earlier today:
    1. 1. Want to move to container paradigm using Kubernetes - will provide guidelines to teams to move from Docker to Kubernetes
       2. Will work with team to prioritize - not sure if APPC be on the priority list
    • ECOMP Controller proposal is not part of release 1; will be considered for Release 2
    • Hector has been involved with OOM
    • • Bell Canada used Kubernetes template to do test - template of ONAP based on Heat templates
      • We want to keep APIs generic, multiple approaches can be taken (ECOMP SDK & OOM, Robot Framework, etc..)
      • Action: Hector will setup a session with John Ng and Nicolas Hu to discuss OOM.
    • Need to see how APPC can contribute to OOM -
    • • Action to AMDOCS team (Michael Meller & Sharon C. to see how  APPC would interplay with OOM

• • Need clear list of all API available for Release 1 and their type - Scott is working with team to get this.

• • Lab readiness (T-LAB)
    • T-Lab setup for vDNS/vFW
    • SDC & AAI integration..  ? What VNFs do we on-booard? Where do we get data?
    • Lab Status:
    • • People are still working on this, but should be done this week. Action: Hector will follow-up on status.

• • Documentation
    • The Documentation project is will provide guidance on how documentation should be done in ONAP; however, each project is responsible for updating their documentation per release
    • When Documentation Project will have their recommendation and tools in place  is TBD at this point.
    • You can refer to their project page to see what is under consideration.
    • APPC has the following documents that will need to be updated for Release 1
    • • API Guide
      • User Guide

• • HA/Resiliency stories identifications [items for roadmap]
    • Cluster deployment
    • Geo-redundancy
    • Note that nothing is being committed for release 1 related to this area, this item is only about having the conversations and contributing stories to the backlog for future releases

• • Replace openecomp with onap [APPC-13]
    • • Any volunteers to start working on this?
  • Educational Video

• What areas are folks interested in ?
• Send note to Randa
• Do you have local environments setup? If not, 'how-to' instructions can be found here:
• https://wiki.onap.org/pages/viewpage.action?pageId=6590586

07/06/17 - Meeting with MultiVIM team

Material reviewed attached.

• appc_restart_overview-v3.pptx
• APPC-CDP-PAL-Reference.xlsx
• CDP_PAL.mht

07/12/17 - APPC Project Weekly Minutes

Agenda:

• ODL Version for R1
• vCPE Use Case
• Code Contributions
• Labs for testing
• MultiVIM
• OOM
• Integration Testing with AAI & SDC
• Other topics?

Notes:

• ODL Version for R1
• Confirmed with SDNC team - they will be using Carbon release of ODL for R1.
• ODL Docker will not be available until end of July.
• SDNC-26 (ODL upgrade) - ETA is end of July
• APPC Story needed:  Need story to upgrade ODL version to Carbon
• vCPE Use Case
  • https://wiki.onap.org/pages/viewpage.action?pageId=3246168
  • Confirmed that we are part of close loop, triggered by Policy
  • APPC action will be Restart of vMUX
  • VNF restart (dependency on DG code contribution from AT&T, ETA pending), VNF restart will entail AAI query for needed data

• Code Contributions -
• Upcoming code contribution from AT&T pre-requisite for vCPE use case support, teams working to get that submitted
• awaiting ETA  (restart DG key)
• Action: Follow-up with Scott on the list of DGs being open-sourced
• Labs
  • T-Lab: Lab prep in progress - Spondon working on this - availability date TBD
  • T-lab still waiting on servers… not likely to be ready this week
  • T-Lab lab will be available externally via VPN
  • Integration team discussion with WindRiver for a possible development lab for pairwise testing… more details pending.
    • They are taking images from Jenkins (latest image) to stand up lab…..
    • Generating jira issues if they run into problems
    • Focusing on e2e connectivity at the moment, using the demo use cases to validate lab.

• MultiVIM
• Scope for R1 - MultiVIM proxies requests…
• Need to confirm support for R1 from CDP-PAL development team
• CDP-PAL is not part of ONAP and opensource available via github, so we need their agreement to partner on this release for any changes needed in CDP-PAL.
• Reached out to development owner of CDP-PAL (Ram Koya), awaiting feedback from the team if they have capacity to support.
• Assuming CDP-PAL is onboard, when would MultVIM target for readiness to start integration testing.
• Action: Randa to check if there are any dependencies between Carbon  & CDP-PAL - checking with Varun
  • 7/18/19 update: No, there is no dependency between CDP-PAL and ODL version
• Multivim: R1 is a short term goal to demonstrate integration with APPC, goal to minimize impact due to lack of bandwidth/resource on both sides,  but for R2 or beyond, long term approach is TBD, various options still under assessment - CDP-PAL, Cloudify, something else??Comment: If they move to a model approach, this is a much larger impact
• OOM
  • Invited David (OOM PTL) to join us for next meeting (7/19)
  • OOM still waiting on seed code, which applications may be impacted is still not clear.
  • Question: Who is responsible for packaging app to work with OOM - does OOM take care of it or are instructions provided to each app to ensure proper packaging.
• HA/Resiliency
  
  • Sharon has some suggestions for capabilities around resiliency that she would like to review with the team.
  • We will plan to focus part of next meeting on this. Sharon will provide a presentation on resiliency/clustering
• Other topics
  • Integration Testing with AAI & SDC - investigating to see what we can do locally
  • Areas of interest from the team? No feedback received.
  • Volunteer to start working on APPC-13 (replace openecomp with ONAP) - no volunteers yet
    
  • Update M1 template (Randa to update)
    • Update dependencies details
      • Add CDP-PAL support if MultiVIM is to be part of R1
    • Add risks
      • Carbon coming end of July, If SDNC runs into issues, could be later; the ODL docker is a fundamental dependency for APPC. 
  • SO & APPC interface
    • Questions received on workflow dependencies between SO and APPC. Response provided: Follow-up discussions will be scheduled as needed.
      

      • From an APPC perspective, it manages Layer 4-7 configuration and life cycle management. APPC exposes a REST API that is accessible via DMaaP and would support the SO adapter calling APPC for any of its workflow engines. The way APPC is architected, it’s model driven, so how the invoking entity is architected is transparent to APPC. APPC strives to be completely agnostic of the network and make no assumptions. The APPC behavior is identified in the model/information sent to APPC. From an APPC perspective, it does not matter who is the calling entity, but the preferred approach is to call  API via a message bus, not direct REST call.    APPC provides a DMaaP message bus library which is used by callers in ONAP if they choose to use DMaaP.    A similar library would be needed if a different message bus is used.

      • Paul Miller, one of our APPC architects gave a nice presentation on the model driven approach for APPC, which is recorded and may be of interest.

        https://wiki.onap.org/display/DW/APPC+Meeting+Minutes?preview=/6593568/8226046/APPC%20Model%20Driven%20Approach%20-%20PMiller%206-22-17.mp4

07/19/17 - APPC Project Weekly Minutes

Agenda:

• OOM discussion with David
• Sharon present information on resiliency and ODL clustering
• MultiVIM
• Generic restart code submission
  • Story APPC-88
• ODL
  • Re-confirmed with Dan Timoney that Carbon is planned for SDNC R1
  • Story APPC-?
• CSIT
• Documentation
• University - propose 2
• Upcoming milestones

Notes:

• OOM discussion with David
  • Question from previous meeting: Who is responsible for packaging app to work with OOM - does OOM take care of it or are instructions provided to each app to ensure proper packaging.
    • Answer: OOM wants each project team to create their own Kubernetes packages; however, for this first release, they will do it. 
  • For R1, scope for APPC is to deploy, upgrade using the 1 click API; however, don't anticipate any development needed on APPC side to support any activities planned for R1.
    
• Presentations from Sharon on APPC Resiliency and HA, plus OAM feature contributions (refer to Epic APPC-38)
  • APPC Resiliency - ONAP.pdf
  • APPC_OAM_Overview - ONAP.pdf
• MultiVIM
  • No big update; waiting on confirmation from CDP-PAL development team on resource availability to support R1 proposal for APPC & MultiVIM integration via proxy.
  • Ram Koya & Varun Gudisena primes for CDP-PAL
• LCM Generic Restart
  • Code submission in progress - APPC-88
  • This will provide the LCM VNF or VM restart capability needed for vCPE use case support.
• ODL Version
  • Re-confirmed with Dan Timoney that Carbon is planned for SDNC R1
  • APPC-91 created to track the work in APPC to update ODL versio
  • Per last conversation with Dan, the ODL docker will be available end of July (delays in this delivery add risk to APPC)
• CSIT
  • Creating a CSIT Test
  • Integration team would like each project to submit a test plan in a form of a docker that can be kicked off by Robot framework
  • Need to define the set of test cases that can be automated.
  • This list of test cases identified is needed for M2 (8/3/17)
• University
  
  • Propose 2 videos: Action: Discuss with Paul and Scott - add Epic & Stories
    • Create Model Driven Architecture training video - Propose Paul
    • Create APPC Overview training video - Propose Scott
• Documentation
  • Documentation Epic:  APPC-89
  • Stories to be added as we better understand what documentation updates are needed.
• SONAR
  • APPC-92 - Skip will start working on addressing current Blockers
  • https://sonar.onap.org/dashboard?id=org.openecomp.appc%3Aappc&did=1
• Labs
  • ETA on  Dev WindRiver lab to be provided by Thurs TSC per Helen during PTL call
    • This lab will be for dev to dev integration testing
    • Reference VNFs will be vFW and vDNS
    • Not sure if it will include vCPE
  • T-Lab - Spondon working on this, no ETA yet
  • Hector is working on standing up an internal ONAP lab, he need AAI credential information from AAI team; he is also working on issues with other components.
• Upcoming Milestones:
  • M2 = 8/3/17
  • What is due:

08/02/17 - APPC Project Weekly Minutes

Agenda:

• Review High Level Release Plan Proposal
• Discuss Story Pointing Approach
• Review List of Functional Test Cases
• MultiVIM update
• Review M2 checklist
• Communication (IRC)
• Labs
• Documentation
• Round Table

Notes:

• Release Plan - high level proposal reviewed with the team;
  
  • Sprint One: 8/1 - 8/16
    • Identify the functional test cases [APPC-105]
    • Restart LCM action [APPC-88]
    • Bug fix contribution [APPC-100]
    • Functional test case automation - part 1
      • Can we automate any during sprint 1?
    • SONAR blockers- Part 1
    • ODL upgrade???
      • Updated ETA from SDNC is now 8/4; so tentative at this point if this is Sprint 1 or 2
    • OAM Epic (APPC-38)
      
      • Action: Discuss with Sharon if some stories need to be in Sprint 2; 
  • Sprint Two: 8/17 - 8/31
    • AT&T feature contributions (epics: APPC-9, 22,12,10,11,53,57,62,63)
    • ODL upgrade ??
    • Functional test case automation - part 2
    • LCM API Doc upgrade
    • SONAR blockers/criticals - Part 2
  • Sprint Three: 9/1 - 9/14
    • MultiVIM integration testing
    • SONAR - blockers/critical - Part 3
    • Documentation updates (Epic APPC-89)
    • Release Notes
    • API Guide
    • User Guide
    • APPC Client Library Guide
  • Sprint Four: 9/15-9/29 - Hardening
    • University training recordings
      
      • Scott - APPC overview
      • Paul - APPC model driven
    • Defect fixes as needed
• Comments on release plan:
  • no major issues raised by team
    
  • question/concern raised on heavy loading of Sprint 2, but that is where the bulk of the code contribution from AT&T and AMDOCs is coming. We will need to see how we can mitigate this during Sprint 2.  Will explore to see If there are opportunities to get some of this in Sprint 1. 
  • JIRA APPC board currently reflect above plan for the most part: APPC JIRA Board
• Story Pointing Approach….
  • We did not get a chance to cover this topic, but my proposal is to use a simple story point method for R1 : 1 or 0
    • 1 means in-progress
    • 0 means it's done.
  • This method seems most reasonable for this release since many of the contribution are coming items being worked by various companies and being pushed to ONAP..
  • Reminders of JIRA good practices:
    • When you start to work a story or bug, move State to In-Progress.
    • When you deliver or close a story or bug, don't forget to update the Resolution field; i.e., don't leave it Unresolved!
      
• Review list of Test Cases (unit, functional, integration) - what can be automated, what can’t be automated; any we can undertake in Sprint 1
  • Story: https://jira.onap.org/browse/APPC-105
  • Wiki: https://wiki.onap.org/display/DW/Funtional+Test+Cases+for+Amsterdam+Release
    • Refer to above wiki for the list of functional test cases for automation.
      
  • What we commit to for automation, we will need to have 50% completed by 8/21
• MultiVIM discussion/priority
  • Discussion took place with CDP-PAL team
  • Identified list of actions that are needed by APPC
    
  • We prioritized list into Priority 1, 2, 3, priority 1 being what we need to support vCPE use case, however, we would also like priority 2.
  • Thanks to Scott Seabolt and Ryan Young, following list was provided to CDP-PAL team.
    • AppC_CDP_PAL_Multivim_Openstack_API_Mapping-v1.xlsx
  • CDP-PAL team to complete the mapping of CDP action to openstack action.
  • MultiVIM has requested changes from CDP-PAL by 8/20; hence, APPC has integration with MultiVIM in Sprint 3.
  • I have requested that integration to MultiVIM be transparent to APPC because I want fallback plan to be CDP-PAL without need to make code changes. All this is still under discussion.
    
• Review M2 checklist
  • https://wiki.onap.org/pages/viewpage.action?pageId=10783608

• Communication - IRC channel (#onap-appc)
  
  • https://www.irccloud.com/#!/ircs://chat.freenode.net:6697/%23onap-appc
  • Thank you Marcus for setting this up.
    
  • We will need to be able to communicate in real-time as testing kicks off in earnest, so this is important.
    
  • AT&T folks will need to request approval to unblock irccloud.com domain- I will share details, SLA is not quick…
• Labs
  
  • Marco Platania has a rackspace lab that is used to deploy new dockers on daily basis, so we will be running through some level of integration testing to make sure we are not breaking anything. We will not have access to do dev testing in this lab, but we may possible request some specific tests. Marco will reach out to APPC if he sees problems.
  • Additionally, Hector is working on his internal lab - making good progress.He was able to bring up a fully working (as far as passing healthchecks go) ONAP instance, We didn't get a chance to discuss this one, we can get more next week.
  •  Lab with vCPE? Still under discussion, no conclusion yet.
• Sonar
  • We have been given a target for unit test/code coverage for R1 - 30% - 50%
  • There is an issue with Sonar not reporting correct data (we were at 18%, but now shows 0%)
  • Ticket opened with LF Helpdesk (ONAP Helpdesk #43745), no response yet.
• R1 blockers
  
  • List was started as part of Virtual developers event - can be found here:
    
    • https://wiki.onap.org/display/DW/July+Virtual+Developers+Event+Blockers
  • I added dependency on ODL Docker from SDNC tean.
    
  • Do you have any other you want to add?
• OpenECOMP vs. ONAP renaming (APPC-13)
  
• This came up as a topic in PTL weekly call
• Making change from openecomp to onap has wide and extensive implications, cannot be accommodated in R1 without impacting other scope.
• Discussion being taken up by TSC - proposal is to identify plan in R1, execute in R2
• Waiting on guidance for this story.
  

08/09/17 - APPC Project Weekly Minutes

Agenda:

• APPC/CDP-PAL/MultiVIM- integration discussion
• Sprint 1 Status
• Documentation

Notes:

• Audio record of meeting: APPC Project Call recording 8-9-17.MP4
• APPC/CDP-PAL/MultiVIM integration discussion
• Primes:
• APPC - Ryan Young and Scott Seabolt
• CDP-PAL - Satish Addagada  and Tyler Smith
• MultiVIM - Xinhui Li  and Bin Yang
• Plan
  • CDP-PAL
    • In order to make expected 8/20 deadline, we will implement the following solution.
    • We will take in the following properties (actual values are subject to change, based upon discussion):

• Based upon those properties, we will route our API calls through the MultiVIM service url.

• • • APPC
      • Will require development to handle new URL format
    • MutlVIM
      • Already working on their keystone proxy
      • Additional information on MultiVIM plan can be found in attached slides:
        • ONAP_MultiCloud_API_July_31.pptx
    • R1 Priority
      • Support actions needed by APPC to support vCPE use case are a must. Identified as Priority 1 in attached file. Priority 2 items are needed to be able to validate other functionality offered by APPC, but not needed to support R1 use cases, but would like to have in R1 (mitigatiion plan is for APPC to be able to support both MultiVIM and CDP-PAL URL formats)
        • AppC_CDP_PAL_Multivim_Openstack_API_Mapping-v2.xlsx
    • Sync-up calls
      • Three sync-up calls will be setup in case we need to address technical questions that may arise:
        • Friday 8/11, Tuesday 8/15, and Thursday 8/17

• Assumptions
  • CDP-PAL
    • When invoking the authentication API call to MultiVIM’s identity url (passing in the openstack username, password, and identity service URL), we will get a token identical to the one we would normally receive from Openstack.

    • In order to access the Openstack provider API’s through the MultiVIM proxy, we need only replace the OpenStack service base url with the MultiVIM service base url. Furthermore, we expect the API response to be identical to what we would normally get if we had interacted directly with the Openstack Provider API.
      e.g. instead of https://OpenStackServiceURL/v2.0/login, we will use  https://MultiVimProxyServiceURL/v2.0/login.

  • MutliVIM
    • MultiVIM team is aligned with above assumption and is aligned with their plans
• Impacts
  • Development impacts for APPC, CDP-PAL, and MultiVIM teams
• Deadlines
  • All components will be code complete by 8/20 with goal of being able to start pairwise testing week of 8/21 pending availability of an environment
• • Testing- where?
    • Most likely environment for use is the WindRiver Dev2Dev lab being setup by Integration team.
    • Action: Randa to follow-up with Helen and Marco on readiness of this environment for testing start week of 8/21.
      • Update: CLOSED. See below: APPC Meeting Minutes
  • Open Issues:
    1. What version of OpenStack does APPC need?
       
       1. https://releases.openstack.org/
       2. VoLTE is using Mitaka, which is EOL, we probably want Newton or Ocata - neet to verify.
• Sprint 1 Status

• • Sprint One: 8/1 - 8/16
    • Identify the functional test cases [APPC-105]
      • This is done; A wiki page has also been added to track these test, plus individual JIRA issues to track automatio of each test case.
      • Looking for volunteers to take on these test case automation. Please let me know if you want to take one on.
        
    • Restart LCM action [APPC-88]
      • This done and available; looking for place to validate, talking with Marco Plantania and Dan Rose about using an internal lab that has latest dockers deployed. Working with them to get vFW VNFs deployed and populated in AAI.
        
    • Bug fix contribution [APPC-100]
      • This is done
        
    • Functional test case automation - part 1
      • Aaron has started working on one of them, but this will be part of Sprint 2, not 1 most likely.
        
      • Still looking for volunteers to work the other ones.
        
    • SONAR blockers- Part 1
      • We will do what we can in Sprint 1 bandwidth permitting.
      • We will create another story for Sprint 2 to make sure we continue focusing on this.
        
      • Need volunteers to look at issues.
        
    • ODL upgrade
      • This will move to Sprint 1.
      • Per Dan Timoney (PTL for CCSDK and SDNC), Carbon package slipped to this week.
      • Also, SDNC was refactored to move core functions into CCSDK, so we will have a bit more work to integrate Carbon ODL. This work is assigned to Patrick (APPC-91)
    • OAM Epic (APPC-38)
      • Will be submitted as part of Sprint 1. Stories moved to Sprint 1.
      • Action: Discuss with Sharon if some stories need to be in Sprint 2; 
        • Update: CLOSED. All stories linked to Epic APPC-38 will be submitted in Sprint 1
          

• Documentation
  • Working with Rich Bennett. He would like to use APPC release notes as the pilot project to demo their proposal for documentation using rst.
  • The idea is that documentation is handled like code, files managed in code repos, changes need to be submitted to Gerrit for reviewes, tools are use  for rendering, etc.
    
    

8/11/2017 - Feedback from discussion with the Integration Team

• Multi-VIM/APPC Testing – Helen will contact the Multi-VIM team to determine which lab is the most appropriated based on their needs
• Labs supported by the Integration Team - OpenStack Flavour: Mitaka & Newton
• The E2E Development Lab (WindRiver) is supporting Mitaka Openstack
• Chetan Doshi's team can get an access to the E2E Development lab but the latest APPC docker image should be available to install on the E2E Dev Lab (WindRiver).
  Sync-up with Marco/Dan is required when the APPC Docker image is available

08/11/17 - APPC/CDP-PAL/MultVIM - Touch Base 1

Participants: 

• RANDA MAHER <rx196w@us.att.com>; SEABOLT, SCOTT <js9808@att.com>; GUDISENA, VARUNESHWAR <vg411h@att.com>; NGUYEN, PHIL <pn8984@att.com>; Parviz Yegani <parviz.yegani@huawei.com>; Veer Rajasekhar <vr772b@us.att.com>; HU, BIN <bh526r@att.com>; YOUNG, RYAN J <ry303t@att.com>

Action Item:

• Confirm with MultiVIM team base url (Varun sent an email on this)

  • Please confirm the base url: base multicloud api call looks like : msb.onap.org:80/api/multicloud/v0/

Notes:

• Update on potential labs for testing provided above by Catherine
• CPD-PAL would like to confirm base URL
• APPC team wanted to confirm format of URL is as documented in slides

  • /namespace_root/multicloud/v0/v2.1/servers

  •  /namespace_root/multicloud/v0/v2.0/network

• APPC does not hard code or configure URL; it receives it in the request and must be able to parse it.
  • Today, this is the pattern matching it's dong and will need to update:

public class IdentityURL {
*
The regular expression pattern used to parse the URL. Capturing groups are used to identify and extract the
various component parts of the URL.

private static Pattern pattern = Pattern.compile("(\\p{Alnum}+)://([^/:]+)(?::([0-9]+))?/(v[0-9\\.]+)/?");

08/15/17 - APPC/CDP-PAL/MultiVIM - Touch Base 2

Participants:

• RANDA MAHER <rx196w@us.att.com>; HAY, AARON <ah415j@att.com>; TYLER SMITH <ts4124@us.att.com>; Marcus Williams <marcus.williams@intel.com>; SEABOLT, SCOTT <js9808@att.com>; GUDISENA, VARUNESHWAR <vg411h@att.com>; Veer Rajasekhar <vr772b@us.att.com>; ADDAGADA, SATISH <sa482b@att.com>; Bin Yang <bin.yang@windriver.com>; YOUNG, RYAN J <ry303t@att.com>; xinhui li <lxinhui@vmware.com>

Action Items

• Need to confirm URL for testing - Randa & Xinhui to follow-up with Helen
• Tyler will work on Priority 2 items for openstack mapping by Thrus., 8/17,
• Ryan and Tyler to discuss how to handle endpoints and come back with expectations/assumptions to get all aligned.
• Bin Yang to document all his questions/concerns and send in advance of this meeting so that we can discuss. There is an open action item on what exactly is getting populated in A&AI. APPC get URL from A&AI.

Action Items from last week:

• Confirm with MultiVIM team base url (Varun sent an email on this)
• Please confirm the base url: base multicloud api call looks like : msb.onap.org:80/api/multicloud/v0/
  • Status: CLOSED. Confirm by Xinhui
    • Re APPC - CDP PAL - MultiVIM Architecture Diagram.msg

Notes:

• APPC Story:  APPC-131 - Ryan working on this one…
• Tyler - coding change small, but testing is the larger scope- need to validate the various use cases
• Bin - there are a lot of other dependencies that need to be in place before we can integrate test with MultiVIM: ESR, A&AI - However, to validate flow from APPC/CDP-PAL to MultiVIM, we don't see a full blown end to end flow. Can we manually populate data in A&AI? AppC will look for URL for MultiVIM in A&AI
• APPC does not hard code URL, it expects to get it with the reqeust
• Need more clarification from MultiVIM team on plans to register with A&AI and what MSB has to do with plans - this was not clear. APPC assumption has always been that the full URL would be coming from A&AI or the incoming request; anything else would need to be reassessed if it can fit into R1 at this stage.

08/16/17 - APPC Project Weekly Minutes

Agenda:

• Wrap up Sprint 1 and start Sprint 2- pending items

• APPC-92 - move to Sprint 2 or close and open new one? Skip

• APPC-87 - why reopened - what's outstanding? Skip

• ODL upgrade - Patrick
• MultiVIM support - Ryan
• CSIT test cases - Aaron
• Documentation updates - Randa
• Upcoming milestone - M3 - 8/24
• Restart testing in ORD lab - Scott, Phil
• Anything else?
  • APPC-90 - Create story to track items we need to go back in clean-up from code review

Notes:

• Sprint 1 will close today;
  
  • APPC-87 okay to close.
  • APPC-92 will be closed and another story will be opened for Sprint 2 to continue working SONAR issues.
• ODL Carbon update (Epic APPC-158)
  
  • This work is in sprint 2;
  • Patrick working on this, changing references over to CCSDK, still having issues with build, some CCSDK items not ready.
  • Marcus will work wth Patrick. Marcus also workig on CCSDK project
• MultiVIM Support (Epic APPC-123)
  
  • Working with CDP-PAL and MultiVIM team.
  • Weekly touchbase meetings being held, working through requirements
  • Next touchbase planned for Thur, 8/17, at 9AM EST
  • Environment for validation will be the WindRiver lab - see below for update from Catherine.

8/16/2017 - Feedback from discussion with the Integration Team

• • • vCPE will be validated on the WindRiver lab while vVolte will be validated in the China Mobile lab
    • Helen will send an e-mail later this week on this topic

• CSIT (APPC-104)
  
  • Working on local environment so that we can validate the test cases using Robot framwork.
  • This continues to be a work in progress; we are supposed to have 50% of planned TC done by M3, but not sure we will hit that
• Documentaton (APPC-89)
  • Paul Miller will update the API Guide for R1/M3 (APPC-102)
  • Documentation project planning a meeting next week, we will find out more about what they recommend, but we need to keep moving ahead with our updates for M3.
• Restart Testing in internal ORD instance
  
  • Have not been able to successfully test restart, still have not been able to get AAI data populated; however, error we are getting suggests that current deployment may not have pick up our code.
  • Action: Patrick to check lab to ensure we have version with code deployed
• Sonar
  • Reporting 0% Unit test coverage - needs investigation why this is reporting incorrect data
  • Action: Marcus and Skip will look into this.
    • Update: Closed. Fixed by Marcus!
      
      • Sonar coverage appears to be back with a slight change to pom.xml that matched jacoco unit test path with oparent pom.xml unit test path (https://urldefense.proofpoint.com/v2/url?u=http-3A__gerrit.onap.org_r_7757&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=kyPZ229JImvwwKH-78nlyg&m=-zpq3Po14MTM-9CVzVfQuXhzAlrXi1D2k616zDRIyW4&s=UccqX1QmANEt45HvDMNqH1JyEu_ykLvgphxFOyBPTv4&e= 
• Tracking deferred Gerrit comments
  • Story APPC-157 opened to track these items for completion.
• Integration Testing
  • Catherine is working with Helen Chen from Integration team to create a JIRA dashboard to track Integration issues
  • Convention to flag issues openend by Integration Team
    • Label will be used to identify issue are originated by Integration Team
    • Affects Version = Amsterdam Release

08/18/17 - APPC/CDP-PAL/MultiVIM - Touch Base 3

Participants:

RANDA MAHER rx196w@us.att.com, Chenfei Gao cgao@research.att.com, Ryan Young ry303t@att.com, Scott Seabolt js9808@att.com, Bin Yang bin.yang@windriver.com, TYLER SMITH ts4124@us.att.com, Ethan Lynn ethanlynnl@vmware.com, Joseph Chou jc2555@att.com, Pamela Dragosh pdragosh@research.att.com, BECKY L HOTZE bk2371@att.com, Bin Hu bh526r@att.com, ram bagadi rb341d@att.com, Skip Wonnell skip@att.com, Phil Nguyen pn8984@att.com, AARON HAY ah415j@att.com, varun gudisena vg411h@att.com, xinhui li lxinhui@vmware.com, Hector Anapan ha076r@att.com

Meeting Recording:

MultiIVIM Meeting 8-18-17- Touchbase3.mp4

Action Items:

• Randa to setup a call with Policy and CLAMP to clarify what APPC will be as part of the closed loop in support of vCPE use case
• Ryan will investigate what additional work would be required if Policy passed the VNFID only and not the full identify URL
• Bing Yang will investigate if MultiVIM can support https
• Tyler will investigate if CDP-PAL can support http
• MultiVIM team still needs to finalize storage of identity-url into AAI - discussion going on with ESR and VID team. 

Conclusion from discussion:

• The full url will be stored in AAI as part of the identity-url, as shown below:

• For username & password, APPC stores the credential locally in a properties file and these are passed to OpenStack to authenticate. For R1, this will remain the same. APPC will make no changes to this existing functionality.
• Ethan indicated that credential would be stored in AAI as part of cloud region, put there by ESR as part of VM info; however, for R1, APPC will not extract username/password from AAI. Implication for testing is that these credentials in properties file must match what is stored in AAI for that cloud instance. 
• Note that APPC only has 1 set of credential for all cloud instance today.

Additional Notes:

• APPC/CDP-PAL use HTTPS; need MultiVIM to investigate if they can support HTTPS. Tyler will do likewise to see if HTTP can be supported by CDP-PAL.
• MutliVIM team is still in discussions on identify-url and how it will get into AAI
• Question from Policy - does Policy need to send the full url or can APPC look it up based on VNF ID and retrieve it from AAI instead of having it passed in request? Ryan to look into what it would take to retrieve the url.

Action Items from last week:

• Need to confirm URL for testing - Randa & Xinhui to follow-up with Helen
  • Status: Pending   Waiting on details to be provided by Helen
• Tyler will work on Priority 2 items for openstack mapping by Thurs., 8/17.
  • Status:  Pending, new ETA 8/21/
• Ryan and Tyler to discuss how to handle endpoints and come back with expectations/assumptions to get all aligned
  • Status: CLOSED - CDP) was under the impression that they would have to manage a different authentication mechanism with VIM; however,  from today's meeting with MultiVIM team,  the confirmed  that the identity url in A&AI would be the same as if were the OpenStack identity. This means that MultiVIM proxy responds identically as OpenStack, so no changes to CDP-PAL.
• Bin Yang to document all his questions/concerns and send in advance of this meeting so that we can discuss. There is an open action item on what exactly is getting populated in A&AI. APPC get URL from A&AI.
  • Status: CLOSED. Were part of items discussed in 8/18 meeting.

Anchor
08/22/17 - ONAP Architecture Subcommittee APPC Interfaces and Restart Flow 08/22/17 - ONAP Architecture Subcommittee APPC Interfaces and Restart Flow

08/22/17 - ONAP Architecture Subcommittee APPC Interfaces and Restart Flow

• Scott Seabolt - APPC Interfaces and R1 Restart Flow

08/23/17 - APPC Project Weekly Minutes

Agenda

• M3 status (Randa)
• ODL upgrade (Patrick)
• MultiVIM integration status (Ryan & Tyler)
• Code contributions (Skip)
• Documentation status (Randa & Scott)
• CSIT (Aaron)
• SONAR coverage
• Testing (Hector)
• Anything else?

Meeting Recording: 8-23-17 APPC Weekly Project Meeting.mp4

Notes:

• EPA (Extended Platform Awareness)
  • Alex requested time to go through EPA project with team to do some brainstorming on what is possible/not possible on what is being proposed
  • Would like to do it before Sep 25-28 F2F meetings
  • Will target 9/13/17 for this discussion.
• M3 Status
  • All items ready with exception of following:
    • CSIT not at 50%
    • Sonar coverage not at 30%
    • Updated API Doc will be posted end of week
    • Refer to M3 checklist
• ODL Upgrade - APPC-158
  • Issues for new ODL dependencies fixed
  • Now testing with new docker image from ccsdk,
  • Project is compiling with new ODL and new CCSDK and test passing, now just need to get new docker image to work.
  • On-track for Sprint 2 (ends 8/30)
• MultiVIM Integration status
  • APPC (Ryan)
    • Meeting held with Policy team - decision that policy will only pass VNFID, APPC will do the look-up for identify URL
    • Meeting held with AAI to get details on API changes - see AAI API VIM Definitions
    • Main work left right now is to determine where the AAI calls wll actually be made from - looking at a couple of places, possible updates to DGs..
    • On-track for Sprint 2 (ends 8/30)
  • CDP-PAL (Tyler)
    • Typler confirmed that CDP-PAL can support either https or http
    • Based on latest changes on APPC, there  may not be any development work for CDP-PAL.
  • Dev (WindRiver) Lab access
    • No update from Helen and she's on vacation this week.
  • Risk - APPC and CDP-PAL can have code ready, but there is no lab yet for integration/pairwise testing.
• Code Contribution Status
  • All code contributed with the exception of the GUI for the Configuration Design Tool (CDT)
  • GUI may be more than 10K lines, having to break it up just to stay under this limit may present problems so we will submit all the code to avoid any delays.
  • Need to go through JIRA stories to ensure they are all updated as applicable.
• Documentation Status
  • Documentation team planning meeting with all PTLs on 8/24
    
    • http://onap.readthedocs.io/en/latest/
    • http://docutils.sourceforge.net/rst.html
  • API Guide - updated draft available; will be posted to wiki in doc format for now as we continue work to convest to rst and submit to git.
    
  • Client Library Guide - draft available, will be posted to wiki in doc format for now as we continue work to convest to rst and submit to git.
  • CDT tool documentation - pending…
  • User Guide update - pending - Randa will setup a call to review this document to see what changes we want to make.
    
  • Release Notes - pending.
• CSIT
  • Healthcheck test case submitted by Aaron - Covers APPC-111
    
  • Patrick will take a closer look at APPC-112 to see if covered by work Aaron did with Healthcheck (APPC-111)
  • Phil will work on APPC-113, APPC-119, APPC-120
  • Aaron will continue working on APPC-115 and APPC-116
    
  • Next?
• SONAR
  • test coverage - only at 13.4% overall, need to improve - see here
    • Randa to setup a call to strategize on increasing coverage.
  • Blockes.. need volunteers to work these...
    • From a process perspective if you work on Sonar issues
      
      • Assign issue to yourself in Sonar if you are going to work on, also
      • Create a task under story to track the submission.(APPC-156).
      • Skip indicated they are working on the "Catch Exception instead of Throwable", which should reduce numbers quite a bit.
• Testing
  • Hector working on his internal lab, trying to test LCM Restart, but blocked by APPC-169. Also partnering with Ashwin on APPC to AAI integration.
  • ORD environment also blocked by APPC-169 and AAI data - reached out to SO team for support.
• Anything else?
  • APPC setup script - provided as part of work submitted by Aaron under APPC-111

08/30/17 - APPC Project Weekly Minutes

Agenda:

• vFW  close loop regression - how will this be supported (Paul, Patrick, Chenfei)
• ODL upgrade status  (Patrick)
• APPC changes to support MultiVIM integration status (Ryan)
• APPC Client Library merge status (Skip)
• CSIT Status (Aaron, Patrick, Phil)
• Documentation Update (Scott)
• Closing Sprint 2
• Sprint 3 (9/1 - 9/15)
• Misc

Meeting Recording: 8-30-17 APPC Weekly Project Meeting.mp4

Notes:

• vFW  close loop regression - how will this be supported (Paul, Patrick, Chenfai)
  • No change needed if using R0 approach
  • The request sent today for closed loop is not doing anything actually on the vFW, it is doing it on the traffic generator, but that doesn't matter, traffic generator can mount; there is no process in the LCM flow to do exactly what they are doing, that is to delete the existing config and apply a new one.  There are 2 options
    • Option 1 - call the same legacy API and DG;
    • Option 2 - make it work through LCM API itself, we have an approach we have used in the patch that we've used for OpenStack action, which allow caller to invoke the LCM API with a version number, but we would end up invoke the existing DG.
    • Option 1 would not require any additional effort, we just use what is currently there for legacy APIs; Option 2 would require some work, no code changes, but records to tables would be needed.
    • Giving where we are in the release cycle and the work yet to complete, decision is to go with Option 1.  Patrick confirmed that DG is still there.

• ODL status update (Patrick)
  • In-Progress; working through some failures; sli features is not coming up; hard to tell if issue is on CCSDK side or APPC side since code is so closely coupled.
  • Patrick will open defect to CCSDK as needed
  • Will work with Marcus since he is also on CCSDK project.

• APPC changes to support MultiVIM integration (Ryan)
  • Pushing out initial changes today for IaaS adapter [APPC-131]
  • APPC-185 - added to include some DG changes for getting AAI info we need to pull for identity url
  • As far as we can tell, there are no CDP-PAL changes at this stage unless testing reveals anything different
  • Biggest change is for APPC getting Identity url from aai and ensure backwards compatibility with CDP-PAL to OpenStack.
  • MultiVIM looks like is only supporting Priority 1 actions and we need to be able to validate the other actions. Don't want to be limited by what MultiVIM can support.
• APPC Client Library update (Skip)
  • Ported to Gerrit (APPC-180)

• CSIT Status (Aaron, Patrick, Phil)
  • Core set
    • Aaron: APPC-115 and APPC-116 done; Current view reflected on the wiki
    • Need to look at the test case implemented to check bundle count; it would require updates if bundles are added/removed.  Can this be done dynamically.
      • Sli APIs are being used for basic healthcheck, not the OAM Get Status API.
      • Phil: Working assigned test cases, but needs the port numbers.
      • ODL check - APPC-111 - if bundles are up and running, then that's a good indicator that OpenDaylight is running.
      • Action: Randa will setup a separate call to discuss ports usage since we need to document this in release notes or deployment guide
        • 9/12/17 - CLOSED - will be documented as part of release notes.
      • Action: Need to review the approach to check health status of APPC to be consistent with the business logic being implemented (i.e, OAM feature). Possible work for R2 since API may need to be updated.
  • Stretch
    
    • LCM restart (VM & VNF level) - Phil currently testing. Randa to create Story

• Documentation Update (Scott)
  • API Guide has been converted to rst format and should be submitted to GIT today/tomorrow
  • APPC Client guide is close and should also be going; need to update location of client library in ONAP.
  • APPC User Guide - meeting will be scheduled to discuss what updates we want to make to this document.

• Closing Sprint 2
  
  • Review list of remaining epic/stories with Skip & Mark - need confirmation if all contributions were make. Randa will setup a call to discuss.
  • Noticed issue with missing tables   For example:
• APPC-75 -Story -
• APPC-155 - bug

• • Hector recommends that all tables be included in the deployment repo.  From email sent,
    • Here are the steps to take to add a database in the ONAP MySQL and add tables using the APPC Docker Image’s deployment scripts: [this addresses new tables, we need to also handle changed table]

• • • • ADD DATABASE (in [appc/deployment.git] / installation / appc / src / main / scripts / installAppcDb.sh) – This script is where all database creations and its permissions should go under. 
      • ADD TABLES (in [appc/deployment.git] / installation / appc / src / main / resources / appcctl.dump) – This file is where all table creations should go under when the tables are in the appcctl database (already created). Currently, appcctl.dump has the definition to create the transactions table.
• Sprint 3 - focus
  • Documentation
  • Finish CSIT
  • Complete items pushed out from Sprint 2
  • SONAR junit Coverage
  • SONAR Blockers
• Testing
  • Lab access  - POD-14
    • Scott was able to VPN and access Horizon console; should have what we need, but need to verify that we can log into the VMs
    • MultiVIM team also requested access to this lab.
    • Not quite certain what’s there yet. Helen indicated that this lab is only being updated weekly, they are not yet in a position to do daily updates.

• Misc
  • New License text changes, so we will see some churn
  • Mysql-connector-java under GPL2.0 - per Phil Robb and Steve Winslow would probably be a blocker for R1  - detected by Nexus IQ Server scan
    • Update: This is covered by following FOSS Exception, should not be a blocker for R1.
      
      • https://www.mysql.com/about/legal/licensing/foss-exception/

09/06/17 - APPC Project Weekly Minutes

Agenda:

• APPC, MutliVIM, AAI/ESR integration testing
• APPC changes to support MultiVIM status
• ODL Carbon upgrade status
• CSIT status
• Sprint 2 closure
• Sprint 3
• Sonar update

Meeting Recording: 9-06-17 APPC Weekly Project Call.mp4

Participants: Bin Hu, Gil Hellmann, Hector Anapan, Jimmy Forsyth, Lionel Goarzin, Lizi, Patrick Brady, Phil Nguyen, Ryan Young, Veer Rajasekhar, Adolfo, Bin Yang, Ethan Lynn, Gildas Lanilis, Honghui Xiao, Keliang, Mark Runnels, Martial Gervais, Rahul Sharma, Skip Wonnell, Gordon Warrack, Scott Seabolt, Aaron Hay, Randa Maher

Action Items:

• Randa: Follow-up with DMaaP team to see if they are ready for integration testing.
  • Update 9-7-17: From Varun Gudisena, "We have the working DMaaP Message Router docker image ready. I will send specs tomorrow"
• Stephen or Gil: Provide more details on the POD-25 lab
  • Update 9-13-17: Details sent to primes listed on pairwise testing wiki.
• Phil: Provide documentation of some test cases that they run internally to see if we can run these in POD-25.
  • Update 9-13-17: List provided, needs to be reviewed to see what can be done in POD-25.

Notes:

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

09/13/17 - APPC Project Weekly Minutes

Agenda:

• POD-25 lab access/details (Gil, Stephen)
• APPC DG changes to retrieve identify URL (Ryan)
• CSIT Jenkins Jobs (Aaron)
• DMaaP integration testing (Varun, Phil, Ryan)
• Test Cases for pairwise testing
• Review outstanding items from Sprint 3
• Sprint 4
• Documentation update
• Misc
  • EPA discussion - 9/15/17 at 12PMEST

Meeting Recording: 9-13-17 APPC Weekly Project Call.mp4

09/15/17 - EPA Presentation by Alex Vul

Meeting Recording: EPA Presentation by Alex Vul 9-15-17.mp4

09/20/17 - APPC Project Weekly Minutes

Agenda:

• POD-25 deployment (Aaron, Bin)
• Build stability & Key issues (All)
• AAI DG changes for MultiVIM integration (Ryan)
• CSIT (Aaron, Phil)
• Test Cases for Pairwise testing
• Documentation (Scott)
• M4 Checklist review
• F2F next week
• Other topics?

10/04/17 - APPC Project Weekly Minutes

Agenda:

• Pairwise testing - outstanding items (Bin, Jimmy, Scott)
• DMaaP integration  (Dominic, Varun)
• CSIT (Phil)
• Documentation (Scott, Randa, Hector)
• Defects

Meeting Recording: 10-04-17 - APPC Weekly Project Call.mp4

Notes:

• Pairwise testing
  
  • Outstanding items (Bin, Jimmy, Scott)
    • AAI data for VNFs
      • Jimmy got vnf data provided by Scott & Ryan loaded today, next step is for APPC to verify now with APPC to see if all is in place; however, note that data given to jimmy does not include MultiVim url, only OpenStack. Data will need to be updated once MultiVIM info is available.
    • AAI data for MultiVIM
      • Bin was able to populate info into AAI, put VIM end point into cloud region - needs to verify first, will let team know when done with validation
        
    • For now, Ryna and Scott can validate that flow works through APPC without MultiVIM - going directly to OpenStack;  Will update and re-run flows via MultiVIM when ready.
    • AAI backup -
      • Once we validate the objects we want, Jimmy will set it up to be populate with each deployment.
• DMaaP integration (Varun, Dominic)
  • Know issues in WindRiver lab and waiting for their IT dept to address (OPENLABS-62) - not ETA at this point.
  • Team has been working on a workaround, but can't guarantee that it will always work.
• CSIT (Phil)
  • 4 of 11 CSIT added are currently failing due to Carbon differences in apidoc explorer.
  • Phil hopes to have a solution sometime today.
• Integration testing…schedule for Amsterdam
• https://wiki.onap.org/display/DW/Integration+Testing+Schedule+for+Amsterdam+Release - Integration team posting schedule/plans on this wiki
• We will need to provide support when APPC issues comes up; we want to complete our pairwise testing asap to get ahead of this
  
• Documentation (http://onap.readthedocs.io/en/latest/release/index.html)
  • API Guide (Scott, Randa)
    • Formatting issues - will submit once technical issues with his local environment are resolved
    • Randa to review for additional updates that need to be made
  • User Guide (Randa) - not started yet
    
  • Deployment documentation (Hector) - one remaining item to be added on how to add DGs using existing code
    
• Defects
  • APPC Defect Board
    
• Sprint 5 - ends 10/13
• License items:
  • Following up with LF to determine if references to mysql-connector need to be removed from seed code (1.0.0)
  • Need to remove powermock-module-javaagent-1.6.5.jar since it's GPL2.0 license (APPC-258)
    

10/11/17 - APPC Project Weekly Minutes

Agenda:

• Pairwise testing (Ryan, Scott)
• Integration testing support (Scott, Ryan, Patrick)
  • vCPE
  • vFW
• CSIT (Phil)
• Documentation (Randa, Hector, Patrick)
• RC0 milestone
• Defects

Notes:

• Pairwise and integration testing taking place in-parallel, members are trying to support both activities.
  • Ryan trying to complete pairwise testing in Dev Pod-25 instance
  • Scott, Ryan, Patrick, Hector, Veer, Aaron supporting vFW integration testing being led by Helen
  • Scott, Ryan, Patrick, Veer, Aaron supporting vCPE integration testing being led by Kang. 
• POD-25 lab is not stable; testing taking longer than anticipated due to lab and access issues with environment
• Key APPC issue needed to un-blocked APPC testing, APPC-259, has been submitted. New issue being investigated: APPC-268.
• Pairwise test cases still to be executed in Dev Pairwise POD-25 instance: (Phil)
  
  • INT-205 - LCM API Healthcheck
  • INT-206 - LCM API VM Restart
  • INT-207 - LCM API VNR Restart (covered by Ryan's testing)
  • INT-208 - LCM API Start
  • INT-209 - LCM API Stop
  • INT-210 - LAMCT API VM Rebuild
• CSIT tests - failing tests now passing.
• Documentation
  • Patrick and Hector working to add more details about APPC properties files to readthedoc under APPC Property section added by Hector
  • We will add a Logging section to readthedoc here. This information is currently buried in the User Guide document. It will be extracted, converted to rst format and put on readthedoc.
  • Randa still working on User Guide, extracting the architecture information to be added to readthedocs under Architecture section here.
  • Platform Component documentation template requests that all component projects provide documentation in the following categories:
    
    • Platform component documentation
      • Architecture
      • Offered APIs
      • Consumed APIs
      • Delivery
      • Logging
      • Installation
      • Configuration
      • Release Notes
• RC0 - we are in good shape, got our CSIT all passing, but still have some High/Highest issues to resolve.
• Defects
  • This is a dynamic list as pairwise and integration testing progresses.
  • APPC issues tracked on the APPC Defect Dashboard:
• Lesson Learned
  • If anyone would like to contribute input, please send them to me and I will roll-up.
  • Catherine Lefevre sent a request for input.
  • Please send your input to see where we have opportunities for improvement and what things we may want to continue doing if they worked well.

• Remaining milestones for the Amsterdam Release

10/25/17 - APPC Project Weekly Minutes

Agenda:

• Sprint 6 pending items
• RC1
• Documentation
• Release branching - will do it by RC2
• Testing
  • Blocking issues:
    • CDP-PAL issue - APPC-285
    • MultiCloud issue - MULTICLOUD-119
  • Testing progress
    • vCPE
    • Pairwise (POD-25 - .80 lab)
• Working session…

Notes:

• Sprint 6 pending items - sprint closes on 10/27
  
  • See list from RC1below
    
• RC1
  • Failing jenkins javadocs job that needs to be fixed  (APPC-266)
  • Pending CCSDK fix
  • Sev 1 issue (APPC-285)
    • CDP-PAL changes being tracked under this APPC ticket.
      
• Documentation
  • Logging section added to readthedocs
  • APPC User Guide, which includes Architecture section added to readthedocs
  • Will be added some documentation on OAM APIs on readthedocs.
  • Release notes still pending.
    
• Release branching - will do it by RC2
• Testing
  • Blocking issues:
    • CDP-PAL issue - APPC-285
    • MultiCloud issue - MULTICLOUD-119
  • Testing progress
    • vCPE
    • Pairwise (POD-25 - .80 lab)
• Working session...

11/08/17 - APPC Project Weekly Minutes

Agenda:

• Wrapping up Amsterdam Release
• Only Highest/High defect priority bug fixes directly related to the use cases are allowed
• Creating release version (v1.2.0) - dependency on CCSDK to complete
• Release branching  (decision to be made at TSC meeting this Thurs)
• Testing details
• APPC Testing Scope and Status
• Quick Review wiki pages being added by Scott…
  • APPC ONAP Testing Notes
• Documentation
• Release Notes: http://onap.readthedocs.io/en/latest/submodules/appc.git/docs/release-notes.html
• Please review and provided input if any
• RC2 checklist
• https://wiki.onap.org/pages/viewpage.action?pageId=16005492
• Other Lose ends…
1. Last test case, WBN, not critical for Amsterdam.
2. Update INT-181 test results

1. Jira Legacy
   server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key INT-206

     - VM restart ?

• Priority once Amsterdam branch is created

11/22/17 - APPC Project Weekly Minutes

Agenda:

• A new amsterdam branch has been created.
  • Beijing changes can now go into master.
    
  • Patrick has already started merging changes into the master.
    

• Jira Legacy
  server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key INT-206

  needs to be validated and documented.
• Package naming will be changing.
  • Due to limitations in Gerrit line count is showing a very large number than was actually changed.
  • Need to strategize with Randa on what the best practices are for handling this scenario.
    

11/29/17 - APPC Project Weekly Minutes

c

• Jira Legacy
  server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key INT-206

  needs to be validated and documented (Scott Seabolt).
  • The team is working to close this test out 11/29/2017.
• The vFirewall project had a question around using REST to create the Netconf mount instead of the demo.sh script via Robot (Team).
  • The "PUT" command and xml are outlined here.
  • Alternatively, the procedure using a curl command and xml body are outline here.
• APPC HealthCheck is failing with the latest Jenkins Staging image (Patrick Brady).
  • Appears to be due to oparent missing in the latest CCSDK package.
    • Patrick is in touch with Dam Timoney with CCSDK.
• ONAP Branching Status email (Taka Cho/Patrick Brady)
• What does the APPC team expect from the next ONAP meeting occuring in two weeks?

Notes:

• INT-206
  • To complete today using MultiCloud instead of going direct to OpenStack.
    
• vFirewall
  • Using REST to create the Netconf mount can easily be done either via Postman or via CURL.  Samples of both are above in the agenda.
    
• APPC Healthcheck
  • Appears to be due to oparent missing in the latest CCSDK package.
  • Patrick is in touch with Dam Timoney with CCSDK.
    • Looks like oparent released the wrong version.  Dan is working to get this issue fixed. 
      
      • Currently all builds are failing due to this issue.
        
• ONAP Branching Status
  • There is one more merged project that needs to be implemented.
  • Patrick made two properties that determine which is used for snapshot and which is the release
    • Changes are done but due to the oparent (CCSDK) issue the builds are failing.
      
• Beijing meeting in two weeks
  • AAF integration:
    • Investigating how APPC handles AAF and making improvements.
    • Currently jars have to be modified.
    • Possibly put a security handler on higher level Jetty instead.
    • Would this change be on AAF or APPC, preferably on AAF so it's more of a global in how apps handle.
  • Change from org.openecomp to org.onap.
  • MultiCloud Integration.
    • What will the architecture be for Beijing?  APPC→CDP-PAL→MultiCloud or APPC→MultiCloud.
    • Possibly create an IaaS service where APPC could plugin to MultiCloud or CDP-PAL.
      • I.e. make it a pluggable architecture.
  • Change APPC to use the OSGI Config admin instead or using property files (Stretch Goal).
    • Allows for a more dynamic configuration.

12/06/17 - APPC Project Weekly Minutes

Agenda:

• Preliminary view of scope for Beijing
• APPC Beijing contributors?
• Upcoming releases - reivew key dates
• JIRA Management
• Key changes with Beijing
• Vacations in Dec/Meeting plans
• CSIT for R1 and R2

Participants: Randa Maher, Former user (Deleted), Aaron Hay, Patrick Brady, ry303t, Scott Seabolt, Skip Wonnell, Takamune Cho, Parviz Yegani, Shubhada Vaze, Veer Rajasekar

Action Items:

• Randa Maher & team: Review architecture diagram for R2 and ensure accurate for APPC.
• Randa Maher & team: Review Enterprise vCPE UC for impact to APPC

Notes:

• 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: 
  • https://wiki.onap.org/display/DW/Projects+for+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
  • Need to confirm input provided for HA config: https://wiki.onap.org/pages/editpage.action?pageId=16010535
• 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, ry303t, 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.
  • 1/10/18 Update: This action item is closed. The CDT tool creates models that are specific to APPC and are needed for the self-service.  CDT is an APPC tool.

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
  • Focus on Beijing is on maturity and multiplier features (i.e., functionality that have general applicabilit across components)
  • Use Case Committee presented the various use cases that were reviewed and from which general functional requirements were derived.
    • Link to the presentation made: https://wiki.onap.org/display/DW/Beijing+Functional+Requirements+for+TSC+Approval
• Carrier Grade Requirements..
  • Levels mentioned at last meeting are documented here:Platform Maturity Requirements (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 Legacy
    server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key APPC-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

Participants:  Patrick Brady, ry303t, Scott Seabolt,  Takamune 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!!

01/10/18 - APPC Project Weekly Minutes

Agenda:

• Review Beijing timeline
• Review Beijing resources
• Review scope
• Misc disc

Participants: Randa Maher, Aaron Hay, Patrick Brady, Skip Wonnell, Shubhada Vaze, Takamune Cho, Linda Horn, Veer Rajasekar, Tomasz Kaminski

Notes:

• Review Beijing Milestones again
  
  • 1/8 - Project Planning closure
  • M1 - 1/18 - M1 review
    • Materials for M1:
      • Release Planning Template:
      • Release Planning Checklist: To be filled out by Jan 17
  • M2 - Functionality Freeze -  2/12
    • no new visible functionality is to be added to the current ONAP release
    • Each Project team has defined and documented their Functional Test Cases
    • A stable document describing the API is documented and available in wiki.
  • M3 - API Freeze - 3/8
    • Mark the end of API and Data Model change. API and Data Model are now Frozen
    • 50% of Functional Test Case are automated.
  • M4 - Code Freeze - 3/29  - 4/5/18 
    • Mark the end of the Features coding
    • 100% of Functional Test Case are automated
  • RC0 - Integration - 4/19
  • RC1
  • RC2
  • Release Delivery - 5/24 - Signoff

• Review Current Dev resources
  • Patrick Brady (Committer) - Dev/test - 100%
  • Skip Wonnell (Committer) - Dev/test - what %?
  • Marcus Williams (Committer)  % ? awaiting feedback
  • ry303t - Dev/tes - 100%
  • Takamune Cho - Dev/test - 100%
  • Former user (Deleted) - Dev/test - 50%
  • Shubhada Vaze - Dev/test - 70-100%
  • Aaron Hay (test/csit/deployment pairwise lab) - 100%
  • Hector Anapan-Lavalle (test/deployment documentation) -  ?
  • Paul Miller  (architect) -
  • Scott Seabolt (architect/doc support)
• Review Scope
  • Remove references and use of openecomp and replace  with onap  APPC-13 - In progress
    • Action: Need to follow-up with Michael Lando on his concern….
  • Platform Maturity (or S3P)
    • Performance - cannot commit anything at this point; too many questions and ambigiuty on what needs to be done. Awaiting input from Benchmarking committee
    • Stability - 1 - 72 hours soak test on component level.
    • Resiliency - this item needs clarification - is 1 for local or geo-red manual failover? Regardless, we will align with CCSDK/SNDC since we get our ODL & DB dockers from them. We will work with SDNC team.
    • Security = 1  - CII Passing badge + 50% Test Coverag
    • Scalability -1 -  APPC uses ODL distribution from CCSDK project. Scaling is a function of ODL capabilities - adding nodes to an existing cluster or adding a new cluster
    • Manageability - 1- APPC supports EELF already.
    • Usability - 1

• • Support AAF (Authentication and Authorization Framework) for API access
    • Dependency on AAF project to provide feature (AAF-91) to enable AAF security on the web server level (jetty level). AAF confirmed they will deliver AAF-91 in Beijing.
      

• • Upgrade ODL version to Nitrogen (driven by CCSDK dependency)
  • Replace MySQL with MariaDB (driven by CCSDK dependency)
  • Increase Code Coverage to 50%
  • Provide support for the following new LCM actions:

• Following Actions in support of In-place software upgrade
  • QuiesceTraffic
  • ResumeTraffic
  • UpgradeSoftware
  • UpgradePreCheck
  • UpgradePostCheck
  • UpgradeBackup
  • UpgradeBackout
• Additional LCM actions including:
  • ActionCancel
  • ActionStatus
  • AttachVolume
  • DetachVolume

• • 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, ry303t, 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. (Closed - APPC-418)
• Patrick Brady to request new repo for CDT tool - appc/cdt (Closed)

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 Clustering.pdf
  • 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)
  • A small sub-team has already had a couple of meetings to flesh out the things that will be needed to execute a 72 hour soak test
  • Details are being trakc on the wiki: APPC 72 Hour Stability Test Discussion
  • Epic is APPC-413
    
• 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: How-To's and other helpful information
  • 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
  • ry303t 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.
  • ry303t 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
  • APPC-405 will be worked on by Taka with the goal in the first sprint to review all the questions that are part of the Passing Badge questionniaire and determine what our gaps are.
  • Use the CLAMP completed questionnaire as a guide to review the questions: https://bestpractices.coreinfrastructure.org/projects/1197#basics
• Review JIRA - housekeeping items
  • We did not get to this topic, we will cover next meeting....
    
• Misc - FOSS & Commit Process
  • Please make sure to review or re-review these two links to make sure you are clear on the FOSS and Commit processes.
    
    • Copyrights and License Declarations
    • Project FOSS
    • Commit Messages
• 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. 
    
    

01/24/18 - APPC Project Weekly Minutes

Agenda:

• M1 update
• AAF update (Sai)
  
• Sprint 1 planning/commitment (run 1/24-2/7)
  
• Review JIRA workflow used by APPC
  
• Misc updates (new repo request, License issue)

Participants: Randa Maher Former user (Deleted), James MacNider, Patrick Brady, ry303t, Scott Seabolt, Sai Gandham, Shubhada Vaze, Takamune Cho

Actions:

• Sai Gandham to schedule meeting with APPC team to review his design plans for AAF-91.
• Skip Wonnell to investigate missing action action-cancel from LCM Provider

Notes:

• M1 update
  • APPC passed M1 on 1/18 with no issues. Manual Scaleout support included.
  • Two new folks added to the project to support Manual Scale out (Ramya and Vidhya)
• AAF update on AAF-91 (Sai)
  • Sai has already started working on this.
    
  • 2/15 is target delivery date!
    
• Sprint 1 planning/commitment (runs 1/24/18 thru 2/7/18) - AppC JIRA Board
  
  • Resiliency (Aaron)
    • Aaron got the 10 additional VM in the WindRiver dev lab
    • He will focus on getting a local environment setup in WindRiver in first sprint (APPC-455) in additional to working on Resiliency items (APPC-475).
      
  • Stability (Scott)
    • See APPC-484
      
  • Manual Scale (Ramya, Vidhya)
    • Requirements discussion progressing
    • Need to determine what can be completed in first sprint; to defined by end of week. Randa will setup follow-up.
    • Scott Blandford and Lauren Lewis will be the E2E owners and drive the cross-team coordination to deliver the use case.
    • APPC needs to provide SO an updated APPC Client Library. Need to define when this can be provided.
      
  • Code Coverage
    
    • Patrick, Taka, Atul, and Tomasz contributing to code coverage in Sprint 1
      
  • Security
    
    • There are 3 things we are covering under security
      
      • CII Badging - Taka to go through the assesement to identify our gaps. Planned in Sprint 1
      • AAF integrations (Ryan) - this has dependency on AAF-91 delivery on 2/15. Need to see AAF design to determine scope of APPC changes. See action item above.
      • Secure DMaaP topics - currently unassigned - Shubada to investigate to see if she wants to tackle this.
        
  • Logging
    
    • ry303t will give a knowledge share on EELF - planned for 1/31/18
      
  • Documentation
    
    • Randa will update LCM API guide for the actions contributed by AT&T, which include:
      
      • QuiesceTraffic
      • ResumeTraffic
      • UpgradeSoftware
      • UpgradePreCheck
      • UpgradePostCheck
      • UpgradeBackup
      • UpgradeBackout
      • ActionCancel
      • ActionStatus
      • AttachVolume
      • DetachVolume
        
• Review JIRA workflow used by APPC
  • We did not get a chance to cover this topic, but APPC uses this workflow!
    
    
• Misc updates
  
  • We are still waiting on TSC to approve new repo request, until we get this, LF will not move forward with adding our repo
  • License question - still waiting for response from Steve Winslow on questions regarding licensing. As this stage, we will assume they do not apply to:
    • .gitignores
    • Eclipse environment related files
    • Test input files
      

01/31/18 - APPC Project Weekly Minutes

Agenda:

• Code Submits
• Sprint 1 status
• License question
• Upcoming milestone
• OOM
• JIRA
• vDNS

Participants: Randa Maher, Scott Seabolt, Aaron Hay, Patrick Brady, Ramya Balaki, ry303t, Takamune Cho, Former user (Deleted), Linda Horn, Shubhada Vaze, Vidhya Nerella, Marcus Williams

Actions from last meeting:

• Sai Gandham to schedule meeting with APPC team to review his design plans for AAF-91. 
  • Update: Per feedback from Sai Gandham, he will schedule a call for Friday
    
• Skip Wonnell to investigate missing action action-cancel from LCM Provider  
  
  • Update: CLOSED. There is no action-cancel planned for Beijing.
    

New Actions Items:

• Scott Seabolt and Takamune Cho to sync-up on questions CII Passing questionnaire to see if further clarification is needed from the Security subcommittee,
• ry303t, Patrick Brady, and Marcus Williams - need further discussion on APPC-500 to determine root cause for log file growth.. Patrick will try to build with later version of CCSDK based on feedback from Marcus to see if this helps
• Randa Maher to schedule call for Friday to discussion more detail on CDT and what is needed.

Notes:

• Code Submits
  
  • There are many changes being submitted to address Sonar issues, but are also making large changes to the code. Committers have no way of testing these code and a simple review for such changes is difficult. There is great concern of breaking the build and application. Contributors must test their code before committing. Please see email sent by Patrick and also refer to the instructions he provided to setup your own local environment: Building and Running APPC Docker Images - feel free to reach out to us via comments on wiki if you have any questions.
• Sprint 1 Status:
  
  • In general, everyone on track for their items by 2/7 (end of Sprint 1)
  • Randa to follow-up with Skip on items assigned to him.
  • Reminder to team: Make sure your code is accompanied by junits, specially any new code. We have a target of 50% to reach for

• License question
  • Do we need to change year in License text to reflect 2017 and 2018? Pending final input from....
• Upcoming milestone
  • M2 coming up on 2/12 - Checklist
• OOM
  
  • OOM is looking for one centralized place they can pull config info to create a Helm chart..
  • Need additional follow-up with OOM team to get more detail on proposal to create a config directory, similar to what was done with doc
• JIRA
  • There are two different workflows supported in ONAP; APPC uses the one discussed in previous notes and discussed in this short video
  • Additional short videos will be provided, but if you have specific questions, please send or post on wiki in comments secton.
• vDNS
  • Paul and Brian had discussions about using LCM to do the configure of vDNS in the Scale Out use case; need further discussionw with Paul on what he had in mind. Randa to follow-up

02/07/18 - APPC Project Weekly Minutes

Agenda:

• Sprint 1 status
• Commit Sprint 2

Participants: Randa Maher, Scott Seabolt, Patrick Brady, Ramya Balaji, ry303t, Skip Wonnell, Former user (Deleted), Mike Zinnikas, Shubhada Vaze, Takamune Cho, Tomasz Kaminski, Vidhya Nerella

Actions from last meeting:

• Sai Gandham to schedule meeting with APPC team to review his design plans for AAF-91.
  
  • Update: Meeting moved to this Thurs, 2/8/18
    

New Actions Items:

• Need to follow-up with SDC again on their plans to move to onap from openecomp; we still have not gotten feedback on timeline for this dependency yet. Takamune Cho to follow-up with SDC,

Notes:

• Sprint 1 Status
  
  • Security update
    
    • APPC-405 - Takamune Cho
      • Action: Need to open stories for area that are "unmet"
      • Taka will update the story with the list of the gaps identified
  • Code Coverage
    
    • APPC-369 - Patrick Brady
      • Junit submitted in Sprint 1, will close and add new story for Sprint
    • APPC-437 - Michal Kabaj
      • Gerrit review waiting review -
    • APPC-439 - Tomasz Kaminski
      • Move to Sprint 2
    • APPC-501 - Former user (Deleted)
      • Move to Sprint 2
    • APPC-533 - Shubhada Vaze
      • Move to Sprint 2
  • Resiliency
    • APPC-475 - Aaron Hay
      • Move to Sprint 2
  • ScaleOut
    • APPC-532 - Ramya Balaji
      • Can be moved to Delivered; code unit tested, junits added - story can be closed

    • APPC-479 - Vidjya Nerella

      • Move to Sprint 2; need additional time..
      • Another item will be added to Sprint 1 due to new requirements added by Paul: Vidhya to send details.

  • Stability-72hr soak

    • APPC-484 - Scott Seabolt

      • this has been prep for testing
      • Environment , clients, jmeter, all loaded
      • Investigation on metrics completed to define what we need to collect
      • Footprint for test defined; Sprint 2 will be to focus on writing the test
      • Aaron can help support these activities; he has a stable Amsterdam env to try things out on first

  • Documentation

    • APPC-357 - Randa Maher

      • Changes submitted; waiting to be merged before closing story

  • Platform Hardening

    • APPC-307 - Takamune Cho

      • Move  out of Sprint 1, need to make decision about wanting to support Rebuilt via APPC provider - Check with Paul on direction.

    • APPC-292 - Patrick Brady

      • Submitted, needs to be merged

    • APPC-254 - Sonar story - many open sub-task

  • Logging

    • APPC-428 - Tomasz Kaminski

      • Follow-up on this one wit Ryan
• ODL & DB upgrade - Send CCSDK PTL request for status on Sprint 1 - sprint shows to be done on 2/3; however, many issues still showing open
  • Input from Dan Timoney is that ODL is not complete yet, he is targeting end of week
  • No update yet on MariaDB.
  • This will deplay our plans to complete these two items in Sprint 2. If CCSDK provides Nitrogen end of week, we can get ODL upgrade done in Sprint 2. For now, will leave both in Sprint 2 until we get further updates.
• AAF dependency
  • Review with Sai Gandham planned for 2/8
  • Initial target for AAF-91 communicated was mid-Feb; will confirm tomorrow if this is still the plan
• CDT
  
  • License scan needs to be done first before submitting seed code
• ScaleOut
  • Multiple meetings have happened today to clarify requirements with SDC, VID, SO, and AAI.
  • It has been a challenge getting all needed participants to these calls due to timezones and VF2F meetings this week.
  • Still need further clarification from SDC on what identifier we can use to uniquely identify a VFModule so that we can associate the correct scale out template.

02/07/18 - Scale Out dependency and cross product coordination

Participants: Scott Seabolt, Takamune Cho, James Forsyth, Lauren Lewis, Ofir Sonsino, Randa Maher, Scott Blandford, Paul Miller, Prabhu Somasundaram, Dan Timoney, Seshu Kumar Mudiganti, Christina Monteleone

Recording:  ScaleOut Requirements Cross Team dependency- 2-7-18-audio_only.m4a

Notes:

• Decision: VID will provide Controller Type Property to SO so that SO can post request to correct DMaaP topic; this should be configurable. VID & SO will work together to flesh out the details.
• Assumption is that user creating the scaleout request will know which controller needs to handle the request to scaleout.
• Seshu will follow-up to determine out SO uses the APPC Client library and get back to us if additional discussions are needed.
• Action: Another meeting is needed to since SDC representative was not able to make meeting. Follow-up sessionwill be planned for Monday, 2/12.
  • Open issue: What identifier can APPC use that uniquiely identifies the VfModule and does not change with environment.
    • Update: vfModuleModelName is proposed. See notes below.

02/12/18 - Scale Out dependency and cross product coordination - Continued

Participants: Takamune Cho, Vidya Jog, Paul Miller, Scott Seabolt, Lior Nachmias, Steve Smokowski, Scott Blandford, Lauren Lewis, Michael Lando, Dan Timoney, Prabhu Somasundaram, David Ho, Shailendra Borale, Michael Zinnikas

Purpose of Meeting: Determine what identifier can be used by APPC that uniquely identifies the VfModule and does not change with environment

Conclusion

• APPC can use the vfModuleModelName. They will have to traverse the AAI data to get to it; VID must pass the vfModule ID in the payload of the ConfigScaleOut request. Using this vfModule ID, APPC can retrive the model name. APPC would have to traverse AAI data (VF Module ID → Model Version ID → Model  → Model Invariant ID → Model  Version → Model Name)
• APPC will be flexible in it's design -
  
  • If it gets controller-template-id in the payload, it will use this value to retrieve the correct ConfigScaleOut template.
    
  • If it does not get controller-template-id in the payload, it will use the vfModule ID, also expected in the payload, to retrieve the vfModuleModelName from AAI and use that to map to the correct ConfigScaleOut template.
    

Action items:

• Michael Lando- follow-up to determine if the content of the CSAR changes per environment
• Michael Lando - follow-up to determine if SDC is setting workload context.
• Randa Maher to check with Ofir Sonsino and Lauren Lewis to make sure VID has requirement to include one of the above cases, using vfModuleID would be prefereable.
• Randa Maher to setup a follow-up call to have further discussion on VID to SO requirements to determine which controller a request needs to go to.

Additional Notes

• Steve Smokowski had some concerns around doing throw-away work to support multiple controllers; ideally, the model should define which controller manages a given VNF and that should be information that is part of the onboarding process for any VNF. However, we are not at that level of maturity yet and the issue extends beyond scale out scenario. The question is what is doable in Beijing, which is why using VID was the interim solution proposed. Some more discussion will take place on this topic. 

02/13/18 - Scale Out dependency and cross product coordination - VID to SO Controller Type- round 2

Participants: Takamune Cho, Vidya Jog, Paul Miller, Scott Seabolt, Lior Nachmias, Lauren Lewis, Michael Lando, Dan Timoney, Prabhu Somasundaram, Ofir Sonsino

Purpose of Meeting: A follow-up session was requested to revisit the decision made on 2/7/18 regarding how we determine to which controller to route the request. 

Conclusion:

• SO was not able to make meeting, so quoram for discussion was not achieved.
• The decision made on this issue is transparent to APPC; i.e., does not affect APPC requirements. There will be impact to APPC Client Library to support this.
  
• Scott Blandford and Lauren Lewis will follow-up with VID and SO teams to get alignment on this particular issue.

02/14/18 - APPC Project Weekly Minutes

Agenda:

• Sprint 2 status
• Misc

Participants: Randa Maher, Aaron Hay, Scott Seabolt, Takamune Cho, Hector Anapan-Lavalle, Patrick Brady, Skip Wonnell, Shubhada Vaze, Michael Zinnikas, Vidhya Nerella

Actions from last meeting:

• Need to follow-up with SDC again on their plans to move to onap from openecomp; we still have not gotten feedback on timeline for this dependency yet. Takamune Cho to follow-up with SDC,
  • Update 2-14-18: Per TPL, Michael Lando, SDC will address namespace change in their next sprint, so looks like APPC won't be able to finish APPC-13 until Sprint 4. There is still an open issue on use of openecomp-tosca-lib, which needs to be clarified.
    
• Sai Gandham to schedule meeting with APPC team to review his design plans for AAF-91.
  
  • Update: 2-07-18: Meeting moved to this Thurs, 2/8/18
  • Update: 2-14-18: Meeting on 2/8 was canceled; Sai indicated another will be schedule this week.
    

New Actions Items:

• 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)
• Aaron Hay to add details on his work on Resiliency epic on wiki - APPC Beijing Testing - feel free to add wiki pages under this entry to capture details.

Notes:

• Sprint 2 started on 2/8 and ends on 2/22.
• M2 deadline was on 2/12
• Sprint 2 status
  • Security
    • APPC-486 - secure DMaaP topics - currently unassigned.... move this to Sprint 3
  • Code Coverage
    • APPC-437 - Michal - will this be implemented for the methods documented ?
    • APPC-501 - Atul - can this be closed?
    • APPC-533 - Shubhada - plan to complete by 2/22 - moved this to backlog; move APPC-617 to Sprint 2
    • APPC-439 - Tomasz - In-Progress...
    • Taka - which issues can we move to Sprint 2?
      
      • APPC-600, 615, 624, 626, 635 moved into Sprint 2.
  • ODL upgrade - APPC-403 (Patrick)
    
    • Dependency on CCSDK - follow-up with Dan, he said he would have it ready this week.
    • Patrick Brady to follow-up with Dan on readiness of ODL from CCSDK.
  • Resiliency (Aaron)

    • APPC-475. APPC-476 - Merging work on 476 & 475

    • Made a lot of progress - Kurbenetes w/OOM setup in WindRiver similar to what SDNC had as documented on their wiki. Everything is working correctly.

    • APPC installed correctly, all the bundles successful. Next step to work on - scale out replicas, which was not successful - if we want APPC to be able to change the number of replicas for appc or appc-dbhost, then statefulset.yaml files will need to be created similar to SDNC

    • Aaron has as separate environment for  work on the resiliency testing (does not interfere with environment being used by Stability team) - working on getting Appc working in Kubernetes

    • Action: Randa to setup call with James McNider & Sharon to discuss with SDNC has done.
    • Action: Aaron to document details of his efforts on APPC wiki
      • I added this wiki page and subpage to start adding details: APPC Beijing Testing
  • CDT
    • Waiting on License scan to complete before pushing code to LF
    • Patrick to create verify jenkins job for cdt repo (APPC-627) - put into Sprint 3
  • Manual Scale Out
    • APPC-479, APPC-544,  (Vidhya)
      • worked on the services classes, working on junit
      • will submit by end of week
    • APPC-543 (Ramya)
      • Code submitted, story can be closed once code is merged.
      • However, requirements are still churning a bit on this, so will have additional changes probably in Sprint 3.
  • Stability - 72hr soak
    • APPC-456 (Scott, Ryan)
      • working on jmeters tests, loading AAI data, set up VMs, but they are evacuating which causes more work for us (we need to keep snapshots around to minimize the impact)
      • Initial testing will be done on the non-clustered environment, but moving to clustered later should be just a matter of pointing to the clustered environment.
      • Where do we want to put the tests?  Deployment project..
      • Action: Create wiki to track our testing status
        • I added this wiki page to start populated tests: APPC Beijing Testing Scope and Status
  • Documentation
    • Nothing planned for Sprint 2
  • Platform Hardening
    • APPC-13 - namespace update - Moved to Sprint 3 since SDC will not address their changes until their next sprint, which wont start until end of Feb.
• Amsterdam jenkins jobs will be removed (APPC-625)
• Vacations
  • Ramya - 2/13/18 - 2/26/18
  • Atul - 2/16/18 - 3/5/18
• Other topics discussed
  
  • Need to review latest email from Steve Winslow received today on license items.
  • Gerrit submits addressing more than just Sonar issue; reviewing some submissions is difficult because a lot of code is moved around. Options proposed by team: Only allow 1 sonar issue per Gerrit submit, stick to fixing the specific Sonar issue and don't try to restructure file, etc....  We don't want to discourage contributions;however, we are responsible as committers to ensure the health of the application, so I propose that code review session be requested with the contributor to step through their changes and have him/her explain the changes and their reasoning behind those that are not clear.
  • We really need to put priority on code coverage/junits since that's tied to the S3P requirements; however, this is difficult to enforce for folks that are not formally part of the APPC Beijing team.

02/21/18 - APPC Project Weekly Minutes

Agenda:

• Sprint 2 status
• Review Action items
• Upcoming milestone: M3 (3/9)

Participants: Randa Maher, Scott Seabolt, Aaron Hay, ry303t, Takamune Cho, Patrick Brady, Skip Wonnell, Shubhada Vaze, Vidhya Nerella, Linda Horn, marge.hillis

Actions from last meeting:

• Need to follow-up with SDC again on their plans to move to onap from openecomp; we still have not gotten feedback on timeline for this dependency yet. Takamune Cho to follow-up with SDC,
  • Update 2-14-18: Per TPL, Michael Lando, SDC will address namespace change in their next sprint, so looks like APPC won't be able to finish APPC-13 until Sprint 4. There is still an open issue on use of openecomp-tosca-lib, which needs to be clarified.
    
• Sai Gandham to schedule meeting with APPC team to review his design plans for AAF-91.
  
  • Update: 2-07-18: Meeting moved to this Thurs, 2/8/18
  • Update: 2-14-18: Meeting on 2/8 was canceled; Sai indicated another will be schedule this week.
    
  • Update: 2-21-18: Meeting schedule for 2/23/18.
    
• 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: still in-progress; no updates to wike made yet
    
• Aaron Hay to add details on his work on Resiliency epic on wiki - APPC Beijing Testing - feel free to add wiki pages under this entry to capture details.
  • Update: 2-21-18: still in-progess; no updates to wike made yet
    

New Actions Items:

• Randa Maher to follow-up with Amaresh on ScaleOut and Test Action Support for CDT tool 

Notes:

• Reminder: Code Complete is 3/28 - we have ony 2 sprints left to complete everything!
• Sprint 2 end 2/22/18 (tomorrow!)
• Sprint 2 Status:
  • Security
    • Moved secure DMaaP topic to Sprint 3 and assigned to Ryan
  • Code Coverage
    • APPC-635 (Takamune Cho) - originator requested task be moved to Sprint 3 since he will not be able to complete
    • APPC-439 (Tomasz Kaminski)
    • APPC-580 (Shubhada Vaze) - closed
    • APPC-437 ( Michal Kabaj) - originator requested task be moved to Sprint 3 since he will not be able to complete
  • ODL upgrade
    • APPC-403 (Patrick Brady) - CCSDK Docker still not done as of 2/20; this is delaying APPC work for upgrade. Will need to move to Sprint 3.
    • Patrick will reach out to Dan to see how close to completion he is.
  • Resiliency
    • APPC-475 (Aaron Hay)
    • APPC-476 (Aaron Hay)
    • Met with SDNC team last week (Joey Sullivan) to get an overview of the stateful files that were built to allow for replica adjustments through K8S; limited progress
    • Aaron reached out to OOM team and they indicated they will support both Cinder and NFS for DB, so we can proceed with same nfs solution used by SDNC for DB resilency.
    • OOM team will setup call with APPC to discuss further; Aaron Hay will notify team.
    • Aaron Hay to update JIRAs (or wiki) with details of the work he has been doing.
  • Scale Out
    • APPC-544 (Santoshi Vidhyasree Nerella)
    • APPC-479 ((Santoshi Vidhyasree Nerella)
    • Both stories should be submitted by 2/22; code done, was running in merge conflict on submitted, working to resolve.
    • There is some concern around churning requirements for APPC Client Library, which is part of Sprint 3 work. Need to have further discussion with Paul next week.
      
  • Stability - 72hr test
    • APPC-456 (Scott Seabolt, ry303t)
    • Story needs to be moved to Sprint 3
      
    • Lost about 3 days due to WindRiver lab issue that blew away all of our work.
    • Got lab back up, can send and receive responses via DMaaP & jmeter
    • Ran into issue that was fixed in a later build and had to upgrade environment to latest dockers; however, we are getting errors. Scott believes it may be a dependency issue
    • Scott will reach out to folks for help in debugging; will open bug issue.
      
  • Platform Hardening
    • APPC-578 - Sonar Issues
      • Several still open sub-tasls
    • Sonar issue:
      • Anand has 422 assigned ??
      • Great progess reducing numbers

  • Date	Blocker	Critical	Major
    01/25/18	39	881	2409
    01/31/18	33	736	2237
    02/08/18	29	615	2083
    02/20/18	15	435	1218

• • Bugs
    • APPC-564 - ry303t will complete this by 2/22
    • APPC-561 - there are some issues around this gerrit submt; meeting scheduled for Friday to review; JIRA will get moved to Sprint 3.
  • CDT
    
    • License scans (BlackDuck and Fossology) being reviewed.
    • If all is well, code will be submitted as part of Sprint 3.
• Upcoming milestone: M3 (API Freeze) on 3/8
  
  • Architecture walkthrough to understand how each project contributes on Release Use Case. ARC to organize the walkthrough.
• Sprint 3 planning
  • Security
    
    • Secure DMaaP topics (Ryan)
    • Update logback version to address security issue (Taka)- APPC-652
    • Review Nexus IQ criticals to determine what we can do (Taka) - APPC-656
  • CDT
    • Seed code contribution
    • CDT Guide
    • Need to follow-up with Amaresh on ScaleOut and Test Action Support.

02/28/18 - CDT and APPC Discussion - Part 1

Link to recorded Session: CDT and APPC Discussion - Part 1- 2-28-18.mp4

03/02/18 - CDT and APPC Discussion - Part 2

Link to recorded Session: CDT and APPC Discussion-Part 2 - 3-02-18.mp4

02/28/18 - APPC Project Weekly Minutes

Agenda:

• Sprint 3 status: (reminder: ends 3/9)
  
  • Security
    • Critical security violations (Taka)
    • AAF (Ryan)
    • Secure DMaaP topics (Ryan)
    • Issue created by change to Logback (Taka, Patrick)
  • Code Coverage (Tomasz/Michael/Shubhada
    • APPC-679, APPC-681 - Shubhada - are these planned for Sprint 3?
  • ODL update (Patrick)
  • CDT (Skip/Patrick)
  • ScaleOut (Ramya/Vidhya)
  • Stability (Scott/Ryan)
  • Resiliency (Aaron)
  • Documentation (Randa)
  • Platform Hardening (Sonar)
• M3 Arch review: on 3/6
• M3 milestone = 3/8
• M4 - new security checklist added.
  • M4: link to security template https://wiki.onap.org/pages/viewpage.action?pageId=25435956
• Misc items
  • Updates from TSC: CLA and CAL

Participants: Randa Maher, Scott Seabolt, Patrick Brady, ry303t, Takamune Cho, Aaron Hay Ramya Balaji, Veer Rajasekhar, Hector Anapan-Lavalle, Michael Zinnikas, Shubhada Vaze, Tomasz Kaminski, Vidhya Nerella, Vishnu Ram OV

Recording:  APPC Weekly Project Call 2-28-18.mp4
Actions from last meeting:

• Need to follow-up with SDC again on their plans to move to onap from openecomp; we still have not gotten feedback on timeline for this dependency yet. Takamune Cho to follow-up with SDC,
  • Update 2-14-18: Per TPL, Michael Lando, SDC will address namespace change in their next sprint, so looks like APPC won't be able to finish APPC-13 until Sprint 4. There is still an open issue on use of openecomp-tosca-lib, which needs to be clarified.
    
• Sai Gandham to schedule meeting with APPC team to review his design plans for AAF-91.
  
  • Update: 2-28-18: Meeting held today; target to have delivery of AAF-91 by end of week; Sai Gandham is currently testing. Will consider this item closed.
    
• 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
• Aaron Hay to add details on his work on Resiliency epic on wiki - APPC Beijing Testing - feel free to add wiki pages under this entry to capture details.
  
  • Update : 2-28-18: Information is being added here: APPC Beijing Testing - this will continue evolving over the next few weeks. Will consider this item closed.
    

New Actions Items:

• Randa Maher to follow-up with Amaresh on ScaleOut and Test Action Support for CDT tool 

Notes:

• Sprint 3 status: (reminder: ends 3/9)
  
  • Security
    • Critical security violations (Taka)
      • APPC-656 added to Sprint 3; Taka going through the critical security issues reported via Nexus IQ. APPC has 20 issues to clear.
        
      • Resolution for the common collections submitted and merged (APPC-665)
      • Working on jackson-mapper issue (APPC-675)
      • Note: Nexis IQ report are visible via Jenkins CLM, but only accessible by committers.
        
    • AAF (Ryan)
      • Meeting planned for later today with Sai to review AAF design approach.
      • Sai Gandham indicates that AAF-91 should be available to APPC by end fo week.
        
      • After call later today, we will determine if APPC-404 can be finished in Sprint 3.
        
    • Secure DMaaP topics (Ryan)
      • First need to get pass current issue with unsecure topics that is blocking Stability testing (APPC-658)
      • The story for document how to setup secure DMaaP secure topic (APPC-486) will likely move to Sprint 4.
        
    • Issue created by change to Logback (Taka, Patrick)
      • The change for logback will be rolled back (APPC-684) because it's causing problems with failing bundles during deployment.
      • EELF team updated EELF to address logback issue, so we will upgrade EELF version after we finish ODL upgrade.
      • eelf-core-1.0.1-oss has been released with upgrade to logback-1.2.1: http://repo1.maven.org/maven2/com/att/eelf/eelf-core/1.0.0-oss/
  • Code Coverage (Tomasz/Michael/Shubhada)
    • APPC-679, APPC-681 - Shubhada - are these planned for Sprint 3? Yes, confirmed. Stories moved into Sprint 3.
    • APPC-439 - Tomasz confirmed this would be completed in Sprint 3.
    • APPC-437 - one commit in new state pending review for ChefAdapterImpl.java
    • APPC-677 moved into Sprint 3
      
    • Confirmed with Release Manage (Gildas Lanilis Gmail) that code coverage is measured back on number in quality gate for line coverage: at the moment, appc is at 39.8%. We will have another 10% to achieve by 3/29.
    • Some low hanging fruit to get our numbers up faster is to look for opportunities in the code using powermocke and change to mockito...
      
  • ODL update (Patrick)
    • Received notification from Dan Timoney that ODL is ready. Patrick will start work on APPC-403; we will have to assess if this can be completed in Sprint 3 or not.
      
    • This is not going to be a simple upgrade; looks like there will be quite a few changes that will need to be made.
      
  • CDT (Skip/Patrick)
    • Plan to push seed code out by Thurs, 2/28.
    • BlackDuck & Fossology scans done and report reviewed; however, another package was added, so we need to run Blackduck again today and review one final time.
      
    • BlackDuck made some incorrect matches that had to be corrected...
      
  • ScaleOut (Ramya/Vidhya)
    • Epic and story descriptions updated to align with latest requirements changes.
    • APPC-683 was added for support of multiple controller types and put into Sprint 4.
    • Vidhya plans to have APPC-544 submitted by tomorrow (3/1) morning and will target APPC-478 by Monday (4/5)
    • Ramya has completed coding for APPC-480 and is working on junits. 2 tasks will likely move to Sprint 4 (APC-622 and APPC-623)
    • Jimmy confirmed that vnfModuleModelName is populated in A&AI model-name attribute under the model-ver object
    • Confirmed with Richard Tabedzki that no changes will be needed to the AAI client to retrieve the model name.
      
  • Stability (Scott/Ryan)
    • Testing currently blocked by APPC-658, team is working on debugging - Scott, Ryan, Aaron, and Patrick pulling together to try to work through this one. Also engaging Dominic from DMaaP team to help troubleshoot.
    • Once APPC-658 bug is resolved, it should not take long to get test going. Team has most of that pretty much figured out, some minor tweeking will be needed. 
  • Resiliency (Aaron)
    • Aaron has been meeting with OOM team (Mike Elliott). OOM team alread has a JIRA in OOM project to setup APPC for resiliency under OOM.
    • Aaron has been working with Mike for last three days. Mike is till working through some issues and has requested some information; Aaron working to collect info and respond.
    • Mike will be going on vacation end of week and will be handing off to someone else on OOM team.
    • Once we get our setup configured correctly in OOM, it should just be a matter of adding code to startODL for joining our applicaiton nodes into the ODL cluster.
      
    • One thing to note with existing solution on DB failover - there is no way to promote DB master, it will be a manual process. Master is read/write, slaves are read only. If you lose the master, you lose write capability.
      
  • Documentation (Randa)
    • CDT user guide progressing; should have initial version for Sprint 3. Another story will need to be created to update it to add the Test action that is being added as part of Beijiing.
    • LCM guide will also be updated to add the ConfigScaleOut action - that will be be completed for Sprint 3.
      
  • Platform Hardening (Sonar)
    
    • We didn't cover this one, but we really need help with code cover over Sonar fixes in Beijing.
      

• M3 Arch review planned on 3/6
• M3 milestone = 3/8
• M4 - new security checklist added. - will discuss this more next meeting
  
  • M4: link to security template https://wiki.onap.org/pages/viewpage.action?pageId=25435956
• Misc items
  • Updates from TSC: CLA and CAL
    • LF will be providing more info on CLA, but it's expected that all developers and their companies sign a Contributor Licensing Agreement by 3/20. Anyone without a signed CLA will be locked out per LF.
    • Commiter Access List is being instantiated to provide more granular controller on the individual repos.  This will be managed by introducing an INFO.YAML file in each repo that identify the approved committers for that repo.
      

03/07/18 - APPC Project Weekly Minutes

Participants:Randa Maher; Patrick Brady; Scott Seabolt; Aaron Hay; Shubhada Vaze; Former user (Deleted); Ramya Balaji; Takamune Cho; Tal Liron; Vidhya Nerella;

Recording:  APPC Weekly Project Call 3-07-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

• Randa Maher to follow-up with Amaresh on ScaleOut and Test Action Support for CDT tool
  
  • Update: 3/6/18: Per feedback, all code is submitted, testing is what remains.

New Actions Items:

• Randa Maher to follow-up with Kenny for an update on the CLA that is due by 3/2 per last communication.
  • Update: 3/7/18: Feedback from Kenny is that Phil Robb plans to address this topic at 3/8 TSC meeting.
• Aaron Hay to deploy another APPC instance running Amsterdam for Stability team
• Aaron Hay to deploy an instance of vDNS VNF in lab.

Agenda & Notes:

• M3 milestone = 3/8
  • APPC presented to Architecture Committee on 3/6; no findings identified
  • APPC Beijing M3 Checklist
  • Only pending item to complete for M3 is failing daily build for one of the jobs.
• Sprint 3 status: (reminder: ends 3/9)
  
  • Security
    • Critical security violations - APPC-656 (Taka)
      • We started out with 20; we are down to 17
      • All the level 8 items in Nexus we cannot address in Beijing. We will need to document them in the security template for M4. These items do not have "non vulnerable version of this component" - this linked to CVE-2017-7525
      • Going through all the level 7 items know with plans to complete by 3/12 - either fix or document. Progress so far...
        • APPC-701 - this is a dependency pulled in from CCSDK, so CCSDK needs to fix
        • APPC-702 - this dependency is coming from ODL. It may get resolved once we upgrade to Nitrogen, don't know at this stage
        • APPC-703 - this one will be fixed
          
    • AAF Integration - APPC-404 (Ryan)
      • Still waiting on AAF-91 feature dependency.
      • If we don't get delivery of AAF-91 by 3/9, we will have to access if this can APPC-404 can stay in scope for Beijing.
        
  • Code Coverage (Tomasz/Michael/Shubhada
    • APPC-681 (Shubhada) - Closed
    • APPC-439 (Tomasz) - need to follow-up on this email
    • APPC-437 (Michal) - per request from Michal, this was moved to Sprint 4
  • ODL update - APPC-403 (Patrick)
    • Patrick downloaded the sli image yesterday and it's still not working.
    • He had been in contact with Dan Timoney on issues he's having with ccsdk sli image.  Fixes are being delayed due to issues with Jenkins
    • Patrick to open defect on CCSDK so that we can track our dependencies and issues causing us delay.
    • The work to integrate Nitrogen is not trivial; there will be a lot of changes.
      
  • CDT
    
    • APPC-682, APPC-687 (Skip) - closed
      
    • APPC-627 (Patrick) - waiting on fix from developer; expected today
    • Patrick is seeing some angular build errors when it run in jenkins, but the artifacts seem to generate fine
      
  • ScaleOut
    
    • APPC-480 (Ramya) - In-progress,
      • Subtask APPC-622 will move to Sprint 4, the others are complete.
    • Discussion still taking place on how to implement changes in APPC client library to support Controller Type; no viable option yet that can fit in the time line.
      
  • Stability
    
    • APPC-456 - (Ryan) - will complete by end of week.
      
    • APPC-612 (Scott) - will complete by end of week.
      
    • APPC-457 - test execution - will move to sprint 4
      
    • Bug; APPC-658  - Ryan has been troubleshooting a lot of issues, but any fixes we make now will need to be redone when ODL is upgraded. Best to wait for ODL upgrade to complete first. To unblock testing, we will go back to Amsterdam release for now. Aaron will deploy another instance running Amsterdam.
      
  • Resiliency
    • APPC-627  (Aaron) - got initial draft of the work that OOM did for the Helm chart; moved info from existing appc directory to their global directory. Initial version had issue with DB coming up and mapping to the physical volume. OOM team has been working through those issues this week, so not up and running 100% yet.  Will need to make good progress around issue of DB and physical volumes to be able close this story in Sprint 3.
      
    • Aaron provided the input requested last week.
    • No discussion from SDNC side on testing with MariaDB.OOM is putting in support, but not clear where CCSDK/SDNC are with respect to MariaDB.
    • Based on last CCSDK project call on 3/2; Dan said he was going to look for a publicly available MariaDB image - that's the extend of what we know at this point.
      
  • Documentation
    
    • APPC-375 (Randa) - initial draft of CDT user guide ontrack to submit by end of week
    • Updates to LCM API Guide to add new ConfigScaleOut API submitted.
    • We will need to do additional updated to CDT guide to update screen shots when we have access to latest CDT UI
      
    • We have a little more time to complete documentation since this is not tied to code freeze.
      
  • Platform Hardening (Sonar)
    • APPC-688 (Ramya) - closed
      
    • APPC-653 (Jakub, Maciej, Tomasz, Kornel) - three subtask still pending under this stry.
      
• M4 - new security checklist added.
  • M4: security template added to project in prep of M4: APPC Beijing Security/Vulnerability Threat

03/14/18 - APPC Project Weekly Minutes

Participants:Randa Maher; Patrick Brady, Aaron Hay, ry303t, Veer Rajasekhar, Ramya Balaji; Takamune Cho; Vidhya Nerella; Shubhada Vaze

Recording:  APPC Weekly Project Call 3-14-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/14/18: Pending
    

• Randa Maher to follow-up with Amaresh on ScaleOut and Test Action Support for CDT tool
  
  • Update: 3/6/18: Per feedback, all code is submitted, testing is what remains.
  • Update: 3/14/18: In Progress, task/stories in Sprint 4; confirmed that ScaleOut and Test Actions are in; just code clean-up and defect fixing now. Closed.

• Randa Maher to follow-up with Kenny for an update on the CLA that is due by 3/2 per last communication.
  • Update: 3/7/18: Feedback from Kenny is that Phil Robb plans to address this topic at 3/8 TSC meeting.
  • Update: 3/14/18: Decision in 3/8/18 TSC meeting is to delay CLA until start of Casablanca. Closed
• Aaron Hay to deploy another APPC instance running Amsterdam for Stability team
  • Update: 3/14/18: Done. Closed
• Aaron Hay to deploy an instance of vDNS VNF in lab.
  • Update: 3/14/18: Worked with Stephen and Eddie, but issue in APPC env. Got Heat templates from Marco, but ssh plublic key not getting integrated with public instance and can't get into them. Reaching out to Marco for assistance.
    

New Actions Items:

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

Agenda & Notes:

• Review upcoming milestones & release plan
• Review action items from last week.
• Status
  
  • Security
    • Critical security violations - APPC-656 (Taka)
      • Went through all the critical security items, expect logback, which is is waiting on upgrade of EELF
      • Need to wait until ODL upgrade is completed before we address the remaining items since they may be addressed with newer version of ODL.
        
      • The level 8 criticals will need to be addressed in Casablanca since there is no version of the software without the vulnerability. 
        
        • Takamune Cho to update security checklist for the leve 8 items at:Security/Vulnerability Threat Template
          
    • AAF Integration - APPC-404 (Ryan)
      • Working with AAF team on delivery of AAF-91; still not ready yet
      • If work for APPC once feature is delivered is more than just configuration, then APPC-404 is at risk for 3/29.
        
  • Code Coverage 
    • Current: 43.9%
    • Target: 50%
    • Many tasks and stories opened by team, need those to complete in Sprint 4. Submit as soon as possible so that we can see how we are progressing towards our target.
      • Sprint 4 Code Coverage Jira Issues
        
  • ODL upgrade - APPC-403 (Patrick)
    • Targeting changing features over to the new structure, basically each pom points to its own different parent now. 
    • Push a few features as drafts, trying to figure out how the imports/exports work in this version - lots of work with this release
      
  • Resiliency
    
    • APPC-476 and  APPC-666 (Aaron)
      • OOM team has completed moving our charts from the old 1-click method to Helm
      • Moved component we need to a common area
      • However, they run into an issue where the DB does not initialize properly under the new charts; meeting later today
      • In parallel, Aaron has repaired his Kubernetes clustered environments now and once he get info from OOM team, he should be able verify his changes in local APPC env
        
  • CDT
    
    • Need to build docker in ONAP; need a volunteer to step up and do the work for this one.
    • Will need a new folder in deployment project, need a docker file to point to tomcat/node.js, pull down artifacts from Nexus and put in docker, etc...
      
  • ScaleOut
    
    • APPC-545 (Ramya)
      • mostly completed; reviewing requirements again to ensure nothing overlooked; testing in local environment
    • APPC-683 (Vidhya)
      • APPC Client library change to add support for controller type will be submitted today; will be available for SO as we test in parallel
    • Code changes for ConfigScaleOut for the most part done on APPC, testing is the next big thing.
      
  • Stability (Scott/Ryan)
    • APPC-457 - test execution
    • Bug; APPC-658 
    • APPC-463 - documentation
    • The framework for the test has been built out, Scott submitted to deployment project, but in terms of actual testing, little progress.
    • Scott on vacation this week; Ryan has been helping AAF team, also dealing with computer issues this week.
      
    • Still having problems with async responses coming back.
      
  • Documentation
    
    • APPC-463 -  (Randa) - updates needed for APPC Client Library guide planned for this sprint.
      
  • Platform Hardening (Sonar)
    • APPC-13 - pending information from SDC
      • openecomp-tosca-datatype - waiting on ETA from Michael
        • Michael requested that we move away from using artifact directly and use their tosca parser since it's a managed/suportted exposed interface.
        • Action: Create story for Casablanca to move to managed tosca parser and remove direct dependency on openecomp-tosca-datatype
          • Status: CLOSED -

            Jira Legacy
            server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key APPC-736

            
            
      • sdc-distribution-client - available now…
    • APPC-660  - need to clear submit
      
    • Please note:  I did not create a Story in sprint 4 for Sonar issues; I need all effort put into increasing code coverage. This close to code freeze, we need to strategise where effort is going with the limited number fo committers and the other dev work they are doing in addition to reviewing code.
      
• Other items
  • CLA - Decision by TSC & LF is to hold off on this for Beijing; it will be required in Casablanc
    
  • Sonar story for issues - see note above
    
  • Risks - any more to add?
    • Possibly Code Coverage hitting 50% by 3/29
    • New security issues popping up after ODL upgrade is done.
      
  • Admin access to APPC in WindRiver to acccess some Openstack comments - provided by Stephen Gooch.
  • MariaDB - this will be pushed out to Casablanca. Confirmed with PTL of CCSDK project that this will move to Cassablanca. 

03/21/18 - APPC Project Weekly Minutes

Participants:Randa Maher; ry303t; Scott Seabolt; Aaron Hay; Patrick Brady; Ramya Balaji; Takamune Cho; Vidhya Nerella; Vidya Jog; Shubhada Vaze; William; Atif ?

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.
    

• Aaron Hay to deploy an instance of vDNS VNF in lab.
  • Update: 3/14/18: Worked with Stephen and Eddie, but issue in APPC env. Got Heat templates from Marco, but ssh plublic key not getting integrated with public instance and can't get into them. Reaching out to Marco for assistance.
  • Update: 3/21/18: Have not heard back from Marco; Randa will follow-up with Marco.
• 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.

New Actions Items:

• Randa Maher setup call to discuss testing in WindRiver APPC dev lab after we get Beijing successfully deployed.
• Takamune Cho will bring up CDT using docker from Nexus to validate it deploys correctly.
• Aaron Hay and Scott Seabolt will deploy APPC WindRiver lab with Beijing release today.
• ry303t will check with Dan to see if he wants to put AAF bundles in CCSDK since all SDNx and APPC both plan to use it.

Agenda & Notes:

• Review upcoming milestone (code freeze)
  • Code Freeze is 3/29!
  • Sprint 4 end is 3/26
• Review action items from last week.
• Sprint 4 Status
  
  • Security 
    • APPC-404 (Ryan) - AAF Integration
      • Got the AAF instance in lab; but what we don't have yet are the jar files from AAF in Nexus (Randa to follow-up with Sai to nail down date...)
        
      • Taking unofficial jars to start testing; however, we need to resolve DMaaP issue first (APPC-658); Ryan will focus on DMaaP first so that we can move ahead with AAF.
        
      • APPC work will involve adding the AAF bundles into the deployment and updating 3 property files; still some unknowns, on the surface looks fairly straight forward.
        
    • APPC-486 - documentation on how to set up secure DMaaP topics
      • Moving to spring 5
        
    • APPC-656  (Taka) Nexus IQ security items
      • EELF version upgrade ?

        • eelf-core-1.0.1-oss has been released with upgrade to logback-1.2.1: http://repo1.maven.org/maven2/com/att/eelf/eelf-core/1.0.0-oss/

        • Taka will submit by Friday
      • Security Checklist: APPC Beijing Security/Vulnerability Threat
      • Cassablanca Epic for Security: APPC-770
        
  • Code Coverage
    
    • Please review any tasks or stories you have open for code coverage and ensure in proper state and plan to close by 3/26
    • We are too close to code freeze, do no do any refactoring of code, change method names or signature, etc.. at this stage as it adds to much risk.
      
  • ODL upgrade 
    • APPC-403 (Patrick) 
      • Working through issues of bundles failing due to dependencies.
        
      • Got past the issue of com.google from yesterday and continue to work other bundles that are failing for different reasons.
      • Patrick is trying to target having everything coming up by end of week, but then it still needs validation.
        
  • Resiliency (and Scalability)
    
    • APPC-476 and APPC-666 (Aaron)
      • In WindRiver Lab, have a clustered environment on  Amsterdam - this is w/3 clustered APPC instances, 1 DB instance
      • What they found out is that there is an issue with the NFS share, can't share DB data on NFS mounts. Solution OOM team says is best is to have a single instance of the MySQL DB on NFS share. With the option, we don't have the slave promoted to master issue. From a resiliency perspective, we only have 1 instance; however, if it goes down, Kubernetes can spin up another instance in 1-2 seconds.  This does provide a level of resiliency, but not scalability on DB side.  On application side, we can scale to N+.
    • Any of these tests in progress ? Can we update wiki ? APPC Beijing Testing Scope and Status
      • Aaron will have his changes committed by end of week and ensure OOM has the changes they need; however, testing will need to wait until he gets back. The testing he has done has been around verifying that things are coming up, but test case execution will be done 1st week in April.
        
      • He is on vacation next week (3/26 -3/30)
      • Aaron will prepare instruction on how to do upgrade image in WindRiver so that team can do it in his absence.
        
  • CDT
    • Should have docker in Nexus by end of day. Need merge the Gerrit in deployment project.
      
    • Taka to use docker to bring up CDT GUI. 
    • Open items:
      
      • We don't have CDT in clustered environment. 
      • Will need to update helm charts for CDT tool
        
  • ScaleOut
    • APPC-545 (Ramya) - ConfigScaleOut Action Flow - Part 2
      • Testing in progress
        
    • APPC-683 (Vidhya) - APPC Client Library Support For Multiple Controllers
      • Changes done, working on testing in local; will keep story open until end of sprint while testing is taking place.
        
  • Stability 
    • APPC-463 (Scott) - APPC Stability Testing - Create Documentation for the APPC 72 Hour Stability Test
      • Documentation started; Create a wiki to store details; will plan to complete this week.
        
    • APPC-658 - (Ryan) - APPC 72-Hour Stability Testing Development - DMaaP Errors with the 431 APPC bundle
      • Blocking testing; Ryan is still debugging - Scott and Ryan will together today until this is resolved.
        
    • APPC-457 (Scott) - APPC Stability Testing - Execute Stability Tests
      • Can be started once APPC-658 is resolved. Some preliminary testing done with Amsterdam but for short periods, but needs to be done on Beijing.
        
  • Documentation
    • APPC-374 (Randa) - Update the APPC Client Library Guide
      • Not started yet, but should be doable by end of Sprint 4.
        
  • Platform Hardening
    • APPC-13 (Patrick) - Replace any remaining openecomp reference by onap
      • Dependent on SDC to complete - no ETA from SDC yet.
        
• Vacations:
  • Randa will be on vacation 4/2 - 4/6
  • Aaron - 3/26 - 3/30
  • Ryan - 3/30 - 4/2

• Looking ahead: 
  • ONS next week
  • Invite Scott Blanford wk of 4/11 to discuss Auto Scaling use case for Casablanca.

03/28/18 - APPC Project Weekly Minutes

Participants:Randa Maher; Patrick Brady; Scott Seabolt; Shubhada Vaze; Former user (Deleted); Takamune Cho;  Ramya Balaji; Vidhya Nerella; Veer Rajasekhar
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.
    

• Aaron Hay to deploy an instance of vDNS VNF in lab.
  • Update: 3/14/18: Worked with Stephen and Eddie, but issue in APPC env. Got Heat templates from Marco, but ssh plublic key not getting integrated with public instance and can't get into them. Reaching out to Marco for assistance.
  • Update: 3/21/18: Have not heard back from Marco; Randa will follow-up with Marco.
  • Update: 3/28/18: Marco deployed vDNS in our lab (VMs are named zdfw1…); however, done using Heat templates, so AAI is not populated with VNF information. Will consider this item CLOSED. AAI data will be tracked separately.
    
• 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
    
• Takamune Cho will bring up CDT using docker from Nexus to validate it deploys correctly.
  • Update: 3/28/18: CLOSED. Scott validated that you can access the CDT UI. Amaresh working to configure it to point to APPC instance.
    
• Aaron Hay and Scott Seabolt will deploy APPC WindRiver lab with Beijing release today.
  • Update: 3/28/18: CLOSED; an intance with Beijing was deployed in the singleton lab
• ry303t will check with Dan to see if he wants to put AAF bundles in CCSDK since all SDNx and APPC both plan to use it.
  • Update: 3/28/18: Query sent to Dan, but no response yet; however, given timeframe we will pull dependency from AAF. I'm going to consider this CLOSED.
    

New Actions Items:

• Ramya to identify the minimum VNF AAI data that is needed to validate ScaleOut. The work around that was provided only addressed the template model name. 

Agenda & Notes:

• M4 review planned for 3/29 with TSC
  • M4 Checklist updated based on status as of 3/27: APPC Beijing M4 Checklist
  • Beijing risks updated: Beijing Risks
  • Functional Requirements updated: Beijing Functional Requirements
  • Platform Maturity updated:Beijing Release Platform Maturity
• Status on outstanding M4 items:
  • ODL Upgrade
    • Still having isues with feature installs freezing with no error messages; SDNC probably did not see this issue since they only install a small number of feature (5 or 6) compared to APPC's 28, plus APPC is using bundle wrapping.
    • Additional problem encoured today is a method APPC uses from CCSDK from their AAI services appears to have been removed. High Priority JIRA opened (CCSDK-229)
  • AAF Integration
    • We are still waiting on AAF-91 to submit their changes and make image available, so APPC cannot complete until that happens
  • OpenEcomp name space change (APPC-13)
    • Dependency on SDC to complete. Waiting on following to be available in Nexus.  <artifactId>openecomp-tosca-datatype</artifactId>
  • Code Coverage
    • Currently at 48.8%; will not hit 50% by Code Freeze on 3/29. Need more time.
• Sprint 4 was closed; anything not completed was moved to Sprint 5 or put into backlog
• WindRiver Dev lab
  • CDT configuration
    • Enviroment.ts is the name of the properties file.
    • All endpoints(URLS/ports) are supposed to be configured there.
  • DMaaP status?
    • Scott still working on this with Sunil; DMaaP sitll not useable in Beijing.
• Vacations:
  • I will be out next week: 4/2 - 4/6; Scott will run the call next Wed., 4/4/18
• Concern raised..
  • Code changes being introduced under junit or Sonar Jira's are extending beyond what is actually needed and some of these changes have broken run time functionaliy. How can we safeguard against this? Unless you have a very high degree of confidence and are extremely familiar with APPC code and functions, you should not be attempting to refactor the code.  Run time breaks are very difficult and virtually impossible to catch in a code reviews.

04/11/18 - APPC Project Weekly Minutes

Participants:Randa Maher;
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.
    

• 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

• Ramya to identify the minimum VNF AAI data that is needed to validate ScaleOut. The work around that was provided only addressed the template model name.

New Actions Items:

Agenda & Notes:

• Status on outstanding items
  
  • ODL upgrade (Patrick)
  • DMaaP issue (Ryan)
  • AAF Integration (Ryan)
  • Code Coverage
  • Security items from CLM report (Taka)
  • Stability retest on Beijing (Scott)
  • Resiliency (Aaron)
• Testing
  • Flow that will be validated by Integration: https://wiki.onap.org/display/DW/Manual+Scale+Out+Use+Case?preview=/25438344/28377562/image2018-3-21_16-36-18.png
  • Question from Marco: How do we know if Healthcheck and ConfigScaleOut request are successful?
  • Progress on testing in WindRiver Dev lab
  • Can we provide a demo to Marco?
• Upcoming milestone - RC0 on April 19.
• Misc items
  • Casablanca dates
    • Release Planning#CasablancaRelease
    • M1 = June 28, 2018  (Dev Start)
  • Beijing branching
    • Date?
    • Work items in prep: Upgrade to support Karaf 4
  • Casablanca
    
    • Release theme: "Deployability"
    • Dependency Driver work:
      • ODL upgrade to Nitrogen
      • MariaDB plus Galera
      • anything else?