APPC Meeting Minutes

Meeting Dates

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

• APPC Meeting Minutes

• APPC Meeting Minutes

• 07/06/17 - APPC Restart Overview slides
• APPC Meeting Minutes
• 07/12/17 - APPC Project Weekly Minutes

6/19/17 - APPC Project Kick-Off

Meeting: APPC Project Kick-Off

Date: 6-19-17

Participants:

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

Agenda & Notes:

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

Decisions/Working agreements:

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

Action Items

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

APPC Team for Release 1

6/21/17 APPC Project Weekly Minutes

Agenda

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

Plan for next meeting

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

Notes around today's discussion.

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

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

06/28/17 - APPC Project Weekly Minutes

Agenda

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

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

Action Items:

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

Notes:

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

07/03/17 - APPC/SDC Discussions

Agenda

• Review of Residential Broadband vCPE with the SDC team

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

Key Notes

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

Action Items:

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

07/05/17 - APPC Project Weekly Minutes

Agenda

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

Participants:

Notes:

• Review items from checklist

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

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

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

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

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

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

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

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

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

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

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

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

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

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

07/06/17 - Meeting with MultiVIM team

Material reviewed attached.

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

07/12/17 - APPC Project Weekly Minutes

Agenda:

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