Monday, 2016-11-28

*** bpokorny has quit IRC00:00
*** bpokorny has joined #openstack-meeting-400:02
*** thorst_ has quit IRC00:04
*** sdake has joined #openstack-meeting-400:15
*** sdake_ has joined #openstack-meeting-400:18
*** haleyb_ has joined #openstack-meeting-400:18
*** sdake has quit IRC00:19
*** bpokorny has quit IRC00:20
*** bpokorny has joined #openstack-meeting-400:21
*** sshnaidm has joined #openstack-meeting-400:23
*** bpokorny has quit IRC00:25
*** limao has joined #openstack-meeting-400:46
*** tovin07 has joined #openstack-meeting-400:48
*** tovin07_ has joined #openstack-meeting-400:49
*** thorst_ has joined #openstack-meeting-400:50
*** thorst_ has quit IRC00:50
*** thorst_ has joined #openstack-meeting-400:54
*** cwolferh has quit IRC00:55
*** thorst_ has quit IRC01:00
*** gongysh has joined #openstack-meeting-401:03
*** tovin07 has quit IRC01:04
*** cathrichardson has joined #openstack-meeting-401:04
*** gongysh has quit IRC01:07
*** cathrichardson has quit IRC01:09
*** tovin07 has joined #openstack-meeting-401:17
*** ricolin has joined #openstack-meeting-401:19
*** zhurong has joined #openstack-meeting-401:27
*** sdake_ has quit IRC01:37
*** hieulq has joined #openstack-meeting-401:44
*** sdake has joined #openstack-meeting-401:46
*** haleyb_ has quit IRC01:48
*** bobmel has quit IRC01:50
*** thorst_ has joined #openstack-meeting-401:57
*** ricolin has quit IRC01:57
*** baoli has joined #openstack-meeting-401:57
*** hippiepete has quit IRC01:59
*** reedip_ has joined #openstack-meeting-402:00
*** baoli has quit IRC02:02
*** thorst_ has quit IRC02:03
*** cathrichardson has joined #openstack-meeting-402:05
*** tovin07_ has quit IRC02:05
*** tovin07_ has joined #openstack-meeting-402:08
*** cathrichardson has quit IRC02:10
*** baoli has joined #openstack-meeting-402:12
*** baoli has quit IRC02:12
*** baoli has joined #openstack-meeting-402:12
*** baoli has quit IRC02:17
*** sdake has quit IRC02:21
*** Jeffrey4l has joined #openstack-meeting-402:28
*** markvoelker has joined #openstack-meeting-402:31
*** reedip_ has quit IRC02:31
*** sdake has joined #openstack-meeting-402:35
*** sdake_ has joined #openstack-meeting-402:41
*** gongysh has joined #openstack-meeting-402:45
*** sdake has quit IRC02:45
*** baoli has joined #openstack-meeting-402:46
*** cwolferh has joined #openstack-meeting-402:48
*** baoli has quit IRC02:48
*** thorst_ has joined #openstack-meeting-402:52
*** bobmel has joined #openstack-meeting-402:53
*** thorst__ has joined #openstack-meeting-402:54
*** thorst_ has quit IRC02:57
*** zhurong has quit IRC02:58
*** zhurong_ has joined #openstack-meeting-402:58
*** bobmel has quit IRC02:58
*** thorst__ has quit IRC03:02
*** cathrichardson has joined #openstack-meeting-403:06
*** limao_ has joined #openstack-meeting-403:10
*** cathrichardson has quit IRC03:11
*** limao has quit IRC03:13
*** gongysh has quit IRC03:14
*** julim has joined #openstack-meeting-403:41
*** cwolferh has quit IRC03:45
*** thorst_ has joined #openstack-meeting-404:04
*** iyamahat has joined #openstack-meeting-404:04
*** thorst_ has quit IRC04:05
*** yamamoto_ has joined #openstack-meeting-404:05
*** cathrichardson has joined #openstack-meeting-404:07
*** psachin has joined #openstack-meeting-404:10
*** cathrichardson has quit IRC04:12
*** links has joined #openstack-meeting-404:13
*** bobmel has joined #openstack-meeting-404:23
*** iyamahat has quit IRC04:26
*** numans has joined #openstack-meeting-404:27
*** bobmel has quit IRC04:28
*** cfarquhar has joined #openstack-meeting-404:34
*** cathrichardson has joined #openstack-meeting-405:08
*** thorst_ has joined #openstack-meeting-405:10
*** JRobinson__ is now known as JRobinson__afk05:11
*** cathrichardson has quit IRC05:13
*** thorst_ has quit IRC05:19
*** janki has joined #openstack-meeting-405:21
*** prateek has joined #openstack-meeting-405:51
*** bobmel has joined #openstack-meeting-405:54
*** bobmel has quit IRC05:59
*** cathrichardson has joined #openstack-meeting-406:09
*** cathrichardson has quit IRC06:14
*** thorst_ has joined #openstack-meeting-406:17
*** anilvenkata has joined #openstack-meeting-406:19
*** Julien-zte has joined #openstack-meeting-406:23
*** thorst_ has quit IRC06:24
*** Julien-zte has quit IRC06:24
*** Julien-zte has joined #openstack-meeting-406:25
*** JRobinson__afk is now known as JRobinson__06:26
*** Julien-zte has quit IRC06:29
*** Julien-zte has joined #openstack-meeting-406:30
*** Julien-zte has quit IRC06:32
*** Julien-zte has joined #openstack-meeting-406:32
*** oshidoshi has joined #openstack-meeting-406:35
*** Julien-zte has quit IRC06:38
*** Julien-zte has joined #openstack-meeting-406:39
*** Julien-zte has quit IRC06:43
*** Julien-zte has joined #openstack-meeting-406:44
*** sdake_ is now known as sdake06:47
*** alij has joined #openstack-meeting-406:50
*** trinaths has joined #openstack-meeting-406:51
*** zhurong_ has quit IRC06:56
*** zhurong has joined #openstack-meeting-406:57
*** Julien-zte has quit IRC06:57
*** Julien-zte has joined #openstack-meeting-406:58
*** nkrinner_afk is now known as nkrinner06:59
*** cathrichardson has joined #openstack-meeting-407:10
*** yamamoto_ has quit IRC07:11
*** dtardivel has joined #openstack-meeting-407:14
*** cathrichardson has quit IRC07:14
*** sdake_ has joined #openstack-meeting-407:22
*** makowals has joined #openstack-meeting-407:22
*** thorst_ has joined #openstack-meeting-407:23
*** sdake has quit IRC07:24
*** JRobinson__ has quit IRC07:24
*** thorst_ has quit IRC07:29
*** Julien-zte has quit IRC07:32
*** Julien-zte has joined #openstack-meeting-407:32
*** Julien-zte has quit IRC07:34
*** Julien-zte has joined #openstack-meeting-407:35
*** Jeffrey4l has quit IRC07:35
*** Julien-zte has quit IRC07:36
*** Julien-zte has joined #openstack-meeting-407:36
*** Jeffrey4l has joined #openstack-meeting-407:43
*** pcaruana has joined #openstack-meeting-407:45
*** irenab has quit IRC07:46
*** Julien-zte has quit IRC07:46
*** irenab has joined #openstack-meeting-407:47
*** Julien-zte has joined #openstack-meeting-407:48
*** janki is now known as janki|lunch07:49
*** matrohon has joined #openstack-meeting-407:52
*** ralonsoh has joined #openstack-meeting-407:53
*** irenab has quit IRC07:55
*** yamamoto_ has joined #openstack-meeting-407:55
*** irenab has joined #openstack-meeting-407:55
*** bobmel has joined #openstack-meeting-407:55
*** ishafran has joined #openstack-meeting-407:58
*** bobmel has quit IRC08:00
*** Julien-zte has quit IRC08:01
*** Julien-zte has joined #openstack-meeting-408:01
*** cathrichardson has joined #openstack-meeting-408:11
*** irenab has quit IRC08:12
*** irenab has joined #openstack-meeting-408:13
*** alij has quit IRC08:15
*** cathrichardson has quit IRC08:15
*** Julien-z_ has joined #openstack-meeting-408:21
*** sdake_ has quit IRC08:23
*** Julien-zte has quit IRC08:25
*** dimak has joined #openstack-meeting-408:39
*** alexchadin has joined #openstack-meeting-408:43
*** Julien-z_ has quit IRC08:45
*** Julien-zte has joined #openstack-meeting-408:45
*** cfarquhar has quit IRC08:45
*** bauwser is now known as bauzas08:47
*** alij has joined #openstack-meeting-408:49
*** xiaohhui has joined #openstack-meeting-408:53
*** Julien-zte has quit IRC08:54
*** jichen has joined #openstack-meeting-408:54
*** Julien-zte has joined #openstack-meeting-408:54
*** unicell1 has joined #openstack-meeting-408:55
*** lihi has joined #openstack-meeting-408:56
*** unicell has quit IRC08:57
*** alij has quit IRC08:59
*** alij has joined #openstack-meeting-408:59
*** oanson has joined #openstack-meeting-409:00
oanson#startmeeting Dragonflow09:00
openstackMeeting started Mon Nov 28 09:00:16 2016 UTC and is due to finish in 60 minutes.  The chair is oanson. Information about MeetBot at http://wiki.debian.org/MeetBot.09:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
dimakHello09:00
*** openstack changes topic to " (Meeting topic: Dragonflow)"09:00
openstackThe meeting name has been set to 'dragonflow'09:00
oansonHi.09:00
oansonWho's here for the Dragonflow meeting?09:00
ntr0pyHi09:00
lihiHi09:00
xiaohhuihello09:00
*** rajivk has joined #openstack-meeting-409:00
*** Julien-zte has quit IRC09:01
*** Julien-zte has joined #openstack-meeting-409:01
oansonAll right, let's get started09:02
oansonWe'll use the same agenda as last week.09:02
oansonIt's almost the same agenda, and I didn't have a chance to update it (Had a meeting this morning)09:02
irenabhi09:02
oanson#info dimak ntr0py liangy xiaohhui irenab in meeting09:03
oanson#info lihi is also in meeting09:03
oanson#topic Ocata roadmap09:03
*** openstack changes topic to "Ocata roadmap (Meeting topic: Dragonflow)"09:03
oanson#link SFC spec https://review.openstack.org/#/c/394498/09:03
*** ricolin has joined #openstack-meeting-409:03
oansonThis spec looks almost complete. I will pass is once this meeting is over09:03
yuli_sHello09:03
oansonI didn't have a chance to do that earlier.09:04
dimakThanks, I hope it will get merged today then09:04
oanson#link Chassis is alive spec https://review.openstack.org/#/c/385719/09:04
*** Julien-zte has quit IRC09:04
oansonThis spec is merged.09:04
*** dimak has left #openstack-meeting-409:04
*** dimak has joined #openstack-meeting-409:04
oansonI understand rajivk will also provide a follow up spec.09:04
rajivkI already provided :)09:05
oansonrajivk, do you want to comment, or are you keeping the suspense until the spec is up?09:05
oansonGreat!09:05
*** Julien-zte has joined #openstack-meeting-409:05
rajivk#link https://review.openstack.org/#/c/402395/09:05
*** Julien-zte has quit IRC09:05
oansonBeat me to it :)09:05
rajivkPlease provide your views :)09:06
rajivkOn specs09:06
*** Julien-zte has joined #openstack-meeting-409:06
oansonI see nick-ma_ already put some comments. I'll go over it the first chance I get09:06
nick-ma_hi09:06
oanson#info nick-ma_ also in meeting09:06
oansonnick-ma_, hi09:07
*** Julien-zte has quit IRC09:07
oanson#link TaaS spec https://review.openstack.org/#/c/396307/09:07
oansonThis spec is also very far along. I think the only thing left is the 'position' argument.09:07
oansonyuli_s, am I correct?09:07
yuli_sI was on vocation for a few days09:07
yuli_sso, had no chance to finish it09:07
*** Julien-zte has joined #openstack-meeting-409:07
yuli_shope to send an updated version today09:08
oansonyuli_s, no worries. :)09:08
oansonNo shortage of work for reviewers :)09:08
yuli_sok ;)09:08
oansonLooking forward to seeing you update.09:08
yuli_sok09:08
oanson#link anonymous sNAT spec https://review.openstack.org/#/c/397992/09:09
*** Julien-zte has quit IRC09:09
oansonIgor, are you here?09:09
oansonI'll hunt him down offline.09:09
oansonIn any case, it looks like there is still a lot of work here.09:10
oansonAnything specific that has to be discussed?09:10
nick-ma_i noticed the northbound api, any specific plan for that part?09:10
*** Julien-zte has joined #openstack-meeting-409:11
oansonI think Igor is working on adding it to Neutron09:11
oansonLet me see if I can find his blueprint09:11
nick-ma_ok. it is a huge work. i'm looking forward to the object model.09:11
*** cathrichardson has joined #openstack-meeting-409:11
irenaboanson: was this agreedto be accepted by neutron drivers?09:12
oansonirenab, As far as I know, it's still in the pipes09:12
ishafranHi, I am back09:12
nick-ma_why need agreement of neutron drivers?09:12
oansonI can't find it in the blueprints. I'll have to ask him.09:12
irenabif the change to neutron, it should be agreedby the team09:13
irenabif its only DF,then it does not09:13
nick-ma_i cannot see any changes to neutron.09:13
ishafranHere is a blueprint but it requires a change: https://blueprints.launchpad.net/neutron/+spec/neutron-local-snat09:13
oanson#link Distributed gateway for optimized local SNAT (Neutron Blueprint) https://blueprints.launchpad.net/neutron/+spec/neutron-local-snat09:14
nick-ma_ok, got it.09:14
oansonishafran, what's the status of it in Neutron? I can't see any discussion?09:14
ishafranI have a reference implementation based on mitaka09:14
nick-ma_i just notice that we are in the discussion of snat.09:14
ishafranRFE itself is confirmed and in wishlist09:15
oansonnick-ma_, what topic were you asking about?09:15
irenabishafran: seems its good to go on then09:15
*** ralonsoh_ has joined #openstack-meeting-409:15
irenabnot before Pika though09:15
*** Julien-zte has quit IRC09:16
ishafranirenab: yes I guess09:16
oansonishafran, we can add the API support in Pike, but the anonymous snat feature as a DF app in Ocata09:16
*** cathrichardson has quit IRC09:16
oansoncontrol it via configuration in Ocata, until API is merged (or at least in review)09:16
*** Julien-zte has joined #openstack-meeting-409:16
*** Julien-zte has quit IRC09:16
*** portdirect_away is now known as portdirect09:17
*** Julien-zte has joined #openstack-meeting-409:17
oansonCan we move on?09:17
ishafranoanson: we can delay an API, in general DF support for this feature is much more flexible09:18
oansonishafran, I think we're in agreement.09:18
*** alij has quit IRC09:18
oansonOnce the API exists, we can add support for it09:18
*** alij has joined #openstack-meeting-409:19
*** ralonsoh has quit IRC09:19
oanson#link LBaaS spec #link LBaaS spec https://review.openstack.org/#/c/397997/09:19
*** ralonsoh_ is now known as ralonsoh09:19
*** Julien-zte has quit IRC09:19
oansonAbout LBaaS, I'll hunt down denghui and ask him to update the spec09:19
oansonI'll also ask him to loiter around in the dragonflow channel in case anyone wants to strike up a discussion09:19
*** Julien-zte has joined #openstack-meeting-409:20
oanson#link Dragonflow deployment in openstack-ansible https://review.openstack.org/#/c/391524/09:20
*** Julien-zte has quit IRC09:20
oansonThis is coming along slowly but surely. It looks like the base is in place. There are a couple of things I want to add to the testing (output df-local-controller log, output subunit results to file)09:21
oansonOnce that is done, I will ask the OSA guys if we can start the review process.09:21
*** Julien-zte has joined #openstack-meeting-409:21
oansonThere is a lot of work still on Dragonflow side, but I think the OSA side is (alomost) good to go (except metadata service, which I'll add later)09:21
oansonSince metadata service requires a bit of network tweaking which is very devstack specific currently, and I want to see if it can be made more general09:22
oansonOr if the way it works currently is good enough.09:22
oansonAnything else for roadmap?09:22
*** Julien-zte has quit IRC09:23
oanson#topic Bugs09:23
*** openstack changes topic to "Bugs (Meeting topic: Dragonflow)"09:23
*** Julien-zte has joined #openstack-meeting-409:23
oansonIt looks like most of the bugs have owners.09:24
*** janki|lunch is now known as janki09:24
oansonThere is one critical bug by xiaohhui09:25
oansonxiaohhui, I am trying to understand the reviews for this bug.09:25
oansonIs it https://review.openstack.org/#/c/385350/ and https://review.openstack.org/#/c/378192 ?09:25
xiaohhuiwhat bug are you referencing?09:26
*** Julien-zte has quit IRC09:26
oansonSorry, this bug: https://bugs.launchpad.net/dragonflow/+bug/162873709:26
openstackLaunchpad bug 1628737 in DragonFlow "Exception occurs when removing last port of compute node" [Critical,In progress] - Assigned to Hong Hui Xiao (xiaohhui)09:26
*** Julien-zte has joined #openstack-meeting-409:27
*** Julien-zte has quit IRC09:27
oansonI see you updated the duplicate bug 1641903 with the reviews09:27
openstackbug 1628737 in DragonFlow "duplicate for #1641903 Exception occurs when removing last port of compute node" [Critical,In progress] https://launchpad.net/bugs/1628737 - Assigned to Hong Hui Xiao (xiaohhui)09:27
*** xiaohhui has quit IRC09:27
*** Julien-zte has joined #openstack-meeting-409:28
*** Julien-zte has quit IRC09:28
oansonIf the last comment is accurate, I can copy the comment to the original bug09:28
oansonHe left :(09:28
oansonProbably not on purpose.09:28
*** Julien-zte has joined #openstack-meeting-409:29
oansonAnyway, it looks like the last comment on https://bugs.launchpad.net/dragonflow/+bug/1641903 states the current status. I'll update the original bug09:29
openstackLaunchpad bug 1628737 in DragonFlow "duplicate for #1641903 Exception occurs when removing last port of compute node" [Critical,In progress] - Assigned to Hong Hui Xiao (xiaohhui)09:29
oansonAnything else in bugs?09:29
*** alij_ has joined #openstack-meeting-409:29
*** alij has quit IRC09:29
oanson#topic Open Discussion09:29
*** openstack changes topic to "Open Discussion (Meeting topic: Dragonflow)"09:29
oansonThe floor is for the takinhg09:29
oansontaking*09:29
nick-ma_cassandra driver is working.09:29
*** Julien-zte has quit IRC09:30
*** Julien-zte has joined #openstack-meeting-409:30
rajivkI have suggestion to everyone, the code contains very large methods. If everyone from now own takes care of writing small methods then it might be readable.09:30
oansonnick-ma_, that's great. Looking forwards to trying it out.09:31
oansonrajivk, that's a good suggestion.09:31
nick-ma_we also have several pending BIG reviews, which were proposed in newton.09:31
*** thorst_ has joined #openstack-meeting-409:31
oansonPersonally I prefer methods no longer than 20 lines09:31
oansonnick-ma_, yes. They also conflict with one another.09:32
nick-ma_like port-qos, topology data consistency, allow address pair, etc.09:32
rajivki too. May be core reviewers can make sure. :)09:32
*** xiaohhui has joined #openstack-meeting-409:32
oansonI'll try to tackle one a day, in this order: DB consistency, active-notify app, qos09:32
xiaohhuimy connection is interrupted09:32
oansonxiaohhui, no worries.09:33
xiaohhuiThe fix will be https://review.openstack.org/#/c/385350/709:33
oansonxiaohhui, I said I'll take the last comment on bug 1641903 and copy it to the original bug09:33
openstackbug 1628737 in DragonFlow "duplicate for #1641903 Exception occurs when removing last port of compute node" [Critical,In progress] https://launchpad.net/bugs/1628737 - Assigned to Hong Hui Xiao (xiaohhui)09:33
xiaohhuihowever, there is a dependent patch https://review.openstack.org/#/c/385349/1009:33
oansonIf anyone prefers a different order, please let me know.09:33
oansonAnd I apologize reviews on my end take so long.09:33
nick-ma_oanson: take it easy.09:34
rajivkoanson, no worries :)09:34
oanson:)09:35
oansonAny other open items?09:35
oansonAll right. Thanks everyone for coming.09:36
*** Julien-zte has quit IRC09:36
nick-ma_ok09:36
nick-ma_thanks.09:36
xiaohhuidinner time09:36
oansonI think the project is really moving forwards! Thanks for your efforts!09:36
*** oshidoshi has quit IRC09:36
oansonBon appetit!09:36
irenabthanks09:36
oanson#endmeeting09:36
rajivkthanks09:36
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"09:36
openstackMeeting ended Mon Nov 28 09:36:39 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:36
openstackMinutes:        http://eavesdrop.openstack.org/meetings/dragonflow/2016/dragonflow.2016-11-28-09.00.html09:36
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/dragonflow/2016/dragonflow.2016-11-28-09.00.txt09:36
openstackLog:            http://eavesdrop.openstack.org/meetings/dragonflow/2016/dragonflow.2016-11-28-09.00.log.html09:36
*** rajivk has left #openstack-meeting-409:37
*** hujie2 has joined #openstack-meeting-409:39
*** thorst_ has quit IRC09:39
*** alexchad_ has joined #openstack-meeting-409:41
*** alexchadin has quit IRC09:41
*** ishafran has quit IRC09:42
*** oshidoshi has joined #openstack-meeting-409:46
*** oshidoshi1 has joined #openstack-meeting-409:54
*** bobmel has joined #openstack-meeting-409:56
*** asettle has joined #openstack-meeting-409:56
*** oshidoshi has quit IRC09:57
*** bobmel has quit IRC10:01
*** zhurong has quit IRC10:02
*** oshidoshi1 has quit IRC10:08
*** alij_ has quit IRC10:08
*** oshidoshi has joined #openstack-meeting-410:09
*** cathrichardson has joined #openstack-meeting-410:12
*** ricolin has quit IRC10:13
*** alij has joined #openstack-meeting-410:15
*** cathrichardson has quit IRC10:17
*** stevemar has quit IRC10:19
*** alexchad_ has quit IRC10:19
*** alexchadin has joined #openstack-meeting-410:20
*** limao_ has quit IRC10:20
*** alij_ has joined #openstack-meeting-410:22
*** alij has quit IRC10:22
*** xiaohhui has quit IRC10:22
*** alexchad_ has joined #openstack-meeting-410:24
*** alexchadin has quit IRC10:24
*** oshidoshi1 has joined #openstack-meeting-410:25
*** oshidoshi has quit IRC10:28
*** anilvenkata is now known as anilvenkata_afk10:34
*** oshidoshi1 has quit IRC10:35
*** thorst_ has joined #openstack-meeting-410:37
*** neiljerram has joined #openstack-meeting-410:41
*** bobmel has joined #openstack-meeting-410:43
*** thorst_ has quit IRC10:44
*** tovin07_ has quit IRC10:50
*** kragniz has quit IRC10:54
*** kragniz has joined #openstack-meeting-410:54
*** sambetts|afk is now known as sambetts10:58
*** hujie2 has left #openstack-meeting-411:01
*** bobmel has quit IRC11:03
*** bobmel has joined #openstack-meeting-411:07
*** irenab has quit IRC11:11
*** irenab has joined #openstack-meeting-411:12
*** alij_ has quit IRC11:12
*** alij has joined #openstack-meeting-411:13
*** cathrichardson has joined #openstack-meeting-411:13
*** trinaths has quit IRC11:14
*** anilvenkata_afk is now known as anilvenkata11:15
*** cathrichardson has quit IRC11:18
*** portdirect is now known as portdirect_away11:22
*** oshidoshi has joined #openstack-meeting-411:24
*** alij has quit IRC11:26
*** alij has joined #openstack-meeting-411:26
*** oanson has quit IRC11:30
*** oanson has joined #openstack-meeting-411:31
*** zenoway has joined #openstack-meeting-411:32
*** irenab has quit IRC11:34
*** irenab has joined #openstack-meeting-411:37
*** irenab has quit IRC11:42
*** thorst_ has joined #openstack-meeting-411:42
*** irenab has joined #openstack-meeting-411:42
*** derekjhyang has joined #openstack-meeting-411:43
*** irenab has quit IRC11:47
*** sdake has joined #openstack-meeting-411:48
*** thorst_ has quit IRC11:49
*** janki has quit IRC11:50
*** alexchad_ has quit IRC11:51
*** irenab has joined #openstack-meeting-411:54
*** rtheis has joined #openstack-meeting-411:56
*** jichen has quit IRC12:02
*** irenab has quit IRC12:02
*** janki has joined #openstack-meeting-412:03
*** limao has joined #openstack-meeting-412:03
*** limao_ has joined #openstack-meeting-412:07
*** irenab has joined #openstack-meeting-412:08
*** oanson has left #openstack-meeting-412:09
*** limao has quit IRC12:10
*** cathrichardson has joined #openstack-meeting-412:14
*** alij has quit IRC12:16
*** alij_ has joined #openstack-meeting-412:16
*** alij has joined #openstack-meeting-412:16
*** cathrichardson has quit IRC12:19
*** dave-mccowan has joined #openstack-meeting-412:19
*** alij_ has quit IRC12:20
*** lihi has quit IRC12:27
*** oshidoshi has quit IRC12:28
*** alij has quit IRC12:28
*** dimak has quit IRC12:28
*** yuli_s has quit IRC12:28
*** oshidoshi has joined #openstack-meeting-412:32
*** yuli_s has joined #openstack-meeting-412:33
*** bauzas has quit IRC12:34
*** alexchadin has joined #openstack-meeting-412:36
*** bauzas has joined #openstack-meeting-412:39
*** prateek has quit IRC12:39
*** pbourke has quit IRC12:41
*** pbourke has joined #openstack-meeting-412:42
*** iurygregory has joined #openstack-meeting-412:42
*** yamamoto_ has quit IRC12:47
*** thorst_ has joined #openstack-meeting-412:48
*** janki has quit IRC12:52
*** bobh has joined #openstack-meeting-412:53
*** bobh has quit IRC12:54
*** bobh has joined #openstack-meeting-412:55
*** makowals has quit IRC12:57
*** lamt has quit IRC12:58
*** bobh has quit IRC12:59
*** makowals has joined #openstack-meeting-412:59
*** kylek3h has quit IRC13:07
*** cathrichardson has joined #openstack-meeting-413:15
*** baoli has joined #openstack-meeting-413:16
*** alij has joined #openstack-meeting-413:17
*** haleyb_ has joined #openstack-meeting-413:19
*** cathrichardson has quit IRC13:19
*** bobh has joined #openstack-meeting-413:19
*** dims has quit IRC13:33
*** yamamoto has joined #openstack-meeting-413:33
*** kylek3h has joined #openstack-meeting-413:34
*** bobh has quit IRC13:34
*** tovin07_ has joined #openstack-meeting-413:42
*** dims has joined #openstack-meeting-413:44
*** uck has joined #openstack-meeting-413:48
*** uck_ has joined #openstack-meeting-413:49
*** uck has quit IRC13:49
*** makowals has quit IRC13:49
*** makowals has joined #openstack-meeting-413:52
*** sp_ has quit IRC13:53
*** janonymous has joined #openstack-meeting-413:56
*** vikasc has joined #openstack-meeting-413:57
*** garyloug has joined #openstack-meeting-413:58
*** ivc_ has joined #openstack-meeting-413:58
*** lmdaly has joined #openstack-meeting-413:58
*** pc_m has joined #openstack-meeting-413:59
*** lamt has joined #openstack-meeting-414:00
*** prateek has joined #openstack-meeting-414:00
*** apuimedo has joined #openstack-meeting-414:01
apuimedo#startmeeting kuryr14:01
openstackMeeting started Mon Nov 28 14:01:38 2016 UTC and is due to finish in 60 minutes.  The chair is apuimedo. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: kuryr)"14:01
openstackThe meeting name has been set to 'kuryr'14:01
apuimedoHello! Welcome to another kuryr weekly meeting!14:01
*** ralonsoh_ has joined #openstack-meeting-414:01
apuimedowho's here?14:01
mchiapperoo/14:01
garylougo/14:01
janonymouso/14:02
vikasco/14:02
lmdalyo/14:02
ltomasbo0?14:02
ltomasbo0/14:02
limao_o/14:02
*** alraddarla_ has joined #openstack-meeting-414:02
ivc_o714:02
alraddarla_o/14:03
apuimedoltomasbo: that's a head with an ear?14:03
*** ralonsoh has quit IRC14:03
apuimedoWelcome all14:03
ltomasbo:D14:03
apuimedo#topic kuryr-lib14:03
*** openstack changes topic to "kuryr-lib (Meeting topic: kuryr)"14:03
apuimedo#info The only missing item for the release that blocks lmdaly and mchiappero's work is https://review.openstack.org/#/c/361993/14:04
apuimedowhich has a -1 from irenab14:04
*** irenab_ has joined #openstack-meeting-414:04
apuimedoI understand that this has been tried out by vikasc and ltomasbo with success14:04
apuimedoand I've seen some contention on the implementation from irenab and limao_14:04
*** links has quit IRC14:04
mchiapperoapuimedo: is there really a dependency? or is it for the release?14:05
apuimedomchiappero: it's for the release14:05
*** thorst_ is now known as thorst_coffee_ru14:05
mchiapperoapuimedo: ok14:05
apuimedothat will make your unit tests suddenly pass14:05
apuimedo:P14:05
apuimedolimao_: irenab: could you voice your concerns14:05
mchiapperoyeah, I didn't know whether you wanted to include it or not :)14:05
*** cathrichardson has joined #openstack-meeting-414:05
apuimedo(no need to go into all the details14:05
apuimedobut it would be nice to sum it up, so we can move into a decision)14:06
*** irenab has quit IRC14:06
limao_apuimedo: I think I already discussed with vikasc and ltomasbo in openstack-kuryr this afternoon, it is ok for me to merge that patch14:06
vikascirenab has opinion that import failure should be handled on kuryr-libnetwork side14:07
apuimedoI have to say that I agree in principle with both limao_'s and irenab_'s comments14:07
*** alexchadin has quit IRC14:07
vikasci too agree14:07
apuimedowhat I propose is to get it in now, being that it works14:07
ltomasbome too14:07
vikasci will remove this check14:07
apuimedoand then we solve those contention points in a point release14:08
apuimedoin general I think that the driver instantiation should be done by kuryr-libnetwork14:08
apuimedoand not by the module14:08
apuimedobut it's something we can move later14:08
vikascsure14:08
apuimedoirenab_: vikasc: agreed?14:08
vikasc+114:08
apuimedolimao_: ltomasbo: ?14:08
limao_+114:08
*** irenab_ has quit IRC14:08
ltomasbo+114:09
*** haleyb_ has quit IRC14:09
apuimedoalright then, so irenab will probably switch the vote later when her isp lets her14:09
*** cathrich_ has joined #openstack-meeting-414:09
apuimedothen we can merge it and trigger the release14:09
*** cathrich_ is now known as cathrichardson_14:09
apuimedofor Ocata I propose14:09
apuimedo(I'll send ML thread)14:09
apuimedo* Move the plugin system to stevedore14:10
apuimedo* clean up the couplings that we still have14:10
apuimedoanybody'14:10
apuimedo*anybody's got anything else that they want to add to kuryr-lib in the ocata cycle?14:10
*** cathrichardson has quit IRC14:11
*** cathrichardson_ is now known as cathrichardson14:11
mchiapperowell, in theory whatever is needed for making the kuryr-libnetwork plugins work14:12
apuimedomchiappero: we'll be taking a bit of a new approach in that regards to solve the bad blocking we had recently14:12
*** irenab has joined #openstack-meeting-414:12
*** yamamoto has quit IRC14:12
apuimedoif something is needed for kuryr-libnetwork. It goes first there, and if we want it in kuryr-kubernetes or fuxi, then it graduates to kuryr-lib14:12
apuimedoso we won't be putting first version stuff to kuryr-lib anymore14:13
apuimedoonly stable and used things14:13
mchiapperoI agree :)14:13
vikascthats nice14:13
limao_+114:13
ivc_+114:13
irenabapuimedo: can you please post the kuryr policies somewhere?14:13
apuimedo#info kuryr-lib is now where code goes when it is mature and usable in other parts, never again first implementations14:13
apuimedoirenab: it is now in the log and summary of this weekly, I'll update it in the kuryr-lib repo later today or tomorrow14:14
apuimedo#action apuimedo to update the repo policy for kuryr-lib14:14
apuimedo#topic kuryr-libnetwork14:14
*** openstack changes topic to "kuryr-libnetwork (Meeting topic: kuryr)"14:14
irenabapuimedo:  thanks14:14
apuimedoirenab: thanks to you for the reminder!14:14
apuimedoirenab: please, switch the vote on https://review.openstack.org/#/c/361993/2814:15
apuimedowe need to merge it14:15
apuimedoand then do a bugfix release14:15
apuimedo#info ltomasbo posted the vlan subports management patch https://review.openstack.org/402462 that uses the kuryr-lib vlan code14:15
irenabapuimedo: will check14:16
apuimedoplease, let's get this reviewed soon14:16
*** thorst_coffee_ru is now known as thorst_14:16
apuimedoand after the kuryr-lib release, this and https://review.openstack.org/400365 https://review.openstack.org/394547 will be taken out of WIP and considered for merging14:16
vikascapuimedo, https://review.openstack.org/#/c/403325/14:16
irenabapuimedo:  I just have one general comment regarding the two patches you posted14:16
apuimedovikasc: irenab: let's get https://review.openstack.org/#/c/399958/ merged14:17
apuimedothis will improve our test stability14:17
apuimedothanks limao_ for that one14:17
vikascapuimedo, sure14:17
apuimedovikasc: irenab: also https://review.openstack.org/#/c/402537/14:18
apuimedoirenab: go ahead14:18
mchiapperoI will rebase https://review.openstack.org/394547 later today to be able to merge soon14:18
irenabfor my general comments, I understand the urgency of adding new functionality, but it should not come on the cost of having less maintainable code14:18
apuimedomchiappero: when they are not missing stuff, take out the [wip] tag too14:18
mchiapperoI'll do while rebasing14:18
apuimedoirenab: I agree. This is only to be merged with the understanding that we are making a point release fixing where this code is loaded14:18
irenabaddingcases per specific drivers in the common controller is not the way to go14:19
apuimedoand the next release will move to the new plugin style that kuryr-kubernetes is pioneering14:19
apuimedoirenab: agreed14:19
irenabapuimedo: thanks14:19
apuimedodrivers, as mchiappero has been advocating, have to be chosen by kuryr-libentwork and kuryr-kubernets, not loaded by the library14:19
apuimedoso we are going to fix that for sure :-)14:20
irenabapuimedo: sounds like we should maintain the list of issue to fix :-)14:20
apuimedolimao_: irenab: please review https://review.openstack.org/#/c/403325/214:20
mchiapperoabout this14:20
apuimedoirenab: yes. We have to file bugs for this and mark them for the release14:20
apuimedo#action apuimedo to mark the bugs for the milestone releases14:21
mchiapperomost if not all (I'm not sure though) of the code for the port drivers could be promoted to kuryr-lib actually14:21
limao_ok14:21
mchiapperoI like the approach14:21
mchiapperoI'm not too sure it's actually 100% doable14:22
mchiapperoI'm looking for your opinion here14:22
irenabmchiappero: by port driver you mean binding driver?14:22
mchiapperono14:22
apuimedoirenab: port creation14:22
irenabBM vs nested?14:23
apuimedoit's basically the same as the portdriver in kuryr-kubernetes14:23
*** yedongcan has joined #openstack-meeting-414:23
apuimedoirenab: that's right14:23
mchiapperoI'm not following you anymore, what part is not clear so that I can reply?14:23
apuimedowe will try to move it to the same style as kuryr-kubernetes soon14:23
*** hongbin has joined #openstack-meeting-414:23
mchiapperoI'm not following the code in kuryr-kubernetes so I'm not sure about it14:23
hongbino/14:23
apuimedohongbin: you're on time :-)14:23
irenabapuimedo: shounds like the topic for vistual summit/sprint14:24
apuimedomchiappero: basically the idea is that for each neutron resource14:24
apuimedothere are drivers14:24
apuimedoirenab: indeed14:24
mchiapperoto recap: irenab you are proposing to get away with the port drivers and move all the code to the binding drivers, right?14:24
apuimedo(using stevedore)14:24
irenabmchiappero: no, not yet at least14:24
apuimedoand there are defaults, of course14:24
irenabdinding is different from create,so we may have 2 different group of drivers14:25
mchiapperoirenab: ok, so I misunderstood, maybe you were referring to some code in the port drivers specifically (if so, which one?)?14:25
apuimedothere's neutron resource drivers14:25
apuimedoand then binding drivers14:25
apuimedowhich in the future should use os-vif with some extensions (since os-vif doesn't have vlan/ipvlan/macvlan)14:25
*** trozet has quit IRC14:25
*** lihi has joined #openstack-meeting-414:26
irenabso the plan for now, keep binding part in the kury lib and the port create part in the libnetwork?14:26
*** trozet has joined #openstack-meeting-414:26
mchiapperook, I'm afraid I'm not able to follow, I'm sorry :(14:26
irenabmchiappero: I may need to take a look on libnetwork code again to answer you14:27
lmdalyalso are we agreed that the port driver code should be refactored to have an abstract class with drivers that provide the implementation or leave the code as is?14:27
ivc_irenab, apuimedo, not to derail the discussion, but we are going to refactor the kuryr-lib binding part to use os-vif VIF objects after it matures in kuryr-k8s, right?14:27
apuimedoivc_: exactly14:27
apuimedowe are going to mature it in kuryr-kubernetes14:27
*** makowals has quit IRC14:28
apuimedothen see how we can use it in kuryr-libnetwork14:28
irenabthe question is what we currently decide for libnetwork14:28
apuimedoand when that is clear, it moves from kuryr-kubernetes to kuryr-libnetwork and both kuryr-kubernetes and kuryr-libnetwork move to use it14:28
mchiapperosomehow the port drivers in many cases just forward straight to kuryr-lib binding drivers, so I guess you meant to move that code directly there and get away with the port drivers14:28
apuimedoirenab: currently we implement what is missing in kuryr-lib in kuryr-libnetwork14:28
irenabcurrent code is getting messed with specific type ==xxx even though we have drivers14:28
*** yamamoto has joined #openstack-meeting-414:29
mchiapperoirenab: some checks for IPVLAN will be removed14:29
*** makowals has joined #openstack-meeting-414:30
mchiapperook, if you want we can go through the code again and make a decision offline, but we do need to know which direction is the preferred one here14:30
irenabmchiappero: its now more relevant for nested support being added in the libnetowrk controller14:30
irenabmchiappero: agree14:30
vikascimo, we should wait on introducing new drivers abstraction and see how resource drivers mature in kuryr-k8s14:30
irenabapuimedo: so for now libnetwork should not use kuryr-lib drivers?14:31
mchiapperook, so let's move on no, but please let's continue later so that we can make progress, thank you14:31
apuimedoirenab: only if they can be used as is14:31
*** yamamoto has quit IRC14:31
apuimedomchiappero: thanks!14:31
apuimedo#topic fuxi14:31
*** openstack changes topic to "fuxi (Meeting topic: kuryr)"14:31
ivc_irenab, apuimedo, so granted that we expect a major binding/VIF driver refactor (prolly in P cycle), imo it should be ok to merge kuryr-lib/kuryr-libnetwork stuff as long as it works and is not _too_ ugly :)14:31
mchiapperothey can, probably will need some changes in the future, but they can14:31
apuimedoivc_: yes. That's the idea, merge what we have in the queue now14:32
apuimedohongbin: you have the floor14:32
*** uck_ has quit IRC14:32
irenabivc_: the problem is that it is ugly …14:32
apuimedo#chair hongbin14:32
openstackCurrent chairs: apuimedo hongbin14:32
hongbinfuxi?14:32
apuimedoirenab: beauty is on the eye of the beholder :P14:32
*** uck has joined #openstack-meeting-414:32
apuimedohongbin: right14:32
hongbinok, i briefly report the status of the fuxi project last week14:32
apuimedothanks14:33
hongbinthere is a patch for setup the devstack plugin for fuxi14:33
*** haleyb_ has joined #openstack-meeting-414:33
apuimedohongbin: first, let me apologize for not getting through the reviews. I've seen the new patches you posted14:33
apuimedobut I want to try the devstack myself before I approve14:33
hongbinapuimedo: np, takes your time14:33
hongbin#link https://review.openstack.org/#/c/402244/14:33
hongbinhere you go14:33
hongbinwelcome everytone to try it, and provide feedback14:34
*** galstrom_zzz is now known as galstrom14:34
hongbinthis week, i will try to setup the CI14:34
hongbinfirst, add some functional tests, then submit a patch to project-config to have a test14:34
hongbinthat is all from me14:34
apuimedosounds great hongbin!14:35
hongbinapuimedo: thanks for pinging me to give an update14:35
*** baoli has quit IRC14:35
apuimedo#action hongbin to set up CI using his devstack patches for fux14:35
apuimedo*fuxi14:35
apuimedocrap, i screwed the action point :(14:35
apuimedo#topic kuryr-kubernetes14:35
*** openstack changes topic to "kuryr-kubernetes (Meeting topic: kuryr)"14:35
ivc_well, we've completed the controller side of port binding last week (thnx apuimedo, irenab, vikasc for reviews)14:36
apuimedo#info irenab and ivc_ have updated the kuryr-kubernetes devref draft document. I highly recommend it: https://docs.google.com/document/d/1hExm0TNp_OMWY_XMVRYpSvg5G8kFrL5hcrT9M_NDCwo/edit?usp=sharing14:36
vikascbetter late than never, its very useful doc :)14:37
ivc_there's also a PoC CNI driver somewhere in that devref comments (tho i encourage you not to try it yet)14:37
apuimedo#info the controller side of port handling was merged last week14:37
*** uck has quit IRC14:37
*** alij has quit IRC14:37
apuimedoivc_: share the link, there's brave and crazy people here :P14:37
ivc_also there's a link to CNI design decisions diagram in that devref (in .xmind format)14:37
ivc_#link http://paste.openstack.org/show/590658/14:38
apuimedoivc_: thanks!14:38
vikascthanks ivc_14:38
ivc_the code is *bad* and not intended for someone to look at it, but whatever :)14:38
apuimedoivc_: don't worry too much, I'll just merge it and...14:39
irenabivc_: but it works :-)14:39
apuimedoxD14:39
ivc_so right now i'm working on a clean implementation that follows the design decisions (see .xmind doc in devref comments)14:39
apuimedo#action ivc_ to post the non-ugly version of the CNI driver WIP14:39
ivc_eta - this week14:39
apuimedoivc_: great14:40
apuimedoafter that I think vikasc and ltomasbo will be trying to get it to work with nested ports14:40
ivc_also we got an issue with devstack due to the release of kuryr-lib14:40
vikascapuimedo, right!!14:40
apuimedothere's two sides that need to be done, a vif port driver14:40
ivc_so we need to fix requirements.txt to point to kuryr-lib release instead of git14:40
vikascapuimedo, i am on it now14:41
apuimedoand the CNI part (as os-vif doesn't have yet what it takes)14:41
irenabivc_: is there a bug?14:41
apuimedoivc_: after we make today's release published yes14:41
ivc_irenab, nope. but the fix is trivial14:41
ivc_irenab, i'm just waiting for an updated kuryr-lib release :)14:41
apuimedoivc_: as soon as irenab swaps the vote on https://review.openstack.org/#/c/361993/ I'll request a release14:42
apuimedoand then I'll send the patch for requirements14:42
mchiapperoplease irenab :P14:42
ivc_ok, cool14:42
apuimedono pressure :P14:42
ivc_like at all :P14:43
irenabapuimedo: you are twisting my arm14:43
apuimedo/¯\_(ツ)_/¯14:43
*** galstrom is now known as galstrom_zzz14:43
irenabapuimedo:  I really cannot +2 this one: https://review.openstack.org/#/c/361993/28/kuryr/lib/segmentation_type_drivers/__init__.py ..14:43
mchiapperostock market might fall if we don't release soon :P14:43
*** vishwana_ has quit IRC14:44
apuimedoit will be like brexit and trump combined14:44
apuimedo:-)14:44
mchiapperorelease! :P14:44
apuimedoanyway14:44
*** vishwanathj has joined #openstack-meeting-414:44
irenabvikasc: lets compromise, put huge REVISIT comment on top of this if clause14:44
apuimedoivc_: anything else?14:44
apuimedoirenab: +114:44
ivc_apuimedo, nope14:44
vikascsure irenab :)14:44
apuimedovery well14:44
apuimedo#topic open discussion14:45
*** openstack changes topic to "open discussion (Meeting topic: kuryr)"14:45
irenabhave to go, enjoy the rest of the meeting14:45
apuimedoI'm considering begging for a room for a developer meetup in Atlanta in case some people do go14:45
ivc_apuimedo, irenab, tho that __init__.py irenab linked does look kinda ugly, i must agree :)14:45
apuimedoirenab: remember to check later for the revisit update and +2 :P14:45
*** sdake_ has joined #openstack-meeting-414:45
*** alij has joined #openstack-meeting-414:46
*** baoli has joined #openstack-meeting-414:46
apuimedoso, if any of you go, let's meet up!14:46
apuimedoanything else from anybody?14:46
alraddarla_any easy tasks a new comer can take care of for you?14:46
apuimedoalraddarla_: kubernetes or libnetwork?14:47
limao_[openstack-dev] [kuryr] - stable release for mitaka or newton14:47
alraddarla_libnetwork for now, but i'd like to look into both eventually14:47
apuimedook14:47
limao_there are a mail asking about stable release for M or N14:47
apuimedooh, that's right14:48
apuimedothe first stable release will be *sorta Newton, as in we'll release it probably in a week or two14:48
mchiapperoyes, I have an open actually regarding this https://review.openstack.org/#/c/397640/14:48
mchiapperoI'm not completely sure about the cause of the failure of the unit tests14:49
apuimedoalraddarla_: ping me later and I'll try to check the outstanding bugs for low hanging fruit14:49
*** sdake has quit IRC14:49
*** anilvenkata has quit IRC14:49
alraddarla_sounds good, thank you apuimedo14:49
mchiapperoon some machines it seems to succeed, there it fails14:49
apuimedoa heisenbug14:49
apuimedo#action apuimedo to check what's up with https://review.openstack.org/#/c/397640/ gates14:50
mchiapperocould be, I'm not too sure about the injected values, it seems like sometimes mox uses a config file14:50
apuimedolimao_ can probably find out easily14:50
apuimedo:-)14:50
mchiapperothank you!14:50
limao_:)14:50
apuimedoalraddarla_: oh, this reminds me! dropping mox for mock is doing $DEITY's work14:50
apuimedoso... there's that boring task to get acquainted with the code and ridding us of mox forever and banishing to the hades14:51
apuimedoanything else?14:51
mchiapperoI don't want to steal time here, but if you want we can return back to the driver thing :)14:51
ivc_mchiappero, i think we can do it in #openstack-kuryr, i doubt we can cover it in 5 minutes here14:52
mchiapperoso, priority #1 is to avoid pushing requirements/changes in kuryr-lib, right?14:52
apuimedomchiappero: please, read https://docs.google.com/document/d/1hExm0TNp_OMWY_XMVRYpSvg5G8kFrL5hcrT9M_NDCwo/edit?usp=sharing and then ping us on #openstack-kuryr14:52
apuimedomchiappero: no. it's making the release, then merging your patches14:53
alraddarla_apuimedo: i can handle that14:53
mchiapperoapuimedo: ok I'll do14:53
apuimedoand doing all that while not touching kuryr-lib except for cleanups14:53
apuimedo*and bugfixes)14:53
ivc_mchiappero, if you got any question about kuryr-k8s, ping me on irc or we can arrange another videoconf14:53
apuimedoivc_: good point14:53
mchiapperoyes, that was my understanding, so no changes to interfaces in kuryr-lib14:53
mchiapperoivc_: ok, thank you!14:54
apuimedomchiappero: exactly14:54
apuimedoalright. Thank you all for joining today! Have a great rest of day!14:54
apuimedo#endmeeting14:54
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:54
openstackMeeting ended Mon Nov 28 14:54:27 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:54
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kuryr/2016/kuryr.2016-11-28-14.01.html14:54
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kuryr/2016/kuryr.2016-11-28-14.01.txt14:54
openstackLog:            http://eavesdrop.openstack.org/meetings/kuryr/2016/kuryr.2016-11-28-14.01.log.html14:54
*** pc_m has left #openstack-meeting-414:56
*** alraddarla_ has left #openstack-meeting-414:56
sigmavirus#startmeeting craton14:59
openstackMeeting started Mon Nov 28 14:59:45 2016 UTC and is due to finish in 60 minutes.  The chair is sigmavirus. Information about MeetBot at http://wiki.debian.org/MeetBot.14:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:59
*** openstack changes topic to " (Meeting topic: craton)"14:59
sigmavirus#chair jimbaker14:59
openstackThe meeting name has been set to 'craton'14:59
openstackCurrent chairs: jimbaker sigmavirus14:59
*** garyloug has left #openstack-meeting-414:59
*** ivc_ has left #openstack-meeting-415:00
jimbakero/15:00
jimbakersulo, sigmavirus, hope you had a nice weekend15:01
sigmavirusI did and I hope you did too jimbaker15:01
* sigmavirus goes off in search of our agenda15:02
sigmavirus#link https://etherpad.openstack.org/p/craton-meetings15:02
sigmavirusLooks like there's no agenda for today15:02
jimbakersigmavirus, ahh, agendas... we have been working off a standing development agenda15:03
jimbakerissues that what are working on this week15:03
*** tonytan4ever has joined #openstack-meeting-415:03
sigmavirusLet's add that to the meeting etherpad then :)15:03
sigmavirus(later)15:03
sigmavirus#action jimbaker to fill out meeting etherpad with generic meeting schedule15:03
jimbaker#action jimbaker adds standing agenda to craton-meetings etherpad15:03
jimbakeryep that will do15:03
*** yedongcan has left #openstack-meeting-415:04
*** ralonsoh__ has joined #openstack-meeting-415:04
jimbakerso let's go through the forthcoming week15:04
*** psachin has quit IRC15:05
*** iurygregory has quit IRC15:05
jimbakersulo, i know you were planning to look at workflows again15:05
jimbakeranything else on your plate?15:05
suloyep, just stated that today15:05
jimbaker(also do ask my help on that patch i gave you re workflow modeling)15:05
sulona i think ill concentrate on that for now15:05
jimbaker(as necessary of course)15:05
*** watanabe_isao has joined #openstack-meeting-415:05
*** ralonsoh_ has quit IRC15:06
suloyep, sure, will do15:06
jimbakersulo, we can get back into the details, but workflow is a big enough chunk to mull upon :)15:06
jimbakersigmavirus, any updates on the forthcoming week?15:06
sigmavirusWell I'm out starting Wednesday15:07
sigmavirusSo I'm going to try to do some more tidying aroudn the client and UX improvements15:07
sigmavirusMight take over some of Harry's reviews for him while I"m here15:07
*** rbak has joined #openstack-meeting-415:07
sigmavirus(if they need taking over)15:07
*** iurygregory has joined #openstack-meeting-415:07
jimbakersigmavirus, thanks for the reminder, and sounds like a good plan. you will be back next monday?15:07
sigmavirusYes I will15:07
sulosigmavirus: ah right .. i think i have a few -1s there that need tyding up15:07
sigmavirusAnd will be around most of December except the around Christmas15:08
sigmavirussulo: good, I'll look at those15:08
sulothanks15:08
jimbakercool. speaking of such things: i will be out the last 2 weeks of december15:08
sulosame .. i am out from the 12th15:08
sigmavirusgreat15:08
sulobut i will be online of and on15:08
sigmavirusI'm out starting teh friday before Christmas15:08
jimbakersigmavirus can run what will be the very short meeting here when he's around ;)15:09
suloheh this is going to be a slow month :)15:09
jimbakerindeed it is15:09
jimbakerwe will have to account accordingly on the roadmap15:09
jimbakerwhich i don't think really gets impacted15:09
jimbakermy turn15:09
*** yamamoto has joined #openstack-meeting-415:10
jimbakerfriday i got most of the rbac modeling done within the database. so i have something that's working in terms of assigning roles to arbitrary resources in our model15:10
jimbakerthere's more to rbac than that, but this was the piece that's really specific to craton15:11
*** alij has quit IRC15:11
jimbakerin particular, one can use an object's resolution_order to describe the scope of a role15:12
jimbakereg, if the role fleet:may-do-X is assigned to a region, then any device in that region has that role15:12
jimbakeri've been working out implications for other aspects. so being able to do stuff like, a workflow can be created by one user ("developer"), then is assigned to a region by another ("authorizer"), and then is run by an operator15:14
jimbakerso this gets setuid like qualities15:15
*** haleyb_ has quit IRC15:15
*** bobh has joined #openstack-meeting-415:16
jimbakerbut such implication will be seen in the corresponding policy.json that we construct15:16
jimbakersigmavirus, i hope you don't mind the mixin approach. but it's really very similar to what was done with variables :)15:17
*** jlvill-travel is now known as jlvillal15:17
*** spotz_zzz is now known as spotz15:18
jimbakersulo, i was revisiting governance considerations15:19
sigmavirusjimbaker: I haven't seen it, so it's hard to object15:19
jimbakersigmavirus, excellent! :)15:19
*** zz_jab is now known as zz_zz_jab15:19
*** hongbin has quit IRC15:20
jimbakersigmavirus, really it's just a triple (resource, principal, role) - the only subtleties are doing the search path with resolution_order; and making it a mixin via a polymorphic association15:20
jimbakerbut both follow the approach we have already done with respect to variables15:20
sigmavirusokay15:20
*** syed__ has joined #openstack-meeting-415:21
jimbakersulo, https://github.com/NerdWalletOSS/versionalchemy is one aspect of governance15:21
jimbakerre auditing15:21
syed__o/15:21
jimbakerthat we might want to look at either using, or least seeing if there's something worth borrowing in terms of approach15:21
jimbakersyed__, hi15:22
jimbakerwe were just talking about rbac15:22
*** numans has quit IRC15:22
syed__Hi jim, i hope everyone is doing fine15:22
jimbakerso i have worked out the db modeling we need (or at least i think i did); and have enough insight to finalize the blueprint15:22
syed__Thats great15:22
*** haleyb_ has joined #openstack-meeting-415:23
*** bknudson has joined #openstack-meeting-415:23
jimbakerany rbac will be a combination of stuff we model in the database; additional policy rules (policy.json) that do the desired forward chaining; and use of oslo.policy decorators in our rest api15:24
sigmavirusso we're planning to register functions for rules, jimbaker ?15:25
jimbakerperhaps the biggest remaining subtlety is how it interacts with keystone. users looks straightforward, and it's possible that keystone's groups + domains just look like users when we see it15:25
jimbakersigmavirus, yeah15:25
sigmavirusjimbaker: did you ever write up the needs/use cases for this rbac?15:26
sigmavirusAlso, is there a WIP/POC anywhere with what you have?15:26
jimbakersigmavirus, part of the investigation15:26
*** watanabe_isao has quit IRC15:26
jimbakerand here's the relevant gist of my WIP for db modeling - https://gist.github.com/jimbaker/6a4fd7e07a16a318a45d7d1d9681904015:26
jimbakersigmavirus, we don't have detailed requirements here. i'm hoping that our discussion with dusty will help precipitate that15:27
sigmaviruscool.15:27
sigmavirusjimbaker: should we let syed__ provide updates?15:27
suloso just to be clear .. i am not sure i am follwing the rbac thing btw15:27
jimbakerthe discussion has been "we need rbac"15:27
sulolike what are we trying to rbac ?15:28
sulois it every resource ?15:28
*** uck has joined #openstack-meeting-415:28
jimbakersulo, we need to rbac every resource. the question is, what does that actually mean :)15:29
suloi guess thats what my question is15:29
jimbakersulo, so i'm working on the assumption that we need to divide below the level of a given project15:29
jimbakerand the easiest way to model this is to use the idea of triples15:30
jimbakerso for a given resource, principal pairing, we can have a set of roles15:30
jimbakerbecause it would be tedious to assign roles for any resource, we need to have some way of providing scope15:31
jimbakerfor a little further clarity: a principal - this follows what gus observed back in the spring - would be users or workflows15:32
jimbakerwe can obviously model this a number of ways, including have a workflow subclass a user. whatever makes the most sense15:33
jimbakersulo, hopefully that adds some clarity15:34
*** uck has quit IRC15:34
suloyeah, makes a bit more sense15:34
sigmavirusjimbaker: so I have questions based off of what you said, but I'd like to let syed__ fill us in on what he's done15:34
sigmavirusand doing15:34
jimbakersigmavirus, agreed - wanted to close one question out a bit15:35
jimbakersyed__, your turn. what are you working on this week?15:35
jimbakerthe other question is, do you have any vacation plans in december?15:35
syed__I will be working over craton endpoint for network tests15:36
syed__And craton client stuff, i have been digging into rbac little bit15:36
*** dims has quit IRC15:36
syed__Will close things up in ny court in this week15:36
syed__I have to make sure the schema we are using for craton is same as client15:37
*** bnemec has joined #openstack-meeting-415:37
jimbakersyed__, how does rbac impact the client?15:37
syed__I have not yet fully looked into that. I believe once blueprint is out there will help me get my mind around how we are approaching rbac for craton15:38
jimbakeri would assume this is just a question of handling 40115:38
jimbaker"not authorized"15:38
syed__I really dont know about that ... but i guess so15:38
jimbakersyed__, no worries, just want to make sure there's not something i haven't considered15:39
*** slaweq_ has quit IRC15:39
syed__Adding tests for routes/schemas is also what i will be doing today15:39
jimbakeri know for sure that i don't know enough yet about the subtleties of keystone's domain/group model, and implications for integration with craton15:39
jimbakersyed__, sounds good15:40
*** dims has joined #openstack-meeting-415:41
*** makowals has quit IRC15:41
*** haleyb_ has quit IRC15:42
jimbakersigmavirus, one other topic that came up in #craton earlier today15:42
*** sdake has joined #openstack-meeting-415:42
jimbakerjust wanted to follow up on openstack client plugin, or not15:43
jimbakersulo, any thoughts on that?15:43
suloi dont know much about openstack client and its plugin structure etc .. tbh15:44
*** galstrom_zzz is now known as galstrom15:44
*** makowals has joined #openstack-meeting-415:44
sulonever used it, so will have to read up on it etc15:44
jimbakersulo, i had not investigated either. i was just curious why keystoneclient cli for example was deprecated15:44
*** sdake_ has quit IRC15:45
jimbakeri haven't had a chance to properly vet15:45
jimbakerbut it seems to me that if we could support the plugin, it could be worthwhile. oth, people care more about shade, right?15:46
jimbakerfor actual usage15:46
jimbakerin all such cases, i would assume the underlying python client code is the foundation...15:47
palendaeopenstack-client was part of a push to have a unified user interface for openstack15:47
sigmavirusjimbaker: so I think you're frankly confusing a bunch of different projects15:47
*** yamamoto has quit IRC15:47
sigmaviruspalendae: is correct, and it's not designed for administrators iirc15:47
sigmavirusit's designed for end users of the cloud15:47
sigmavirusas I understand it, cratonclient is designed for the administrators of a cloud15:47
sigmavirusshade is also designed for end users of MANY clouds15:47
jimbakersigmavirus, correct about our target users15:48
sulosigmavirus: yeah, so thats completely differnt then15:48
sigmaviruse.g., Rackspace Public Cloud, Rackspace Private Cloud, and other openstack public cloud15:48
sigmavirusShade hides incompatibilities in all three behind a common interface15:48
sigmavirusSo when Glance actually lands image creation code that RAX pub cloud could use, then shade will use that for Rackspace Public, and use the regular PUT calls for everything else15:48
palendaeAnd only exposes some of the functionality15:48
sigmavirus(because literally no one else has problems with PUTing image data to glance)15:49
*** ralonsoh_ has joined #openstack-meeting-415:49
jimbakerbut to further confuse things, we are now looking at admin of non openstack clouds :)15:49
sigmaviruspalendae: correct15:49
palendaeFrom their docs: "shade is a simple client library for interacting with OpenStack clouds. The key word here is simple. Clouds can do many many many things - but there are probably only about 10 of them that most people care about with any regularity. If you want to do complicated things, you should probably use the lower level client libraries - or even the REST API directly."15:49
jimbakerpalendae, yes15:49
sigmavirusjimbaker: all the more reason not to try to integrate with OpenStack cilent as the CLI portion of cratonclient15:49
sigmavirusPeople who might use Craton to manage an AWS cloud probably don't want to download the 50 dependencies of OpenStackClient15:49
jimbakersigmavirus, just asking questions here :)15:50
sigmavirusThey just want the 5-10 cratonclient deps :)15:50
palendaejimbaker: While the multi-cloud thing is worth staying cognizant of, I think it's also better to get something working first15:50
*** ralonsoh__ has quit IRC15:50
*** prateek_ has joined #openstack-meeting-415:50
sigmavirus== palendae15:50
jimbakerand that makes perfect sense. you would get a quite a bundle15:50
jimbakerpalendae, sigmavirus, i understand. trust me, i'm going to try to push that work to ecosystem15:51
*** slaweq_ has joined #openstack-meeting-415:52
sigmavirusjimbaker: sure, I just really don't think that OSC is where craton's commands live15:52
sigmavirusWe can make our commands *better* by mimicking their UX if we want to15:52
jimbakersigmavirus, ack. better UX is a good thing15:52
jimbakerwhat that specifically is, TBD15:52
jimbakerso some conclusions then15:53
jimbaker1. let's continue our craton client CLI work as is15:53
*** prateek has quit IRC15:53
*** Sukhdev has joined #openstack-meeting-415:54
*** trinaths has joined #openstack-meeting-415:54
*** dtardivel has quit IRC15:54
jimbaker2. if of interest, it should be a straightforward ecosystem task to add an openstackclient plugin, built on this work - especially the underlying python client code15:54
*** hongbin has joined #openstack-meeting-415:54
jimbakerpalendae, sigmavirus, sulo - sounds reasonable?15:54
palendaeSure, if someone wants it in openstackclient they can do that work themselves. But I'm inclined to agree with sigmavirus that they have different audiences15:55
jimbaker(ecosystem task is a term of art where we get someone else to do the work...)15:55
*** yamahata has joined #openstack-meeting-415:56
sigmavirusjimbaker: yeah, the person who wants it there can write that code15:56
sigmavirusI don't think it will ever fit in there though15:56
*** iyamahat has joined #openstack-meeting-415:56
jimbakersure. it's the only reasonable way to build out this project. not just being glib here :)15:56
jimbakerjust a few minutes left in our scheduled time15:57
jimbakerany other questions/concerns before we move back to #craton ?15:58
sigmavirusAny reviews people should prioritize this week?15:58
jimbakerthat is a great question15:59
jimbakerlet's discuss on #craton, time to end this specific meeting15:59
sulosigmavirus: the one on tests ;)15:59
jimbaker#endmeeting15:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:59
openstackMeeting ended Mon Nov 28 15:59:46 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/craton/2016/craton.2016-11-28-14.59.html15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/craton/2016/craton.2016-11-28-14.59.txt15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/craton/2016/craton.2016-11-28-14.59.log.html15:59
*** derekjhyang has quit IRC16:01
jrollSukhdev: shall we?16:01
SukhdevFolks - time for Ironic-Neutron meeting16:01
jroll\o/16:01
Sukhdevjroll : yup16:01
Sukhdev#startmeeting ironic_neutron16:01
openstackMeeting started Mon Nov 28 16:01:33 2016 UTC and is due to finish in 60 minutes.  The chair is Sukhdev. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: ironic_neutron)"16:01
openstackThe meeting name has been set to 'ironic_neutron'16:01
*** hieulq has quit IRC16:01
*** tovin07 has quit IRC16:01
*** shaohe_feng has quit IRC16:01
*** fkautz has quit IRC16:01
*** david-lyle has quit IRC16:01
*** hughhalf has quit IRC16:01
*** HenryG has quit IRC16:01
*** janonymous has quit IRC16:01
*** ntr0py has quit IRC16:01
*** notmyname has quit IRC16:01
*** xgerman has quit IRC16:01
*** draynium has quit IRC16:01
*** zigo has quit IRC16:01
*** freerunner has quit IRC16:01
*** tovin07_ is now known as tovin0716:01
Sukhdev#topic: Agenda16:01
*** draynium has joined #openstack-meeting-416:01
*** openstack changes topic to ": Agenda (Meeting topic: ironic_neutron)"16:01
*** zigo has joined #openstack-meeting-416:01
*** hughhalf has joined #openstack-meeting-416:01
*** ntr0py has joined #openstack-meeting-416:01
Sukhdev#link: https://wiki.openstack.org/wiki/Meetings/Ironic-neutron#Meeting_November_28.2C_201616:01
*** lihi has quit IRC16:02
*** tovin07_ has joined #openstack-meeting-416:02
*** david-lyle has joined #openstack-meeting-416:02
*** hieulq has joined #openstack-meeting-416:02
*** vryzhenkin has joined #openstack-meeting-416:02
Sukhdev#topic: Announcements16:02
*** openstack changes topic to ": Announcements (Meeting topic: ironic_neutron)"16:02
*** shaohe_feng has joined #openstack-meeting-416:02
*** vryzhenkin is now known as freerunner16:02
Sukhdevjroll : any announcements?16:02
jrollI have none16:02
*** HenryG has joined #openstack-meeting-416:02
jrolldid security groups land/16:03
Sukhdevyup16:03
jrollnice16:03
jroll\o/16:03
*** notmyname has joined #openstack-meeting-416:03
*** fkautz has joined #openstack-meeting-416:06
*** janonymous has joined #openstack-meeting-416:06
*** tonytan4ever has quit IRC16:06
*** tonytan4ever has joined #openstack-meeting-416:06
*** sukhdev_ has joined #openstack-meeting-416:07
jrollSukhdev: shall we continue?16:07
*** xgerman has joined #openstack-meeting-416:07
sukhdev_Sorry I lost power16:07
*** Sukhdev has quit IRC16:08
*** sukhdev_ is now known as sukhdev16:08
sukhdevWifi is out.  On cell phone now16:08
jroll:/16:09
sukhdevI will upload the documentation patch later today16:09
jrollcool16:09
jrollsukhdev: want me to take over the meeting? :)16:09
sukhdevCan you please?16:09
jrollya16:10
jroll#topic Security Groups for Baremetal deployments16:10
jrollsince we're on it already :)16:10
jrollsukhdev: oh, can you #chair jroll16:10
sukhdev#chair Kroll16:10
jrollsambetts: are you here btw?16:10
sukhdevOops16:11
sambettso/ sorry in downstream meeting16:11
sukhdev#chair jroll16:11
jrollcool16:11
jrollthanks sukhdev16:11
jroll#topic Security Groups for Baremetal deployments16:11
jrollopenstack: wut r u doin16:11
* jroll wonders if meetbot doesn't think sukhdev is a chair16:13
*** zenoway has quit IRC16:14
jrollsukhdev: /nick Sukhdev16:14
jrolland then #chair jroll16:14
sambettsthe nicks have to match, I hit that problem before16:14
*** zenoway has joined #openstack-meeting-416:14
*** cwolferh has joined #openstack-meeting-416:15
*** sukhdev is now known as Sukhdev16:15
Sukhdev#chair jroll16:16
openstackCurrent chairs: Sukhdev jroll16:16
jrollwoo.16:16
jroll#topic Security Groups for Baremetal deployments16:16
*** openstack changes topic to "Security Groups for Baremetal deployments (Meeting topic: ironic_neutron)"16:16
*** lmdaly has left #openstack-meeting-416:16
jrollok so16:16
jrollsecurity groups merged16:16
jrollSukhdev is going to upload a new docs patch this week16:16
SukhdevYes16:16
jroll#topic Port Groups16:17
*** openstack changes topic to "Port Groups (Meeting topic: ironic_neutron)"16:17
jrollso the spec update landed16:17
jrollnow the code needs review16:17
jrollanything else new here?16:17
sambettsI don't think so, spec update was good :)16:17
jrollcool16:17
jroll#topic Ironic Interface attach API16:18
*** openstack changes topic to "Ironic Interface attach API (Meeting topic: ironic_neutron)"16:18
jrollI saw this got vasyl's review and sambetts has some updates to make16:18
jrollsambetts: it's a pretty big patch, wonder if it's possible to break it up?16:18
*** Sukhdev_ has joined #openstack-meeting-416:18
*** zenoway has quit IRC16:19
sambettsI pushed an update this morning, it is large I might be able to split it possibly :/ maybe split driver changes/RPC API/API again ?16:19
*** nkrinner is now known as nkrinner_afk16:19
jrollyeah, that was my first thought16:19
jrollif it's painful, don't need to split, but it'll take longer to get reviews16:20
sambettshaha I should revise my words, I meant to push an update this moring, /me forgot to git review...16:20
sambettsjust pushed it up16:20
Sukhdev_:)16:20
jrollcool16:21
jrollanything else here?16:21
sambettsI'll play around and see if I can split it down those boundrys should be pretty strauight forward I hope16:21
jrollcool, thanks16:21
sambettsI assume driver side changes need to be the bottom right? API last?16:22
jrollyeah16:22
jrollinside out :P16:22
sambettscool16:22
jrollthanks!16:22
jroll#topic VLAN aware Instances spec after aligning with Neutron/Ironic discussion16:22
*** openstack changes topic to "VLAN aware Instances spec after aligning with Neutron/Ironic discussion (Meeting topic: ironic_neutron)"16:22
jrollnot much here, I assume, still on the backburner?16:22
*** uck has joined #openstack-meeting-416:22
sambettsstill backburner, any reviews on the spec would be nice though16:23
jrollnod16:23
Sukhdev_I will review it16:23
jrollthanks Sukhdev_16:24
jroll#topic open discussion16:24
*** openstack changes topic to "open discussion (Meeting topic: ironic_neutron)"16:24
jrollanything here?16:24
Sukhdev_one question -16:24
*** limao_ has quit IRC16:24
Sukhdev_during PTG meetings - are you considering networking sprint as well?16:25
jrollSukhdev_: I expect the ironic team will talk about networking for some amount of time, if that's what you mean16:25
Sukhdev_right16:25
Sukhdev_I registered for it - and will be hopping between neutron and Ironic16:25
sambettscan we organise some overlap between neutron and Ironic?16:26
jrollcool16:26
jrollsambetts: probably16:26
*** oshidoshi has quit IRC16:26
sambettsjust thinking for the features like the neutron notifyer stuff it might be good to have it16:26
jrollyeah, I don't see why not16:26
jrollwould be cool to get the neutron side of that done for summit16:26
sambettscool16:26
Sukhdev_good16:26
Sukhdev_ nothing else from me16:27
*** uck has quit IRC16:27
sambettsme neither16:27
jrollcool16:27
jrollthanks y'all16:27
jroll#endmeeting16:27
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:27
openstackMeeting ended Mon Nov 28 16:27:44 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:27
sambettso/16:27
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ironic_neutron/2016/ironic_neutron.2016-11-28-16.01.html16:27
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ironic_neutron/2016/ironic_neutron.2016-11-28-16.01.txt16:27
openstackLog:            http://eavesdrop.openstack.org/meetings/ironic_neutron/2016/ironic_neutron.2016-11-28-16.01.log.html16:27
*** alij has joined #openstack-meeting-416:28
*** haleyb_ has joined #openstack-meeting-416:38
*** cwolferh has quit IRC16:40
*** haleyb_ has quit IRC16:43
*** tovin07 has left #openstack-meeting-416:49
*** irenab has quit IRC16:49
*** jschwarz is now known as jschwarz|mtg16:50
*** alij has quit IRC16:51
*** irenab has joined #openstack-meeting-416:54
*** revon has joined #openstack-meeting-416:54
*** trinaths has quit IRC16:57
*** gnuoy has joined #openstack-meeting-416:57
*** jovon has joined #openstack-meeting-416:58
gnuoy\o17:00
thedaco/17:00
jamespageo/17:01
coreycbo/17:01
jamespagehi folks17:01
tinwoodhi17:01
* jamespage grabs a short coffee17:01
*** cwolferh has joined #openstack-meeting-417:01
wolseno/17:01
gnuoyicey is chair today I think. Lets give him a sec17:02
beisnero/17:03
cargonzao/17:03
gnuoyok, I think icey is a no show17:03
tinwoodwe can ping him.17:03
gnuoy#startmeeting charms17:03
openstackMeeting started Mon Nov 28 17:03:43 2016 UTC and is due to finish in 60 minutes.  The chair is gnuoy. Information about MeetBot at http://wiki.debian.org/MeetBot.17:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:03
*** openstack changes topic to " (Meeting topic: charms)"17:03
openstackThe meeting name has been set to 'charms'17:03
gnuoy#topic Review ACTION points from previous meeting17:04
*** openstack changes topic to "Review ACTION points from previous meeting (Meeting topic: charms)"17:04
gnuoyACTION: gnuoy determine which openstack release the ceilometer micro services will be introduced17:04
gnuoyI did not do that. Carrying forward17:04
gnuoyACTION: jamespage to identity alternate week slot and get scheduled (carried forward)17:04
*** matrohon has quit IRC17:04
jamespageI have a review raised - needs a fix but lemme check time17:04
gnuoyYou did that didn't you James ? ^17:04
*** armax has joined #openstack-meeting-417:04
jamespageMondays 1000 UTC17:05
jamespagethe other monday17:05
gnuoykk, thanks17:05
gnuoyACTION: all to read through the charm specs: http://specs.openstack.org/openstack/charm-specs/ (carried forward)17:05
gnuoyI have no doubt that everyone has done that17:05
gnuoyso I'll close that17:05
gnuoyACTION: jamespage allocate days in month for bug squashing. (carried forward)17:05
jamespagefailing misreably at that17:05
gnuoyok, np. I'll carry it forward17:06
jamespageI was going to suggest the first thursday of every month?17:06
jamespagehow dows that sound?17:06
gnuoysure, +117:06
wolsen+117:06
tinwood+117:06
thedac+117:06
gnuoykk, thanks everyone17:06
jamespageok I'll sen the note17:07
gnuoy#topic State of Development for next Charm Release17:07
*** openstack changes topic to "State of Development for next Charm Release (Meeting topic: charms)"17:07
gnuoyanyone have something they'd like to highlight?17:07
jamespagesure we have three new charms inbound17:08
gnuoythat is true17:08
jamespagemistral, trove and murano (thanks gnuoy for raising the pc changes)17:08
gnuoynp17:08
*** jschwarz|mtg is now known as jschwarz17:08
jamespageand I think tinwood is almost there with manila landing17:08
jamespage\o/17:08
tinwoodyes, manila is about to land17:08
beisnerthere is the charm-helper update/sync which will be required for ocata support in the non-layer/reactive charms17:08
jamespageoh and I need to loop in the cloudkitty charm developer - I want to get their charm into the project as well17:08
jamespageI'll reply to his mail via the list!17:09
gnuoyI need a pc change to pull in charm templates too fwiw17:09
jamespagegnuoy, ++ pls17:09
jamespagegnuoy, you're about to start on the memcache support for token caching right?17:10
gnuoyRight, I'll be onto that tomorrow I hopw17:10
gnuoy* hope17:10
jamespage\o/17:10
gnuoyok, I'm about to move on if anyone wants to jump in before that...17:10
gnuoy#topic High Priority Bugs17:11
beisnerwe still have an outstanding issue where all src/layer charm repos are gate-blocked on a tox behavior change which now causes missing (undefined) tests to fail.17:11
*** openstack changes topic to "High Priority Bugs (Meeting topic: charms)"17:11
beisnereveryone should take a sec and read the last comment here real quick: https://review.openstack.org/#/c/399299/17:11
gnuoybeisner, to we have a pc change up to fix that?17:11
*** cwolferh has quit IRC17:11
gnuoybeisner, ah, ok17:11
beisnerwhich seems to say, that we will be forced to add a no-op shim for py27 in the charm repos instead of not-testing-py27 on python3-only charms /o\17:11
gnuoyIt's not ideal but *shrug*17:12
tinwoodI'm with gnuoy -- just put a comment in the tox.ini17:12
beisnerso although i did get the project configs sorted in a way where we can start moving charms to the python3 only bucket as they're ready, TC isn't there just yet.17:12
beisnerduct tape it is /o\  /o\17:13
jamespage:(17:14
gnuoyWe've tripped over some bugs with Juju and secgroups and Juju and volumes.17:14
beisnerwhat the actual..17:14
gnuoy#link https://bugs.launchpad.net/juju/+bug/164529817:14
openstackLaunchpad bug 1645298 in juju "unable to removed units with attached storage with OpenStack Mitaka" [Undecided,New]17:14
gnuoy#link https://bugs.launchpad.net/juju/+bug/162562417:14
openstackLaunchpad bug 1625624 in juju-core "juju 2 doesn't remove openstack security groups" [Critical,Triaged]17:14
gnuoyseem to be mitaka+ specific17:14
gnuoyAnyone got any others bugs they'd like to highlight?17:15
gnuoy...17:16
*** sdake has quit IRC17:16
gnuoy#topic Openstack Events17:16
*** openstack changes topic to "Openstack Events (Meeting topic: charms)"17:16
jamespagePTG!17:16
gnuoyjamespage, You've got one on Thursday, right?17:16
jamespageFeb 20th17:16
jamespageoh yes17:16
jamespageOpenStack Meetup in London17:16
*** sdake has joined #openstack-meeting-417:16
jamespagenot speaking about charms specifically but will be doing a lighting talk on LXD containers in OpenStack17:17
*** uck has joined #openstack-meeting-417:17
tinwoodSounds good.17:17
beisnerjamespage, can you talk py27 retirement with tc as ptl?  with our py3 push, we'll need a clear path forward.17:17
jamespageI can17:17
jamespagegnuoy, pls action me17:17
beisnermany thanks17:17
gnuoy#action jamespage  talk py27 retirement with tc as ptl17:18
jamespageta17:18
gnuoy#topic Open Discussion17:18
*** openstack changes topic to "Open Discussion (Meeting topic: charms)"17:18
beisnerjamespage, "just think of the virtualenvs you won't have to build for no-ops" ;-)17:18
*** cwolferh has joined #openstack-meeting-417:18
*** pcaruana has quit IRC17:19
gnuoyanything to openly discuss before i end the meeting?17:20
gnuoy...17:20
gnuoy#endmeeting17:20
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:20
openstackMeeting ended Mon Nov 28 17:20:31 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:20
openstackMinutes:        http://eavesdrop.openstack.org/meetings/charms/2016/charms.2016-11-28-17.03.html17:20
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/charms/2016/charms.2016-11-28-17.03.txt17:20
openstackLog:            http://eavesdrop.openstack.org/meetings/charms/2016/charms.2016-11-28-17.03.log.html17:20
thedacthanks, gnuoy17:20
tinwoodthanks gnuoy17:20
gnuoynp17:20
*** cwolferh_ has joined #openstack-meeting-417:20
jamespageta gnuoy17:21
*** uck has quit IRC17:21
*** rbak has quit IRC17:21
beisnerthanks gnuoy17:22
*** rbak has joined #openstack-meeting-417:22
*** cwolferh has quit IRC17:24
*** unicell1 has quit IRC17:29
*** sdake_ has joined #openstack-meeting-417:34
*** sdake has quit IRC17:36
*** haleyb_ has joined #openstack-meeting-417:40
*** haleyb_ has quit IRC17:45
*** yfauser has joined #openstack-meeting-417:49
*** prateek_ has quit IRC17:50
*** Sukhdev_ has quit IRC17:51
*** makowals_ has joined #openstack-meeting-417:52
*** makowals has quit IRC17:55
*** makowals_ has quit IRC17:57
*** makowals has joined #openstack-meeting-417:58
*** ralonsoh_ has quit IRC18:02
*** portdirect_away is now known as portdirect18:04
*** yfauser has quit IRC18:06
*** bpokorny has joined #openstack-meeting-418:07
*** rbak has quit IRC18:10
*** slaweq_ has quit IRC18:13
*** rbak has joined #openstack-meeting-418:16
*** sambetts is now known as sambetts|afk18:17
*** piet has joined #openstack-meeting-418:17
*** sdake has joined #openstack-meeting-418:18
*** woodard has joined #openstack-meeting-418:18
*** anilvenkata has joined #openstack-meeting-418:20
*** sdake_ has quit IRC18:21
*** piet has quit IRC18:22
*** Swami has joined #openstack-meeting-418:30
*** reedip_ has joined #openstack-meeting-418:36
*** makowals has quit IRC18:38
*** haleyb_ has joined #openstack-meeting-418:41
*** unicell has joined #openstack-meeting-418:41
*** bnemec has quit IRC18:45
*** haleyb_ has quit IRC18:46
*** hemanth is now known as hemanth|lunch18:54
*** s3wong has joined #openstack-meeting-418:55
*** piet has joined #openstack-meeting-418:57
*** tonytan4ever has quit IRC19:03
*** uck has joined #openstack-meeting-419:05
*** reedip_ has quit IRC19:05
*** irenab has quit IRC19:05
*** bpokorny has quit IRC19:06
*** bpokorny has joined #openstack-meeting-419:07
*** uck has quit IRC19:10
*** vishnoianil has joined #openstack-meeting-419:10
*** haleyb_ has joined #openstack-meeting-419:10
*** bpokorny has quit IRC19:11
*** haleyb_ has quit IRC19:15
*** bobh has quit IRC19:15
*** bobh has joined #openstack-meeting-419:16
*** bobh has quit IRC19:20
*** bpokorny has joined #openstack-meeting-419:21
*** makowals has joined #openstack-meeting-419:29
*** makowals has quit IRC19:31
*** spzala has joined #openstack-meeting-419:37
*** hemanth|lunch is now known as hemanth19:38
*** matrohon has joined #openstack-meeting-419:44
*** slaweq_ has joined #openstack-meeting-419:51
*** Sukhdev_ has joined #openstack-meeting-419:53
*** Sukhdev has quit IRC20:01
*** bpokorny has quit IRC20:02
*** bpokorny has joined #openstack-meeting-420:02
*** bnemec has joined #openstack-meeting-420:03
*** slaweq_ has quit IRC20:04
*** woodster_ has joined #openstack-meeting-420:05
*** bpokorny has quit IRC20:07
*** piet has quit IRC20:13
*** anilvenkata has quit IRC20:19
*** iyamahat has quit IRC20:25
*** slaweq_ has joined #openstack-meeting-420:25
*** yamahata has quit IRC20:25
*** bobh has joined #openstack-meeting-420:30
*** piet has joined #openstack-meeting-420:30
*** rtheis has quit IRC20:45
*** iyamahat has joined #openstack-meeting-420:47
*** Sukhdev_ has quit IRC20:47
*** beagles is now known as beagles_biab20:49
*** slaweq_ has quit IRC20:51
*** uck has joined #openstack-meeting-420:53
*** MeganR has joined #openstack-meeting-420:55
*** Sukhdev has joined #openstack-meeting-420:57
*** uck has quit IRC20:58
*** slaweq_ has joined #openstack-meeting-420:58
*** bpokorny has joined #openstack-meeting-421:00
*** spzala has quit IRC21:01
*** yamahata has joined #openstack-meeting-421:04
*** vishwana_ has joined #openstack-meeting-421:04
*** slaweq_ has quit IRC21:06
*** vishwanathj has quit IRC21:08
*** slaweq_ has joined #openstack-meeting-421:08
*** slaweq_ has quit IRC21:21
*** sdake_ has joined #openstack-meeting-421:32
*** vishwana_ has quit IRC21:35
*** Jeffrey4l has quit IRC21:35
*** sdake has quit IRC21:35
*** vishwanathj has joined #openstack-meeting-421:35
*** thorst_ has quit IRC21:37
*** thorst_ has joined #openstack-meeting-421:37
*** thorst_ has quit IRC21:42
*** matrohon has quit IRC21:45
*** Jeffrey4l has joined #openstack-meeting-421:47
*** Julien-zte has joined #openstack-meeting-421:50
*** sdake_ is now known as sdake21:50
*** jwagner is now known as jwagner_lunch21:52
*** kylek3h has quit IRC21:58
*** rbak has quit IRC21:59
*** rbak has joined #openstack-meeting-421:59
*** MeganR has quit IRC22:01
*** lamt has quit IRC22:05
*** lamt has joined #openstack-meeting-422:10
*** thorst_ has joined #openstack-meeting-422:12
*** spotz is now known as spotz_zzz22:14
*** thorst__ has joined #openstack-meeting-422:15
*** thorst_ has quit IRC22:17
*** Sukhdev has quit IRC22:19
*** zigo has quit IRC22:29
*** zigo has joined #openstack-meeting-422:36
*** cathrich_ has joined #openstack-meeting-422:37
*** cathrichardson has quit IRC22:37
*** bobh has quit IRC22:40
*** uck has joined #openstack-meeting-422:41
*** cathrich_ has quit IRC22:43
*** baoli has quit IRC22:43
*** uck has quit IRC22:46
*** JRobinson__ has joined #openstack-meeting-422:48
*** cathrichardson has joined #openstack-meeting-422:57
*** slaweq_ has joined #openstack-meeting-422:58
*** reedip_ has joined #openstack-meeting-423:00
*** spzala has joined #openstack-meeting-423:01
*** cathrichardson has quit IRC23:01
*** cathrich_ has joined #openstack-meeting-423:01
*** cathrich_ is now known as cathrichardson23:02
*** Swami has quit IRC23:05
*** spzala has quit IRC23:06
*** lamt has quit IRC23:18
*** jovon has quit IRC23:18
*** thorst__ is now known as thorst_23:21
*** thorst_ has quit IRC23:23
*** thorst_ has joined #openstack-meeting-423:24
*** thorst_ has quit IRC23:32
*** baoli has joined #openstack-meeting-423:33
*** Julien-zte has quit IRC23:33
*** baoli has quit IRC23:37
*** bnemec has quit IRC23:37
*** bobmel has quit IRC23:45
*** bobmel has joined #openstack-meeting-423:54
*** hemanth is now known as hemanth|away23:55
*** bobmel has quit IRC23:59

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!