18:01:09 <bh526r> #startmeeting gluon
18:01:10 <openstack> Meeting started Wed Aug 24 18:01:09 2016 UTC and is due to finish in 60 minutes.  The chair is bh526r. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:01:11 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
18:01:14 <openstack> The meeting name has been set to 'gluon'
18:01:22 <bh526r> hello guys
18:01:49 <KamilRenczewski> Hello
18:01:55 <georgk> Hi
18:01:55 <bh526r> Hi Kamil
18:02:02 <bh526r> Hi Georg
18:02:32 <bh526r> #topic Roll Call and Introduction
18:02:55 <georgk> #info Georg Kunz
18:03:01 <KamilRenczewski> #info Kamil Renczewski
18:03:03 <bh526r> #info Bin Hu
18:03:31 <bh526r> #topic Admin Update
18:04:17 <bh526r> #info we plan to have a Gluon F2F session in Barcelona
18:04:57 <bh526r> #info Currently OpenStack is allocating rooms for official projects, which is the priority
18:05:59 <bh526r> #info Bin communicated with Thierry, and agreed that once the room assignment for official projects has been done, if there is more spaces available, we can get it
18:06:39 <bh526r> #info Bin Hu Right now, the space in Barcelona is tighter compared to prior summits
18:06:41 <pcarver> #info Paul Carver
18:06:54 <bh526r> welcome Paul
18:08:09 <bh526r> another topic is that we need to ask for a slot in Nova and/or Neutron's meetings in Barcelona
18:09:06 <bh526r> #info Bin will also try to ask for a slot in Nova and/or Neutron's sessions in Barcelona to introduce Gluon
18:09:33 <bh526r> That's all of admin update.
18:10:06 <bh526r> #topic Summary of Face-to-Face Meeting on August 18 and 19
18:10:11 <georgk> thanks for th update
18:10:44 <bh526r> #info Gluon had an F2F meeting in Sunnyvale on 8/18 and 8/19.
18:11:05 <bh526r> #info The summary of discussion and conclusion is as follows:
18:11:12 <bh526r> welcome Jin.
18:11:25 <bh526r> Please #info your attendance
18:12:23 <bh526r> #info 1. Group discussed Gluon and Neutron Interaction Model. Group agreed and concluded that:
18:13:05 <bh526r> #info 1.1 A Proton stays the same. i.e. YAML -> { Pecan, DB Schema, etcd interface }
18:13:50 <bh526r> #info 1.2 Gluon will use Neutron plugin approach for North Bound, i.e. as a Gluon ML2 driver (core plugin)
18:14:15 <bh526r> #info - Gluon Wrapper ML2 Driver subclasses ML2 Driver
18:14:35 <bh526r> #info - If it is Proton port, sends to Proton
18:14:40 <jinli> #info JinLi join
18:14:53 <bh526r> #info - Otherwise, goes to normal ML2 driver
18:15:25 <bh526r> #info 1.3 Dummy network, subnets etc. object will be used by Gluon ML2 driver to satisfies Nova-Neutron relationship
18:15:49 <bh526r> #info 1.4 Backend SDN controllers will create network, subnets etc. in our desired way
18:16:15 <bh526r> #info 1.5 South Bound stays the same etcd to communicate via Shim Layers with SDN Controllers, i.e.:
18:16:37 <bh526r> #info - Gluon ML2 core plugin will connect with etcd to determine port ownership
18:16:55 <bh526r> #info - Contrail will use existing plugin/mechanism driver, which is at the same level as etcd
18:17:15 <bh526r> #info - Contrail’s mechanism driver needs to work with Gluon ML2 Core Plugin
18:17:41 <bh526r> #info 1.6 Tom and Jin will look into it if this really works or not
18:18:07 <georgk> one question
18:18:13 <bh526r> #info 2. Group discussed how to explore Gluon ML2 Core Plugin
18:18:25 <georgk> for my understanding
18:18:50 <bh526r> #info 2.1 Experiment with wrapping / sub-classing method
18:19:03 <bh526r> Sure, what is the question, Georg?
18:19:18 <georgk> have you guys looked into how you can ¨go to normal¨ ML2 driver
18:19:37 <georgk> or rather: is that part of Tom´s investigation?
18:19:42 <bh526r> Tom and Jin are looking into it.
18:19:56 <georgk> ok
18:20:01 <bh526r> Yes, that is part of Tom's investigation - how to implement this ML2 Plugin approach
18:20:35 <bh526r> Tom cannot join today, because of an overlapping meeting.
18:20:53 <bh526r> And he has been recovering from laptop issues in the past a few days
18:21:06 <georgk> ok, I see
18:21:19 <bh526r> #info - If successful, done
18:21:19 <KamilRenczewski> Another one from me:
18:21:19 <georgk> sorry for canceling yesterdays meeting by the way
18:21:33 <bh526r> Not a problem, Georg
18:21:37 <kamal___> #info Kamal Hussain
18:21:37 <bh526r> Yes, Kamil
18:21:42 <KamilRenczewski> Contrail should implement its own ML2 plugin or driver for gluon plugin?
18:23:06 <bh526r> Based on conversation with Nachi last week, Contrail's plugin is at the same level of Gluon Neutron Plugin
18:23:36 <bh526r> So it reuses its own ML2 plugin
18:23:50 <KamilRenczewski> OK
18:24:22 <bh526r> The challenge is there is still a need of shim layer in Contrail to sync up with etcd
18:25:17 <bh526r> #info 2.2 If not successful, we try to fix ML2 by working with Neutron ML2 team
18:25:37 <bh526r> #info - If successful, done
18:25:58 <bh526r> #info 2.3 If not successful, we will use Original Gluon Model, i.e. Nova-Gluon-Neutron
18:26:19 <bh526r> #info - Customization for commercial deployment
18:26:38 <bh526r> #info Tom and Jin look into it if this really works or not
18:27:10 <bh526r> #info 3. Group discussed Demo Scope for OpenStack Summit in Barcelona, and agreed:
18:27:35 <bh526r> #info 3.1 Multiple SDN Controller Backend Interoperability – use Proton
18:27:58 <bh526r> #info - New interaction Model with Neutron, compared to demo in OPNFV Summit
18:28:42 <kamal___> Regarding new usecases, Ian had mentioned Point to Point services. Any concrete examples on this?
18:28:50 <bh526r> #info - Create VM with two vNICs. Neutron Port (e.g Linux Bridge) and Gluon Port  (OVS, vRouter, etc)
18:29:17 <bh526r> #info 3.2 New service on-demand (new Proton/APIs generated on-demand)
18:29:39 <bh526r> #info - Dummy service implementation
18:30:15 <bh526r> #info 4. Group also discussed that we need to clean up Nova Plugin so that we can have Gluon as Neutron Proxy, which is our model today
18:30:38 <bh526r> #info Group recognized that it would take long time.
18:30:52 <bh526r> #info Ian will work on it, and in his to-do list
18:31:26 <bh526r> ok, that is pretty much the summary of what we discussed and agreed last week
18:31:38 <bh526r> any other question?
18:32:36 <bh526r> ok, let's move on
18:32:52 <bh526r> #topic New Blueprint Discussion
18:33:07 <bh526r> based on what we discussed last week, I created 2 BPs:
18:33:33 <bh526r> Gluon ML2 Plugin BP: https://blueprints.launchpad.net/python-gluon/+spec/gluon-ml2-plugin
18:33:54 <bh526r> Gluon Nova Plugin BP: https://blueprints.launchpad.net/python-gluon/+spec/gluon-nova-plugin
18:34:26 <bh526r> ML2 Plugin is assigned to Tom, and Nova Plugin is assigned to Ian
18:34:41 <bh526r> Any question?
18:35:05 <bh526r> #info Based on F2F discussion, 2 Blueprints were created:
18:35:24 <bh526r> One is for Gluon ML2 Plugin BP: https://blueprints.launchpad.net/python-gluon/+spec/gluon-ml2-plugin. This is assigned to Tom
18:35:38 <bh526r> #info One is for Gluon ML2 Plugin BP: https://blueprints.launchpad.net/python-gluon/+spec/gluon-ml2-plugin. This is assigned to Tom
18:36:02 <bh526r> #info The other one is for Gluon Nova Plugin BP: https://blueprints.launchpad.net/python-gluon/+spec/gluon-nova-plugin. This is assigned to Ian
18:36:27 <bh526r> Anu question and comments?
18:37:13 <bh526r> Shall we approve them so that Tom and Ian can officially work on it?
18:37:52 <georgk> ok, do we need to approve them officially?
18:38:17 <bh526r> We need in record.
18:38:20 <georgk> :-)
18:38:22 <georgk> ok
18:38:46 <bh526r> If you need more time to read it, it is fine too and we can approve it next week
18:39:13 <georgk> no, I am good
18:39:30 <georgk> I am rather uninformed when it comes to the official ways of working
18:39:31 <bh526r> Thank you.
18:39:37 <georgk> we can approve it
18:39:42 <bh526r> :)
18:39:47 <georgk> do we need a quorum?
18:40:03 <pcarver> The Nova one is pretty vague. Shouldn't it have more detail in it?
18:40:13 <bh526r> Good question.
18:40:27 <bh526r> We can ask Ian to add more details in it.
18:40:41 <pcarver> The ML2 one seems ok
18:41:15 <bh526r> I propose to approve the Gluon ML2 Plugin BP.
18:41:21 <pcarver> +1
18:41:42 <KamilRenczewski> +1
18:42:18 <georgk> +1
18:42:43 <bh526r> Great, and thank you. Gluon ML2 Plugin BP is approved
18:42:49 <bh526r> I will communicate with Ian to add more details in Nova Plugin BP
18:43:20 <bh526r> #info Gluon ML2 Plugin BP: https://blueprints.launchpad.net/python-gluon/+spec/gluon-ml2-plugin is approved unanimously
18:43:40 <bh526r> #info Bin will communicate with Ian to add more details in Nova Plugin BP
18:43:52 <bh526r> Thank you
18:44:04 <bh526r> #topic Tracking Progress of PoC
18:44:41 <bh526r> In F2F meeting last week, it was indicated that for PM purpose, Jira is a better tool than Launchpad
18:45:07 <bh526r> So I created a JIRA ticket under OPNFV NetReady project to track PoC
18:45:28 <bh526r> This is also in line with NetReady's role of originating PoC
18:45:44 <bh526r> https://jira.opnfv.org/browse/NETREADY-21
18:46:09 <bh526r> The fixed version field is empty so it won't be mixed with any OPNFV releases
18:46:19 <pcarver> I assume this is PM for the surrounding non-programming tasks, right?
18:46:44 <bh526r> The label is OpenStack-Gluon to group all related tickets together
18:46:48 <pcarver> Launchpad + Gerrit would be used to track all coding activity I hope?
18:47:23 <bh526r> Yes, coding is under the ML2 Driver BP and tracked by Gerrit in OpenStack, of course
18:47:33 <pcarver> Jira makes sense for things that don't belong under Git
18:47:45 <bh526r> Jira is for all tasks, including logistics
18:47:54 <pcarver> ok. Thanks makes sense
18:48:22 <pcarver> But we should use Launchpad whiteboard to track all Gerrit reviews associated with each blueprint
18:49:02 <pcarver> Jira for tasks, activities that aren't in the form of Git commits
18:49:13 <bh526r> Coding related will be done in Gerrit and BP/Launchpad
18:49:30 <bh526r> That's why we created the BP for this coding
18:49:39 <pcarver> Coding and I assume also documentation. We should keep documentation under Git as well.
18:49:49 <bh526r> In Jira, I also created a story under the PoC Epic: https://jira.opnfv.org/browse/NETREADY-22
18:50:17 <bh526r> which reference back to BP for all coding related work, and documentation
18:50:56 <bh526r> So Jira is for PoC related tasks
18:51:28 <bh526r> And the coding and documentation related task is referenced back to BP so that those will be tracked in Gerrit and BP
18:51:57 <pcarver> That sounds good
18:52:57 <georgk> yes, sounds good
18:53:08 <bh526r> #info A JIRA ticket was created as PM tool for PoC: https://jira.opnfv.org/browse/NETREADY-21
18:53:35 <bh526r> #info Note that it is only for PoC related tasks, including logistics and other non-coding tasks
18:54:16 <bh526r> #info Coding the documentation related tasks are referenced back to BP so that those will be tracked in Gerrit and BP/Launchpad in OpenStack
18:55:21 <bh526r> #info For example, a story of Gluon ML2 Driver in JIRA references back to Gluon ML2 Driver BP: https://jira.opnfv.org/browse/NETREADY-22
18:55:53 <bh526r> #info Details of the Gluon ML2 Driver work will be tracked in Gerrit and BP/Launchpad
18:56:28 <bh526r> #info Once the coding and documentation are completed, JIRA will merely change ths status to "Resolved".
18:57:06 <bh526r> That's all for today from my side
18:57:21 <bh526r> Any question/suggestion/comment?
18:57:59 <georgk> i am good
18:58:05 <bh526r> We are good. Thank you all and talk to you next week
18:58:08 <georgk> thanks for the update Bin
18:58:14 <bh526r> #info Meeting adjourned
18:58:18 <georgk> byw
18:58:20 <georgk> bye
18:58:22 <KamilRenczewski> Thanks for all the information
18:58:24 <KamilRenczewski> bye
18:58:24 <bh526r> Thank you Georg and have a good night
18:58:31 <bh526r> Bye all
18:58:36 <bh526r> #endmeeting