Thursday, 2015-08-06

*** MarkAtwo_ has joined #openstack-meeting-400:17
*** MarkAtwood has quit IRC00:19
*** KunalGandhi has quit IRC00:37
*** jmcbride has joined #openstack-meeting-400:42
*** IlyaG has quit IRC00:51
*** ivar-laz_ has joined #openstack-meeting-400:51
*** Tango|2 has quit IRC00:52
*** ivar-lazzaro has quit IRC00:55
*** ivar-laz_ has quit IRC00:56
*** jmcbride has quit IRC01:01
*** echoingu_ has quit IRC01:06
*** puranamr has joined #openstack-meeting-401:07
*** Brian has joined #openstack-meeting-401:08
*** Brian is now known as Guest1741301:08
*** IlyaG has joined #openstack-meeting-401:12
*** Sukhdev has quit IRC01:15
*** dims_ has joined #openstack-meeting-401:21
*** dims has quit IRC01:22
*** jmcbride has joined #openstack-meeting-401:23
*** IlyaG has quit IRC01:23
*** jmcbride has quit IRC01:25
*** sdake has joined #openstack-meeting-401:27
*** galstrom_zzz is now known as galstrom01:28
*** s3wong has quit IRC01:28
*** sdake_ has joined #openstack-meeting-401:30
*** MarkAtwo_ has quit IRC01:32
*** sdake has quit IRC01:34
*** SourabhP has quit IRC01:39
*** harshs has joined #openstack-meeting-401:40
*** echoingumesh has joined #openstack-meeting-401:41
*** makarandp has quit IRC01:45
*** yamamoto has joined #openstack-meeting-401:46
*** galstrom is now known as galstrom_zzz01:46
*** yamamoto has quit IRC01:47
*** yamamoto has joined #openstack-meeting-401:47
*** yamamoto has quit IRC01:49
*** harshs has quit IRC01:56
*** dims has joined #openstack-meeting-402:03
*** dims_ has quit IRC02:05
*** dims_ has joined #openstack-meeting-402:06
*** dims has quit IRC02:09
*** sdake_ has quit IRC02:09
*** IlyaG has joined #openstack-meeting-402:10
*** galstrom_zzz is now known as galstrom02:10
*** markvoelker has quit IRC02:11
*** markvoelker has joined #openstack-meeting-402:12
*** bharath has quit IRC02:13
*** vivek-ebay has quit IRC02:16
*** echoingumesh has quit IRC02:19
*** puranamr has quit IRC02:19
*** dannywilson has quit IRC02:20
*** echoingumesh has joined #openstack-meeting-402:20
*** irenab_ has joined #openstack-meeting-402:22
*** dims_ has quit IRC02:22
*** echoingumesh has quit IRC02:24
*** irenab has quit IRC02:24
*** irenab_ is now known as irenab02:24
*** galstrom is now known as galstrom_zzz02:35
*** IlyaG has quit IRC02:36
*** yamamoto has joined #openstack-meeting-402:39
*** puranamr has joined #openstack-meeting-402:40
*** irenab has quit IRC02:40
*** irenab has joined #openstack-meeting-402:40
*** harshs has joined #openstack-meeting-402:43
*** rfolco has quit IRC02:56
*** krtaylor has quit IRC02:59
*** markvoelker has quit IRC03:04
*** puranamr has quit IRC03:12
*** krtaylor has joined #openstack-meeting-403:12
*** bharath has joined #openstack-meeting-403:13
*** irenab has quit IRC03:17
*** bharath has quit IRC03:18
*** irenab has joined #openstack-meeting-403:22
*** csd has quit IRC03:27
*** csd has joined #openstack-meeting-403:29
*** puranamr has joined #openstack-meeting-403:34
*** lazy_prince has joined #openstack-meeting-403:40
*** irenab has quit IRC03:40
*** irenab has joined #openstack-meeting-403:45
*** vivek-ebay has joined #openstack-meeting-403:47
*** vivek-ebay has quit IRC03:53
*** ramanjaneya_ has joined #openstack-meeting-403:56
*** coolsvap|away is now known as coolsvap03:58
*** irenab has quit IRC04:02
*** lazy_prince has quit IRC04:03
*** irenab has joined #openstack-meeting-404:03
*** markvoelker has joined #openstack-meeting-404:04
*** vivek-ebay has joined #openstack-meeting-404:05
*** markvoelker has quit IRC04:09
*** vivek-ebay has quit IRC04:10
*** irenab has quit IRC04:10
*** vivek-ebay has joined #openstack-meeting-404:10
*** irenab has joined #openstack-meeting-404:11
*** Guest17413 has quit IRC04:11
*** bharath has joined #openstack-meeting-404:15
*** bharath has quit IRC04:19
*** puranamr has quit IRC04:22
*** vivek-ebay has quit IRC04:25
*** vivek-ebay has joined #openstack-meeting-404:26
*** lakshmiS has joined #openstack-meeting-404:28
*** vivek-ebay has quit IRC04:28
*** vivek-ebay has joined #openstack-meeting-404:29
*** lakshmiS has quit IRC04:34
*** MarkAtwood has joined #openstack-meeting-404:37
*** lakshmiS has joined #openstack-meeting-404:38
*** IlyaG has joined #openstack-meeting-404:39
*** Brian has joined #openstack-meeting-404:47
*** Brian is now known as Guest330504:47
*** Guest3305 has quit IRC04:49
*** irenab_ has joined #openstack-meeting-404:49
*** irenab has quit IRC04:50
*** irenab_ is now known as irenab04:50
*** MarkAtwood has quit IRC04:59
*** irenab_ has joined #openstack-meeting-405:00
*** MarkAtwood has joined #openstack-meeting-405:00
*** irenab has quit IRC05:00
*** irenab_ is now known as irenab05:01
*** lakshmiS has quit IRC05:01
*** vivek-ebay has quit IRC05:03
*** jpekkari has joined #openstack-meeting-405:03
*** irenab has quit IRC05:05
*** IlyaG has quit IRC05:05
*** irenab has joined #openstack-meeting-405:06
*** IlyaG has joined #openstack-meeting-405:07
*** irenab has quit IRC05:13
*** bharath_ has joined #openstack-meeting-405:15
*** lazy_prince has joined #openstack-meeting-405:17
*** bharath_ has quit IRC05:20
*** harshs has quit IRC05:22
*** Brian has joined #openstack-meeting-405:32
*** Brian is now known as Guest6643905:33
*** Guest66439 has quit IRC05:34
*** IlyaG has quit IRC05:36
*** yamahata has quit IRC05:43
*** SourabhP has joined #openstack-meeting-405:50
*** markvoelker has joined #openstack-meeting-405:51
*** markvoelker has quit IRC05:56
*** dims has joined #openstack-meeting-406:03
*** dims has quit IRC06:09
*** irenab has joined #openstack-meeting-406:14
*** irenab has quit IRC06:22
*** irenab has joined #openstack-meeting-406:24
*** ramanjaneya_ has quit IRC06:24
*** Brian has joined #openstack-meeting-406:30
*** Brian is now known as Guest6655006:30
*** Guest66550 has quit IRC06:35
*** mohankumar has quit IRC06:46
*** belmoreira has joined #openstack-meeting-406:52
*** blogan has quit IRC07:03
*** blogan has joined #openstack-meeting-407:04
*** lazy_prince has quit IRC07:06
*** irenab has quit IRC07:08
*** irenab has joined #openstack-meeting-407:08
*** zeih has joined #openstack-meeting-407:10
*** numan has joined #openstack-meeting-407:24
*** zeih has quit IRC07:27
*** Brian has joined #openstack-meeting-407:30
*** Brian is now known as Guest8095707:31
*** numan has quit IRC07:33
*** pbourke has quit IRC07:33
*** pbourke has joined #openstack-meeting-407:33
*** ramanjaneya_ has joined #openstack-meeting-407:46
*** SourabhP has quit IRC07:47
*** numan has joined #openstack-meeting-407:50
*** zeih has joined #openstack-meeting-407:52
*** markvoelker has joined #openstack-meeting-407:52
*** sdake has joined #openstack-meeting-407:54
*** markvoelker has quit IRC07:56
*** apuimedo has joined #openstack-meeting-407:59
*** zeih has quit IRC07:59
*** Guest80957 has quit IRC08:06
*** IlyaG has joined #openstack-meeting-408:08
*** IlyaG has quit IRC08:12
*** tfukushima has joined #openstack-meeting-408:12
*** tfukushima has quit IRC08:15
*** tfukushima has joined #openstack-meeting-408:17
*** tfukushima has quit IRC08:22
*** Brian has joined #openstack-meeting-408:32
*** Brian is now known as Guest7757408:32
*** xingchao has joined #openstack-meeting-408:59
*** RedShift has joined #openstack-meeting-409:12
*** RedShift is now known as Guest8209109:12
*** zeih has joined #openstack-meeting-409:15
*** Guest82091 has quit IRC09:18
*** MarkAtwood has quit IRC09:22
*** yamamoto has quit IRC09:26
*** Guest77574 has quit IRC09:29
*** matrohon has joined #openstack-meeting-409:31
*** Brian has joined #openstack-meeting-409:33
*** Brian is now known as Guest1177209:33
*** xingchao has quit IRC09:34
*** xingchao has joined #openstack-meeting-409:44
*** yamamoto has joined #openstack-meeting-409:44
*** zeih has quit IRC09:46
*** dims has joined #openstack-meeting-409:49
*** zeih has joined #openstack-meeting-409:49
*** qwebirc19039 has joined #openstack-meeting-409:52
*** markvoelker has joined #openstack-meeting-409:53
*** zeih has quit IRC09:54
*** qwebirc19039 has quit IRC09:56
*** markvoelker has quit IRC09:57
*** Guest11772 has quit IRC10:04
*** ramanjaneya_ has quit IRC10:14
*** Brian has joined #openstack-meeting-410:24
*** Brian is now known as Guest3210510:25
*** tfukushima has joined #openstack-meeting-410:29
*** RedShift has joined #openstack-meeting-410:31
*** RedShift is now known as Guest9205510:31
*** Guest32105 has quit IRC10:41
*** dims_ has joined #openstack-meeting-410:51
*** dims has quit IRC10:53
*** markvoelker has joined #openstack-meeting-410:54
*** markvoelker has quit IRC10:58
*** sdake has quit IRC11:07
*** xingchao has quit IRC11:08
*** sankarshan is now known as sankarshan_away11:09
*** MarkAtwood has joined #openstack-meeting-411:10
*** MarkAtwood has quit IRC11:15
*** yamamoto has quit IRC11:16
*** Brian has joined #openstack-meeting-411:20
*** Brian is now known as Guest1704311:20
*** shalq has joined #openstack-meeting-411:22
*** Guest17043 has quit IRC11:34
*** Guest92055 has quit IRC11:39
*** klamath has joined #openstack-meeting-411:52
*** klamath has joined #openstack-meeting-411:52
*** jpekkari has quit IRC11:53
*** yamamoto has joined #openstack-meeting-411:55
*** markvoelker has joined #openstack-meeting-412:16
*** Brian has joined #openstack-meeting-412:20
*** Brian is now known as Guest4484712:20
*** woodard has joined #openstack-meeting-412:21
*** dims has joined #openstack-meeting-412:24
*** dims_ has quit IRC12:27
*** VW_ has joined #openstack-meeting-412:34
*** krtaylor has quit IRC12:50
*** yamamoto has quit IRC12:50
*** VW_ has quit IRC12:52
*** VW_ has joined #openstack-meeting-412:52
*** VW_ has quit IRC12:53
*** VW_ has joined #openstack-meeting-412:54
*** VW_ has quit IRC12:56
*** Guest44847 has quit IRC12:56
*** VW_ has joined #openstack-meeting-412:56
*** RedShift has joined #openstack-meeting-412:57
*** RedShift is now known as Guest4202412:58
*** MarkAtwood has joined #openstack-meeting-413:00
*** VW_ has quit IRC13:01
*** Guest42024 has quit IRC13:02
*** yamamoto has joined #openstack-meeting-413:02
*** krtaylor has joined #openstack-meeting-413:03
*** yamamoto has quit IRC13:04
*** MarkAtwood has quit IRC13:05
*** pmesserli has joined #openstack-meeting-413:06
*** yamamoto has joined #openstack-meeting-413:09
*** abhishekk has joined #openstack-meeting-413:09
*** yamamoto has quit IRC13:10
*** yamamoto has joined #openstack-meeting-413:10
*** rfolco has joined #openstack-meeting-413:18
*** aventerav has joined #openstack-meeting-413:19
*** bunting has joined #openstack-meeting-413:20
*** jpeeler has quit IRC13:20
*** wko has joined #openstack-meeting-413:29
*** TheIntern has joined #openstack-meeting-413:29
*** marcusvrn has joined #openstack-meeting-413:30
*** singlethink has joined #openstack-meeting-413:32
*** pmesserli has quit IRC13:32
*** mestery has quit IRC13:32
*** jmckind has joined #openstack-meeting-413:34
*** mestery has joined #openstack-meeting-413:38
*** VW_ has joined #openstack-meeting-413:38
*** IlyaG has joined #openstack-meeting-413:39
*** IlyaG has quit IRC13:43
*** bknudson has joined #openstack-meeting-413:44
*** MarkAtwood has joined #openstack-meeting-413:49
*** harshs has joined #openstack-meeting-413:49
*** wokuma has joined #openstack-meeting-413:51
*** RedShift has joined #openstack-meeting-413:55
*** sigmavirus24_awa is now known as sigmavirus2413:55
*** sdake has joined #openstack-meeting-413:55
*** RedShift is now known as Guest102513:55
*** jmcbride has joined #openstack-meeting-413:57
*** TheIntern is now known as TheIntern_awa14:00
*** jckasper has quit IRC14:01
*** bpoulos has joined #openstack-meeting-414:01
sigmavirus24No glance meeting?14:02
sigmavirus24nikhil_k: ?14:02
rosmaitasigmavirus24: good morning14:02
flaper87meeting?14:02
flaper87:D14:02
flaper87ops14:02
flaper87just read sigmavirus24's message14:02
sigmavirus24Someone should start it14:02
sigmavirus24And then hand it over to nikhil when he shows up14:02
*** MarkAtwood has quit IRC14:03
rosmaitasigmavirus24: go for it14:03
sigmavirus24#startmeeting glance14:03
flaper87getting the agenda14:03
openstackMeeting started Thu Aug  6 14:03:20 2015 UTC and is due to finish in 60 minutes.  The chair is sigmavirus24. Information about MeetBot at http://wiki.debian.org/MeetBot.14:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:03
*** openstack changes topic to " (Meeting topic: glance)"14:03
openstackThe meeting name has been set to 'glance'14:03
sigmavirus24#chair nikhil_k14:03
openstackCurrent chairs: nikhil_k sigmavirus2414:03
sigmavirus24#link https://etherpad.openstack.org/p/glance-team-meeting-agenda14:03
sigmavirus24That's our agenda ^14:03
abhishekko/14:03
harshso/14:03
jokke_o/14:03
sigmavirus24Courtesy meeting reminder: ativelkov, cpallares, esheffield, flaper87, flwang1, hemanthm, ivasilevskaya, jokke_, kragniz, lakshmiS, mclaren, mfedosin, nikhil_k, Nikolay_St, Olena, pennerc, rosmaita, sigmavirus24, sabari, TravT, zhiyan, pkoniszewski, krykowski, ajayaa, GB21, bpoulos, harshs, abhishekk, bunting14:03
buntingo/14:04
rosmaitao/14:04
*** jmcbride has left #openstack-meeting-414:04
nikhil_ksigmavirus24: thanks for starting14:04
sigmavirus24nikhil_k: all yours ;)14:04
sabario/14:04
*** jmcbride has joined #openstack-meeting-414:04
sigmavirus24nikhil_k: take it away :D14:05
*** MarkAtwood has joined #openstack-meeting-414:05
*** TheIntern_awa has quit IRC14:05
nikhil_kSO, we had the midcycle last week and there were a couple of discussion items that I wanted to bring up here as the write couldn't be completed in time. Other items can come on the ML14:05
*** jmckind has quit IRC14:05
nikhil_k#topic glance_store and glance14:05
*** openstack changes topic to "glance_store and glance (Meeting topic: glance)"14:05
*** radez_g0n3 is now known as radez14:06
nikhil_kThe relationship, as you all know, is bitter sweet14:06
nikhil_kand a proposal was made to put back the store modules in glance tree (Same repo)14:06
jokke_++ :P14:06
sigmavirus24Why?14:06
flaper87I'm interested in knowing the reasoning behind that14:07
nikhil_kno objections were raised at that time and the use cases known intially weren't supporting the need of a separate lib14:07
sigmavirus24I see absolutely no benefits to doing so and there was no reasoning provided for it on the ML or elsewhere as part of a summary14:07
nikhil_kfor example, glance_store being consumed by other projects isnt considered favorable14:07
jokke_my personal reasoning would be that having it separate causes more issues than solves them as there is no use case to have them separate14:07
nikhil_ksigmavirus24: ?14:08
flaper87In addition to that, I'd also like to mention that we've put lots of efforts in splitting out and merging it back gives us nothing14:08
flaper87jokke_: what issues?14:08
*** jmckind has joined #openstack-meeting-414:08
flaper87nikhil_k: why isn't it considered favorable?14:08
nikhil_kthe summary can be as long as needed14:08
jokke_glance_store being separate lib has one extra surface to break our dependencies and gating due to the fact that we gate glance against released libs, not against the head14:08
sigmavirus24nikhil_k: sure, but this discussion wasn't forwarded to the mailing list.14:08
flaper87jokke_: that's true for every library we have14:09
sigmavirus24jokke_: so we add a reverse gate at glance_store that tests with glance against the latest glance_store14:09
sigmavirus24there are ways around that14:09
*** MarkAtwood has quit IRC14:09
jokke_just check on #openstack-glance discussion today between myself and jamielennox14:09
jokke_flaper87: true, so why have one extra there that has no benefots being separate14:10
flaper87jokke_: there are benefits, it's just that people don't agree with those14:10
*** degorenko has quit IRC14:10
nikhil_kflaper87: for the reason that the projects do not want to know the backend details, deal with authN/Z issues, creation of cyclic dependency between projects consuming glance which in turn consuming store14:10
jokke_sigmavirus24: sure, but as said that's a benefit for you to merge it back in. I'd like to hear benefits keeping it out14:10
sigmavirus24jokke_: administrators may only have a bug in glance_store and only want to update glance_store to include that fix on a stable branch. They might not want to analyze all of the fixes between what they have installed and what they need for glance before upgrading14:10
nikhil_kthe discussion was complementary, so the summarization won't be accurate or complete14:10
flaper87nikhil_k: if that's the case, then we should prevent users to get the locations and remove direct_url14:11
nikhil_kguess, someone needs to start it14:11
flaper87because that exposes details about the backend14:11
sigmavirus24I posit there will be fewer fixes in stable glance_store than stable glance14:11
*** mclaren has joined #openstack-meeting-414:11
flaper87it's sad that for such an important topic there's not a good summary of what happened, TBH14:11
*** vikram_ has joined #openstack-meeting-414:11
jokke_sigmavirus24: so we should separate every module to their own repo's to give 200 packages for admins to keep track of14:12
jokke_?14:12
sigmavirus24jokke_: I expect better from you than strawman arguments14:12
flaper87sigmavirus24: ++14:12
sigmavirus24The store is not a service14:12
mclarenum, is this glance_store?14:12
flaper87mclaren: yup14:12
nikhil_kwell expression of sadness might be good but more important is to raise rational arguments for any outstanding use cases14:12
mclarenThat's my fault then.14:12
mclarenI just threw out the idea of re-integrating it to see what folks thought.14:13
*** Guest1025 has quit IRC14:13
sigmavirus24jokke_: we could easily split out glance into micro-services though, I'm sure that would go great14:13
nikhil_kthe glance_Store topic was a bit unexpected and the summarization was even tricker with no one taking notes at that time for the same reason14:13
flaper87nikhil_k: which I'm doing and I'd expect those arguments to be raised for us to understand why this is happening14:13
jokke_sigmavirus24: I honestly would be really surprised any admin being interested to have projects split for them to keep track of14:13
flaper87mclaren: I'm currently asking what's the reasoning behind that idea14:13
nikhil_kI don't want to misinterpret people so trying to get some thoughts before creating another community deadlock14:14
*** sdake has quit IRC14:14
mclarenwell it wasn't a firm proposal first of all14:14
jokke_but my only reasoning bringing it back is that there is no known use cases for it and it causes overhead to maintain alone14:14
sigmavirus24jokke_: I guess following your logical progression, we should be merging requests back into Glance?14:14
jokke_nothing more religious than that ;)14:14
sigmavirus24Because it's one less library for operators to be concerned with14:14
mclarenI guess the motivation was that decoupling the store and the rest of the code can create some additional overhead/complexity.14:15
jokke_sigmavirus24: if glance is only use case for requests, absolutely14:15
flaper87jokke_: there are use cases, they just haven't been implemented yet because, oh well, nova still uses v1 and has some hacks to talk to glance14:15
jokke_but I think there might be few others as well14:15
flaper87mclaren: but it's been around for what, 2, 3, cycles?14:15
nikhil_kflaper87: in that case the issue is that whether nova wants to use glance_store and that was proposed against14:16
flaper87I'm pretty sure OPs/packages are way passed delivering it14:16
nikhil_kwith the proposal for a seam for glance as a long term solution the needs for store is less14:16
flaper87nikhil_k: I keep missing the when and why, mostly the why14:16
nikhil_k^14:16
*** bpoulos has quit IRC14:16
flaper87because we talked about this in Paris and everything was good14:16
nikhil_kless == minimal14:17
* flaper87 really doens't like the proposal of seam14:17
flaper87:P14:17
flaper87(as stated in the review)14:17
nikhil_kmy use case then was store was needed for some task operations but then we don't want users to use glance_store for that14:17
nikhil_kso that use case has gone down the drain14:17
flaper87nikhil_k: agreed14:17
flaper87We've always been reluctant to let users consume glance_store14:18
mclarenI guess in terms of the store the questions are: 1) is it/will it be consumed by anything other than glance14:18
flaper87The real use case would be for the under-cloud14:18
nikhil_kso, is the only outstanding use case now is deciding whther nova needs to use glance_store or not?14:18
flaper87mclaren: there seem to be 2 answeres to that14:18
flaper87also, in addition to nova's use case, we also have cinder14:18
nikhil_kor more generic question like mclaren proposed14:19
flaper87which interacts with images too14:19
flaper87if you ask me, I'd say yes, there are still use-cases (the ones I've mentioned already)14:19
jokke_I haven't heard anyone from cinder side being interested of consuming glance_store14:19
flaper87jokke_: when the store was proposed, there was interest14:19
flaper87we'd have to check again to make sure they didn't change their minds14:20
nikhil_kalright, so this is exactly what we needed some action items!14:20
*** radez is now known as radez_g0n314:20
*** radez_g0n3 is now known as radez14:20
nikhil_k#action flaper87, mclaren : check with cinder if they want to /should use glance_store14:21
mclarenfwiw I don't feel terribly stongly about this. Basically if there's consensus it's unlikely to be used, and people think its a good idea we can put it back. If not, no problemo!14:21
*** irenab has quit IRC14:21
nikhil_k#action flwang (images liaison for nova): check with nova if they need to /should use glance_store14:21
flaper87tbh, I'd rather have folks interested in more important tasks than merging glance_store back. Even if the original use-cases are gone14:21
sigmavirus24We should also carry this discussion to the ML14:22
flaper87I don't see, as of now, glance_store as a big burden for us14:22
flaper87sigmavirus24: ++14:22
sigmavirus24For example flwang isn't in here and probably hasn't seen our mention and will not know they have an action item14:22
flaper87that'd be easier than pinging each team14:22
sigmavirus24flaper87: agreed14:22
* flaper87 will do that14:22
flaper87ACTION ME!14:22
nikhil_ksigmavirus24: not everyone affected by this are likely to respond on ML and I want a consensun and not a deadlock at the end of the cycle14:22
flaper87nikhil_k: seriously, ML is the medium for cross-project discussions14:23
flaper87lets ask those folks to respond14:23
mclarennikhil_k: ok, will check with cinder14:23
flaper87or the cp meeting14:23
flaper87which is very hard for me to attend because TZs14:23
nikhil_kwhoever sends to the ML, make sure it reaches cores/drivers/active contributors inbox without tags/filters14:23
nikhil_kwhich I can do14:24
sigmavirus24nikhil_k: to be fair, I think cinder/nova cores monitor the ML much better than we do =/14:24
flaper87sigmavirus24: ++14:24
nikhil_kthat's a preference problem that I can't solve, unfortunately14:24
flaper87nikhil_k: whatever works for me, I'm happy to send it unless you prefer sending it.14:25
nikhil_kirc is expected but governance doesn't enforce/soft enforce ML14:25
flaper87nikhil_k: but that's also not playing nice with the community, which has chosen the ML as a medium for these dscussions14:25
nikhil_kflaper87: I will send it tonight14:25
flaper87nikhil_k: thanks14:25
flaper87nikhil_k: you can cc folks there14:25
nikhil_kflaper87: might be a good discussion topic for this cycle14:25
*** dims has quit IRC14:25
*** carl_baldwin has joined #openstack-meeting-414:26
flaper87nikhil_k: I've started that discussion N times but I digress (and agree)14:26
*** dims has joined #openstack-meeting-414:26
nikhil_k:)14:26
nikhil_kok, moving on in the interest of time14:26
nikhil_k#topic glance v2 reupload and image status change14:26
*** openstack changes topic to "glance v2 reupload and image status change (Meeting topic: glance)"14:26
*** marekd has joined #openstack-meeting-414:27
nikhil_kso, glance v1 allows status changes as a part of the metadata update14:27
nikhil_kglance v2 can result into unrecoverable 409s (conflicts during uploads)14:27
nikhil_kthere's a proposal for enabling that so that when a upload fails from say nova, a reupload to glance be possible on the killed state14:28
nikhil_kstatus*14:28
mclarennikhil_k: remind me, which status changes does v1 allow users to do? thanks14:28
nikhil_k#link https://review.openstack.org/#/c/206250/6/specs/liberty/upload-retry.rst14:28
nikhil_kmclaren: PUT on active can put image to queued status. hemanthm can confirm as he raised this yesterday14:29
nikhil_kthis is big change in terms of the way uploads would work14:30
mclarenso the existing v1 api allows the user to take the image out of active state? I hadn't realised...14:30
nikhil_k:)14:30
mclarenbug or feature? :-)14:31
jokke_perhaps v3 is good place to consider such, specially thinking how much there has been cry to stabilize the v2 api14:31
nikhil_ksimilar to this #link https://github.com/openstack/nova/blob/master/plugins/xenserver/xenapi/etc/xapi.d/plugins/glance#L18414:31
mclarenwow, I had no idea!14:33
jokke_mclaren: I'd say that's very much bug as it breaks the guarantee to immutability14:33
flaper87tbh, I had no idea either14:33
hemanthmneither did I. I found out yday working on the upload retry spec14:33
mclarenhmm, have we verified this?14:33
hemanthmI did14:33
flaper87I haven't read the spec but I will14:33
flaper87hemanthm: thanks14:34
mclarenhemanthm: ok, so this will move and image from active back to queued?14:34
mclarenand->an14:34
*** TravT has joined #openstack-meeting-414:34
rosmaitahttps://github.com/openstack/nova/blob/master/plugins/xenserver/xenapi/etc/xapi.d/plugins/glance#L18414:34
hemanthmmclaren: yes. I created a snapshot and with a PUT operation, I could change the status to queued and back to active again14:35
flaper87jeez14:36
flaper87do we have a bug for this already?14:36
mclarenMindblown.14:36
flaper87**214:36
nikhil_kflaper87: I think we should check if this is not a breaking change. It may be API backward incompatible14:36
hemanthmnot, yet. Will create one after reproducing in devstack. I reproduced it in our staging env14:36
nikhil_kit may come in the realm of API backward incompatible14:37
jokke_thanks hemanthm14:37
flaper87mmhh, true14:37
jokke_hemanthm: so between state changes, does it allow to upload a new data into the image as well?14:38
* flaper87 needs to think about this14:38
nikhil_kanyways, let's give people time to digest this lightning strike14:38
mclarenlol14:38
rosmaitai don't think it's a breaking change if it was never supposed to happen14:38
nikhil_kjokke_: you can reupload if image is put again in queued state14:38
flaper87rosmaita: that's my thinking too14:38
*** jasondot_ is now known as jasondotstar14:38
hemanthmjokke_: I have't tried that14:38
flaper87rosmaita: that's a bug in the API design so, not really a breaking change14:38
rosmaitaflaper87: +114:39
flaper87sorry, in the API implementation14:39
flaper87which was designed to be immutable14:39
rosmaitaalso seems like a security problem14:39
mclarenthe original image bytes won't be handled properly ... lots of problems14:39
flaper87rosmaita: agreed14:39
jokke_we guarantee that the image is immutable ... this is security vulnerability and if it breaks someone abusing it, we seriously can't care14:39
*** RedShift has joined #openstack-meeting-414:39
rosmaitajokke_: +114:39
flaper87omg, did we just talked for 20mins on public, logged ,IRC about a security issue?14:39
*** RedShift is now known as Guest9820514:39
* flaper87 head -> desk14:39
jokke_yes14:39
flaper87:P14:39
nikhil_kI think this is the issue with glance v1 exposed publicly14:40
rosmaitaguess i shouldn't have used the "S" word14:40
flaper87in our defense, no one knew anything about this14:40
nikhil_kas most glance v1 are internal only and aren't subjected to this risk14:40
nikhil_kmoving on for now14:40
rosmaitasigmavirus24: it's a private cloud problem!14:40
flaper87I mean, are supposed to be internal but they aren;t14:41
nikhil_k#topic Reuse the deleted image-member14:41
*** openstack changes topic to "Reuse the deleted image-member (Meeting topic: glance)"14:41
flaper87hemanthm: mind filing a bug for this? :D14:41
flaper87(erm, this -> the above)14:41
sigmavirus24rosmaita: hm?14:41
nikhil_k#link   https://review.openstack.org/#/c/207042/14:41
hemanthmflaper87: yes. I'm just holding off until I reproduce this on devstack, which I'm doing currently14:41
nikhil_kthat's the spec14:41
flaper87hemanthm: awesome14:41
rosmaitasigmavirus24: i'm thinking only private clouds would expose v1 to end-users14:42
nikhil_k#link https://review.openstack.org/#/c/190895/14:42
sigmavirus24rosmaita: yeah14:42
nikhil_kshalq: was that you?14:42
jokke_hemanthm: thanks for that, please ping the -glance channel when you're done14:42
shalqyes14:42
hemanthmjokke_: sure14:42
nikhil_kshalq: can you please elaborate on what you wanted to discuss14:43
nikhil_k?14:43
*** yamamoto has quit IRC14:43
shalqthe spec is ready for review, and we have a customer issue for that case.14:43
nikhil_kI reviewed the code as well and it looked mostly good last seen14:44
flaper87I'll get back to this spec tomorrow morning14:44
flaper87can we wait till then?14:45
flaper87I'd love to take a look at it14:45
shalqthanks, flaper8714:45
flaper87shalq: thank you :)14:45
nikhil_kshalq: all it needs are some functional and unit tests14:45
shalqokay, I will design some unit test for that later.14:46
nikhil_kthanks14:46
nikhil_k#topic Returning when illiegal body ( bunting )14:46
*** openstack changes topic to "Returning when illiegal body ( bunting ) (Meeting topic: glance)"14:46
nikhil_k#link https://review.openstack.org/#/c/207150/14:47
nikhil_kbunting: around?14:47
mclarenbunting: type faster!14:47
buntingAs start points out on the review, using chunked encoding means that weob seems to remove the body14:47
*** nhairston has joined #openstack-meeting-414:48
buntingunless someone knows how to detect if a body exists in a chuncked encoding, it may mean that if it is not chuncked it will return 400 and if it is it will ignore the body14:48
jokke_by quick look I'd rather say we do not deserialize it14:48
*** delattec has joined #openstack-meeting-414:48
mclarenbasically we can't figure out a way to always detect if the initial request had a body or not14:48
*** lakshmiS has joined #openstack-meeting-414:49
mclarenwe're either being dumb, or webob just won't let us do it14:49
jokke_webob.Request seems to be quite happy with all bodies on all requests14:49
*** yamamoto has joined #openstack-meeting-414:49
mclarensigmavirus24: any idea if there's a canonical way to figure out if the request had a body?14:49
*** Guest98205 has quit IRC14:50
mclarenwe've tried a few things but keep hitting gotchas, eg is_body_readable doesn't seem to work for some HTTP verbs14:50
nikhil_khmm, yeahhh14:51
jokke_there is also problem that some of the ways to identify body are invasive so we really don't want to check them on all requests14:52
sigmavirus24mclaren: in webob, I'm not sure14:52
*** TheIntern has joined #openstack-meeting-414:53
nikhil_kmy ideas stock is empty momentarily14:53
mclarensigmavirus24: nikhil_k ok14:53
nikhil_kguess, we can discuss more on the review/-glance14:53
nikhil_kthanks mclaren14:53
nikhil_k#topic reviews14:54
*** openstack changes topic to "reviews (Meeting topic: glance)"14:54
jokke_so some mechanisms to access the body in the request-object actually changes content lenght etc. so if we check only requests we don't want to have body, we don't need to care and that's doable14:54
mclarensure, just thought someone might have seen/done this before14:54
abhishekkhi, https://review.openstack.org/#/c/207847/14:54
nikhil_kmclaren: I think there's some environ var you can set on wsgi.__ but it's been a while14:54
abhishekk^^^ This patch fixes below three bugs,14:54
abhishekkhttps://bugs.launchpad.net/glance/+bug/1478690 - Request ID has a double req- at the start14:54
openstackLaunchpad bug 1478690 in Glance "Request ID has a double req- at the start" [Undecided,In progress] - Assigned to Abhijeet Malawade (abhijeet-malawade)14:54
abhishekkhttps://bugs.launchpad.net/glance/+bug/1480191 - User can send 'request-id' from headers to glance api14:54
abhishekkhttps://bugs.launchpad.net/glance/+bug/1480196 - Request-id is not getting returned if glance throws 500 error14:54
openstackLaunchpad bug 1480191 in Glance "User can send 'request-id' from headers to glance api" [Undecided,In progress] - Assigned to Abhijeet Malawade (abhijeet-malawade)14:54
openstackLaunchpad bug 1480196 in Glance "Request-id is not getting returned if glance throws 500 error" [Undecided,In progress] - Assigned to Abhijeet Malawade (abhijeet-malawade)14:55
*** banix has joined #openstack-meeting-414:55
abhishekkI have removed the code which is generating the request-id and instead using oslo_middleware's RequestId in the default paste deploy pipeline.14:55
jokke_abhishekk: the second one is by design, not a bug14:55
abhishekkPlease review and give your feedback for the same.14:55
abhishekkjokke_: ok, but this can be used to flood the log files14:56
abhishekkI can send large value in a header right?14:56
nikhil_kabhishekk: you can but the proxy servers can stripe such things and is sort of recommended deployment strategy14:57
abhishekkbut we can restrict user to send x-openstack-request-id in headers by using request-id middleware14:57
abhishekkand no other services are accepting this from header14:58
jokke_abhishekk: what's the max length of the req-id that can be sent?14:58
nikhil_ksabari: around for quick peak in https://review.openstack.org/#/c/184351/ ?14:58
sabarinikhil_k: half-awake :)14:58
nikhil_ksabari: any pre-prepared notes?14:59
nikhil_k:)14:59
flaper87can I ask you to review these patches and the spec for it? https://review.openstack.org/#/c/197899/14:59
sabarinikhil_k: just want to make sure the image is completely deleted is not stuck in upload14:59
abhishekkjokke_: header length is configurable14:59
flaper87these -> that one and the one it depends on14:59
nikhil_kwko: I approved your blocked review :)14:59
flaper87I'd love to get feedback on the spec14:59
nikhil_k#action all: review https://review.openstack.org/#/c/195820/14:59
wokumathanks nikhil_k14:59
abhishekkjokke_: https://github.com/openstack/glance/blob/master/glance/common/wsgi.py#L8815:00
jokke_abhishekk: so we have no limitation on the req-id leght apart from max header size?15:00
nikhil_ksabari: gotcha, it should ideally be put in killed state when it's data is deleted and then deleted15:00
abhishekkjokke_: yes15:00
nikhil_kabhishekk: ah cool15:00
*** MarkAtwood has joined #openstack-meeting-415:00
*** sjmc7 has joined #openstack-meeting-415:00
nikhil_kwe are sort out of time, thanks for adjusting in this busy meeting15:00
flaper87o/15:01
nikhil_khave a good one all! I can be available for any review requests on #openstack-glance15:01
abhishekkthank you all, please review the patches15:01
nikhil_kThanks all!15:01
sigmavirus24#endmeeting15:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:01
openstackMeeting ended Thu Aug  6 15:01:29 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-08-06-14.03.html15:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-08-06-14.03.txt15:01
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-08-06-14.03.log.html15:01
sigmavirus24We're invading searchlight's time =P15:01
nikhil_k:P15:01
TravT#startmeeting openstack search15:01
openstackMeeting started Thu Aug  6 15:01:55 2015 UTC and is due to finish in 60 minutes.  The chair is TravT. 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:02
nikhil_kand stepping on toes of people, so good things to make the most of time I sup15:02
TravTo/15:02
nikhil_ko/15:02
lakshmiSo/15:02
nikhil_kTravT: your hi-5 is very hip ;)15:02
TravTlol15:02
sjmc7o/15:03
*** abhishekk has left #openstack-meeting-415:03
rosmaitao/15:03
*** bunting has left #openstack-meeting-415:03
TravTOk, i know sigmavirus24 is around15:03
TravThere's our agenda:15:03
TravThttps://etherpad.openstack.org/p/search-team-meeting-agenda15:03
TravTadd anything you want to it15:03
TravTi don't have any general status updates today.15:03
* sigmavirus24 neither15:04
sigmavirus24except webob is awful15:04
TravTlol15:04
TravTso, on to topics15:04
TravT#topic Testing15:04
*** openstack changes topic to "Testing (Meeting topic: openstack search)"15:04
TravT    Python 3 https://review.openstack.org/#/c/209939/15:04
sjmc7yay!15:05
TravTsvilgelm just put that patch up...15:05
TravTlet's take a look at it and if it looks good, this should mean we can enable another set of gate tests for python, I believe15:05
lakshmiSthats great. no need to test on case by case basis15:06
TravT    FYI if you use POSTMAN: https://www.getpostman.com/collections/8c0b1e05875c7c58e96715:06
TravTI just have a few POSTMAN tests that I use for manual testing.  If you use postman, thought I'd share them15:07
lakshmiSi think we should link that to documentation under examples/tools15:07
TravTyeah, i was thinking maybe a wiki15:07
TravTnot sure that should be in source15:07
TravTsince they'll change...15:08
TravTbut the manual testing leads to the next topic.15:08
TravT    Functional Tests - https://blueprints.launchpad.net/searchlight/+spec/set-up-functional-tests15:08
TravTwe are missing functional / integration tests / whatever you want to call them.15:08
TravTand this is starting to be more problematic i think15:09
sjmc7yes... it's really easy to break stuff at the moment15:09
lakshmiSI have started working on glance plugin tests, but getting elasticsearch up is the key15:09
sjmc7lakshmiS - was the unmerged patch to glance any help, or not?15:09
TravTdoes it make sense to build a mock ES layer?15:09
ekarlsoo/15:10
nikhil_koh boy15:10
sjmc7TravT - i did consider that15:10
lakshmiSsjmc7: yes i did take whatever i can15:10
nikhil_kthat's a black hole15:10
sjmc7but yeah, it's potentially a lot of work. unfortunately there's no 'fake es driver' i could find15:10
lakshmiSnikhil_k is assigned to build mock ES layer15:10
nikhil_k:P15:10
TravTlakshmiS: do you want to talk a bit more on what you are working on?15:11
nikhil_kso, I thought we ere going with #link https://review.openstack.org/#/c/157209/ to begin with?15:12
lakshmiSfor timebeing i am spinning up ES and testing the glance plugin code for indexing image data15:12
*** krtaylor has quit IRC15:13
TravThow are you spinning up ES?15:13
TravTi mean are you doing that manually?15:13
lakshmiSmanually :)15:13
TravTokay, so, what can we do to help out here?15:14
sjmc7i did do some work on that15:14
sjmc7in that patch15:15
nikhil_ksjmc7: wondering if the issue is that we need stronger gating?15:15
lakshmiSsjmc7: i haven't created a new patch but I have code which I can also add to that patch15:15
nikhil_kis the breaking stuff due to missing in-tree functional tests or is for cross project updates testing?15:16
sjmc7nikhil_k - the problem is that the unit tests don't cover everything15:16
*** jmcbride has quit IRC15:16
sjmc7no, it's in-tree15:16
nikhil_kgotcha15:16
*** vivek-ebay has joined #openstack-meeting-415:17
nikhil_kyeah, I was under the impression that the patch would land and give us more direction15:17
* david-lyle slips in late15:17
TravTso, this one in glance needs to be abandoned obviously15:17
sjmc7that patch on its own can't land15:17
lakshmiSI will create a new patch and merge with my code as startup then15:18
TravTsjmc7, i know this is something you worked on early.  what do we need to with infra to make this work?15:19
sjmc7i've never worked with infra..15:19
*** vishwanathj has joined #openstack-meeting-415:19
TravTok, so lakshmiS will port this over to searchlight15:19
TravTand then maybe we should have follow up discussion / even a hangout if necessary15:20
nikhil_kTravT: why infra?15:20
TravTnikhil_k, i don't know... steve has that in his notes on the BP15:20
*** dannywilson has joined #openstack-meeting-415:20
nikhil_kah15:20
nikhil_ksjmc7: may be that's after we have done gating work, iiuc?15:20
sjmc7i think my note was about getting it gating - i'm not sure elasticsearch is typiucally available15:21
TravTwell, it isn't typically available.15:21
sjmc7the WIP glance patch assumed e-s was available on the system15:21
TravTbut our devstack installer installs it15:21
sjmc7ok, so that's maybe what the note about infra was about15:21
*** harshs has quit IRC15:21
TravTwhen we install searchlight via our plugin15:21
TravTthanks to ekarlso15:21
TravTinfra has a ES installation library that both we and ceilometer depend on15:22
TravTis that what you mean?15:22
sjmc7yeah, that sounds like it would be useful, so maybe it's a solved problem. like i say, i know very little about infra15:23
TravTok.  well, i can say that with devstack, you get a working env with ES15:23
lakshmiSceilometer might already have gating jobs with dependency on ES. I could talk with them on how they do it15:24
TravTlakshmiS, that'd be great.15:24
*** blahRus has joined #openstack-meeting-415:24
TravTwe have some good patches in the pipeline and I would feel a lot better with these integration level tests in the gate.15:25
TravTokay, so it seems like we have next steps there.15:25
TravTlakshmiS, if you want to have a time setup to talk sooner, then please do.  I know with the timezone diff it can be hard.15:26
lakshmiSsure15:26
TravT#topic Planning a liberty 3 prioritization hangout (TravT)15:26
*** openstack changes topic to "Planning a liberty 3 prioritization hangout (TravT) (Meeting topic: openstack search)"15:26
TravTSo, i'd really like to have a release at end of liberty 3.15:27
TravTand we have a number of blueprints in the pipeline.15:27
TravTsome of them have patches, some don't.15:27
TravTbut i think we should start focusing most efforts on a few of them...15:27
david-lylelakshmiS: there is a gate-tempest-dvsm-ceilometer-es job in project-config/zuul/layout.yaml that looks promising15:28
lakshmiSthx david-lyle15:28
TravTfunctionally, I think nova plugin, designate plugin should be the functional target.15:29
sjmc7from my perspective, the most important BPs i've done work on are swapping out 'index' and 'type' for an unchanging 'resource name'; nova; plugin config15:29
TravTIMO we should focus on helping get through what has been started.15:30
TravTAnd there are a number of items like you just mentioned sjmc7 that are about solidifying the api and code15:31
*** sdake has joined #openstack-meeting-415:31
*** MarkAtwood_ has joined #openstack-meeting-415:31
sjmc7yeah. i'm working on your comments on the nova one; i'd like reviews on the 'resource name' one15:31
TravTi did provide a review on the resource one15:31
TravTthere is some room for discussion in it.15:31
sjmc7ok15:31
*** Brian has joined #openstack-meeting-415:31
TravTwe have topics for those in just a sec.15:31
sjmc7i'll try to spend some time today, been a busy week15:31
sjmc7k15:31
*** daneyon has quit IRC15:32
*** Brian is now known as Guest1820915:32
*** daneyon has joined #openstack-meeting-415:33
TravTso, maybe next week in this meeting or as a separate meeting after next week, we should have a walkthrough of the BPs and check their target series.15:33
TravTthat's all.15:33
TravT#topic bug review15:33
nikhil_kTravT: do you think we shoud have a action item for such things? or wait for the video conferencing stuff?15:33
*** openstack changes topic to "bug review (Meeting topic: openstack search)"15:33
TravTnikhil_k: it might be a lot easier to do a video conference to walk through the blueprints and talk about them15:34
TravTprobably take less time and provide richer forum for discussion.15:34
TravTI could send out a doodle poll for times.15:34
TravTwhat do you think?15:34
rosmaitaTravT: +115:34
TravTok15:35
sjmc7yup15:35
* TravT forgets the command for action items.15:35
lakshmiSare you planning for next week?15:35
TravTit can be next week or the week after.15:35
TravTare you around next week?15:36
nikhil_kTravT: works for me15:36
*** Guest18209 has quit IRC15:36
lakshmiSyes. earlier the better to finalize on what BP's will go in15:36
*** galstrom_zzz is now known as galstrom15:36
TravT#action TravT will setup a BP prioritization review meeting for Liberty 315:36
nikhil_kTravT: might worth doing some prep work on our sides for the meeting next week15:36
TravTguess that wasn't it15:37
TravTnikhil_k, ok15:37
nikhil_kTravT: that's it!15:37
TravTok, i'll work on that.15:37
TravTon to bug reviews.15:37
nikhil_kthanks15:38
TravTthere are a few that already have some review.15:38
TravTone of them is critical15:38
TravT    Already one +215:38
TravT    Critical - Ceilometer / Notifications: https://review.openstack.org/#/c/20239215:38
TravT    High - Glance indexing https://review.openstack.org/20771915:38
TravT    Medium - Doc update https://review.openstack.org/20875015:38
*** singlethink has quit IRC15:38
TravTPlease try to look at them.15:39
TravT#topic Blueprint review15:39
*** openstack changes topic to "Blueprint review (Meeting topic: openstack search)"15:39
*** IlyaG has joined #openstack-meeting-415:39
TravTsjmc7, as we just discussed, i did put some comments on the nova patch.15:40
TravTanything about that which we should discuss in larger forum?15:40
sjmc7yep, working on them15:40
TravTok, cool.15:40
sjmc7just the issue of denormalizing15:40
sjmc7specifically what you called out with glance image names, flavor names15:41
TravTyeah, what occurred to me looking through that patch was that we might have to think about the concept of plugins affecting other plugins.15:41
TravTso, to explain briefly to everybody here.15:42
sjmc7right - the nova plugin can't listen to glance notifications, for instance15:42
sjmc7well.. i take that back, we can assign multiple handlers15:42
sjmc7it does create that mass-update scenario though15:42
*** krtaylor has joined #openstack-meeting-415:42
TravTin the nova data, sjmc7 was putting things like image name in there when the instance is indexed.15:42
TravThowever image name can change independent of the instance15:43
nikhil_kbut that's from the instance response for the image-meta info15:43
nikhil_kright?15:43
TravTbut the nova plugin which indexes instances doesn't get notifications related to that15:43
nikhil_kright15:43
sjmc7it can do, i can add a handler15:43
nikhil_kthta was my concern with nova notifications in our call last week15:44
*** IlyaG has quit IRC15:44
nikhil_kI wonder if for nova we should make a call to the api on notification trigger?15:44
nikhil_kif we do not want to go down the route of direct access to DB15:44
TravTsjmc7, so, you are thinking that the nova plugin would include an image notification handler as well?15:44
sjmc7no, but it needs to hook into glance notifications15:45
TravTok.15:45
TravTi was trying to think how that would affect message consumption and acknowledgment15:45
lakshmiSmay there should be link from image updates independend of instance updates and link them in ES index15:45
nikhil_kinteresting15:45
nikhil_kTravT: I think one more issue is15:46
nikhil_knova has static image-meta where as the one on the image itself might change15:46
nikhil_knova basically copies over that info15:46
TravTand does nova ever update that data?15:47
rosmaitano15:47
*** jckasper has joined #openstack-meeting-415:47
nikhil_kI think nova admin api might15:47
TravTis it even updated when an instance is first created?15:47
nikhil_kneed to double check15:47
rosmaitahow are we getting the image_ properties from nova?15:47
nikhil_kAPI call15:48
rosmaitai didn't think those were exposed in the API?15:48
nikhil_kTravT: it's copied from glance when instance is (first) booted15:48
nikhil_krosmaita: some are, right? you are correct mostly all are hidden15:48
rosmaitathe novaclient displays image name, but it does a request to get the image detail and constructs it client'side15:49
TravTso novaclient call's glance anyway?15:49
rosmaitawell, by proxying through the compute api15:49
TravTor is it calling the nova server for image info and nova server is just proxying?15:49
nikhil_ksecond15:49
TravT(v1 / v2 fun)15:49
nikhil_knah15:50
nikhil_kjust bad separation15:50
nikhil_kit might be worth investigating proposing a standard immutable prop in glance to avoid such things15:51
rosmaitaideally the entries for servers in the index would contain only permanent info about images, probably just uuid15:51
*** Abhinav has joined #openstack-meeting-415:51
rosmaitabut, what happens if hte image is deleted?15:51
rosmaitamuch sadness15:51
nikhil_k:)15:51
sjmc7one option is we don't try to answer this15:51
nikhil_k++15:51
*** TheIntern has quit IRC15:51
sjmc7and we don't have image name, flavor name indexed with servers15:51
nikhil_krosmaita: I think it's worth having deleted images in ES index15:52
sjmc7but that makes the searching much less impressive15:52
sjmc7images that are deleted get deleted15:52
* TravT misses relational joins sometimes.15:52
*** ivar-lazzaro has joined #openstack-meeting-415:52
lakshmiSwell there are parent child relationships in ES we can explore15:52
nikhil_kwell I think we are going too far away. whatever we do it might be worth keep some options open for changing design later15:53
rosmaitalakshmiS: that sounds cool15:53
lakshmiShttps://www.elastic.co/blog/managing-relations-inside-elasticsearch15:53
*** Abhinav has quit IRC15:53
nikhil_klakshmiS: are there horizontal inheritance capabilities, I might be thinking something crazy to do here but it might work15:54
nikhil_k?15:54
sjmc7for the sake of getting something working then, that is an option - don't try to denormalize now15:54
nikhil_kcool15:54
TravTi'm okay with that as starting point, i think.15:54
nikhil_ksjmc7: works for me for now15:54
TravTbut we can talk through queries further15:54
sjmc7ok. it does mean that cross-resource searching will be largely not-useful, i think15:54
nikhil_kfor now15:55
nikhil_k:)15:55
TravTthe parent child isn't for nesting virtual docs, i think.15:55
TravTi mean if image is index as a doc in index a type b15:55
TravTthe instance can't contain it as a reference, i thought.15:56
sjmc7i would urge us to stay away from it15:56
TravTok... so, we won't have it in first pass.15:56
TravTrunning out of time.15:57
TravTthe doc type review takes a little thought.15:57
TravTso also please look at that one.15:57
TravTi already added some comments15:57
*** ivar-laz_ has joined #openstack-meeting-415:57
TravThttps://review.openstack.org/#/c/207672/15:57
sjmc7thanks, will take a look today15:58
sjmc7other comments welcome15:58
TravTand finally, designate plugin.15:58
sjmc7yeah, let's get that in as well15:58
rosmaitai thought they were all hidden since they are in instance_system_metadata table15:58
sjmc7i haven't tested ekarlso's latest patch15:58
TravTi did seem to finally get a working devstack with designate so that i could have some intelligence when reviewing the patch.15:58
TravTbut yesterday got clobbered with meetings.15:59
lakshmiSlakshmiS is stilly unlucky with devstack install for designate15:59
TravT#topic 12 seconds of open discussion15:59
*** openstack changes topic to "12 seconds of open discussion (Meeting topic: openstack search)"15:59
*** mattymo_ has left #openstack-meeting-415:59
*** ivar-lazzaro has quit IRC15:59
sjmc7:)  think we covered everything i wanted to15:59
nikhil_k:)15:59
*** TheIntern has joined #openstack-meeting-415:59
*** yamahata has joined #openstack-meeting-415:59
*** odyssey4me has joined #openstack-meeting-416:00
TravTokay, that's it.  thanks everybody16:00
nikhil_kTHanks!16:00
TravT#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Thu Aug  6 16:00:16 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-08-06-15.01.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-08-06-15.01.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-08-06-15.01.log.html16:00
odyssey4me#startmeeting OpenStack Ansible Meeting16:00
openstackMeeting started Thu Aug  6 16:00:57 2015 UTC and is due to finish in 60 minutes.  The chair is odyssey4me. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: OpenStack Ansible Meeting)"16:00
openstackThe meeting name has been set to 'openstack_ansible_meeting'16:01
*** evrardjp has joined #openstack-meeting-416:01
*** lakshmiS has left #openstack-meeting-416:01
*** rromans has joined #openstack-meeting-416:01
odyssey4me#topic Agenda & rollcall16:01
*** openstack changes topic to "Agenda & rollcall (Meeting topic: OpenStack Ansible Meeting)"16:01
*** b3rnard0 has joined #openstack-meeting-416:01
*** sjmc7 has left #openstack-meeting-416:01
*** stevelle has joined #openstack-meeting-416:02
serverascodeo/16:02
odyssey4memorning/afternoon/evening everyone16:02
ApsuMorning16:02
b3rnard0hello16:02
palendaeMorning16:02
*** prometheanfire has joined #openstack-meeting-416:02
prometheanfiremoin16:03
stevellehellos16:03
evrardjphello16:03
*** belmoreira has quit IRC16:03
odyssey4me#topic Review action items from last week16:05
*** openstack changes topic to "Review action items from last week (Meeting topic: OpenStack Ansible Meeting)"16:05
*** cfarquhar has joined #openstack-meeting-416:05
odyssey4mesigmavirus24 I saw the mail thread, but didn't see anyone weight in on it except me :/16:05
*** wokuma has left #openstack-meeting-416:05
*** Sam-I-Am has joined #openstack-meeting-416:05
odyssey4methanks for doing that though16:06
*** wko has quit IRC16:06
odyssey4mecan others please weigh in?16:06
*** hogepodge has quit IRC16:06
odyssey4meACTION: sigmavirus24 and cloudnull to put together a POC for pip and epoch's16:06
*** afv has joined #openstack-meeting-416:06
odyssey4mesigmavirus24 how's that going?16:07
*** matrohon has quit IRC16:07
*** hogepodge has joined #openstack-meeting-416:07
odyssey4meok, it seems that'll have to carry16:09
*** geoffarnold has joined #openstack-meeting-416:09
odyssey4me#action sigmavirus24 and cloudnull to put together a POC for pip and epoch's16:09
sigmavirus24sorry16:09
odyssey4meACTION: odyssey4me to move all unassigned juno bugs to the 10.1.12 milestone16:09
sigmavirus24Haven't had time to act on it16:09
odyssey4methat was done16:09
odyssey4mesigmavirus24 no worries, it's not urgent at this stage16:10
odyssey4meACTION: odyssey4me to move all unassigned and not yet 'in-progress' kilo bugs to the 11.1.1 milestone16:10
odyssey4methat was also done16:10
odyssey4me#topic Blueprints16:10
*** openstack changes topic to "Blueprints (Meeting topic: OpenStack Ansible Meeting)"16:10
odyssey4me#link https://blueprints.launchpad.net/openstack-ansible/+spec/ceph-block-devices16:10
odyssey4meso a patch for this has merged to master, and we have yet to release 11.1.0, so some discussion has been had around backporting this16:11
odyssey4meany thoughts?16:11
odyssey4mesvg evrardjp git-harry ?16:11
odyssey4memattt ^16:12
evrardjpmm16:12
*** TravT has left #openstack-meeting-416:12
evrardjpI'll let the others talk: I'm only starting to test it16:12
odyssey4methe question is whether it's gone through enough testing - I know that mattt and git-harry had reservations and think it should stay on the 11.2.0 milestone16:12
odyssey4meunfortunately they're not here to discuss it16:13
*** echoingumesh has joined #openstack-meeting-416:13
evrardjpwhen has the decision to be taken?16:13
odyssey4mewell, it seems that we'll have to carry that decision and it all depends on when 11.1.0 gets released, which is an agenda point later16:14
odyssey4mebut based on what I'm seeing in the channel discussions I think it may be best to leave on the 11.2.0 milestone16:14
*** sdake has quit IRC16:14
odyssey4meany thoughts from anyone?16:14
*** TheIntern has quit IRC16:15
evrardjpat least waiting for svg and git-harry input would be wise16:15
evrardjpso if you can't have it now, let's postpone the merge to kilo?16:15
odyssey4meyeah, neither are in the channel - so we'll carry the decision16:16
odyssey4me#topic reviews16:16
*** openstack changes topic to "reviews (Meeting topic: OpenStack Ansible Meeting)"16:16
odyssey4me#link https://review.openstack.org/#/q/starredby:%22Jesse+Pretorius%22+project:stackforge/os-ansible-deployment,n,z16:16
odyssey4meI have found a cause for the master branch being stuck.16:16
odyssey4mehttps://review.openstack.org/209998 should fix it16:16
odyssey4mehttps://launchpad.net/bugs/1482260 explains the bug in detail16:17
openstackLaunchpad bug 1482260 in openstack-ansible trunk "python-zaqarclient has incompatible requirements with oslo.middleware" [High,In progress] - Assigned to Jesse Pretorius (jesse-pretorius)16:17
*** vikram_ has quit IRC16:17
odyssey4mesigmavirus24 palendae please review https://review.openstack.org/209998 asap - just vote, no workflow for now until the gate check passes16:18
*** abhisri has joined #openstack-meeting-416:18
*** SourabhP has joined #openstack-meeting-416:18
odyssey4meas for the rest of the starred reviews, we're not meeting the 11.1.0 deadline, so either we shift the deadline again or we shift the blueprints not yet merged to the 11.2.0 milestone16:19
odyssey4methoughts?16:19
evrardjpit doesn't serve to always postpone right?16:19
odyssey4meevrardjp yeah, we need to release so that we can continue to push forward with patch releases16:20
stevelleI'm leaning towards shifing to 11.2.16:20
odyssey4mewe have a build-up of bugs and fixes for them which need to get in16:20
stevelleagreed16:20
odyssey4meunfortunately it seems that we don't have a quorum of cores here, so the decision will have to wait :/16:21
odyssey4mepalendae sigmavirus24 any thoughts before we move on?16:22
sigmavirus24sorry I'm very distracted16:22
*** s3wong has joined #openstack-meeting-416:22
palendaeI'd be fine with moving some blueprints to 11.216:22
sigmavirus24I want at least the SP patch into 11.1016:22
*** SourabhP_ has joined #openstack-meeting-416:22
sigmavirus24*11.1.016:22
sigmavirus24Other things make sense for 11.216:22
*** IlyaG has joined #openstack-meeting-416:23
sigmavirus24Is master unblocked yet for the SP patch?16:23
odyssey4mesigmavirus24 it may be after the above-mentioned patch16:23
*** SourabhP has quit IRC16:24
*** SourabhP_ is now known as SourabhP16:24
odyssey4mepalendae sigmavirus24 note that https://review.openstack.org/201136 has been thoroughly tested by miguelgrinberg and stevelle so we're needing a final vote there to get https://blueprints.launchpad.net/openstack-ansible/+spec/multi-region-swift through16:24
sigmavirus24Yeah I'd like to test that but I think that might need to be targetted to 11.216:24
*** echoingumesh has quit IRC16:25
odyssey4memost importantly the end-user experience is not changed for any currently supported swift deployment16:25
evrardjpso ceilometer is the only inclusion in 11.1?16:25
odyssey4meso my vote is to merge it to get it done and open the gate for more thorough testing and minor patches16:26
evrardjpseems a big inclusion already16:26
palendaeodyssey4me: Sure, not changing defaults is good, but I'd like to at least read over it. Supposed lack of enablement isn't necessarily grounds for merge16:27
odyssey4meevrardjp if we stay in this state, yes - that and all the wishlist items, some of which are actually quite significant16:27
*** singlethink has joined #openstack-meeting-416:28
odyssey4mepalendae sure, my concern though is that we've not released anything in kilo for over a month now and we usually release a hotfix every two weeks, so we need to get back to our release cadence16:28
odyssey4meshall we defer until tomorrow to give time to release master and review those patches?16:29
*** kbyrne has quit IRC16:29
*** RedShift has joined #openstack-meeting-416:29
*** RedShift is now known as Guest1396216:29
stevelleThe value of deferring would be to reduce the demands on eyeballs?16:30
stevelleAs they are split between priorities with master being blocked?16:30
*** SourabhP has quit IRC16:30
palendaeodyssey4me: Sure, I get that; not sure I want to release just to release...also unfortunately my time is fairly booked this week =\16:30
*** cfarquhar has quit IRC16:31
odyssey4meok, how about we switch the discussion a bit to help16:31
odyssey4mewhen should we aim to release 11.2.0 ?16:31
stevelleI vote for after 11.1.016:31
odyssey4melol16:31
*** apuimedo has quit IRC16:32
evrardjpif we continue to postpone 11.1.0 that's not gonna be easy ><16:33
*** kbyrne has joined #openstack-meeting-416:33
*** Brian has joined #openstack-meeting-416:33
sigmavirus24== stevelle16:33
evrardjp(to release after 11.1.0 for those who didn't get the joke)16:34
*** vivek-eb_ has joined #openstack-meeting-416:34
*** Brian is now known as Guest1127616:34
sigmavirus24why not tag 11.1.0 and 11.2.0 simultaneously?16:34
odyssey4meso the project's cadence has always been to release fast and release often16:34
sigmavirus24just 11.2.0 30 seconds later?16:34
odyssey4meat least for hotfix releases16:34
stevellejoking aside, this project has maintained a cadence of putting fixes out to the community quickly, and maintained the principle that version numbers are cheap. we already pushed a deadline and it didn't give us any reward so I would like to revert to prior behavior.16:34
*** cfarquhar has joined #openstack-meeting-416:35
palendaeSo we're +2ing just to get a release16:35
evrardjp11.1 includes ceilometer, that deserves a release alone (just my opinion)16:35
odyssey4meliberty will hit feature freeze in Sep16:35
odyssey4meso I vote for releasing 11.1.0 this week (tomorrow) and anything that's not in yet can release with 11.2.0 which we should plan to release at the end of Aug IMO16:36
palendaeI'm fine with that16:36
evrardjp+116:36
odyssey4meend Aug - mid Sep - somewhere around there, giving us perhaps 3 hotfix releases before then16:36
evrardjpppl would still have the time to give their opinion16:36
*** vivek-ebay has quit IRC16:37
*** Guest13962 has quit IRC16:37
odyssey4meok, we'll aim to release 11.1.0 tomorrow and jump back into the hotfix cadence16:37
*** Guest11276 has quit IRC16:38
odyssey4mewhatever is already in, will be in and whatever doesn't make it can go forward into a hotfix or 11.2.016:38
*** vivek-eb_ has quit IRC16:38
*** jmcbride has joined #openstack-meeting-416:38
odyssey4me#topic Open Discussion16:38
*** openstack changes topic to "Open Discussion (Meeting topic: OpenStack Ansible Meeting)"16:38
sigmavirus24so long as SP doesn't land in a hot fix16:38
odyssey4meis there anything anyone wants to raise?16:38
odyssey4mesigmavirus24 agreed16:38
odyssey4me#action odyssey4me to release 11.1.0 on 7 Aug 2015, any blueprints not yet merged to be postponed to 11.2.016:39
*** jmckind has quit IRC16:39
palendaeReally the issue we're having right now is the majority of cores are on vacation/holiday, and the rest are being pulled into internal work16:40
odyssey4me#action odyssey4me to set 11.2.0 release date to the (tentative) date of 4 Sep16:40
*** sbalukoff has quit IRC16:40
evrardjppalendae: when is the return from holidays?16:40
palendaeevrardjp: They're all different16:40
odyssey4meevrardjp we have three returning next week I think16:41
Sam-I-Amnothing is happening with the wedged gate :/16:42
*** yamamoto has quit IRC16:42
*** qwebirc63773 has joined #openstack-meeting-416:42
odyssey4meSam-I-Am we're waiting for gate results, but https://review.openstack.org/209998 should unwedge it16:42
Sam-I-Amodyssey4me: cool16:42
*** puranamr has joined #openstack-meeting-416:42
odyssey4meI'm still having issues with bumping SHA's in master though - something seems to have changed upstream that's breaking our AIO network config16:43
odyssey4meinstances are not getting DHCP16:43
*** abhisriatt has joined #openstack-meeting-416:43
Sam-I-Amwouldnt surprise me if neutron is beoken16:43
Sam-I-Amshould see if the neutron gates are passing16:44
Sam-I-Amneutron broke kilo for a while too16:44
odyssey4meSam-I-Am Apsu I could do with some help with that, but that may have to wait until next week as I know you guys are tied up with other work right now16:44
Sam-I-Amthe old l2pop problem that blocked our release16:44
odyssey4meSam-I-Am we can chat after the meeting, perhaps you can help me figure it out16:44
Sam-I-Ami have another meeting after this meeting, then more meetings16:45
Sam-I-Ambut you dont sleep, so we're good16:45
ApsuSam-I-Am sounds like your guy16:45
Sam-I-Ami just need to kick a box16:45
odyssey4mealright, if that's all then we can move to the channel for other discussions :)16:45
odyssey4methank you all for attending, even with your busy schedules16:46
odyssey4me#endmeeting16:46
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:46
openstackMeeting ended Thu Aug  6 16:46:05 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:46
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-08-06-16.00.html16:46
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-08-06-16.00.txt16:46
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-08-06-16.00.log.html16:46
*** stevelle has left #openstack-meeting-416:47
*** odyssey4me has left #openstack-meeting-416:47
*** singleth_ has joined #openstack-meeting-416:49
*** MaxKlyus has joined #openstack-meeting-416:51
*** Sam-I-Am has left #openstack-meeting-416:52
*** vikram_ has joined #openstack-meeting-416:52
*** qwebirc16464 has joined #openstack-meeting-416:52
*** singlethink has quit IRC16:53
*** qwebirc63773 has quit IRC16:53
*** cfarquhar has quit IRC16:54
*** rromans has left #openstack-meeting-416:55
*** LouisF has joined #openstack-meeting-416:57
*** qwebirc26030 has joined #openstack-meeting-416:57
*** vivek-ebay has joined #openstack-meeting-416:57
*** johnsom has joined #openstack-meeting-416:59
*** cathy_ has joined #openstack-meeting-417:00
LouisFhi17:00
s3wonghello17:00
cathy_#startmeeting service_chaining17:01
openstackMeeting started Thu Aug  6 17:01:17 2015 UTC and is due to finish in 60 minutes.  The chair is cathy_. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:01
*** openstack changes topic to " (Meeting topic: service_chaining)"17:01
openstackThe meeting name has been set to 'service_chaining'17:01
cathy_hello everyone17:01
johnsomo/17:01
*** xiaodongwang has joined #openstack-meeting-417:01
vikram_Hi17:01
pcarverhi17:01
abhisriatthi, this is abhinav.17:01
abhisriattfrom AT&T Research.17:01
s3wongabhisriatt: welcome to the meeting17:02
*** jmcbride has quit IRC17:02
cathy_abhisriatt: hi, welcome to the meeitng17:02
pcarverThanks for joining us Abhinav17:02
LouisFi have posted update to https://review.openstack.org/#/c/204695 API doc17:02
abhisriattThanks Guys.17:02
*** Brian___ has joined #openstack-meeting-417:02
pcarvercathy_: Abhinav is one of the people I mentioned who has worked on the flow steering work internally at AT&T17:02
cathy_pcarver: great17:03
xiaodongwanghi17:03
Brian___hi all17:03
cathy_so maybe today we can have abhisriatt give a instrocution on the flow steering work at AT&T?17:03
cathy_Brian___: xiaodongwang Hi17:03
LouisFand also https://review.openstack.org/#/c/207251 Port Chain API and DB17:04
LouisFhi xiaodongwang17:04
*** afv has quit IRC17:04
MaxKlyushi from NetCracker research group17:04
LouisFhi MaxKlyus17:05
cathy_Louis has posted an update to the API doc. I saw some new comments. Could everyone please review the latest one and give all your comments so that we can get them addressed and merged?17:05
cathy_MaxKlyus: Hi, welcome!17:05
s3wongMaxKlyus: welcome to the meeting!17:05
LouisFcathy_: yes vikram had some more comments I will post a new patch later today to address them17:06
*** afv has joined #openstack-meeting-417:06
vikram_LouisF: I have few more :-)17:06
cathy_LouisF: I saw that Jenkins -1 on https://review.openstack.org/#/c/207251.17:06
cathy_LouisF: Thanks!17:06
LouisFcathy_: yes still some pep8 issues17:06
LouisFcathy_: will ork through them today17:07
cathy_vikram_: could you please post them today so that Louis can address them all in one shot ?17:07
LouisFwork17:07
cathy_LouisF: Thanks!17:07
cathy_While Louis fixes the pep8 issue, everyone can start review the "Port Chain API and DB" codes please.17:09
vikram_cathy_: sure17:09
cathy_vikram_: thanks! BTW, I remember you previously signed up on the Horizon part code support for this project. How is that working going?17:10
s3wongcathy_: yes17:10
*** b3rnard0 has left #openstack-meeting-417:10
cathy_s3wong: thanks.17:10
*** harshs has joined #openstack-meeting-417:11
vikram_cathy_: I think we got to finalize the API's + Server code is needed for testing..17:11
vikram_cathy_: Framework is done17:12
cathy_Also could everyone get on the OVS Driver and Agent  spec and do a detail review of it? https://review.openstack.org/#/c/208663/17:12
s3wongcathy_: sure17:13
abhisriattcathy_:sure17:13
cathy_vikram_: Agree with you. But I will not expect much change on the API side. So to speed up the coding work, we cna do this in parallel. I expect the API will be merged soon. What do you think?17:13
cathy_s3wong: abhisriatt thanks.17:14
vikram_cathy_: +1, we are doing it .. My only concern is getting the API's finalisied soon.. It's impacting both horizon and CLI17:14
*** jwarendt has joined #openstack-meeting-417:14
cathy_vikram_: Sure. Agree with you.17:15
cathy_vikram_: Thanks for starting the coding work.17:15
*** cfarquhar has joined #openstack-meeting-417:15
*** VW_ has quit IRC17:16
cathy_vikram_: so you will post all your comments today and Louis will address all comments and post a new version for final review. Let's get the API finalized as soon as possible so that it will not impact other pieces of work17:16
*** VW_ has joined #openstack-meeting-417:16
vikram_cathy_: Sure. Will do!17:16
LouisFcathy_: will do17:16
cathy_vikram_: LouisF Thanks, folks!17:17
cathy_Any other topic you have in mind?17:17
abhisriattcathy_:if you want, I can give you brief overview of our work done in AT&T on flow steering.17:17
cathy_abhisriatt: sure, please go ahead17:18
abhisriattThe flow steering project that we started in Research was to give control to deploy Tenant-defined middle-boxes to give mor control to cloud tenants.17:19
abhisriattsorry..to give contro to tenants to deploy middlebox of their choice.17:19
LouisFabhisriatt: middleboxes being service functions?17:21
*** VW_ has quit IRC17:21
abhisriattThe idea is that tenants will request some services, especially security services firewall, IDS, IPS, etc., that will run inside MBs.17:21
abhisriattLouisF: Yes, like  firewall, IDS, IPS, etc.17:21
LouisFabhisriatt: ok17:22
*** Mohankumar__ has joined #openstack-meeting-417:22
abhisriattThe cloud provider’s job is to accept the request from tenants and setup the networking pipes in a way that packets should flow through these MBs.17:23
LouisFabhisriatt: so it is possible to steer traffic to these service?17:23
*** cfarquhar has quit IRC17:23
abhisriattLouisF: Yes.17:23
*** yamahata has quit IRC17:24
Mohankumar__sorry for joining late17:24
cathy_Mohankumar__: it is oK17:24
*** yamahata has joined #openstack-meeting-417:24
cathy_abhisriatt: This requirement is what service chain project can provide17:24
pcarverIf I can give a little more detail, the AT&T work originally started out doing QoS (DSCP bit manipulation) in OvS using an external service that integrated with OpenStack APIs.17:25
pcarverAbhinav's work was to then extend that framework to do flow steering which is basically the same intent as service chaining17:25
abhisriattOur APIs or CLIs are simple and in the form of: Source (VM or external traffic), destination VM (or any local VM), MB1, MB2,… MBn17:25
cathy_abhisriatt: Your APIs are very similar to the API of the service chain project.17:26
*** cfarquhar has joined #openstack-meeting-417:26
abhisriatti.e. any traffic from source to destination should flow through these set of MBs.17:26
abhisriattcathy_: Yes. that’s why pcarver asked me to join this work..17:27
LouisFabhisriatt: looks like close alignment with the port-chain apis17:27
pcarverWe've worked through the prototype stage and have some experience with the necessary OvS flowmods required17:27
cathy_pcarver: great.17:27
LouisFpcarver: excellent please jump in on suggestions on the ovs driver and agent17:28
pcarverThe implementation wasn't conceived as a part of OpenStack, but rather sitting outside and interacting with Nova, Neutron, and Keystone, as well as interacting directly with OvS17:28
abhisriattLouisF: Yes, and we are actually designing new set of APIs that actually look very similar to what you guys have on the wiki.17:28
pcarverThe networking-sfc work differs mainly in being a part of OpenStack rather than sitting slightly outside of it17:28
pcarverBut with both the QoS and flow steering we've had some experience with how to manipulate OvS flow mods without disrupting Neutron's use of OvS17:29
*** rods_ has joined #openstack-meeting-417:29
abhisriattAs Paul mentioned, we extensively used OVS flow mods to route packets from one MB to other without disrupting any existing flows or traffic.17:30
LouisFabhisriatt: that is exactly what we need to do for port-chains17:30
cathy_pcarver: "OVS flowmods" refer to the interface between OVS Agent and OVS on the same computing node or  OVS driver on Neutron Server and OVS Agent on the Computing node?17:30
pcarverMy thinking is that we should model the networking-sfc interactions with OvS after the networking-qos interactions, but that we can leverage some of Abhinav's and other AT&T folks experience17:31
LouisFabhisriatt: do you support ant form of load distribution across a set of MBs in a port-group17:31
pcarvercathy_: yes, flowmod meaning the "magic incantations" that we need to put into OvS to make things happen17:31
LouisFany ^17:31
cathy_abhisriatt: Yes, our design on the data path flow steering is similar to yours: route packets from one MB to other without disrupting any existing flows or traffic.17:31
abhisriattcathy_: flowmods are nothing but open flow rules that are inserted in OVS.17:32
abhisriattLouisF: We are currently working on load balancing across MBs, and we call it scalable flow steering.17:32
*** cfarquhar has quit IRC17:33
pcarverIn our implementation the thing that puts the flowmods into OvS is an independent server process outside of Neutron and doesn't use any Neutron agents17:33
*** sdake has joined #openstack-meeting-417:33
abhisriattHere again, we are using Open flow features such as multipath, learning rules to load balance across many MBs.17:34
pcarverBut I think it should be adaptable, at least the underlying building blocks17:34
abhisriattpcarver:Yes.17:34
LouisFabhisriatt: https://review.openstack.org/#/c/208663 descibes OF group-mod for doing load balancing across a group17:34
*** salv-orlando has quit IRC17:35
LouisFabhisriatt: suggestions welcome17:35
cathy_pcarver: agree with you, I think this project can leverage your OVS flow table part can17:35
abhisriattLouisF: sure, I will take a look at.17:35
*** tfukushima has quit IRC17:36
*** xiaodongwang has quit IRC17:36
cathy_Instead of using an external server process to program the OVS, in our project the path will be OVS Driver on Neutron server talking with OVS Agent and the OVS Agent programming the OVS via openflow commands17:37
*** qwebirc16464 has quit IRC17:37
*** tfukushima has joined #openstack-meeting-417:37
abhisriattcathy_: Ideally, that should be the design.17:37
cathy_abhisriatt: Louis has posted the link which described the design. Could you get on that and give your input and comments?17:38
abhisriattHowever, we started this project with QoS and the OVS agent cannot create queues in OVS. That’s why we have to use an external process to achieve that.17:38
*** VW_ has joined #openstack-meeting-417:38
*** tfukushima has quit IRC17:39
cathy_abhisriatt: could you clarify what you mean by "can not create queues in OVS"? What are the queues used for?17:39
*** ivar-laz_ has quit IRC17:39
*** puranamr has quit IRC17:39
abhisriattcathy_: to rate limit the flows—a functionality needed by the bandwidth reservation project.17:40
*** qwebirc26030 has quit IRC17:40
pcarvercathy_: That's some of the history I referenced briefly. The AT&T flow steering work was built on top of a QoS project. That piece of it isn't especially relevant to networking-sfc project, but was just the framework that we started with17:40
cathy_abhisriatt: so that is related to your QoS funcitonality, right?17:40
abhisriattcathy_:yes. not related to networking-sfc.17:41
cathy_pcarver: Yes, that is what i think. This part is not relevant to the service chaining feature itself17:41
pcarverSince the OpenStack networking-qos work is proceeding independently we don't really need to focus on that part17:41
cathy_pcarver: cool. we are in sync17:41
*** cfarquhar has joined #openstack-meeting-417:42
pcarverEssentially we had an existing server framework that handled Neutron, Nova, and Keystone interaction and Abhinav worked on adding flow steering via OvS flowmods into that existing QoS framework17:42
cathy_abhisriatt: pcarver when do you think you can carve out the OVS part of codes for use in networking-sfc project?17:42
*** yamamoto has joined #openstack-meeting-417:42
abhisriattBTW, we made our controller open source.17:43
abhisriatthttps://github.com/att/tegu17:43
*** ivar-lazzaro has joined #openstack-meeting-417:43
*** marcusvrn has quit IRC17:43
pcarvercathy_: I think the first step is to get Abhinav aligned on which existing reviews are touching the OvS agent and which pieces are currently just stubbed out or don't exist at all17:43
cathy_abhisriatt: OK, thanks.17:43
*** puranamr has joined #openstack-meeting-417:43
s3wongabhisriatt: Go code!17:43
*** markvoelker has quit IRC17:44
cathy_s3wong: :-)17:44
abhisriatt:)17:44
abhisriattActually, it is written in “GO”, too.17:44
cathy_pcarver: Ok, let's do that first. Thanks for bringing in abhisriatt !17:44
pcarverHe needs to get oriented on the structure of the networking-sfc code base and then he can start bringing in his experience from Tegu (that's the name of our server)17:45
s3wongabhisriatt: that's what I meant: code in Go :-)17:45
abhisriattokay :)17:45
cathy_pcarver: sure.17:46
pcarverI haven't been through all the reviews yet. Has anyone started touching OvS or is it all still stubs at this time?17:46
*** yamamoto has quit IRC17:47
*** VW__ has joined #openstack-meeting-417:47
s3wongpcarver: I started to look at it --- but in gerrit review (not merged yet), the dummy driver (stub) is all there is17:47
cathy_pcarver: still stubs. But we are working on the codes now17:47
LouisFpcarver: driver manager and dummy driver only17:48
pcarvercathy_: Ok, we need to get Abhinav sync'd up so that he doesn't do duplicate work17:48
cathy_Let's get the design reviewed and agreed first. Then we can start posting codes and review the codes.17:48
vikram_+117:48
cathy_pcarver: yes, I am thinking we cna divide the coding work among us.17:48
*** TheIntern has joined #openstack-meeting-417:49
cathy_s3wong: has also signed on the the OVS part of code development. Actually the design posted is co-authored with s3wong17:49
s3wongyes17:49
cathy_s3wong: Thanks for your insight and comtributiont!17:50
cathy_contribution!17:50
*** VW_ has quit IRC17:51
*** cfarquhar has quit IRC17:51
s3wongpcarver, abhisriatt: please review the OVS driver spec and we will iterate the design from there17:51
pcarvers3wong: will do17:52
abhisriatts3wong: will do17:52
cathy_As for the coding part, I am thinking someone should get a basic OVS  framework code and then we can have a meeting to review the framework and then divide the detail code development work among us?17:52
*** padkrish has joined #openstack-meeting-417:52
s3wongcathy_: framework? as in the OVS driver on Neutron server?17:53
cathy_Ok with this or any other suggestion how we avoid duplicate work as vikram_ pointed out?17:53
cathy_s3wong: by framework I mean OVS driver on Neutron server, OVS agent on compute node, and OVS itself on Compute node17:54
s3wongcathy_: that's everything :-)17:54
*** SumitNaiksatam has joined #openstack-meeting-417:54
cathy_I think we might need a consistent framework without much coding detail so that we each of us start coding, we do not have big mismatch17:55
MaxKlyussorry I have an open question to everybody, what do you think about OVS mpls based traffic chaining?17:55
cathy_s3wong: no code detail, just framework:-)17:55
LouisFMaxKlyus: various drivers can be used17:56
pcarverMaxKlyus: raw MPLS or MPLS over GRE or UDP?17:56
MaxKlyusraw MPLS multiple stack17:56
*** bharath has joined #openstack-meeting-417:56
pcarverWe're definitely thinking about MPLS, but pretty much orthogonal to service chaining17:57
cathy_MaxKlyus: we are running out of time. Maybe we cna discuss this in the next meeting. I think out framework should be able to support multiple transport and encap in the data path17:57
s3wongor move discussion to openstack-neutron17:57
MaxKlyusit will be great17:58
cathy_MaxKlyus: good question. We can discuss it in the next meeting or on openstack-neutron. Actually this question was touched before in the original API review.17:58
*** echoingumesh has joined #openstack-meeting-417:58
*** VW__ has quit IRC17:59
abhisriattOne last question: how are you guys thinking of steering flows from one MB to another.17:59
cathy_OK, folks. Thanks for joining the meeting and all the discussions. I think we are making good progress! Let's continue the discussion in next meeting.18:00
cathy_bye now18:00
LouisFby18:00
s3wongabhisriatt: a chain of two Neutron ports?18:00
*** VW_ has joined #openstack-meeting-418:00
*** padkrish has quit IRC18:00
abhisriattyes18:00
s3wongOK. Thanks guys!18:00
abhisriattbye18:00
cathy_abhisriatt: wera re running out of time, let address that in next meeting.18:00
abhisriattcathy_:okay18:00
Mohankumar__bye18:00
MaxKlyusok18:00
vikram_bye18:01
MaxKlyusthanks a lot18:01
*** padkrish has joined #openstack-meeting-418:01
MaxKlyusbye18:01
cathy_#stopmeeting18:01
s3wongendmeeting?18:01
*** padkrish has quit IRC18:01
cathy_#endmeeting18:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:01
openstackMeeting ended Thu Aug  6 18:01:25 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/service_chaining/2015/service_chaining.2015-08-06-17.01.html18:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/service_chaining/2015/service_chaining.2015-08-06-17.01.txt18:01
openstackLog:            http://eavesdrop.openstack.org/meetings/service_chaining/2015/service_chaining.2015-08-06-17.01.log.html18:01
cathy_s3wong: :-)18:01
*** padkrish has joined #openstack-meeting-418:01
*** johnsom has left #openstack-meeting-418:02
*** tfukushima has joined #openstack-meeting-418:04
*** markvoelker has joined #openstack-meeting-418:05
*** irenab has joined #openstack-meeting-418:12
*** abhisriatt has quit IRC18:12
*** jmcbride has joined #openstack-meeting-418:12
*** abhisri has quit IRC18:15
*** apuimedo has joined #openstack-meeting-418:17
*** Brian___ has quit IRC18:18
*** Sukhdev has joined #openstack-meeting-418:20
*** daneyon has quit IRC18:20
*** daneyon has joined #openstack-meeting-418:20
*** RedShift has joined #openstack-meeting-418:24
*** RedShift is now known as Guest2473418:24
*** Guest24734 has quit IRC18:29
*** prometheanfire has left #openstack-meeting-418:34
*** cathy_ has quit IRC18:35
*** vikram_ has quit IRC18:36
*** irenab has quit IRC18:36
*** salv-orlando has joined #openstack-meeting-418:37
*** LouisF has quit IRC18:43
*** salv-orlando has quit IRC18:44
*** puranamr has quit IRC18:45
*** lakshmiS has joined #openstack-meeting-418:45
*** jmcbride has quit IRC18:47
*** jmcbride has joined #openstack-meeting-418:47
*** Mohankumar__ has quit IRC18:49
*** xingchao has joined #openstack-meeting-418:51
*** padkrish has quit IRC18:53
*** jmckind has joined #openstack-meeting-418:53
*** padkrish has joined #openstack-meeting-418:54
*** MaxKlyus has quit IRC18:55
*** lakshmiS has quit IRC18:58
*** padkrish has quit IRC18:58
*** tfukushima has quit IRC19:04
*** harshs has quit IRC19:05
*** cfarquhar has joined #openstack-meeting-419:06
*** puranamr has joined #openstack-meeting-419:06
*** padkrish has joined #openstack-meeting-419:08
*** dahoo has joined #openstack-meeting-419:08
*** dahoo is now known as jerryz19:08
*** abhisriatt has joined #openstack-meeting-419:13
*** xingchao has quit IRC19:14
*** padkrish has quit IRC19:17
*** padkrish has joined #openstack-meeting-419:17
*** padkrish has quit IRC19:18
*** padkrish_ has joined #openstack-meeting-419:18
*** padkrish_ has quit IRC19:22
*** padkrish has joined #openstack-meeting-419:22
*** harshs has joined #openstack-meeting-419:24
*** harshs has quit IRC19:25
*** padkrish has quit IRC19:26
*** padkrish has joined #openstack-meeting-419:28
*** padkrish has quit IRC19:29
*** padkrish has joined #openstack-meeting-419:29
*** numan has quit IRC19:30
*** puranamr has quit IRC19:31
*** abhisriatt_ has joined #openstack-meeting-419:31
*** singleth_ has quit IRC19:32
*** armax has quit IRC19:32
*** abhisriatt_ has quit IRC19:33
*** abhisriatt has quit IRC19:34
*** padkrish has quit IRC19:39
*** singlethink has joined #openstack-meeting-419:43
*** irenab has joined #openstack-meeting-419:46
*** salv-orlando has joined #openstack-meeting-419:47
*** jmcbride has quit IRC19:49
*** puranamr has joined #openstack-meeting-419:50
*** salv-orlando has quit IRC19:51
*** cfarquhar has quit IRC19:56
*** jmcbride has joined #openstack-meeting-419:57
*** TheIntern has quit IRC20:00
*** jmcbride has quit IRC20:01
*** jmcbride has joined #openstack-meeting-420:03
*** jmcbride has quit IRC20:03
*** cfarquhar has joined #openstack-meeting-420:04
*** ivar-lazzaro has quit IRC20:04
*** ivar-lazzaro has joined #openstack-meeting-420:09
*** cfarquhar has quit IRC20:09
*** Brian has joined #openstack-meeting-420:09
*** VW_ has quit IRC20:09
*** Brian is now known as Guest9170820:09
*** VW_ has joined #openstack-meeting-420:09
*** Guest91708 has quit IRC20:13
*** afv has quit IRC20:13
*** VW_ has quit IRC20:14
*** ivar-lazzaro has quit IRC20:14
*** xingchao has joined #openstack-meeting-420:15
*** rods_ is now known as rods20:18
*** IlyaG has quit IRC20:18
*** xingchao has quit IRC20:20
*** Sukhdev has quit IRC20:20
*** dims_ has joined #openstack-meeting-420:23
*** dims_ has quit IRC20:24
*** dims_ has joined #openstack-meeting-420:25
*** dims has quit IRC20:26
*** jmcbride has joined #openstack-meeting-420:26
*** echoingumesh has quit IRC20:27
*** echoingumesh has joined #openstack-meeting-420:28
*** jmckind_ has joined #openstack-meeting-420:28
*** jmckind has quit IRC20:32
*** echoingumesh has quit IRC20:32
*** jmckind_ has quit IRC20:33
*** cfarquhar has joined #openstack-meeting-420:37
*** cfarquhar has quit IRC20:38
*** jmckind has joined #openstack-meeting-420:38
*** cfarquhar has joined #openstack-meeting-420:39
*** RedShift has joined #openstack-meeting-420:42
*** RedShift is now known as Guest2441120:42
*** echoingumesh has joined #openstack-meeting-420:46
*** salv-orlando has joined #openstack-meeting-420:52
*** dannywilson has quit IRC20:54
*** IlyaG has joined #openstack-meeting-420:54
*** dannywilson has joined #openstack-meeting-420:55
*** IlyaG has quit IRC20:56
*** IlyaG has joined #openstack-meeting-420:57
*** salv-orlando has quit IRC21:00
*** cfarquhar has quit IRC21:00
*** radez is now known as radez_g0n321:01
*** rfolco has quit IRC21:02
*** radez_g0n3 is now known as radez21:03
*** britthou_ has quit IRC21:05
*** woodard_ has joined #openstack-meeting-421:07
*** dannywilson has quit IRC21:08
*** dannywilson has joined #openstack-meeting-421:08
*** woodard has quit IRC21:10
*** yamamoto has joined #openstack-meeting-421:10
*** cfarquhar has joined #openstack-meeting-421:11
*** woodard_ has quit IRC21:11
*** VW_ has joined #openstack-meeting-421:13
*** nhairston has quit IRC21:14
*** abhisriatt has joined #openstack-meeting-421:15
*** jmckind has quit IRC21:19
*** yamamoto has quit IRC21:19
*** radez is now known as radez_g0n321:20
*** SumitNaiksatam has quit IRC21:22
*** markvoelker has quit IRC21:22
*** armax has joined #openstack-meeting-421:22
*** harshs has joined #openstack-meeting-421:24
*** cfarquhar has quit IRC21:31
*** belmoreira has joined #openstack-meeting-421:35
*** abhisriatt has quit IRC21:36
*** abhisriatt has joined #openstack-meeting-421:37
*** cfarquhar has joined #openstack-meeting-421:38
*** echoingumesh has left #openstack-meeting-421:38
*** galstrom is now known as galstrom_zzz21:38
*** dannywilson has quit IRC21:39
*** dannywilson has joined #openstack-meeting-421:40
*** carl_baldwin has quit IRC21:41
*** cfarquhar has quit IRC21:42
*** abhisriatt has quit IRC21:47
*** abhisriatt has joined #openstack-meeting-421:47
*** abhisriatt has quit IRC21:49
*** jmcbride has quit IRC21:49
*** armax has quit IRC21:53
*** armax has joined #openstack-meeting-421:54
*** banix has quit IRC21:57
*** SumitNaiksatam has joined #openstack-meeting-421:57
*** delattec has quit IRC21:58
*** salv-orlando has joined #openstack-meeting-421:59
*** klamath has quit IRC22:02
*** ivar-lazzaro has joined #openstack-meeting-422:03
*** salv-orlando has quit IRC22:08
*** jckasper has quit IRC22:13
*** armax has quit IRC22:15
*** yamamoto has joined #openstack-meeting-422:19
*** IlyaG has quit IRC22:22
*** bknudson has quit IRC22:23
*** yamamoto has quit IRC22:25
*** VW_ has quit IRC22:25
*** VW_ has joined #openstack-meeting-422:26
*** VW_ has quit IRC22:30
*** singlethink has quit IRC22:32
*** VW_ has joined #openstack-meeting-422:35
*** VW__ has joined #openstack-meeting-422:36
*** asselin__ has joined #openstack-meeting-422:37
*** puranamr has quit IRC22:38
*** britthouser has joined #openstack-meeting-422:38
*** asselin has quit IRC22:39
*** VW_ has quit IRC22:39
*** VW__ has quit IRC22:40
*** asselin__ has quit IRC22:43
*** dims_ has quit IRC22:50
*** markvoelker has joined #openstack-meeting-422:50
*** radez_g0n3 is now known as radez23:06
*** sc68cal has quit IRC23:09
*** dims_ has joined #openstack-meeting-423:10
*** aventerav has quit IRC23:10
*** abhisriatt has joined #openstack-meeting-423:11
*** sc68cal has joined #openstack-meeting-423:14
*** abhisriatt has quit IRC23:15
*** shalq has quit IRC23:16
*** shalq has joined #openstack-meeting-423:16
*** abhisriatt has joined #openstack-meeting-423:17
*** blahRus has quit IRC23:24
*** Daviey has quit IRC23:25
*** Daviey has joined #openstack-meeting-423:26
*** salv-orlando has joined #openstack-meeting-423:27
*** echoingumesh has joined #openstack-meeting-423:29
*** echoingumesh has quit IRC23:33
*** bknudson has joined #openstack-meeting-423:35
*** sdake has quit IRC23:38
*** bharath has quit IRC23:38
*** VW_ has joined #openstack-meeting-423:40
*** abhisriatt has quit IRC23:44
*** VW_ has quit IRC23:49
*** Sukhdev has joined #openstack-meeting-423:53
*** dannywil_ has joined #openstack-meeting-423:54
*** puranamr has joined #openstack-meeting-423:56
*** dannywilson has quit IRC23:57
*** dannywil_ has quit IRC23:58

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