Versions Compared

Key

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

...

07/05/17 - APPC Project Weekly Minutes

Agenda (draft)

  • 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