Thursday, 2015-07-02

*** puranamr has quit IRC00:01
*** puranamr_ has quit IRC00:02
*** puranamr has joined #openstack-meeting-400:03
*** banix has joined #openstack-meeting-400:05
*** xingchao_ has quit IRC00:09
*** Swami has quit IRC00:10
*** banix has quit IRC00:12
*** saneax has quit IRC00:21
*** padkrish has joined #openstack-meeting-400:25
*** puranamr has quit IRC00:28
*** Rockyg has quit IRC00:29
*** SumitNaiksatam has quit IRC00:36
*** Sukhdev has quit IRC00:45
*** carl_baldwin has quit IRC00:53
*** dannywilson has quit IRC01:02
*** trey has joined #openstack-meeting-401:02
*** SumitNaiksatam has joined #openstack-meeting-401:09
*** hughhalf has quit IRC01:10
*** xingchao_ has joined #openstack-meeting-401:13
*** hughhalf has joined #openstack-meeting-401:16
*** hughhalf has quit IRC01:18
*** xingchao_ has quit IRC01:18
*** dims_ has quit IRC01:19
*** hughhalf has joined #openstack-meeting-401:20
*** padkrish has quit IRC01:21
*** sankarshan_away is now known as sankarshan01:25
*** banix has joined #openstack-meeting-401:25
*** armax has quit IRC01:26
*** fallenpegasus has joined #openstack-meeting-401:28
*** s3wong has quit IRC01:33
*** puranamr has joined #openstack-meeting-401:38
*** dims has joined #openstack-meeting-401:39
*** sigmavirus24 is now known as sigmavirus24_awa01:40
*** puranamr has quit IRC01:42
*** carl_baldwin has joined #openstack-meeting-401:42
*** marcusvrn has joined #openstack-meeting-401:55
*** ivar-laz_ has joined #openstack-meeting-401:59
*** ivar-lazzaro has quit IRC02:02
*** ivar-laz_ has quit IRC02:03
*** xingchao_ has joined #openstack-meeting-402:06
*** xingcha__ has joined #openstack-meeting-402:08
*** xingchao_ has quit IRC02:08
*** jwang_ has joined #openstack-meeting-402:18
*** marcusvrn has quit IRC02:19
*** yamahata has quit IRC02:21
*** jwang__ has quit IRC02:21
*** sbalukoff has quit IRC02:22
*** armax has joined #openstack-meeting-402:29
*** catherine_d|1 has joined #openstack-meeting-402:42
*** xingcha__ has quit IRC02:43
*** catherine_d|1 has quit IRC02:43
*** xingchao_ has joined #openstack-meeting-402:46
*** lazy_prince has quit IRC03:18
*** dims has quit IRC03:22
*** VanL has joined #openstack-meeting-403:36
*** xingchao_ has quit IRC03:40
*** DericHorn-HP has joined #openstack-meeting-404:19
*** VanL has quit IRC04:23
*** DericHorn-HP has quit IRC04:23
*** sdake has joined #openstack-meeting-404:30
*** delattec has joined #openstack-meeting-404:43
*** cdelatte has quit IRC04:45
*** nkrinner has joined #openstack-meeting-404:54
*** SumitNaiksatam has quit IRC04:58
*** SumitNaiksatam has joined #openstack-meeting-404:58
*** amit213 has joined #openstack-meeting-405:00
*** amit213 has quit IRC05:00
*** ajayaa has joined #openstack-meeting-405:00
*** amit213 has joined #openstack-meeting-405:00
*** saneax has joined #openstack-meeting-405:06
*** mmedvede has quit IRC05:10
*** carl_baldwin has quit IRC05:12
*** DericHorn-HP has joined #openstack-meeting-405:18
*** saneax has quit IRC05:33
*** saneax has joined #openstack-meeting-405:34
*** DericHorn-HP has quit IRC05:45
*** ivar-lazzaro has joined #openstack-meeting-405:47
*** irenab has quit IRC05:52
*** ivar-lazzaro has quit IRC05:53
*** ivar-lazzaro has joined #openstack-meeting-405:53
*** ivar-lazzaro has quit IRC05:54
*** ivar-lazzaro has joined #openstack-meeting-405:54
*** ivar-lazzaro has quit IRC05:56
*** ivar-lazzaro has joined #openstack-meeting-405:57
*** ivar-lazzaro has quit IRC05:59
*** numan has joined #openstack-meeting-406:00
*** armax has quit IRC06:04
*** banix has quit IRC06:18
*** irenab has joined #openstack-meeting-406:26
*** mandre has left #openstack-meeting-406:32
*** kobis has joined #openstack-meeting-406:41
*** belmoreira has joined #openstack-meeting-406:44
*** radek_ has joined #openstack-meeting-406:45
*** xingchao_ has joined #openstack-meeting-406:47
*** ivar-lazzaro has joined #openstack-meeting-406:47
*** belmoreira has quit IRC06:47
*** ivar-lazzaro has quit IRC06:50
*** belmoreira has joined #openstack-meeting-406:58
*** belmoreira has quit IRC06:58
*** belmoreira has joined #openstack-meeting-406:59
*** matrohon has joined #openstack-meeting-407:13
*** rharwood has quit IRC07:20
*** rharwood has joined #openstack-meeting-407:23
*** lyarwood_ has quit IRC07:34
*** lyarwood has joined #openstack-meeting-407:34
*** jckasper has quit IRC07:36
*** xingchao_ has quit IRC07:38
*** qwebirc24354 has joined #openstack-meeting-407:46
*** qwebirc24354 has quit IRC07:47
*** jckasper has joined #openstack-meeting-407:49
*** jckasper has quit IRC08:11
*** matrohon has quit IRC08:18
*** matrohon has joined #openstack-meeting-408:18
*** GB21 has joined #openstack-meeting-408:21
*** jckasper has joined #openstack-meeting-408:25
*** jckasper has quit IRC08:33
*** jckasper has joined #openstack-meeting-408:45
*** amotoki has quit IRC08:46
*** ajayaa has quit IRC08:53
*** fallenpegasus has quit IRC09:06
*** jpekkari has joined #openstack-meeting-409:20
*** dims has joined #openstack-meeting-409:24
*** bradjones has quit IRC09:33
*** bradjones has joined #openstack-meeting-409:35
*** bradjones has quit IRC09:35
*** bradjones has joined #openstack-meeting-409:35
*** akwasnie has joined #openstack-meeting-409:50
*** ajayaa has joined #openstack-meeting-409:55
*** rfolco has quit IRC10:35
*** marcusvrn has joined #openstack-meeting-411:44
*** lyarwood has quit IRC12:01
*** lyarwood has joined #openstack-meeting-412:01
*** matrohon has quit IRC12:02
*** matrohon has joined #openstack-meeting-412:03
*** rfolco has joined #openstack-meeting-412:13
*** numan has quit IRC12:21
*** marcusvrn has quit IRC12:23
*** marcusvrn has joined #openstack-meeting-412:25
*** GB21 has quit IRC12:27
*** matrohon has quit IRC12:35
*** matrohon has joined #openstack-meeting-412:35
*** nkrinner has quit IRC12:38
*** marcusvrn has quit IRC12:43
*** jpekkari has quit IRC12:44
*** lyarwood has quit IRC12:53
*** lyarwood has joined #openstack-meeting-412:53
*** lakshmiS_ has joined #openstack-meeting-412:55
*** klamath has joined #openstack-meeting-413:02
*** klamath has quit IRC13:03
*** mmedvede has joined #openstack-meeting-413:03
*** klamath has joined #openstack-meeting-413:03
*** marcusvrn has joined #openstack-meeting-413:05
*** matrohon has quit IRC13:06
*** ajmiller__ has joined #openstack-meeting-413:06
*** matrohon has joined #openstack-meeting-413:06
*** ajmiller_ has quit IRC13:10
*** saneax has quit IRC13:23
*** amotoki has joined #openstack-meeting-413:28
*** singlethink has joined #openstack-meeting-413:32
*** Bjoern_ has joined #openstack-meeting-413:42
*** Bjoern_ is now known as BjoernT13:42
*** fallenpegasus has joined #openstack-meeting-413:43
*** gema has left #openstack-meeting-413:43
*** TheIntern has joined #openstack-meeting-413:46
*** TheIntern has left #openstack-meeting-413:46
*** VanL has joined #openstack-meeting-413:50
*** sankarshan is now known as sankarshan_13:51
*** sankarshan_ is now known as sm|CPU13:51
*** sm|CPU is now known as sankarshan13:51
*** VanL has quit IRC13:53
*** singleth_ has joined #openstack-meeting-413:54
*** tsekiyam has joined #openstack-meeting-413:54
*** irenab has quit IRC13:56
*** bpoulos has joined #openstack-meeting-413:56
*** sigmavirus24_awa is now known as sigmavirus2413:56
*** fallenpegasus has quit IRC13:57
*** singlethink has quit IRC13:57
*** puranamr has joined #openstack-meeting-413:58
*** dshakhray has joined #openstack-meeting-413:59
*** llu-laptop has joined #openstack-meeting-413:59
*** TravT has joined #openstack-meeting-414:00
nikhil_k1awayCourtesy 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, abhishekk14:00
*** tsufiev has joined #openstack-meeting-414:00
nikhil_k1away#startmeeting Glance14:00
openstackMeeting started Thu Jul  2 14:00:50 2015 UTC and is due to finish in 60 minutes.  The chair is nikhil_k1away. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
kragnizhihi14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** kbaikov has left #openstack-meeting-414:00
*** openstack changes topic to " (Meeting topic: Glance)"14:00
openstackThe meeting name has been set to 'glance'14:00
llu-laptopo/14:00
TravTo/14:01
jokke_o/14:01
mfedosino/14:01
dshakhrayo/14:01
bpouloso/14:01
flaper87o/14:01
lakshmiS_o/14:01
kragnizo/14:01
flaper87nikhil_k1away IS BACK!14:01
tsufievhi14:01
*** nikhil_k1away is now known as nikhil_k14:01
kragniznikhil_k1notaway14:01
hemanthmo/14:02
nikhil_kHi all14:02
nikhil_kI was away for past few days so don't have much on updates14:02
nikhil_kexcept for one thing14:02
nikhil_k#topic14:02
nikhil_k#topic Updates14:02
*** sankarshan has quit IRC14:02
*** sankarshan has joined #openstack-meeting-414:02
nikhil_k#info added entry for Glance mid-cycle to #link https://wiki.openstack.org/wiki/Sprints14:03
*** aventerav has joined #openstack-meeting-414:03
nikhil_k#action all: please visit https://etherpad.openstack.org/p/liberty-glance-mid-cycle-meetup and fill out the necessary surveys14:03
*** banix has joined #openstack-meeting-414:03
*** jcook has joined #openstack-meeting-414:04
nikhil_kThanks for bringing that up flaper87 on the ML. I will response for everyone's awareness hwoever, updates and meeting minutes on the event would be a preference14:04
flaper87nikhil_k: awesome, thanks14:05
nikhil_kI am arranging for vidyo capability in the conf room and that enables remote participation very likely14:05
nikhil_kAlso, I will try to investigate the tool mentioned by Jeremy on the ML if that seems more useful. We had little luck with mumble last time :/14:05
nikhil_kmoving on..14:06
nikhil_k#topic Glance images streaming from Horizon14:06
nikhil_ktsufiev: please go ahead14:06
nikhil_k#link https://review.openstack.org/#/c/166969/14:06
tsufievso, the problem is with support of file-like object during images upload via Glance v2 API14:07
tsufievAFAIK (or more precisely, I was told), there isn't such capability in v2 API14:07
tsufievis that true?14:07
jokke_tsufiev: could you please be bit more precise?14:08
flaper87I believe tsufiev's refering to stream whatever is being uploaded to horizon directly to glance14:09
*** wxy has joined #openstack-meeting-414:09
flaper87without re-uploading it to glance14:09
tsufievjokke_, sure. So, when I'm to upload an image file into Glance, I could pass some object as 'data' key value, the most important requirement for it is to have .read() method implemented - that works for me in v1 API14:10
tsufievI'm speaking about using glanceclient from Horizon api wrappers14:10
flaper87I guess I got it wrong...14:10
jokke_tsufiev: as far as I know only problem we have (and which is not solvable) is that the client cannot do progress bar for stuff like fifos etc. where it cannot check the size14:10
flaper87in which cases we can just disable the progress bar14:11
flaper87but since this is horizon, I doubt they are using the CLI at all14:11
jokke_other than that I see no problem passing the data through horizon (obviously you need to implment the bits to make that happen in horizon end)14:11
tsufievflaper87, nope, we're speaking about the same thing, just on different level of detalization14:11
flaper87but rather the library itself14:11
flaper87tsufiev: a-ha14:11
flaper87I thought you could pass f-like objs to glanceclient14:11
*** akwasnie has quit IRC14:11
flaper87or at least it was possible14:11
flaper87mmhh14:11
tsufievflaper87, well, our glance experts said I couldn't do it for API v214:12
jokke_tsufiev: you can push the image data through fifo or just stdin on v2 as well no problem14:12
tsufievmfedosin, ^^^14:12
*** jwagner_away is now known as jwagner14:12
*** sankarshan is now known as sankarshan_away14:12
nikhil_ktsufiev: The file like obj should work on glance v2 API. If they don't work in glanceclient then we have a bug. But the functionality should exist14:12
flaper87tsufiev: that's were the difference between your comment and mine is. If you're asking whether glanceclient supports file like object, then the answer is (probably) yes14:13
jokke_it's there and we fixed the behavior around early juno ... the defaults did not work great on glanceclient back then, but it has been working perfectly fine for about a year now14:13
flaper87if the question is whether glanceclient honors the file-like object the right way, then I guess it doesn't14:13
tsufievflaper87, okay, but is .read() method on that object in v2 API supported?14:13
tsufievhm... perhaps I was misinformed...14:14
*** puranamr has quit IRC14:14
nikhil_ktsufiev: I see, it's just a data stream14:14
flaper87tsufiev: https://github.com/openstack/python-glanceclient/blob/master/glanceclient/common/http.py#L58-L6414:14
nikhil_kyou may be referring to copy-from in v1 that's more along the lines of .read() you are asking for14:15
*** sankarshan_away is now known as sankarshan14:16
tsufievflaper87, nikhil_k: the above line seems like the thing that should work for me14:16
nikhil_kand that's how I could make more sense of you comment on the review:- Since image_update is run in a separate thread and the browser itself14:16
nikhil_ksends the large file via XHR, it is imperative that User doesn't close14:16
nikhil_kHorizon page/tab before the image transfer is complete - otherwise it14:16
sigmavirus24tsufiev: can you point to the code you'r eusing for v1 right now?14:16
nikhil_kwill fail.14:16
sigmavirus24maybe that will help clear up the confusion14:16
mfedosinhttps://github.com/openstack/glance/blob/master/glance/common/utils.py#L15614:17
mfedosinI think CooperativeReader uses in both apis14:17
mfedosin(is used)14:18
flaper87wait, I'm confused now. Are we talking about glanceclient or glance14:18
tsufievas a Horizon developer I'm only able to use glanceclient directly :)14:18
flaper87tsufiev: exactly14:18
jokke_that's what I thought as well14:19
jokke_and API perspective neither of the API gets file ... they get datastream14:19
*** dims has quit IRC14:19
tsufievjokke_, so there are no serious differences in v1 vs v2 datastream processing?14:20
flaper87not that I can think of14:21
flaper87tsufiev: is there an issue your facing ?14:21
flaper87Error? Failure? different behaviour ?14:21
flaper87it may be related to the API but not to the datastream14:21
jokke_tsufiev: I didn't say that (meaning I'm not sure), but API perspective there is no file for the REST api ... it gets datastream from the client.14:21
jokke_and the differencies in the python-glanceclient side were unified about year ago14:22
tsufievflaper87, I shall try for myself with v2 - will ping you back (file a bug) if something wrong happens14:22
flaper87tsufiev: roger, that'd be very useful14:22
tsufievsorry for possibly false alarm14:22
sigmavirus24Shouldn't this have been brought up before the emeting?14:22
jokke_but as long as we're talking about doing something with around upload process I'm assuming we're talking about the client14:22
sigmavirus24In #openstack-glance for example?14:22
flaper87sigmavirus24: yeah14:23
sigmavirus24Can we move on to the next topic?14:23
tsufievsure14:23
jokke_sigmavirus24: I see no problem having discussions like this on meeting or mailing list ... that's why we have these14:23
flaper87jokke_: erm, I disagree14:24
flaper87support -> openstack-glance14:24
nikhil_kOk, folks. Let's clear the confusion offline.14:24
flaper87and you gate it 24h/7d14:24
*** matrohon has quit IRC14:24
flaper87s/gate/get/14:24
nikhil_k#topic Reviews/Bugs/Releases14:24
sigmavirus24== flaper8714:24
*** matrohon has joined #openstack-meeting-414:24
flaper87anywa, we're halfway through our meeting, lets move on14:24
nikhil_k#info change default notification exchange name14:24
nikhil_k#link https://review.openstack.org/#/c/194548/14:25
*** tsufiev has left #openstack-meeting-414:25
llu-laptopso, this patch is meant to change the default exchange name for glance notification14:25
llu-laptopjust like nova/cinder/etc14:25
llu-laptopfrom original 'openstack' to 'glance'14:25
sigmavirus24s/original/default/14:26
llu-laptopsigmavirus24: thanks for the clarification14:26
flaper87uuu, I just realized llu-laptop replied, I'm sorry about that14:26
flaper87so, ceilo may listen by default on glance and that's fine14:26
llu-laptopyeah, need your reviews :)14:27
nikhil_kWhat's the motivation for changing defauls? (besides others doing it)14:27
sigmavirus24Yeah I think I agree with llu-laptop14:27
sigmavirus24nikhil_k: I think we were supposed to have changed them when we adopted the notifications work14:27
sigmavirus24It's not that nova, et. all, are just doing this now14:27
*** wxy_ has joined #openstack-meeting-414:27
sigmavirus24It's that we never did it (if I understand correctly)14:27
flaper87I understand it doesn't prohibit admins to set control_exchange14:27
jokke_llu-laptop: sorry, can check the review right now, but what's the reasoning behind this. I'm really really reluctant to change our defaults lightly14:27
flaper87my concern is that we're not warnning them that default has changed14:28
flaper87:)14:28
*** hogepodge has quit IRC14:28
nikhil_ksigmavirus24: gotcha, so a antique bug :)14:28
flaper87which means, if there are other downstream apps listenting on the 'openstack' exchange, then we'll break them\14:28
sigmavirus24nikhil_k: it's an antique free-range artisinal bug14:28
jokke_flaper87: ++14:28
nikhil_kheh14:29
flaper87aaaaaaaand, this is part of the public API14:29
llu-laptopjokke_: follow the openstack norm, is my first motivation14:29
flaper87well, not really public14:29
flaper87but under-cloud public14:29
sigmavirus24flaper87: I think the real question is "Does anyone really listen to notifications?" =P14:29
flaper87llu-laptop: I think your change is fine14:29
flaper87sigmavirus24: we'll never know until we break them14:29
nikhil_kflaper87: :) notifications public?14:29
flaper87but I'd assume yes14:29
sigmavirus24flaper87: my point exactly14:29
*** ajayaa has quit IRC14:29
sigmavirus24so let's change them and find out what happens =P14:29
*** wxy_ has quit IRC14:29
flaper87sigmavirus24: I'll give them your home address14:29
flaper87nikhil_k: they are in the under-cloud14:30
*** wxy_ has joined #openstack-meeting-414:30
sigmavirus24flaper87: yeah that's fine14:30
flaper87say you have your own billing service, you may want to listen there14:30
sigmavirus24I have an extra bed or two I could loan them14:30
flaper87sigmavirus24: can you give me your home address ?14:30
nikhil_ksecond level, right. tfter som processing. so...14:30
flaper87:D14:30
nikhil_kllu-laptop: I don't mind changing it given it makes more consistent/ Just want to ensure that we have it done right.14:30
sigmavirus24flaper87: so the thing is that operators may already be changing this to do billing right14:30
*** wxy_ has quit IRC14:30
sigmavirus24Can we send a message to openstack-operators asking for feedback14:30
*** wxy_ has joined #openstack-meeting-414:30
sigmavirus24Like we can sit here and guess at the impact, or we can ask the people who know14:30
jokke_Seriously guys, you're ok breaking our next upgrade just for cosmetics?!?!?14:31
sigmavirus24jokke_: I'm trolling14:31
*** wxy has quit IRC14:31
flaper87sigmavirus24: I'm all for changing it but I'd like to see if there's a way to avoid the breakage OR at least have a warnning14:31
nikhil_kllu-laptop: these flags seem important to get people attn: DocImpact, UpgradeImpact and the email shoutout like sigmavirus24 mentioned14:31
flaper87and deprecate it14:31
flaper87oh and yeah, what nikhil_k just said14:31
llu-laptopnikhil_k: got that, will put those into commit message14:31
flaper87My point is that assumption is the mother of all fuck ups14:31
flaper87or most of them14:31
jokke_++14:32
flaper87and I don't feel comfortable assuming people have control_exchange=glance already14:32
sigmavirus24I said "may" not "probably"14:32
sigmavirus24=P14:32
flaper87so, my two options are: 1) We change it in a way we don't break it14:32
flaper872) we deprecate it the right way14:32
sigmavirus24I'm fine with saying that we're changing this in M14:32
flaper872 means, we change it in M14:32
sigmavirus24You have L to set it correctly14:32
flaper87right14:32
nikhil_k+114:33
jokke_so L having deprecation warning of the old option and M changing the default14:33
jokke_I'd be fine with that14:33
nikhil_k#action llu-laptop : ensure https://review.openstack.org/#/c/194548 has mention and work done for -- L having deprecation warning of the old option and M changing the default14:34
llu-laptopjokke_: it's not deprecating old options, but changing the default value14:34
nikhil_koh right14:34
nikhil_k#action llu-laptop : ensure https://review.openstack.org/#/c/194548 has mention and work done for -- L having deprecation warning of the change in default and M changing the default14:34
flaper87llu-laptop: sorry for giving trouble for such a small change but breaking backwards compatibility is something that we try really freaking hard not to do: https://www.youtube.com/watch?v=EYKdmo9Rg2s14:34
jokke_llu-laptop: yes old default value rather than option14:34
llu-laptopflaper87: understandable14:35
jokke_llu-laptop: what I thought wasn't what I typed ;)14:35
nikhil_kLet's move on14:36
nikhil_k#info  scrub images in parallel14:36
nikhil_k#link https://review.openstack.org/#/c/196240/14:36
*** MarkAtwood has joined #openstack-meeting-414:37
nikhil_kguess hemanthm is away14:37
sigmavirus24Why are we reducing that from 1000 to 100?14:37
nikhil_kI had a chat with him14:37
*** wxy has joined #openstack-meeting-414:37
jcook+1 to scrub images in parallel14:37
sigmavirus24"Oh to not overwhelm the swift cluster"14:37
sigmavirus24(it as in the commit message)14:37
*** TheIntern has joined #openstack-meeting-414:37
*** TheIntern has left #openstack-meeting-414:37
jcookat Rackspace production scale it can't scrub all the images in serial14:38
sigmavirus24jcook: right14:38
*** TheIntern has joined #openstack-meeting-414:38
jokke_I think last time we discussed about this it was discarded because of the extra load the parallel scrubbing would cause, so rather do it slower, but ensuring that the services are not overloaded14:38
*** dims has joined #openstack-meeting-414:38
flaper87I haven't reviewed the patch but the idea sounds nice14:38
jcookI saw on the order of 10s of thousands in the backlog that in parallel cleared up rather quickly and not noticeable prod issues14:39
nikhil_kYeah, the alternative is to refactor the scrubber to enable it to do the deletes over the day/week etc14:39
jcookSwift is designed for parallel scaling for speed of downloads and uploads14:39
jcookyeah I have a spec for that14:40
jcookI think hemanthm is working with an intern on task scrubbing and maybe image scrubbing updates14:40
*** wxy_ has quit IRC14:40
jokke_sorry not being able to check the review atm. but are/can we do that as configurable?14:40
nikhil_kI agree that production deployments of swift should be able to handle this14:40
jcookin the short term though, the scrubber does not scale14:40
jcookand swift (in my experience) handles it fine14:41
nikhil_knot necessarily devstack14:41
* jokke_ would like to remind that we have other backends than just swift14:41
nikhil_kyeah14:41
jcookthat is true, make it configurable?14:41
jcookparallelizing deletes that is14:42
nikhil_kI doubt if 100 threads would be too much for other backends14:42
*** galstrom has joined #openstack-meeting-414:42
*** galstrom has left #openstack-meeting-414:42
jokke_I would prefer than ... I know that it's again one more thing to take in account when deploying, but it would be way safer bet than again assuming that based on experience with swift the others wouldn't be affected14:42
jokke_/than/that/14:43
sigmavirus24nikhil_k: shouldn't be a problem for the filesystem backend, http store doesn't allow deletes, cinder is broken miserably14:43
sigmavirus24rbd?14:43
jcookeither that or just make thread pool configurable and default 114:43
sigmavirus24flaper87: would that maybe be a problem for rbd (same question to sabari for vmware)14:43
*** VanL has joined #openstack-meeting-414:43
nikhil_kI doubt if vmwaer is using scrubber14:44
*** dims has quit IRC14:44
flaper87I don't think it would be a problem for RBD itself. What would worry me is:14:44
flaper87if you're using  rbd for nova, glance and cinder, you may be stressing it more than you want14:44
*** matrohon has quit IRC14:45
flaper87and vms/devices will be affected14:45
kragnizcinder should be less broken if this lands: https://review.openstack.org/#/c/166414/14:45
flaper87so, having it configurable is definitely the right thing to do in this regard14:45
jcook#startvote What to do with scrubber? approve-it, config-for-parallel, config-for-thread-pool, config-both, other14:45
openstackOnly the meeting chair may start a vote.14:45
*** matrohon has joined #openstack-meeting-414:45
jcookboo14:45
nikhil_k#startvote What to do with scrubber? approve-it, config-for-parallel, config-for-thread-pool, config-both, other14:45
openstackOnly the meeting chair may start a vote.14:45
jokke_haha! :P14:45
jcookyay!14:45
*** nikhil_k is now known as nikhil_k1away14:45
nikhil_k1away#startvote What to do with scrubber? approve-it, config-for-parallel, config-for-thread-pool, config-both, other14:46
openstackBegin voting on: What to do with scrubber? Valid vote options are approve-it, config-for-parallel, config-for-thread-pool, config-both, other.14:46
openstackVote using '#vote OPTION'. Only your last vote counts.14:46
*** nikhil_k1away is now known as nikhil_k14:46
*** nikhil_k is now known as nikhil_k1away14:46
jcook#vote approve-it14:46
*** banix has quit IRC14:46
jcookbut I'm ok with config too14:46
nikhil_k1away#chair nikhil_k14:46
openstackWarning: Nick not in channel: nikhil_k14:46
openstackCurrent chairs: nikhil_k nikhil_k1away14:46
tsekiyamkragniz: yeah, I'd like to make it progress. Any reviews for it are appreciated14:46
*** nikhil_k1away is now known as nikhil_k14:46
sigmavirus24#vote config-both14:46
flaper87#vote config-both14:46
sigmavirus24Why not increase testing complexity? (He says semi-seriously)14:46
jokke_#vote config-both14:46
kragniz#vote config-both14:47
nikhil_k#vote config-for-thread-pool14:47
nikhil_kconfig-for-thread-pool solves both problems14:47
mfedosin#vote config-both14:47
jcookyeah config for pool does solve both14:48
jcookthough having an option to not use threads is fine14:48
jcookerm14:48
flaper8710 mins left14:48
flaper8712 to be precise14:48
jcookI guess we are using them either way14:48
nikhil_kyep14:49
jcook#vote config-for-thread-pool14:49
nikhil_kmoving away from eventlet would be our goal when the entire ecosystem does so14:49
flaper87if the entire ecosystem does so ;)14:49
* jokke_ is really looking for that day14:49
nikhil_kheh14:49
*** dims has joined #openstack-meeting-414:49
jokke_even more than deprecating v1 api14:49
sigmavirus24#vote config-for-thread-pool14:50
sigmavirus24I hate eventlet14:50
sigmavirus24jokke_: are we ever going to port glance to twisted?14:50
flaper87is the vote still open?14:50
jokke_sigmavirus24: I seriously would love that option14:50
flaper87longest voting ever :P14:50
nikhil_kyes14:50
jcook>_>;14:50
sigmavirus24#endflaper87vote14:50
flaper87hahahaha14:50
jcooklol14:50
nikhil_kpeople still voting, what can I do.. :P14:50
nikhil_k#endvote14:50
openstackVoted on "What to do with scrubber?" Results are14:50
openstackconfig-for-thread-pool (3): sigmavirus24, nikhil_k, jcook14:50
openstackconfig-both (4): kragniz, mfedosin, jokke_, flaper8714:50
jcookboth it is14:51
nikhil_kpeople are showing bitterness for more options in openstack14:51
jcookhemanthm: ^14:51
nikhil_kconfigurations to be precise14:51
nikhil_k#topic Open Discussion14:51
*** openstack changes topic to "Open Discussion (Meeting topic: Glance)"14:51
jokke_nikhil_k: certain devs are ;)14:51
tsekiyamI'd like to make progress my proposal for implement upload/download to cinder glance_store.14:52
tsekiyamhttps://review.openstack.org/#/c/166414/14:52
mfedosinafair we wanted to have artifacts 5min discussions14:52
tsekiyamThis fix up the broken cinder backend.14:52
nikhil_kflaper87: what's up? You seemed antsy to move on?14:52
tsekiyamAny advice to make it forward? Does it help if I ask cinder experts for reviews for it?14:52
sigmavirus24mfedosin: we have 9 minutes to have a 5 min discussion14:52
flaper87what cinder backend? #joke14:52
tsekiyamlol14:52
sigmavirus24tsekiyam: yeah having cinder SMEs look at it would be helpful14:52
nikhil_kmfedosin: yep, let's do that if you14:52
flaper87nikhil_k: haha, all good. I was just doing some sigmavirus24trolling14:53
mfedosinso, just everyone to be aware of it...14:53
nikhil_kyou've time. I forgot to update the agenda and people had added items for today14:53
nikhil_k:)14:53
flaper87tsekiyam: I'll review your patch and get back to you14:53
mfedosinAlex Tivelkov status: He is fighting with oslo.versioned object. He made several commit there, but they were reverted, because they broke nova and cinder. Now he's working on fixing it.14:53
tsekiyamokey, I'll ask someone in cinder devs to review it.14:54
flaper87mfedosin: :(14:54
flaper87mfedosin: but I'm happy he's working on that14:54
flaper87that's a great cross-project effort14:54
mfedosinMy and Darja status: We are working on the glance v3 client14:54
mfedosinCurrently we have 3 commits there:14:54
nikhil_ksigmavirus24: flaper87 do you guys have anything for drivers' meeting that  happened this week? #link http://eavesdrop.openstack.org/meetings/glance_drivers/2015/glance_drivers.2015-06-30-14.02.html14:54
mfedosininitial one (https://review.openstack.org/#/c/189860/)14:55
*** xingchao_ has joined #openstack-meeting-414:55
mfedosinCRUD (https://review.openstack.org/#/c/192261/)14:55
mfedosinblob operations (https://review.openstack.org/#/c/197970/)14:55
mfedosinAlso we have a commit in domain model https://review.openstack.org/#/c/197053/ and it wants an approve :)14:55
jokke_nikhil_k: I think worth of mentioning, I managed to troll flaper87 totally on the drivers meeting :P14:55
mfedosinFuture plans are to start working on api stabilization with api-wg and move out from domain model to something more plain.14:55
nikhil_kjokke_: :) my guess is glance_store?14:56
jokke_nikhil_k: yup14:56
sigmavirus24nikhil_k: just the email flaper87 sent to the ML14:56
nikhil_kthanks sigmavirus24 !14:56
nikhil_kjokke_: :)14:56
*** carl_baldwin has joined #openstack-meeting-414:56
nikhil_kmfedosin: thanks for the update. I guess the action item is14:56
*** wxy has quit IRC14:57
*** wxy has joined #openstack-meeting-414:57
mfedosinAlso there is a good bug https://bugs.launchpad.net/glance/+bug/146981714:57
openstackLaunchpad bug 1469817 in Glance liberty "Glance doesn't handle exceptions from glance_store" [High,Confirmed] - Assigned to Mike Fedosin (mfedosin)14:57
nikhil_k#action review needed for input for glanceclient artifacts support14:57
*** bradjones has quit IRC14:57
*** yamahata has joined #openstack-meeting-414:58
mfedosinIt was found by Alexei Galkin and now we have 39% test coverage instead of 38 :)14:58
mfedosinMy idea to inherit all glance exceptions from similar glance_store exception and then catch glance_store exceptions on the upper level14:58
nikhil_kha14:58
*** wxy has quit IRC14:58
*** bradjones has joined #openstack-meeting-414:58
*** bradjones has quit IRC14:58
*** bradjones has joined #openstack-meeting-414:58
mfedosinGod help us when there will be 42%14:58
tsekiyammfedosin: they only says that "sorry for inconvenience"14:59
nikhil_kWe are out of time.15:00
flaper87jokke_: ++ for the troll :D15:00
nikhil_kThanks all!15:00
flaper87sorry I got distracted15:00
nikhil_k#endmeeting15:00
*** openstack changes topic to "Automatic Task Triggering (Meeting topic: glance drivers)"15:00
openstackMeeting ended Thu Jul  2 15:00:08 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-07-02-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-07-02-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-07-02-14.00.log.html15:00
jokke_Thanks15:00
*** bpoulos has left #openstack-meeting-415:00
*** llu-laptop has left #openstack-meeting-415:00
TravT#startmeeting openstack search15:00
openstackMeeting started Thu Jul  2 15:00:27 2015 UTC and is due to finish in 60 minutes.  The chair is TravT. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: openstack search)"15:00
openstackThe meeting name has been set to 'openstack_search'15:00
nikhil_ko/15:00
kragnizo/15:00
david-lyleo/15:00
*** lazy_prince has joined #openstack-meeting-415:00
*** hogepodge has joined #openstack-meeting-415:01
TravThello everybody.15:01
lakshmiS_o/15:01
TravTgive a min to see if other join15:01
*** dshakhray has quit IRC15:01
*** tsekiyam has quit IRC15:01
sigmavirus24o/15:02
sigmavirus24sorry15:02
TravTlet me try to track down sjmc7...15:03
TravTso, agenda is here as usual: https://etherpad.openstack.org/p/search-team-meeting-agenda15:03
TravTplease add anything you'd like to talk about.15:04
TravTtoday, i mainly wanted to walk through bugs / blueprints15:04
TravTnikhil_k, anything else you had in mind15:04
nikhil_kTravT: nope, I just got back from a long travel15:05
*** sjmc7 has joined #openstack-meeting-415:05
sigmavirus24"bugs" there are no bugs, just accidental features15:05
nikhil_kso cactchin up :)15:05
nikhil_ksigmavirus24: lol15:05
sigmavirus24flaper87: ^^15:05
sjmc7hey15:06
TravTok, so then15:06
*** dims has quit IRC15:06
TravT#topic bugs https://bugs.launchpad.net/searchlight15:06
*** openstack changes topic to "bugs https://bugs.launchpad.net/searchlight (Meeting topic: openstack search)"15:06
* flaper87 reads15:07
flaper87sigmavirus24: LOL15:07
*** Guest42148 has joined #openstack-meeting-415:07
TravTso i'll start with an easy one to discuss as it leads to another15:07
TravTi created a bug (could have been a bp) for setting a dev env15:07
TravThttps://bugs.launchpad.net/searchlight/+bug/147019415:07
openstackLaunchpad bug 1470194 in OpenStack Search (Searchlight) "Missing developer manual install docs" [Undecided,In progress] - Assigned to Travis Tripp (travis-tripp)15:07
TravTi think it is done.15:07
TravTjust addressed some minor comments from krykowski15:08
TravTbut it the process of that lakshmi and I remembered that we  have  a problem with notification listening15:08
*** Guest42148 is now known as dims_15:09
TravThttps://bugs.launchpad.net/searchlight/+bug/147062715:09
openstackLaunchpad bug 1470627 in OpenStack Search (Searchlight) "Searchlight does not receive notification when deployed in same env as Ceilometer" [High,New]15:09
TravTsjmc7 originally found this while working on our summit demo15:09
sigmavirus24oof15:10
*** belmoreira has quit IRC15:10
sjmc7i never definitely confirmed it15:10
sigmavirus24that hurts15:10
TravTsjmc7 or lakshmiS can you characterize a bit of what we think the problem is15:10
TravTsjmc7, i confirmed it yesterday15:10
sjmc7but it would explain some behavior i saw15:10
sjmc7ok15:10
sjmc7the problem is15:10
sjmc7that we're sharing notifications with ceilometer, so to rabbitmq ceilometer and searchlight look like the same consumer15:10
TravTwhen i killed the ceilometer processes, notifications flowed.15:11
lakshmiS_ceilometer also listens on the same glance notification info15:11
lakshmiS_and searchlight doesnt seem to recieve it when ceilometer is running15:11
lakshmiS_i was trying to create a pool name to isolate it but still troubleshooting it15:12
TravTok, so lakshmiS_ does that mean you can take ownership of this bug?15:13
lakshmiS_sure15:13
sjmc7being able to set up a separate consumer would be a much neater fix than having to have services send requests to multiple topics15:13
*** asselin_ has joined #openstack-meeting-415:14
TravTanybody have any ideas to help lakshmiS_ out?15:14
lakshmiS_yeah that the idea behind a pool name as an namespace which oslo messaging should send it multiple consumers but somehow not working15:14
TravTok, i guess we can move on.15:16
*** matrohon has quit IRC15:16
*** matrohon has joined #openstack-meeting-415:16
TravTnext bug seems pretty small. not much to say about it.15:16
TravThttps://bugs.launchpad.net/searchlight/+bug/146933615:16
openstackLaunchpad bug 1469336 in OpenStack Search (Searchlight) "Errors are returned as html" [Undecided,New]15:16
*** puranamr has joined #openstack-meeting-415:17
TravTso moving on #topic blueprints https://blueprints.launchpad.net/searchlight15:17
TravT#topic blueprints https://blueprints.launchpad.net/searchlight15:17
*** openstack changes topic to "blueprints https://blueprints.launchpad.net/searchlight (Meeting topic: openstack search)"15:17
TravTekarlso has done some great work on getting a devstack plugin going15:18
TravThttps://blueprints.launchpad.net/searchlight/+spec/devstack-plugin15:18
nikhil_kyay!15:18
sigmavirus24TravT: agreed15:18
TravTI tested it quite a bit yesterday15:18
*** VanL has quit IRC15:18
TravTfound a few things and he addressed overnight15:18
*** DericHorn-HP has joined #openstack-meeting-415:18
TravTi just was almost done testing it again this morning15:18
TravThit an odd error, that I think was my fault15:18
*** TheIntern has quit IRC15:18
TravT#link https://review.openstack.org/#/c/194251/15:19
TravTbut this is a bit tricky to test.15:19
TravTI'd like to suggest that we don't all nitpick this patch too much15:19
*** lazy_prince has quit IRC15:19
TravTbecause it enables everybody and is kinda difficult to test in current state15:20
TravTbecause of the way devstack plugins work.15:20
TravTyou kind of have to install devstack twice15:20
TravTi put some notes in a comment yesterday15:20
TravTon that.15:20
TravTbut hopefully we can get it in and then improve from there15:21
*** VanL has joined #openstack-meeting-415:21
sjmc7agree about not nitpicking too much,although i would like to get the entrypoints tidied up15:21
TravTwell, that is a chicken or the egg kind of thing right?15:21
TravTyou are referring to #link https://review.openstack.org/#/c/196750/15:22
TravT?15:22
sjmc7it's an ordering issue, yes15:22
sjmc7yeah, i guess it doesn't matter which way round15:22
TravTboth are marked as essential.15:23
TravTso, just walking down through the bp's15:23
TravTnext is https://blueprints.launchpad.net/searchlight/+spec/glance-metadef-plugin15:23
TravTsjmc7 are metadefs basically done?15:24
TravTat least for first pass?15:24
sjmc7i *think* so, though i'd like someone who understands them to test it15:25
*** med_ has joined #openstack-meeting-415:25
*** VanL has quit IRC15:25
sjmc7in particular i think updates may need looking at. the original was very complicated and relied heavily on database access15:25
TravTany volunteers to look through that?  lakshmiS_?15:26
lakshmiS_i think kamil would be a better person, but i can also check15:26
*** puranamr has quit IRC15:26
TravTok, let's ping kamil.  he's been pretty active recently.15:26
TravTi will be looking at them from a consumer standpoint shortly.15:27
TravTok, so next is nova.15:27
TravTnikhil_k owns it, but i believe sjmc7 you were going to do an initial drop of the summit demo POC code?15:28
TravThttps://blueprints.launchpad.net/searchlight/+spec/nova-instances-plugin15:28
sjmc7yeah, i was. i will try and do it today15:28
sjmc7or over the weekend15:28
* nikhil_k needs to consult nova folks about object versioning and indexing15:28
sjmc7yeah, i'm not getting involved with that :)15:28
TravTok, well, i guess if you can just update the blueprint with what you know.15:29
sjmc7i'll get an initial review up when i can15:30
nikhil_kmissed my meeting with john this week, I will try to schedule one next and update15:30
TravTsjmc7, it is a holiday weekend, so not asking you to work over it!15:30
sjmc7that's going to happen anyway unfortunately15:30
*** ajmiller__ is now known as ajmiller15:30
TravTin my doc patch, i have started a rst for glance plugin as an initial landing place for documenting the plugins15:31
TravThttps://review.openstack.org/#/c/197232/8/doc/source/plugins/glance.rst15:31
TravTwe'll want to do the same for other plugins15:31
TravTso, maybe what you find out nikhil_k could go in rst file like that15:31
TravTin patch15:31
nikhil_kTravT: sure15:32
TravTthanks15:32
nikhil_k#action nikhil_k : add infromation on nova pluging reqs to documentation15:32
TravTnext up is indexing cli15:32
TravTbp is basically blank at this point.15:32
TravThttps://blueprints.launchpad.net/searchlight/+spec/indexing-cli15:32
* nikhil_k is half asleep/tired15:32
TravTi'm wondering how this relates to the entrypoints15:32
sjmc7i don't know what this is :)15:33
TravTthere was some discussion about it in brainstorming session15:33
TravTahh... now i remember15:34
TravTthis is diff than searchlight-index15:34
TravTthis is more like the glanceclient has a cli15:34
TravTi seem to remember kragniz being opinionated on this, but since the BP is basically blank and I filed it, I'll try to first clarify from old notes15:35
nikhil_kwrapper around API? then why just on index?15:35
TravTnikhil_k, idk15:35
nikhil_kmay be we can ask on that BP?15:36
TravTyeah, if you can fill in anything on it, please do.15:36
nikhil_kand ask for differentiation between searchlight-index ?15:36
*** singleth_ has quit IRC15:37
TravTany other comments on CLI to add here?15:37
sjmc7i think this was to aboid having to run the equiv of glance-manage15:38
sjmc7something you could use to force indexing from elsewhere15:38
TravTi would like to see the index command API make a comeback15:39
TravTiirc that got ripped out of what landed in glance15:39
TravTi mean, it never made it into glance15:39
TravTand so we still don't have it15:39
sjmc7i've no objection to doing that. the plumbing is mostly there15:39
*** armax has joined #openstack-meeting-415:39
TravTso, i suppose that means a new BP for the API first15:40
TravTAnybody willing to file it?  I think we could copy paste from our original spec in glance.15:40
sjmc7if nobody else wants to do it i'll volunteer and hopefully not forget this one too15:41
TravTlol15:41
lakshmiS_you mean the original spec?15:41
TravTwe had a whole section in the original spec on an index management API...15:41
TravTthat's basically the BP i'm talking about filing15:42
lakshmiS_yeah i can do that too15:42
TravTok. cool15:42
TravTnext up functional tests15:42
TravThttps://blueprints.launchpad.net/searchlight/+spec/set-up-functional-tests15:42
TravTanybody willing to take ownership?15:42
TravTguess we'll have to come back to that.15:44
lakshmiS_i have some of the RBAC sceanarios that brian has given previously which i can add some of them but not all the tests15:44
nikhil_kTravT: ++15:44
sjmc7we keep getting caught up on what we mean by functional tests15:44
nikhil_klakshmiS_: I can pair with you on adding more covrage15:44
sjmc7there's the patch that was never merged into glance that i did, but last week it sounded like that wasn't what people want15:44
TravTlakshmiS_, you don't have to own the whole thing.15:44
lakshmiS_nikhil_k: sure15:44
ekarlsooii guys15:44
ekarlsosorry I just got back home ;)15:45
TravTo/ ekarlso15:45
TravTwe praised your devstack work earlier15:45
TravTi had hoped to have it re-tested by the start of this meeting15:45
TravTbut got a weird erro.15:45
TravTr15:45
nikhil_ksjmc7: I think we agreed to take that route for now (merge that patch) and refactor testing15:45
TravTmight ping you afterwords15:45
*** marcusvrn has quit IRC15:45
nikhil_krefactor testing later (in early M)15:46
ekarlsouse the project room after then TravT :)15:46
sjmc7ok. i've not had time to do that this week15:46
ekarlsoi'll volunteer partially for testing btw :)15:46
TravT:)15:46
TravTnikhil_k, that is what I remember as well15:46
TravTok, so if somebody can take it as being assigned to them, it doesn't mean you own everything15:47
TravTnext up is horizon integration for images15:48
TravThttps://blueprints.launchpad.net/searchlight/+spec/horizon-integration-images15:48
*** TheIntern has joined #openstack-meeting-415:48
TravTi'm working towards that15:48
TravTi've filed a couple blueprints in horizon.15:48
TravTwe have a chain of things that have to happen15:48
nikhil_klakshmiS_: ekarlso and I can be coassignees (added in the notes)15:48
lakshmiS_ok15:48
TravTthanks guys!15:48
TravTbasically in horizon, we are trying to angularize the tables.15:49
TravTso, we have to get the images table angularized first.15:49
TravTwhich is also dependent on a bunch of other work going on that david-lyle and i are supporting15:49
TravTbut, i have a personal goal of getting a first pass at angularizing the images table next week.15:50
* david-lyle 's personal waterloo15:50
sjmc7:)15:50
TravTand want to have some initial integration attempt with searchlight by the horizon mid-cycle in a 2-ish weeks.15:51
*** sbalukoff has joined #openstack-meeting-415:51
*** b3rnard0 has joined #openstack-meeting-415:51
ekarlsoi'll be pushing designate support also very soon15:51
TravTthis is intended to serve two purposes.  first is to figure out what more needs to be done in horizon, but second, help drive any improvements to our API.15:51
TravTok. so that's it for high's.15:53
TravTkragniz: how is the "remove from glance" going?15:53
*** mzawadzki_mirant has joined #openstack-meeting-415:54
* TravT maybe he dropped.15:54
kragnizTravT: it's going well15:54
*** adityav has joined #openstack-meeting-415:54
TravTanything needed from us?15:54
kragnizall tests are passing, appart from a requirements issue that wasn't related15:54
kragnizapart from reviews, not much15:55
kragniz#link https://review.openstack.org/#/c/197043/15:55
TravTwe are almost out of time, but i wanted to ask about two other BP's.  swift and neutron.15:55
nikhil_k#link https://review.openstack.org/#/c/197043/15:55
sjmc7havn't had a chance to look at neutron15:56
*** stevelle has joined #openstack-meeting-415:56
TravTkragniz, have you, mclaren, lakshmiS_ been able to make progress with the swift team?15:56
lakshmiS_yeah i also wanted to know from stuart if he heard any further on the swift?15:56
kragnizTravT: not much from us15:57
*** alextricity has joined #openstack-meeting-415:57
kragnizmclaren's away for a few days15:57
lakshmiS_last thing i saw was a note from stuart on a similar spec in swift15:57
TravTok. well, let's talk next week when stuart is back.  just don't want that team to move along without us.15:58
TravTekarlso, from a priority standpoint, we can bump up designate plugin if you are gonna be working on it.15:59
TravTand we should talk with david-lyle re: horizon priority15:59
*** odyssey4me has joined #openstack-meeting-415:59
TravTI just wanted to thank everybody for the progress we made.16:00
david-lylehorizon priority for?16:00
*** GB21 has joined #openstack-meeting-416:00
TravTi think going from not a project to being a project with a repo and (almost) installable via devstack in one milestone is great progress!16:00
TravTdavid-lyle: time is up. let's chat in the room16:01
david-lylesure16:01
TravTthanks everybody!16:01
TravT#endmeeting16:01
*** openstack changes topic to "Automatic Task Triggering (Meeting topic: glance drivers)"16:01
openstackMeeting ended Thu Jul  2 16:01:23 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:01
*** bgmccollum has joined #openstack-meeting-416:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-07-02-15.00.html16:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-07-02-15.00.txt16:01
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-07-02-15.00.log.html16:01
*** Sam-I-Am has joined #openstack-meeting-416:01
*** sjmc7 has left #openstack-meeting-416:01
cloudnull#startmeeting OpenStack Ansible Meeting16:01
openstackMeeting started Thu Jul  2 16:01:40 2015 UTC and is due to finish in 60 minutes.  The chair is cloudnull. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: OpenStack Ansible Meeting)"16:01
openstackThe meeting name has been set to 'openstack_ansible_meeting'16:01
*** lakshmiS_ has quit IRC16:01
Sam-I-Ammoo16:01
sigmavirus24oom16:01
cloudnull#topic Agenda & rollcall16:01
*** openstack changes topic to "Agenda & rollcall (Meeting topic: OpenStack Ansible Meeting)"16:01
sigmavirus24o/16:01
palendaeo/16:02
stevelleo/16:02
alextricityHey16:02
TheInterno/16:02
*** evrardjp has joined #openstack-meeting-416:02
Sam-I-Amsigmavirus24: little-endian cow16:02
odyssey4meo/16:02
alextricityhah16:02
evrardjphello16:02
b3rnard0howdy16:02
*** asselin_ has quit IRC16:02
cloudnull#topic Blueprints16:02
*** openstack changes topic to "Blueprints (Meeting topic: OpenStack Ansible Meeting)"16:02
*** dannywilson has joined #openstack-meeting-416:03
cloudnullodyssey4me hughsaunders miguelgrinberg sigmavirus24 how goes the fed sp idp efforts ?16:03
cloudnull#link https://blueprints.launchpad.net/openstack-ansible/+spec/keystone-federation16:03
cloudnull#link https://blueprints.launchpad.net/openstack-ansible/+spec/keystone-sp-adfs-idp16:03
miguelgrinbergcloudnull: idp is blocked on the keystone v3 module, but otherwise in good shape16:03
hughsaunderscloudnull: ok... currently having some gating issues with getting the v3 update for keystone module in16:03
sigmavirus24Keystone v3 module upgrades are soo close16:03
odyssey4meSo for those who don't know, we've been working on adding federation configuration to os-ansible-deployment. ^16:03
odyssey4meWe sent out a mail to the openstack-operators and openstack-dev mailing lists to request feedback on the first spec which is near ready.16:04
cloudnullhas there been any traction on that so far?16:05
hughsaundersA few approving replies16:05
odyssey4meWe have working prototypes for both the keystone2keystone federation, and just today we managed to get the ADFS-keystone federation working too.16:05
odyssey4meI'll spend tomorrow updating the two specs to refect what we've learned and to adjust the use-cases for the first as we've discovered that keystone in kilo is not ready to be a full IdP.16:06
*** TravT has left #openstack-meeting-416:06
*** matrohon has quit IRC16:06
cloudnullok16:07
odyssey4meI've seen a few comments trickling in on the spec reviews, but we'd like more attention on that from everyone here if possible today before I iterate it tomorrow.16:07
cloudnullNext up, ceilometer . #link https://review.openstack.org/#/c/17306716:07
cloudnullalextricity: ^16:07
alextricityIt's ready for reviews. There was a merge conflict this morning so a new patch set was neede16:08
alextricityneeded*16:08
cloudnullthe patch as is LGTM . and now has doc dep thats following it16:08
alextricity^16:09
alextricity#link https://review.openstack.org/#/c/198025/216:09
odyssey4meyeah, I've gone through it and it looks good from a code standpoint.16:09
cloudnulli have it up and running on a few boxes and it works.16:09
alextricityI've also done testing and metrics are reporting back normally16:09
odyssey4meI'd like to see some testing feedback from anyone who has a gap to try it out.16:09
alextricityThe database connection looks good too16:09
cloudnullthats all we have in the way of open bps being worked on .16:10
alextricityI'll just need cloudnull and odyssey4me to give it another +1 with the new patch set16:11
*** singlethink has joined #openstack-meeting-416:11
cloudnull#topic Open discussion16:11
*** openstack changes topic to "Open discussion (Meeting topic: OpenStack Ansible Meeting)"16:11
cloudnullto build up on what we were talking about last week .16:12
cloudnullDefining the project mission - odyssey4me16:12
cloudnullwe now have a wiki page https://wiki.openstack.org/wiki/OpenStackAnsible16:12
cloudnulland i've posted a WIP manifesto16:12
cloudnull#link https://etherpad.openstack.org/p/openstack-ansible-manifesto16:12
cloudnullthat i'd like people to tear apart16:13
odyssey4mecloudnull nice work!16:13
*** dannywilson has quit IRC16:14
evrardjpto avoid losing people over different wiki pages, I'd like to add a link of this new wiki page on the main repo documentation16:14
cloudnullsometime in the next week or so i'd like to pul lthat out of the wiki and PR it to the main repo16:14
cloudnullevrardjp: ++16:14
odyssey4mecloudnull +116:14
*** amotoki_ has joined #openstack-meeting-416:14
cloudnullso lets chew on that for the next week or so.16:15
cloudnullnext:16:15
cloudnullWhat is our roadmap like? Will making fernet tokens in keystone be an 11.1.0 feature? palendae16:15
cloudnullwe have https://launchpad.net/openstack-ansible/+milestone/11.1.016:16
alextricitynice! this manifesto answers all the questions that i've been asked about osad16:16
cloudnullwhich is looking good so far.16:16
sigmavirus24cloudnull: I think it should be an 11.1.0 feature16:16
palendaecloudnull: That one's my bad, should have removed that after last week16:16
palendaeWe already discussed it and I think it was agreed it's 11.1.016:16
cloudnulli know palendae, just building up on what we talked about.16:17
odyssey4mecloudnull should we be targeting the federation blueprints for 11.1.0 too?16:17
palendaecloudnull: Yep16:17
*** amotoki has quit IRC16:17
sigmavirus24odyssey4me: if we can get them in shape for 11.1.0, why not?16:17
cloudnullodyssey4me: do we think it will be ready for 11.1.0 ?16:17
cloudnullif so i say yes16:17
cloudnullif no then we'll do it for 11.2.016:18
b3rnard0is cloudnull asking for an estimate?16:18
sigmavirus24b3rnard0: nope16:18
cloudnull# /kick b3rnard016:18
sigmavirus24Just a guess16:18
palendaeguesstimate16:18
odyssey4mecloudnull I think there's a fair chance that we'll be code ready - not necessarily docs ready16:18
odyssey4memiguelgrinberg hughsaunders your thoughts?16:18
cloudnulland odyssey4me version numbers are cheap, if it merges for master a day after we drop 11.1 im happy to rev to 11.2 within the next cycle.16:19
miguelgrinbergwhen's 11.1.0?16:19
cloudnullbut if its ship shape for 11.1 then lets do it16:19
odyssey4mehow about we target for 11.1 and review in the final week before d day?16:19
cloudnullok16:19
cloudnullfair16:20
odyssey4meI don't recall us discussing the due date, by the way? Was that date chosen for any special reason?16:20
hughsaundersgating not withstanding, I think we are quite close16:20
palendaemiguelgrinberg: https://launchpad.net/openstack-ansible/+milestone/11.1.0 says 17/7/201516:20
cloudnullit was chosen as being two weeks after the 11.0.4 drop16:20
miguelgrinbergand besides, none of this is going to be enabled by default, so the normal use cases are safe16:20
miguelgrinbergI think we can make it for the 17th, yes16:21
odyssey4memiguelgrinberg true16:21
cloudnullbefore we can target these items we need to target the specs, thus https://review.openstack.org/#/c/194147/ and https://review.openstack.org/#/c/194255/ need to be reviewed16:21
miguelgrinbergwrost case we get federation bugs, which we fix for the next one16:21
cloudnullso cores typie typie.16:21
palendaeyou mean votie votie?16:21
sigmavirus24no16:22
sigmavirus24typie typie16:22
sigmavirus24you need to give -1s with feedback16:22
odyssey4meyup, I'll update the specs tomorrow based on feedback and lessons learned - hopefully we can do final votes on the specs next week16:22
cloudnull#action odyssey4me to update the specs for federation.16:23
*** kobis has quit IRC16:24
cloudnullmoving on.16:24
cloudnull#topic Reviews16:24
*** openstack changes topic to "Reviews (Meeting topic: OpenStack Ansible Meeting)"16:24
*** kobis has joined #openstack-meeting-416:25
cloudnull11.0.4 is coming soon we need the following items worked on https://review.openstack.org/#/q/starredby:cloudnull+status:open,n,z16:25
cloudnulland if there are issues that need backports from https://launchpad.net/openstack-ansible/+milestone/11.0.4 we need to do that too16:25
cloudnullthe keystone fernet update needs love for master.16:27
cloudnull#link https://review.openstack.org/#/c/195853/16:27
cloudnullit looks like its been generaly accepted however we need another core to merge it.16:28
cloudnullpresently we're gating on a fernet token system that has a few issues, which are corrected by that patch.16:28
*** kobis has quit IRC16:29
cloudnullanother review in need of some attention is https://review.openstack.org/#/c/181957/16:30
cloudnullwhich is for ceph client support.16:30
cloudnullsvg: ^16:30
cloudnulllooks like svg is going to post a new review soon .16:30
cloudnullbut if we have folks with more ceph experience it would be great to get more reviews on that.16:31
*** xingchao_ has quit IRC16:31
cloudnullmost of this was mentioned on the ML16:31
cloudnull#link http://lists.openstack.org/pipermail/openstack-dev/2015-June/068362.html16:31
*** singleth_ has joined #openstack-meeting-416:31
odyssey4meyeah, I'd like to ask everyone reviewing that to also pay attention to the ceph-ansible playbooks - we don't need any clashes in variables between the two.16:31
cloudnull++16:32
cloudnull#link https://github.com/ceph/ceph-ansible16:32
evrardjpI agree, while I admit that it doesn't mean that ceph need to/will be deployed by ansible, so the importance of it could be reduced...16:34
palendaeYeah, as about to ask16:34
palendaeAre we assuming that Ceph is deployed with ceph-ansible only?16:34
cloudnullno,16:34
andymccri dont think its an assumption, but if you wanted to and the vars overlapped it could create difficulties16:34
cloudnullwe're simply assuming that there is a ceph cluster available.16:34
palendaeOr are you just asking to be sure we don't have duplicate variable names in case a deployer does use both?16:35
palendaeOk andymccr, makes sense16:35
palendaeI misunderstood16:35
*** VanL has joined #openstack-meeting-416:35
*** singlethink has quit IRC16:35
cloudnullso anything else we want to mention regarding open reviews?16:36
cloudnullmoving on16:37
cloudnull#topic Bugs16:37
*** openstack changes topic to "Bugs (Meeting topic: OpenStack Ansible Meeting)"16:37
cloudnulldo we have an open issues that we want to highlight and or work on ?16:37
*** Swami has joined #openstack-meeting-416:37
cloudnull#link https://bugs.launchpad.net/openstack-ansible16:37
*** fallenpegasus has joined #openstack-meeting-416:37
cloudnullwe have 73 open issues, most of which are low/wishlist items so imo we're looking quite good16:38
cloudnullBjoernT: nothing ?16:39
andymccryeh i think if you remove fix commited its 41 and most of those are assigned already16:39
cloudnullscielence is acceptance16:40
BjoernTThanks for asking, I have nothing special for today. I will go over the wishlist next week16:40
cloudnullok16:40
cloudnullsounds good16:40
cloudnull#topic Open discussion16:40
*** openstack changes topic to "Open discussion (Meeting topic: OpenStack Ansible Meeting)"16:40
cloudnulldoes anyone have anything that they want to talk about? the floor is yours.16:41
odyssey4meit might be a good idea in the bug triage meeting to look at new bugs, but also to revisit old bugs16:41
*** ivar-lazzaro has joined #openstack-meeting-416:41
*** ivar-lazzaro has quit IRC16:41
cloudnullin the last few we've been focusing on new/high and some of the incomplete, but it may be a good idea to start picking through the wishlist16:41
cloudnulland other items.16:42
cloudnulllets give it a go next tuesday  ?16:42
*** ivar-lazzaro has joined #openstack-meeting-416:42
odyssey4meother than that, I would like to ask that we not get into the bad habit of prematurely backporting patches - it makes reviewing them take longer because you have to verify that the backport is the same as the master patch... and quite often the master patch goes through several iterations16:42
odyssey4mewe've ended up having patches land in other branches before master by mistake16:43
evrardjp+116:43
cloudnull+116:43
evrardjpshould there be a timeframe odyssey4me?16:44
odyssey4meif you backport from gerrit once the patch in master has merged, the cherry-pick message will be done properly16:44
cloudnullI'd say that once a patch has +w its ok to bp16:44
odyssey4meevrardjp no timeframe - just no backport until the master patch has merged16:44
evrardjpI agree.16:44
odyssey4mecloudnull +w is fine too if there's a time crunch or something... but that takes more time as the backporter will have to do the backport form the CLI16:45
cloudnullthis is true. if you dont know the git CLI you should wait for the patch to merge into master.16:45
cloudnull:)16:45
odyssey4me:p16:46
*** SumitNaiksatam has quit IRC16:47
cloudnullok motion carries .16:47
cloudnull#action we will no longer backport things from master until its been +w / merged into master.16:47
cloudnullwhat else we got ?16:48
Sam-I-Amnada here16:49
*** SumitNaiksatam has joined #openstack-meeting-416:49
cloudnullthen we're done here IMO .16:49
Sam-I-Amimo too16:49
palendaeYep, don't have anything either16:49
Sam-I-Amback to typey typey16:49
cloudnullsounds good .16:49
odyssey4me\o/16:49
cloudnullgreat work on everything in flight guys16:49
cloudnulland thanks16:50
cloudnull#endmeeting16:50
*** openstack changes topic to "Automatic Task Triggering (Meeting topic: glance drivers)"16:50
openstackMeeting ended Thu Jul  2 16:50:06 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:50
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-07-02-16.01.html16:50
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-07-02-16.01.txt16:50
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-07-02-16.01.log.html16:50
*** Sam-I-Am has left #openstack-meeting-416:50
*** cloudnull has left #openstack-meeting-416:50
*** TheIntern has left #openstack-meeting-416:50
*** odyssey4me has left #openstack-meeting-416:50
*** ivar-lazzaro has quit IRC16:54
*** banix has joined #openstack-meeting-416:54
*** mestery has quit IRC16:55
*** cathy_ has joined #openstack-meeting-416:57
cathy_#startmeeting service_chaining17:00
openstackMeeting started Thu Jul  2 17:00:14 2015 UTC and is due to finish in 60 minutes.  The chair is cathy_. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: service_chaining)"17:00
openstackThe meeting name has been set to 'service_chaining'17:00
cathy_hi everyone17:00
*** vikram_ has joined #openstack-meeting-417:00
*** mfedosin has quit IRC17:00
vikram_hi17:00
cathy_vikram_: hi17:00
vikram_cathy: hi17:01
xgermanhi17:01
*** stevelle has left #openstack-meeting-417:01
cathy_let's wait for a little bit for others to join.17:01
cathy_xgerman: hi17:01
Swamihi17:02
cathy_Swami: hi17:02
cathy_OK, let's start now.17:03
cathy_here are some topics I have in mind for today's discussion. 1.Service chain spec status https://review.openstack.org/#/c/192933/5 2.Repository for Neutron client code to support service chain project 3.Vikram update on discussion with Yuji regarding flow classifier included in SFC spec and implemented in SFC project as a independent module which can be used in the future by other features17:03
cathy_any other topic ?17:04
cathy_#topic Service chain spec status https://review.openstack.org/#/c/192933/517:04
*** openstack changes topic to "Service chain spec status https://review.openstack.org/#/c/192933/5 (Meeting topic: service_chaining)"17:04
*** jwarendt has joined #openstack-meeting-417:05
*** evrardjp has left #openstack-meeting-417:05
*** s3wong has joined #openstack-meeting-417:05
cathy_s3wong: hi17:05
s3wongcathy_: hello17:05
jwarendthi17:05
*** singlethink has joined #openstack-meeting-417:05
cathy_many people have given comments to the spec and the spec has been updated many versions to address those comments.17:06
cathy_jwarendt: hi17:06
*** carl_baldwin has quit IRC17:06
*** VanL has quit IRC17:07
*** saneax has joined #openstack-meeting-417:07
cathy_In our last last IRC meeting, we agreed that we should finalize the spec on June 24. Now we have given it one more week. So it is now time to merge the spec. OK with everyone?17:07
*** banix has quit IRC17:07
cathy_Anyone has different opinion?17:08
*** sankarshan is now known as sankarshan_away17:08
*** singleth_ has quit IRC17:08
s3wongcathy_: let's do it :-)17:08
SwamiLet us wait till the end of this week.17:08
amotoki_cathy_: one question. do you plan to update the current version? inline answers are hard to be tracked later.17:09
pcarverThis spec only addresses "serial" chains, right? I don't see a way of scaling out in parallel.17:09
Swamior shall we go ahead and merge it right now.17:09
cathy_amotoki_: it is already updated17:09
amotoki_i don't oppose to merge itself, but just would like to clarify.17:09
*** puranamr has joined #openstack-meeting-417:10
amotoki_cathy_: woops.  got it.The above link was old :-(17:10
s3wongSwami: unless you think we are going to comment on it during the ID4 weekend...17:10
cathy_pcarver: yes, its scope is serial chain if we mean the same by "serial"17:10
pcarverI'd like to see scale out, i.e. multiple VMs in parallel at a given link in the chain, but I could see how that might need to be a second phase and a later addition to the spec.17:10
Swamino I did see there are some comments from vikram. So if we are going to roll it, why not give it another couple of days, so that we can collect all the input and do a single roll.17:11
vikram_Swami: My comments are more about semantics and elaboration.. design wise i am fine.17:11
*** jwagner is now known as jwagner_away17:12
Swamivikram_: yes I understand, but still should we not roll it address those comments.17:12
vikram_Swami: Ok17:12
Swamivikram_: I am not saying that there is a major change that need to happen.17:12
pcarvercathy_: I think so. This approach to service chaining assumes that all the traffic in the chain can be handled by every VM in the chain. No support for splitting the load among VMs.17:12
Swamipcarver: can't we extend that use case later.17:13
*** rods_ has joined #openstack-meeting-417:13
vikram_Swami: Ok; +117:13
pcarverpcarver: I'm fine with adding it later as long as there's nothing that would prevent it.17:13
Swamipcarver: we don't wan't to address too many use cases and then not able to complete the implemetation in time.17:13
pcarverSwami: I agree17:13
Swamiok then let us proceed.17:14
amotoki_question from newcomer to this meeting. Is there any pointers which describe the scope of the initial work?17:14
pcarverSwami: better to get a first iteration out as long as it doesn't preclude later expansion17:14
cathy_Swami: so you are OK with that we ask for core members to approve it, right?17:14
amotoki_my question looks similar from pcarver.17:14
cathy_pcarver: No, it does not preclude later extension.17:14
Swamicathy_:=117:15
Swamicathy_:+117:15
cathy_pcarver: agree with you that we'd better get the first iteration out, otherwise we will never start:-)17:15
pcarvercathy_: +117:16
amotoki_cathy_: +1. One suggestion is to document the scope of the first iteration.17:16
s3wongcathy_: +117:16
vikram_cathy, pcarver :+117:16
vikram_amotoki: +117:17
amotoki_by doing so we can avoid the same discussions/questions again and again.17:17
vikram_amotoki: bingo..17:17
jwarendt+117:18
vikram_:)17:18
cathy_OK, let's do a formal vote (sorry you have to do again). I will type #startvote, then you type #vote17:18
cathy_#startvote yes or no17:18
openstackUnable to parse vote topic and options.17:18
s3wongopenstack doesn't like it :-017:18
xgermanstarvote question? Yes or No17:18
*** b3rnard0 has left #openstack-meeting-417:19
cathy_oops, it does not work. OK, I guess these +1 counts.17:19
Swamicathy_: yes +1 counts17:19
s3wongor just +1 on the gerrit itself?17:19
vikram_+117:19
cathy_Swami: good :-)17:19
xgermanI think we have consensus17:19
*** Mohankumar_ has joined #openstack-meeting-417:19
*** auld has quit IRC17:20
cathy_s3wong: yes, like your suggestion. Please everyone go to the Gerrit spec to give +117:20
s3wongcathy_: just voted17:20
cathy_xgerman: yes17:20
cathy_cool, let's go to next topic17:20
amotoki_I think we can check api spec and document the first iteration scope in separate reviews.17:21
amotoki_so we can go forward.17:21
*** fitoduarte has joined #openstack-meeting-417:21
cathy_amotoki_: yes17:21
cathy_#agreed  everyone agreed (give +1)  that the spec is now ready to be approved by the core members,  https://review.openstack.org/#/c/192933/517:22
cathy_#topic 2.Repository for Neutron client code to support service chain project17:23
*** openstack changes topic to "2.Repository for Neutron client code to support service chain project (Meeting topic: service_chaining)"17:23
cathy_vikram and Swami : any input on this?17:23
Mohankumar_hi cathy17:23
vikram_cathy: i have checked other repo's, they just keep the updated files only.17:24
cathy_Mohankumar_: hi17:24
Swamicathy_: as I mentioned before we should be using the same repo "networking-sfc" for any client side changes that are specific to sfc.17:24
Mohankumar_shall we split cli into two parts17:24
Swamicathy_: here is an example.17:24
Mohankumar_[1] port chain [2] FLowfliter17:24
amotoki_I agree with Swami as the main maintainer of neutroncleint.17:25
Swamicathy_: #link https://github.com/openstack/networking-l2gw/tree/master/networking_l2gw/l2gatewayclient17:25
vikram_https://github.com/openstack/networking-bgpvpn/tree/master/networking_bgpvpn/neutronclient/neutron/v2_0/bgpvpn17:25
Swamicathy_: the l2gateway folks did similar thing in the networking-l2gw repo,so we should follow the same model.17:25
amotoki_neutronclient has plugin mechanism and you can define a class of sfc command lines.17:25
amotoki_another option is the way l2gw folks does.17:25
amotoki_they have separate CLI.17:25
Swamiamotoki_: which one do you prefer, the former or the later17:26
amotoki_I don't have a strong opinion on this.17:26
cathy_Mohankumar_: yes, let's split the CLI into two parts17:26
pcarverwe want to share the flow classifier with other functions such as QoS, right?17:26
amotoki_personally I am wondering OSC integration but it is a slow progress.17:26
vikram_Swami, amotoki: My confusion is how about the base files which will need changes17:27
Swamivikram_: when you say base files are you talking about the "shell.py".17:27
cathy_pcarver: yes, so let's split the CLI into two parts , one for port chain , another for flow classifier17:27
vikram_eg: client.py / shell.py17:27
amotoki_vikram_: base files? could you elaborate more?17:27
*** aventera_ has joined #openstack-meeting-417:27
vikram_ex: shell.py17:28
pcarvercathy_: good, that makes sense17:28
amotoki_vikram_: let me find a link.17:28
amotoki_I think the contrib mechanism works: https://github.com/openstack/python-neutronclient/tree/master/neutronclient/neutron/v2_0/contrib17:29
amotoki_I don't cover the detail now. you can reach me later.17:29
Mohankumar_I was splited cli s  and submitted neutron client changes [1] https://review.openstack.org/#/c/197014/ [2]https://review.openstack.org/#/c/197040/17:30
*** SumitNaiksatam has quit IRC17:30
vikram_amotoki: thanks for sharing but my question is we might need some common files in the repo already17:30
*** aventerav has quit IRC17:30
cathy_Mohankumar_: thanks. Everyone please review the neutron client changes.17:30
amotoki_Mohankumar_: let me check later17:31
vikram_otherwise when we raise a patch for review then diff for common files like shell.py and client.py will be not accurate17:31
*** rods_ has quit IRC17:31
vikram_amotoki_: you got my question?17:31
Mohankumar_thansk Cathy_ ,amotoki_17:31
*** Brian__ has joined #openstack-meeting-417:32
amotoki_vikram_: which one? if it s about shell.py, I think I answered.17:32
amotoki_vikram_: the contrib mechanism. I can share more detail later.17:32
vikram_amotoki_: ok.. I will take this offline17:33
cathy_Swami: what's your input about vikram's quesiton on "otherwise when we raise a patch for review then diff for common files like shell.py and client.py will be not accurate"?17:33
vikram_eq: https://review.openstack.org/#/c/197014/1/networking_sfc/python-neutronclient/neutronclient/shell.py17:33
Swamicathy_: I think vikram_ can discuss this with amotoki_ since he might be able to provide the right direction since he is the core on the neutron_client.17:34
Brian__I think client code should be in different repository from network-sfc:-)17:34
amotoki_neutron client does not have a separete core team17:34
vikram_Swami, cathy_: ok will discuss with amotoki_17:34
cathy_great.17:35
cathy_#action vikram discuss with amotoki_ about neutron client repository17:35
s3wongyeah, normally client is in a different repo, but maintained by the same set of core17:36
cathy_now can we go to next topic?17:36
Mohankumar_i need json resposes to verify my horizon code17:36
Mohankumar_any can help on this ?17:37
amotoki_Mohankumar_: is it a topic for open discussion? if so we can go to the next topic in the agenda.17:37
vikram_cathy_: Mohankuamr_ need neutron-server changes for verifying horizon changes17:37
cathy_Mohankumar_: OK, Brian can work with you offline on that, OK with you?17:37
Mohankumar_okay cathy_17:37
cathy_vikram_: I will work with Mohankumar_ on the server side17:38
vikram_cathy_:thanks17:38
cathy_#topic 3.Vikram update on discussion with Yuji regarding flow classifier included in SFC spec and implemented in SFC project as a independent module which can be used in the future by other features17:38
*** mzawadzki_mirant has quit IRC17:38
*** openstack changes topic to "3.Vikram update on discussion with Yuji regarding flow classifier included in SFC spec and implemented in SFC project as a independent module which can be used in the future by other features (Meeting topic: service_chaining)"17:38
-amotoki_- longest meeting I have ever seen17:38
-amotoki_- longest topic I have ever seen17:39
s3wong:-)17:39
cathy_:-)17:39
vikram_Yuji agreed that flow classifier and Classifier spec are identical17:39
Swamivikram_: but is he going to drop his spec and follow ours.17:40
Swamivikram_: if both are the same we need to add our input in his spec and either combine the both into one or else get rid of the other.17:40
s3wongvikram_, Swami: yeah, I thought cathy_ mentioned classifier definition would be part of SFC spec?17:40
vikram_Swami: Yuji's only concerns is that the flow classifier spec is proposed in SFC and can it be applicable to neutron?17:40
cathy_vikram_: thanks for the update.17:40
*** VanL_ has joined #openstack-meeting-417:41
cathy_Swami: since flow classifier is a must for our SFC feature, we have included it in the SFC spec.17:41
cathy_s3wong: yes17:41
Swamivikram_: so in that case, if we want to make the Flow classifier generic, then we should follow Yuji's spec and make it generic so that it can be extended later.17:41
*** carl_baldwin has joined #openstack-meeting-417:41
*** xiaodongwang has quit IRC17:42
vikram_Swami: +!17:42
amotoki_Swami: +117:42
s3wongvikram_: and if we make classifier generic, it may need to get into Neturon repo, and SFC would have a dependency on this development17:42
*** aventera_ has quit IRC17:42
vikram_Swami: I feel the current proposal is also generic17:42
cathy_Swami: the flow classifier in our spec is also generic since they are exactly the same. Implementing it inside SFC project does not mean it can not be done in a generic way and be used by other features.17:42
Swamis3wong: yes if we make it generic then we need to dependent on that spec.17:43
*** aventerav has joined #openstack-meeting-417:43
amotoki_SFC is a first consumer of flow classifier and we first need to clarify what is needed for SFC17:43
vikram_s3wong: in the end sfc developed code will also be merged to neutron :)17:43
*** galstrom has joined #openstack-meeting-417:43
Swamivikram_: cathy_: I think we are going in circles.17:43
amotoki_and then discuss how to make it more general.17:43
cathy_s3wong: Yes, that is a key point. We do not like to create a dependency on another new project.17:44
s3wongvikram_: in that case, we may the spec part of networking-sfc spec, and have the development done in network-sfc repo17:44
vikram_s3wong: +117:44
amotoki_Options are (1) we discuss the generic model first or (2) we conclude what is required as SFC project.17:44
*** TheIntern has joined #openstack-meeting-417:44
cathy_s3wong: +117:44
*** TheIntern has left #openstack-meeting-417:44
Swamicathy_: vikram_: my concern is if we don't get to consensus on the flow classifier today with Yuji then it would end up in two different implementations.17:45
cathy_amotoki_: it is required ad SFC project, no doubt. Without it we cna not say we deliver the SFC feature17:45
s3wongamotoki_: I think given that SFC development is slated (to get something done by) Liberty, we may need to first get a classifier that is more specific to SFC first before iterating it to be generic17:45
amotoki_Swami: what is the key difference of two diff impls?17:45
vikram_Swami: this concern is already raised via https://etherpad.openstack.org/p/flow-classifier17:45
Swamiamotoki_: vikram_ says that it is the same. So my request is to make it as a single spec.17:46
cathy_I think s3wong are amotoki_ are saying the same thing and I agree with their point.17:46
*** auld has joined #openstack-meeting-417:46
vikram_amotoki_: i have read both the spec and they are same.. even yuji has admitted that17:46
amotoki_i think there are two points: API perspective and implementation.17:48
cathy_vikram_: so I don't think we need to create a separate spec which address the same as what is in our SFC spec.17:48
vikram_Swami: I have also asked Kyle to help us on this soon.17:48
s3wongvikram_: in that case, let's put the classifier spec in networking-sfc, so we have a specific use case, and can discuss/reach-consensus accordingly; now it is filed against neutron-specs17:48
amotoki_let me check. I think I haven'ts spent enought time to review them both.17:48
*** carl_baldwin has quit IRC17:49
vikram_s3wong: no need of separate spec..17:49
vikram_i feel the same spec is okay17:49
*** nbouthors has joined #openstack-meeting-417:49
s3wongvikram_: as you said earlier, things in networking-sfc will eventually merge into Neutron anyway17:49
vikram_what i meant was just we develope code as a generic model as per the spec17:49
amotoki_i think there are two points: API perspective and implementation. let me check both specs. I will reach yuji tomorrow morinig.17:50
s3wongvikram_: so in that case, we can first iterate the classifier spec within the SFC team17:50
vikram_s3wong: i am not sure on this.. may be cathy/Swami/amotoki_ will answer it better17:51
*** carl_baldwin has joined #openstack-meeting-417:51
*** carl_baldwin has quit IRC17:51
*** carl_baldwin has joined #openstack-meeting-417:52
Swamivikram_: yes I agree with s3wong that we can bring everything into the SFC spec under networking-sfc and then proceed, so that we don't have any dependency and everything is confined within this team.17:52
amotoki_I think it is better to start in SFC team as long as the requriements are clarified.17:52
cathy_The bottom line is that we need the flow classifier spec API and implementation in our SFC feature. Without it we can not deliver the SFC feature.17:52
cathy_I agree with Swami and amotoki_ and s3wong17:53
cathy_So it seems the consensus is to have the flow classifier in the SFC spec and proceed.17:54
*** CheKoLyN has joined #openstack-meeting-417:54
vikram_cathy_: so what's will be the next step on this?17:54
amotoki_one important point is to clarify the requirements for classifier from SFC perspective in our discussion.17:54
cathy_vikram_: let's proceed with the SFC spec and start coding as fast as we can with high quality:-)17:55
amotoki_if it is claer, we can discuss more general modle easier.17:55
*** xingchao_ has joined #openstack-meeting-417:55
*** BjoernT has quit IRC17:56
cathy_amotoki_: yes, agree with you. The requirements of classifier for SFC has been addressed in the SFC spec itself.17:56
cathy_It is needed to associate a specific tenant's flow with a service chain that the flow will be steered through to get the sequence of services specified by the chain.17:57
s3wongcathy_: in fact, the classifier definition is already in the SFC API spec, right?17:57
cathy_Good discussion.17:57
s3wongcathy_: so really no need for another spec, honestly17:57
cathy_s3wong: yes, exactly17:57
s3wongcathy_: yes --- time to implement :-)17:58
nbouthorsWhat about support for application Id ? It is not in the spec yet, but ODL SFC has it.17:58
vikram_I am not sure if i can ask this question now.. how we are planning to implement flow-classifier?17:58
cathy_s3wong: creating another spec duplicating the exact same content will cause more confusion than benefit, just as we were confused and spent so much time inline and offline doing comparison etc.17:59
s3wongcathy_: +1 --- in the context of networking-sfc, it really isn't necessary17:59
cathy_vikram_: let's discuss the implemenation in next meeting17:59
*** auld has quit IRC17:59
*** xingchao_ has quit IRC17:59
cathy_nbouthors: sorry time is up. let's discuss it offline17:59
vikram_cathy_:+117:59
vikram_bye18:00
jwarendtthanks18:00
Brian__bye18:00
s3wongfast one hour18:00
cathy_#agreed the flow classifier will be part of the SFC spec and implemented inside the SFC project18:00
vikram_yes...18:00
nbouthorsbye18:00
amotoki_thanks. I try to be here next week or later. it is a bit late in japan :-(18:00
Mohankumar_bye18:00
cathy_thanks everyone. Bye now.18:00
s3wongamotoki_: good to have you here though!18:00
Swamibye18:00
s3wongThanks. Bye!18:01
vikram_amotoki_: nice to have you here:)18:01
cathy_amotoki_: thanks for joining!18:01
*** jwarendt has quit IRC18:01
cathy_#endmeeting18:01
*** openstack changes topic to "Automatic Task Triggering (Meeting topic: glance drivers)"18:01
openstackMeeting ended Thu Jul  2 18:01:24 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-07-02-17.00.html18:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/service_chaining/2015/service_chaining.2015-07-02-17.00.txt18:01
openstackLog:            http://eavesdrop.openstack.org/meetings/service_chaining/2015/service_chaining.2015-07-02-17.00.log.html18:01
*** Mohankumar_ has quit IRC18:01
*** vikram_ has quit IRC18:02
*** banix has joined #openstack-meeting-418:07
*** padkrish has joined #openstack-meeting-418:07
*** amotoki_ has quit IRC18:09
*** cathy_ has quit IRC18:09
*** Brian__ has quit IRC18:11
*** puranamr has quit IRC18:12
*** puranamr has joined #openstack-meeting-418:13
*** padkrish has quit IRC18:14
*** padkrish has joined #openstack-meeting-418:14
*** padkrish has quit IRC18:19
*** auld has joined #openstack-meeting-418:19
*** jwagner_away is now known as jwagner18:21
*** banix has quit IRC18:29
*** padkrish has joined #openstack-meeting-418:29
*** padkrish has quit IRC18:29
*** padkrish has joined #openstack-meeting-418:30
*** puranamr_ has joined #openstack-meeting-418:33
*** puranamr has quit IRC18:37
*** yamahata has quit IRC18:38
*** auld has quit IRC18:48
*** Sukhdev has joined #openstack-meeting-418:48
*** VanL_ has quit IRC18:49
*** auld has joined #openstack-meeting-418:49
*** dannywilson has joined #openstack-meeting-418:50
*** auld has quit IRC18:50
*** VanL has joined #openstack-meeting-418:54
*** dannywilson has quit IRC18:56
*** dannywilson has joined #openstack-meeting-418:56
*** SumitNaiksatam has joined #openstack-meeting-418:58
*** sdake_ has joined #openstack-meeting-418:58
*** sdake has quit IRC19:00
*** sdake has joined #openstack-meeting-419:01
*** auld has joined #openstack-meeting-419:01
*** marcusvrn has joined #openstack-meeting-419:02
*** ajayaa has joined #openstack-meeting-419:03
*** sdake_ has quit IRC19:04
*** lyarwood has quit IRC19:07
*** lyarwood has joined #openstack-meeting-419:07
*** ajayaa has quit IRC19:12
*** lyarwood has quit IRC19:12
*** lyarwood has joined #openstack-meeting-419:13
*** marcusvrn_ has joined #openstack-meeting-419:14
*** marcusvrn has quit IRC19:17
*** marcusvrn_ is now known as marcusvrn19:17
*** padkrish has quit IRC19:18
*** padkrish has joined #openstack-meeting-419:18
*** kobis has joined #openstack-meeting-419:21
*** padkrish has quit IRC19:23
*** puranamr_ has quit IRC19:25
*** kobis1 has joined #openstack-meeting-419:31
*** kobis has quit IRC19:31
*** puranamr has joined #openstack-meeting-419:32
*** delatte has joined #openstack-meeting-419:34
*** auld has quit IRC19:34
*** auld has joined #openstack-meeting-419:36
*** delattec has quit IRC19:37
*** kobis has joined #openstack-meeting-419:44
*** kobis1 has quit IRC19:44
*** yamahata has joined #openstack-meeting-419:48
*** DericHorn-HP has quit IRC19:53
*** alextricity has quit IRC19:55
*** marcusvrn1 has joined #openstack-meeting-419:59
*** padkrish has joined #openstack-meeting-420:05
*** marcusvrn1 has quit IRC20:09
*** padkrish has quit IRC20:09
*** padkrish has joined #openstack-meeting-420:10
*** padkrish has quit IRC20:15
*** hogepodge has quit IRC20:17
*** hogepodge has joined #openstack-meeting-420:18
*** padkrish has joined #openstack-meeting-420:19
*** singleth_ has joined #openstack-meeting-420:25
*** singlethink has quit IRC20:29
*** puranamr has quit IRC20:31
*** kobis has quit IRC20:35
*** puranamr has joined #openstack-meeting-420:38
*** padkrish has quit IRC20:42
*** padkrish has joined #openstack-meeting-420:42
*** GB21 has quit IRC20:44
*** padkrish_ has joined #openstack-meeting-420:47
*** padkrish has quit IRC20:47
*** Sukhdev has quit IRC20:48
*** auld has quit IRC20:49
*** Sukhdev has joined #openstack-meeting-420:56
*** auld has joined #openstack-meeting-420:56
*** DericHorn-HP has joined #openstack-meeting-420:56
*** padkrish_ has quit IRC21:01
*** padkrish has joined #openstack-meeting-421:02
*** rfolco has quit IRC21:02
*** padkrish_ has joined #openstack-meeting-421:02
*** padkrish has quit IRC21:02
*** jwagner is now known as jwagner_away21:05
*** Rockyg has joined #openstack-meeting-421:08
*** DericHorn-HP has quit IRC21:08
*** auld has quit IRC21:12
*** ddutta has joined #openstack-meeting-421:20
*** carl_baldwin has quit IRC21:25
*** padkrish_ has quit IRC21:27
*** padkrish has joined #openstack-meeting-421:27
*** padkrish has quit IRC21:28
*** padkrish has joined #openstack-meeting-421:28
*** carl_baldwin has joined #openstack-meeting-421:29
*** Rockyg has quit IRC21:31
*** DericHorn-HP has joined #openstack-meeting-421:33
*** VanL has quit IRC21:37
*** sambetts has quit IRC21:39
*** DericHorn-HP has quit IRC21:40
*** sambetts has joined #openstack-meeting-421:42
*** auld has joined #openstack-meeting-421:45
*** GB21 has joined #openstack-meeting-421:46
*** puranamr has quit IRC21:47
*** puranamr has joined #openstack-meeting-421:50
*** rods has joined #openstack-meeting-421:55
*** padkrish has quit IRC22:02
*** padkrish has joined #openstack-meeting-422:05
*** klamath has quit IRC22:06
*** singlethink has joined #openstack-meeting-422:09
*** singleth_ has quit IRC22:12
*** rods has quit IRC22:14
*** puranamr_ has joined #openstack-meeting-422:16
*** puranamr has quit IRC22:19
*** rods has joined #openstack-meeting-422:19
*** puranamr has joined #openstack-meeting-422:21
*** sdake has quit IRC22:22
*** sdake has joined #openstack-meeting-422:22
*** rods has quit IRC22:22
*** DericHorn-HP has joined #openstack-meeting-422:24
*** auld has quit IRC22:24
*** puranamr_ has quit IRC22:24
*** mmedvede has quit IRC22:28
*** puranamr has quit IRC22:28
*** puranamr has joined #openstack-meeting-422:28
*** rods has joined #openstack-meeting-422:29
*** sambetts has quit IRC22:29
*** sambetts has joined #openstack-meeting-422:30
*** puranamr_ has joined #openstack-meeting-422:30
*** puranamr has quit IRC22:33
*** puranamr_ has quit IRC22:35
*** puranamr has joined #openstack-meeting-422:35
*** briancurtin has quit IRC22:36
*** DericHorn-HP has quit IRC22:37
*** puranamr_ has joined #openstack-meeting-422:38
*** andymccr has quit IRC22:38
*** briancurtin has joined #openstack-meeting-422:39
*** puranamr has quit IRC22:39
*** puranamr has joined #openstack-meeting-422:40
*** galstrom is now known as galstrom_zzz22:40
*** dannywilson has quit IRC22:41
*** dannywilson has joined #openstack-meeting-422:42
*** CheKoLyN has quit IRC22:42
*** amit213 has quit IRC22:42
*** puranamr_ has quit IRC22:42
*** sdake has quit IRC22:43
*** mancdaz has quit IRC22:43
*** sdake has joined #openstack-meeting-422:44
*** andymccr has joined #openstack-meeting-422:44
*** mancdaz has joined #openstack-meeting-422:44
*** sdake has quit IRC22:46
*** puranamr has quit IRC22:48
*** puranamr has joined #openstack-meeting-422:48
*** sdake has joined #openstack-meeting-422:50
*** xingchao_ has joined #openstack-meeting-422:51
*** sdake has quit IRC22:51
*** sdake has joined #openstack-meeting-422:52
*** Sukhdev has quit IRC22:56
*** singlethink has quit IRC22:56
*** sdake has quit IRC22:58
*** puranamr_ has joined #openstack-meeting-422:59
*** rharwood has quit IRC23:01
*** puranamr has quit IRC23:03
*** dannywilson has quit IRC23:03
*** puranam__ has joined #openstack-meeting-423:04
*** rharwood has joined #openstack-meeting-423:05
*** aventerav has quit IRC23:07
*** puranamr_ has quit IRC23:07
*** puranam__ has quit IRC23:09
*** puranamr has joined #openstack-meeting-423:10
*** puranamr has quit IRC23:11
*** puranamr has joined #openstack-meeting-423:14
*** puranamr has quit IRC23:14
*** puranamr has joined #openstack-meeting-423:15
*** ddutta has quit IRC23:15
*** puranamr_ has joined #openstack-meeting-423:16
*** radek_ has quit IRC23:17
*** puranam__ has joined #openstack-meeting-423:18
*** puranamr_ has quit IRC23:18
*** puranamr has quit IRC23:19
*** rods has quit IRC23:23
*** padkrish has quit IRC23:24
*** padkrish has joined #openstack-meeting-423:25
*** padkrish has joined #openstack-meeting-423:25
*** rods has joined #openstack-meeting-423:26
*** Sukhdev has joined #openstack-meeting-423:27
*** ddutta has joined #openstack-meeting-423:29
*** sdake has joined #openstack-meeting-423:37
*** rods_ has joined #openstack-meeting-423:40
*** padkrish has quit IRC23:40
*** padkrish has joined #openstack-meeting-423:40
*** carl_baldwin has quit IRC23:40
*** rods_ has quit IRC23:42
*** padkrish_ has joined #openstack-meeting-423:44
*** padkrish has quit IRC23:44
*** Swami_ has joined #openstack-meeting-423:46
*** Swami has quit IRC23:49
*** Swami_ has quit IRC23:57
*** rods has quit IRC23:57
*** rods has joined #openstack-meeting-423:58
*** rods has quit IRC23:58
*** rods has joined #openstack-meeting-423:59
*** ddutta has quit IRC23:59

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