#opendaylight-meeting: OpenDaylight OPNFV monthly sync

Meeting summary

1. OpenDaylight integration using Docker (ChrisPriceAB, 14:18:13)
   1. Dan outlines the method used for running ODL in a container integrated to Neutron. (ChrisPriceAB, 14:18:38)
   2. Dan will hold a demo at 11:00 EST (daylight) showing the work done and how it is executing. (ChrisPriceAB, 14:19:24)
   3. The motivations for running in containers is to: avoid port conflicts, architecturally removing dependencies between ODL and OpenStack, the deployment of the controller for resiliency is better controller using containers. (ChrisPriceAB, 14:20:51)
   4. additionally removes dependancies on the JDK versions of the OPNFV components. (ChrisPriceAB, 14:21:36)
   5. dneary asks if there were any issues packaging opendaylight. (ChrisPriceAB, 14:22:04)
   6. Dan outlines the build and deploy (tarball) to docker flow he uses. (ChrisPriceAB, 14:22:25)
   7. dneary asks about timing issues between OpenStack/OpenDaylight (ChrisPriceAB, 14:22:44)
   8. dan outlines the flow of deployment, the use of a pre-built container with all dependancies handled provides a mechanism to manage race conditions. (ChrisPriceAB, 14:23:37)
   9. dan says eventually he would like to handle config by API rather than pre-packaged for deployment (ChrisPriceAB, 14:24:24)
   10. Dan has not done any validation of HA yet. (ChrisPriceAB, 14:25:35)
   11. Dan describes issues with tightly coupling OpenStack and OpenDaylight in the architecture with regard to resource and control resiliency (ChrisPriceAB, 14:27:33)
   
   
2. Future development in OpenDaylight for OPNFV releases. (ChrisPriceAB, 14:35:53)
   
3. dneary asks if there are additional areas we would want to collaborate on (ChrisPriceAB, 14:36:25)
   1. regXboi mentions there are tight dependencies on OpenStack when looking at OPNFV networking features. (ChrisPriceAB, 14:37:07)
   2. For example: Many Neutron blueprints are not part of current release schedule, spending cycles in ODL to implement code which will not be exposed through OpenStack (dneary, 14:37:57)
   
   
4. OpenDaylight overview of processes for engaging for future development (ChrisPriceAB, 14:45:12)
   1. dneary asks how we can propose features, is there a process we can follow? how do we engage? (ChrisPriceAB, 14:45:35)
   2. In OpenDaylight, there is not a blueprint process, processes vary from person to persn, project to project (dneary, 14:46:13)
   3. Little formal architectural oversight and vetting of project roadmaps (dneary, 14:46:40)
   4. ChrisPriceAB proposes that OPNFV comes to ODL with similar blueprints to what we submit to OpenStack, which will allow us to be a good citizen and increase our odds of having features accepted (dneary, 14:47:57)
   5. https://wiki.opendaylight.org/view/Simultaneous_Release:Lithium_Release_Plan (ChrisPriceAB, 14:48:18)
   6. regXboi describes project offsets related to milestones. (dneary, 14:48:18)
   7. opendaylight release plan for OpenDaylight Lithium (ChrisPriceAB, 14:48:52)
   8. example release plan for SFC in OpenDaylight (ChrisPriceAB, 14:51:48)
   9. https://wiki.opendaylight.org/view/Service_Function_Chaining:Lithium_Release_Plan (ChrisPriceAB, 14:51:51)
   10. an example of a release plan for a project that does not expose new functionality (ChrisPriceAB, 14:52:54)
   11. https://wiki.opendaylight.org/view/Openflow_Protocol_Library:Lithium_Release_Plan (ChrisPriceAB, 14:52:57)
   12. Brady describes the milestones for a project in OpenDaylight. (ChrisPriceAB, 14:53:39)
   13. https://wiki.opnfv.org/community/opendaylight (dneary, 14:53:57)
   14. dneary wraps up the meeting stating rather than a regular monthly meeting we should likely establish meetings focused on specific topics (ChrisPriceAB, 14:58:40)
   15. dneary describes there is a topic filter on opnfv-tech-discuss for OpenDaylight related discussion topics. (ChrisPriceAB, 15:00:48)

Action items

1. (none)

People present (lines said)

1. ChrisPriceAB (38)
2. dneary (19)
3. odl_meetbot (6)
4. dfarrell07 (3)