18:00:10 <bh526r> #startmeeting gluon 18:00:11 <openstack> Meeting started Wed Mar 8 18:00:10 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:12 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:00:14 <openstack> The meeting name has been set to 'gluon' 18:00:23 <bh526r> #topic Roll Call 18:00:29 <bh526r> #info Bin Hu 18:00:32 <georgk> #info Georg Kunz 18:00:38 <pcarver> #info Paul Carver 18:00:42 <bh526r> Hi Georg 18:00:45 <bh526r> Hi Paul 18:01:02 <georgk> hi 18:01:23 <bh526r> #topic Admin Update 18:02:09 <bh526r> #info Since we successfully released 1.0.0 in stable/ocata, there have been 3 bug fixes 18:02:32 <jinli> Hi All 18:02:36 <bh526r> #info Patch 434726, 437253, and 438709 were approved and merged, and cherry picked to stable/ocata 18:02:37 <jinli> #info JinLi 18:02:39 <bh526r> Hi Jin 18:03:17 <bh526r> #info Based on the bug fixes, master was tagged 1.0.1, and stable/ocata was tagged 1.0.2 18:03:51 <bh526r> #info Both 1.0.1 and 1.0.2 are identical, but different tags on different commit-id in 2 different branches 18:04:27 <bh526r> #info moving forward, master will be focused on new features, and stable/ocata will be focused on bug fixes if any 18:04:55 <bh526r> #info we are on the right path, which is recognized by release management 18:05:29 <bh526r> #info Users will always clone from stable/ocata as the install guide was updated 18:05:51 <bh526r> #info And Linux distro needs to use the tag 18:06:33 <bh526r> any question? 18:08:11 <bh526r> #topic New "Network Type" in Neutron 18:09:11 <bh526r> #link https://bugs.launchpad.net/neutron/+bug/1664466 18:09:11 <openstack> Launchpad bug 1664466 in neutron "[RFE] Neutron API enhancement - add optional attribute to network" [Undecided,New] 18:09:28 <bh526r> #info This was discussed with Neutron in PTG 18:10:34 <bh526r> #info Ian and Sukhdev are working on implementation solution to drive it into Neutron 18:10:58 <bh526r> any question? 18:11:41 <bh526r> #topic Outstanding Patches 18:11:59 <bh526r> #info One is Test Case for “gluon/api/root.py” 18:12:12 <bh526r> #link https://review.openstack.org/#/c/429140/ 18:12:27 <bh526r> #info Jin abandoned it 18:13:25 <bh526r> #info Another one is to remove elements from core plugin that are simply pass-through 18:13:39 <bh526r> #link https://review.openstack.org/#/c/430446/ 18:13:50 <bh526r> #info Ian is still working on resolving the comments 18:14:24 <bh526r> #info 3rd one is devstack plugin 18:14:27 <bh526r> #link https://review.openstack.org/#/c/404069/ 18:14:49 <bh526r> #info This is for Pike, and Ian is continuing to work on it 18:15:55 <bh526r> any question? 18:16:17 <bh526r> #topic Planning for Gluon Pike Release 18:16:26 <bh526r> #link https://wiki.openstack.org/wiki/Gluon/Tasks-Pike 18:16:39 <bh526r> #info This was shared last week. Any comments? 18:18:35 <bh526r> #info All are encouraged to review the task list for Pike, and we can assign the tasks to individuals. 18:19:11 <bh526r> #topic Planning for OpenStack Summit "Forum" in Boston 18:19:21 <bh526r> Any suggestions? 18:21:04 <bh526r> #info More information regarding Forum is here: 18:21:07 <bh526r> #link http://lists.openstack.org/pipermail/openstack-dev/2017-March/113459.html 18:22:43 <bh526r> #info There is also a brainstorming activity here: 18:22:47 <bh526r> #link http://lists.openstack.org/pipermail/openstack-dev/2017-March/113115.html 18:23:23 <bh526r> #info Examples of the types of discussions are: 18:24:18 <bh526r> #info (1) Strategic, whole-of-community discussions: with increased emphasis on issues that are relevant to all areas of the community. An example could be "Rolling Upgrades at Scale". 18:25:00 <bh526r> #info (2) Project-specific sessions: This is quite self-explanatory 18:25:52 <ildikov> bh526r: you might also be interested in looking into this planning etherpad for Telecom/NFV: https://etherpad.openstack.org/p/BOS-UC-brainstorming-Telecom&NFV 18:26:27 <ildikov> bh526r: sorry to interrupt :) 18:26:44 <bh526r> Cool, thank you for letting us know, ildikov 18:28:25 <bh526r> All - please think about it and propose topics to the Telecom/NFV, as well as perhaps a session of our own group there 18:29:31 <bh526r> #info All are encouraged to input topics to Telecom/NFV planning as well as a potential Gluon session 18:29:44 <bh526r> #link https://etherpad.openstack.org/p/BOS-UC-brainstorming-Telecom&NFV 18:29:58 <bh526r> Any other suggestions? 18:30:37 <ildikov> bh526r: np, please let me know if I can help with anything 18:30:53 <bh526r> Sure, thank you ildikov. 18:31:21 <bh526r> One potential issue is the logistics, i.e. room / space availability 18:31:40 <bh526r> Do you have any insight on how the room/space will be assigned? 18:32:21 <ildikov> bh526r: I think we're getting closer to have a view on that, but I need to ask to get details 18:32:35 <ildikov> I will get back to you on this one 18:33:00 <bh526r> great, perhaps you can share the details in the next a few meetings once you have those information 18:33:29 <bh526r> Thank you ildikov for your help 18:33:57 <bh526r> #topic AOB 18:34:33 <bh526r> #info I am thinking of a PoC in OpenStack Summit in Boston and OPNFV Summit in Beijing too 18:35:00 <bh526r> #info The potential scenario may include SFC, P2P network, or anything that is fancier 18:35:49 <bh526r> #info So please review the task list, and comment/add/revise so that we have more sufficient details of implementing in demoable PoC in 2 months 18:36:35 <bh526r> #Info Bin will communicate with OPNFV in terms of PoC in OPNFV booth in Boston 18:36:44 <ildikov> bh526r: latest info is on the ML: http://lists.openstack.org/pipermail/openstack-dev/2017-March/113459.html 18:36:53 <bh526r> #info And Bin will submit a proposal for PoC in OPNFV Summit in Beijing 18:37:24 <bh526r> anything else? 18:37:27 <ildikov> #link http://lists.openstack.org/pipermail/openstack-dev/2017-March/113459.html - Rooms for the Forum in Boston 18:37:35 <bh526r> comments? suggestions? 18:38:28 <bh526r> Thank you Ildiko 18:39:11 <bh526r> any other thing/topic to discuss? 18:39:57 <bh526r> If nothing else, I sugges to adjourn and give back everyone 20 minutes 18:40:08 <bh526r> #info Meeting adjourned 18:40:18 <bh526r> #endmeeting