Versions Compared

Old Version 123

changes.mady.by.user Randa Maher

Saved on

compared with

New Version Current

changes.mady.by.user Takamune Cho

Saved on

Key

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

Meeting Dates

6/19/17 - APPC Project Kick-Off

Meeting: APPC Project Kick-Off

Date: 6-19-17


6/19/17 - APPC Project Kick-Off

Meeting: APPC Project Kick-Off

Date: 6-19-17

Participants:

...

...

Present

Name

Email

Role

Allocation

 Notes

Yes

Reuben Klein

rk1518@att.com

Architect

10%

Co-wrote proposal  with Avi for APPC Release 1; will be acting as architect for Release 1

Yes

Avi Chapnick

avich@amdocs.com

Architect

10%

Co-wrote proposal  with Reuben for APPC Release 1; will be acting as architect for Release 1

No

Piyush Garg

Piyush.Garg1@amdocs.com

Committer

 ?

Need to follow-up for participation details

Yes

Hector Anapan

ha076r@att.com

Contributor

25%

Led open source effort for APPC for seed contribution;

Wants to continue as a contributor;

Hector is also part of integration project as a committer and interested in pairwise/integration testing

No

Jamil Chawki

jamil.chawki@orange.com

TSC


Part of Architecture sub-committer

Will engage in testing support post August as resource availability opens up

No

Vimal Begwani

begwani@att.com

Architecture/Consultant


Works for Paul Bartolli and his role is to put together a Controller guide; he's involved in all the controller work - Look to him to define what falls into APPC and what does not based on use cases. Also, if we need library support from other implementation, he may be the resource.

No

Paul Bartoli

pb2317@att.com

Architecture/Consultant


Part of Architecture sub-committee

Yes

Marcus Williams

marcus.williams@intel.com

Committer


35%

Marcus will be 100% on ONAP but his time will be spread between three projects, APPC, SDNC, CCSDK. I will contribute code and review code.

Yes

Pat Velardo

pv1753@att.com

APPC Consultant



Yes

James MacNider

James.MacNider@amdocs.com

APPC Consultant


James will be moving to another project (SDNC), will be providing consultation to other members who will contribute to APPC (Joey and Rahul)

Yes

Rahul Sharma

rahul.sharma2@amdocs.com

Contributor

25%

Working closely with James

No

Alexis de Talhouët

alexis.de_talhouet@bell.ca

?

?

OOO notification June, 19 until July, 3.

Catherine will write to manager to see if Alexis can be a potential contributor

No

Rashmi Pujar

rashmi.pujar@bell.ca

?

?

Catherine will write to manager to see if Alexis can be a potential contributor

No

Bin Yang

bin.yang@windriver.com

Multi-VM SME/Consultant


Bin is a committer of Multi-VIM/Cloud project; his focus will be to help identify the dependency/interaction between APP-C and Multi-VIM/Cloud so that we can synergy our effort.

Yes

Paul Miller

pm3608@att.com

Architect

10%


Yes

Patrick Brady

pb071s@att.com

Committer

100%

Patrick has been prime for maintaining APPC repo and merging to date..

Yes

Skip Wonnell -

kw5258@att.com

Committer

100%

Skip will also be a contributor as well as a committer

Yes

Randa Maher

rx196w@att.com

Proposed PTL

50%


Yes

Joey Sullivan

joey.sullivan@amdocs.com

Contributor

25%

Working closely with James


6/21/17 APPC Project Weekly Minutes

Agenda

...

      • 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

...

  • 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

...

  • 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

...

  • 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

...

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

...


07/06/17 - Meeting with MultiVIM team

Material reviewed attached.

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?

...

  • 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

...

  • 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://wikilf-onap.onapatlassian.orgnet/wiki/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

...

Functionality freeze

M2

August 03, 2017

Functionality freeze, no new visible functionality is to be added to the current ONAP release.

Each Project team has defined and documented their Functional Test Cases.

The vendor equipments have been delivered.

A stable document describing the API is documented and available in wiki.


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

...

  • 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
  • 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.
    • 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
  • Communication - IRC channel (#onap-appc)
  • 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
  • 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

...

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

...

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

...

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:

...

  • 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

...

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

...

  • 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

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?

...

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

...

  • 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

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

...

  • 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

...

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

...

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


RC1Oct 26, 2017Release Candidate 1

RC2Nov 9, 2017Release Candidate 2
Sign-OffRelease DeliveryNov 16, 2017Amsterdam Release Sign-Off


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…

...

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

  • 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
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyINT-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
    serverSystem Jira
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
    keyINT-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?

...

  • 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

...

  • 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://wikilf-onap.onapatlassian.orgnet/wiki/display/DW/Release+Planning#ReleasePlanning-ONAPBeijingReleasePlanning
      • 1/8 - Project Planning closure
      • 1/18 - M1 review
        • Must be completed for M1
          • Release Planning Template, filled out by 1/8
          • Release Planning Checklist: To be filled out by Jan 17
      • 4/5 - Code Freeze
      • 5/24 - Signoff
  • Projects in Beijing release: 
  • JIRA Management
    • If you port a defect fix back to Amsterdam - make sure Amsterdam AND Beijing are listed in Fix Version field.
    • When you submit Gerrit, move your JIRA ticket to Submitted, when changed is Merged, move your JIRA ticke to Delivered.
    • If you opened the Jira, you can close it once your changed is merged. If you did not open the ticket, reassign ticket to originator for closure (ticket should be in Delivered state when you assign back to originator)
    • Randa will try to create a quick cheat-sheet for reference.
  • Lab needs for Beijing - review with team; need for geo-red
  • Key changes with Beijing
    • Being proposed: All code contributions need to be accompanied with juni
  • Vacations in Dec/Meeting plans
    • Patrick out after 12/19 until 1/2
    • Skip out after 12/13 until 1/2
    • Randa out after 12/15 until 1/2
    • Meeting for 12/20 & 12/27 will most likely be canceled.
  • CSIT for R1 and R2
    • CSIT will run on snapshot for Amsterdam; running them on released version does not make sence.
    • CSIT will run on also run on Beijing (Master)

12/13/17 - APPC Project Weekly Minutes

Agenda:

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

...

  • Contributors for Beijing
  • F2F Santa Clara notes
  • 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
      serverSystem Jira
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keyAPPC-342
      ) and team members can create stories under this epic to document which module they will work on so we don't have duplicated effort.
  • Project Meetings:
    • Takamune Cho will host the 12/20 meeting.
    • 12/27 meeting will be canceled


12/20/17 - APPC Project Weekly Minutes

Agenda:

  • ONAP logging framework discussion
  • Beijing Release join effort

...

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

...

    • 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

...

  • Resiliency Testing (Sharon)
    • Sharon shared details on what SDNC is doing to meet the Resiliency testing recuirement for Level 2 (automated failover - single  site) - see slides
    • SDNC is leveraging  Kubernetes and OOM to address resiliency requirements
    • Advantage of using Kubernetes (vs. cluster capabiity of ODL) is that Kubernetes capability to recover a failed node
    • Healthcheck currently is at the pod level to determine if failover will be done or not. Sharon will confirm this.
    • Aaron Hay is the prime for the APPC Resiliency Epic (APPC-414)
    • APPC and SDNC teams will work closely together since there is a lot of synergy to be realized due to similar architectures & dependencies.
  • 72 hr test planning (Scott)
  • Code Coverage
    • Patrick provided a demo on using Junit and Mockito so that everyone can contribute to this requirements.
    • Slides and recording have been posted to wiki: 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
  • 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
  • Review JIRA - housekeeping items
    • We did not get to this topic, we will cover next meeting....
  • Misc - FOSS & Commit Process
  • Ansible code (DG/Adapter)
    • SDNC project has a need for this capability; the current plan is for them to clone this code into CCDSK for Beijing to support their Change Management use case.
    • However since this is common functionality, the proposal is to move this to CCSDK project long term. APPC will not do anything with this in Beijing, but something that needs to be addressed in Cassablanca. 

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)

...

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

...

  • License question
    • Do we need to change year in License text to reflect 2017 and 2018? Pending final input from....
  • Upcoming milestone
  • 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

...

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

    • 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

  • 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

...

  • 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

...

  • 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

...

  • 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

...

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

...

    • 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
    • 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.
  • Misc items
    • Updates from TSC: CLA and CAL

...

  • M3 Arch review planned on 3/6
  • M3 milestone = 3/8
  • M4 - new security checklist added. - will discuss this more next meeting
  • 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;

...

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


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

...

  • 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. 
      • 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.
    • 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
              serverSystem Jira
              serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
              keyAPPC-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 ?

...

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

...

  • M4 review planned for 3/29 with TSC
  • 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; Patrick Brady; Scott Seabolt; Aaron Hay; ry303t; Skip Wonnell; Ramya Balaji; Vidhya Nerella; Andrej Zan, Shubhada Vaze; Takamune Cho

Recording: APPC Weekly Poject Call 4-11-18.mp4

...

    • Progress on testing in WindRiver Dev lab
      • Scott and Ryan working to get DMaaP working in the Beijing/Carbon singleton lab. Anticipate having this resolved today.
      • Need to decide where we deploy Beijing/Nitrogen - do we replace Beijing/Carbon, replace Amsterdam, or spin up a new APPC?
      • Vidhya still having issues with access to the various VMs in the lab. Patrick and team will work with her to get past the issues.
      • Once items above are resolved, need to focus on ScaleOut testing.  Scott will start looking into the needed AAI data.
    • Can we provide a demo to Marco?
  • Upcoming milestone - RC0 on April 19.
  • Misc items
    • Casablanca dates
    • Beijing branching
      • Date?
      • Work items in prep: Upgrade to support Karaf 4
    • Casablanca
      • Release theme: "Deployability"
      • Dependency Driven work:
        • ODL upgrade to Oxygen
        • MariaDB plus Galera
        • Code Coverage
        • Upgrade to Karaf 4
      • anything else?
        • Allow support for multicloud integration beyond Generic_restart - move named query up to DGorchestrator - low priority; not likely to get into Casablanca.
  • Vacations
    • Patrick is out on Monday, 4/16
    • Ryan is out on Friday, 4/13
    • Taka is out from 4/12 through 4/17

App C success message and success return code can be found in the Karaf.log; however, they are debug logs.

status":{"code":400,"message":"SUCCESS - request has been processed successfully"}}

...

04/18/18 - APPC Project Weekly Minutes

Participants:Randa Maher; ry303t; Aaron Hay; Takamune Cho; Patrick Brady;  Vidhya Nerella; Andrej Zan, Shubhada Vaze; Vidya Jog
Recording: not recorded today

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
    • Update: 4/11/18: In-Progress
    • Update: 4/18/18: Team is still working through APPC w/Nitrogen stability; need to get past the issue with Request Handler not coming up. Until that's resolved, little testing can be done.
  • ry303t to investigate security vulnerabilty reported againt org.glassfish.grizzly, which is pulled in by CDP-PAL.
    • Update: 4/18/18: No update today, have more urgent items around AAF integration feature that still needs to be completed.

New Actions Items:

  • Takamune Chowill follow-up with Dan on SDNC project to see if he was able to successfully upgrade EELF. APPC has issues with version incompatibility with logback & sl4j and ODL.

Agenda & Notes:

  • Status on outstanding items
    • ODL upgrade (Patrick)
      • Changes to upgrade to Nitrogen completed. Story APPC-403 closed.
      • Additional testing in progress, but seeing some delays due to failing builds due to changes in CCSDK (CCSDK-242). Resolved today, so should be able to proceed with new builds.
      • Currently troubleshooting issue with Request Handler bundle not coming up.
    • DMaaP issue (Ryan)
      • We have not been able to progress on testing the fix for this issue; currently blocked by issue Patrick is looking into around the Request Handler not coming up. Until this issue is fixed, this validation is blocked.
    • AAF Integration (Ryan, Scott)
      • APPC AAF integration is blocked due to AAF-250. AAF team needs to get this resolved.
    • Security items
      • Reintroduce ugraded EELF to clear logback issue?
      • EELF is pulling versions of logback and sl4j that appear to be incompatible with Nitrogen.
  • Defects
    • APPC-854  (Aaron)
      • Reassigned to Patrick.
      • The docker manifest needs to be updated when we build our release dockers.
    • APPC-307 (Taka)
      • Taka to check with Scott to see if this can be retested in Beijing to see if issue still exists.
  • Testing
    • ConfigScaleOut (Ramya, Vidhya)
      • No progress on testing in WindRiver lab due to other blocking issues with APPC build.
    • CDT - did we get details from Amaresh?
    • Resiliency (Aaron)
    • Stability retest on Beijing (Scott)
      • Waiting on stable Beijing with Nitrogen to rerun the 72hour soak test
  • Upcoming milestone - RC0 on April 19.
    • APPC Beijing RC0 Checklist - Completed checklist and current disposition is: Not ready for RC0 yet,
      • Need to address failing jenkins jobs
      • Need to provide release version artifacts
      • Need to complete AAF story
      • Need to resolve issue with Request Handler bundle failure.
      • Failing CSIT we believe is related to LF performance issues. Requests are timing out. Hopefully with today's Nexus upgrade, CSIT tests will pass. Need to check tomorrow morning.

04/25/18 - APPC Project Weekly Minutes

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

Actions from last meeting:

  • Scott Seabolt & Aaron Hay to work together to pull together some lab diagrams for WindRiver lab setup for APPC usage (clustered vs non-clustered environments)
  • 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: 4/25/18: Still working through some blocking issues (see APPC-859)
  • ry303t to investigate security vulnerabilty reported againt org.glassfish.grizzly, which is pulled in by CDP-PAL.
    • Update: 4/18/18: No update today, have more urgent items around AAF integration feature that still needs to be completed.
    • Update: 4/25/18: Pending; working higher priority items at the moment.
  • Takamune Chowill follow-up with Dan on SDNC project to see if he was able to successfully upgrade EELF. APPC has issues with version incompatibility with logback & sl4j and ODL. (related to APPC-784)
    • Update: 4/25/18: Query sent, no response yet
  • Provide list of ODL plugins used by APPC (question raised by Andrej Zán)
    • Update: 4/25/18: odl.yangtools, odl.mdsal, broker-mdsal, odl.mdsal.model, odl.mdsal.features, odl.controller.mdsal, odl.mdsal.yang.binding, odl.controller.config.api, odl.ietf-inet-types, odl.ietf-yang-types, odl.yang.jmx.generator,  odl.sal.api.gen.plugin, odl.commons.opendaylight, odl.karaf.empty.distro, odl.sal.core.api

New Actions Items:

Agenda & Notes:

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

Integration

RC0

Avril 19, 2018

Release Candidate 0

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

Project Team focused its effort on:

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


RC1

May 3, 2018

Release Candidate 1


RC2

May 17, 2018

Release Candidate 2

Sign-Off

Release Delivery

May 24, 2018

Beijing Release Sign-Off

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

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


05/02/18 - APPC Project Weekly Minutes

Participants: Randa Maher;  Aaron Hay Scott Seabolt; Patrick Brady; ry303t; Takamune Cho; Vidhya Nerella; Ramya Balaji; Samuli Silvius; Shubhada Vaze; Mike Zinnikas, Andrej Zán, Jorge Hernandez-Herrero

Actions from last meeting:

  • 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: 4/25/18: Still working through some blocking issues (see APPC-859)
  • ry303t to investigate security vulnerabilty reported againt org.glassfish.grizzly, which is pulled in by CDP-PAL.
    • Update: 4/18/18: No update today, have more urgent items around AAF integration feature that still needs to be completed.
    • Update: 4/25/18: Pending; working higher priority items at the moment.
    • Update: 5/2/18: Closed, refer to APPC-841
  • Takamune Chowill follow-up with Dan on SDNC project to see if he was able to successfully upgrade EELF. APPC has issues with version incompatibility with logback & sl4j and ODL. (related to APPC-784)
    • Update: 4/25/18: Query sent, no response yet
    • Update: 5/2/18: Closed, logback version updated, security vulnerability removed.
  • Provide list of ODL plugins used by APPC (question raised by Andrej Zán)
    • Update: 4/25/18: odl.yangtools, odl.mdsal, broker-mdsal, odl.mdsal.model, odl.mdsal.features, odl.controller.mdsal, odl.mdsal.yang.binding, odl.controller.config.api, odl.ietf-inet-types, odl.ietf-yang-types, odl.yang.jmx.generator,  odl.sal.api.gen.plugin, odl.commons.opendaylight, odl.karaf.empty.distro, odl.sal.core.api
    • Update: 5/2/18: Closed, response provided
  • Aaron Hay will  create JIRA for heat deployment of CDT and submit changes
    • Update: 5/2/18: Closed, completed, refer to APPC-864
  • Takamune Cho to update APPC-656, update & close out remaining sub-tasks and create story for the items that carry to Casablanca. Ensure Security checklist is aligned with current CLM report.
  • Ramya, Vidhya, and Ryan to review the properties documentation to see if anything needs to be updated: http://onap.readthedocs.io/en/latest/submodules/appc/deployment.git/docs/APPC%20Properties/APPC%20Properties.html
    • Update: 5/2/18: Pending

New Actions Items:

  • Nothing new

Agenda & Notes:

  • Testing & pending items - APPC Beijing Testing Scope and Status
    • Regression
      • In progress; main thing left is to run through tests in OOM envirnoment
      • Ryan is working on the netconf mount for the vFW usecase
    • CDT testing
      • In-Progress, but need new APPC build to be deployed to Env to pick up Patrick's changes
      • Vidhya is focuing on this activity.
    • ScaleOut testing
      • Ramya continues to work on this; recevied the AAI data and instructions on access to Karaf from Scott and will plan to test via apidoc.
    • Resiliency
      • Aaron continunes to monitor changes in OOM and validating as needed.
      • Documentation related to this activity will target completion by 5/11.
    • Stability
      • Another 72 soak test was run over the weekend on Beijing w/Nitrogen. Everything went well; the system stayed up and handled transactions. Some errors were seen, but they were valid errors.
    • Pairwise per Integration list - APPC Pair Wise Testing for Beijing Release
      • APPC ↔ Policy, via DMaaP - will need to use SB07, we don't think we can reach Policy from our Dev environment. Jorge will share detail of the Policy request with Scott.
      • APPC ↔  vFW , via Netconf- Marco deployed vFW in our env, Ryan working to get netconf mount working correctly
      • APPC ↔  AAI, via API (OOM env) - in-progress - query to AAI worked, had issue in that environment after the AAI call; ran into issue in jdbc driver in OOM environment, works in Heat. APPC-876 opened to track this issue.
  • Defects
    • APPC-872 - not an APPC issue
      • This is really an issue with CCSDK, not APPC. Ticket moved to CCSDK project: CCSDK-261
    • APPC-874 - Not a bug
      • linked to OOM-1021 - Aaron worked with Borislav - both tickets closed now.
  • RC1 - Deadline = 5/3, still need to close out remaining items.


05/09/18 - APPC Project Weekly Minutes

Participants: Randa Maher;

Actions from last meeting:

New Actions Items:

Agenda & Notes:

  • Testing (APPC Beijing Testing Scope and Status)
    • CDT blocking issue
    • ConfigScaleOut testing
    • Stability
    • Resiliency/Scalability
  • Release of APPC artifacts and docker
  • Branching Beijing
  • Documentation
    • Properties update
    • CDT UG update
    • Release Notes
  • Upcoming Milestone: RC2 = 5/17/18

05/22/18 - APPC Project Weekly Minutes

Participants: Randa Maher; Beka Tsotsoria; Scott Seabolt; Veer Rajasekhar; Vidhya Nerella; Patrick Brady; ry303t; Łukasz Urbański; Marcus Williams; Mayank Gupta; Ramya Balaji; s.silvius; Shubhada Vaze; Takamune Cho

Actions from last meeting:

New Actions Items:

Agenda & Notes:

  • Testing (APPC Beijing Testing Scope and Status)
    • Testing completed for the most part; supporting integration team now
      • Demo'd to Integration team how APPC tested Resiliency
    • Continuing to run regression - Ramya testing out LCM VNF Healthcheck, investigating following bug: APPC-917.
  • Release of APPC artifacts and docker (Patrick)
    • We have a dependency on CCSDK release dockers; which they won't start until end of week; they also need to fix CCSDK-290
    • APPC Release activities will need to wait on CCSDK dockers availability.
  • Branching Beijing
    • Completed;
    • Beijing branch created
    • Master is now Casablanca Release - junit submissions can start being merged and fixes not gating Beijing.
  • Documentation
    • Release Notes - In progress
    • Need to fix some rst/link errors:  APPC-918 - In-progress
  • TSC decision to shift Beijing dates:
    • RC2 = 5/31/18  <=== Must be done by next week.
    • Sign-off = 6/7/18
  • Misc - round-robin...
    • netconf issues - Beka Tsotsoria (Nokia)
      • Using OOM environment; having issues getting CDT to connect to APPC runtime.
      • Need to wait on a couple of fixes that Patrick is working on...
    • Chef questions - Mayank Gupta (Amdoc)
      • follow-up via email or wiki for questions related to Chef; need to locate right resources with domain knowledge
      • First upgrade to Beijing release first and base question on working with Beijing;
      • Beijing is required if you want to use CDT to create our VNF appc artifacts.
    • Refer to APPC wiki for a lot of useful information on testing: APPC ONAP Testing Notes and APPC Beijing Testing