Meeting Dates
- APPC Meeting Minutes
- 6/21/17 - APPC Project Weekly Minutes
- APPC Model Driven Approach - PMiller 6-22-17.mp4
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
- 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.
- 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 | Role | Allocation | Notes | |
Yes | Reuben Klein | Architect | 10% | Co-wrote proposal with Avi for APPC Release 1; will be acting as architect for Release 1 | |
Yes | Avi Chapnick | Architect | 10% | Co-wrote proposal with Reuben for APPC Release 1; will be acting as architect for Release 1 | |
No | Piyush Garg | Committer | ? | Need to follow-up for participation details | |
Yes | Hector Anapan | 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 | TSC | Part of Architecture sub-committer Will engage in testing support post August as resource availability opens up | ||
No | Vimal Begwani | 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 | Architecture/Consultant | Part of Architecture sub-committee | ||
Yes | Marcus Williams | 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 | APPC Consultant | |||
Yes | James MacNider | 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 | Contributor | 25% | Working closely with James | |
No | Alexis de Talhouët | ? | ? | OOO notification June, 19 until July, 3. Catherine will write to manager to see if Alexis can be a potential contributor | |
No | Rashmi Pujar | ? | ? | Catherine will write to manager to see if Alexis can be a potential contributor | |
No | Bin Yang | 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 | Architect | 10% | ||
Yes | Patrick Brady | Committer | 100% | Patrick has been prime for maintaining APPC repo and merging to date.. | |
Yes | Skip Wonnell - | Committer | 100% | Skip will also be a contributor as well as a committer | |
Yes | Randa Maher | Proposed PTL | 50% | ||
Yes | Joey Sullivan | Contributor | 25% | Working closely with James |
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.