#opendaylight-users: AdvisoryGroup

Meeting started by phrobb1 at 15:00:35 UTC (full logs).

Meeting summary

    1. Chris Donley (odl-casey, 15:06:52)
    2. Jay Etchings (odl-casey, 15:06:59)
    3. Margaret Chiosi (phrobb1, 15:07:10)
    4. Jamil Chawki (phrobb1, 15:07:15)
    5. Pedro Aranda (phrobb1, 15:07:25)
    6. Todd Benzies (odl-casey, 15:07:49)
    7. Kristi ?? (odl-casey, 15:08:11)
    8. Chris Donley provided slides and presents a slide deck to the group (phrobb1, 15:08:16)
    9. Melissa Logan (tbenzies, 15:08:25)
    10. Kristi Tan (tbenzies, 15:08:28)
    11. Phil Robb (odl-casey, 15:08:50)
    12. Casey Cain (odl-casey, 15:08:55)
    13. Cablelabs began to investigate SDN in 2012 but openflow wasn't quite the protocol they needed (phrobb1, 15:09:56)
    14. Cablelabs began to investigate ODL in Auguest of 13 with COPS to control legacy CMTSs (phrobb1, 15:10:37)
    15. they demo-ed their work at a trade show and got very strong positive feedback (phrobb1, 15:11:27)
    16. next moved the COPS plugin to Helium (phrobb1, 15:11:55)
    17. Cablelabs is now looking to expand work on ODL through OPNFV with Intent interfaces and MEF needs (phrobb1, 15:12:32)
    18. (slide 4) VNE arch. Cablelabs wants to help develop common open APIs that the Cable industry can use (phrobb1, 15:14:31)
    19. (slide 5) Cablelabs wants to implement virtual "Customer Premise Equipment" CPE on ODL (phrobb1, 15:16:00)
    20. https://wiki.opendaylight.org/images/e/eb/ODL-AG-CableLabs_update.pdf (tbenzies, 15:16:29)
    21. (slide 7) virtualizing CPE functions in the home (they also want to do the same for businesses as well) (phrobb1, 15:16:52)
    22. need strong protocols between the MSO and the subscriber home (cable gateway) (phrobb1, 15:17:44)
    23. Chris Luke (tbenzies, 15:17:47)
    24. (slide 8) CableLabs has a revised version of PCMM in Lithium, and adding the MEF plugin by Beryllium (phrobb1, 15:18:35)
    25. feedback for ODL - Onboarding is difficult… the community is very helpful but the documentation and tooling needs improvement (phrobb1, 15:19:37)
    26. 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 (phrobb1, 15:20:23)
    27. the SAL is a key differentiator for ODL… supporting multiple SB protocols in parallel (phrobb1, 15:21:17)
    28. very strong interest in Intent but feels that it's a bit focused on datacenter (phrobb1, 15:22:01)
    29. need more constructs for operator… layered subscriber models, parent/kid access, and device differences… xbox, pc, tablet etc. (phrobb1, 15:22:58)
    30. more focus on service APIs (phrobb1, 15:23:29)
    31. Q: in a proj with Huawei doing intent with NEMO model that may fit the net operator better than ONF Intent model today (phrobb1, 15:24:33)
    32. Pedro is who is working with Huawei (phrobb1, 15:25:29)
    33. Jamil asks on slide 6 is it legacy or also new service deploy?… (phrobb1, 15:26:03)
    34. A: started with Legacy and ODL, now looking at OpenStack through OPNFV for more service deploy (phrobb1, 15:26:41)
    35. Q: Are you going to use PCMM or Netconf? (odl-casey, 15:27:30)
    36. what is the relationship between CableLabs and the member orgs? (phrobb1, 15:28:04)
    37. A: PCMM is a better solution for them (odl-casey, 15:28:31)
    38. Cablelabs does research for building the models then help the vendors and MSO to develop on top of the models (phrobb1, 15:28:47)
    39. 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 (phrobb1, 15:29:59)
    40. MEF part now using OVSDB looking for "tier 69?" in the future (phrobb1, 15:30:35)
    41. Q: is there a service orchastrator in the VCPE use case? (phrobb1, 15:31:01)
    42. A: yes, openstack is the pick now (phrobb1, 15:31:12)
    43. choice for them is "where to put the VM"… in the MSO or in the home of the home gateway (phrobb1, 15:31:37)
    44. OpenStack is not so good at multi-site and easy distributed deployment of VMs on a physical wet of HW… (phrobb1, 15:32:42)
    45. OpenStack feels that such orchestration should be done outside of OpenStack (phrobb1, 15:33:10)
    46. Orange has a similar config OVSDB & NETCONF for config of their net (phrobb1, 15:33:42)
    47. 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 (phrobb1, 15:35:40)
    48. 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 (phrobb1, 15:36:26)
    49. OpenStack talks about developing a more generic Neutron plugin to allow more controller flexability. (odl-casey, 15:40:02)
    50. Talks about adding abstraction to Neutron and improving the Intent. (odl-casey, 15:41:27)
    51. OpenStack reached out to Ericson, Brocade, Cisco about continuing the discussion about a Neutron Interface, abstraction and intent (odl-casey, 15:44:35)
    52. Q: ODL was asked how it positioning to be the controller of choice and the differences from ONOS. (odl-casey, 15:47:55)
    53. 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. (odl-casey, 15:49:50)
    54. OpenStack talks about a Global Controller, and Optic Controllers, and local controllers. Doesn't feel that the industry is ready for a single controller. (odl-casey, 15:52:55)
    55. OpenStack wants to get %70 of their infrastructure virtualized by 2020. (odl-casey, 15:54:40)
    56. Phil thanks everyone for their participation. (odl-casey, 15:58:03)
    57. final note Pedro Aranda was discussing his team's experience with NEMO (phrobb1, 15:59:58)


Meeting ended at 16:00:05 UTC (full logs).

Action items

  1. (none)


People present (lines said)

  1. phrobb1 (44)
  2. odl-casey (21)
  3. odl_meetbot (4)
  4. tbenzies (4)


Generated by MeetBot 0.1.4.