14:17:35 <ChrisPriceAB> #startmeeting OpenDaylight OPNFV monthly sync
14:17:35 <odl_meetbot> Meeting started Thu Mar 19 14:17:35 2015 UTC.  The chair is ChrisPriceAB. Information about MeetBot at http://ci.openstack.org/meetbot.html.
14:17:35 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:17:35 <odl_meetbot> The meeting name has been set to 'opendaylight_opnfv_monthly_sync'
14:17:40 <ChrisPriceAB> #chair dneary
14:17:40 <odl_meetbot> Current chairs: ChrisPriceAB dneary
14:17:53 <dneary> Thanks
14:18:05 <dneary> Showing my 1st class organizational skills...
14:18:13 <ChrisPriceAB> #topic OpenDaylight integration using Docker
14:18:38 <ChrisPriceAB> #info Dan outlines the method used for running ODL in a container integrated to Neutron.
14:19:24 <ChrisPriceAB> #info Dan will hold a demo at 11:00 EST (daylight) showing the work done and how it is executing.
14:20:51 <ChrisPriceAB> #info 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.
14:21:36 <ChrisPriceAB> #info additionally removes dependancies on the JDK versions of the OPNFV components.
14:22:04 <ChrisPriceAB> #info dneary asks if there were any issues packaging opendaylight.
14:22:25 <ChrisPriceAB> #info Dan outlines the build and deploy (tarball) to docker flow he uses.
14:22:44 <ChrisPriceAB> #info dneary asks about timing issues between OpenStack/OpenDaylight
14:23:29 <dneary> etsi start-up script?
14:23:37 <ChrisPriceAB> #info dan outlines the flow of deployment, the use of a pre-built container with all dependancies handled provides a mechanism to manage race conditions.
14:23:45 <dneary> I'm sure I misheard
14:24:24 <ChrisPriceAB> #info dan says eventually he would like to handle config by API rather than pre-packaged for deployment
14:24:33 * ChrisPriceAB think you misheard
14:24:47 <dneary> ah
14:24:52 <dneary> /etc
14:25:09 * ChrisPriceAB maybe its-a start-up script. ?!?
14:25:18 <ChrisPriceAB> oh cool
14:25:19 <dneary> Which I pronounce "slash ee tee see"
14:25:25 <dfarrell07> Can someone drop the meeting info link here? VPN issues keeping me from reaching it...
14:25:35 <ChrisPriceAB> #info Dan has not done any validation of HA yet.
14:26:39 <ChrisPriceAB> no link dfarrell07, dial in: 800 451 8679 - code 915 507 3783#
14:26:47 <dfarrell07> ChrisPriceAB: thanks!
14:26:54 * ChrisPriceAB np
14:27:33 <ChrisPriceAB> #info Dan describes issues with tightly coupling OpenStack and OpenDaylight in the architecture with regard to resource and control resiliency
14:33:03 <dneary> ChrisPriceAB, What exactly can regXboi not disagree with?
14:34:21 * ChrisPriceAB dneary, I just wanted to remember that regXboi said that about a statement I made... Mind you I am good at stating the obvious.
14:34:45 <dneary> :-)
14:35:53 <ChrisPriceAB> #topic Future development in OpenDaylight for OPNFV releases.
14:36:25 <ChrisPriceAB> #topic dneary asks if there are additional areas we would want to collaborate on
14:37:07 <ChrisPriceAB> #info regXboi mentions there are tight dependencies on OpenStack when looking at OPNFV networking features.
14:37:57 <dneary> #info 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
14:44:55 * dfarrell07 can give a (super quick) Foreman update if needed
14:45:12 <ChrisPriceAB> #topic OpenDaylight overview of processes for engaging for future development
14:45:35 <ChrisPriceAB> #info dneary asks how we can propose features, is there a process we can follow?  how do we engage?
14:46:13 <dneary> #info In OpenDaylight, there is not a blueprint process, processes vary from person to persn, project to project
14:46:40 <dneary> #info Little formal architectural oversight and vetting of project roadmaps
14:47:39 <dneary> #info 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 expected
14:47:42 <dneary> accepted
14:47:51 <dneary> #undo
14:47:51 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x1bac1d0>
14:47:57 <dneary> #info 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
14:48:18 <ChrisPriceAB> #link https://wiki.opendaylight.org/view/Simultaneous_Release:Lithium_Release_Plan
14:48:18 <dneary> #info regXboi describes project offsets related to milestones.
14:48:37 <ChrisPriceAB> #info opendaylight release plan for Release plan
14:48:43 <ChrisPriceAB> #undo
14:48:43 <odl_meetbot> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x1bac710>
14:48:52 <ChrisPriceAB> #info opendaylight release plan for OpenDaylight Lithium
14:51:48 <ChrisPriceAB> #info example release plan for SFC in OpenDaylight
14:51:51 <ChrisPriceAB> #link https://wiki.opendaylight.org/view/Service_Function_Chaining:Lithium_Release_Plan
14:52:54 <ChrisPriceAB> #info an example of a release plan for a project that does not expose new functionality
14:52:57 <ChrisPriceAB> #link https://wiki.opendaylight.org/view/Openflow_Protocol_Library:Lithium_Release_Plan
14:53:39 <ChrisPriceAB> #info Brady describes the milestones for a project in OpenDaylight.
14:53:57 <dneary> #link https://wiki.opnfv.org/community/opendaylight
14:54:28 <dneary> I would like to see us expanding that page to a similar format to the OpenStack page
14:54:38 * ChrisPriceAB pound agree
14:58:40 <ChrisPriceAB> #info dneary wraps up the meeting stating rather than a regular monthly meeting we should likely establish meetings focused on specific topics
15:00:48 <ChrisPriceAB> #info dneary describes there is a topic filter on opnfv-tech-discuss for OpenDaylight related discussion topics.
15:01:07 <ChrisPriceAB> #endmeeting