Thursday, 2017-03-23

*** gongysh has joined #openstack-meeting-400:03
*** salmankhan has quit IRC00:07
*** uck has quit IRC00:07
*** woodard_ has joined #openstack-meeting-400:20
*** woodard has quit IRC00:20
*** baoli_ has joined #openstack-meeting-400:21
*** baoli has quit IRC00:25
*** liangy has joined #openstack-meeting-400:26
*** adisky_ has quit IRC00:29
*** limao has joined #openstack-meeting-400:38
*** zhurong has joined #openstack-meeting-400:42
*** bobh has joined #openstack-meeting-400:46
*** bobh has quit IRC00:46
*** bobh has joined #openstack-meeting-400:47
*** reedip has quit IRC00:47
*** bobmel has joined #openstack-meeting-400:48
*** bobh_ has joined #openstack-meeting-400:49
*** bobh has quit IRC00:49
*** bobmel has quit IRC00:52
*** bobh_ has quit IRC00:53
*** bobh has joined #openstack-meeting-400:53
*** tovin07_ has joined #openstack-meeting-400:54
*** Julien-zte has joined #openstack-meeting-400:55
*** SerenaFeng has joined #openstack-meeting-400:56
*** baoli has joined #openstack-meeting-401:02
*** baoli_ has quit IRC01:05
*** armax has quit IRC01:08
*** zhurong has quit IRC01:23
*** SerenaFeng has quit IRC01:24
*** reedip has joined #openstack-meeting-401:24
*** yamahata has quit IRC01:27
*** iyamahat has quit IRC01:27
*** dharinic has joined #openstack-meeting-401:33
*** liangy has quit IRC01:37
*** dave-mccowan has quit IRC01:37
*** dave-mccowan has joined #openstack-meeting-401:39
*** SerenaFeng has joined #openstack-meeting-401:40
*** gongysh has quit IRC01:40
*** jtaryma has joined #openstack-meeting-401:42
*** zhurong has joined #openstack-meeting-401:43
*** julim has joined #openstack-meeting-401:46
*** raj_sing- has joined #openstack-meeting-401:46
*** pshedimb has joined #openstack-meeting-401:49
*** dharinic- has joined #openstack-meeting-401:53
*** hieulq has quit IRC01:56
*** Sukhdev_ has quit IRC01:56
*** SerenaFeng has quit IRC01:58
*** hieulq has joined #openstack-meeting-401:59
*** dave-mcc_ has joined #openstack-meeting-402:08
*** dave-mccowan has quit IRC02:10
*** dave-mccowan has joined #openstack-meeting-402:14
*** unicell has quit IRC02:15
*** dave-mcc_ has quit IRC02:16
*** rfolco has quit IRC02:19
*** shaohe_feng has joined #openstack-meeting-402:22
*** hongbin has joined #openstack-meeting-402:23
*** gongysh has joined #openstack-meeting-402:36
*** dharinic has quit IRC02:37
*** dharinic- is now known as dharinic02:37
*** hieulq has quit IRC02:39
*** hieulq has joined #openstack-meeting-402:41
*** l4yerffeJ has joined #openstack-meeting-402:41
*** unicell has joined #openstack-meeting-402:48
*** bobmel has joined #openstack-meeting-402:48
*** vishnoianil has quit IRC02:51
*** 7IZAAUKJJ has joined #openstack-meeting-402:52
*** bobmel has quit IRC02:53
*** bzhao_ has joined #openstack-meeting-402:58
*** 7IZAAUKJJ has quit IRC03:00
*** lihi has quit IRC03:06
*** lihi has joined #openstack-meeting-403:07
*** l4yerffeJ has quit IRC03:10
*** dimak has quit IRC03:13
*** dimak has joined #openstack-meeting-403:13
*** zhubingbing has joined #openstack-meeting-403:17
*** baoli has quit IRC03:22
*** bobh has quit IRC03:29
*** Sukhdev has joined #openstack-meeting-403:33
*** bobh has joined #openstack-meeting-403:34
*** hongbin has quit IRC03:37
*** links has joined #openstack-meeting-403:37
*** amotoki has quit IRC03:37
*** bobh has quit IRC03:38
*** bobh has joined #openstack-meeting-403:38
*** bot_Jeffrey4l has joined #openstack-meeting-403:43
*** bobh has quit IRC03:43
*** bot_Jeffrey4l has quit IRC03:47
*** bot_Jeffrey4l has joined #openstack-meeting-403:47
*** zhurong has quit IRC03:48
*** bobmel has joined #openstack-meeting-403:49
*** armax has joined #openstack-meeting-403:49
*** dave-mccowan has quit IRC03:50
*** amotoki has joined #openstack-meeting-403:50
*** hieulq has quit IRC03:50
*** hieulq has joined #openstack-meeting-403:53
*** bobmel has quit IRC03:54
*** amotoki has quit IRC03:55
*** amotoki has joined #openstack-meeting-403:59
*** anilvenkata has joined #openstack-meeting-404:07
*** iyamahat has joined #openstack-meeting-404:09
*** uck has joined #openstack-meeting-404:14
*** amotoki has quit IRC04:19
*** adisky_ has joined #openstack-meeting-404:20
*** uck has quit IRC04:24
*** tovin07_ has quit IRC04:25
*** psachin has joined #openstack-meeting-404:28
*** amotoki has joined #openstack-meeting-404:28
*** vks1 has joined #openstack-meeting-404:32
*** gongysh has quit IRC04:34
*** tovin07_ has joined #openstack-meeting-404:36
*** tovin07_ has quit IRC04:38
*** limao has quit IRC04:38
*** tovin07_ has joined #openstack-meeting-404:44
*** armax has quit IRC04:44
*** armax has joined #openstack-meeting-404:44
*** yamahata has joined #openstack-meeting-404:48
*** limao has joined #openstack-meeting-404:55
*** Jeffrey4l_ has quit IRC04:55
*** Jeffrey4l has joined #openstack-meeting-404:56
*** iyamahat has quit IRC04:59
*** gongysh has joined #openstack-meeting-405:03
*** markvoelker has quit IRC05:08
*** markvoelker has joined #openstack-meeting-405:09
*** markvoelker has quit IRC05:13
*** baoli has joined #openstack-meeting-405:24
*** baoli has quit IRC05:29
*** aunnam has joined #openstack-meeting-405:42
*** bobmel has joined #openstack-meeting-405:50
*** zhurong has joined #openstack-meeting-405:53
*** Sukhdev has quit IRC05:53
*** SerenaFeng has joined #openstack-meeting-405:54
*** bobmel has quit IRC05:54
*** arif-ali has quit IRC05:56
*** arif-ali has joined #openstack-meeting-405:58
*** irenab has joined #openstack-meeting-406:01
*** armax has quit IRC06:03
*** armax has joined #openstack-meeting-406:03
*** armax has quit IRC06:04
*** armax has joined #openstack-meeting-406:05
*** armax has quit IRC06:05
*** tonyb_ has joined #openstack-meeting-406:06
*** kbyrne_ has joined #openstack-meeting-406:09
*** jokke__ has joined #openstack-meeting-406:09
*** markvoelker has joined #openstack-meeting-406:09
*** unicell1 has joined #openstack-meeting-406:10
*** unicell has quit IRC06:11
*** tonyb has quit IRC06:13
*** flaper87 has quit IRC06:13
*** lkoranda has quit IRC06:13
*** kbyrne has quit IRC06:13
*** jokke_ has quit IRC06:13
*** kbyrne_ is now known as kbyrne06:13
*** markvoelker has quit IRC06:13
*** lkoranda has joined #openstack-meeting-406:15
*** tovin07_ has quit IRC06:26
*** tonytan4ever has quit IRC06:26
*** tonytan4ever has joined #openstack-meeting-406:26
*** tonytan4ever has quit IRC06:31
*** jtaryma is now known as joanna06:35
*** chigang has joined #openstack-meeting-406:35
*** bzhao_ has quit IRC06:38
*** vds has quit IRC06:40
*** vds has joined #openstack-meeting-406:43
*** vishnoianil has joined #openstack-meeting-406:46
*** oshidoshi has joined #openstack-meeting-406:47
*** amotoki_ has joined #openstack-meeting-406:52
*** amotoki has quit IRC06:55
*** tovin07_ has joined #openstack-meeting-407:01
*** isq has quit IRC07:01
*** sbezverk_ has joined #openstack-meeting-407:01
*** isq has joined #openstack-meeting-407:02
*** jasondotstar has quit IRC07:03
*** dmellado has quit IRC07:03
*** kfox1111 has quit IRC07:04
*** kfox1111 has joined #openstack-meeting-407:04
*** sbezverk has quit IRC07:05
*** iyamahat has joined #openstack-meeting-407:08
*** jasondotstar has joined #openstack-meeting-407:08
*** dmellado has joined #openstack-meeting-407:08
*** mandre has left #openstack-meeting-407:22
*** janki has joined #openstack-meeting-407:24
*** nkrinner_afk is now known as nkrinner07:25
*** baoli has joined #openstack-meeting-407:25
*** janki has quit IRC07:27
*** janki has joined #openstack-meeting-407:27
*** baoli has quit IRC07:31
*** kzaitsev_ws has joined #openstack-meeting-407:31
*** iyamahat has quit IRC07:42
*** matrohon has joined #openstack-meeting-407:53
*** bogdando has joined #openstack-meeting-407:54
*** oshidoshi1 has joined #openstack-meeting-408:00
*** oshidoshi has quit IRC08:01
*** janki is now known as janki|lunch08:04
*** pcaruana has joined #openstack-meeting-408:06
*** vds has left #openstack-meeting-408:06
*** flaper87 has joined #openstack-meeting-408:08
*** markvoelker has joined #openstack-meeting-408:10
*** zhubingbing has left #openstack-meeting-408:10
*** markvoelker has quit IRC08:14
*** matrohon has quit IRC08:20
*** tonytan4ever has joined #openstack-meeting-408:27
*** matrohon has joined #openstack-meeting-408:35
*** ralonsoh has joined #openstack-meeting-408:43
*** yamahata has quit IRC08:46
*** reedip has quit IRC08:49
*** Julien-zte has quit IRC08:54
*** ltomasbo|away is now known as ltomasbo08:55
*** SerenaFeng has quit IRC08:56
*** SerenaFeng has joined #openstack-meeting-408:58
*** makowals_ has quit IRC09:00
*** makowals has joined #openstack-meeting-409:01
*** janki|lunch is now known as janki09:08
*** dtardivel has joined #openstack-meeting-409:11
*** david-lyle has quit IRC09:11
*** jrist has quit IRC09:12
*** david-lyle has joined #openstack-meeting-409:13
*** jrist has joined #openstack-meeting-409:13
*** alexchadin has joined #openstack-meeting-409:15
*** reedip has joined #openstack-meeting-409:25
*** david-lyle_ has joined #openstack-meeting-409:27
*** david-lyle has quit IRC09:27
*** tonytan4ever has quit IRC09:27
*** gongysh has quit IRC09:38
*** links has quit IRC09:39
*** amotoki_ has quit IRC09:40
*** matrohon has quit IRC09:42
*** matrohon has joined #openstack-meeting-409:43
*** SerenaFeng has quit IRC09:46
*** salmankhan has joined #openstack-meeting-409:49
*** salmankhan has quit IRC09:53
*** salmankhan has joined #openstack-meeting-409:55
*** links has joined #openstack-meeting-409:56
*** amotoki has joined #openstack-meeting-409:59
*** limao has quit IRC10:09
*** limao has joined #openstack-meeting-410:10
*** markvoelker has joined #openstack-meeting-410:11
*** links has quit IRC10:11
*** pbourke has quit IRC10:14
*** limao has quit IRC10:15
*** vsaienk01 has left #openstack-meeting-410:16
*** pbourke has joined #openstack-meeting-410:16
*** markvoelker has quit IRC10:16
*** links has joined #openstack-meeting-410:23
*** links has quit IRC10:35
*** makowals has quit IRC10:38
*** makowals has joined #openstack-meeting-410:43
*** amotoki has quit IRC10:46
*** amotoki has joined #openstack-meeting-410:49
*** links has joined #openstack-meeting-410:51
*** salmankhan has quit IRC10:57
*** salmankhan has joined #openstack-meeting-410:58
*** salmankhan has quit IRC11:02
*** salmankhan has joined #openstack-meeting-411:04
*** alexchadin has quit IRC11:12
*** tovin07_ has quit IRC11:15
*** matrohon has quit IRC11:16
*** tovin07 has quit IRC11:19
*** Julien-zte has joined #openstack-meeting-411:24
*** tonytan4ever has joined #openstack-meeting-411:28
*** pshedimb has quit IRC11:36
*** dharinic has quit IRC11:36
*** raj_sing- has quit IRC11:36
*** joanna has quit IRC11:36
*** aunnam has quit IRC11:36
*** amotoki has quit IRC11:45
*** rfolco has joined #openstack-meeting-411:48
*** salmankhan has quit IRC11:54
*** bobh has joined #openstack-meeting-411:58
*** salmankhan has joined #openstack-meeting-412:02
*** salmankhan has quit IRC12:08
*** salmankhan has joined #openstack-meeting-412:08
*** chigang has quit IRC12:09
*** markvoelker has joined #openstack-meeting-412:13
*** anilvenkata has quit IRC12:13
*** bobh has quit IRC12:14
*** julim has quit IRC12:15
*** markvoelker has quit IRC12:17
*** julim has joined #openstack-meeting-412:17
*** srwilkers has joined #openstack-meeting-412:22
*** zhurong has quit IRC12:22
*** tonytan4ever has quit IRC12:28
*** vks1 has quit IRC12:29
*** tonytan4ever has joined #openstack-meeting-412:33
*** woodard_ has quit IRC12:35
*** woodard has joined #openstack-meeting-412:35
*** matrohon has joined #openstack-meeting-412:38
*** bogdando has quit IRC12:40
*** markvoelker has joined #openstack-meeting-412:46
*** klamath has joined #openstack-meeting-412:46
*** klamath has quit IRC12:47
*** klamath has joined #openstack-meeting-412:47
*** psachin has quit IRC12:52
*** dave-mccowan has joined #openstack-meeting-412:53
*** belmoreira has joined #openstack-meeting-412:55
*** rwallner has joined #openstack-meeting-413:07
*** rwallner has quit IRC13:08
*** rwallner has joined #openstack-meeting-413:09
*** baoli has joined #openstack-meeting-413:13
*** amotoki has joined #openstack-meeting-413:13
*** pmesserli has joined #openstack-meeting-413:13
*** cleong has joined #openstack-meeting-413:23
*** haleyb has joined #openstack-meeting-413:28
*** mbruzek has joined #openstack-meeting-413:32
*** mbruzek has quit IRC13:32
*** mbruzek has joined #openstack-meeting-413:32
*** limao has joined #openstack-meeting-413:35
*** bobmel has joined #openstack-meeting-413:35
*** cathrichardson has joined #openstack-meeting-413:37
*** limao has quit IRC13:39
*** bobh has joined #openstack-meeting-413:39
*** cathrich_ has joined #openstack-meeting-413:41
*** cathrichardson has quit IRC13:41
*** krtaylor has joined #openstack-meeting-413:43
*** janki has quit IRC13:45
*** limao has joined #openstack-meeting-413:49
*** stevelle has joined #openstack-meeting-413:49
*** vks1 has joined #openstack-meeting-413:49
*** cathrich_ has left #openstack-meeting-413:50
*** bogdando has joined #openstack-meeting-413:50
*** alex_bash has joined #openstack-meeting-413:56
*** limao has quit IRC13:57
*** limao has joined #openstack-meeting-413:58
rosmaitaCourtesy meeting reminder on #openstack-meeting-4: ativelkov, cpallares, flaper87, flwang1, hemanthm, jokke_, kragniz, lakshmiS, mclaren, mfedosin, nikhil_k, Nikolay_St, Olena, pennerc, rosmaita, sigmavirus24, sabari, TravT, ajayaa, GB21, bpoulos, harshs, abhishek, bunting, dshakhray, wxy, dhellmann, kairat, aavraham, alex_bash13:59
rosmaita#startmeeting glance14:00
openstackMeeting started Thu Mar 23 14:00:04 2017 UTC and is due to finish in 60 minutes.  The chair is rosmaita. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: glance)"14:00
openstackThe meeting name has been set to 'glance'14:00
rosmaita#topic roll call14:00
*** openstack changes topic to "roll call (Meeting topic: glance)"14:00
rosmaitakind of quiet in here this morning14:00
*** dharinic has joined #openstack-meeting-414:00
rosmaitahello dharinic14:00
dharinicGood Morning rosmaita14:01
*** liangy has joined #openstack-meeting-414:01
alex_basho/14:01
rosmaitahi alex14:01
*** cjloader_ has joined #openstack-meeting-414:01
stevelleo/14:01
*** yfauser has joined #openstack-meeting-414:01
*** hongbin has joined #openstack-meeting-414:02
jokke__o/14:02
rosmaitaok, guess we can get started14:03
rosmaitai'm starting with general openstack updates anyway14:03
rosmaita#topic updates14:04
*** openstack changes topic to "updates (Meeting topic: glance)"14:04
rosmaita#topic update - R release naming14:04
*** openstack changes topic to "update - R release naming (Meeting topic: glance)"14:04
rosmaita#link http://lists.openstack.org/pipermail/openstack-dev/2017-March/114436.html14:04
rosmaitathat email give you the info about the rules14:04
rosmaitaso if you'd like to be immortalized, you can suggest an R name and maybe make the cut for the big vote14:05
rosmaitathat's all about that14:05
*** vks1 has quit IRC14:05
rosmaita#topic update - quotas action14:05
*** openstack changes topic to "update - quotas action (Meeting topic: glance)"14:05
rosmaitathis is for awareness of what's happening right now14:06
rosmaitasean dague has proposed a "unified limits" conceptual spec14:06
*** cjloader_ has quit IRC14:06
rosmaita#link http://lists.openstack.org/pipermail/openstack-dev/2017-March/114230.html14:06
rosmaitathat email gives some info14:06
rosmaitakey things are:14:06
rosmaitaaiming for 2-week comment cycle so that it will be clear whether this can happen in Pike or not14:06
rosmaitaand, comments close 30 March14:07
rosmaitahere's the actual spec link14:07
rosmaita#link https://review.openstack.org/#/c/440815/14:07
rosmaitai think nikhil is the glancer most interested in this, but i don't seem him around atm14:07
*** caoyuan has joined #openstack-meeting-414:08
rosmaitaanyway, the quotas work will eventually impact glance, so take a look at the spec if you want to provide input on the ground floor14:08
rosmaita#topic update - log messages14:08
*** openstack changes topic to "update - log messages (Meeting topic: glance)"14:08
*** limao has quit IRC14:08
rosmaitain case you haven't followed the discussion on the ML, log messages are no longer translated14:08
rosmaitathere's a patch up to remove the _L* from glance code:14:09
rosmaita#link https://review.openstack.org/44797014:09
*** limao has joined #openstack-meeting-414:09
jokke__so I have to admit, I haven't followed ... is this permanent?14:09
rosmaitathe rationale for removal is that most people google log messages to figure out what they mean14:09
jokke__as those translation rules seems to change every second cycle14:10
rosmaitaso keeping them all in english means less fragmentation and better results14:10
rosmaitajokke__: good point14:10
rosmaitai believe this is meant to be permanent14:10
alex_bashI also thought the discussion was still ongoing14:10
rosmaitabut i was wondering whether it would be better to make the _L* no-ops instead of removing14:10
rosmaitabut it would make the coder harder to read14:11
jokke__yeah, that has been discussed a lot exactly for that reason and the rationale has always been that the localization people have been super agains that specially around the more dominant languages14:11
rosmaitathough, no harder than it is presently14:11
rosmaitaalex_bash: i thought it had concluded, but maybe not14:11
alex_bashrosmaita: you mean redefine them ourselves or within i18n?14:11
jokke__lets hold off with that patch, please ... I have a look on that discussion and probe for more info if needed14:12
rosmaitathere are refs to the ML in the commit message of that patch14:12
jokke__cheers14:12
rosmaitaok, that's a good idea14:12
rosmaita#action rosmaita determine actual status of i18n for log messages14:12
stevelleI endorse this action14:12
rosmaitai'll put a note on the patch to that effect14:12
stevelletranslating logs was always flawed for this reason but let's be sure14:13
rosmaitaalex_bash: i was thinking within glance for the _L* no-ops14:13
rosmaitai must admit14:13
rosmaitamy reading of the discussion was that it was trending to non-translation14:13
*** caoyuan has left #openstack-meeting-414:13
rosmaitaand then i saw the patch and figured it was a done deal14:13
rosmaitabut that was an inference, not a fact14:13
rosmaitaso i will check14:13
rosmaitaand report back next week14:14
rosmaitaok, jokke__ , make sure you are seated comfortably before the next one14:14
rosmaita#update - microversioning in glance14:14
rosmaitaoops14:15
rosmaita#topic update - microversioning in glance14:15
*** openstack changes topic to "update - microversioning in glance (Meeting topic: glance)"14:15
rosmaitai need to write some macros or something14:15
jokke__oh this is quick topic ;)14:15
jokke__-2 ... neext14:15
rosmaitadraft API compatibility/stability "guidelines" (actually requirements for asserting the proposed 'assert:supports-api-compatibility' tag14:15
rosmaita#link https://review.openstack.org/#/c/421846/14:15
rosmaitachanges will require version changes, and the only acceptable versioning scheme satisfying the guidelines is microversions14:16
rosmaitaso, without microversions14:16
rosmaitawe either don't make changes14:16
rosmaitaor don't assert the tag14:16
stevelleso I really love what Graham has been saying on that guideline14:16
rosmaitastevelle: tell us more, i haven't looked in about a week14:17
stevelleI want glance to work toward the tag by simply not changing the API14:17
stevelleGraham is suggesting the alternative to microversions is "stop changing stuff"14:17
stevellewhen an API goes into Supported, no changes as all14:17
jokke__rosmaita: so easy, we don't assert the tag14:17
jokke__;)14:17
stevellewhen it's time to change that resource, you make a new version and he is trying to carve space for experimental apis14:18
hemanthmI haven't read that stuff yet, but what's a "change" here?14:18
*** limao_ has joined #openstack-meeting-414:18
stevellehemanthm: anything that can be seen is a change14:18
mugsiestevelle: well, not quite - but we shouild get api's right before saying users can rely on them14:18
*** armax has joined #openstack-meeting-414:18
rosmaitachange to url, change to resource representation, change to response codes, etc14:18
rosmaitabasically, anything14:18
rosmaitathat you can see through the api14:18
hemanthma bug fix too?14:19
rosmaitayep14:19
jokke__mugsie: o/ ... totally agree on that one ;)14:19
*** limao has quit IRC14:19
rosmaitaonly serious security ones will be allowed14:19
rosmaitaso basically, all our ocata changes are impossible under the guideline14:19
stevelleI agree mugsie, which is why I'm enthusiastic about that line of discussion on the guideline14:19
jokke__yeah, I'm just happy not asserting that tag14:19
jokke__for now14:19
mugsieyeah - I hope people come on board to back me up  :)14:19
jokke__lets say next 6 or 7 cycles14:19
mugsiecomments welcome14:20
stevellemy hope is that Glance can bundle intended API changes for 2y at a time and just increment major versions14:20
*** vks1 has joined #openstack-meeting-414:20
rosmaitai had a bunch of early comments, but have really nothing more to say14:20
rosmaitajust want this to be a point of information for everyone to cogitate upon14:21
rosmaitaand as mugsie points out, leave comments if you have an opinion14:21
rosmaitaany other comments about that?14:22
hemanthmI do but I don't want to derail the meeting :)14:22
stevellemaybe we can discuss in #openstack-glance after this14:22
rosmaitaok, hold 'em for open discussion14:22
rosmaitaor what stevelle said14:22
rosmaitaok, moving along, last update14:22
rosmaita#topic update - farewell to Ian14:23
*** openstack changes topic to "update - farewell to Ian (Meeting topic: glance)"14:23
rosmaita#link http://lists.openstack.org/pipermail/openstack-dev/2017-March/114462.html14:23
jcook=(14:23
hemanthm-214:23
rosmaitasigmavirus is moving on14:23
dharinic:(14:23
rosmaitayes, i am bummed, too14:23
* stevelle is now an abandoned change set14:23
sigmavirus=/14:24
*** limao has joined #openstack-meeting-414:24
sigmavirusI'm not thrilled either, but c'est la vie14:24
hemanthmAll the very best to you!14:25
rosmaitasigmavirus: thank you for all your service to glance, you will be missed a lot!14:25
dharinicGlance was so much fun and lively with sigmavirus/roosevirus around.14:25
stevellefair speed and don't take any wooden nickels, sigmavirus14:25
rosmaitaand as ttx pointed out, openstack expects to expand to encompass the entire universe of software, so we should meet again14:26
*** limao_ has quit IRC14:26
dharinicThank you for all the motivation sigmavirus. All the best. :)14:26
jokke__sigmavirus: I was afraid this will come14:26
sigmavirusrosmaita++14:26
rosmaitabut, the sad departure of sigmavirus does leave us with some holes to fill14:26
rosmaita#topic volunteers and responsibilities14:26
*** openstack changes topic to "volunteers and responsibilities (Meeting topic: glance)"14:26
sigmavirusy'all better step up... or else... my Rooseghost will haunt y'all14:26
* stevelle hides14:27
rosmaita#link https://etherpad.openstack.org/p/glance-pike-volunteers14:27
jokke__sigmavirus: Thanks a million and keep in touch! If we ever land to same area, lets get drunk as ducks. ;)14:27
rosmaitai didn't realize ducks were big drinkers14:27
hemanthmme neither14:27
jokke__rosmaita: they are not, thus they get very drunk ;)14:27
* hemanthm was about to google drunk ducks14:27
rosmaitajokke__: thanks, that explains it14:27
rosmaitaok, please open that etherpad14:28
rosmaitai've asked hemanthm to become release czar14:28
rosmaitaian's departure also leaves an opening on glance coresec14:28
rosmaitafor which i propose stevelle14:28
rosmaitai have a question about stable branch liason14:29
*** sshnaidm is now known as sshnaidm|mtg14:29
*** adisky_ has quit IRC14:29
rosmaitawhich i think jokke__ is answering "live" on the etherpad14:29
rosmaitaok, great14:30
rosmaitai like having different ptl - release czar - and stable branch people14:30
rosmaitai think it keeps a healthy balance of opinions on impacting issues14:30
rosmaitaok, cool14:30
rosmaitaalex_bash is doing documentation14:31
* jokke__ is still also part of the glance release team, and happy to keep it so and help out 14:31
rosmaitaasettle has enhanced the expections of the docs liason, so he'll be busy14:31
jokke__I've been following the OS release side pretty closely anyways14:31
rosmaitajokke__: great, you will provide some continuity14:32
rosmaitakey unfilled slots are: infra, which i am filling in for now, but i'm open to let someone else take over14:32
rosmaitakey thing about infra CPL is that the infra team wants a +1 from infra CPL before they approve changes14:33
rosmaitaso that slot *must* be filled14:33
rosmaitabut i'll do it for now14:33
jokke__for that, I'm not willing to step in :P14:33
rosmaitai was thinking of volunteering dharinic for oslo CPL14:33
jokke__Voluntold :)14:33
rosmaitasince she has some commits into oslo14:33
dharinicI would love that. :)14:33
rosmaitadharinic: that's great if you are serious, i don't want to make you do it14:34
hemanthmrosmaita: you already did :)14:34
rosmaitawell, i meant it to be a hint14:34
rosmaitai used the wrong font, i guess14:34
dharinicI was serious.14:34
rosmaitait all looks alike in irc!14:34
*** limao has quit IRC14:34
*** galstrom_zzz is now known as galstrom14:34
rosmaitadharinic: great, happy to have you do that14:35
dharinicI have contributed to oslo and would love to do this.14:35
dharinicThanks for volunteering me rosmaita14:35
rosmaitaeveryone: please review the expectations on https://wiki.openstack.org/wiki/CrossProjectLiaisons14:35
rosmaita#link https://wiki.openstack.org/wiki/CrossProjectLiaisons14:35
*** limao has joined #openstack-meeting-414:35
rosmaitaOK, a key unfilled CPL is QA14:35
rosmaitabut we can look for someone later on that14:36
jokke__hehe14:37
rosmaitamy thought is that once everyone is confirmed, i will move this etherpad into the priorities for pike page in teh specs repo, which i'll put up after the spec freeze14:37
rosmaitawhich reminds me, the spec proposal freeze is soon14:37
jokke__that will be fun position to take on ... it's shame sigmavirus is leaving ... would love to have his character dealing with them ;)14:37
rosmaita:)14:37
hemanthmjokke__: I think you're a good character fit too :P14:38
rosmaita#info spec proposal freeze - patch with spec must be up before 13:59 UTC on Thursday 30 March 201714:38
rosmaitaok, moving on14:38
jokke__hemanthm: _if_ I would understand anything about testing :P14:38
rosmaita#topic "owned" topics reports14:38
*** openstack changes topic to ""owned" topics reports (Meeting topic: glance)"14:38
*** links has quit IRC14:38
rosmaitaok, dharinic has been active on removing deprecated options14:39
rosmaitahemanthm has a patch up for E-m-C docs14:39
dharinichere is my update14:39
dharinicThe important opt: “show_multiple_locations”. 
We would be removing it in favor of RBAC (Role Based Access Control) from policy.json.  nikhil, rosmaita and I had some discussions on few combinations for the property rules and nikhil will be putting up a spec for it.14:39
dharinicI have a patch up with code changes for one such combination for review and opinions (https://review.openstack.org/#/c/444540/)14:39
rosmaitathank you14:39
dharinicAnother set of opts was the swift store auth opts like “swift_store_auth_address”, “swift_store_user” etc. There were to be removed in favor of reading related information from the swift store config file. This requires considerable code change with respect to swift store in multi-tenant mode (we are currently not allowing a swift conf file to be given if multi-tenant mode is on). I am working on this and will14:40
jokke__dharinic: just a reminder ... do we have the policy options in place for the multiple locations yet?14:40
dharinicI assume we do not need a spec/lite-spec for this ^14:40
rosmaitanikhil said he'd have a patch up soon for the removal spec, not sure if it's there yet, though i did see an early draft on an etherpad14:40
dharinicjokke__: Currently they are open.14:41
rosmaitadharinic: for the swift-opts, you mean?14:41
rosmaitajokke__: yes, we have policies, but the default is ""14:41
dharinicrosmaita: yeah, i meant spec/lite-sepc fopr swift auth opts.14:41
rosmaitait's a problem, as you'll see from nikhil 's spec14:41
dharinicfor the show_multiple_locations, nikhil will be putting up a patch soon14:41
rosmaitadharinic: were they the ones i said do release notes first?14:41
rosmaita(i am not fully caffeinated this morning)14:42
jokke__ok ... so we need to document the change well in release notes and make sure we do not open that up by anyone upgrading14:42
rosmaitajokke__: exactly!14:42
dharinicyes rosmaita. I have the release note: https://review.openstack.org/#/c/448316/14:42
rosmaitadharinic: ty14:42
rosmaitaso, instead of a lite spec, i asked dharinic to put up the release note14:42
rosmaitawe can review it to see what hte impact looks like14:43
rosmaitahopefully, won;t need a spec, but i haven't looked yet14:43
rosmaita#action everyone review https://review.openstack.org/#/c/448316/14:43
dharinicplease feel free to help me edit the release note for the swift store auth opts. Wordings are not great.. Want to make sure things are conveyed correctly.14:43
rosmaita#link https://review.openstack.org/#/c/448316/14:43
rosmaitaok, thanks14:43
rosmaitajokke__: i owe you reviews on your patches14:44
rosmaitai intend to go offline and do nothing but that this afternoon14:44
rosmaitago to get you unblocked14:44
dharinicAnd the last opt which i also started work on: https://review.openstack.org/#/c/447172/14:44
rosmaitaok, thanks to all the "owners" for keeping things moving!14:44
jokke__rosmaita: cheers ... there is some gate failures still down in that chain I haven't been able to figure out ... any help would be great14:45
rosmaitanext topic is a fun one, show and tell14:45
rosmaita#topic     docs update -- discuss for 5 minutes and then we will vote14:45
*** openstack changes topic to "docs update -- discuss for 5 minutes and then we will vote (Meeting topic: glance)"14:45
rosmaitaShinya Kawabata has a POC patch up for improving one of our docs pages, which right now is really hard to read because of the way the options and there descriptions are all jammed in together14:45
rosmaitahe put together a POC giving us 2 options14:45
*** sneti has joined #openstack-meeting-414:45
rosmaitaso please opent the next link in your browser:14:46
rosmaita#link http://docs-draft.openstack.org/80/423880/6/check/gate-glance-docs-ubuntu-xenial/628a2af//doc/build/html/configuring.html14:46
*** yfauser has quit IRC14:46
*** limao has quit IRC14:46
rosmaitaoptions: headings ("Configuring multiple swift accounts/stores") vs. definition list ("Configuring the RBD storage backend")14:46
stevelleand this patch is a rework before the lift and shift of this section to the proper place in openstack-manuals, right?14:46
rosmaitacorrect14:46
rosmaitathis is a readability issue on this page14:46
*** limao has joined #openstack-meeting-414:47
rosmaitaso, if you open that page14:47
hemanthmI like the latter14:47
rosmaitalook at the OTC in the left bar14:47
rosmaitai mean the TOC14:47
stevellethat readability issue will be fixed by `git rm` :)14:47
rosmaitanot a choice atm, though14:48
alex_bash+1 #214:48
*** sneti has quit IRC14:48
rosmaitaok, so the problem is that the options have bullets and it's hard to see what description goes with what option14:48
rosmaitaso the http://docs-draft.openstack.org/80/423880/6/check/gate-glance-docs-ubuntu-xenial/628a2af//doc/build/html/configuring.html#configuring-multiple-swift-accounts-stores14:48
rosmaitamakes each option a heading14:48
rosmaitapro: it also shows up in the TOC14:49
rosmaitacon: it's going to fill up the TOC when all these are headings14:49
stevelleI prefer the "multiple swift " formatting but I would love to see the option titles bolded or bumped in size one step14:49
rosmaitabut, it does make stuff easy to find14:49
jokke__rosmaita: please no :(14:49
*** sneti has joined #openstack-meeting-414:50
rosmaitaok, other option is like the RBD14:50
rosmaitaa simple definition list14:50
jokke__that toc becomes totally unusable if we make every option being heading and crapping it out14:50
rosmaitahttp://docs-draft.openstack.org/80/423880/6/check/gate-glance-docs-ubuntu-xenial/628a2af//doc/build/html/configuring.html#configuring-the-rbd-storage-backend14:50
rosmaitajokke__: that's my worry too14:50
stevellethere should be a way to limit the depth of the toc14:50
hemanthmYes, TOC won't be TOC any more with all the noise14:50
rosmaitastevelle: there is, we can keep stuff out of the toc14:50
stevelleif we can exclude those headings from toc that makes that formatting work14:51
rosmaitadon't have control over the size without hacking the styles, though14:51
jokke__it's already long as it is and if you're looking just for specific option and it's documentation you can always use search on that page14:51
rosmaitaeveryone ready to vote?14:51
hemanthmaye14:51
stevelleits the HRs that help for me, we could add HRs without the use of headings too14:51
jokke__stevelle: ++14:52
rosmaitahmmm ... i tend to not like HRs14:52
rosmaitai prefer the indentation like the RBD stuff14:52
rosmaitaanyway, that's why we can vote and just go with the majority14:52
jokke__rosmaita: that is more pythonic tbh14:52
rosmaitabelieve it or not this is my first vote, so let14:53
rosmaita's see what happens14:53
jokke__but the question is which one is more convenient for the non-developer reader14:53
stevelleso many questions, jokke__14:53
rosmaita#startvote (how to markup the config page) ? headings, definition-list14:53
openstackBegin voting on: (how to markup the config page) ? Valid vote options are headings, definition-list.14:53
openstackVote using '#vote OPTION'. Only your last vote counts.14:53
jokke__stevelle: information is key to right decisions14:53
rosmaita#vote definition-list14:53
hemanthm#vote definition-list14:54
jokke__#vote definition-list14:54
dharinic<dl>14:54
stevelle#vote definition-list14:54
dharinic#vote definition-list14:54
* stevelle is swayed14:55
rosmaitaanyone else?14:55
hemanthmalex_bash: mentioned #2 earlier14:55
rosmaitaalex_bash: ??14:55
alex_bashoption 2 has already carried, my vote is meaningless14:55
alex_bashI demand a recount14:56
rosmaitano vote is meaningless!14:56
rosmaitasome just have less meaning than others14:56
alex_bashso that I can vote first14:56
jokke__alex_bash: get your disagreement recorded if you have one so you can bitch about the "wrong" decision later ;)14:56
stevellealex_bash: you're just reading the exit polls14:56
alex_bash#vote definition-list14:56
rosmaitaok14:56
rosmaita#endvote14:56
openstackVoted on "(how to markup the config page) ?" Results are14:56
openstackdefinition-list (6): jokke__, dharinic, stevelle, alex_bash, hemanthm, rosmaita14:56
rosmaitaand it appears to be stuck14:56
rosmaitaanyway, it's a landslide for definition-list14:57
rosmaitaok, next topic14:57
jokke__be quick ... we have 3 left14:57
jokke__3 min I mean14:57
rosmaita#topic technical debt - time bomb14:57
*** openstack changes topic to "technical debt - time bomb (Meeting topic: glance)"14:57
rosmaita#link https://review.openstack.org/#/c/419074/14:57
*** limao has quit IRC14:57
rosmaitawe merged that last week, and14:57
rosmaitatick, tick, boom: https://review.openstack.org/#/c/448653/14:58
rosmaitajust a point of awareness14:58
*** limao has joined #openstack-meeting-414:58
rosmaita#topic - looking for owners14:58
*** openstack changes topic to "- looking for owners (Meeting topic: glance)"14:58
rosmaitai'm going to solicit for these on the ML14:58
*** lei-zh has joined #openstack-meeting-414:58
rosmaitaboth require some expertise we don't currently have, anyway14:58
rosmaita#topic open discussion14:59
*** openstack changes topic to "open discussion (Meeting topic: glance)"14:59
rosmaita50 seconds!14:59
alex_bashshameless own patch plug: https://review.openstack.org/#/c/436257/ & https://review.openstack.org/#/c/436258/ were +A, but had to rebase because of the time bomb14:59
alex_bashso close14:59
stevellemore talk of api stability and other topics in glance channel14:59
jokke__Thanks everyone!14:59
rosmaitathanks!15:00
rosmaita#endmeeting15:00
*** openstack changes topic to " (Meeting topic: ironic_neutron)"15:00
hemanthmThanks rosmaita. Thanks everyone.15:00
openstackMeeting ended Thu Mar 23 15:00:04 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2017/glance.2017-03-23-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2017/glance.2017-03-23-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2017/glance.2017-03-23-14.00.log.html15:00
*** sjmc7 has joined #openstack-meeting-415:00
*** alex_bash has left #openstack-meeting-415:00
*** cathrich_ has joined #openstack-meeting-415:00
*** cathrich_ is now known as cathrichardson15:00
*** premsankar has joined #openstack-meeting-415:01
sjmc7#startmeeting openstack search15:01
openstackMeeting started Thu Mar 23 15:01:30 2017 UTC and is due to finish in 60 minutes.  The chair is sjmc7. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: openstack search)"15:01
openstackThe meeting name has been set to 'openstack_search'15:01
*** TravT has joined #openstack-meeting-415:01
*** belmorei_ has joined #openstack-meeting-415:01
sjmc7morning15:02
*** belmoreira has quit IRC15:02
*** stevelle has left #openstack-meeting-415:02
rosmaitasorry, i went 2 sec over with glance meeting15:03
rosmaitaactually 4 sec15:03
Kevin_Zhengo/15:03
lei-zho/15:03
sjmc7i was 90 seconds late, so it all worked out15:03
rosmaitaexcellent!15:03
*** marst has joined #openstack-meeting-415:03
TravTo/15:03
sjmc7probably going to be a short one today15:04
sjmc7#topic Nova cells15:04
*** openstack changes topic to "Nova cells (Meeting topic: openstack search)"15:04
sjmc7I took a look through the list of implemented versioned notifications on https://docs.openstack.org/developer/nova/notifications.html#existing-versioned-notifications15:04
sjmc7The only one missing that we use is volume.[attach/detach] and i’m told someone is working on that now15:05
sjmc7I’m going to go through the payloads as well, but they look reasonably complete15:05
*** jokke__ is now known as jokke_15:05
sjmc7and actually in many cases are much more complete than the unversioned ones15:06
*** limao_ has joined #openstack-meeting-415:06
sjmc7so we may get a two-for-one and reduce or remove the API calls we have to make15:06
TravTthat's a positive15:06
lei-zhthat's a good news15:07
sjmc7yeah. i’ll try to go through that more carefully when i can carve out 30 minutes to do it15:07
gibisjmc7: attach is here https://review.openstack.org/#/c/401992/15:07
sjmc7the actual change itself should be quite easy. i’m inclined to switch over to the versioned ones entirely if they provide additional benefits15:08
sjmc7thanks gibi. i’ll keep an eye on it15:08
*** limao has quit IRC15:08
*** armax has quit IRC15:09
sjmc7if we can keep the two handlers there with minimal differences in the data they emit, we’ll do that15:10
sjmc7i’m not going ot invest a lot of time making the outputs identical15:10
*** limao_ has quit IRC15:10
*** yingjun has joined #openstack-meeting-415:10
sjmc7and we’ll recommend people use versioned ones15:10
*** cathrichardson has left #openstack-meeting-415:11
sjmc7#topic Resource registration UI code15:12
*** openstack changes topic to "Resource registration UI code (Meeting topic: openstack search)"15:12
sjmc7the only other thing i had on the agenda today was the work richard jones has been doing to move some code from searchlight-ui to horizon15:12
sjmc7he had some problems getting searchlight installed in devstack (I think because he was triyng to use elasticsearch 5) that i’ll work through with him, but it’ll be good to get that code moved out15:13
sjmc7i uploaded https://review.openstack.org/#/c/446620 to add elasticsearch 5 support15:14
sjmc7though the python-elasticsearch library will still be capped by global-requirements15:14
TravThmm interesting.15:14
*** matrohon has quit IRC15:14
TravTso did he get it working?15:14
TravTdid he try es 2?15:14
*** matrohon has joined #openstack-meeting-415:15
sjmc7not sure, our time zones only overlap by an hour and he filed it last night15:15
sjmc7i’ve asked for clarification on https://bugs.launchpad.net/searchlight/+bug/164825515:15
openstackLaunchpad bug 1648255 in OpenStack Search (Searchlight) "devstack plugin doesn't support elasticsearch 5.x" [Undecided,New] - Assigned to Ruslan Gustomyasov (rusik)15:15
sjmc7i didn’t really have much else for today. i was out for a long weekend and been busy with other stuff this week15:17
sjmc7#topic open discussion15:17
*** openstack changes topic to "open discussion (Meeting topic: openstack search)"15:17
sjmc7did anyone else have anything they wanted to talk about?15:18
TravTno, not today15:18
rosmaitanot me15:18
rosmaita(see, i am paying attention)15:18
*** sshnaidm|mtg is now known as sshnaidm15:18
rosmaita(he says guiltily)15:19
lei-zhI've assigned wsgi deploy blueprint to me, have looked on how other projects did this15:19
*** liangy has quit IRC15:19
sjmc7ah, yeah15:19
*** bobmel has quit IRC15:19
*** bobmel has joined #openstack-meeting-415:20
lei-zhif there is no weird issue running in apache, should not be too hard to fix15:20
sjmc7ok. there shouldn’t be, but you never know15:22
sjmc7to run for development i guess you’d host it in gunicorn or something15:22
lei-zhwe'd keep current api cmd for development and testing purpose, right15:24
*** woodard has quit IRC15:24
sjmc7yeah, if that’s what other projects have done15:24
lei-zhyeah15:25
lei-zhI'm finished15:25
*** bobmel has quit IRC15:25
sjmc7ok :)15:25
sjmc7if there’s nothing else, i’ll end it here and let people go to sleep15:25
sjmc7ok, thanks everyone!15:26
sjmc7#endmeeting15:28
*** openstack changes topic to " (Meeting topic: ironic_neutron)"15:28
openstackMeeting ended Thu Mar 23 15:28:12 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:28
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_search/2017/openstack_search.2017-03-23-15.01.html15:28
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_search/2017/openstack_search.2017-03-23-15.01.txt15:28
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_search/2017/openstack_search.2017-03-23-15.01.log.html15:28
*** yingjun has quit IRC15:29
*** liangy has joined #openstack-meeting-415:32
*** woodard_ has joined #openstack-meeting-415:36
*** spzala has joined #openstack-meeting-415:36
*** armax has joined #openstack-meeting-415:42
*** ttx has quit IRC15:44
*** jtaryma has joined #openstack-meeting-415:45
*** ttx has joined #openstack-meeting-415:46
*** shasha_t_ has joined #openstack-meeting-415:48
*** aunnam has joined #openstack-meeting-415:53
*** lei-zh has quit IRC15:54
*** uck has joined #openstack-meeting-415:55
*** lamt has joined #openstack-meeting-415:56
*** nkrinner is now known as nkrinner_afk15:57
*** dharinic- has joined #openstack-meeting-415:58
*** david-lyle_ is now known as david-lyle15:58
*** stevelle has joined #openstack-meeting-415:59
*** belmorei_ has quit IRC15:59
evrardjphello everyone16:02
cloudnullo/16:02
stevelleo/16:03
palendaeHello16:03
evrardjp#startmeeting openstack_ansible_meeting16:03
openstackMeeting started Thu Mar 23 16:03:41 2017 UTC and is due to finish in 60 minutes.  The chair is evrardjp. Information about MeetBot at http://wiki.debian.org/MeetBot.16:03
d34dh0r53o/16:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:03
*** openstack changes topic to " (Meeting topic: openstack_ansible_meeting)"16:03
openstackThe meeting name has been set to 'openstack_ansible_meeting'16:03
odyssey4meo/16:03
evrardjpThe agenda for today is16:04
evrardjp#link https://wiki.openstack.org/wiki/Meetings/openstack-ansible#Agenda_for_next_meeting16:04
xgermano/16:04
evrardjpIs there someone against the agenda for today?16:04
evrardjpor in english, everyone agrees with the topics?16:04
evrardjp:D16:04
odyssey4meit looks like the agenda is the same as the last two weeks - we haven't cleaned up :/16:04
evrardjpYes. Let me clean that up.16:05
*** fdegir has joined #openstack-meeting-416:06
evrardjpI propose we keep the topics for discussion, except the Operations guide that we'll skip for this time16:06
*** matrohon has quit IRC16:06
evrardjpOk let's assume the roll call is over, and everyone agrees16:07
*** unicell has joined #openstack-meeting-416:07
evrardjpPS: I miss asettle gifs.16:07
evrardjpso16:07
odyssey4melol16:07
evrardjp#topic Review action items from last week16:07
*** openstack changes topic to "Review action items from last week (Meeting topic: openstack_ansible_meeting)"16:07
evrardjppalendae will flip coins for names tomorrow for the python package ?16:07
palendaeevrardjp: Chosen!\16:08
palendaehttps://review.openstack.org/#/c/418076/16:08
evrardjpwoot!16:08
palendaeosa_toolkit16:08
evrardjp#link https://review.openstack.org/#/c/418076/16:08
palendaeAnd hopefully we'll get a passing gate16:08
evrardjpgood16:08
odyssey4megate passing will require that we have a general master passing gate, which we do not16:08
palendaeodyssey4me: Ah. In that case, I'll just keep rebasing :)16:08
evrardjpodyssey4me: let's talk about this in open discussion?16:09
*** unicell1 has quit IRC16:09
palendaeAnyway, the name was chosen and in that review16:09
*** oshidoshi1 has quit IRC16:09
evrardjp\o/16:09
odyssey4metempest tests are failing, and no-one except andymccr has taken the time to look into it, but I think he's been swamped so volunteers to resolve it are welcome16:09
evrardjp^ ^ ^ ^16:09
evrardjp#action help andymccr to unblock gates16:09
odyssey4mea general sha bump doesn't help because the powervm driver has an issue with incompatible requirements16:09
odyssey4methat's on the way to being resolved16:10
evrardjpthere is also work on ocata16:10
evrardjpcinder/tempest16:10
*** belmoreira has joined #openstack-meeting-416:10
evrardjpbut let's talk about that later16:10
evrardjpfirst let's finish last week action points16:10
evrardjp#action andymccr to look into getting an on-boarding room at the summit16:11
evrardjpthat's gonna be for next week.16:11
evrardjpok next topic!16:11
evrardjp#topic Discussion - Operations guide16:11
*** openstack changes topic to "Discussion - Operations guide (Meeting topic: openstack_ansible_meeting)"16:11
evrardjpasettle: being away let's skip this, except if someone wants to add something for her?16:12
evrardjp(only friendly messages are allowed)16:12
palendaeI've nothing to add16:12
odyssey4menope, except that anyone able should keep reviewing and patching16:12
evrardjpok, next topic16:12
evrardjp#topic Discussion - New periodic jobs16:12
*** openstack changes topic to "Discussion - New periodic jobs (Meeting topic: openstack_ansible_meeting)"16:12
evrardjpodyssey4me: ?16:13
odyssey4meit's running, it's failing for the same reason as the current master: http://logs.openstack.org/periodic/periodic-openstack-ansible-upgrade-aio-master-ubuntu-xenial/e58e9cf/console.html#_2017-03-23_08_33_38_36149016:13
*** belmoreira has quit IRC16:13
odyssey4meso basically the upgrade happens from ocata to master, there's nothing except a broken master stopping it from passing as far as I know16:13
odyssey4meI was thinking of adding another test for newton->ocata - thoughts?16:14
evrardjpit has value for me16:14
evrardjpmaking sure we can upgrade to latest official stable is good.16:14
odyssey4meok, I'll push up the infra change to add it16:15
odyssey4meonce that's going right I'll do the mitaka->newton one too16:15
evrardjpthat's fancy :)16:15
*** spzala has quit IRC16:15
jmccrorycan you still get trusty image for mitaka-newton?16:15
evrardjpthat will be a problem16:15
evrardjpif not now, it oculd16:16
evrardjpcould*16:16
evrardjpsame for N trusty16:16
odyssey4mejmccrory yeah, until mitaka's EOL'd that won't be an issue16:16
*** mgariepy has joined #openstack-meeting-416:16
jmccroryok cool16:16
evrardjpin the meantime it's not a problem, so let's do it :)16:16
odyssey4mejmccrory logan- we need to revisit the upgrade improvements etherpad and figure out where to go with it16:17
odyssey4mebut that's another topic, this one is done :)16:17
evrardjpok16:17
evrardjp#topic Release Planning and Decisions16:17
*** openstack changes topic to "Release Planning and Decisions (Meeting topic: openstack_ansible_meeting)"16:17
evrardjpodyssey4me: ?16:17
odyssey4mereleases will happen next week (which will be a minor version bump due to the repo build changes in Newton +)16:17
odyssey4methe repo build changes necessitated a minor revision bump to signal it16:18
odyssey4methat's a minor rev bump for newton and ocata16:18
odyssey4meIntegrated build is broken on master, but the sha bump PR should be fixed by https://review.openstack.org/#/c/448674/ - once the dependent patch merges and the SHA is bumped for nova-powervm.16:18
odyssey4meWe have some tempest issues in stable/ocata causing cinder jobs to fail, but the PR to bump tempest SHA in the role is broken atm (thinking about that I need to actually edit the tests repo instead – will fix quickly.16:19
odyssey4meby 'I' it means andymccr :) I'm literally copying and pasting his update16:19
odyssey4meUpgrade jobs are all working except cinder on Ocata (which should merge once the above fixes) and then they’ll be set to voting.16:19
odyssey4meThe cinderv3 work is still pending, the nova patch needs to merge: https://review.openstack.org/#/c/446508/ - then backports16:19
evrardjpit's a complete update from andymccr,  including non release conversations :)16:20
evrardjpI feel like he is here.16:20
evrardjpAnyway, please have a look!16:20
evrardjpok next topic16:20
evrardjp#topic Blueprint work16:20
*** openstack changes topic to "Blueprint work (Meeting topic: openstack_ansible_meeting)"16:20
*** erikmwilson has joined #openstack-meeting-416:21
evrardjpAny information to give there? Nothing pending except upgrade testing and operations guide?16:21
*** bobmel has joined #openstack-meeting-416:21
evrardjpok let's move to something else16:22
evrardjp#topic Open discussion16:22
*** openstack changes topic to "Open discussion (Meeting topic: openstack_ansible_meeting)"16:22
evrardjpHas anyone something to say? I feel like it's only odyssey4me and me talking today16:22
odyssey4me:p16:22
palendaeI don't really have anything today16:23
palendaeSeems like a lot of people are busy with other things16:23
evrardjpWe are sitting next to each other at the office, I don't need that to talk to him. :p16:23
*** TravT has left #openstack-meeting-416:23
xgermanwaiting my turn16:23
evrardjpnow would be it.16:23
palendaeevrardjp: Talking there wouldn't be documented though :)16:23
odyssey4mexgerman it's open discussion, so it's anyone's turn16:23
evrardjppalendae: fair point, fair point!16:24
xgermanok, #link https://review.openstack.org/44715116:24
xgermanthe trove people have some questions about the communities stance on networks bridging vm and control plane.16:24
evrardjpMassive commit scope :p16:25
*** dharinic has left #openstack-meeting-416:25
evrardjpthe communities, you mean general trove users, or our deployers?16:25
xgermanI am wondering if I need to add things for Octavia besides the iptables firewall?16:25
xgermancommunity he means OSA16:26
xgermandevelopers16:26
*** matrohon has joined #openstack-meeting-416:26
*** bobmel has quit IRC16:26
*** Julien-zte has quit IRC16:27
stevelleI am generally supportive of the solution xgerman is persuing here but we need folks to look and think hard about it16:27
evrardjpso the question is how to bring consensus on the two roles "way of integrating with osa"?16:27
xgermanyep16:27
odyssey4methis looks like it's working towards the ideal we discussed at the PTG16:27
xgermanyeah, I laid my thinking out in the response that there should be a security guide so operators can judge for themselves which risks they are taking16:28
*** Julien-zte has joined #openstack-meeting-416:28
*** Julien-zte has quit IRC16:28
evrardjpI agree16:28
kylek3hxgerman: agreed.  i just was pointing out the roles should be doing similar things16:29
*** Julien-zte has joined #openstack-meeting-416:29
evrardjpI will review this, but I don't think it's a bad starting point16:29
evrardjpagreed with kylek3h too there16:29
*** Julien-zte has quit IRC16:29
*** mohankumar has joined #openstack-meeting-416:29
evrardjpkylek3h: do you see other roles except trove that could have issues?16:29
*** Julien-zte has joined #openstack-meeting-416:29
kylek3hnot at the moment.  our focus has been on trove16:29
evrardjpthat could be a "osa community goal" in the future to move the role to this standard16:30
evrardjpwhatever the "this" means.16:30
xgermanI knew cue had similar issues but that project has been abandoned16:30
*** Julien-zte has quit IRC16:30
*** Julien-zte has joined #openstack-meeting-416:30
evrardjpok16:30
*** tonytan4ever has quit IRC16:31
odyssey4mexgerman this is looking way, way better and seems to address the concerns we raised early on16:31
*** Julien-zte has quit IRC16:31
*** tonytan4ever has joined #openstack-meeting-416:31
odyssey4mekylek3h from what I see so far, this is a good approach which provides the right flexibility between doing the nasty things for testing or small environments, but being able to break it out for larger environments16:31
evrardjp#action review https://review.openstack.org/#/c/447151 and talk about shared "osa community goals" for network integration best practices next week (useful for trove and octavia)16:31
odyssey4meI would be very interested in you guys tying a similar approach and helping to fix up the model to be responsibly secure for the small/test environments16:32
xgermanwhen I looked at the OSA docs there were chapters on networking but no text - so I assume that will be filled and I can go light on detals in my doc16:32
kylek3hodyssey4me: yeah.  i have Ravi working on a similar approach for trove16:32
*** SerenaFeng has joined #openstack-meeting-416:32
evrardjpkylek3h: woot16:33
evrardjpgood16:33
odyssey4mexgerman what docs are you referring to?16:33
*** mbruzek has quit IRC16:33
*** SerenaFeng has quit IRC16:33
odyssey4mexgerman if you're browsing the docs through github you will miss many things - make sure you're browsing the *published* docs16:34
xgerman#link https://docs.openstack.org/developer/openstack-ansible/draft-operations-guide/maintenance-tasks/network-maintain.html16:34
odyssey4meah, but that's the *draft* operations guide16:34
odyssey4meit's still being populated16:34
odyssey4methe deploy guide has networking info in it16:35
evrardjpProbably work to be done there, in a different section than the existing one16:35
odyssey4meas does the neutron role, and others16:35
evrardjp#link https://docs.openstack.org/developer/openstack-ansible/draft-operations-guide/maintenance-tasks/firewalls.html16:35
odyssey4mebut, to be clear, the intent it never to duplicate any upstream information16:35
odyssey4meall we ever decribe is how we lay things out and how to interact with OSA's deployment... any details about how octavia works should be submitted upstream16:36
*** liangy has quit IRC16:36
odyssey4mewe should only ever do a basic intro and point to upstream docs16:36
xgermanyes, I was more thinking how networks are defined in OSA. kyle3h had a comment and my thinking was to defer that to upcoming network guides16:36
evrardjpagreed16:36
evrardjpand agreed16:36
odyssey4menetworks being defined in OSA should be something in our docs16:37
odyssey4mehttps://docs.openstack.org/project-deploy-guide/openstack-ansible/draft/overview-network-arch.html16:37
odyssey4mehttps://docs.openstack.org/project-deploy-guide/openstack-ansible/draft/app-networking.html16:37
odyssey4methat brings me to another topic actually - we currently have two examples in the docs, but I think we'll need to have more16:38
xgerman+116:38
odyssey4mewe have a 'test' and 'production' example - I think we're going to have to rename those and add a 'ceph' example, and probably others16:38
xgermanI was able to figure it out but I also had some help ;-)16:38
xgermanOctavia example?16:38
odyssey4meI think perhaps an octavia example should perhaps be combined with something like autoscaling or whatever16:39
xgermank16:39
odyssey4meperhaps ironic, magnum, ocatavia16:39
*** spzala has joined #openstack-meeting-416:39
evrardjp+ heat, telemetry for autoscaling16:40
odyssey4methe point with the examples is to illustrate how to adjust based on the special things we can do16:40
evrardjpit makes sense to me16:40
odyssey4methe 'test' and 'prod' examples were trying to illustrate different configs needed for the amount of NIC's and the storage subsystem16:40
evrardjpok I think we are drifting from xgerman main topic, but it's good !16:42
evrardjpproductivitay16:42
evrardjp\o/16:42
xgermanyeah, documentation is a priority for the Octavia team16:43
evrardjpanyone else? logan- jmccrory? Need to add something to the agenda for next week, or need help on anything?16:43
logan-nope i've got nothing. good first stab at the iptables work xgerman, thanks. going to think about that some and compare to how i've got mine setup now16:44
evrardjpgreat.16:44
evrardjpyou're also using it for octavia? Else generic work can also be documented16:45
jmccrorywould be good to get this in https://review.openstack.org/#/c/445334/ rally is broken in newton without it16:45
evrardjp#action review https://review.openstack.org/#/c/445334/16:45
logan-no mine is generic across all of the other basic osa containers16:45
evrardjplogan-: do you want to move it to ops, this way you don't have to maintain it alone, or is specific?16:46
odyssey4methere are a bunch of small reviews in play, it'd be great if we could plow through those asap16:46
*** corey_ has joined #openstack-meeting-416:46
odyssey4medon't forget to look at the next page of reviews ;)16:46
xgerman:-)16:46
logan-i wouldn't mind pushing it to ops. will take a look at getting it into a review16:46
*** liangy has joined #openstack-meeting-416:47
evrardjpI don't force anything logan-, I'm just trying to help.16:47
*** cleong has quit IRC16:47
logan-yeah i think it would at the very least be helpful to have a port mapping of everything to reference later if we get a role template together16:48
evrardjpyeah16:48
evrardjp2.3 is gonna make role templates really easy btw16:48
*** sjmc7 has left #openstack-meeting-416:49
evrardjpit's gonna be without any code change, as there is a env var for the boilerplate path.16:49
evrardjpok, anything to wrap up?16:49
logan-interesting16:49
jmccroryoh that's one more than, the lxc connection plugin in 2.3 blows up. i did some digging and will added what i found in the review testing it, but basically they moved to using a constant for the remote file and use that more consistently16:50
evrardjp2.3 is gonna be an interesting one with long running connections, etc.16:50
evrardjpjmccrory: well that's not a bad thing to be more consistent. If you have a link I'd be happy to have a look at it.16:51
jmccrorysure, i'll add more details later today here https://review.openstack.org/#/c/446173/16:52
odyssey4mecloudnull ^16:52
evrardjpjmccrory: the refactor of connection systems in ansible 2.3 is a proof we may need to focus more on our plugins.16:52
* cloudnull looking16:52
evrardjpok anything else?16:54
*** mohankumar has quit IRC16:54
odyssey4melooks like we're pretty much out of time to discuss this - I'd say we move it to the channel16:54
evrardjpok thank you everyone!16:54
evrardjp#endmeeting16:54
*** openstack changes topic to " (Meeting topic: ironic_neutron)"16:54
openstackMeeting ended Thu Mar 23 16:54:57 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:54
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2017/openstack_ansible_meeting.2017-03-23-16.03.html16:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2017/openstack_ansible_meeting.2017-03-23-16.03.txt16:55
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2017/openstack_ansible_meeting.2017-03-23-16.03.log.html16:55
*** stevelle has left #openstack-meeting-416:55
*** LouisF has joined #openstack-meeting-416:56
*** ltomasbo is now known as ltomasbo|away16:57
*** songole has joined #openstack-meeting-417:00
LouisF#startmeeting service_chaining17:00
openstackMeeting started Thu Mar 23 17:00:30 2017 UTC and is due to finish in 60 minutes.  The chair is LouisF. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: service_chaining)"17:00
openstackThe meeting name has been set to 'service_chaining'17:00
LouisFhi all17:00
bcafarelhello17:00
songoleHi17:00
pcarverhi17:00
*** mak454 has joined #openstack-meeting-417:00
LouisF#agenda17:00
LouisFhttps://wiki.openstack.org/wiki/Meetings/ServiceFunctionChainingMeeting#Agenda_for_the_Networking-SFC_Meeting_.283.2F23.2F2017.2917:01
vks1hi all17:01
LouisF#topic CLI17:01
*** openstack changes topic to "CLI (Meeting topic: service_chaining)"17:01
LouisFCLI in python-neutronclient https://review.openstack.org/#/c/409759/17:01
LouisFMohan has posted an new patch17:02
LouisFplease review17:03
LouisFi think we are close to getting this merged17:03
LouisF#topic API reference17:04
*** openstack changes topic to "API reference (Meeting topic: service_chaining)"17:04
*** haleyb has quit IRC17:04
LouisFAPI reference https://review.openstack.org/#/c/389385 https://review.openstack.org/#/c/411409/17:04
bcafarelyes, I'll test it again too tomorrow to confirm all commands work fine (from someone else), that was requested in the review17:04
LouisFbcafarel: thanks17:04
pcarverI think the API reference is about done, but Armando's last comment was that he doesn't want to merge it until the API definition is done too. I think I'm getting close to having the API definition done.17:05
pcarverOr at least a patch set that passes tox17:05
LouisFpcarver: great, thanks17:05
pcarverI'm leaving out the exceptions17:05
LouisFpcarver: ok17:05
*** ltomasbo|away is now known as ltomasbo17:06
LouisF#topic Pike work17:06
* igordcard says hi17:06
*** openstack changes topic to "Pike work (Meeting topic: service_chaining)"17:06
*** unicell has quit IRC17:06
LouisF#topic SF tap17:07
*** openstack changes topic to "SF tap (Meeting topic: service_chaining)"17:07
*** iyamahat has joined #openstack-meeting-417:07
LouisFhad discussion last week to use "tap-enabled" instead of "insertion-mode"17:07
vks1LouisF: I have changed it17:08
LouisFi will post patch to update the spec17:08
LouisFvks1: ok17:08
vks1LouisF: Its a pretty much WIP. I have few questions will send out an email17:08
*** kzaitsev_ws has quit IRC17:08
LouisFvks1: we can discuss now it you like17:09
vks1LouisF: ok like I have decoupled the TAP enablement from the default mode17:09
vks1but then I see classifier builder to be changed for TAP support17:10
vks1as of the nature of the deployment17:10
vks1LouisF: also I want to first enable TAP at the end of chains17:12
LouisFvks1: are you talking about the adding "tap-enabled" to the API?17:12
vks1that is done17:12
vks1I have moved forward to change the ovs driver17:12
LouisFvks1: ok17:12
vks1and I was talking about changes I am doing in ovs driver17:13
LouisFhow are you planning to change the ovs driver to do the  tap operation?17:13
*** amotoki has quit IRC17:14
*** pcaruana has quit IRC17:14
vks1LouisF: probably I will send across the patch to get comment17:14
LouisFvks1: ok will wait for patch17:14
vks1that will make discussion easier17:15
vks1yeah17:15
LouisFcan you do at leat two patches: one for api/db changes and another of ovs work17:15
LouisFleast17:15
vks1ok will do that17:16
LouisFvks1: thanks17:16
LouisFvks1: you sent an email about an "active" tap - what do you mean by that?17:17
*** haleyb has joined #openstack-meeting-417:17
vks1LouisF: "active" means in deployment it should be inline17:18
LouisFvks1: explain?17:18
LouisFyou also mentioned about "other modes of deployment" - can you clarify?17:19
vks1LouisF: yeah like "standalone atp"17:20
vks1LouisF: few use case can be found at taas links17:21
vks1I will reply to mail chain with the link17:21
LouisFvks1: can you post link?17:21
vks1yeah sure17:21
vks1will do that, will be god for discussion17:21
igordcardvks1: in active taps you say they forward traffic back to networking devices... does that mean traffic will get duplicated towards the end of the chain?17:22
LouisFvks1: i want make sure that the use cases are investigated17:22
igordcardlinks are welcome17:22
*** bobmel has joined #openstack-meeting-417:22
LouisFduplicated traffic is a no no17:22
vks1LouisF: yeah will only do if everyone agress on that17:23
LouisFvks1: i am still inclear on the meaning of an "active tap"17:24
LouisFunclear17:24
vks1LouisF: https://www.gigamon.com/sites/default/files/resources/whitepaper/wp-understanding-network-taps-the-first-step-to-visibility-3164.pdf17:24
*** vishnoianil has quit IRC17:25
igordcardvks1: thanks17:25
vks1igordcard: :)17:25
vks1igordcard: this will open too many use cases for us17:25
vks1:;)17:25
*** bobmel has quit IRC17:27
LouisFvks1: the normal behavior of a SF is to process a payload and then forward it on to the next downsteam SF towards the destination17:28
*** iyamahat has quit IRC17:28
igordcardin this regard I was also thinking about whether sfc graphs (now service graphs) could be expanded to allow mirroring branches too17:28
LouisFvks1: and so it is essentially already performing the "active tap" behavior - right?17:28
igordcardinstead of just conditional branches17:29
igordcardthen tap would be incorporated there17:29
LouisFigordcard: you are referring to branching which is different from the tap operation17:30
vks1LouisF: in some sense17:30
igordcardLouisF: non-conditional branching... so the whole branch would be your tap (if your branch had a single function, that would be your tap device)17:31
vks1igordcard: explanation please ?17:31
igordcardvks1: it's essentially the same but modelled differently in the API, and you could have more functions after your first tap function... if wanted17:32
LouisFigordcard: the tap operation is simply to replicate packets and send them to a passive17:32
LouisFSF which acts as a black hole17:32
LouisFigordcard: branching is having the SF steer the packet flow to a sub-chain17:34
igordcardLouisF: the black hole claim is important... whatever gets implemented should then guarantee that even if the tap function returns traffic that it is discarded by the switch17:34
*** songole has quit IRC17:34
LouisFigordcard: agree any packets send from the egress port of the SF are ignored17:34
igordcardI agree it's best to not conflate the servuce graph with the taps, at least for the time being..17:35
LouisFhaving duplicate packets in the network is a recipe for disaster17:36
LouisFigordcard: +100017:36
igordcardyeah17:36
LouisFi think we should move ahead with the "passive tap" as defined in the BP and spec17:37
vks1LouisF: I agree , I see now issues with passive only17:37
vks1active can open lot of new issues17:37
LouisFvks1: such as?17:38
LouisFvks1: what issues do you have with passive tap?17:38
vks1LouisF: that's was I was referring to earlier , TAP  becoming the special case17:39
vks1for implementation17:39
LouisFvks1: ok probably best to post the patch for ovs changes to do the tap17:40
LouisFvks1: we can review and comment17:40
vks1yeah17:40
vks1will do that at earliest17:40
*** salmankhan has quit IRC17:40
LouisF#topic SF graph17:40
*** openstack changes topic to "SF graph (Meeting topic: service_chaining)"17:40
LouisFigordcard: how is sfc graph work?17:41
*** salmankhan has joined #openstack-meeting-417:41
*** krtaylor has quit IRC17:42
igordcardwas finishing some other technical work this week and still going slow with the graph17:42
LouisFigordcard: ok17:42
*** erikmwilson has quit IRC17:42
igordcardexpect new patchsets in 2 weeks or so17:43
*** iyamahat has joined #openstack-meeting-417:43
LouisFi want to ask you about the sharing of PPs between PP groups when using NSH encap17:44
*** erikmwilson has joined #openstack-meeting-417:44
LouisFigordcard: ok thanks on the patch update17:44
LouisFcan you elaborate on your ideas17:45
vks1LouisF: why the restriction ?17:45
LouisFvks1: the PP group defines how the load balancing is done to the PP in the group17:46
igordcardvks1: matching on the flow classifier unambiguously17:46
igordcardtoo17:46
*** rosmaita has left #openstack-meeting-417:46
*** lionelze has quit IRC17:46
igordcardLouisF: so if packets are encapd in nsh17:46
*** lionelze has joined #openstack-meeting-417:47
igordcardyou don't have to look at the classification to decide what the next group is17:47
igordcardyou just look at nsp/nsi (spi/si)17:47
LouisFthe LB for a PP group knows which SF have been allocated traffic17:47
igordcardso the action of load balacing across pps of a ppg will still exist and work just fine17:48
igordcardit's just that a particular PP may now be the object of load balacing in another group too17:49
LouisFso the LB for the group has to have exclusive ownership of the SFs in the group to do the LB operation properly17:49
igordcardtoday without pp correlation there is a tight coupling between the result of load balacing and the mac address of the selected ingress port of the port pair17:50
LouisFigordcard: it is not related to selecting the next hop17:50
igordcardut when you have nsh you don't have to wait to know which was the selected PP17:50
igordcards/ut/but17:51
*** links has joined #openstack-meeting-417:52
LouisFigordcard: with nsh there may be several SFs in a group that all receive the packets with same nsp value17:53
igordcard#link https://github.com/openstack/networking-sfc/blob/master/networking_sfc/services/sfc/agent/extensions/openvswitch/sfc_driver.py#L40817:53
*** sshnaidm is now known as sshnaidm|afk17:54
LouisFigordcard: agree the dest mac is used to steer the packets to the correct next hop SF17:54
LouisFin the current implementation17:54
igordcardit's just that it doesn't matter how many ppgs is a pp member of, when you're only looking at the nsh header for matching next hops17:55
*** mbruzek has joined #openstack-meeting-417:56
*** mbruzek has joined #openstack-meeting-417:56
LouisFbut with NSH, the LB can add a metadata tag to steer the packet to one of the downstream SFs in the PPG17:56
igordcardhow would the tag look like?17:57
*** s3wong has joined #openstack-meeting-417:57
igordcardis it needed when there is nsp+nsi already in the packet?17:57
igordcardI'll send a new email, about this subject, it's easier to do it in multi-line17:58
*** links has quit IRC17:58
igordcardand I have a quick question, is the team expecting to go to boston?17:59
LouisFnsp+nsi does not allow selection of one of several downstream SF at a specific hop (nsi) in a specific chain (nsp)17:59
igordcardwe could some brainstorming there on future work17:59
LouisFigordcard: yes17:59
igordcardnsp+nsi influences the selection that is executed by the sff (ovs basically) given what it knows about the infrastructure17:59
LouisFits a wrap bye  all18:00
igordcardand deployed sfcs18:00
*** SumitNaiksatam has joined #openstack-meeting-418:00
LouisFigordcard: email me18:00
igordcardLouisF: already18:00
igordcardalright*18:00
LouisF#endmeeting18:00
*** openstack changes topic to " (Meeting topic: ironic_neutron)"18:00
openstackMeeting ended Thu Mar 23 18:00:43 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/service_chaining/2017/service_chaining.2017-03-23-17.00.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/service_chaining/2017/service_chaining.2017-03-23-17.00.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/service_chaining/2017/service_chaining.2017-03-23-17.00.log.html18:00
*** ralonsoh has quit IRC18:04
*** LouisF has quit IRC18:05
*** ltomasbo is now known as ltomasbo|away18:08
*** haleyb has quit IRC18:08
*** matrohon has quit IRC18:08
*** anilvenkata has joined #openstack-meeting-418:11
*** vks1 has quit IRC18:15
*** Sukhdev has joined #openstack-meeting-418:17
*** bogdando has quit IRC18:22
*** mak454 has quit IRC18:23
*** haleyb has joined #openstack-meeting-418:23
*** anilvenkata has quit IRC18:34
*** neiljerram has quit IRC18:38
*** cjloader_ has joined #openstack-meeting-418:39
*** mgariepy has left #openstack-meeting-418:42
*** unicell has joined #openstack-meeting-418:43
*** egonzalez has joined #openstack-meeting-418:55
*** baoli has quit IRC19:00
*** baoli has joined #openstack-meeting-419:01
*** jtaryma is now known as joanna19:03
*** sneti has quit IRC19:07
*** sneti has joined #openstack-meeting-419:07
*** lionelze has quit IRC19:11
*** krtaylor has joined #openstack-meeting-419:15
*** uck has quit IRC19:15
*** baoli has quit IRC19:17
*** salmankhan has quit IRC19:21
*** revon has joined #openstack-meeting-419:22
*** bobmel has joined #openstack-meeting-419:23
*** sshnaidm|afk has quit IRC19:26
*** baoli has joined #openstack-meeting-419:26
*** sshnaidm has joined #openstack-meeting-419:27
*** bobmel has quit IRC19:28
*** matrohon has joined #openstack-meeting-419:32
*** baoli has quit IRC19:34
*** baoli has joined #openstack-meeting-419:44
*** spzala has quit IRC19:49
*** dtardivel has quit IRC20:00
*** uck has joined #openstack-meeting-420:01
*** belmoreira has joined #openstack-meeting-420:07
*** belmoreira has quit IRC20:07
*** baoli has quit IRC20:12
*** ekarlso has left #openstack-meeting-420:13
*** spzala has joined #openstack-meeting-420:17
*** egonzalez has quit IRC20:21
*** spzala has quit IRC20:23
*** liangy has quit IRC20:29
*** cjloader_ has quit IRC20:30
*** baoli has joined #openstack-meeting-420:32
*** corey_ has quit IRC20:38
*** rwallner has quit IRC20:47
*** liangy has joined #openstack-meeting-420:57
*** yamahata has joined #openstack-meeting-420:58
*** galstrom is now known as galstrom_zzz21:01
*** galstrom_zzz is now known as galstrom21:05
*** rfolco has quit IRC21:06
*** krtaylor has quit IRC21:08
*** sdague has quit IRC21:10
*** lamt has quit IRC21:10
*** lamt has joined #openstack-meeting-421:12
*** rbak has quit IRC21:12
*** rbak has joined #openstack-meeting-421:14
*** rbak has quit IRC21:18
*** bobmel has joined #openstack-meeting-421:24
*** galstrom is now known as galstrom_zzz21:25
*** galstrom_zzz is now known as galstrom21:26
*** matrohon has quit IRC21:27
*** lamt has quit IRC21:28
*** bobmel has quit IRC21:29
*** vishnoianil has joined #openstack-meeting-421:36
*** salmankhan has joined #openstack-meeting-421:37
*** uck_ has joined #openstack-meeting-421:39
*** uck has quit IRC21:39
*** spzala has joined #openstack-meeting-421:45
*** galstrom is now known as galstrom_zzz21:55
*** bobh has quit IRC21:58
*** haleyb has quit IRC22:03
*** erikmwilson has quit IRC22:12
*** bobmel has joined #openstack-meeting-422:13
*** erikmwilson has joined #openstack-meeting-422:16
*** bobmel has quit IRC22:17
*** sshnaidm is now known as sshnaidm|off22:21
*** mbruzek has quit IRC22:29
*** baoli has quit IRC22:30
*** sneti has quit IRC22:32
*** dave-mcc_ has joined #openstack-meeting-422:33
*** liangy has quit IRC22:36
*** dave-mccowan has quit IRC22:36
*** dave-mccowan has joined #openstack-meeting-422:38
*** dave-mcc_ has quit IRC22:40
*** unicell1 has joined #openstack-meeting-422:46
*** unicell has quit IRC22:46
*** marst has quit IRC22:50
*** vishnoianil has quit IRC22:53
*** bobmel has joined #openstack-meeting-422:53
*** bobmel has quit IRC22:58
*** srwilkers has quit IRC22:58
*** salmankhan has quit IRC23:03
*** pmesserli has quit IRC23:08
*** klamath has quit IRC23:23
*** vishnoianil has joined #openstack-meeting-423:25
*** uck_ has quit IRC23:26
*** spzala has quit IRC23:27
*** spzala has joined #openstack-meeting-423:30
*** vishnoianil has quit IRC23:33
*** spzala_ has joined #openstack-meeting-423:34
*** spzala has quit IRC23:34
*** spzala has joined #openstack-meeting-423:35
*** spzala_ has quit IRC23:38
*** hongbin has quit IRC23:38
*** spzala has quit IRC23:39
*** vishwanathj has quit IRC23:43
*** vishnoianil has joined #openstack-meeting-423:47
*** bobh has joined #openstack-meeting-423:48
*** egonzalez has joined #openstack-meeting-423:48
*** armax has quit IRC23:55
*** spzala has joined #openstack-meeting-423:58

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