Thursday, 2015-05-28

*** Gavin_Pratt_HP has quit IRC00:01
*** stevelle has joined #openstack-meeting-400:02
*** stevelle has left #openstack-meeting-400:02
*** Sukhdev has quit IRC00:04
*** Sukhdev has joined #openstack-meeting-400:08
*** ivar-laz_ has joined #openstack-meeting-400:14
*** ivar-laz_ has quit IRC00:14
*** salv-orlando has joined #openstack-meeting-400:15
*** daneyon_ has joined #openstack-meeting-400:15
*** ivar-lazzaro has quit IRC00:17
*** daneyon has quit IRC00:18
*** s3wong has quit IRC00:19
*** salv-orlando has quit IRC00:19
*** daneyon_ has quit IRC00:21
*** aduarte has quit IRC00:24
*** Sukhdev has quit IRC00:28
*** tobe has joined #openstack-meeting-400:32
*** tobe has quit IRC00:36
*** puranamr has quit IRC00:39
*** mwang2_ has quit IRC00:47
*** eghobo has quit IRC00:59
*** asselin_ has quit IRC01:02
*** igordcard_ has quit IRC01:12
*** igordcard_ has joined #openstack-meeting-401:12
*** VW has joined #openstack-meeting-401:13
*** tobe has joined #openstack-meeting-401:18
*** fallenpegasus has joined #openstack-meeting-401:26
*** sdake_ has quit IRC01:28
*** markvoelker has quit IRC01:30
*** markvoelker_ has joined #openstack-meeting-401:30
*** Rockyg has quit IRC01:31
*** fallenpegasus has quit IRC01:32
*** VW has quit IRC01:34
*** dims_ has quit IRC01:35
*** VW has joined #openstack-meeting-401:37
*** puranamr has joined #openstack-meeting-401:50
*** sigmavirus24 is now known as sigmavirus24_awa01:50
*** puranamr has quit IRC01:54
*** sarob has quit IRC01:58
*** sbalukoff has quit IRC02:20
*** bharath has quit IRC02:21
*** VW has quit IRC02:26
*** salv-orlando has joined #openstack-meeting-402:37
*** VW has joined #openstack-meeting-402:39
*** yamahata has quit IRC02:42
*** salv-orlando has quit IRC02:42
*** VW has quit IRC02:44
*** VW has joined #openstack-meeting-402:45
*** Sukhdev has joined #openstack-meeting-402:46
*** jckasper has quit IRC03:06
*** jckasper has joined #openstack-meeting-403:07
*** VW_ has joined #openstack-meeting-403:19
*** bharath has joined #openstack-meeting-403:21
*** VW has quit IRC03:22
*** SumitNaiksatam has quit IRC03:24
*** bharath has quit IRC03:26
*** sarob has joined #openstack-meeting-403:28
*** eghobo has joined #openstack-meeting-403:56
*** banix has quit IRC04:15
*** bharath has joined #openstack-meeting-404:23
*** bharath has quit IRC04:28
*** VW_ has quit IRC04:31
*** jckasper has quit IRC04:32
*** tobe has quit IRC04:36
*** sdake has joined #openstack-meeting-404:39
*** fallenpegasus has joined #openstack-meeting-404:42
*** salv-orlando has joined #openstack-meeting-404:42
*** SumitNaiksatam has joined #openstack-meeting-404:43
*** Sukhdev has quit IRC04:45
*** puranamr has joined #openstack-meeting-404:48
*** sdake_ has joined #openstack-meeting-404:50
*** salv-orlando has quit IRC04:53
*** sdake has quit IRC04:54
*** puranamr has quit IRC04:55
*** puranamr has joined #openstack-meeting-404:55
*** puranamr has quit IRC04:58
*** puranamr has joined #openstack-meeting-404:58
*** nkrinner has joined #openstack-meeting-404:59
*** numan has joined #openstack-meeting-405:11
*** puranamr has quit IRC05:15
*** puranamr has joined #openstack-meeting-405:16
*** puranamr has quit IRC05:19
*** puranamr has joined #openstack-meeting-405:20
*** salv-orlando has joined #openstack-meeting-405:23
*** RAMAP has joined #openstack-meeting-405:23
*** puranamr has quit IRC05:23
*** puranamr has joined #openstack-meeting-405:24
*** sarob has quit IRC05:26
*** armax has quit IRC05:27
*** RAMAP has quit IRC05:27
*** puranamr_ has joined #openstack-meeting-405:28
*** puranamr_ has quit IRC05:28
*** puranamr_ has joined #openstack-meeting-405:29
*** puranamr has quit IRC05:30
*** fallenpegasus has quit IRC05:30
*** puranamr_ has quit IRC05:32
*** puranamr has joined #openstack-meeting-405:34
*** matrohon has joined #openstack-meeting-405:39
*** fallenpegasus has joined #openstack-meeting-405:43
*** puranamr has quit IRC05:48
*** matrohon has quit IRC06:04
*** tobe has joined #openstack-meeting-406:04
*** fallenpegasus has quit IRC06:05
*** numan has quit IRC06:07
*** bharath has joined #openstack-meeting-406:12
*** radek__ has joined #openstack-meeting-406:15
*** bharath has quit IRC06:17
*** simon-AS559 has joined #openstack-meeting-406:31
*** numan has joined #openstack-meeting-406:34
*** sbalukoff has joined #openstack-meeting-406:34
*** [1]evgenyf has joined #openstack-meeting-406:34
*** ajayaa has joined #openstack-meeting-406:54
*** simon-AS559 has quit IRC07:00
*** salv-orlando has quit IRC07:00
*** salv-orlando has joined #openstack-meeting-407:00
*** jpekkari has joined #openstack-meeting-407:01
*** sc68cal has quit IRC07:15
*** matrohon has joined #openstack-meeting-407:20
*** simon-AS559 has joined #openstack-meeting-407:26
*** paramite has joined #openstack-meeting-407:26
*** GB21 has joined #openstack-meeting-407:28
*** spredzy|afk is now known as spredzy07:33
*** nmj3e has quit IRC07:35
*** salv-orlando has quit IRC07:38
*** jpekkari has quit IRC07:42
*** jpekkari has joined #openstack-meeting-407:43
*** GB21 has quit IRC07:53
*** simon-AS559 has quit IRC07:57
*** dims_ has joined #openstack-meeting-408:02
*** dims_ has quit IRC08:08
*** eghobo has quit IRC08:08
*** sc68cal has joined #openstack-meeting-408:11
*** simon-AS559 has joined #openstack-meeting-408:16
*** simon-AS5591 has joined #openstack-meeting-408:17
*** simon-AS559 has quit IRC08:21
*** rgerganov has joined #openstack-meeting-408:27
*** salv-orlando has joined #openstack-meeting-408:39
*** salv-orlando has quit IRC08:45
*** sdake has joined #openstack-meeting-408:58
*** bharath has joined #openstack-meeting-409:01
*** sdake_ has quit IRC09:01
*** sdake_ has joined #openstack-meeting-409:04
*** simon-AS5591 has quit IRC09:04
*** bharath has quit IRC09:05
*** sdake has quit IRC09:07
*** markvoelker_ has quit IRC09:16
*** GB21 has joined #openstack-meeting-409:26
*** dims_ has joined #openstack-meeting-409:57
*** salv-orlando has joined #openstack-meeting-410:10
*** markvoelker has joined #openstack-meeting-410:17
*** markvoelker has quit IRC10:23
*** kbyrne has quit IRC10:34
*** sdake_ has quit IRC10:38
*** kbyrne has joined #openstack-meeting-410:41
*** numan has quit IRC10:42
*** smccully has quit IRC10:50
*** jpekkari has quit IRC10:50
*** spredzy is now known as spredzy|afk10:51
*** jpekkari has joined #openstack-meeting-410:54
*** jpekkari has quit IRC10:56
*** jpekkari has joined #openstack-meeting-410:58
*** numan has joined #openstack-meeting-411:00
*** salv-orlando has quit IRC11:12
*** dims_ has quit IRC11:16
*** simon-AS5591 has joined #openstack-meeting-411:16
*** dims_ has joined #openstack-meeting-411:17
*** spredzy|afk is now known as spredzy11:24
*** dims_ has quit IRC11:28
*** dims_ has joined #openstack-meeting-411:28
*** tobe has quit IRC11:30
*** dims_ has quit IRC11:33
*** dims_ has joined #openstack-meeting-411:39
*** tobe has joined #openstack-meeting-411:39
*** amotoki has quit IRC11:45
*** saaasfd has joined #openstack-meeting-411:46
*** saaasfd has quit IRC11:46
*** marcusvrn1 has joined #openstack-meeting-411:52
*** marcusvrn has quit IRC11:55
*** ajayaa has quit IRC12:00
*** markvoelker has joined #openstack-meeting-412:02
*** GB21 has quit IRC12:08
*** GB21 has joined #openstack-meeting-412:10
*** salv-orlando has joined #openstack-meeting-412:12
*** banix has joined #openstack-meeting-412:14
*** ajayaa has joined #openstack-meeting-412:19
*** paramite is now known as paramite|afk12:21
*** paramite|afk is now known as paramite12:23
*** VW has joined #openstack-meeting-412:28
*** ajayaa has quit IRC12:28
*** paramite is now known as paramite|afk12:35
GB21hello12:36
*** banix has quit IRC12:39
*** ajayaa has joined #openstack-meeting-412:40
*** paramite|afk is now known as paramite12:44
*** rods has joined #openstack-meeting-412:50
*** jpekkari has quit IRC12:57
*** evrardjp has joined #openstack-meeting-413:00
*** VW has quit IRC13:01
*** klamath has joined #openstack-meeting-413:01
*** VW has joined #openstack-meeting-413:01
*** klamath has quit IRC13:01
*** klamath has joined #openstack-meeting-413:02
*** VW has quit IRC13:06
*** tobe has quit IRC13:08
*** salv-orlando has quit IRC13:11
*** smccully has joined #openstack-meeting-413:11
*** salv-orlando has joined #openstack-meeting-413:11
*** jckasper has joined #openstack-meeting-413:11
*** bknudson has joined #openstack-meeting-413:19
*** singlethink has joined #openstack-meeting-413:29
*** ChuckC has quit IRC13:32
*** dims_ has quit IRC13:37
*** bnemec has quit IRC13:37
*** dims_ has joined #openstack-meeting-413:38
*** ajayaa has quit IRC13:41
*** bnemec has joined #openstack-meeting-413:42
*** abhishekk has joined #openstack-meeting-413:43
*** [1]evgenyf has quit IRC13:47
*** [1]evgenyf has joined #openstack-meeting-413:47
*** klamath has quit IRC13:49
*** klamath has joined #openstack-meeting-413:49
*** geetika_ has joined #openstack-meeting-413:51
*** GB21 has quit IRC13:54
*** bpoulos has joined #openstack-meeting-413:59
*** ativelkov has joined #openstack-meeting-413:59
*** nkrinner has quit IRC13:59
*** rosmaita has joined #openstack-meeting-414:00
nikhil_khi all14:00
kragnizhi14:00
nikhil_kCourtesy 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, GB2114:00
nikhil_k#startmeeting Glance14:01
openstackMeeting started Thu May 28 14:01:02 2015 UTC and is due to finish in 60 minutes.  The chair is nikhil_k. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: Glance)"14:01
openstackThe meeting name has been set to 'glance'14:01
flaper87o/14:01
kragnizo/14:01
rosmaitao/14:01
bpouloso/14:01
nikhil_kThanks, looks like we've decent turnout soon after the summit.14:02
nikhil_kWe have a short agenda #link https://etherpad.openstack.org/p/glance-team-meeting-agenda14:02
*** sigmavirus24_awa is now known as sigmavirus2414:02
abhishekk0/14:02
* sigmavirus24 apologizes for being late14:02
nikhil_kThanks for joining guys14:03
nikhil_kLet's get started14:03
nikhil_k#topic Request from Docker team14:03
*** openstack changes topic to "Request from Docker team (Meeting topic: Glance)"14:03
nikhil_kWe had a request from Docker team prior to summit to collaborate on #link https://etherpad.openstack.org/p/liberty-fishbowl-magnum-project-ideas14:03
*** TravT_ has joined #openstack-meeting-414:04
nikhil_kMore discussion at #link https://etherpad.openstack.org/p/YVR-ops-containers14:04
ativelkovo/14:04
mfedosino/14:04
*** ivasilevskaya has joined #openstack-meeting-414:04
TravT_o/14:04
ivasilevskayao/14:04
nikhil_kCool, more people coming in.14:05
flaper87I couldn't attend that session but I'll catch up14:05
nikhil_kThanks flaper8714:05
nikhil_k#action everyone: Please go through the links and please share your thoughts related to Glance. If you have concerns/suggestions please bring them up at our meetings.14:05
*** geetika_ is now known as GB2114:05
nikhil_kMoving on14:06
nikhil_k#topic Domain Model14:06
*** openstack changes topic to "Domain Model (Meeting topic: Glance)"14:06
nikhil_kLooks like this was from flaper8714:06
GB21hello!14:06
* nikhil_k hands over the mic14:06
*** sabari has joined #openstack-meeting-414:06
flaper87yeah14:06
flaper87so, it's more like a general note and gathering feedback14:06
jokke_o/14:06
flaper87I'm not a huge fan of the domain model we have but I do understand that planning a change now might be too crazy14:07
flaper87BUT, we do have some areas where we're introducing serious race scenarios that would break HA for glance-api14:07
ativelkovwell, at least we may consider dropping it for v3 if we decide to14:07
flaper87ativelkov: ++14:07
jokke_I don't think it's never too late to get rid of that, but ativelkov please ;)14:07
ativelkovwhat's the connection of domain with races?14:08
flaper87so, I'd like to get consensus on allowing exceptions were we skip the domain model and just do saves to the database14:08
mfedosindomain is too much from Java world I think14:08
nikhil_kativelkov: flaper87 : Can we collaborate on ideas and suggestions on an etherpad?14:08
flaper87yes14:08
flaper87but wait14:08
flaper87let me anser ativelkov14:08
* flaper87 gets a link14:08
flaper87#link https://github.com/openstack/glance/commit/b000c85b7fabbe944b4df3ab57ff73883328f40d#diff-dffa5011f2dd4af675a4075b5c33d4adR25014:08
*** mclaren has joined #openstack-meeting-414:09
mfedosinbtw, do you need an article about organization of domain model?14:09
mfedosinwith examples and pictures14:09
flaper87That deactive method gets the image status, checks with an if, sets it to something else and never saves the new value14:09
*** sdake has joined #openstack-meeting-414:09
* jokke_ thinks that if we get rid of eventlet that would be good timing to refactor the domain model as well if we agree to do so14:09
flaper87instead it just  goes ahead and lets the rest of the domain calls to happen14:09
ativelkovah, got it14:09
TravT_mfedosin: do you have that link?14:09
flaper87That kind of operations should happen atomically14:09
ativelkovAgree14:10
flaper87my proposal for now is, that in cases like this we should just call a function from the db_api and do the update in place14:10
mfedosinTravT_, yes, but ut's in russian14:10
ativelkovmfedosin: lol :)14:10
flaper87I guess doing that meanwhile we get rid of it should be fine14:10
*** sdake_ has joined #openstack-meeting-414:10
* mfedosin needs some time to translate14:10
flaper87it's  not like we're breaking it, just skiping the chain for the sake of safety14:11
ativelkovas far as I understand DM is mostly about the separation of concerns14:11
flaper87it'll end up in more writes, I guess but mmh14:11
flaper87ativelkov: yeah14:11
flaper87thoughts ?14:11
ativelkovbut probably it does not work due to these races14:11
nikhil_kSounds good. Update in place can make things messy if we do not refactor. For example, authZ for admin or not.14:11
ativelkovI think I know another example14:11
jokke_flaper87: sounds like decent workaround, but I hope we don't need to do too many of those or it gets really messy14:11
flaper87I'm happy to do these changes myself but I'd like to avoid suprises on reviews14:11
flaper87jokke_: agreed14:12
ativelkovthe quota thing should be racy as well in this case14:12
nikhil_kyeah14:12
flaper87we've several cases like this14:12
flaper87:(14:12
flaper87that's all I have14:12
flaper87thanks for listening14:12
* flaper87 hands tea toe veryone \_/?14:12
nikhil_kDomain model was introduced in 2012-2013 exactly for such reasons14:12
jokke_nikhil_k: to create race conditions? ;p14:13
ativelkovso, all these things should happen in transactions, and the reads of that transactions should be done with "select for update"14:13
nikhil_kWe have expanded our feature domains a bt broad since, so it/s kinda ironic that this does not scale well.14:13
flaper87ativelkov: indeed14:13
nikhil_kI see14:13
nikhil_kthat has another tradeoff though14:14
flaper87ultimatedly, we should get rid of the DM14:14
flaper87but for now, i think this is a good solution to fix these issues14:14
nikhil_kIf you have multiple select for updates you will have a livelock14:14
flaper87with not such a huge impact in performance14:14
flaper87Last famous words14:14
*** sdake has quit IRC14:14
ativelkovAnd the current v2 implementation is conceptually wrong: at first it reads the objects from DB (and closes the transaction afterwards), builds domain objects, runs some layers of logic - and then flushes the changes into DB in another transaction14:14
ativelkovnikhil_k: yes, livelock14:15
* flaper87 welcomes ativelkov to his hell :D14:15
ativelkovand also Galero have issues with select for update14:15
ativelkovGalera*14:15
nikhil_khmm, I hear they are fixing it14:15
nikhil_kMay be we get to know more on how14:15
sigmavirus24Yeah we can probably talk to the galera team about that14:16
flaper87indeed14:16
flaper87I'd like to take small steps towards the final fix14:16
ativelkovYup, but at least for now Galera is likely to throw DeadLockExceptions under heavy loads if the select for update is used14:16
jokke_I can ping the guys if needed14:16
rosmaitaso what's the general idea here, all status changes should be persisted immediately to the DB?  Any other image fields we need to do this for?14:16
flaper87first fix the immediate races, then we can do refactors14:16
jokke_but galera only solution is not good enough14:16
flaper87rosmaita: all ops that require cmp+swap14:17
nikhil_kumm, flaper87 I think he may mean some properties too14:17
ativelkovyup, quota checks, various kinds of uniqueness checks etc14:17
nikhil_kfor example the dynamic update to some files like prop protection, (may be) conf14:17
rosmaitajust trying to guess how many LOC this will impact14:18
nikhil_krosmaita: me too!14:18
ativelkovjokke_: that's not "galera only", that's about "galera compliant"14:18
nikhil_kthanks for bringing that up14:18
* flaper87 is trying to think about that too14:18
flaper87no idea, tbh.14:18
*** stevelle has joined #openstack-meeting-414:18
flaper87are you going to propose to refactor right away?14:18
ativelkov"select for update" is a generic SQL thing, but specifically on Galera it may fail.14:18
nikhil_kflaper87: how about we share our thoughts on etherpad to see how much of traction is there for a change and everyone opinions are in a single place?14:18
jokke_ativelkov: sure ... just ensuring that we're not trying to solve it with single db vendor specific fix ;)14:18
rosmaitaflaper87: that's what i'm wondering14:18
nikhil_k#link https://etherpad.openstack.org/p/liberty-glance-domain-model14:19
flaper87nikhil_k: rosmaita might be worth putting some extra thought on this14:19
rosmaitawe will have to improve test coverage a lot first, i think14:19
flaper87yup14:19
* ativelkov thinks about writing v3 without the domain at all14:20
* flaper87 would be in favor, FWIW14:20
* jokke_ too14:20
mfedosinI have nothing against domain model actually, but then you have to suggest better solution14:21
nikhil_k#info everyone please share thoughts on DM refactoring and cases when we need and do not need the same: https://etherpad.openstack.org/p/liberty-glance-domain-model14:21
ativelkovWhen we were doing artifacts, domain caused more problems than it solved14:21
nikhil_kThe etherpad link has been added to our liberty etherpad: #link https://etherpad.openstack.org/p/liberty-glance14:21
flaper87ativelkov: did it solve *any* problem? #RandomRant14:22
ativelkovflaper87: well, at least we could do things one-by-one14:22
mclarenI was a bit late, are we talking about refactoring v2 (as well as our v3 work)?14:23
nikhil_kheh14:23
* flaper87 pictures mclaren calling 91114:23
jokke_mclaren: just the guts of it ;)14:23
nikhil_kmclaren: We are just ranting about Domain Model and hoping Mark is not reading this14:23
ativelkovand separate the work between developers: mfedosin was doing DB while ivasilevskaya worked with store: as these were different layers they almost didn't interfere14:23
flaper87ativelkov: no no no, don't say anything in favor of it PLEASE!14:24
flaper87:P14:24
nikhil_kPlease everyone collaborate else, we may soon have another divided team that we can't afford this cycle14:24
flaper87jokes apart, those are good points14:24
flaper87So, etherpad, brainstorm, come back with a plan!14:24
* flaper87 drops mic14:24
ativelkovagreed14:24
* jokke_ prepares to fork glance twisted without DM ;)14:24
nikhil_kor write it in GO14:25
nikhil_k?14:25
* flaper87 read that as: prepare to fork glance and make it use twisted14:25
flaper87RUSTLANG!14:25
kragnizlet's just do the whole thing in haskell14:25
* flaper87 does the rust dance14:25
* flaper87 pushes kragniz down the hill14:25
ivasilevskayamm.. lisp will also do14:25
* flaper87 drinks ivasilevskaya's tea14:26
flaper87ok, really, we can change topic now :D14:26
flaper87I have nothing else to say14:26
flaper87in case you didn't notice it14:26
* nikhil_k laughs at his evil plan to distract everyone from DM and make mclaren a bit happy14:26
flaper87:P14:26
* flaper87 pictures mclaren throwing his pager out of the window into the sea14:27
mclarenlol14:27
flaper87(inside a box with some weight in it)14:27
nikhil_kThanks all for the thoughts on an important topic14:27
nikhil_kMoving on14:27
jokke_flaper87: the sea is bit far away, mut I see it rolling on the parking lot ;)14:27
nikhil_k#topic Search project update14:28
*** openstack changes topic to "Search project update (Meeting topic: Glance)"14:28
TravT_hey everybody. thank you all for the engaging session at the summit and all the discussion we've had on catalog index service this past year.14:28
sigmavirus24flaper87: rust14:28
TravT_we've started the process of launching it as a new project. To start with, we've now got a meeting scheduled for 15:00 on Thursdays on #openstack-meeting-414:28
nikhil_k#link https://etherpad.openstack.org/p/search-team-meeting-agenda14:28
*** prometheanfire has joined #openstack-meeting-414:28
flaper87jokke_: don't doubt mclaren's strenght14:28
kragnizTravT_: so just after this one?14:28
sigmavirus24kragniz: yes14:28
flaper87TravT_: w0000h00000014:28
sigmavirus24TravT_: I'll be there14:29
TravT_yep14:29
TravT_very conveniently turned out to be open14:29
sigmavirus24TravT_: that's probably our fault ;)14:29
TravT_and got it approved in the schedule list by ttx last night14:29
TravT_i'd like to invite any of you that are interested in helping to move this forward to join in!14:29
ativelkovCool, do you start today?14:29
TravT_yep14:29
TravT_today is the first meeting14:29
TravT_main topics will be around the basics of getting everything setup14:30
TravT_including a name14:30
TravT_which we have to clear trademark review.14:30
sigmavirus24Yeah "Searchlight" might conflict with Fox's Searchlight movie studio14:31
TravT_yeah, i'm not clear on trademark law.  my google lawyer skills aren't too effective14:31
* ativelkov remembers three renamings of the project which is currently known as "Murano" - exactly due to copyright issues14:32
mfedosinand Sahara too ;)14:32
TravT_ahh, i didn't remember that ativelkov14:32
TravT_i remembered quantum14:33
kragnizativelkov: copyright shouldn't come into it14:33
*** carl_baldwin has joined #openstack-meeting-414:33
TravT_and flaper87 renamed macaroni ;)14:33
ativelkovkragniz: ehm, I mean trademark. It always confuses me14:33
mfedosinSahara was Savanna previously14:33
*** jroll has joined #openstack-meeting-414:33
mclarenhttp://martinfowler.com/bliki/TwoHardThings.html14:33
sigmavirus24TravT_: because people were getting fat while working on it ;)14:33
TravT_lol14:33
sigmavirus24== mclaren14:33
kragnizativelkov: yeah, trademark != copyright14:33
sigmavirus24Trademark law and Copyright law are two similar yet disjoint things that are baffling to everyone including those who write the laws14:34
TravT_so, this will be one of the opening topics in the next meeting.  would love for you to stick around for it.14:34
TravT_https://etherpad.openstack.org/p/search-team-meeting-agenda14:35
*** armax has joined #openstack-meeting-414:35
TravT_that's all I have at the moment. :)14:35
sabari* thinks Searchlight should have a cool logo like the bat signal * ;)14:35
jokke_++14:35
nikhil_knice imagination sabari14:36
nikhil_kI always get confused with OSX' spotlight14:36
TravT_yeah, anybody have photoshop skills?14:36
kragnizwhatever the name is, it needs to be easy to come up with a cool logo14:36
* kragniz glares at glance14:36
sabarilol14:36
TravT_did you guys get a glance patch at the summit?14:36
kragnizTravT_: inkscape is better for logos14:36
ativelkovwe still need a logo for Glance14:36
jokke_we have really cool one ;)14:36
TravT_kragniz: sounds like you are volunteering14:37
kragnizTravT_: come up with a name first!14:37
jokke_TravT_: you can have Glance's old ... even before we get new one ;)14:37
TravT_i'm hoping searchlight sticks... but we'll see14:37
*** carl_baldwin has quit IRC14:37
nikhil_kWell now that we have a path forward for CIS, I wanted to thank everyone for the reviews and the contribution made to Glance over the past few months. We now have a way for discovering Data Assets incl. metadefs efficiently.14:39
nikhil_kThe vision and mission of Glance will now be partially supported by better searching techniques. It started by TravT_'s brilliant idea of metadefs #link http://specs.openstack.org/openstack/glance-specs/specs/juno/metadata-schema-catalog.html14:40
*** sdake has joined #openstack-meeting-414:40
nikhil_kAnd I don't want to miss out on the rest of the team that helped contribute ideas, code, reviews etc14:40
TravT_Yes, thanks everybody!14:41
nikhil_kIf we have enough data in Glance that people can use to discover and analyze to make magic happen in the cloud, the IAAS industry should rock!14:41
nikhil_kOnly yesterday, we recieved a message from the Auto Scaling team at the Rack; they may have a decent use case for indexing DB.14:42
TravT_mclaren and kragniz had the swift PTL approach them asking for indexing...14:43
nikhil_kThey do need this for instances though and my feeling is that others too so, it makes sense to broaden the scope and help support the search service startng with Glance followed by other important services.14:43
rosmaitaare there other important services? :)14:44
nikhil_k:)14:44
*** sdake_ has quit IRC14:44
nikhil_kAt least, now we have another one14:44
jokke_Designate guys were interested as well14:44
sigmavirus24rosmaita: says the image service product person ;)14:45
nikhil_kAlso one very important that things that happend in Glance in Kilo. We have some good improvements done in the notifications side due to the priority need of CIS. So, thanks everyone who made this happen; we had a win-win case there.14:46
mclarenoff topic, but I've a spec up if anyone has some free review cycles: https://review.openstack.org/#/c/17056414:46
nikhil_kLast but not the least, I think other clouds would be happy to see this service successful as we had some excellent feedback from sigmavirus24 around his discussion with other ops.14:48
*** TravT_ has quit IRC14:48
nikhil_kThat was it from my end.14:49
nikhil_kMoving on as we are a bit short of time..14:49
*** TravT has joined #openstack-meeting-414:49
nikhil_k#topic V3 post-summit follow-up14:49
*** openstack changes topic to "V3 post-summit follow-up (Meeting topic: Glance)"14:49
ativelkovThat was mine14:49
*** ajayaa has joined #openstack-meeting-414:49
nikhil_kThanks, please take the mic14:49
*** aventerav has joined #openstack-meeting-414:50
ativelkovSo, we actually have two patches pending on review, and one has to be updated based on the summit results14:50
ativelkovi.e. we need to rename v0.1 to v3 and put it back to glance-api process14:50
ativelkovbut before we do it I want to discuss one more API-related things14:51
ativelkovin the proposed artifact API we had a common URI section for all the artifacts: i.e. we have /v0.1/artifacts/some_type/...14:51
ativelkovSo, if we now consider it as v3 API: do we still want to have the "artifacts" section or should we drop it?14:52
*** Sukhdev has joined #openstack-meeting-414:52
ativelkovi.e. what is better: /v3/artifacts/images, /v3/artifacts/heat-templates etc or /v3/images, /v3/heat-templates etc?14:53
mfedosinI think we should get rid of 'artifacts' section14:53
sigmavirus24Hm14:53
ativelkovhttps://etherpad.openstack.org/p/glance_v3_API14:53
mclarencould there be a future case where we have a resourse which isn't an artifact?14:53
ativelkov#link https://etherpad.openstack.org/p/glance_v3_API14:53
sigmavirus24That's a good question, and probably a better question for the API-WG14:53
nikhil_kI personally like the second one, for resons of a consistent v3 API14:53
ativelkovmclaren: we have such cases14:53
*** abhishekk has quit IRC14:53
nikhil_k== sigmavirus2414:53
ativelkovfor example, there are schemas14:53
sigmavirus24Also /v3/images, /v3/templates fwiw14:53
ativelkovand there are tasks14:53
nikhil_kmclaren: example14:54
sigmavirus24not heat-templates (please)14:54
nikhil_k?14:54
ativelkovsigmavirus24: the actual name of type-specific section is up to the plugin developers14:54
*** carl_baldwin has joined #openstack-meeting-414:54
sigmavirus24ativelkov: sure, just saying, templates is a nicer route ;)14:54
nikhil_kativelkov: However, we will keep a published list of templates right?14:54
rosmaitaativelkov: how will discovery work? i.e., how do you find out what artifacts are available?14:55
sigmavirus24nikhil_k: confusing that with apps.o.o?14:55
sigmavirus24rosmaita: good point14:55
mclarenif there are non-artifact resources then possibly putting things that have the common artifact behaviour under /artifacts potentially makes sense14:55
sigmavirus24/v3/types might be hard to have as an extension if that's how you discover types14:55
ativelkovso, the etherpad I've linked has some pros and cons mentioned14:55
sigmavirus24I see where mclaren is coming from14:55
mclarenand a get of /artifacts potentially lists all artifacts14:56
rosmaitamclaren: +114:56
ativelkovmclaren: yes, this makes sence14:56
sigmavirus24Yeah I think I'm with mclaren14:56
sigmavirus24Especially since tasks probably can't be considered a plugin type14:56
nikhil_kativelkov: your proposal says that /artifacts will have separate endpoints14:56
sigmavirus24And someone may want to distribute task artifacts (task files) via /v3/artifacts/tasks14:56
nikhil_khow will that discovery proposal work in such case?14:57
ativelkovnikhil_k: separate keystone endpoints, yes14:57
nikhil_kThen there won't really be discovery on Glance, rather all on keystone14:57
*** david-lyle_ has joined #openstack-meeting-414:57
ativelkovnikhil_k: yes, this may cover discoverability issue14:58
nikhil_kHaving it under /v3/<artifact_type> and another call mydomain.org/v3/artifacts-resources can enable discovery14:58
nikhil_knaming can be different14:58
rosmaitaativelkov: you are thinking a separate service catalog entry for every single artifact-type?14:59
nikhil_kyep14:59
nikhil_kBTW, we are almost out of time.14:59
sigmavirus24I'm not sure about that14:59
ativelkovrosmaita: yes, as this was the feedback from def-core according to what I understood from flaper8714:59
nikhil_kWe should continue the discussion on #link https://etherpad.openstack.org/p/glance_v3_API14:59
stevelleshouldn't types discovery happen at /v3/ then14:59
sigmavirus24== nikhil_k14:59
* flaper87 was a bit distracted14:59
ativelkovyup, any feedback is welcome14:59
nikhil_kSorry ativelkov , we can continue this in th next meeting15:00
*** emagana has joined #openstack-meeting-415:00
ativelkovBTW, we may have deeper discussion with API WG - I just need some quick decision now so we can proceed with the commits15:00
nikhil_kHeads up: glance_store release coming out soon15:00
*** smc7 has joined #openstack-meeting-415:00
flaper87w000t15:00
nikhil_kativelkov: please keep us in the loop15:00
nikhil_kThanks all!15:00
*** ongk has joined #openstack-meeting-415:00
kragniznikhil_k: thanks15:00
nikhil_k#endmeeting15:00
*** openstack changes topic to "(Meeting topic: sc)"15:00
openstackMeeting ended Thu May 28 15:00:56 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-05-28-14.01.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-05-28-14.01.txt15:01
nikhil_kTravT: all yours15:01
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-05-28-14.01.log.html15:01
*** Sam-I-Am has joined #openstack-meeting-415:01
TravTthanks nikhil_k15:01
*** Sam-I-Am has left #openstack-meeting-415:01
TravT#startmeeting openstack search15:01
openstackMeeting started Thu May 28 15:01:26 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:01
ativelkovo/ :)15:01
sigmavirus24o/15:01
kragnizo/15:01
*** krykowski has joined #openstack-meeting-415:01
TravTo/ :)15:01
*** fallenpegasus has joined #openstack-meeting-415:01
david-lyle_o/15:01
smc7morning!15:01
nikhil_ko/15:01
rosmaitao/15:02
nikhil_kExciting day!15:02
sigmavirus24"OpenStack Search: The Search for a working OpenStack installation" ;)15:02
david-lyle_lol15:02
*** stevelle has left #openstack-meeting-415:02
krykowskio/15:02
TravTsigmavirus24, let's not get too crazy here15:02
sigmavirus24That'll be airing weekly on Fox after American Idol I think15:02
jokke_o/15:02
TravTallirght, well looks like we have a good crowd!15:03
kragnizsigmavirus24: lol15:03
TravThere's the agenda I proposed: https://etherpad.openstack.org/p/search-team-meeting-agenda15:03
TravTwe officially got this added to the meeting list last night.15:03
nikhil_k\o/15:04
TravTjust under the generic name "search"15:04
TravTso, naming will be an important topic.15:04
TravT#topic Summit Review15:04
*** openstack changes topic to "Summit Review (Meeting topic: openstack search)"15:04
TravTwe had two sessions on this at the summit.15:05
TravTone in the Glance fishbowl and one in the horizon fishbowl15:05
nikhil_kDoes anyone have links handy?15:05
* nikhil_k scutters 15:05
*** sarob has joined #openstack-meeting-415:06
TravTdavid-lyle: do you have that link for horizon/15:06
TravT?15:06
david-lyle_I'll find it, wrong laptop15:06
kragnizthis one? https://etherpad.openstack.org/p/YVR-horizon-performance15:06
rosmaitawaiting for etherpad to respond so i can see if i have the correct link15:06
nikhil_khttps://etherpad.openstack.org/p/catalog-index-service-liberty15:06
TravTthat looks right15:06
TravTnot much was captured on the etherpad I think.15:07
david-lyle_#link https://etherpad.openstack.org/p/YVR-horizon-performance15:07
david-lyle_oops15:07
david-lyle_thanks kragniz15:07
TravTBut overall, my impression was that we had very positive feedback in both sessions.15:07
rosmaitathat was my impression as well15:07
mclarenagreed15:08
ativelkov"Shut up and take my money" comment was awesome :)15:08
TravTativelkov: :)15:08
sigmavirus24thirded15:08
smc7:)15:08
TravTa number of us had side conversations as well15:09
TravTkragniz: mclaren: want to share anything about the conversation with the swift guys?15:09
mclarenum, sure15:10
mclarenthere's been some prior discussion on search for swift, eg see https://etherpad.openstack.org/p/liberty-swift-metadata-search15:10
sigmavirus24Was it "Swift is fast and this will slow us down so, no"?15:10
mclarento quote rosmaita 'swift was built for comfort not for speed' :-)15:10
rosmaitamclaren: +115:11
mclarenbut anyway, John Dickenson (swift PTL) actually brought the topic up (rather than other way around)15:11
mclarenso, I'm not sure how high it is on their list of priorities, but they do seem interested15:11
TravTyeah, it was interesting.  they tried to track us down for that session the next day.15:12
mclarenJust need to find out more about that existing spec, and the degree to which they'd be willing to work with us15:12
smc7that they're adding notifications is a good first step15:12
*** VW has joined #openstack-meeting-415:12
*** Adri2000 has joined #openstack-meeting-415:12
*** Adri2000 has quit IRC15:12
*** Adri2000 has joined #openstack-meeting-415:12
nikhil_kafaik, swift uses lightweigth DBs like sqllite. Wondering what their intent to restructure the scheme here is?15:13
TravTYes, so i think that'll be an area to explore in the coming the weeks.15:13
nikhil_kAlso, these DBs are distributed15:13
nikhil_kLooks like an interesting topic15:13
TravTi also attended the big tent meeting and spoke with a number of TC / board members15:14
TravTit seems that we just need to get a few ducks in a row and then can propose the project to go under openstack governance15:14
TravTwhich leads to the next topic15:14
kragnizTravT: did that show some light on going into stackforge vs straight into openstack?15:15
TravTstraight into openstack15:15
*** VW has quit IRC15:15
kragnizcool15:15
mclarenfwiw my understanding is the swift dbs are just sqlite dbs which are kept in sync by replication15:15
nikhil_kkragniz: straight into openstack has some nice process. That can be found in the governance repo15:15
*** VW has joined #openstack-meeting-415:15
TravTso we might as well jump to that topic.15:15
TravT#topic openstack governance15:16
*** openstack changes topic to "openstack governance (Meeting topic: openstack search)"15:16
TravT#link: http://governance.openstack.org/reference/new-projects-requirements.html15:16
nikhil_kmclaren: yep, though these are file like entities and indexing can be tricky unless we have good connectors to the indexer from file. Update model via notification would help here.15:16
TravTthere are a number of requirements to be considered.15:17
TravTchief among them is openness15:17
*** tsufiev has joined #openstack-meeting-415:17
TravTand from my conversations with people like monty and jay pipes, since we developed this all to date under Glance, we already meet those criteria15:18
nikhil_kI think your proposal covers most if not all of these, TravT15:18
*** pkarikh has joined #openstack-meeting-415:18
TravThowever there are a few things to take care of.15:19
TravTwhich i've started to capture on this etherpad15:19
* nikhil_k is staring at Keystone support15:19
TravT#link https://etherpad.openstack.org/p/liberty-searchlight15:19
TravTand thank to everybody for starting to jump in on it15:19
nikhil_k++15:20
TravTwe proposed the name searchlight initially15:21
TravTbut as you all probably know, we need to consider trademark15:21
david-lyle_namechanges aren't the end of the world, maybe go with searchlight until there is a problem?15:22
TravTSo, on that etherpad, you can put some alternate ideas up15:22
nikhil_k:)15:22
TravTdavid-lyle_: probably not a bad idea.15:22
david-lyle_because without vetting the list, we won't know if an obscure name is ok either15:22
nikhil_kdavid-lyle_: I think that makes sense. There is that small risk of losing some emails on ML until people change their filters but then we all are available on IRC :-)15:23
smc7let's try and get through to the openstack lawyers but if we've not heard by tomorrow just go with searchlight?15:23
mclarenTravT: any idea of lawyer turnaround time on searchlight?15:23
david-lyle_good to have alternatives that could potentially go through review at the same time, so we have a fallback15:23
TravTyeah, so we contacted HP's attorney and it kind of is a black hole.  not sure where it is15:24
nikhil_kCan we tag [all] in the emails for now?15:24
TravTdavid-lyle_: suggested contacting jonathan bryce directly15:24
mclarenTravT: ok (not hugely surprised)15:24
david-lyle_TravT, any success?15:24
TravTi sent private message to him yesterday, but just got an "away from keyboard message"15:24
nikhil_kI doubt if anyone else is looking for this name in stackforge/openstack-big-tent but good to check there too15:24
TravTi will try again after this meeting15:24
*** ativelkov has left #openstack-meeting-415:25
nikhil_kTravT: I know someone who can get us there. So, if no luck we can try that route.15:25
david-lyle_TravT, or go through another foundation employee15:25
sigmavirus24yeah15:25
sigmavirus24VanL is a Foundation person iirc and can probably help research this too15:25
rosmaitasigmavirus24: and he is a lawyer15:26
nikhil_kand he has Law degree too15:26
sigmavirus24I was hoping "can probably help research this too" would imply that ;)15:26
david-lyle_it's only been a day with jbryce, we can probably give it a little more time15:26
*** jwagner_away is now known as jwagner15:26
TravTso do you guys know VanL?15:27
sigmavirus24TravT: sort of? He works for Rackspace15:27
rosmaitawe are all friends & family15:27
sigmavirus24Oh, maybe he's just a defcore person and not a foundation person15:27
TravTokay, how about I reach out the jbryce again right after this meeting, but it couldn't hurt for you guys to check in with VanL as well.15:28
david-lyle_we should move on, there's many ways to move contacting jbryce forward15:28
TravTAnd then how about if we don't have explicit "no" that we go with searchlight for a name and go ahead and create base wiki's and irc room with it?15:29
mclarenso we wait a period of time 'x' and then just start with searchlight?15:29
TravTby end of Friday15:29
TravT?15:29
david-lyle_+115:29
smc7+115:29
mclarensure15:29
sigmavirus24+115:29
nikhil_kTravT: I recommend giving people the weekend to catch up on email15:30
nikhil_kmay be Monday morning ?15:30
TravTthat seems reasonable15:30
TravTso there are a few other items to do before submission15:31
TravT#topic new repo for CIS code15:31
*** openstack changes topic to "new repo for CIS code (Meeting topic: openstack search)"15:31
TravTsmc7 and lakshmiS have been working on this15:31
TravTsmc7 can you give an update?15:31
smc7sure15:31
kragnizI had a look through uk trademarks - https://www.ipo.gov.uk/tmcase/Results/4/EU00914840415:31
smc7like i said in the email, the intent's to get to functional parity with the code in glance, but with references to glance removed15:32
sigmavirus24kragniz: close but no cigar15:32
smc7the code in github now indexes glance images with tests and pep8 compliance. i intend to add metadef support today or tomorrow but then i don't intend to do any changes until we're in gerrit15:32
TravTsmc7, can you give a link?15:33
smc7https://github.com/lakshmisampath/searchlight15:33
smc7so what we'll (hopefully) import into openstack will very closely match what's in glance15:33
sigmavirus24smc7: makes sense15:33
smc7i'd really like to wait til we're in gerrit to comply with the openness model, but people can feel free to start filing bugs etc15:33
TravTyeah, we don't want to do any new work outside of gerrit worfklow.15:34
smc7they just might not get acted on for a bit15:34
david-lyle_keystone support is a requirement15:34
kragnizsmc7: wouldn't it be nice to maintain the current git history?15:34
nikhil_k== david-lyle_15:34
nikhil_kI was surprised15:34
smc7kargniz - it's mostly just one big commit in glance15:34
smc7we do support keystone15:34
david-lyle_have yet to look through the repo15:34
david-lyle_smc7, ok15:34
nikhil_ksmc7: for all APIs? including indexing?15:35
TravTso, remember, we aren't separating metadefs from glance.15:35
kragnizsmc7: okay, I was eyeing up that "Change README to RST format" commit15:35
david-lyle_ah, because it was a separate service before15:35
smc7err.. yes, on all three counts15:35
sigmavirus24TravT: right15:35
nikhil_kvery important point TravT !15:35
*** numan has quit IRC15:36
mclarenis there currently keystone support for the api requests to the CIS port?15:36
smc7yes - but we'll still be indexing metadefs15:36
smc7from e.g. horizon, mclaren? yes15:36
smc7it's very similar to any other openstack API15:36
mclarenok, so keystone support = check15:36
smc7yep15:37
TravTso, i'm not entirely clear how it goes from this github repo to an openstack one.15:37
TravTeven though i asked about a dozen people15:37
TravTthe impression i was given is that they can just import it15:38
TravTdhellman offerred to help15:38
kragnizTravT: there's some import thing where you tell infra where to clone from15:38
smc7ativelkov - do you know the process murano went through?15:38
david-lyle_#link http://docs.openstack.org/infra/manual/creators.html15:38
TravTi think ativelkov dropped, unfortunately15:39
smc7ah, even better15:39
TravTok, we'll need to study that.15:39
david-lyle_but it doesn't explicitly say how to seed the repo15:40
kragnizdavid-lyle_: that's some good documentation!15:40
smc7"If you have an existing repository that you want to import"15:40
david-lyle_infra means business15:40
TravTwe had several people tell us as long as it is in a repo, infra can import.15:40
smc7http://docs.openstack.org/infra/manual/creators.html#adding-the-repository-to-the-ci-system15:40
kragniz`upstream: git://github.com/awesumsauce/<repositoryname>.git`15:40
kragnizin gerrit/projects.yaml15:40
TravTmonty said to not first go into stackforge.15:40
mclarenkragniz: +115:40
smc7yeah, looks like it doesn't matter where it originates15:40
david-lyle_kragniz, right15:40
*** VW has quit IRC15:41
sigmavirus24TravT: I agree with monty15:42
TravThmm... so i wonder if we do that before submitting the governance projects yaml patch.15:42
sigmavirus24TravT: same time maybe?15:42
TravTsigmavirus24: that would make some sense.15:42
kragnizTravT: after the governance projects is merged, I think15:43
nikhil_kI think infra might stick on goverance first (that's a hunch though) they are very particular15:43
TravTok, then we should talk about that15:43
TravT#topic governance repo15:43
*** openstack changes topic to "governance repo (Meeting topic: openstack search)"15:43
TravTon this same page15:43
TravThttps://etherpad.openstack.org/p/liberty-searchlight15:43
david-lyle_you need approval for using the namespace before adding to it15:43
TravTi put a possible draft for what to submit to the projects yaml15:44
TravTI kept the first pass at mission statement very simple.  Most other projects are pretty simple15:45
*** ajayaa has quit IRC15:45
TravTlooks like nikhil_k suggested adding index to it15:45
TravTwhat do you all think?15:45
*** dannywilson has joined #openstack-meeting-415:45
*** dannywilson has quit IRC15:45
nikhil_kYeah, it used to be CIS (C "Index" S) :-)15:45
*** dannywilson has joined #openstack-meeting-415:46
smc7i'm in favor of adding that15:46
TravTCurrent: To provide advanced and scalable search across multi-tenant cloud resources.15:46
TravTPossible: To provide advanced and scalable indexing and search across multi-tenant cloud resources.15:47
david-lyle_does the implementation detail matter in the mission statement?15:47
mclarensimple is good.15:47
nikhil_kCan we quickly discuss pros and cons?15:47
TravTplease15:47
nikhil_kdavid-lyle_: I think sorta yes15:47
TravTdavid-lyle_: you can also look through the other projects mission statements here  https://github.com/openstack/governance/blob/master/reference/projects.yaml15:48
nikhil_kThe reason being, it defined the scope and direction. I was happy to see TravT pointing out in the summit that we are going with ES based search in the presentation.15:48
nikhil_kdefines**15:48
mclarenwe're just indexing and searching openstack service metadata rather than of the documents themselves? (AWS has a search service for searching inside documents like pdf etc)15:49
*** paramite has quit IRC15:49
rosmaitai think a key aspect of the project is the plugins or whatever that will allow indexing of other projects15:49
nikhil_kA few comments that we received in Glance in Kilo were that it was a simple ES proxy, thought that might be a good thing. However, as a separate program we need to be clear and loud about it.15:49
david-lyle_nikhil_k, I agree that ES is the base technology, whether it's important to call that out (shrug)15:49
sigmavirus24mclaren: I believe so15:50
nikhil_kThe API would get defined by it, I think15:50
david-lyle_but adding indexing isn't bad, and mission statements can be altered in time if necessary15:50
rosmaita+1 adding indexing15:50
nikhil_kThat makes me wonder if we should consult API-WG for some API guideline while that happens. I can volunteer to go for that discussion.15:50
TravTregarding ES.  i definitely don't want us to be inventing a new lowest common denominator language.15:50
TravThowever, at best we could support the plugins declaring a type of backend syntax they'll accept15:51
TravTinitially only elastic search15:51
rosmaitaTravT: yes, the potential consumers i have spoken with definitely want ES, not some kind of openstack query language15:51
sigmavirus24I think perhaps we shouldn't plan for that15:51
sigmavirus24We should try to build what we can for a liberty release15:52
smc7yes, far distant future15:52
TravTsigmavirus24: i like that line of thinking15:52
sigmavirus24And in a distant future support other providers than elasticsearch15:52
*** singlethink has quit IRC15:52
nikhil_kTravT: That being the main reason ,for me being pro indexing in mission stmt. We do not want people prosing sessions in summit that have dozens of people who can to reinvent stuff. You can never be sure what the other side of the worlds is thinking15:52
nikhil_kproposing**15:53
TravTok, i like adding indexing to it.15:53
TravTis this enough?15:53
TravTTo provide advanced and scalable indexing and search across multi-tenant cloud resources.15:53
TravTor more specific?15:53
sigmavirus24I'm okay with just that15:53
kragnizTravT: that sounds pretty good15:53
TravTseems we should do a formal vote here to record it.15:53
david-lyle_works for me15:53
smc7yep, good with me15:53
nikhil_k(That was a very ill formed suggestion from me)15:54
TravTanybody know how to make that work?15:54
sigmavirus24TravT: beware, #startvote is the worst15:54
nikhil_kTravT: lgtm15:54
nikhil_k(+1)15:54
kragnizTravT: don't, the voting is broken last I saw15:54
sigmavirus24TravT: #startvote (Question)? Response1, Response2, etc.15:54
sigmavirus24Or something like that15:54
rosmaitai think #startvote doesn't work, but we should get all the votes in one place, so go ahead and do it15:54
sigmavirus24rosmaita: I think OpenStack's fork requires options for it to work15:54
sigmavirus24#help15:55
mclaren+1 (obviously others can comment on the patch when it goes up)15:55
TravT#startvote (ratify mission statement  To provide advanced and scalable indexing and search across multi-tenant cloud resources.) ? yes, no15:55
openstackBegin voting on: (ratify mission statement  To provide advanced and scalable indexing and search across multi-tenant cloud resources.) ? Valid vote options are yes, no.15:55
openstackVote using '#vote OPTION'. Only your last vote counts.15:55
sigmavirus24#vote yes15:55
smc7#vote yes15:55
nikhil_k#vote yes15:55
TravT#vote yes15:55
rosmaita#vote yes15:55
krykowski#vote yes15:55
kragniz#vote yes15:55
mclaren#vote yes15:55
sigmavirus24Is that everyone?15:56
david-lyle_#vote: yes15:56
openstackdavid-lyle_: : yes is not a valid option. Valid options are yes, no.15:56
david-lyle_#vote yes15:56
TravTanybody outstanding?15:56
* david-lyle_ thinks of himself that way15:56
david-lyle_:D15:56
TravT#endvote15:56
openstackVoted on "(ratify mission statement  To provide advanced and scalable indexing and search across multi-tenant cloud resources.) ?" Results are15:56
openstackyes (9): david-lyle_, mclaren, smc7, sigmavirus24, nikhil_k, TravT, krykowski, kragniz, rosmaita15:56
nikhil_k:)15:56
rosmaitahey, it worked!15:56
kragnizwow, it worked15:56
TravTSweet!  we can accomplish great things!  thanks sigmavirus2415:57
sigmavirus24Yw15:57
sigmavirus24kragniz: explicit options15:57
sigmavirus24that's the key15:57
TravTok, so we are about out of time.15:57
nikhil_ksigmavirus24: ++15:57
TravTdo you guys want to startup an IRC room #openstack-searchlight until monday?15:57
mclaren#help15:57
TravTor communicate in glance until then?15:57
sigmavirus24mclaren: doesn't work15:57
kragnizsigmavirus24 for votebot liaison15:57
sigmavirus24TravT: up to y'all15:58
mclarenheh15:58
nikhil_kTravT: glance works until monday15:58
sigmavirus24kragniz: I once read votebot's source.15:58
TravTok, let's do that.15:58
TravTso #action-item TravT follow up with jbryce15:58
TravTmaybe that isn't format?15:58
*** sdake_ has joined #openstack-meeting-415:58
sigmavirus24TravT: just "#action ..."15:58
nikhil_k#action TravT follow up with jbryce15:58
david-lyle_TravT: #action15:58
nikhil_kHoped that worked :D15:58
sigmavirus24like nikhil_k15:58
TravTthanks nikhil_k15:58
david-lyle_what nikhil_k said15:58
TravT#action TravT follow up with jbryce15:59
TravT#action smc7 finish direct port of code to repo15:59
nikhil_kFrom Glance's side15:59
TravTwho else wants actions?15:59
nikhil_klet's please discuss the split out15:59
nikhil_kSO, that people (devs, deployers, OpenStack) are aware15:59
*** sdake has quit IRC15:59
nikhil_kgah15:59
nikhil_kso that*15:59
TravTyeah.15:59
TravTi'm not sure if we'll get kicked out of here16:00
kragnizwe're out of time in here, anyway16:00
*** sdake has joined #openstack-meeting-416:00
* nikhil_k needs a long break16:00
TravTcan we have a follow on discussion Monday?16:00
* nikhil_k will catch up with everyone soon :-)16:00
TravTinformally16:00
nikhil_k++16:00
kragnizTravT: go for it16:00
david-lyle_sure16:00
TravTok.  thanks everybody!16:01
smc7later16:01
nikhil_kTravT: please do incl. [all] tag in ML16:01
TravTok16:01
nikhil_k\o/16:01
TravTreally excited about this effort and this team!16:01
nikhil_k++16:01
*** stevelle has joined #openstack-meeting-416:01
kragniz#openstack-searchlight is lonely, everyone!16:01
nikhil_klol16:01
TravT#endmeeting16:01
*** openstack changes topic to "(Meeting topic: sc)"16:01
openstackMeeting ended Thu May 28 16:01:37 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-05-28-15.01.html16:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-05-28-15.01.txt16:01
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-05-28-15.01.log.html16:01
TravTkragniz, i'll join you there.16:01
TravT;)16:01
*** smc7 has quit IRC16:01
*** Sam-I-Am has joined #openstack-meeting-416:01
*** Sam-I-Am has left #openstack-meeting-416:02
*** sjmc7 has joined #openstack-meeting-416:02
*** Sam-I-Am has joined #openstack-meeting-416:02
Sam-I-Amy meeting time?16:02
sigmavirus24Sam-I-Am: 3 meetings in a row here for me16:02
*** krykowski_ has joined #openstack-meeting-416:02
d34dh0r53cry more noob16:03
dstaneknice16:03
d34dh0r53lol16:03
cloudnullsigmavirus24:  yw16:03
d34dh0r53in the nicest way possible of course16:03
*** sdake_ has quit IRC16:03
sigmavirus24yeah16:03
sigmavirus24sure16:03
dstanekstartmeeting?16:04
cloudnull#startmeeting openstack_ansible_meeting16:04
openstackMeeting started Thu May 28 16:04:52 2015 UTC and is due to finish in 60 minutes.  The chair is cloudnull. Information about MeetBot at http://wiki.debian.org/MeetBot.16:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:04
*** openstack changes topic to " (Meeting topic: openstack_ansible_meeting)"16:04
openstackThe meeting name has been set to 'openstack_ansible_meeting'16:04
cloudnullgood day gents16:05
*** sjmc7 has left #openstack-meeting-416:05
prometheanfireg'day16:05
cloudnull#topic role call16:05
stevelleo/16:05
*** openstack changes topic to "role call (Meeting topic: openstack_ansible_meeting)"16:05
prometheanfireo/16:05
dstaneko/16:05
d34dh0r53 //0\\16:05
*** odyssey4me has joined #openstack-meeting-416:05
odyssey4meo/16:05
*** krykowski has quit IRC16:05
*** bpoulos has left #openstack-meeting-416:05
Sam-I-Ammoo16:06
*** ongk has left #openstack-meeting-416:06
*** rromans has joined #openstack-meeting-416:07
cloudnullso we have no action items from next week16:07
sigmavirus24o/16:07
cloudnullso lets move on .16:07
sigmavirus24cloudnull: we couldn't, it hasn't happened yet16:07
sigmavirus24(action items)16:07
*** mclaren has quit IRC16:08
Sam-I-Amaction items - osad is the bomb diggity16:08
odyssey4meback to the future?16:08
prometheanfirereview spec please :P16:08
cloudnull's/next/last/'16:08
Sam-I-Ami have a spec that needs attention too :/16:08
cloudnull#topic blueprints16:08
*** openstack changes topic to "blueprints (Meeting topic: openstack_ansible_meeting)"16:08
cloudnullhttps://review.openstack.org/#/q/status:open+project:stackforge/os-ansible-deployment-specs,n,z16:08
cloudnull#link https://review.openstack.org/#/q/status:open+project:stackforge/os-ansible-deployment-specs,n,z16:08
*** rosmaita has left #openstack-meeting-416:09
cloudnullfirst up is the gentoo hosts spec16:09
*** svg has joined #openstack-meeting-416:09
* Sam-I-Am taps foot16:09
*** chuckC_ has joined #openstack-meeting-416:09
* sigmavirus24 taps Sam-I-Am 16:09
cloudnullso with that spec we've had a few reviews16:09
*** aduarte has joined #openstack-meeting-416:10
cloudnulland it looks like this may be a good turning point in the spec to work out all of the issues that we'll face with multi distro support.16:10
cloudnullIE what odyssey4me said in the last comment16:10
Sam-I-Ambindep, anyone?16:10
prometheanfireshould that be a seperate spec that I depend on instead?16:10
prometheanfirestep 1, make generic16:11
prometheanfirestep 2, add gentoo support16:11
Sam-I-Ama generic spec makes sense from a framework perspective16:11
cloudnullit does.16:11
Sam-I-Ami'm just dying to make it use rdo packages and ovs :)16:11
prometheanfireyou can be in charge of that16:11
cloudnull# /kick Sam-I-Am16:12
Sam-I-Amlol16:12
Sam-I-Ami know how to get cloudnull riled up16:12
cloudnullthat said there are some technical issues that can come up with dealing with different os types.16:12
cloudnullin a single deployment.16:12
cloudnullin partcular the wheel building process can be incompatible between distros16:13
Sam-I-Amthat sounds like poor life choices16:13
Sam-I-Amwouldnt it be 1 distro per deployment?16:13
*** fallenpegasus has quit IRC16:13
cloudnullespecially in the case where linked libs are being used.16:13
prometheanfireI'm not sure we can know all the badness until we try16:13
cloudnull^ that is true16:13
sigmavirus24Should we set a level of badness that kills this idea?16:13
prometheanfireit'll be an itteritive process16:14
sigmavirus24i.e., if $badness -gt $X16:14
prometheanfiresigmavirus24: if you can quantify badness16:14
cloudnullso from my perspective I hink that it would be best to start with a consistent. IE containers and hosts are the same base os16:14
sigmavirus24Pretty sure there's a scale for that16:14
cloudnullconsistent deployment16:14
prometheanfirecontainers should be abstracted from the host imo16:15
* Sam-I-Am likes consistent deployment idea16:15
cloudnull#link http://ptgmedia.pearsoncmg.com/imprint_downloads/informit/images/articles/mcgraw/072111_mcgrawfig02.jpg16:15
odyssey4meyeah, it may be good to break this into two stages - one for the controller/infra hosts only, with Ubuntu still being deployed on the compute/storage hosts and containers using Ubuntu16:15
cloudnullgentoo deployment , gentoo lxc containers.16:16
odyssey4methe next stage would be to go down into the containers and compute/storage hosts16:16
odyssey4metwo linked blueprints16:16
cloudnullrhel deployment , rhel lxc containers.16:16
prometheanfirehmm16:16
prometheanfireI thought we wanted to avoid multiple container types16:16
*** david-lyle_ has quit IRC16:16
cloudnullprometheanfire:  the good thing here is that the container base image already exists.16:17
cloudnullhttps://images.linuxcontainers.org:8443/images/16:17
Apsu^16:17
prometheanfire40416:17
ApsuI see supporting distros in containers as a base-image issue.16:17
ApsuProvide appropriate base image, everything else is wheels and git16:17
cloudnulluse a real network .16:17
prometheanfirefair enough16:17
prometheanfire443 works :P16:18
prometheanfireneat, we have armhf containers too16:18
Sam-I-Amcan we use docker images?16:18
prometheanfirebeen working on getting openstack keyworded for arm16:18
* Sam-I-Am ducks16:18
ApsuSam-I-Am: *ducker16:18
prometheanfireSam-I-Am: /kick16:18
cloudnull# /kick Sam-I-Am16:18
prometheanfireso, to tie this up16:18
odyssey4mecloudnull what was that tool which openstack-infra suggested at the summit which would handle the different dependant package names?16:19
prometheanfirenew spec for making osad generic, for both containers and hosts16:19
ApsuHost-wise, that's essentially modularizing the distro-specific parts (file locations and package management)16:20
prometheanfireDelorean?16:20
ApsuContainer-wise, imo that should be base-image things16:20
prometheanfireApsu: network config16:20
Apsuprometheanfire: Not our problem.16:20
odyssey4meprometheanfire just one thing though, if openstack-infra doesn't have support for gentoo then we can't hope to support it as we'll have no way to gate it16:20
ApsuWe only use bridges that are already made.16:20
ApsuWe happen to also provide an example config file for Ubuntu16:21
prometheanfireodyssey4me: I'll have an image they can use16:21
ApsuBut that's the deployer's job16:21
Sam-I-Ami think infra only currently has centos and ubuntu?16:21
prometheanfirealready building openstack images, just need to clean it up some16:21
Sam-I-Ami'm guessing cent/rhel would be the most popular option behind ubuntu16:21
odyssey4meprometheanfire you need to organise that with openstack-infra and get a working devstack on it16:21
prometheanfireI assume so as well16:21
ApsuSam-I-Am: Fedora might be more popular, actually. But hey16:21
odyssey4meotherwise for now we can only work with centos/ubuntu16:21
prometheanfireeww, devstack16:22
Apsuodyssey4me: Or takeover the world and replace devstack with our AIOs :D16:22
Sam-I-AmApsu: rpm-based16:22
d34dh0r53Apsu: +116:22
Sam-I-Amfedora is popular, but it is not "enteprise linux"16:22
odyssey4meyeah, the point is that OSAD can't go down the path of trying to add support for something that doesn't have more general openstack support16:22
odyssey4meand we gate in openstack-infra, so that's the first entry-point for any new platform16:22
ApsuSam-I-Am: Yes. Unfortunately most people who want "enterprise linux" also want versions that have software/kernels so old most of the modern features they want out of openstack won't work :P16:23
ApsuBut hey!16:23
prometheanfireodyssey4me: fair enough16:23
*** matrohon has quit IRC16:23
*** eghobo has joined #openstack-meeting-416:23
odyssey4meanyway, if you're prepared to put the work into making room for other distro's then great... it'll pave the way for centos and others16:23
prometheanfirestep 1 can be done now16:24
sigmavirus24odyssey4me: fwiw, the thing you were thinking of is bindep16:24
sigmavirus24mordred can probably explain it well16:24
odyssey4mesigmavirus24 yes, that's the one16:24
prometheanfirewhich is just making osad prepared to be generic (staying with ubuntu/ubuntu)16:24
odyssey4mebindep will be a key tool for the spec - otherwise we'll be maintaining package dependency lists...16:25
cloudnull++16:25
prometheanfirestep 2 relies on infra having os image testing and whatnot16:25
*** singlethink has joined #openstack-meeting-416:25
odyssey4meprometheanfire sounds like you have two blueprints there - one to prep the foundation, another to add support for centos16:25
prometheanfirecentos?16:26
prometheanfirewhat's that?16:26
odyssey4mein the background you can get gentoo images into openstack-ci16:26
prometheanfireI'm not doing that16:26
sigmavirus24prometheanfire: the only other OS people use to deploy openstack?16:26
sigmavirus24prometheanfire: it's pretty easy to add new images according to the infra docs16:26
odyssey4meif the concept is proven on centos, gentoo would be next16:26
* sigmavirus24 is kidding of course16:26
prometheanfireI have users using gentoo hosts16:26
odyssey4meFYI there are a few interested parties with regards to CentOS16:26
prometheanfirethen they can work on it16:27
prometheanfirethat would be a third spec16:27
Sam-I-Ami get a lot of requests for rpm-based distros16:27
odyssey4mealright, then gentoo second - and others can do centos in parallel16:27
prometheanfireif rax wants me to work on it then I'll do both16:27
sigmavirus24Sam-I-Am: centos charges on a revolutions per minute basis?16:27
prometheanfirethis is a my own time thing16:27
Sam-I-Amsigmavirus24: yes, its the new hotness16:27
sigmavirus24interesting16:27
* sigmavirus24 strokes beard16:28
odyssey4meprometheanfire ah, ok cool16:28
cloudnullok so next spec16:28
cloudnullhttps://review.openstack.org/#/c/184726/16:29
cloudnull#link https://review.openstack.org/#/c/184726/16:29
*** TravT has left #openstack-meeting-416:29
Sam-I-Amyes16:29
cloudnullso there has been some interest from vendors to provide vendor functionalty has been a thing.16:30
Sam-I-Amany of the spec devs here?16:30
cloudnulland so OSAD is going to need to come up with some contrib  or extras repo that vendors can contribute to16:31
cloudnull i really dont want vendor roles in tree.16:31
Sam-I-Ammakes sense16:31
cloudnullbut i understand the desire16:31
odyssey4meI'm down with vendors laying the groundwork, but their roles should be in their own repositories and playbooks should be external too.16:31
ApsuSounds like they should make this, then.16:31
cloudnullso i think that OSAD can build upon what has been done in rpc-extras16:31
Sam-I-Amthey should work something like rpc-extras16:32
Sam-I-Amyeah :)16:32
odyssey4meOSAD provides the facility to consume extra roles. The issue at this point is more to do with where to put the playbooks.16:32
stevelleso do we have momentum to merge rpc-extras into osad? :D16:32
cloudnullodyssey4me:  if i pull from what cinder / neutron has been doing for a while now they both have lots of vendor functionality backed in.16:32
cloudnullhowever now they are attemptoing to remove that16:32
cloudnulland pull those extra bits into other repos16:33
cloudnulli think we can do that from the very beginning .16:33
Apsustevelle: Wat? No. Church and state.16:33
odyssey4mecloudnull Sure, much like we should start to use external roles for some of the bits we do in OSAD.16:33
ApsuIMO, clone what rpc-extras is doing and make osad-extras.16:33
cloudnullif plubgrid wants a community supportable distribution of their product in osad i think thats awesome i just dont want it in OSAD proper.16:34
ApsuMake noise about it, let vendors start doing work16:34
ApsuDone16:34
ApsuWe can evolve what that means as we go16:34
odyssey4mecloudnull it sounds like there should be a stackforge repo for the role then16:34
cloudnullodyssey4me:  i agree with the external roles thing, on premiss, i've just not found external roles to be able to provide what we need at present.16:34
cloudnullnot that we couldnt contribute to these other roles to make them better,16:35
odyssey4meso it comes down to something similar to the hosts16:35
cloudnullbut whos to say we need to when our roles work and provide all the things we need.16:35
cloudnullbut back to plumbgrid16:35
odyssey4meOSAD and OpenStack expect the bits outside of OpenStack configs to be there already16:35
odyssey4meie Plumbgrid can do whatever to get their bits deployed, but OSAD needs to facilitate that OpenStack can be configured to use that substructure16:36
cloudnullbut osad is an openstack deployment system. the only thing we expect is that the OS is present.16:36
Sam-I-Amplumgrid :)16:36
Sam-I-Amits a fruit16:36
Sam-I-Amhas anyone seen their playbooks yet?16:37
cloudnullodyssey4me:  ++16:37
odyssey4meSo I figure that they should ensure that OSAD is configurable, but no plumgrid bits should be installed using OSAD directly.16:37
odyssey4meall OSAD should be doing is allowing their drivers to be enabled, and allowing any bits they don't need configured to be disabled16:38
Sam-I-Amwouldnt it work something like run-the-plumgrid-bits which sets things in os-ansible configs that pertain to it? such as... neutron stuffs.16:39
Apsuosad-extras 4 lief16:39
prometheanfireplugin16:39
*** fallenpegasus has joined #openstack-meeting-416:39
d34dh0r53I like the osad-extras, not sure where it will live or what the review/commit process will be though16:41
*** puranamr has joined #openstack-meeting-416:42
cloudnullso im inclined to accept the spec / work until we work out a contributor model for vendors to put there stuff.16:43
cloudnullonce we do that we move the vendor roles into osad-contrib or something similar.16:43
sigmavirus24I don't think osad needs to maintain a contrib repo16:44
odyssey4meby contrib do you mean playbooks and roles sit underneath a subtree?16:44
sigmavirus24Unless we give the contrib people core to only merge stuff on their bits16:44
*** ivasilevskaya has left #openstack-meeting-416:44
*** rsaha has joined #openstack-meeting-416:45
cloudnullsimilar to what neutron has done with the lbaas, vpnaas bits16:45
cloudnullwhich we could give core access to within those repos.16:46
cloudnullwe could also create a vendor-playbooks directory in the main repo16:46
cloudnullwhere they could contribute these extra roles within16:46
odyssey4mecloudnull we could, but then do we exempt those from gate checks and automate their approvals?16:47
*** ajmiller has joined #openstack-meeting-416:47
cloudnullbut telling them to piss off and host their bits elsewhere is not going to help build our community16:47
odyssey4mewhy should we be policing their contributions?16:47
odyssey4me(to their own stuff which only they use)16:47
odyssey4meit's not about sending anyone away, it's just about scoping16:48
cloudnullright. its similar to what we already have with netapp support for cinder.16:48
odyssey4meI don't see why this project should carry bits that it'll never consume and has no idea what to do with16:48
cloudnullits just that we baked that functionality into the cinder roles.16:48
Apsuodyssey4me: That I agree with.16:49
odyssey4menetapp support for cinder is exactly what I'm happy to have in OSAD - configs in OpenStack are facilitated, NetApp stuff is already in-place16:49
cloudnullthe netapp driver is part of core cinder.16:49
*** pkarikh has left #openstack-meeting-416:49
cloudnulland the logic, which we'll never consume, is in our cinder role.16:50
cloudnullwhich is made possible by our support for cinder nfs + netapp.16:50
odyssey4meie we need to ensure that our roles/plays allow any vendor (Cisco/Plumgrid/etc) to emable their driver and configure OpenStack... but we don't need to install/configure Plumgrid's proprietary software or Cisco's properiatary software/switches16:50
Sam-I-Amso...16:51
Sam-I-Amthis sounds like another bigger topic16:51
*** tsufiev has left #openstack-meeting-416:51
Sam-I-Amperhaps a separate item at a future meeting16:51
cloudnullas of now sigmavirus24 and odyssey4me have reviewed the spec. if we're pushing for now, can we -2 the spec?16:52
*** Sukhdev has quit IRC16:52
odyssey4me-2 is too harsh, I'd like to see it adjusted as per my comments16:53
odyssey4me-2 sticks between patch sets16:53
Sam-I-Ami'm still curious about the code16:53
*** simon-AS5591 has quit IRC16:54
sigmavirus24odyssey4me: -2 is probably appropriate though if there are fundamental objections to the spec16:54
cloudnullbut the spec is to provide plumbgrid roles the generifying neutron is being done as part of another spec. if we have no intention on allowing them in then we need to firmly block it. IMO.16:54
sigmavirus24and -2s can be removed16:54
cloudnullso changing gears for the last few minutes.16:55
Sam-I-Am-2 is just do not merge, not do not ever merge16:55
cloudnull#topic open discussion16:55
*** openstack changes topic to "open discussion (Meeting topic: openstack_ansible_meeting)"16:55
Sam-I-Amguess we'll do the config spec later :P16:55
cloudnullSam-I-Am:  yes16:56
d34dh0r53I talked to Alex and he would like to get the ceilometer stuff on the agenda for next weeks meeting16:56
cloudnullwe have only 5 min left.16:56
cloudnullor we can talk more about in the channel.16:56
*** odyssey4me has left #openstack-meeting-416:57
cloudnullI would like to invite "svg" to the core team. but he doesn't quite meet all of the requirements.16:57
cloudnullso i thought i would bring it up here16:57
cloudnullto see if there are any objects.16:57
cloudnullbefore i submit it to the mailing list.16:57
sigmavirus24cloudnull: requirements?16:57
sigmavirus24Is svg not reviewing enough of the rest of the codebase or something?16:58
cloudnullhttps://wiki.openstack.org/wiki/Governance/Approved/CoreDevProcess16:58
cloudnullmostly that he has not had a lot of reviews.16:58
cloudnullhowever has merged code, has been in the channel for some time, and is well versed in ansible16:58
sigmavirus24If we're really concerned about the requirements, we can work with svg to get their review status up16:58
cloudnull+ ceph experience16:59
sigmavirus24Otherwise, I have no objection16:59
stevelleif svg has capacity for some more reviews I have no objection16:59
cloudnullso imo i think he's a good fit, but before i propose it on the ml i thought i'd ask for oppinions here.16:59
cloudnullso if nobody has any? ill send out a note in a bit.17:00
d34dh0r53cloudnull: +117:00
cloudnullother than that, we're out of time.17:00
cloudnullso thanks everyone.17:00
cloudnull#endmeeting17:00
d34dh0r53#agenda ceilometer17:00
Sam-I-Amda17:00
*** openstack changes topic to "(Meeting topic: sc)"17:00
openstackMeeting ended Thu May 28 17:00:37 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-05-28-16.04.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-05-28-16.04.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-05-28-16.04.log.html17:00
d34dh0r53damn17:00
*** Sam-I-Am has left #openstack-meeting-417:00
*** sbalukoff has quit IRC17:04
*** prometheanfire has left #openstack-meeting-417:06
*** krykowski_ has quit IRC17:08
*** krykowski has joined #openstack-meeting-417:08
*** david-lyle_ has joined #openstack-meeting-417:09
*** bgmccollum has joined #openstack-meeting-417:10
*** dannywilson has quit IRC17:11
*** krykowski has quit IRC17:15
*** dannywilson has joined #openstack-meeting-417:18
*** david-lyle_ has quit IRC17:18
*** simon-AS559 has joined #openstack-meeting-417:22
*** simon-AS5591 has joined #openstack-meeting-417:23
*** [1]evgenyf has quit IRC17:24
*** simon-AS559 has quit IRC17:26
*** daneyon has joined #openstack-meeting-417:32
*** daneyon_ has joined #openstack-meeting-417:33
*** sdake_ has joined #openstack-meeting-417:35
*** banix has joined #openstack-meeting-417:36
*** daneyon has quit IRC17:36
*** sdake has quit IRC17:39
*** SumitNaiksatam has quit IRC17:39
*** salv-orlando has quit IRC17:43
*** puranamr has quit IRC17:46
*** salv-orlando has joined #openstack-meeting-417:47
*** spredzy is now known as spredzy|afk17:52
*** puranamr has joined #openstack-meeting-417:54
*** pcarver has joined #openstack-meeting-417:55
*** ivar-lazzaro has joined #openstack-meeting-417:57
*** cdelatte has quit IRC17:58
*** GB21 has quit IRC17:58
*** ivar-lazzaro has quit IRC17:58
*** cdelatte has joined #openstack-meeting-417:58
*** ivar-lazzaro has joined #openstack-meeting-417:59
*** SumitNaiksatam has joined #openstack-meeting-418:00
*** fallenpegasus has quit IRC18:01
*** abhide_ has joined #openstack-meeting-418:04
*** bharath has joined #openstack-meeting-418:04
*** abhide_ has quit IRC18:05
*** s3wong has joined #openstack-meeting-418:06
*** bknudson has quit IRC18:13
*** bknudson has joined #openstack-meeting-418:18
*** slaweq has joined #openstack-meeting-418:19
*** evrardjp has left #openstack-meeting-418:20
*** s3wong has quit IRC18:24
*** s3wong has joined #openstack-meeting-418:24
*** s3wong has quit IRC18:24
*** slaweq_ has joined #openstack-meeting-418:24
*** krtaylor has quit IRC18:27
*** GB21 has joined #openstack-meeting-418:38
*** sjmc7 has joined #openstack-meeting-418:47
*** bgmccollum has left #openstack-meeting-418:55
*** fallenpegasus has joined #openstack-meeting-418:56
*** Sukhdev has joined #openstack-meeting-418:56
*** slaweq has quit IRC19:04
*** asselin_ has joined #openstack-meeting-419:06
*** evrardjp has joined #openstack-meeting-419:14
*** GB21 has quit IRC19:18
*** sdake has joined #openstack-meeting-419:26
*** sdake_ has quit IRC19:29
*** radek__ has quit IRC19:34
*** radek__ has joined #openstack-meeting-419:35
*** sjmc7 has quit IRC19:40
*** slaweq_ has quit IRC19:41
*** ajmiller has quit IRC19:42
*** slaweq has joined #openstack-meeting-419:42
*** krtaylor has joined #openstack-meeting-419:43
*** evrardjp has left #openstack-meeting-419:49
*** puranamr has quit IRC19:50
*** eghobo has quit IRC19:51
*** jckasper has quit IRC19:57
*** matrohon has joined #openstack-meeting-419:59
*** jckasper has joined #openstack-meeting-420:00
*** singleth_ has joined #openstack-meeting-420:00
*** eghobo has joined #openstack-meeting-420:00
*** jckasper has quit IRC20:01
*** jckasper has joined #openstack-meeting-420:02
*** puranamr has joined #openstack-meeting-420:02
*** singlethink has quit IRC20:03
*** daneyon has joined #openstack-meeting-420:05
*** fallenpegasus has quit IRC20:06
*** fallenpegasus has joined #openstack-meeting-420:07
*** daneyon_ has quit IRC20:08
*** rsaha has quit IRC20:21
*** eghobo_ has joined #openstack-meeting-420:24
*** sdake_ has joined #openstack-meeting-420:26
*** eghobo has quit IRC20:27
*** puranamr has quit IRC20:27
*** rods has quit IRC20:28
*** rods has joined #openstack-meeting-420:29
*** sdake has quit IRC20:30
*** puranamr has joined #openstack-meeting-420:31
*** pkoniszewski has joined #openstack-meeting-420:35
*** fallenpegasus has quit IRC20:36
*** s3wong has joined #openstack-meeting-420:42
*** sdake_ has quit IRC20:47
*** daneyon has quit IRC20:48
*** sdake has joined #openstack-meeting-420:49
*** salv-orlando has quit IRC20:49
*** bharath has quit IRC20:54
*** bharath has joined #openstack-meeting-420:54
*** Sukhdev has quit IRC20:56
*** sjmc7 has joined #openstack-meeting-420:58
*** bharath has quit IRC21:07
*** slaweq has quit IRC21:07
*** sdake_ has joined #openstack-meeting-421:11
*** sdake has quit IRC21:14
*** bharath has joined #openstack-meeting-421:16
*** jpeeler has quit IRC21:17
*** jckasper has quit IRC21:45
*** fallenpegasus has joined #openstack-meeting-421:49
*** salv-orlando has joined #openstack-meeting-421:50
*** salv-orlando has quit IRC21:55
*** sdake has joined #openstack-meeting-421:59
*** matrohon has quit IRC22:00
*** sdake_ has quit IRC22:03
*** puranamr has quit IRC22:07
*** pkoniszewski has quit IRC22:09
*** klamath has quit IRC22:09
*** jwagner is now known as jwagner_away22:09
*** salv-orlando has joined #openstack-meeting-422:15
*** marcusvrn1 has quit IRC22:21
*** singlethink has joined #openstack-meeting-422:22
*** fallenpegasus has quit IRC22:22
*** fallenpegasus has joined #openstack-meeting-422:23
*** sdake_ has joined #openstack-meeting-422:23
*** IlyaG has joined #openstack-meeting-422:23
*** singleth_ has quit IRC22:24
*** puranamr has joined #openstack-meeting-422:26
*** ivar-lazzaro has quit IRC22:26
*** ivar-lazzaro has joined #openstack-meeting-422:27
*** sdake has quit IRC22:27
*** ivar-laz_ has joined #openstack-meeting-422:28
*** ivar-lazzaro has quit IRC22:32
*** barra204 has joined #openstack-meeting-422:43
*** bknudson has quit IRC22:45
*** rods has quit IRC22:47
*** singlethink has quit IRC22:48
*** bharath has quit IRC22:51
*** bharath has joined #openstack-meeting-422:51
*** eghobo_ has quit IRC22:57
*** barra204 has quit IRC23:01
*** krtaylor has quit IRC23:05
*** bharath has quit IRC23:05
*** bharath_ has joined #openstack-meeting-423:05
*** bharath_ has quit IRC23:06
*** Sukhdev has joined #openstack-meeting-423:07
*** ajmiller has joined #openstack-meeting-423:11
*** simon-AS5591 has quit IRC23:14
*** aventerav has quit IRC23:15
*** barra204 has joined #openstack-meeting-423:16
*** dims_ has quit IRC23:17
*** dims_ has joined #openstack-meeting-423:20
*** carl_baldwin has quit IRC23:29
*** salv-orlando has quit IRC23:30
*** asselin_ has quit IRC23:35
*** asselin_ has joined #openstack-meeting-423:36
*** sjmc7 has quit IRC23:36
*** eghobo has joined #openstack-meeting-423:37
*** bharath has joined #openstack-meeting-423:38
*** eghobo has quit IRC23:45
*** eghobo has joined #openstack-meeting-423:46
*** krtaylor has joined #openstack-meeting-423:51
*** fallenpegasus has quit IRC23:56
*** fallenpegasus has joined #openstack-meeting-423:56
*** radek__ has quit IRC23:59

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