Thursday, 2015-06-25

*** puranamr has quit IRC00:01
*** geoffarnold has joined #openstack-meeting-400:03
*** geoffarn_ has joined #openstack-meeting-400:04
*** salv-orlando has joined #openstack-meeting-400:05
*** david-ly_ has joined #openstack-meeting-400:06
*** geoffarnold has quit IRC00:07
*** dwalleck has quit IRC00:07
*** david-lyle has quit IRC00:08
*** geoffarn_ has quit IRC00:09
*** puranamr has joined #openstack-meeting-400:10
*** fallenpegasus has joined #openstack-meeting-400:11
*** padkrish has joined #openstack-meeting-400:11
*** salv-orlando has quit IRC00:12
*** dims_ has joined #openstack-meeting-400:14
*** padkrish has quit IRC00:14
*** padkrish has joined #openstack-meeting-400:15
*** padkrish has quit IRC00:16
*** padkrish has joined #openstack-meeting-400:16
*** dims has quit IRC00:16
*** padkrish has quit IRC00:16
*** catherineD has joined #openstack-meeting-400:17
*** buchi has joined #openstack-meeting-400:17
*** salv-orlando has joined #openstack-meeting-400:21
*** puranamr has quit IRC00:22
*** salv-orlando has quit IRC00:27
*** puranamr has joined #openstack-meeting-400:31
*** harshs has joined #openstack-meeting-400:31
*** padkrish has joined #openstack-meeting-400:34
*** puranamr has quit IRC00:37
*** puranamr has joined #openstack-meeting-400:39
*** geoffarnold has joined #openstack-meeting-400:41
*** puranamr has quit IRC00:42
*** padkrish has quit IRC00:42
*** xingchao has joined #openstack-meeting-400:44
*** nzhou has joined #openstack-meeting-400:54
*** tobe has joined #openstack-meeting-400:56
*** sigmavirus24 is now known as sigmavirus24_awa00:58
*** dwalleck has joined #openstack-meeting-400:59
eglute#startmeeting DefCore01:00
openstackMeeting started Thu Jun 25 01:00:25 2015 UTC and is due to finish in 60 minutes.  The chair is eglute. Information about MeetBot at http://wiki.debian.org/MeetBot.01:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.01:00
*** openstack changes topic to " (Meeting topic: DefCore)"01:00
openstackThe meeting name has been set to 'defcore'01:00
hogepodgeo/01:00
*** geoffarnold has quit IRC01:00
egluteHello Everyone! Raise your hand if you are here and include time zone.01:00
egluteo/ CST01:01
hogepodgeo/ PDT01:01
markvoelkero/ EDT01:01
*** amotoki has joined #openstack-meeting-401:01
catherineDo/PDT01:01
dwallecko/ CST01:01
hogepodgeagenda #link https://etherpad.openstack.org/p/DefCoreFlag.501:01
egluteRob said he won't be able to attend today, so if anyone else wants to chair the meeting with me let me know!01:02
eglute#chair hogepodge01:02
openstackCurrent chairs: eglute hogepodge01:02
eglute#topic agenda01:03
*** openstack changes topic to "agenda (Meeting topic: DefCore)"01:03
eglutedo we have enough people attending the meeting?01:03
markvoelkereglute: you mean in general or in this particular timeslot?01:04
eglutefor this evening01:04
eglutei counted 5 :(01:04
markvoelkerI think we have enough to do useful things.01:04
nzhoupls also count me :)01:04
*** Rockyg has joined #openstack-meeting-401:05
eglutewelcome nzhou! what time zone are you in?01:05
*** nzhou has left #openstack-meeting-401:05
*** amotoki has quit IRC01:05
* markvoelker reminds folks that we're supposed to review whether this meeting schedule is working out during the Flag.7 meeting on July 801:06
*** nzhou has joined #openstack-meeting-401:06
nzhouGMT+8 :)01:06
Rockygo/01:06
egluteI agree markvoelker we can get enough stuff done! we do have agenda on the etherpad. do you want to tackle it in order or start with more pressing items?01:06
markvoelkereglute: the first several items should be pretty short I think01:07
hogepodgeI generally try to do things in order01:07
eglute#topic mid-cycle planning01:07
*** openstack changes topic to "mid-cycle planning (Meeting topic: DefCore)"01:07
eglutewe have set the date last week, right now Rob is waiting to hear on confirmation for the space.01:08
egluteif we don't hear back, we will work on location B, which most likely be Rackspace Austin office01:08
markvoelker#info Still waiting on venue confirmation for July 29-30 midcycle meetup01:09
Rockygthat could be a tight fit01:09
egluteRockyg what do you mean?01:10
egluteIn terms or planning, or having space?01:10
Rockygspace01:10
RockygDefcore has become much more popular01:10
hogepodgerax has loads of space in the Austin office01:10
hogepodge(at least afaik from my last visit there)01:11
eglutewe have two offices there too... yes, it is pretty big01:11
hogepodgeFoundation offices would be much tougher. It was tight last time, and sure to be much tighter this time.01:11
markvoelkerI'm not worried about space...we had 10 people reply to the Doodle01:11
eglutefrom the doodle, it did not appear that we would get too many people attending. Though I am sure a lot of rackers will attend if it is there01:11
eglutemarkvoelker agree! i would be surprised if we get 20 in person01:12
markvoelkerAnd a couple of those said they weren't coming or were going to be remote IIRC01:12
*** harshs has quit IRC01:12
markvoelkereglute: before we move on from midcycle planning, does someone have an AI to draft an agenda?  Don'01:12
markvoelkert think we need to do that here, but it wants doing.01:12
Rockygoops I saw rackspace and thought foundation - which is tiny01:13
eglutemarkvoelker yes, I was thinking we need to start agenda, but thought it might be a bit early still01:13
egluteRockyg yes, foundation office is very cozy!01:13
markvoelkereglute: I'm thinking now is a good time to start drafting.  We're only about 4 weeks away, right?01:14
egluteif other people think that we should start working on agenda now, we can start etherpad.01:14
egluteyes, only 4 weeks, but I was thinking we might resolve some issues in these meetings01:14
egluteI am ok with starting early too01:15
markvoelkereglute: +1 to starting soon.  I've got a couple of things to add to a prospective agenda.01:15
eglute#action eglute start etherpad for mid-cycle agenda01:15
*** DericHorn-HP has joined #openstack-meeting-401:16
egluteready for next topic?01:16
markvoelkereglute: thanks.  Also, for travel planning purposes: I presume we're planning to use the full day both days?  E.g. 9-5 or something?01:16
egluteyes, I would think so01:16
hogepodgemarkvoelker: We had a full agenda last time, so I would hope 2 full days01:17
markvoelkerExcellent.  Ok, next topic!01:17
eglutealso, Foundation Board has a meeting the day before, so the board members will be there early01:17
eglute#topic capabilities subdivision01:17
*** openstack changes topic to "capabilities subdivision (Meeting topic: DefCore)"01:17
eglute#link https://review.openstack.org/#/c/194975/101:17
eglutethank you hogepodge for starting this, i think it is still work in progress, correct?01:18
*** wojdev has quit IRC01:18
markvoelkerhogepodge: Haven't had time for more than a cursory look at this today, sorry.  Will try to spend more time on it tomorrow or Friday.01:18
*** harshs has joined #openstack-meeting-401:19
hogepodgeIt's based off of the work that VanL and catherineD have been doing in the google sheet.01:19
hogepodgeThat's where the json file comes from01:19
hogepodgeThere's a bug in the name, and dwalleck has some good points on the categorization and tests01:19
dwalleckI hopefully didn't brain dump too much feedback, but I still have a bit more to poke around through01:20
*** mickeys has quit IRC01:20
* dwalleck spends way too much time looking at tests01:20
hogepodgePlus the descriptions could be better.01:20
eglutehogepodge dwalleck is it ready to be reviewed?01:21
hogepodgeSince the json is generative, anything that can go back to the capabilities json file will help to reduce the hand-editing of the next.json file01:21
markvoelkerdwalleck: thanks for having a look.  hogepodge: might be useful to have Catherine look at this too, I'll add her01:21
catherineDdwalleck: Thanks for the suggestion on the categorization and tests ... so if we are going to make some changes ... will we start with the spreadsheet?01:21
hogepodgeOne thing to note is that I'm just capturing existing capabilities/tests.01:21
hogepodgeSo refactoring the current state. I know that Van wants to add a lot more tests.01:21
catherineDwe should decide on which is the source ...01:21
hogepodgeAlso, zehicle had a good point about how we keep information on removed tests. Maybe a new category in the next.json file that lists them for reference.01:22
markvoelker+1 on limiting this change to refactoring current state01:22
eglutesounds like we should finish with the refactoring and then add new tests separately?01:22
hogepodgeeglute: that's what I was thinking01:23
dwalleckthat might be easier01:23
catherineDeglute: +101:23
eglutethank you hogepodge01:23
markvoelkereglute: yes.  We have a lot of work to do on adding tests and expect we'll spend some time on that in Austin. =)01:23
*** puranamr has joined #openstack-meeting-401:23
hogepodge#link http://lists.openstack.org/pipermail/defcore-committee/2015-June/000869.html01:23
eglutemarkvoelker true!01:23
markvoelkerOk, so action is for all of us to review this....anything else on that topic?01:24
*** xingchao has quit IRC01:24
markvoelker#action Everyone please review https://review.openstack.org/#/c/194975/01:24
eglute#link midcycle ehterpad for planning purposes: https://etherpad.openstack.org/p/DefCoreFlag.MidCycle01:25
egluteagree on need time to review it.01:26
eglutenext topic?01:26
eglute#topic review hacking file01:26
*** openstack changes topic to "review hacking file (Meeting topic: DefCore)"01:26
eglute#link https://review.openstack.org/#/c/188661/601:27
eglutewe had action item from the last meeting for everyone to review it01:27
markvoelkereglute: actually https://review.openstack.org/#/c/188661/7 now.  Rob added a new patchset earlier today (in lieu of purp I guess?)01:27
egluteoh sorry, took the link from etherpad01:28
eglute#link https://review.openstack.org/#/c/188661/701:28
*** sdake has joined #openstack-meeting-401:28
*** fallenpe_ has joined #openstack-meeting-401:29
eglutehas everyone had a chance to look at it?01:29
*** sdake_ has joined #openstack-meeting-401:29
markvoelkereglute: since that patchset is so new (just uploaded this morning) I don't think most of us have had a chance to look at it much yet.01:29
egluteok, so will have an action item for everyone to look it over01:30
hogepodgeaside from whitespace issues it's a good start01:30
eglute#action Everyone review and provide feedback https://review.openstack.org/#/c/188661/701:30
egluteare there any points that people would like to discuss now?01:30
markvoelkereglute: I think we still haven't settled the security question01:31
hogepodgeI'm actually a bit confused by the language and what it's trying to convey01:31
RockygI had reviewed it last week (but wasn't signed in)  This is much clearer around D40401:31
markvoelkerRob said he wanted a security clause, but I actually don't see one in the latest patchset.01:31
*** DericHorn-HP has quit IRC01:31
*** fallenpegasus has quit IRC01:32
markvoelkerBut actually since Rob isn't able to be here tonight maybe we should just continue that discussion in gerrit.....01:32
eglutemarkvoelker you are right, I thought it was included. yes, gerrit comments would be great01:32
markvoelkereglute: ok, so AI for folks to review it and move on?01:33
egluteRockyg i really like 40401:33
*** sdake has quit IRC01:33
eglutemarkvoelker yes, i already posted AI01:33
eglute#topic strategic test planning01:34
*** openstack changes topic to "strategic test planning (Meeting topic: DefCore)"01:34
eglute#link http://lists.openstack.org/pipermail/defcore-committee/2015-June/000818.html01:34
markvoelkerhogepodge: to me this feels like a thing that would well benefit from some face-to-face discussion in Austin, though I'm happy to continue commenting via email in the interim01:35
hogepodgetopic kind of fell flat with the nova/glance discussions going on.01:35
hogepodgeI would like to get a sense of how we can start matching tests up to APIs and give guidance to devs as to what defcore means for interop01:35
*** david-ly_ is now known as david-lyle01:36
hogepodgehappy to wait to f2f on this01:36
dwalleckhogepodge: as in a list of API request a given test makes?01:36
*** s3wong has quit IRC01:36
hogepodgedwalleck: yes, but also what we really want to support.01:37
eglutehogepodge I think it might help if it was an issue in gerrit, what do you think?01:37
egluteget some discussion that way, and finish in f2f01:37
Rockygdwalleck:Yeah.  Essentially a test coverage/distribution/case analysis and see how we can create a plan and layout that is more effective (from my perspective)01:38
hogepodgeIf a dev wants to boot a machine with a public IP, what's the interoperable way to do that, for example01:38
markvoelkerhogepodge: the developer community <-> DefCore relationship is actually one of the most interesting parts of this I think.  Whatever happened to the idea of colocating DefCore and QA midcycles?01:39
dwalleckI've been doing some sanity checking over the tests. There might be a way to generate the actual list of requests per test so you can see it step by step01:39
RockygUser centric use/test cases that translate into the Api work flow01:39
eglutemarkvoelker co-location didnt work out because QA midcycle was too late/not set01:39
hogepodgedwalleck: Tempest logs it, from what I gather01:39
dwalleckRockyg: +1 to user test cases01:39
hogepodgedwalleck: or it can01:39
markvoelkereglute: Bummer, thought that might be the case.01:39
dwalleckhogepodge: It does, but it doesn't isolate it per test case I think. There might be something I missed01:40
markvoelkerI see a big part of this initiative as needing some buy-in from the Tempest folks, for example.  Would be neat if we could set an agenda early enough that we could invite some of them in for that part of the dicussion01:40
eglutemarkvoelker i think it is in the meeting notes somewhere, I do not remember which meeting though. 2 or 3?01:40
Rockygdwalleck: maybe you, me and Ievgenia can get together on IRC and plan something out01:40
*** mitchjameson has quit IRC01:40
eglutemarkvoelker: good idea. https://etherpad.openstack.org/p/DefCoreFlag.MidCycle01:41
dwalleckRockyg: sounds good to me!01:41
Rockyghogepodge: the logs only capture what is logged.  The APIs are currently incosistent on reporting. and events are almost totally missed01:41
hogepodgeLooking at the qa meeting logs I'm not seeing much discussion on mid cycle yet01:42
hogepodgethere are full logs and abbreviated logs of the meetings01:42
Rockygdwalleck: you've been digging in more.  Wanna put together a strawman we can start with?  We'll send out email on Defcore list for that irc meet01:43
dwalleckRockyg: I'm hoping that should be fixable. They are working from one base rest client, so there's a solid injection point. It just has to be used consistently, which is maybe something we can help with01:43
egluteRockyg dwalleck i think it would be great if you could do that01:43
markvoelkerhogepodge: no worries, if we can alert those folks to when we'll be talking about it in Austin we could potentially get them to join us via Hangout or whatever (or in person, even).  Would be good to hear from them on this.01:43
Rockyghogepodge: too many logs;-) I was talking test run logs01:44
* markvoelker notes we're down to 15 minutes remaining01:44
Rockygdwalleck: ++ I'm driving the log improvement effort.  Nuff said on this.  Next topic?01:44
dwalleckRockyg: Sure, can do.01:45
dwalleckThat makes it easy then :)01:45
*** rfolco has quit IRC01:45
hogepodgeRockyg: I have an engineer looking at capturing the api information, so it's a priority to figure it out01:45
eglute#action Rockyg dwalleck work together on tests and logs01:45
eglute#topic flagged tests01:45
*** dims_ has quit IRC01:45
*** openstack changes topic to "flagged tests (Meeting topic: DefCore)"01:45
*** ivar-lazzaro has joined #openstack-meeting-401:46
*** harshs_ has joined #openstack-meeting-401:46
eglute#link https://review.openstack.org/#/c/189927/01:46
eglutethis one is still from last week in our notes01:47
*** ivar-lazzaro has quit IRC01:47
markvoelkereglute: On this one I think the big question was just whether we go ahead and flag it or wait and see if the fixes upstream land01:47
hogepodgeI'd like to see if that can be cleared without flagging again since a fix is in progress01:47
hogepodgeBut if we can't wait then I'm ok with flagging01:47
*** ivar-lazzaro has joined #openstack-meeting-401:48
eglutehogepodge yes, you are right.01:48
markvoelkerIf we have somebody waiting for logo certification that needs this, we should flag it (IMO).  The remaining upstream fix looks like it could be a while yet.01:48
markvoelkerBut if it's not actually bothering anyone, no real harm either way01:48
* markvoelker notes the remaining patch has been active since March but hasn't yet attracted a +2, so could be a while yet.01:49
*** harshs has quit IRC01:49
*** harshs_ is now known as harshs01:49
hogepodgeI can try to poke on it01:50
*** dims has joined #openstack-meeting-401:50
eglutefor certification, people can still certify on the previous defcore cycle as well.01:51
markvoelkereglute: I'd hate to force somebody back to an old version for something that's still broken upstream though.01:51
eglutehogepodge are you getting any requests that are held because of the flagged tests?01:52
eglutemarkvoelker yes, not ideal01:52
hogepodgeno01:52
Rockygknock on wood01:52
markvoelkerE.g. ideally we want lots of people using the same Guideline so we know we've actually got some level of interoperability01:52
hogepodgeI only have one pending review.01:52
egluteok, so not an issue now, hogepodge  please raise it if it comes up01:53
hogepodgeI can report back next week and we can make a decision.01:53
catherineDhogepodge: the only spec with flagged tests right now is 2015.0401:53
markvoelkercatherineD: just the thing I was going to bring up next =)01:53
eglutethank you hogepodge01:54
hogepodgeTo start I'd like us to remove the tests that are flagged and won't be part of the standard01:54
hogepodgeBut that also means considering adding a new field of permanently removed tests, which I think would be good to prevent test/flag churn.01:54
hogepodgeI'm also ok with not waiting for fixes too.01:55
egluteok, time check: 5 min. next topic?01:56
*** dontalton has quit IRC01:56
markvoelkerhogepodge: in related news, we have no flags in 2015.05 even though we know we probably should.  I'll put up some patches for that this week.01:56
catherineDsince 2015.05 is the only spec for Kilo, without flagged tests in 2105.05 ... we won't be able to certify Kilo01:56
hogepodgeCan we have an action for everyone to start reviewing the flagged changes?01:56
eglute#action Everyone start reviewing flagged changes01:56
markvoelkercatherineD: agreed, was just discussing this w/hogepodge earlier in the week.  We're behind on some housekeeping and I'll start working on that this week01:57
hogepodgeparticularly for tests that we want to remove flags on. I'd like for those who were running into troubles to check to see if it's ok to remove the flags01:57
hogepodge(I removed my -1 on the ssh tests)01:57
eglute#topic capabilities review01:57
*** openstack changes topic to "capabilities review (Meeting topic: DefCore)"01:57
eglutewe had not reviewed capabilities yet in IRC meeting, do you think we need a separate meeting?01:58
* markvoelker throws in a quick promo for https://review.openstack.org/#/c/193727/ while we're talking housekeeping01:58
egluteI think we always run out of time01:58
hogepodgemarkvoelker: I can review my patches to target 05 too01:58
hogepodges/review/revise01:58
markvoelkereglute: Also a thing I've been thinking about.  So far the combined meeting hasn't really allotted any time, but we are a bit early yet accorindg ot the 2015A timeline01:59
markvoelkerI think maybe we just need to set aside some time in the next couple of meetings to divvy up the work of identifying new capabilities amongst ourselves.01:59
eglutecatherineD Rockyg hogepodge dwalleck what do you think?01:59
eglutemarkvoelker i think that could work too02:00
dwalleckThat might be a good idea so we have the time to focus02:00
markvoelkerThen later we can converge with patches in gerrit and add contentious ones to the agenda here.  If we're spending a lot of time on that, we'll break out a meeting.02:00
catherineDagreed02:00
eglutewould it be helpful to start an email thread so people start reviewing?02:00
RockygYeah.  That sounds possible.  I think we will eventually need a separate meeting to wrap it up, though.02:01
egluteRockyg I think you might be right02:01
eglutewe are once again out of time- anything else you want to discuss while we are here?02:02
eglutethank you everyone!02:03
eglute#endmeeting02:03
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"02:03
openstackMeeting ended Thu Jun 25 02:03:42 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)02:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/defcore/2015/defcore.2015-06-25-01.00.html02:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/defcore/2015/defcore.2015-06-25-01.00.txt02:03
openstackLog:            http://eavesdrop.openstack.org/meetings/defcore/2015/defcore.2015-06-25-01.00.log.html02:03
Rockygthanks all!02:03
*** dims has quit IRC02:04
*** catherineD has left #openstack-meeting-402:06
*** puranamr has quit IRC02:09
*** dims has joined #openstack-meeting-402:10
*** DericHorn-HP has joined #openstack-meeting-402:11
*** DericHorn-HP has quit IRC02:12
*** sdake has joined #openstack-meeting-402:13
*** DericHorn-HP has joined #openstack-meeting-402:14
*** dwalleck has quit IRC02:17
*** sdake_ has quit IRC02:17
*** DericHorn-HP has quit IRC02:17
*** puranamr has joined #openstack-meeting-402:18
*** Rockyg has quit IRC02:22
*** puranamr has quit IRC02:27
*** yamahata has quit IRC02:28
*** puranamr has joined #openstack-meeting-402:28
*** salv-orl_ has joined #openstack-meeting-402:29
*** armax has joined #openstack-meeting-402:32
*** fallenpe_ has quit IRC02:32
*** sankarshan_away is now known as sankarshan02:34
*** salv-orl_ has quit IRC02:34
*** mitchjameson has joined #openstack-meeting-402:43
*** mestery has joined #openstack-meeting-402:44
*** mestery has quit IRC02:57
*** mestery has joined #openstack-meeting-402:57
*** dims has quit IRC02:58
*** Sukhdev has joined #openstack-meeting-403:01
*** amotoki has joined #openstack-meeting-403:02
*** amotoki has quit IRC03:06
*** harshs has left #openstack-meeting-403:06
*** harshs has joined #openstack-meeting-403:12
*** amit213 has quit IRC03:12
*** amit213 has joined #openstack-meeting-403:13
*** xingchao_ has joined #openstack-meeting-403:13
*** harshs has left #openstack-meeting-403:13
*** xingchao_ has quit IRC03:18
*** fallenpegasus has joined #openstack-meeting-403:25
*** tobe has quit IRC03:26
*** puranamr has quit IRC03:26
*** puranamr has joined #openstack-meeting-403:33
*** puranamr has quit IRC03:35
*** puranamr has joined #openstack-meeting-403:35
*** dannywil_ has joined #openstack-meeting-403:36
*** tobe has joined #openstack-meeting-403:39
*** dannywilson has quit IRC03:40
*** dannywil_ has quit IRC03:40
*** ivar-lazzaro has quit IRC03:42
*** harshs has joined #openstack-meeting-403:43
*** puranamr_ has joined #openstack-meeting-403:47
*** puranamr has quit IRC03:47
*** diga has quit IRC03:57
*** sarob has quit IRC03:57
*** jckasper has quit IRC04:01
*** amotoki has joined #openstack-meeting-404:10
*** mestery_ has joined #openstack-meeting-404:19
*** mestery has quit IRC04:19
*** puranamr has joined #openstack-meeting-404:21
*** puranamr_ has quit IRC04:21
*** fallenpegasus has quit IRC04:26
*** fallenpe_ has joined #openstack-meeting-404:26
*** harshs has quit IRC04:27
*** DericHorn-HP has joined #openstack-meeting-404:28
*** puranamr_ has joined #openstack-meeting-404:29
*** puranamr has quit IRC04:29
*** fallenpe_ has quit IRC04:31
*** ajmiller has quit IRC04:32
*** puranamr_ has quit IRC04:34
*** puranamr has joined #openstack-meeting-404:34
*** mitchjameson has quit IRC04:35
*** lazy_prince has joined #openstack-meeting-404:39
*** salv-orlando has joined #openstack-meeting-404:41
*** sarob has joined #openstack-meeting-404:44
*** sarob has quit IRC04:47
*** sarob has joined #openstack-meeting-404:47
*** salv-orlando has quit IRC04:47
*** bobmel has joined #openstack-meeting-404:49
*** puranamr has quit IRC04:50
*** puranamr has joined #openstack-meeting-404:51
*** sarob has quit IRC04:57
*** sarob has joined #openstack-meeting-404:57
*** Sukhdev has quit IRC05:01
*** dannywilson has joined #openstack-meeting-405:07
*** mestery_ has quit IRC05:09
*** puranamr_ has joined #openstack-meeting-405:10
*** puranamr has quit IRC05:13
*** sarob has quit IRC05:13
*** sarob has joined #openstack-meeting-405:14
*** irenab has joined #openstack-meeting-405:14
*** sarob has quit IRC05:15
*** dwalleck has joined #openstack-meeting-405:17
*** puranamr_ has quit IRC05:18
*** xingchao_ has joined #openstack-meeting-405:18
*** nzhou has quit IRC05:18
*** dwalleck has quit IRC05:22
*** xingchao_ has quit IRC05:25
*** dannywilson has quit IRC05:30
*** dannywilson has joined #openstack-meeting-405:31
*** puranamr has joined #openstack-meeting-405:31
*** puranamr has quit IRC05:31
*** puranamr has joined #openstack-meeting-405:33
*** dannywilson has quit IRC05:35
*** puranamr has quit IRC05:37
*** nkrinner has joined #openstack-meeting-405:39
*** markvoelker has quit IRC05:43
*** armax has quit IRC05:49
*** DericHorn-HP has quit IRC06:04
*** kobis has joined #openstack-meeting-406:08
*** numan has joined #openstack-meeting-406:08
*** tobe has quit IRC06:14
*** wojdev has joined #openstack-meeting-406:30
*** tobe has joined #openstack-meeting-406:33
*** wojdev has quit IRC06:36
*** markvoelker has joined #openstack-meeting-406:43
*** markvoelker has quit IRC06:49
*** belmoreira has joined #openstack-meeting-406:53
*** salv-orlando has joined #openstack-meeting-406:54
*** salv-orlando has quit IRC06:56
*** salv-orlando has joined #openstack-meeting-406:56
*** bradjones has quit IRC07:02
*** bradjones has joined #openstack-meeting-407:04
*** bradjones has quit IRC07:04
*** bradjones has joined #openstack-meeting-407:04
*** fallenpegasus has joined #openstack-meeting-407:07
*** sarob has joined #openstack-meeting-407:08
*** sarob has quit IRC07:12
*** s3wong has joined #openstack-meeting-407:48
*** tobe has quit IRC07:48
*** mickeys has joined #openstack-meeting-407:51
*** mickeys has quit IRC07:57
*** s3wong has quit IRC07:57
*** tobe has joined #openstack-meeting-408:04
*** markvoelker has joined #openstack-meeting-408:32
*** markvoelker has quit IRC08:37
*** fallenpegasus has quit IRC08:41
*** salv-orl_ has joined #openstack-meeting-408:53
*** salv-orlando has quit IRC08:57
*** xingchao_ has joined #openstack-meeting-408:57
*** salv-orl_ has quit IRC08:58
*** xingchao_ has quit IRC09:04
*** salv-orlando has joined #openstack-meeting-409:51
*** salv-orl_ has joined #openstack-meeting-409:56
*** salv-orlando has quit IRC09:58
*** salv-orl_ has quit IRC09:59
*** salv-orlando has joined #openstack-meeting-409:59
*** salv-orl_ has joined #openstack-meeting-410:01
*** salv-orlando has quit IRC10:03
*** buchi has quit IRC10:09
*** sarob has joined #openstack-meeting-410:12
*** dims has joined #openstack-meeting-410:14
*** sarob has quit IRC10:17
*** husanu3 has joined #openstack-meeting-410:19
*** markvoelker has joined #openstack-meeting-410:21
*** husanu3 has quit IRC10:25
*** markvoelker has quit IRC10:25
*** husanu1 has joined #openstack-meeting-410:30
*** husanu1 has quit IRC10:31
*** sdake has quit IRC10:50
*** GB21- has joined #openstack-meeting-410:55
*** plopix has quit IRC11:00
*** dims has quit IRC11:02
*** dims has joined #openstack-meeting-411:05
*** dims_ has joined #openstack-meeting-411:10
*** dims has quit IRC11:11
*** tobe has quit IRC11:11
*** salv-orl_ has quit IRC11:14
*** dims_ has quit IRC11:16
*** jpekkari has joined #openstack-meeting-411:17
*** david-lyle has quit IRC11:17
*** dims has joined #openstack-meeting-411:21
*** david-lyle has joined #openstack-meeting-411:21
*** markvoelker has joined #openstack-meeting-411:37
*** bradjones has quit IRC11:38
*** EmilienM|off is now known as EmilienM11:38
*** bradjones has joined #openstack-meeting-411:41
*** bradjones has quit IRC11:41
*** bradjones has joined #openstack-meeting-411:41
*** markvoelker has quit IRC11:41
*** salv-orlando has joined #openstack-meeting-411:49
*** VW_ has joined #openstack-meeting-411:50
*** sankarshan is now known as sankarshan_away11:50
*** marcusvrn has quit IRC11:53
*** amotoki has quit IRC11:57
*** markvoelker has joined #openstack-meeting-411:58
*** VW_ has quit IRC12:08
*** marcusvrn has joined #openstack-meeting-412:12
*** rfolco has joined #openstack-meeting-412:17
*** killer_prince has joined #openstack-meeting-412:18
*** bknudson has joined #openstack-meeting-412:19
*** killer_prince has quit IRC12:21
*** lazy_prince has quit IRC12:22
*** numan has quit IRC12:29
*** dims has quit IRC12:31
*** dims has joined #openstack-meeting-412:31
*** VW_ has joined #openstack-meeting-412:33
*** david-ly_ has joined #openstack-meeting-412:35
*** david-lyle has quit IRC12:39
*** xingchao_ has joined #openstack-meeting-412:39
*** xingchao_ has quit IRC12:39
*** xingchao_ has joined #openstack-meeting-412:40
*** bradjones has quit IRC12:47
*** bradjones has joined #openstack-meeting-412:50
*** bradjones has quit IRC12:50
*** bradjones has joined #openstack-meeting-412:50
*** ajayaa has joined #openstack-meeting-412:50
*** husanu3 has joined #openstack-meeting-412:50
*** husanu3 has quit IRC12:52
*** sankarshan_away is now known as sankarshan12:52
*** jpekkari has quit IRC12:54
*** xingchao_ has quit IRC12:56
*** sdake has joined #openstack-meeting-412:56
*** husanu5 has joined #openstack-meeting-412:56
*** husanu5 has quit IRC13:00
*** jpekkari has joined #openstack-meeting-413:05
*** belmoreira has quit IRC13:05
*** rfolco has quit IRC13:08
*** klamath has joined #openstack-meeting-413:09
*** klamath has joined #openstack-meeting-413:10
*** husanux4 has joined #openstack-meeting-413:13
*** husanux4 has quit IRC13:13
*** irenab has quit IRC13:14
*** husanux0 has joined #openstack-meeting-413:14
*** fallenpegasus has joined #openstack-meeting-413:18
*** VanL has joined #openstack-meeting-413:18
*** husanux0 has quit IRC13:18
*** lyarwood has quit IRC13:19
*** lyarwood has joined #openstack-meeting-413:19
*** husanux9 has joined #openstack-meeting-413:20
*** husanux9 has quit IRC13:21
*** lyarwood has quit IRC13:24
*** lyarwood has joined #openstack-meeting-413:24
*** husanux0 has joined #openstack-meeting-413:25
*** salv-orl_ has joined #openstack-meeting-413:27
*** husanux0 has quit IRC13:29
*** salv-orlando has quit IRC13:31
*** nkrinner has quit IRC13:32
*** ajmiller has joined #openstack-meeting-413:35
*** mmedvede has joined #openstack-meeting-413:37
*** marcusvrn1 has joined #openstack-meeting-413:38
*** marcusvrn has quit IRC13:39
*** zehicle has quit IRC13:42
*** zehicle has joined #openstack-meeting-413:44
*** ajmiller_ has joined #openstack-meeting-413:47
*** bpoulos has joined #openstack-meeting-413:47
*** VW_ has quit IRC13:47
*** ajmiller_ has quit IRC13:48
*** ajmiller has quit IRC13:49
*** lakshmiS_ has joined #openstack-meeting-413:49
*** VW_ has joined #openstack-meeting-413:49
*** xingchao_ has joined #openstack-meeting-413:50
*** GB21- has quit IRC13:54
*** VanL has quit IRC13:56
*** ativelkov has joined #openstack-meeting-413:56
*** harshs has joined #openstack-meeting-413:57
*** harshs has quit IRC13:57
*** agalkin has joined #openstack-meeting-413:57
*** harshs has joined #openstack-meeting-413:57
*** dshakhray has joined #openstack-meeting-413:58
*** puranamr has joined #openstack-meeting-413:59
*** jpekkari has quit IRC14:01
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, GB21, bpoulos, harshs, abhishekk14:02
*** VanL has joined #openstack-meeting-414:02
lone-ragero/14:02
nikhil_k#startmeeting Glance14:02
openstackMeeting started Thu Jun 25 14:02:41 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:02
ativelkovo/14:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:02
*** openstack changes topic to " (Meeting topic: Glance)"14:02
kragnizo/14:02
openstackThe meeting name has been set to 'glance'14:02
mfedosino/14:02
lakshmiS_o/14:02
nikhil_k#topic agenda14:02
*** openstack changes topic to "agenda (Meeting topic: Glance)"14:02
*** lone-rager is now known as hemanthm14:02
flaper87o/14:02
ajayaao/14:02
harshso/14:02
nikhil_k#link https://etherpad.openstack.org/p/glance-team-meeting-agenda14:02
bpouloso/14:03
dshakhrayo/14:03
*** stevelle has joined #openstack-meeting-414:03
nikhil_kWelcome all14:03
nikhil_k#topic Updates14:03
*** openstack changes topic to "Updates (Meeting topic: Glance)"14:03
agalkino/14:03
jokke_o/14:04
nikhil_k#info Liberty-1 released on Tuesday. We had decent number of bug fixes done.14:04
nikhil_k#link https://launchpad.net/glance/+milestone/liberty-114:04
*** wko has joined #openstack-meeting-414:05
*** Bjoern__ has joined #openstack-meeting-414:06
nikhil_kThere isn't much listed on Liberty-2 atm, #link http://status.openstack.org/release/14:06
nikhil_kGuess, first thing we need to do is plan features that need to merge by then14:06
*** mclaren has joined #openstack-meeting-414:06
nikhil_kPlease bring those up in the drivers meeting, so that people can prioritize and review them accordingly14:06
jokke_rather what we can merge by then14:07
*** jpekkari has joined #openstack-meeting-414:07
nikhil_kyes14:07
nikhil_k#topic Other Glance related meetings14:07
*** openstack changes topic to "Other Glance related meetings (Meeting topic: Glance)"14:07
nikhil_kTo bring those up14:07
nikhil_ksee, #link http://eavesdrop.openstack.org/#Glance_Drivers_Meeting14:08
nikhil_kand #link http://eavesdrop.openstack.org/#Glance_Artifacts_Sub-Team_Meeting14:08
nikhil_kWill move on if nothing else14:08
jokke_just ref those two14:08
jokke_can we dedicate 2x 5min timeslots of the start of this meeting from now on to sunc updates from the previous Driver and Artifact meetings?14:09
nikhil_k#startvote should we have? -- 2x 5min timeslots of the start of this meeting from now on to sunc updates from the previous Driver and Artifact meetings14:10
openstackBegin voting on: should we have? Valid vote options are --, 2x, 5min, timeslots, of, the, start, of, this, meeting, from, now, on, to, sunc, updates, from, the, previous, Driver, and, Artifact, meetings.14:10
openstackVote using '#vote OPTION'. Only your last vote counts.14:10
nikhil_k#vote yes14:10
openstacknikhil_k: yes is not a valid option. Valid options are --, 2x, 5min, timeslots, of, the, start, of, this, meeting, from, now, on, to, sunc, updates, from, the, previous, Driver, and, Artifact, meetings.14:10
jokke_#vote yes14:10
openstackjokke_: yes is not a valid option. Valid options are --, 2x, 5min, timeslots, of, the, start, of, this, meeting, from, now, on, to, sunc, updates, from, the, previous, Driver, and, Artifact, meetings.14:10
nikhil_klol14:10
kragnizthat's a lot of options you've got there14:10
nikhil_k#endvote14:10
*** ajayaa has quit IRC14:10
openstackVoted on "should we have?" Results are14:10
nikhil_k#startvote should we have,  2x 5min timeslots of the start of this meeting from now on to sunc updates from the previous Driver and Artifact meetings ?14:11
openstackBegin voting on: should we have,  2x 5min timeslots of the start of this meeting from now on to sunc updates from the previous Driver and Artifact meetings ? Valid vote options are Yes, No.14:11
openstackVote using '#vote OPTION'. Only your last vote counts.14:11
jokke_#vote yes14:11
ativelkov#vote yes14:11
nikhil_k#vote yes14:11
mclaren#vote yes14:11
kragniz#vote yes14:11
harshs#vote yes14:11
mfedosin#vote yes14:11
agalkin#vote yes14:11
flaper87#vote yes14:11
nikhil_k#endvote14:12
openstackVoted on "should we have,  2x 5min timeslots of the start of this meeting from now on to sunc updates from the previous Driver and Artifact meetings ?" Results are14:12
nikhil_k#action nikhil_k : change the format of the meeting to have those time slots14:12
nikhil_k#action all: read the logs and keep agenda of the Glance weekly meeting updated ( https://etherpad.openstack.org/p/glance-team-meeting-agenda )14:12
nikhil_kmore?14:13
nikhil_k#topic glance-quota-enhancements14:14
*** openstack changes topic to "glance-quota-enhancements (Meeting topic: Glance)"14:14
jokke_thanks14:14
nikhil_kharshs: please go ahead14:14
harshsthanks nikhil_k14:14
nikhil_k#action harshs : create a spec for that BP14:14
harshsthis is the blueprint14:14
harshshttps://blueprints.launchpad.net/glance/+spec/glance-quota-enhancements14:14
harshsjust wanted to know thoughts from the folks14:14
nikhil_k#link https://github.com/openstack/glance-specs/14:14
nikhil_kQuotas are racy (very very racy)14:15
harshs:)14:15
nikhil_kPlus they can be really tricky if you wanna ensure across services14:15
nikhil_kNova is doing some work around this14:15
nikhil_kThe idea scenario is we have a openstack wide quota lib14:15
jokke_they are also really really wanted across the userspace14:15
nikhil_kideal*14:15
mclarennikhil_k: has there been any progress on that front?14:16
nikhil_kharshs: we should sycn with Nova PTL to see how much traction we can get there. I think we need them14:16
harshsnikhil_k: ok. makes sense14:16
nikhil_kmclaren: Only on abstract level. we need people for making it happen that's all :)14:16
harshsright14:17
mclarenyeah I think other services eg cinder have done their own thing so I wouldn't be against us not waiting for a global thing14:17
harshsalso as far as i know there isn’t still a consensus on the common quota lib front or is there?14:17
mclarenare these per-user quotas?14:17
harshsmclaren: per user or per tenant14:18
mclarencool14:18
flaper87mclaren:++14:18
flaper87we've waited long enough14:18
mclarenwould they be for v1/v2/v3 or common to all?14:18
flaper87please, lets stop adding stuff to v1 :D14:18
nikhil_kI think we don't want any more feature richness in v114:18
* flaper87 hides from mclaren's looks14:18
mclarenok, so if you want quotas you have to disable v1?14:19
nikhil_kmclaren: I think we have to start deprecation path for v1 very soon nonethelss14:19
jokke_flaper87: I do agree, but as long as v1 is the only one Nova is using, it really does not help to enforce the quotas only on the later ones :D14:19
nikhil_kthere's some buzz happeing around defcore14:19
mclarensure, just trying to understand the big picture14:19
nikhil_kjokke_: we MUST move away from Nova using v1 this cycle14:20
jokke_personally I think any quotas should be api version agnostic14:20
mfedosinI remember Jay Pipes's promise to switch nova to v2 at the weekend :)14:20
flaper87jokke_: right but there are efforts on changing that for Liberty and as long as we keep saying: "We'll add this to v1 because nova is sitll using it" we won't ever move away from v114:20
flaper87You want quotas? Oh look, v2 has them14:20
flaper87:)14:20
harshs:)14:21
flaper87which gives this spec even more value14:21
flaper87:D14:21
nikhil_kmfedosin: cool! I have your writting proxy now :P14:21
mclarenyeah I think that's fine. Perhaps an incentive to swifch off v114:21
flaper87but yeah, I agree they should be as agnostic as possible14:21
nikhil_kwritten*14:21
jokke_flaper87: ofc, as that approach has worked so well :P14:21
flaper87jokke_: what do we have that v1 doesn't? Except for tasks (that require writing json on the CLI) and fewer bugs ?14:22
mclarenso we target v2, but try to keep v3 in mind with the design?14:22
* flaper87 won't get into the v1/v2 war now14:22
nikhil_k+1 mclaren14:22
flaper87mclaren++14:22
flaper87mclaren: you are on a roll14:22
flaper87:D14:22
jokke__but_ actual details on that bp ... do we track difference between image and snapshot? I did not think so14:22
nikhil_kharshs: please bring this up in the artifacts meeting14:22
harshsnikhil_k: sure14:22
nikhil_kmoving on14:23
jokke_so regarding the actual proposal I think snapshot quotas needs to be implemented on Nova & Cinder as they actually know what the image is they are creating/uploading14:23
nikhil_k#topic Glance-api and ceph ( mfedosin )14:23
*** openstack changes topic to "Glance-api and ceph ( mfedosin ) (Meeting topic: Glance)"14:24
mfedosinhi, folks14:24
nikhil_k#link  https://review.openstack.org/#/c/186780/14:24
mfedosinI want to discuss one thing with you about ceph backend.14:24
mfedosinSome time ago our QAs played with it (like switched on and off) and at some point ceph stopped to answer.14:24
mfedosinWhen they tried to upload an image there with glance, glance-api hanged with no response.14:24
mfedosinI figured out what it was - cinder guys had the same problem.14:25
mfedosinActually two problems:14:25
mfedosin1. We don't have connection timeout with it.14:25
mfedosinhttps://review.openstack.org/#/c/10342414:25
mfedosin2. And since RBD is a python binding for librados it isn't patched by eventlet.14:26
mfedosinhttps://review.openstack.org/#/c/175555/14:26
mfedosinCombination of these two issues leads to infinite hangup of glance-api, if there is no response from the ceph-server.14:27
flaper87:(14:27
mfedosinonly restart helps14:27
jokke_1) I'm all up to putting timeouts on all those calls14:27
mfedosinI started to work on this https://review.openstack.org/#/c/186780/14:27
*** Zucan has joined #openstack-meeting-414:28
mfedosinbut it seems like we need massive refactoring of the driver14:28
mfedosinlike creating a single method for getting a connection, because currently it happens in every method.14:28
*** Zucan has left #openstack-meeting-414:28
mfedosinIs it okay and can you review it after it's done, because I'm not so familiar with ceph?14:28
jokke_2) I think we need to address this somehow, BUT I'm not really fond of starting to spin up threads for all kind of blocking things that the current eventlet approach can't handle ... this is again one of those things that we need to add to the list adding weight to get rid of eventlet14:29
nikhil_k== jokke_ 2)14:29
flaper87mfedosin: why do you think a major rewrite is needed ?14:29
mfedosinflaper87, not so much actually14:30
flaper87I'd like to involve rdb folks on this14:30
*** yamahata has joined #openstack-meeting-414:30
mfedosinjust a single method for getting a connection14:30
mfedosinwhich works with timeout14:30
mfedosinflaper87, thanks!14:30
nikhil_kmfedosin: the purpose of limiting thread size is dissolved if we create another pool14:30
flaper87mfedosin: please, keep me posted and I'd like to review it14:31
*** TravT has joined #openstack-meeting-414:31
*** marcusvrn has joined #openstack-meeting-414:31
nikhil_kthis needs a security eval from operators actually using rbd14:31
mfedosinseparate threads is not necessary, it's just an improvement14:31
nikhil_ks/thread size/thread pool size/g14:31
nikhil_kyeah14:31
flaper87mfedosin: can we start with just the timeout for now14:32
nikhil_kI think we shouldnt' create a separate pool14:32
flaper87I think it'd be better to keep these patches separate14:32
*** dshakhray has quit IRC14:32
flaper87just to make sure we have a "Panic Revert Exit"14:32
flaper87that is clearer14:32
jokke_definitely14:32
mfedosinokay, let's start with timeout, because second part is easy14:32
*** dshakhray has joined #openstack-meeting-414:32
flaper87mfedosin: awesome, thanks for working on this14:32
flaper87I wasn't aware of this issue14:32
flaper87mfedosin: do we have a way to replicate it?14:33
mfedosinAlso I think I should file a bug in launchpad, based on the information fro the QAs14:33
flaper87(that doesn't imply mocking)14:33
nikhil_kmfedosin: please do :-)14:33
jokke_until this is really evaluated I'm more than happy to -2 any patch that starts spinning up wild threads from glance ;)14:33
stevellewild threads in their natural environment14:34
*** marcusvrn1 has quit IRC14:34
nikhil_k#topic test coverage ( agalkin )14:34
*** openstack changes topic to "test coverage ( agalkin ) (Meeting topic: Glance)"14:34
nikhil_kagalkin: you're not kidding!14:34
mfedosinokay, I will say a couple of words here14:34
mfedosinso, about test coverage...14:35
mfedosinIt's very low, you know :)14:35
nikhil_kagalkin: what feedback/help do you need from us? I think this is a good start.14:35
mfedosinAnd Alexey Galkin is eager to improve it.14:35
mfedosinSo I think he's going to write a small etherpad document, that describes concrete steps of what will be done.14:35
mclarendo we have any stats?14:36
mfedosinagalkin, am I right?14:36
jokke_can someone tell me what is the test coverage on glance - artifacts + indexing (as in searchlight)14:36
mfedosin38% currently14:36
agalkinmfedosin, yes you are right14:36
nikhil_kglance - (artifacts + indexing) is 38% ?14:36
mfedosinI thinks these stats about v1 and v2 excluding artifacts and stuff14:37
agalkin<nikhil_k>, without artifacts14:37
mfedosinnikhil_k, yes14:37
mclarenv1 versus v2 would be interesting14:37
mfedosinagalkin, can you compare v1 and v2 too?14:38
nikhil_kagalkin: would love to know more on the details of the stats. I think functional coverage might be way lower so that a big concern14:38
agalkin<mfedosin> well, I'll try14:39
mfedosinagalkin, thank you! please, provide as much stat information as you can in your etherpad14:39
mfedosinso we can discuss it on the next meeting14:40
mfedosinActually one question: do we need a blueprint on this, or just etherpad + irc discussions is enough?14:40
nikhil_ketherpad + irc14:40
mfedosinnikhil_k, okay, get you14:41
mfedosinso, that's all for now. thanks for your responses14:41
nikhil_k#topic Open Discussion14:41
*** openstack changes topic to "Open Discussion (Meeting topic: Glance)"14:41
nikhil_kmclaren: is your travel looking tentative (still) ? (for mid-cycle)14:42
*** jpekkari has quit IRC14:42
mclarendid we finalize a date?14:43
*** mitchjameson has joined #openstack-meeting-414:43
*** puranamr has quit IRC14:43
* jokke_ is wondering what the heck our tests are testing ... glance/ -tests/ is around 49k lines and tests is around 58k lines14:43
nikhil_kmclaren: june 28-3014:43
nikhil_kerr14:43
*** puranamr has joined #openstack-meeting-414:44
nikhil_kjuly 28-3014:44
mclarenah, ok, thanks.14:45
bpouloshave we finalized a location?14:45
nikhil_kBecause we seem to have tentatively very low particiation from outside of US, and a lot!! of people wanted to have mid-cycle in Blacksburg, we will conduct there14:45
mclarennikhil_k: I may be able to make that but I'm not fussy on location at all14:46
nikhil_kbut since a lot of the active members are busy and find it hard to travel during these dates/venue and we have an incresibly tough scheduling problem14:46
nikhil_kwe will limit our decisions on the important specs unless people have good experience with video conferencing tool14:47
*** SamYaple has left #openstack-meeting-414:47
nikhil_kI have chatted witht he repr there and they are willing to support the same req14:47
*** puranamr has quit IRC14:48
nikhil_kThe problem now is of time slots for important sessions/topic14:48
nikhil_kmclaren: thanks!14:49
jokke_nikhil_k: Blacksburg as in Blacksburg, Virginia?14:49
nikhil_kruding for you and flaper87 to join the same14:49
nikhil_kand others who said that it was not likely (before)14:49
nikhil_kjokke_: yes14:49
jokke_nikhil_k: Washington and Atlanta being closest airports? That place looks like really interesting to get in to :P14:50
bpoulosCharlotte is closer14:50
nikhil_kjokke_: CLT14:50
*** mitchjameson has quit IRC14:51
nikhil_kif people are flying into CLT, I can arrange for ride-share (by someone who is attending the same)14:51
*** vikram_ has joined #openstack-meeting-414:51
jokke_nikhil_k: yeah the end half of July & August are normally bad times for Europeans as they are either on holidays or crazy busy covering someone who is on holidays on top of their own job14:52
nikhil_kgotcha14:53
nikhil_kI thought it would be a bad idea to postpone it beyond July considering the cycle is small14:53
nikhil_kearly in the July did not work out for a long time14:54
mclarenyeah, it's a lot of folks from a lot of places to try to co-ordinate14:54
jokke_nikhil_k: I'm not blaming, just stating the most probable reason for your note not seeing much attendance out of US14:55
nikhil_kSince, we had the past couple of mid-cycle in summer during this period, I figured it might be a good possiblity.14:55
mclarennikhil_k: what's the defcore buzz you mentioned earlier?14:55
nikhil_kjokke_: gotcha. Thanks, I am a little fried and burned by this scheduling experience :P14:55
*** carl_baldwin has joined #openstack-meeting-414:55
*** mestery has joined #openstack-meeting-414:56
nikhil_kmclaren: the problem is that people want a single API that needs to be supported for a really long time14:56
nikhil_ksomething that can't be deprecated (forever)14:56
nikhil_kpeople are asking which is that API14:56
mclarenyeah14:57
nikhil_kplus we moved v1 to supported and v2 to current now14:57
nikhil_kNova still needs v114:57
*** VW_ has quit IRC14:57
nikhil_kthat can be confusing for operators who have upgraded to kilo14:57
nikhil_kon top of that14:57
nikhil_kwe have 2 ways to do upload and downloads14:57
jokke_nikhil_k: wasn't it just v1 from current to supported? IIUC both of them were stated as current for long time14:58
nikhil_kso the tempest tests for defcore need to pass for all clouds on that sigle API defined necessary for interop14:58
*** VW_ has joined #openstack-meeting-414:58
nikhil_kjokke_: it's just our plan for moving away from supported that's confusing14:58
mclarenI guess a v3 adds to the buzz?14:59
*** puranamr has joined #openstack-meeting-414:59
nikhil_kmoving away from supported == deprecating the API14:59
nikhil_knot at this point14:59
nikhil_kbut could be14:59
nikhil_kit's the tasks that is the problem, actually14:59
jokke_I think the problem becomes if v3 starts to support images at some point14:59
nikhil_kthe wrapping of the v2 APi on top of v3 can help with that15:00
jokke_if we get nova, cinder, horizon using v2 and kick v1 out, I think defcore would be perfectly happy to be told that that is de facto images api15:00
*** sjmc7 has joined #openstack-meeting-415:00
mfedosinnikhil_k, we're thinking about that15:00
nikhil_kjokke_: +1 on nova, cinder, horizon using v215:00
nikhil_kkicking out v1 would be tricky but possible15:01
*** david-ly_ is now known as david-lyle15:01
nikhil_kthanks mfedosin15:01
nikhil_kOk, we are out of time15:01
nikhil_kThanks all!15:01
mclarenthanks!15:01
nikhil_k#endmeeting15:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:01
openstackMeeting ended Thu Jun 25 15:01:44 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-06-25-14.02.html15:01
jokke_nikhil_k: that's different topic ... this was the imaginary way to satisfyy defcore's one eternal api wish15:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-06-25-14.02.txt15:01
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-06-25-14.02.log.html15:01
*** stevelle has left #openstack-meeting-415:01
jokke_thanks!15:01
*** mclaren has quit IRC15:01
TravT#startmeeting openstack search15:02
openstackMeeting started Thu Jun 25 15:02:01 2015 UTC and is due to finish in 60 minutes.  The chair is TravT. Information about MeetBot at http://wiki.debian.org/MeetBot.15:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:02
*** openstack changes topic to " (Meeting topic: openstack search)"15:02
openstackThe meeting name has been set to 'openstack_search'15:02
nikhil_ko/15:02
TravT#chair nikhil_k15:02
openstackCurrent chairs: TravT nikhil_k15:02
TravThey nikhil_k15:02
*** ajayaa has joined #openstack-meeting-415:02
nikhil_khi TravT15:02
kragnizo/15:02
lakshmiS_o/15:02
nikhil_kHope you had a great trip15:02
TravTwell, i'm about 20 minutes back into work...15:02
*** bpoulos has left #openstack-meeting-415:03
TravTalways rough to get going again15:03
david-lyleo/15:03
nikhil_k:)15:03
*** armax has joined #openstack-meeting-415:03
sjmc7o/15:03
TravTok15:03
TravTso, looks like the first #topic is mid cycle meetup15:04
*** jwagner_away is now known as jwagner15:04
TravTnikhil_k, any updates on this?15:04
TravT#topic mid-cycle meetup15:05
*** openstack changes topic to "mid-cycle meetup (Meeting topic: openstack search)"15:05
nikhil_k#link https://etherpad.openstack.org/p/search-team-meeting-agenda/q15:05
nikhil_ko/15:05
nikhil_kThe Glance mid-cycle is planned to be in BLacksburg, VA July 28-3015:05
TravTdavid-lyle: horizon is finalized for July 21 - 23rd in Fort Collins, right?15:05
david-lylecorrect15:06
nikhil_kThere was a lot of demand from US folks who showed interest in attending and in Blakcsburg so we went ahead with that plan15:06
TravTso, we won't have the overlap that would have helped with travel planning coordination.15:06
nikhil_kI have asked for video conferencing capability and from experience it works very well in Blacksburg15:07
nikhil_k+1 TravT15:07
TravTkragniz, laskhmiS_: you guys couldn't travel anyway, right?15:07
lakshmiS_yes15:07
kragnizTravT: likely15:07
nikhil_kAs a lot of the european folks aren't showing the possiblity of attending during that time frame (for travel and other reasons) we will have it remote heavy15:08
nikhil_kBut I request everyone to please try and attend personally if possible!15:08
TravTso, the question is whether or not we should try to do a one day searchlight meetup at the same time in blacksburg?15:09
TravTor if we should do a morning or two of virtual conferences (US morning)15:09
nikhil_kThat would be fantastic but like GLance we can agree to not make important decisions if people aren't able to attend (Even remotely)15:10
nikhil_kHaving people personally will help with some face to face time and rapport building15:10
TravTsjmc7 how are things looking for you?15:10
sjmc7manager's been on vacation til today. i am 100% certain i could get clearance to travel to FC for the horizon one, not sure about VA15:11
nikhil_kAlso, if someone is planning to fly into CLT we can arrange for ride-sharing (With someone attending the meetup)15:11
TravTi think some of the best value we could get is if we do some pair programming.15:11
*** puranamr has quit IRC15:12
TravTdavid-lyle: what is your availability?15:12
david-lyleI'm not sure I can make it to VA :(15:13
TravTok, so it sounds like we need to all have a discussion with our managers.15:13
*** mwang2_ has quit IRC15:14
*** mwang2_ has joined #openstack-meeting-415:14
TravTnikhil_k, is this tied to the interest, time, virtual meetings topic up next?15:14
TravTor is that separate?15:14
nikhil_kTravT: yes15:14
nikhil_kit's the same, just wanted some feedback15:15
nikhil_kBasically, the only reason the announcement is not on the ML is to check any red flags15:15
*** praveens has joined #openstack-meeting-415:15
nikhil_kThe homework to schedule it in Blacksburg has been mostly done15:15
TravTok, well, I can probably get to blacksburg if we can get a few other people there.15:16
nikhil_kand I am too tired now to think about rescheduling :)15:16
TravTbut I think all of this is tied to another topic15:16
TravT#topic Liberty 2 Release Plan15:16
*** openstack changes topic to "Liberty 2 Release Plan (Meeting topic: openstack search)"15:16
TravTIf we hope to have something usuable in liberty, we need to make some solid progress on implementing some blueprints in Liberty 215:17
TravTI guess first of all, there are 3 blueprints on liberty-115:18
TravT#link https://launchpad.net/searchlight/+milestone/liberty-115:18
TravTlakshmiS, sjmc7, kragniz: are they all implemented?15:18
TravTor do we need to move any of them to liberty 2?15:18
nikhil_kTravT: I checked with rel-mgrs the other day and they are cool with the team releasing it's own milestone(s) in Liberty timeframe. We dont' have to stick to the common schedule15:18
*** dannywilson has joined #openstack-meeting-415:18
sjmc71 and 2 are, TravT15:18
sjmc7not sure about whether the code's out of glance yet15:19
nikhil_kSo, may be we just pick a date and call it Liberty-0.1 or something15:19
TravTsjmc7: can you update the status15:19
nikhil_ksjmc7: it's not yet. (last time I checked)15:19
TravTnikhil_k: what are the pros and cons?15:19
nikhil_kpro: we don't have to wait. something is out is good for real world testing and getting interested poeple using it beta15:20
*** dannywil_ has joined #openstack-meeting-415:20
nikhil_kcons: we have to keep track of the dates and rel-mgmt ourselves and it doesn't happen in batch mode15:20
*** dannywilson has quit IRC15:20
lakshmiS_but i think it should be an easy task to remove the code15:21
TravThmm... so are you saying maybe we'd do like a 0.1 and then go back to standard milestones?15:21
lakshmiS_since its isolated15:21
nikhil_kpro: we can work on fixing packaging issues offline and not in the gate (& other rush) during peak rel periods15:21
*** jwagner is now known as jwagner_away15:21
TravTdavid-lyle: what should we consider from a horizon consumption of searchlight perspective when it comes to releases?15:22
nikhil_kcons: we may hav eto resolve packing woes ourselves and get less help from the experts working upstream already15:22
nikhil_kTravT: yeah, I think we can go with 0.1 as alpha and may be a 0.2 beta followed with Liberty overall for beta-prod15:22
david-lyleHorizon will likely only consume a client if there is one and the version for that can be anything15:23
*** praveens has quit IRC15:23
david-lyleif there's not, they dependency wise, I suppose we don't have one15:23
david-lyles/they/then/15:23
*** ajayaa has quit IRC15:23
david-lylejust make the API calls and hope for the best15:23
*** praveens1 has joined #openstack-meeting-415:23
nikhil_k:)15:23
TravTdavid-lyle: we need to talk through the whole client concept and see if we would initially write direct queries from horizon.15:24
sjmc7we can make available the code from the summit demo if that'd help discussion15:24
sjmc7i think it's on github15:24
david-lyleI think initially it's fine to make direct calls15:24
TravTsjcm7: yep, i was planning on syncing up with you and kelly on that in the next day or so15:24
david-lylethe API shouldn't be overly complex to need a wrapper15:24
david-lyleand we can adjust later if necessary15:25
nikhil_k++15:25
david-lylebut in that case, if searchlight shows up in the service catalog, we'll expose it in horizon, otherwise no15:25
sjmc7again, we had some PoC code to do that that might be good to start conversation15:26
david-lylesjmc7: are you saying it's a mess ;)15:26
TravTsjmc7: definitely, i want to start working from some of that code in horizon.  was going to open a proper blueprint on the horizon side.15:27
sjmc7it's charming and rough around the edges15:27
*** DericHorn-HP has joined #openstack-meeting-415:27
TravTdavid-lyle: was thinking of first opening a blueprint to angularize images table.15:27
TravTand start working on that15:27
TravTand then adding the searchlight integration for images first15:28
TravTsince it is in theory ready for images15:28
TravTand then do instances15:28
david-lylegood to use what's there rather than what's not15:28
david-lyle++15:28
TravTbut hopefully instances BP will be ready soon.15:28
*** agalkin has quit IRC15:28
TravTso, we can swing back around on this tangent15:29
TravTnikhil_k on releases, what all is involved?15:29
nikhil_kTravT: if we do it ourselves, getting the script that does the tagging of bugs15:30
nikhil_kwe will hav eto manually update BPs15:30
*** kobis has quit IRC15:30
nikhil_kalso, rel notes are written by the PTL so that15:30
nikhil_krequirements check15:31
nikhil_kstable branch15:31
*** Swami has joined #openstack-meeting-415:31
nikhil_kand setting up backports etc tags in BP to help keep track of stuff15:31
nikhil_kminor things15:31
nikhil_kbut many15:31
nikhil_kthese are two edged swords, it used by openstack rel-mgrs then we would always be in a rush. but if we do it personally then a bit of work15:32
nikhil_ks/it/if/g15:32
*** bobmel_ has joined #openstack-meeting-415:32
david-lylerelease mgmt should still help us even if we pick an open release schedule15:32
TravTok, so, if we wait until liberty 2, they'd take care of a number of the above?15:32
*** daneyon has joined #openstack-meeting-415:33
nikhil_kdavid-lyle: I hope so, they said that team should do it on its own schedule for newer projects15:33
david-lylebe parting of the integrated 6 month release is no longer a requirement15:33
david-lylecan't type15:33
david-lylebeing part15:33
TravTok, well, it seems like even if we try to line up with liberty 2, that we should start heading in that direction sooner than later.15:34
david-lyleincubated projects in the past also set their own milestones15:34
*** TheIntern has joined #openstack-meeting-415:34
nikhil_kTravT: may be. the tone of the response seemed tentative as there is a lot of work as is with so many older projects15:34
*** daneyon_ has joined #openstack-meeting-415:34
david-lylenikhil_k: hedging against overload15:34
nikhil_kMy feeling was that we have something out soon-ish for people to start consuming it and that might be worth one realse on our own15:35
nikhil_kdavid-lyle: yeah, I understand15:35
TravTok, so we should try to do that.15:35
TravT#action nikhil_k, TravT work on release plan15:36
TravTSo let's talk about important bp15:36
TravT#topic Important BPs15:36
*** openstack changes topic to "Important BPs (Meeting topic: openstack search)"15:36
TravT#link https://blueprints.launchpad.net/searchlight15:36
*** bobmel has quit IRC15:36
nikhil_ksorry, I forgot to add my name15:37
TravTgo ahead nikhil_k15:37
nikhil_kbut feel free to go ahead15:37
nikhil_k:)15:37
*** daneyon has quit IRC15:37
nikhil_kWas curious if we can work on the devstack bit first and setup tests15:37
nikhil_khaving a good working dev environment doesn't hurt15:38
TravTi would definitely like to see us get devstack in right away15:38
*** ajmiller has joined #openstack-meeting-415:38
TravTekarlso: wko15:38
TravT#link: https://review.openstack.org/#/c/194251/15:38
wkoyes15:38
TravTwko, have you had a chance to look over the above?15:39
wkoonly just15:39
TravTsince you had catalog index service working for glance15:39
TravTok, well, i just saw it right before the meeting.  I will look through it later today.15:41
TravTsjmc7, looks like you've already given it a once over15:41
wkoit looks different to me, but, sorta the same15:41
TravTthere is some question about whether devstack should be under contrib folder or not15:41
sjmc7yeah - i didn't have a chance to run it yet. there were some things i noted in the review but it follows the template of other projects fairly closely15:41
TravTi see that karlso might have done that because it provides some symmetry with the vagrant file15:42
TravTbut, if we could all make it a priority to look over it, run it, review it, that'd be best.15:43
TravTnikhil_k, what other items did you have on this topic?15:43
nikhil_kI haven't had a chance to look at the possiblity of us using tempest-lib. this would mean we have intergration tests in the repo and not use the functional tests concept in glance (which is flawed anyways as it does a lot of integration testing). I am a bit caught up in nova using glance v2 work and that may take a bit of time in the coming weeks. Should we just play it by ear and go ahead with sjmc7's plan to port functional tests to SL?15:44
TravTwhat this in last week's meeting?15:45
nikhil_kyeah15:45
TravTi need to catch up on that15:46
sjmc7yeah, we didn't make a decision15:46
*** ajayaa has joined #openstack-meeting-415:46
nikhil_kno worries, just throwing it out there15:46
*** marcusvrn1 has joined #openstack-meeting-415:47
*** marcusvrn has quit IRC15:47
sjmc7the tests i had did were mainly to exercise RBAC15:47
sjmc7i don't think it had a requirement on keystone or any other services15:47
nikhil_kyeah, it uses fake auth15:47
nikhil_kwhich is terrible15:47
sjmc7:)15:48
nikhil_kbut so are other things in glance :)15:48
sjmc7it means they run as functional tests, rather than requiring a full stack15:48
* nikhil_k pretends he did not just say that :P15:48
TravTso, i thought integration testing was becoming more a responsibility within projects?15:48
nikhil_kslowly15:48
*** xingchao_ has quit IRC15:48
nikhil_ksjmc7: yeah, but they spin up a server process15:48
*** GB21 has joined #openstack-meeting-415:49
nikhil_kso it's kinda really in the middle15:49
nikhil_kand have it's own config, rbac etc setup15:49
nikhil_kwithin the repo15:49
TravTsjmc7 what would be your recommendation here?15:50
sjmc7ultimately, we need tempest tests15:50
*** sdake_ has joined #openstack-meeting-415:50
sjmc7we can't do that until we're integrated properly, and until then i think there's value in having tests that run against elasticsearch15:50
TravTi agree with that15:50
sjmc7whether we invest the time doing it is another question15:51
sjmc7versus getting into tempest asap15:51
TravTif we don't have tests that run against elastic search, i'm not sure how we'd have any level on confidence15:51
nikhil_ksjmc7: I agree with you. if we all can agree to not maintain functional tests in the repo and use tempest later, it would be really nice15:52
TravTseems reasonable to me.15:53
TravThate to rush us, but this is still on topic.  nikhil_k where are you in looking at a nova plugin?15:53
nikhil_khaven't started yet :(15:53
TravTkragniz, lakshmiS, do you have any plugin work started on swift?15:53
*** sdake has quit IRC15:54
*** cloudnull has joined #openstack-meeting-415:54
nikhil_kI can take a look late next week, (after coming abck from travel) but wouldn;t have status in the next meeting.15:54
lakshmiS_stuart was asking for info from a spec which has similar requirement15:54
TravTnikhil_k, do you want sjmc7 to post his initial nova plugin and then you guys (kragniz, lakshmiS) as well, could collaborate on it from there?15:54
sjmc7i couldn't find any evidence swift sends notifications at the moment15:54
nikhil_kwith the defcore stuff in glance/nova images, I couldnt get a chance to ask John15:54
lakshmiS_https://review.openstack.org/#/c/180918 is the spec which will send notications15:54
nikhil_kTravT: that would work15:55
*** b3rnard0 has joined #openstack-meeting-415:55
lakshmiS_hopefully we can get them to use searchlight instead and let them develop the notifications15:55
sjmc7TravT, nikhil_k - you want me to push a review up with the nova work from the summit and hand it over?15:55
TravTsjmc7, that sounds good.  maybe you guys can co-author on it.  I'm sure lakshmiS can contribute as well.15:56
TravTjust want to see us start getting other data in from other services.15:56
TravTwe also, need somebody to start looking at neutron15:56
nikhil_ksjmc7: sounds good15:57
TravT#topic Adding an entrypoint for the agent process, potentially renaming searchlight-index because it's confusing15:57
*** openstack changes topic to "Adding an entrypoint for the agent process, potentially renaming searchlight-index because it's confusing (Meeting topic: openstack search)"15:57
TravTsjmc715:57
sjmc7this was me!15:57
TravTnot much time15:57
sjmc7i'll be brief15:57
TravTsorry15:57
sjmc7i think endre had some confusion (understably) about the searchlight-index entrypoint15:57
sjmc7which in fact is more akin to glance-manage15:58
sjmc7rather than being the notification indexing service15:58
*** rromans has joined #openstack-meeting-415:58
sjmc7so we a) need an entry point for agent_notifications15:58
sjmc7and b) i suggest renaming searchlight-index to searchlight-manage or something similar15:58
sjmc7and using searchlight-monitor or -agent or -listener for the daemon processes15:59
TravTno -monitor15:59
sjmc7-listener might be best15:59
TravTtoo many impleications15:59
TravT-listener sounds pretty good15:59
*** armax_ has joined #openstack-meeting-415:59
nikhil_k+1 -listener15:59
nikhil_kand on searchlight-manage15:59
TravTi'm +1 on that as well16:00
nikhil_khow about searchlight-ctrl16:00
sjmc7i'll file a BP and make the change if nobody objects within a day or so16:00
TravTyeah, BP would be best16:00
TravTthanks everybody16:00
sjmc7nikhil_k - i'll post the BP in a bit16:00
TravTwe are out of time.16:00
nikhil_kthanks!16:00
sjmc7make suggestions there16:00
*** s3wong has joined #openstack-meeting-416:00
nikhil_ksjmc7: sure16:00
sjmc7thanks TravtT16:00
TravT#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Thu Jun 25 16:00:42 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-06-25-15.02.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-06-25-15.02.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-06-25-15.02.log.html16:00
*** Sam-I-Am has joined #openstack-meeting-416:00
cloudnull#startmeeting OpenStack Ansible Meeting16:01
openstackMeeting started Thu Jun 25 16:01:05 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-Ammoo.16:01
*** armax has quit IRC16:01
*** armax_ is now known as armax16:01
*** sjmc7 has left #openstack-meeting-416:01
rromans.16:01
cloudnullwe have lots of ground to cover today so we're skipping the formalities.16:01
cloudnullo/ everyone16:02
b3rnard0hello16:02
cloudnull#topic Defining the project mission - odyssey4me16:02
*** openstack changes topic to "Defining the project mission - odyssey4me (Meeting topic: OpenStack Ansible Meeting)"16:02
*** odyssey4me has joined #openstack-meeting-416:02
cloudnull#link https://review.openstack.org/19110516:03
odyssey4mesorry I'm late, now present16:03
*** Sukhdev has joined #openstack-meeting-416:03
cloudnulldid you want to talk about "Defining the project mission"16:03
hughsaundershey16:03
palendaePresent16:03
cloudnullspecifically - Is our mission to deploy OpenStack (just OpenStack services), or to deploy whole OpenStack environment (OpenStack and all supporting infrastructure)? Where do we draw the line?16:04
cloudnullIMO i think its the later. we build a batteries included stack for use in production.16:04
Sam-I-Amgood question16:04
odyssey4meSure, I just wanted to raise the questions set out in the agenda and have us discuss them again. It seems that we didn't quite get to a conclusion before and we're being inconsistent already16:04
*** git-harry has joined #openstack-meeting-416:05
Sam-I-Amwith infra (such as galera) is more opinionated, but its easier to guarantee a working product when you do those things16:05
hughsaunderscloudnull: I think the focus is on openstack, but we should be able to deploy all thats needed to get it to work.16:05
Sam-I-Amif you say 'have a sql database' who knows what you're getting into16:05
palendaeHow much of openstack?16:05
Sam-I-Amcould be mariadb, could be postgres, maybe redundant, maybe not16:06
odyssey4meI don't have strong feelings either way, but I would like us to be clear on what we're about so that we can use the principle as a backing for reviews and spec decisions.16:06
palendaeFor instance...mongo for ceilometer16:06
hughsaundersI think we could probably focus more on openstack by reusing other people's bits for infra, however that always sounds easier than it is.16:06
Sam-I-Amthere always the option of making it an option16:06
palendaeI know others have expressed opinions on it before, just pointing out that deploying what openstack needs to work also leaves the question of what parts of openstack do we care about?16:06
odyssey4meAs a for instance, we could easily draw the ELK stack roles back into the project as they are OpenStack focused and developed for this stack...16:07
Sam-I-Amjust dont run the infra plays. if you dont, here's a set of prereqs16:07
cloudnullIm with hughsaunders that if we can consume upstream other things we should do that, however I've not found roles that are "better" than what we already have .16:07
cloudnullwhich we could replace16:07
*** VW_ has quit IRC16:07
git-harryI'd like to see use break some of the roles out16:07
git-harry*us16:07
git-harryI've always thought osad should be a consumer of roles not an owner of them16:08
hughsaunders#note git-harry spoke in a meeting16:08
odyssey4meSure, I think we could do better at breaking the roles out into their own repositories and posting them into galaxy. This would be especially useful for infra-type roles which could be used for other deployments.16:08
Sam-I-Amhughsaunders: lol16:08
odyssey4mehowever, my question related a lot more to whether our focus is on deploying openstack... or are we going the whole hog of also facilitating pinning, package additions/removals, host setups, networking setups, etc16:09
odyssey4methese all support an openstack environment, but aren't essential16:09
odyssey4me... to include in this project16:09
cloudnullonce we move we'll have the ability to create new repos as needed, which will help facilitate moving roles into stand alone repos as needed.16:09
cloudnullah. i read the question wrong, odyssey4me16:10
git-harryodyssey4me: that's where I see osad as a ref implementation. So all the roles should be broken out and then osad is essentially a way to test them16:10
git-harryIt's never going to be all things to all people16:11
git-harryby breaking all the roles out it makes most of the project easy to consume by others16:11
git-harrys/easy/easier/16:11
hughsaundersthis is presumably why we don't do pxe - so we can fit in with existing provisioning systems16:11
odyssey4megit-harry yes, perhaps actually a role break-out is the way to show people how to be more flexible and consume other roles16:11
Sam-I-Amso... back to the idea of saying you can use our infra roles or you need to meet a set of prereqs that the openstack roles expect?16:11
cloudnullodyssey4me: in that sense i say no. we dont do pxe booting of hosts / network setup / pinning of system packages.16:11
hughsaundersdoes mean we can't win rule the stack though :/16:12
Sam-I-Amcloudnull: that sounds like more of a per-deployer task (like rpc)16:12
*** spredzy is now known as spredzy|afk16:12
cloudnull++16:12
Sam-I-Amunless its something that impacts openstack itself16:12
cloudnullhughsaunders:  we can rule the stack, just bring your own pxe system16:12
cloudnull:)16:12
*** svg has joined #openstack-meeting-416:12
hughsaunderscloudnull:  :)16:12
svgo/16:13
*** VW_ has joined #openstack-meeting-416:13
* svg struggling to get online on it train16:13
odyssey4memy concern is really down to the question of where we draw the line16:13
hughsaunderssvg: are you visiting the uk?16:13
Sam-I-Amodyssey4me: i dont think we need to draw a line, just provide options?16:13
odyssey4meif our arms are too wide open then we risk bit rot16:13
svg*gr*16:14
Sam-I-Am"heres what we test, if your stuff meets or exceeds the expectations, you can do your own thing for any part of it"16:14
*** VW_ has quit IRC16:14
odyssey4meperhaps we should shift the question to where we draw the line in terms of testing things that get added16:15
cloudnulli think its safe to say that we will do some host tuning and that we will have to interact with host machines however I dont think that we do anything in terms of provisioning.16:15
Sam-I-Amwe probably need a) more contributors b) more contributors with specialization in things like galera16:15
*** VW_ has joined #openstack-meeting-416:15
odyssey4mecloudnull and what if someone decides to submit patches for provisioning16:15
Sam-I-Am"we do software"16:15
Sam-I-Amhost provisioning sounds pretty generic16:16
cloudnullin big tent i'd say those get moved to a new repo.16:16
Sam-I-Amthey can be used for anything16:16
cloudnullbut odyssey4me would that be ansible provisioning ?16:16
cloudnullor ansible setting up a provisioning system ?16:16
*** harshs has quit IRC16:16
cloudnullthat is later used to boot strap hosts?16:16
odyssey4mecloudnull alright, I think essentially if we adopt the strategy of breaking out the roles then we're not creating first and second class citizens16:16
*** armax has quit IRC16:17
odyssey4mewhich would then mean that we accept all the things, but we only test against a reference set of configurations and roles.... any other roles need to be tested individually16:17
palendaeYeah, providing reference configurations would be helpful there16:18
palendaeHere's an AIO test, here's a 3 node test, here's a 516:18
cloudnullthis is likely. and we're probably going to have to revise our test scripts to facilitate better testing of those roles.16:18
cloudnulland add more jobs16:18
cloudnullIE stand alone keystone, keystone + swift, all the things, etc. .16:19
palendaeYeah16:19
odyssey4meyup16:19
palendaeinfra said they could support multi-node tests at summit, too16:19
*** geoffarnold has joined #openstack-meeting-416:19
palendaeBut there'll be some networking monkeying we'll have to do16:19
odyssey4mebut, for instance, bugs like https://bugs.launchpad.net/openstack-ansible/+bug/1411897 would not be something we turn away if we accept all things16:20
openstackLaunchpad bug 1411897 in openstack-ansible "Make package auto updates tunable" [Wishlist,Invalid]16:20
*** dwalleck has joined #openstack-meeting-416:20
*** dolphm has joined #openstack-meeting-416:20
odyssey4mepalendae yeah, it's on my to-do list to get multi-node working... I have all the info I need, I just need the time16:20
palendaeCool16:20
Sam-I-Ampfft time16:20
palendaeAnd that particular one they move to rpc-openstack16:20
*** DericHorn-HP has quit IRC16:20
*** dwalleck has left #openstack-meeting-416:20
palendaemoved*16:21
cloudnullodyssey4me:  i dont agree.16:21
odyssey4mepalendae yep, it was moved because it was denied in the project because it was considered out of scope for OSAD16:21
cloudnullwe turn that away because we're not pinning16:21
cloudnullbut we've provided the ability for a deployer to pin16:21
odyssey4meso the question stands, where do we draw the line?16:21
*** armax has joined #openstack-meeting-416:21
odyssey4mesure, so should we provide the ability to blacklist packages?16:21
cloudnulland that package is installed in the base os at install time, which they configure.16:22
odyssey4meor to remove specified packages, or to tune the unattended updates?16:22
cloudnullso its on their provisioning system to make that go away .16:22
*** VW_ has quit IRC16:22
*** sarob has joined #openstack-meeting-416:22
palendaeYeah, I kinda of agree with odyssey4me. We're allowing a hook to pin packages, but we're not allowing a hook to turn off auto updates?16:23
*** geoffarnold has quit IRC16:23
odyssey4mewe're not making consistent decisions about what we allow or disallow - that's what I'm trying to address16:23
cloudnullagain provisioning. would also add a hook to remove the gnome desktop should they have it installed ?16:23
odyssey4mepinning has nothing to do with openstack, so why do we have a hook for it?16:24
*** geoffarnold has joined #openstack-meeting-416:24
cloudnullpinning does not. and Id be happy to remove that role.16:24
odyssey4meif we have a hook for that, why can't we have a hook for gnome desktop, widget1 and salamander_love123?16:24
cloudnullit was added to help deployers (rax)16:24
odyssey4mecloudnull yep, and I thought we had decided not to add it and had referred it just like we did the auto updates thing... then suddenly there was a patch merged for it16:25
odyssey4meinconsistency :)16:25
*** sdake_ is now known as sdake16:25
cloudnulli hate pinning, its up to the deployer to create a repo . if they dont have one they get the community repo.16:25
* svg uses aptly to 'pin' packages16:26
odyssey4meI really do feel that we can happily welcome anything and everything. I'm happy if someone preps a patch for it and agree that we can facilitate anything, but we only get opinionated about how to use that framework when it comes to a reference architecture for the project.16:26
cloudnullsvg:  doing it right16:26
palendaeSo if we're doing things for deployers16:27
palendaeNot every deployer will agree with us on everything16:27
palendaeRegardless of whether one of our cores hates some approach or not16:27
odyssey4mepalendae sure, that's why I'm happy to provide a framework in the project - but the deployer needs to configure something for it to do anything16:28
svg(but now I need to have the container images to use that repo too, IIRC not configureabl)16:28
*** harshs has joined #openstack-meeting-416:28
odyssey4mepalendae but then we need to be consistent about it - we allow anything in terms of a framework, but not something opinionated unless it has a reference architecture with it which is gate-tested16:29
palendaeodyssey4me: I agree with you16:29
cloudnullso lets revert this and stick to our guns https://review.openstack.org/#/c/18061316:29
odyssey4mecloudnull what I'm suggesting is that we don't - we allow it and anything else16:30
odyssey4mebut much like that patch, it does nothing unless a deployer uses it16:30
palendaeOk, so once that's reverted, how would a deployer add that functionality without having to edit osad roles directly?16:30
Sam-I-Amof course this leads to... what if someone wants to deploy this on another distro :)16:31
cloudnullif that means that we allowing provisioning into core OSAD, as a blanket "we accept all the things". i say no.16:31
cloudnullsvg: you could change the repo url to point to upstream and not add the repo containers ?16:31
odyssey4mein fact, for these sorts of things the right way to do it would be to create a role in github/stackforge - then it can be consumed, but optionally16:33
cloudnullpalendae: a deployer could create their own role to pin.16:33
palendaecloudnull: Ok, but then how do they make the osad ones rely on it?16:33
cloudnullor have a proper mirror16:33
odyssey4mewe could perhaps just have a doc in our repo providing basic info on roles we've worked with and how to consume them in osad's framework16:33
palendaeThat particular patch touches a lot of osad roles16:33
cloudnullit does16:33
*** Swami has quit IRC16:34
hughsaundersbut they are all role deps - the role could be run in an earlier play without those.16:34
odyssey4mepalendae cloudnull it only does because the decision was made to change all the disparate pinning in those roles to consume this role... which was a good decision16:34
odyssey4meanyway, this has taken enough time and I think we should sleep on it and talk some more about it next meeting16:35
cloudnullok16:35
cloudnull#topic What is our roadmap like? Will making fernet tokens in keystone be an 11.1.0 feature? palendae16:35
*** openstack changes topic to "What is our roadmap like? Will making fernet tokens in keystone be an 11.1.0 feature? palendae (Meeting topic: OpenStack Ansible Meeting)"16:36
palendaeYeah, my question here was do we have those point releases figured out yet?16:36
palendaeFernet tokens is just a good example16:36
cloudnull#link https://review.openstack.org/#/c/193729 (fernet tokens as the default)16:36
cloudnullshort answer palendae no.16:37
palendaek16:37
palendaeI've heard rule-of-thumb16:37
cloudnullgenerally, the road map is dicated by specs16:37
palendae"It's a big change, changes a default"16:37
cloudnulland not set16:37
cloudnullbut we dont really have much in the way of specs, yet16:37
cloudnullin this case I'd say fernet hits master , and its backported to kilo, which changes the default token provider in a big way so we rev.16:38
cloudnulland 11.0.4 becomes 11.1.016:38
Sam-I-Amso... why did we go with fernet?16:39
Sam-I-Am(on a side note)16:39
cloudnullits faster, and ha.16:39
*** ivar-lazzaro has joined #openstack-meeting-416:39
odyssey4meI agree with that as a strategy, but I kinda think that perhaps we should pile-up a few things before we declare a minor rev16:39
palendaecloudnull: Ok16:39
dolphmSam-I-Am: performance, infrastructure overhead, scalability16:39
cloudnulldolphm: -cc16:39
palendaeodyssey4me: I agree with that too16:39
odyssey4meAnd yes, perhaps the switch to fernet tokens should be covered by a spec to infom people why16:39
palendaeSo fernet as default goes in 11.1.0, but it's not the only thing16:39
*** lbragstad has joined #openstack-meeting-416:40
cloudnullthis is what we have so far in 11.0.416:40
odyssey4meeven if the spec is a small one16:40
Sam-I-Amdolphm: ok, figured as much16:40
cloudnull#link https://launchpad.net/openstack-ansible/+milestone/11.0.416:40
*** gchamoul is now known as strider|afk16:40
*** yamahata has quit IRC16:40
cloudnullwe have quite a few "features" targetting 11.0.416:41
palendaeodyssey4me: Agreed with a spec16:41
cloudnullIE cinder on metal, keystone ssl, fernet, etc...16:41
*** VW_ has joined #openstack-meeting-416:41
odyssey4mecloudnull fair enough - I think it may be worth shifting those to a new milestone and seeing how that looks16:42
dolphmcloudnull: are they targeted to the milestone?16:42
cloudnullthey are16:42
cloudnull11.0.416:42
dolphmthere's no Wishlist bugs or blueprints16:42
cloudnullnope.16:42
odyssey4meyep - we seem to have adopted a strategy of not marking things as wishlist any more16:42
dolphmthen there's clearly no features being tracked against 11.0.4!16:43
*** bobmel_ has quit IRC16:43
palendaeSo many things went wishlist we never touched them16:43
odyssey4methis is a bad habit16:43
* cloudnull still sifting through them16:43
palendaeYeah16:43
palendaeIt is16:43
*** mickeys has joined #openstack-meeting-416:43
palendaeWe swung the opposite direction16:43
palendaeSo many things not marked wishlist, we never touch them :)16:43
*** bobmel has joined #openstack-meeting-416:43
*** TravT has quit IRC16:43
cloudnulli agree with specs being created.16:44
odyssey4mewishlist items should be small feature changes - the rest should be blueprints and the bigger ones with specs16:44
odyssey4meI think we should create a 11.1 milestone - move the ones that look like features to it, then decide on which become specs and which become wishlist items16:44
cloudnull++16:45
dolphmthere's not much point to a blueprint without a spec, given how broken blueprints are on their own. how to draw the line between the two is another story...16:45
palendaeodyssey4me: +116:45
odyssey4mewe're too easily falling into the trap of letting everything be a bug and we need to get more disciplined about this16:45
cloudnullso with that said we need people to write these specs and will need to do it retro actively for the items that we have had in the queue for a while16:45
cloudnullexample16:46
cloudnull#link https://bugs.launchpad.net/bugs/145523816:46
openstackLaunchpad bug 1455238 in openstack-ansible "Ceph Support" [Medium,In progress] - Assigned to Serge van Ginderachter (svg)16:46
cloudnullso who, with me, is going to do this ?16:47
cloudnulldont all speak at once. . .16:47
*** VanL has quit IRC16:48
cloudnullso maybe we do this going forward ?16:48
*** bobmel has quit IRC16:48
odyssey4mecloudnull I'll be happy to assist after the federation sprints are done, so that'll be in around 2-3 weeks :/16:48
*** puranamr has joined #openstack-meeting-416:48
cloudnullok so if nobody wants to help write specs then im inclided to say that we do it from NOW on. and mark all of the "features" as wishlist which will be merged into 11.1.016:49
odyssey4mecloudnull I think that's fair16:50
cloudnullgoing once.16:50
cloudnullgoing twice.16:50
palendaeThat also means we (cores especially) need to be vigilant about pushing back when someone doesn't propose a spec16:50
palendaeYou want it, you spec it16:50
odyssey4mepalendae yep16:50
*** xingchao_ has joined #openstack-meeting-416:50
cloudnulland sold.16:50
hughsaundersbang?16:50
palendaeWe can help, but shouldn't do it for you16:50
cloudnullfrom this day forth no spec, no feature. everything in the pipline will be makred as wishlist and handled in our current targetted milestones.16:51
palendaeSo say we all16:51
b3rnard0by your command16:51
cloudnullnext16:51
cloudnull#topic Discuss https://review.openstack.org/189998 (Fernet token support for keystone) odyssey4me16:52
*** openstack changes topic to "Discuss https://review.openstack.org/189998 (Fernet token support for keystone) odyssey4me (Meeting topic: OpenStack Ansible Meeting)"16:52
cloudnulli think we can do this with the same pattern we're using for the swift ring distribution .16:52
cloudnullin terms of rotation.16:52
odyssey4meSo currently the patch we have has 3 keys, and only rotates when the playbook for installing keystone is run.16:52
*** Swami has joined #openstack-meeting-416:52
cloudnullin the proposed default patch its been set to 716:53
cloudnullhttps://review.openstack.org/#/c/193729/15/playbooks/roles/os_keystone/defaults/main.yml16:53
svgback16:53
odyssey4meI'm in favor of the keystone user having ssh keys and the keys being distributed on rotation in something like a cron job.16:53
cloudnulls/proposed/merged16:53
cloudnullodyssey4me:  me too.16:54
cloudnullwhich will also get rid of the need to sync back the keys to the deploy host.16:54
cloudnulland then distribute16:54
odyssey4meI think that this should form part of the 'feature' for 11.1 and we shouldn't release 11.1 until that's done as it's a key requirement for making this production ready16:54
cloudnulldone.16:54
cloudnulli am in agreement.16:55
odyssey4mealright, so who's going to do it? sigmavirus24_awa ?16:55
cloudnullim happy to bang it out. i know the swift code failly well .16:56
cloudnulland it shouldnt take much to get it in16:56
odyssey4mecloudnull cool, thanks :)16:56
*** jwagner_away is now known as jwagner16:56
cloudnullso last 5 min.16:57
cloudnull#topic open16:57
*** openstack changes topic to "open (Meeting topic: OpenStack Ansible Meeting)"16:57
odyssey4meopen bar, perhaps?16:57
cloudnullanything that we want to talk about ?16:57
cloudnullopen bar would be nice !16:57
dolphmi just finished re-assigning a few bug priorities to wishlist in https://launchpad.net/openstack-ansible/+milestone/11.0.4, none are committed yet though, so it's still sane to release 11.0.4 at the moment16:58
*** harshs_ has joined #openstack-meeting-416:58
cloudnulltyvm dolphm!16:58
*** ativelkov has left #openstack-meeting-416:59
*** xingchao_ has quit IRC16:59
*** sankarshan is now known as sankarshan_away16:59
cloudnullok we're done here.16:59
cloudnull#endmeeting16:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:59
openstackMeeting ended Thu Jun 25 16:59:46 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-06-25-16.01.html16:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-06-25-16.01.txt16:59
cloudnullthanks everyone !16:59
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-06-25-16.01.log.html16:59
*** cathy_ has joined #openstack-meeting-416:59
vikram_hi17:00
*** TheIntern has left #openstack-meeting-417:00
s3wonghello17:00
*** praveens has joined #openstack-meeting-417:00
*** TheIntern has joined #openstack-meeting-417:00
*** harshs has quit IRC17:01
*** harshs_ is now known as harshs17:01
*** igordcard_ has joined #openstack-meeting-417:01
*** mohankumar__ has joined #openstack-meeting-417:01
*** TheIntern has left #openstack-meeting-417:01
*** dwalleck has joined #openstack-meeting-417:01
s3wongcathy_: src meeting?17:01
*** johnsom has joined #openstack-meeting-417:01
s3wong*sfc17:01
*** Brian has joined #openstack-meeting-417:01
cathy_#startmeeting service_meeting17:01
openstackMeeting started Thu Jun 25 17:01:58 2015 UTC and is due to finish in 60 minutes.  The chair is cathy_. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:02
*** openstack changes topic to " (Meeting topic: service_meeting)"17:02
openstackThe meeting name has been set to 'service_meeting'17:02
cathy_#startmeeting service_chaining17:02
openstackcathy_: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.17:02
cathy_#endmeeting service_meeting17:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:02
openstackMeeting ended Thu Jun 25 17:02:34 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/service_meeting/2015/service_meeting.2015-06-25-17.01.html17:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/service_meeting/2015/service_meeting.2015-06-25-17.01.txt17:02
openstackLog:            http://eavesdrop.openstack.org/meetings/service_meeting/2015/service_meeting.2015-06-25-17.01.log.html17:02
*** praveens1 has quit IRC17:02
cathy_#startmeeting service_chaining17:02
openstackMeeting started Thu Jun 25 17:02:46 2015 UTC and is due to finish in 60 minutes.  The chair is cathy_. Information about MeetBot at http://wiki.debian.org/MeetBot.17:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:02
*** openstack changes topic to " (Meeting topic: service_chaining)"17:02
openstackThe meeting name has been set to 'service_chaining'17:02
cathy_hi everyone17:03
s3wonghello17:03
*** Sam-I-Am has left #openstack-meeting-417:03
johnsomo/17:03
vikram_hi cathy17:03
mohankumar__Hi :-)17:03
cathy_vikram_: welcome back17:03
Swamihi17:03
vikram_:)17:03
cathy_OK, let's go to topic #117:03
vikram_:)17:03
*** sballe has joined #openstack-meeting-417:03
cathy_#topic Neutron port chain API spec discussion17:04
*** openstack changes topic to "Neutron port chain API spec discussion (Meeting topic: service_chaining)"17:04
*** jwarendt has joined #openstack-meeting-417:04
*** DericHorn-HP has joined #openstack-meeting-417:05
cathy_I see comments some of us have posted and also replies to comments. Any questions on the replies?17:05
*** odyssey4me has left #openstack-meeting-417:05
s3wongso it seems like Louis just updated the spec17:05
mohankumar__Hi Cathy .. python client cli changes completed .. and submitted for review ..17:06
cathy_s3wong: I replied to your comments. Are you OK with them?17:06
ajmillero/17:06
cathy_mohankumar__: great, let's go to that in our next topic17:06
s3wongcathy_: yes -- that was just a point, but no need to address from the get-go (regarding multiple port-chains on the same port that may have overlapping classifier matches)17:07
cathy_s3wong: OK, good.17:07
Swamimohankumar__: are you talking about the python neutronclient changes for the api17:07
*** yamahata has joined #openstack-meeting-417:07
cathy_any other questions/comments we would like to discuss in this IRC meeting?17:08
mohankumar__Yes ..17:08
SwamiIs this in the spec doc17:08
cathy_Swami: yes. it is the python neutron client changes17:08
mohankumar__Swami yes .. some addition I did for list and show clis17:09
Swamimohankumar__: thanks17:09
vikram_i would like everyone to provide their views on https://etherpad.openstack.org/p/flow-classifier17:09
cathy_yes, please go to the etherpad to provide your input and we can update the neutron port chain spec to include them17:10
cathy_vikram_: thanks for setting that up17:10
vikram_cathy: thanks17:11
*** dwalleck has quit IRC17:11
vikram_i feel once the BP is approved we can start the work about flow classifier otherwise rework will be more17:12
s3wongcathy_, vikram_: is the generic classifier a different project altogether from SFC?17:12
cathy_in our last meeting, we agree on a time to finalize the port chain API which is yesterday. So I would suggest that everyone go to the updated spec and review it again, post comments if you have more or give it +1  if you feel we can start implementing the API17:12
cathy_s3wong: no17:12
Swamivikram_: but we need to get a consensus on the flow classifier before we start our work or that can be done in parallel.17:13
cathy_the generic classifier will be included in our SFC spec17:13
vikram_swami: i feel we can start the work in parallel..17:14
cathy_s3wong: good question.  flow classifier is a key part of the SFC delivery and we can not say we deliver SFC without the classifier.17:14
s3wongcathy_: and it will be part of the work item for Liberty?17:14
cathy_s3wong: Yes, we are targeting that that release.17:14
vikram_BTW, i want to start with the existing proposal so that i will be ready with the changes when others needs it17:14
cathy_s3wong: the project has been officially accepted by Neutron17:14
Swamivikram_: ok, but that might cause more changes to the code who is implimenting the classifier. But if you thing that other parts of the sfc can proceed and classifier can catch then it makes sense.17:15
cathy_Now it all depends when we can get the code completed and integration testing completed.17:15
s3wongcathy_: so we need to limit the scope for the generic classifier, and view SFC as the primary use case for now17:16
cathy_s3wong: I will work with Kyle Mestery how to release this feature17:16
cathy_s3wong: yes, agree with you17:16
*** Bjoern__ has left #openstack-meeting-417:16
*** dwalleck has joined #openstack-meeting-417:16
vikram_Swami: IMHO, the existing proposal about flow-classifier is generic and I don't feel classifier will need lot of changes17:16
Swamivikram_: is that an assumption.17:17
cathy_the functionality of the generic classifier proposed in the SFC spec will be the one we deliver and it cna be easily extended since we will implement it as a modular component that cna be used by other use cases17:17
vikram_Swami: I have read both the proposals and to me flow-classifier and classifier are almost same17:17
cathy_Swami: yes, agree with vikram. I have read both too, they are the same17:18
*** Brian has quit IRC17:18
Swamivikram_: if they are the same we need to consolidate and make it a single BP17:18
vikram_Swami: Exactly17:19
Swamicathy_: so that there is no issue later.17:19
vikram_+117:19
cathy_Swami: Maybe you would like to read them too. If you see any major difference, let's discuss in our next IRC meeting. OK with you?17:19
Swamivikram_: that is what I mentioned by getting consensus with different BP owners.17:19
vikram_i will be working with Yuji and merge it one17:19
Swamicathy_: thanks will do.17:19
cathy_Swami: should be no issue.17:19
*** Brian has joined #openstack-meeting-417:19
vikram_Swami:+117:19
*** sdake_ has joined #openstack-meeting-417:20
*** yamahata has quit IRC17:20
cathy_vikram_: Thanks for working with Yuji!!17:20
*** yamahata has joined #openstack-meeting-417:20
cathy_I know Yuji can not join this IRC meeting and Thanks Vikram for working with him in another time slot17:20
vikram_Cathy: I have a question about the code submission17:21
vikram_what topic we need to mention in the patch17:21
*** sambetts has quit IRC17:21
vikram_and how the patches will be reviewed17:21
vikram_sorry all, if I am off topic17:22
cathy_vikram_:not sure what you mean? Isn't it service chaining17:22
Swamivikram_: topic can be "bp-networking-sfc"17:22
vikram_ok17:22
SwamiSo if all the patches go in with the same topic, it would be easy for the reviewers to sort it.17:22
vikram_+117:22
cathy_Swami: I see. Yes. makes sense17:23
cathy_shall we use "networking-sfc"?17:23
Swamiyes "bp" states that you are implementing the blueprint for "networking-sfc".17:24
*** sdake has quit IRC17:24
Swamibut if you don't want "bp" I am ok with that.17:24
Swamiend of the day it is just a "tag".17:24
*** sambetts has joined #openstack-meeting-417:24
cathy_Swami: Actually I am OK with either one. How about others? which one you prefer17:24
vikram_+1 for "networking-sfc"17:25
*** LouisF has joined #openstack-meeting-417:25
mohankumar__networking-sfc17:25
Brian+1 for 'networking-sfc'17:25
s3wongcathy_, Swami: doesn't matter, just settle on one so we are consistent. networking-sfc has less typing :-)17:25
*** bradjones has quit IRC17:26
cathy_Ok, let's use "networking-sfc"17:26
vikram_How we want to implement flow-classifier.. I feel it will be better as core-extension17:26
vikram_Any suggestion's17:27
cathy_For flow classifier, I will work with Jay Pipe to see how we position the implementation.17:27
cathy_Since he gives comment on security group. But we replied to his comments on the limitation of security group17:27
s3wongvikram_: I think we will finalize via your etherpad... given that Yuji isn't here, it may be good to finalize on the etherpad17:27
vikram_We need to conclude for coding17:27
vikram_S3wong: Make sense17:28
*** bradjones has joined #openstack-meeting-417:28
*** bradjones has quit IRC17:28
*** bradjones has joined #openstack-meeting-417:28
LouisFJay had suggested re-use of SGs instead of a flow-filter/classifier17:28
*** sdake_ is now known as sdake17:29
LouisFbut I think a separate flow-filter/classifer is a better approach17:29
s3wongcathy_, LouisF: SG rules are created to attached directly to SG, though it is a resource by itself, it isn't being used outside of SG17:30
cathy_vikram_: please bring back the discussion result with Yuji in our next IRC meeting. Basically we need to reach consensus on whether to extend security group or create a more indepenedent new flow classifier17:30
cathy_s3wong: we agree with you17:30
cathy_s3wong: that is our reply to Jay Pipe too17:30
vikram_Cathy: Sure17:31
s3wongcathy_, LouisF: in fact, a SG rule can't even be shared between two SGs, so how do we refactor that out would be quite a bit of work17:31
cathy_vikram_: what's your opinion on using SG or a new independent flow classifier?17:31
LouisFs3wong: agree, a separate FF/classifer would be better17:32
vikram_I am not familiar with Security Group in detail.. Need to dig more17:32
cathy_s3wong: exactly. I think most of us agree that we should use a separate indepenent flow classifier.17:32
*** puranamr has quit IRC17:33
cathy_Swami: are you OK with implementing a separate flow classifier instead of using the SG?17:33
Swamicathy_:+117:34
cathy_Swami: thanks17:34
s3wongcathy_, LouisF, vikram_: in fact, SG is so widely used, if we were to say add DSCP match on SG rules, it will have major regression effect17:34
*** marcusvrn1 has quit IRC17:34
s3wongit is just so unideal17:34
vikram_s3wong: that's a good point17:35
cathy_s3wong: yes, 100% agree with you.17:35
vikram_then flow classifier makes more sense as it can be extended easily17:36
*** puranamr has joined #openstack-meeting-417:36
cathy_Could you go to the spec and give it a one more review and give +1 if you think we can start implementing the API? We really need to finalize this.17:36
Briansure17:37
cathy_Let's move to next topic17:37
*** praveens has quit IRC17:37
cathy_#topic SFC code implementation17:37
*** openstack changes topic to "SFC code implementation (Meeting topic: service_chaining)"17:37
s3wongcathy_: sure17:37
LouisFs3wong: agree - changing SG rules will have regression issues17:37
*** sambetts has quit IRC17:38
cathy_mohankumar__: would you like to update on the Neutron client code status for SFC?17:38
mohankumar__Yes .. Will do17:39
vikram_https://review.openstack.org/#/c/194648/17:39
*** sambetts has joined #openstack-meeting-417:40
*** puranamr_ has joined #openstack-meeting-417:40
mohankumar__Patches submitted .. pls review17:41
Swamivikram_: mohankumar__: I would say that we should have the server side code first and the client side code comes in at the end.17:41
cathy_mohankumar__: OK, we will review it today. BTW, have you done some unit test?17:41
LouisFmohankumar__: will be testing with your code today17:41
s3wongSwami: yeah, that's normally the order...17:42
mohankumar__UT .. Will do once rework done17:42
Swami:wq!17:42
cathy_Swami: We will start implementing the server side API now. And do some testing on the client side code.17:42
mohankumar__Louis F thanks17:42
Swamicathy_: thanks17:43
*** puranamr has quit IRC17:43
*** VW_ has quit IRC17:44
cathy_mohankumar__: we will test your code. In the mean time you can start working on the Horizon part.17:45
*** SumitNaiksatam has joined #openstack-meeting-417:45
cathy_mohankumar__: vikram_ OK with you?17:45
vikram_okay17:45
mohankumar__Yeah ok17:45
cathy_mohankumar__: great. Thanks.17:46
vikram_cathy: what's the plan on BP approval17:47
cathy_Is Nicolas in this meeting? We can discuss about application ID he suggested if he is in this meeting17:47
cathy_seems he is not in the meeting.17:47
cathy_Any thing else anyone would like to discuss? Otherwise I will summarize the action items17:48
*** padkrish has joined #openstack-meeting-417:48
vikram_cathy: what's the plan on BP approval17:48
*** Mohankumar_ has joined #openstack-meeting-417:50
*** puranamr_ has quit IRC17:51
*** puranamr has joined #openstack-meeting-417:51
*** vikram_ has quit IRC17:52
cathy_vikram_: good question. After people giving -1 change to +1, I can start approve it and then I will ask Kyle and armax to approve too. SFC project has a separate core team to approve the BP.17:53
*** marcusvrn has joined #openstack-meeting-417:53
*** vikram_ has joined #openstack-meeting-417:53
cathy_Now let me summary the agreement and action items for this IRC meeting17:53
s3wongcathy_: right, SFC specs go into SFC repo, so it should be +2/+A by SFC cores17:54
cathy_#agree we reached consensus on the flow classifier in this meeting: we will implement a separate independent flow classifier instead of using/extending SG. Vikram will bring back consensus with Yuji in next IRC meeting17:54
*** irenab has joined #openstack-meeting-417:55
cathy_#action Everyone review the Client API codes for SFC and  test the API with Server side API17:56
cathy_#agree topic for the code patches: networking-sfc17:57
cathy_s3wong: yes.17:58
*** mitchjameson has joined #openstack-meeting-417:58
cathy_Ok, thanks everyone for joining the meeting, Let's discuss more in next IRC meeting. Bye now17:58
*** fallenpegasus has quit IRC17:58
Brianbye17:58
Swamibye17:58
s3wongbye17:58
LouisFbye17:58
Mohankumar_Bye17:58
xgermanbye17:58
cathy_#endmeeting17:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:59
openstackMeeting ended Thu Jun 25 17:59:05 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/service_chaining/2015/service_chaining.2015-06-25-17.02.html17:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/service_chaining/2015/service_chaining.2015-06-25-17.02.txt17:59
openstackLog:            http://eavesdrop.openstack.org/meetings/service_chaining/2015/service_chaining.2015-06-25-17.02.log.html17:59
vikram_bye17:59
*** vikram_ has quit IRC18:00
*** johnsom has left #openstack-meeting-418:00
*** ivar-lazzaro has quit IRC18:00
*** fitoduarte has joined #openstack-meeting-418:00
fitoduartehere18:01
*** husanu7 has joined #openstack-meeting-418:02
*** dontalton has joined #openstack-meeting-418:02
*** Sukhdev has quit IRC18:03
*** Mohankumar_ has quit IRC18:03
*** Brian has quit IRC18:03
*** VW_ has joined #openstack-meeting-418:03
*** TheIntern has joined #openstack-meeting-418:03
*** VW_ has quit IRC18:05
*** VW_ has joined #openstack-meeting-418:05
*** Sukhdev has joined #openstack-meeting-418:07
*** dwalleck has quit IRC18:11
*** puranamr has quit IRC18:13
*** husanu7 has quit IRC18:14
*** cathy_ has quit IRC18:14
*** puranamr has joined #openstack-meeting-418:16
*** fallenpegasus has joined #openstack-meeting-418:17
*** harshs has quit IRC18:17
*** harshs has joined #openstack-meeting-418:18
*** dwalleck has joined #openstack-meeting-418:21
*** DericHorn-HP has quit IRC18:31
*** krtaylor has quit IRC18:31
*** VanL has joined #openstack-meeting-418:37
*** VW_ has quit IRC18:37
*** timsim has joined #openstack-meeting-418:38
*** dwalleck has quit IRC18:39
*** VW_ has joined #openstack-meeting-418:43
*** LouisF has quit IRC18:43
*** dontalton has quit IRC18:44
*** VW_ has quit IRC19:01
*** VW_ has joined #openstack-meeting-419:02
*** VW_ has quit IRC19:03
*** VW_ has joined #openstack-meeting-419:03
*** singlethink has joined #openstack-meeting-419:09
*** singleth_ has joined #openstack-meeting-419:10
*** padkrish has quit IRC19:12
*** padkrish has joined #openstack-meeting-419:12
*** singlethink has quit IRC19:13
*** padkrish has quit IRC19:16
*** VanL has quit IRC19:23
*** padkrish has joined #openstack-meeting-419:25
*** rromans has left #openstack-meeting-419:25
*** s3wong has quit IRC19:31
*** mickeys has quit IRC19:33
*** ajayaa has quit IRC19:38
*** dwalleck has joined #openstack-meeting-419:39
*** TheIntern has left #openstack-meeting-419:40
*** daneyon_ has quit IRC19:42
*** dwalleck has quit IRC19:44
*** lyarwood has quit IRC19:45
*** lyarwood has joined #openstack-meeting-419:45
*** GB22 has joined #openstack-meeting-419:46
*** DericHorn-HP has joined #openstack-meeting-419:50
*** GB22 has quit IRC19:50
*** wko has quit IRC19:51
*** lyarwood has quit IRC19:51
*** padkrish has quit IRC19:51
*** lyarwood has joined #openstack-meeting-419:52
*** padkrish has joined #openstack-meeting-419:52
*** padkrish has quit IRC19:53
*** padkrish has joined #openstack-meeting-419:53
*** VanL has joined #openstack-meeting-419:57
*** VW_ has quit IRC19:59
*** Shamail has joined #openstack-meeting-419:59
*** VW_ has joined #openstack-meeting-420:03
*** Sukhdev has quit IRC20:07
*** mohankumar__ has quit IRC20:08
*** krtaylor has joined #openstack-meeting-420:09
*** padkrish has quit IRC20:15
*** padkrish has joined #openstack-meeting-420:15
*** gabriel-bezerra has quit IRC20:17
*** SumitNaiksatam has quit IRC20:18
*** SumitNaiksatam has joined #openstack-meeting-420:18
*** VW_ has quit IRC20:18
*** gabriel-bezerra has joined #openstack-meeting-420:20
*** sdake_ has joined #openstack-meeting-420:24
*** sdake has quit IRC20:28
*** sdake_ is now known as sdake20:29
*** padkrish has quit IRC20:33
*** mickeys has joined #openstack-meeting-420:34
*** marcusvrn has quit IRC20:34
*** dwalleck has joined #openstack-meeting-420:41
*** Shamail has quit IRC20:42
*** padkrish has joined #openstack-meeting-420:44
*** dwalleck has quit IRC20:45
*** sarob_ has joined #openstack-meeting-420:46
*** puranamr_ has joined #openstack-meeting-420:46
*** GB21 has quit IRC20:47
*** sarob has quit IRC20:49
*** puranamr has quit IRC20:49
*** padkrish has quit IRC20:57
*** padkrish has joined #openstack-meeting-420:57
*** ivar-lazzaro has joined #openstack-meeting-421:01
*** padkrish has quit IRC21:02
*** dannywilson has joined #openstack-meeting-421:02
*** ivar-lazzaro has quit IRC21:02
*** ivar-lazzaro has joined #openstack-meeting-421:03
*** dannywil_ has quit IRC21:05
*** padkrish has joined #openstack-meeting-421:05
*** DericHorn-HP has quit IRC21:08
*** kobis has joined #openstack-meeting-421:09
*** jwagner is now known as jwagner_away21:11
*** DericHorn-HP has joined #openstack-meeting-421:11
*** VW_ has joined #openstack-meeting-421:20
*** mickeys has quit IRC21:34
*** mickeys has joined #openstack-meeting-421:34
*** kobis has quit IRC21:36
*** hogepodge has quit IRC21:38
*** padkrish has quit IRC21:40
*** padkrish has joined #openstack-meeting-421:41
*** singleth_ has quit IRC21:42
*** dwalleck has joined #openstack-meeting-421:45
*** krtaylor has quit IRC21:47
*** VanL has quit IRC21:50
*** padkrish has quit IRC21:51
*** padkrish has joined #openstack-meeting-421:51
*** padkrish_ has joined #openstack-meeting-421:56
*** padkrish has quit IRC21:56
*** dannywilson has quit IRC22:01
*** dannywilson has joined #openstack-meeting-422:02
*** dannywilson has quit IRC22:02
*** dannywilson has joined #openstack-meeting-422:03
*** Rockyg has joined #openstack-meeting-422:04
*** klamath has quit IRC22:06
*** padkrish_ has quit IRC22:13
*** dwalleck has quit IRC22:22
*** xingchao_ has joined #openstack-meeting-422:23
*** mickeys has quit IRC22:23
*** padkrish has joined #openstack-meeting-422:29
*** dims has quit IRC22:30
*** krtaylor has joined #openstack-meeting-422:30
*** padkrish has quit IRC22:31
*** dontalton has joined #openstack-meeting-422:32
*** dwalleck has joined #openstack-meeting-422:33
*** xingchao_ has quit IRC22:33
*** IlyaG has joined #openstack-meeting-422:35
*** dims_ has joined #openstack-meeting-422:38
*** carl_baldwin has quit IRC22:41
*** armax has quit IRC22:45
*** DericHorn-HP has quit IRC22:45
*** dontalton has quit IRC22:45
*** dhellmann has quit IRC22:46
*** dhellmann has joined #openstack-meeting-422:46
*** dwalleck has quit IRC22:49
*** armax has joined #openstack-meeting-422:51
*** VW_ has quit IRC22:53
*** hogepodge has joined #openstack-meeting-422:58
*** sdake_ has joined #openstack-meeting-423:00
*** sdake has quit IRC23:04
*** sdake has joined #openstack-meeting-423:07
*** mestery has quit IRC23:07
*** fallenpegasus has quit IRC23:09
*** sdake_ has quit IRC23:11
*** Sukhdev has joined #openstack-meeting-423:21
*** armax has quit IRC23:24
*** markvoelker has quit IRC23:24
*** Swami has quit IRC23:49
*** puranamr_ has quit IRC23:53
*** sdake has quit IRC23:54
*** sdake has joined #openstack-meeting-423:55
*** Sukhdev has quit IRC23:56
*** Rockyg has quit IRC23:57

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