15:00:35 <phrobb1> #startmeeting AdvisoryGroup
15:00:35 <odl_meetbot> Meeting started Thu May 21 15:00:35 2015 UTC.  The chair is phrobb1. Information about MeetBot at http://ci.openstack.org/meetbot.html.
15:00:35 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:35 <odl_meetbot> The meeting name has been set to 'advisorygroup'
15:00:54 <phrobb1> #chair odl-casey tbenzies
15:00:55 <odl_meetbot> Current chairs: odl-casey phrobb1 tbenzies
15:06:52 <odl-casey> #info Chris Donley
15:06:59 <odl-casey> #info Jay Etchings
15:07:10 <phrobb1> #info Margaret Chiosi
15:07:15 <phrobb1> #info Jamil Chawki
15:07:25 <phrobb1> #info Pedro Aranda
15:07:49 <odl-casey> #info Todd Benzies
15:08:11 <odl-casey> #info Kristi ??
15:08:16 <phrobb1> #info Chris Donley provided slides and presents a slide deck to the group
15:08:25 <tbenzies> #info Melissa Logan
15:08:28 <tbenzies> #info Kristi Tan
15:08:35 <phrobb1> thanks Todd :-)
15:08:50 <odl-casey> #info Phil Robb
15:08:55 <odl-casey> #info Casey Cain
15:09:56 <phrobb1> #info Cablelabs began to investigate SDN in 2012 but openflow wasn't quite the protocol they needed
15:10:37 <phrobb1> #info Cablelabs began to investigate ODL in Auguest of 13 with COPS to control legacy CMTSs
15:11:27 <phrobb1> #info they demo-ed their work at a trade show and got very strong positive feedback
15:11:55 <phrobb1> #info next moved the COPS plugin to Helium
15:12:32 <phrobb1> #info Cablelabs is now looking to expand work on ODL through OPNFV with Intent interfaces and MEF needs
15:14:31 <phrobb1> #info (slide 4) VNE arch. Cablelabs wants to help develop common open APIs that the Cable industry can use
15:16:00 <phrobb1> #info (slide 5)  Cablelabs wants to implement virtual "Customer Premise Equipment" CPE on ODL
15:16:29 <tbenzies> #link https://wiki.opendaylight.org/images/e/eb/ODL-AG-CableLabs_update.pdf
15:16:52 <phrobb1> #info (slide 7) virtualizing CPE functions in the home (they also want to do the same for businesses as well)
15:17:44 <phrobb1> #info need strong protocols between the MSO and the subscriber home (cable gateway)
15:17:47 <tbenzies> #info Chris Luke
15:18:35 <phrobb1> #info (slide 8)  CableLabs has a revised version of PCMM in Lithium, and adding the MEF plugin by Beryllium
15:19:37 <phrobb1> #info feedback for ODL - Onboarding is difficult… the community is very helpful but the documentation and tooling needs improvement
15:20:23 <phrobb1> #info a dev left the co at the end of the year.  Updating the PCMM proj we had difficulties because the old dev is the only one that had commit rights
15:21:17 <phrobb1> #info the SAL is a key differentiator for ODL… supporting multiple SB protocols in parallel
15:22:01 <phrobb1> #info very strong interest in Intent but feels that it's a bit focused on datacenter
15:22:58 <phrobb1> #info need more constructs for operator… layered subscriber models, parent/kid access, and device differences… xbox, pc, tablet etc.
15:23:29 <phrobb1> #info more focus on service APIs
15:24:33 <phrobb1> #info Q: in a proj with Huawei doing intent with NEMO model that may fit the net operator better than ONF Intent model today
15:25:29 <phrobb1> #info Pedro is who is working with Huawei
15:26:03 <phrobb1> #info Jamil asks on slide 6 is it legacy or also new service deploy?…
15:26:41 <phrobb1> #info A: started with Legacy and ODL, now looking at OpenStack through OPNFV for more service deploy
15:27:30 <odl-casey> #info Q: Are you going to use PCMM or Netconf?
15:28:04 <phrobb1> #info what is the relationship between CableLabs and the member orgs?
15:28:31 <odl-casey> #info A: PCMM is a better solution for them
15:28:47 <phrobb1> #info Cablelabs does research for building the models then help the vendors and MSO to develop on top of the models
15:29:59 <phrobb1> #info Q: MEF services in ODL?.. A: through OPNFV working to put the service inside ODL for MEF services.  Took it to MEF and they strongly support the effort
15:30:35 <phrobb1> #info MEF part now using OVSDB looking for "tier 69?" in the future
15:31:01 <phrobb1> #info Q: is there a service orchastrator in the VCPE use case?
15:31:12 <phrobb1> #info A: yes, openstack is the pick now
15:31:37 <phrobb1> #info choice for them is "where to put the VM"… in the MSO or in the home of the home gateway
15:32:42 <phrobb1> #info OpenStack is not so good at multi-site and easy distributed deployment of VMs on a physical wet of HW…
15:33:10 <phrobb1> #info OpenStack feels that such orchestration should be done outside of OpenStack
15:33:42 <phrobb1> #info Orange has a similar config OVSDB & NETCONF for config of their net
15:35:40 <phrobb1> #info A: Neutron is not supporting complex net pieces well, trying to come up with a vision of simple neutron to pass request to app to drive a controller… does the group have thoughts on interface from ODL to neutron… Ed Warnike proposed something in the 10 minute design session but more wil be done as follow up
15:36:26 <phrobb1> #info the telco/NFV group in openstack  is where those types of discussion happen, but that group is talking about small incremental changes instead of looking at the problem statement as a whole
15:38:14 <phrobb1> please take notes
15:38:33 <odl-casey> Ok, I wasn't sure who was talking.  :)
15:40:02 <odl-casey> #info OpenStack talks about developing a more generic Neutron plugin to allow more controller flexability.
15:41:27 <odl-casey> #info Talks about adding abstraction to Neutron and improving the Intent.
15:44:35 <odl-casey> #info OpenStack reached out to Ericson, Brocade, Cisco about continuing the discussion about a Neutron Interface, abstraction and intent
15:46:15 <odl-casey> who???  Looked at NEMO and found it very promising.  Didn't find ONF to be enough.
15:47:55 <odl-casey> #info Q: ODL was asked how it positioning to be the controller of choice and the differences from ONOS.
15:49:50 <odl-casey> #info A: ONOS is focused on a specific area. We want to continue to provide more abstraction and flexibility. We would see some common ground in the future.
15:52:55 <odl-casey> #info OpenStack talks about a Global Controller, and Optic Controllers, and local controllers.  Doesn't feel that the industry is ready for a single controller.
15:54:40 <odl-casey> #info OpenStack wants to get %70 of their infrastructure virtualized by 2020.
15:58:03 <odl-casey> #info Phil thanks everyone for their participation.
15:58:41 <odl-casey> phrobb1: You still here?
15:59:08 <phrobb1> yep
15:59:19 <phrobb1> shall I end the meeting?… anything else you want to document?
15:59:30 <odl-casey> I missed it it was talking about NEMO
15:59:54 <odl-casey> He found it promising and didn't find ONF to be suitable.
15:59:58 <phrobb1> #info final note Pedro Aranda was discussing his team's experience with NEMO
16:00:05 <phrobb1> #endmeeting