/
APPC Meeting Minutes - (Jun'17 - May'18)

APPC Meeting Minutes - (Jun'17 - May'18)

Owned by Randa Maher
Last updated: Dec 19, 2018 by Takamune Cho

Meeting Dates


6/19/17 - APPC Project Kick-Off

Meeting: APPC Project Kick-Off

Date: 6-19-17

Participants:

Agenda & Notes:

Decisions/Working agreements:

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

Action Items

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


APPC Team for Release 1

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

Plan for next meeting

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

Notes around today's discussion.

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


06/28/17 - APPC Project Weekly Minutes

Agenda

Action Items:

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

Notes:

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

07/03/17 - APPC/SDC Discussions

Agenda

  • Review of Residential Broadband vCPE with the SDC team

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

Key Notes

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

Action Items:

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

07/05/17 - APPC Project Weekly Minutes

Agenda

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

Participants:

Role

Name

Present

Email

Architecture

Reuben Klein

 No

rk1518@att.com

Architecture

Avi Chapnick

 No

avich@amdocs.com

Architecture

Vimal Begwani

 No

begwani@att.com

Architecture

Jamil Chawki

 No

jamil.chawki@orange.com

Architecture

Paul Bartoli

 No

pb2317@att.com

Architecture

Pat Velardo

 No

pv1753@att.com

Architecture

Paul Miller

 Yes

pm3608@att.com

Architecture

Alex Vul

 Yes

alex.vul@intel.com

Architecture

Scott Seabolt

 Yes

js9808@att.com

Committer

Marcus Williams

No

marcus.williams@intel.com

Committer

Piyush Garg

No

Piyush.Garg1@amdocs.com

Committer

Patrick Brady

No

pb071s@att.com

Committer

Skip Wonnell

Yes

kw5258@att.com

Contributor

Hector Anapan

Yes

ha076r@att.com

 Contributor

Rahul Sharma

Yes

rahul.sharma2@amdocs.com

 Contributor

James MacNider

Yes

James.MacNider@amdocs.com

 Contributor

Joey Sullivan

No

joey.sullivan@amdocs.com

 Contributor

Alexis de Talhouët

No

alexis.de_talhouet@bell.ca

 Contributor

Rashmi Pujar

No

rashmi.pujar@bell.ca

 Contributor

Spondon Dey

No

sd4351@att.com

Contributor (Test)

Eric  Debeau

No

eric.debeau@orange.com

Multi-VM SME/Consultant

Bin Yang

?

bin.yang@windriver.com

Contributor

Catherine Lefevre

Yes

cl664y@intl.att.com

Contributor

Sharon Chisholm

Yes

 sharon.chisholm@amdocs.com

Contributor

Michael Meller

Yes

michael.meller@amdocs.com


Notes:

  • Release 1 key goals
    1. Consume all the code contributions, large part coming end of July. Deliver on the model driven design and additional features
    2. Support VM Restart for vCPE use case
    3. Support vDNS/vFW
  • Scope for Release 1 - specifics
    • Consume all code contributions [stories in backlog - need to update/complete adding stories - Action: Randa to update]
    • Upgrade to Carbon to stay aligned with SDNC
      • Need to validate/confirm with Dan Timoney from SDNC team that this is indeed the plan for R1
      • If so, Need to raise as a risk for APPC - could have multiple side effects that could impact timeline.
      • Drop date date for ODL Docker needed from SDNC would be 8/4
      • Working to get confirmation from Dan
    • Support vCPE Use Case for VM level restart
      • Need DG for VM Restart
        • What is needed to make this work… ?
      • How do we test -
        • Will we depend on Integration team to validate, or
        • Can we connect Integration lab to our APPC in  TLAB?
      • Action: Need details on the vCPE - are they running on hardware or Openstack?  -  schedule call for Monday w/Vimal & Brian -
        • Randa following up to see if we can setup a review on Monday at 11AM EST if that works.
    • Integration with MultiVIM
      • Discussion taking place with MultiVIM team to see how APPC is impacted by this change.
      • Meeting planned for tomorrow (Thurs @11AM EST; working to get CDP-PAL SME to present CDP-PAL, Scott will provide flow sample for APPC.
      • Demo proposal - VM/VNF restart of vDNS/vFW via MultiVIM ?   Need to discuss in more detail
    • Integration with OOM
      • Per Catherine, Objectives for release 1 based on OOM call earlier today:
        1. Want to move to container paradigm using Kubernetes - will provide guidelines to teams to move from Docker to Kubernetes
        2. Will work with team to prioritize - not sure if APPC be on the priority list
      • ECOMP Controller proposal is not part of release 1; will be considered for Release 2
      • Hector has been involved with OOM
        • Bell Canada used Kubernetes template to do test - template of ONAP based on Heat templates
        • We want to keep APIs generic, multiple approaches can be taken (ECOMP SDK & OOM, Robot Framework, etc..)
        • Action: Hector will setup a session with John Ng and Nicolas Hu to discuss OOM.
      • Need to see how APPC can contribute to OOM -
        • Action to AMDOCS team (Michael Meller & Sharon C. to see how  APPC would interplay with OOM
    • Need clear list of all API available for Release 1 and their type - Scott is working with team to get this.
    • Lab readiness (T-LAB)
      • T-Lab setup for vDNS/vFW
      • SDC & AAI integration..  ? What VNFs do we on-booard? Where do we get data?
      • Lab Status:
        • People are still working on this, but should be done this week. Action: Hector will follow-up on status.
    • Documentation
      • The Documentation project is will provide guidance on how documentation should be done in ONAP; however, each project is responsible for updating their documentation per release
      • When Documentation Project will have their recommendation and tools in place  is TBD at this point.
      • You can refer to their project page to see what is under consideration.
      • APPC has the following documents that will need to be updated for Release 1
    • HA/Resiliency stories identifications [items for roadmap]
      • Cluster deployment
      • Geo-redundancy
      • Note that nothing is being committed for release 1 related to this area, this item is only about having the conversations and contributing stories to the backlog for future releases
    • Replace openecomp with onap [APPC-13]
        • Any volunteers to start working on this?
    • Educational Video


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?

Notes:

  • ODL Version for R1
    • Confirmed with SDNC team - they will be using Carbon release of ODL for R1.
    • ODL Docker will not be available until end of July.
    • SDNC-26 (ODL upgrade) - ETA is end of July
    • APPC Story needed:  Need story to upgrade ODL version to Carbon
  • vCPE Use Case
  • Code Contributions -
    • Upcoming code contribution from AT&T pre-requisite for vCPE use case support, teams working to get that submitted
    • awaiting ETA  (restart DG key)
      • Action: Follow-up with Scott on the list of DGs being open-sourced
  • Labs
    • T-Lab: Lab prep in progress - Spondon working on this - availability date TBD
    • T-lab still waiting on servers… not likely to be ready this week
    • T-Lab lab will be available externally via VPN
    • Integration team discussion with WindRiver for a possible development lab for pairwise testing… more details pending.
      • They are taking images from Jenkins (latest image) to stand up lab…..
      • Generating jira issues if they run into problems
      • Focusing on e2e connectivity at the moment, using the demo use cases to validate lab.
  • MultiVIM
    • Scope for R1 - MultiVIM proxies requests…
    • Need to confirm support for R1 from CDP-PAL development team
    • CDP-PAL is not part of ONAP and opensource available via github, so we need their agreement to partner on this release for any changes needed in CDP-PAL.
    • Reached out to development owner of CDP-PAL (Ram Koya), awaiting feedback from the team if they have capacity to support.
    • Assuming CDP-PAL is onboard, when would MultVIM target for readiness to start integration testing.
    • Action: Randa to check if there are any dependencies between Carbon  & CDP-PAL - checking with Varun
      • 7/18/19 update: No, there is no dependency between CDP-PAL and ODL version
    • Multivim: R1 is a short term goal to demonstrate integration with APPC, goal to minimize impact due to lack of bandwidth/resource on both sides,  but for R2 or beyond, long term approach is TBD, various options still under assessment - CDP-PAL, Cloudify, something else??Comment: If they move to a model approach, this is a much larger impact
  • OOM
    • Invited David (OOM PTL) to join us for next meeting (7/19)
    • OOM still waiting on seed code, which applications may be impacted is still not clear.
    • Question: Who is responsible for packaging app to work with OOM - does OOM take care of it or are instructions provided to each app to ensure proper packaging.
  • HA/Resiliency
    • Sharon has some suggestions for capabilities around resiliency that she would like to review with the team.
    • We will plan to focus part of next meeting on this. Sharon will provide a presentation on resiliency/clustering
  • Other topics
    • Integration Testing with AAI & SDC - investigating to see what we can do locally
    • Areas of interest from the team? No feedback received.
    • Volunteer to start working on APPC-13 (replace openecomp with ONAP) - no volunteers yet
    • Update M1 template (Randa to update)
      • Update dependencies details
        • Add CDP-PAL support if MultiVIM is to be part of R1
      • Add risks
        • Carbon coming end of July, If SDNC runs into issues, could be later; the ODL docker is a fundamental dependency for APPC. 
    • SO & APPC interface
      • Questions received on workflow dependencies between SO and APPC. Response provided: Follow-up discussions will be scheduled as needed.

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

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

          https://lf-onap.atlassian.net/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

Notes:

  • OOM discussion with David
    • Question from previous meeting: Who is responsible for packaging app to work with OOM - does OOM take care of it or are instructions provided to each app to ensure proper packaging.
      • Answer: OOM wants each project team to create their own Kubernetes packages; however, for this first release, they will do it. 
    • For R1, scope for APPC is to deploy, upgrade using the 1 click API; however, don't anticipate any development needed on APPC side to support any activities planned for R1.
  • Presentations from Sharon on APPC Resiliency and HA, plus OAM feature contributions (refer to Epic APPC-38)
  • MultiVIM
    • No big update; waiting on confirmation from CDP-PAL development team on resource availability to support R1 proposal for APPC & MultiVIM integration via proxy.
    • Ram Koya & Varun Gudisena primes for CDP-PAL
  • LCM Generic Restart
    • Code submission in progress - APPC-88
    • This will provide the LCM VNF or VM restart capability needed for vCPE use case support.
  • ODL Version
    • Re-confirmed with Dan Timoney that Carbon is planned for SDNC R1
    • APPC-91 created to track the work i