18:00:07 <bh526r> #startmeeting gluon
18:00:07 <openstack> Meeting started Wed Jan  4 18:00:07 2017 UTC and is due to finish in 60 minutes.  The chair is bh526r. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:00:08 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
18:00:10 <openstack> The meeting name has been set to 'gluon'
18:00:16 <pcarver> hello
18:00:20 <bh526r> #topic Roll Call
18:00:28 <bh526r> Hi Paul, happy new year
18:00:36 <bh526r> #info Bin Hu
18:00:37 <pcarver> same to you
18:00:44 <pcarver> #info Paul Carver
18:01:16 <bh526r> looks like only you and I now
18:02:02 <pcarver> yup, maybe so
18:02:07 <alraddarla_> #info Darla Ahlert
18:02:16 <alraddarla_> I'm here too :)
18:02:26 <bh526r> Hi Darla, happy new year
18:02:27 <pcarver> hi Darla
18:02:35 <alraddarla_> hello! Happy new year!
18:02:42 <kamal___> #info Kamal Hussain
18:02:50 <kamal___> happy new year all!
18:02:56 <bh526r> Hi Kamal, happy new year
18:03:09 <kamal___> thanks
18:03:19 <jinli> Happy New Year !
18:03:24 <jinli> #info JinLi
18:03:34 <bh526r> Happy new year Jin
18:04:46 <bh526r> #topic Admin Update
18:05:12 <bh526r> Looks like many groups are planning PTG meeting in the end of February
18:05:50 <bh526r> I communicated with Thierry from Foundation regarding those logistics in PTG, especially room assignment
18:06:20 <bh526r> The situation is that the PTG is organized around team rooms rather than around individual sessions.
18:06:51 <bh526r> Foundation will publish an event map, rather than an event schedule.
18:07:31 <bh526r> Because Foundation offers full rooms to teams (for multiple days), only official projects can get a full room assigned at the PTG.
18:08:14 <bh526r> Regarding unofficial projects like us, there are lots of hallway / lunch space that can be reused for discussions around other projects or not-yet-official initiatives.
18:08:47 <tomhambleton> #info Tom Hambleton
18:08:51 <bh526r> So they won't appear as a "room" on the event maps.
18:09:59 <bh526r> In a word, unofficial projects won't get a room in PTG. If we want to meet in PTG, we only can reuse hallway/lunch space
18:10:47 <bh526r> So that's the information I got so far for PTG
18:11:26 <bh526r> #info Many groups are planning PTG meeting in the end of February
18:11:43 <bh526r> #info Bin communicated with Thierry from Foundation regarding those logistics in PTG, especially room assignment
18:11:47 <Uri_> sorry for the ignorance, PTG???
18:12:00 <bh526r> Project Team Gathering
18:12:07 <pcarver> https://www.openstack.org/ptg/
18:12:22 <bh526r> It used to be design summit. Now it is a separate event PTG.
18:12:38 <Uri_> thx
18:12:40 <bh526r> #info The situation is that the PTG is organized around team rooms rather than around individual sessions.
18:12:55 <bh526r> #info Foundation will publish an event map, rather than an event schedule.
18:13:10 <bh526r> #info Because Foundation offers full rooms to teams (for multiple days), only official projects can get a full room assigned at the PTG.
18:13:30 <bh526r> #info Regarding unofficial projects like us, there are lots of hallway / lunch space that can be reused for discussions around other projects or not-yet-official initiatives.
18:13:54 <bh526r> #info In a word, unofficial projects won't get a room in PTG. If we want to meet in PTG, we only can reuse hallway/lunch space
18:14:26 <alraddarla_> Is anyone planning on going to PTG?
18:14:55 <bh526r> Let us think about the strategy to best use PTG
18:15:26 <bh526r> Ian is working on those Gluon patches in Nova, and potentially in Neutron
18:15:40 <pcarver> I'm planning to put in a travel request to go to the PTG. No idea yet on whether it's likely to be approved.
18:16:01 <bh526r> So he needs to go to PTG. But let me communicate with him to make sure he is going to.
18:16:32 <bh526r> Ian's presence is critical, in my view
18:17:03 <bh526r> so that he can work with Nova and Neutron team there to get our patch/BP move forward
18:18:00 <bh526r> Because we won't have a room there, only hallway/lunch space ca be reused, it may not be practical to have a formal Gluon team meeting there.
18:18:20 <rob_tao> I wonder if Gluon guys or others can just sit in the room of an official project, for example, Nova? If yes it would be helpful if some of us are there imho
18:18:26 <bh526r> That's an unfortunate reality
18:19:33 <bh526r> That's right. Instead of Gluon team meeting, our critical mass, such as Ian, need to be in Nova and Neutron's room to work on our topics with Nova and Neutron.
18:20:36 <bh526r> So whoever plans to go to PTG, that's the major goal.
18:22:33 <bh526r> #info So everyone is encouraged to think about the best way of working in PTG, and either plan to go to PTG and work with Nova and Neutron on Gluon topics, or stay in back office to get our work done.
18:23:50 <bh526r> #info Bin will take an action to communicate with Ian and convince him to go.
18:24:40 <bh526r> any other thoughts?
18:25:33 <pcarver> If my travel request is approved I expect to spend time working with the Neutron team on sub-projects, but would also join in any Gluon discussions that happen to take place ad hoc
18:26:08 <bh526r> That's great Paul. Thank you
18:26:41 <pcarver> It's probably not worth travelling for anyone who is strictly working on Gluon and isn't following activies ongoing in one or more of the official OpenStack projects.
18:28:15 <bh526r> I didn't send travel request for PTG, because under this situation, my presence there may not make a significant difference. So I would rather save some money. But Ian is critical.
18:29:26 <bh526r> ok, let's move on to other topics
18:29:51 <bh526r> #topic Gluon Tasks
18:29:57 <bh526r> routine record here
18:30:21 <bh526r> #Info Ocata Tasks
18:30:26 <bh526r> #link https://wiki.openstack.org/wiki/Gluon/Tasks-Ocata
18:30:40 <bh526r> #link https://etherpad.openstack.org/p/ocata-gluon-work-plan
18:30:53 <bh526r> #link https://etherpad.openstack.org/p/ocata-nova-neutron-session
18:31:44 <bh526r> #topic Status Update
18:32:09 <bh526r> #info 1. Authentication and Access Control
18:32:25 <bh526r> #link https://review.openstack.org/#/c/411000/
18:32:46 <bh526r> #info Patch 411000 was merged after our last discussion on Dec 21
18:33:06 <bh526r> #info 2. OpenContrail's Mechanism Driver
18:33:21 <bh526r> #link https://review.openstack.org/#/c/402071/
18:33:42 <bh526r> #info Pending on Juniper's new repo, and then update of instruction
18:34:05 <bh526r> #info 3. Testing
18:34:19 <bh526r> #link https://review.openstack.org/#/c/405689/
18:34:20 <kamal___> I am also working on more changes for the access control
18:34:58 <bh526r> #info Kamal is also working on fine tuning and polishing etc. more changes of access control
18:35:33 <bh526r> #info 405689 Jenkins failed. Georg and Darla had comments
18:35:49 <jinli> I am still working on that one
18:36:06 <bh526r> #info Jin is continuing working on it
18:36:25 <bh526r> #info 4. Shim Layer for Open Daylight
18:36:40 <bh526r> #link https://review.openstack.org/#/c/413011/
18:37:24 <tomhambleton> I am still reviewing it.  I have a few issues with it but overall it looks good
18:37:34 <bh526r> #info We discussed it on Dec 21. It looks good. The pending action is how to handle a prior patch 407388
18:38:05 <bh526r> #info We generally agreed that 407388 should be abandoned on Dec 21
18:39:15 <bh526r> #info Because Georg and Niko are still on vacation, we can wait for them to come back then formally abandon 407388.
18:39:34 <bh526r> #info Meanwhile, Tom will continue to review 413011.
18:40:21 <bh526r> #info All are also encouraged to continue to review 413011, and post comments there
18:41:01 <bh526r> #info 5. Gluon API Specification
18:41:14 <bh526r> #link https://review.openstack.org/#/c/411918/
18:41:57 <bh526r> #info Tom has done a great job, and also addressed many comments
18:42:16 <tomhambleton> I am getting some good feedback on this spec.  Hopefully we can get this approved in a week or so
18:42:28 <bh526r> Paul - you also just posted some comments before the meeting
18:42:50 <bh526r> Perhaps you can share some here with Tom too?
18:43:35 <pcarver> sure, I just had a few questions on things that weren't completely clear
18:43:42 <pcarver> I think it looks good overall
18:44:22 <pcarver> I think a few more examples would be helpful to clarify some of the bits that weren't entirely clear.
18:44:44 <tomhambleton> Will do,  I will process all of your comments
18:44:59 <bh526r> Great, thank you both Paul and Tom
18:45:18 <bh526r> #info 5. Bug Fixes
18:45:30 <bh526r> #link https://review.openstack.org/#/c/413307/
18:45:35 <pcarver> I'm planning to attempt to describe the current networking-sfc API and the Contrail SFC API in YAML
18:45:48 <bh526r> #info this was approved and merged after our last meeting on Dec 21
18:46:20 <bh526r> That is awesome, Paul.
18:47:04 <bh526r> #info 7. Devstack Integration (Work in Progress)
18:47:19 <bh526r> #link https://review.openstack.org/#/c/404069/
18:47:29 <bh526r> #info Ian is still working on it
18:47:52 <bh526r> #info 8. Add Entry Points to our Neutron Plugin (Work in Progress)
18:48:12 <bh526r> #link https://review.openstack.org/#/c/404390/
18:48:20 <bh526r> #info Ian is still working on it
18:48:36 <bh526r> #info 9. Nova Enhancement (Work in Progress)
18:48:52 <bh526r> #info This is what Ian is working with John in Nova team
18:49:29 <bh526r> #link https://review.openstack.org/#/c/390513/
18:49:52 <bh526r> #info Most recent comments were on Dec 13
18:50:34 <bh526r> #info On Jan 3, Nova PTL Matt suggested "This has to be moved to the nova/specs/pike/approved directory as ocata is closed for new specs."
18:51:17 <bh526r> #info So Ian will take action to continue it in Pike cycle.
18:51:55 <bh526r> #topic AOB
18:52:11 <bh526r> That's all of the update. Anything else to discuss?
18:52:49 <rob_tao> I would like to take this opportunity to bring up the multi-site setup for lab/future demo we talked about.  One Question I have for your guys: what should be used for the underlay encapsulation(GRE/MPLS/or...) between sites? Can we determine one only?
18:53:41 <tomhambleton> MPLSoGRE
18:54:01 <tomhambleton> That is what we did before
18:54:15 <rob_tao> Will it be used by all? ideally it is the case
18:55:11 <rob_tao> Anything on the Gluon lab status?
18:55:39 <bh526r> We can ask Georg once he is back from vacation next week
18:56:29 <rob_tao> ok then. thanks to all
18:56:29 <bh526r> anything else?
18:56:44 <bh526r> Thank you Robert
18:57:09 <bh526r> If nothing else, let's adjourn the meeting
18:57:17 <bh526r> #info Meeting adjourned
18:57:23 <bh526r> #endmeeting