Thursday, 2015-06-11

*** Swami_ has joined #openstack-meeting-400:04
*** Sukhdev has quit IRC00:07
*** Sukhdev has joined #openstack-meeting-400:07
*** Swami has quit IRC00:08
*** nateziemann has quit IRC00:09
*** belmoreira has joined #openstack-meeting-400:11
*** puranamr has quit IRC00:15
*** stevelle has joined #openstack-meeting-400:17
*** sarob has quit IRC00:20
*** rfolco has quit IRC00:24
*** dannywil_ has joined #openstack-meeting-400:30
*** amotoki has joined #openstack-meeting-400:33
*** dannywilson has quit IRC00:33
*** xingchao has quit IRC00:33
*** dannywil_ has quit IRC00:35
*** amotoki has quit IRC00:38
eglute #startmeeting DefCore01:00
hogepodgeo/01:00
markvoelkero/01:00
egluteHi Everyone! if you are attending defcore meeting, do as hogepodge and markvoelker! o/01:01
markvoelkerhmm...is meetbot down?01:01
*** hughhalf has joined #openstack-meeting-401:01
egluteis it?01:01
eglutemaybe it just does not like me01:02
markvoelker#startmeeting01:02
openstackmarkvoelker: Error: A meeting name is required, e.g., '#startmeeting Marketing Committee'01:02
markvoelker#startmeeting DefCore01:02
openstackMeeting started Thu Jun 11 01:02:37 2015 UTC and is due to finish in 60 minutes.  The chair is markvoelker. Information about MeetBot at http://wiki.debian.org/MeetBot.01:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.01:02
*** openstack changes topic to " (Meeting topic: DefCore)"01:02
openstackThe meeting name has been set to 'defcore'01:02
*** zehicle has joined #openstack-meeting-401:02
purpo/01:02
markvoelker#chair eglute01:02
openstackCurrent chairs: eglute markvoelker01:02
hughhalf.01:02
zehicleo/01:02
markvoelker#chair zehicle01:03
openstackCurrent chairs: eglute markvoelker zehicle01:03
eglutethanks, it didnt like me then.01:03
zehicle#link https://etherpad.openstack.org/p/DefCoreFlag.301:03
markvoelkerno problem....I'll turn it over to you to drive now. =)01:03
eglutethank you markvoelker01:03
zehicleroll call pleasde01:03
*** dwalleck has joined #openstack-meeting-401:03
egluteo/01:04
zehicleplease indicate your time zone also, I'd like to make sure that we're accomplishing our objective01:04
zehicleo/  Central01:04
egluteo/ CST01:04
markvoelkero/ EDT01:04
*** bknudson has joined #openstack-meeting-401:04
dwallecko/ CST01:04
hughhalfo/ AEST - GMT+10 (Canberra Australia)01:04
hogepodgeo/ PDT01:04
purpPDT01:05
purpo/ PDT01:05
eglutesomeone emailed the list and said this time does not work for him, he is in GMT +1201:05
zehicleyy, that's Robert01:05
eglutey01:05
zehicleok, I'm thinking to follow the agenda on the ether pad01:06
zehicleplease make additions/changes there and we'll incorporate it01:06
eglutesounds good01:06
zehicle#topic mid-cycle meeting01:06
*** openstack changes topic to "mid-cycle meeting (Meeting topic: DefCore)"01:06
zehicleI'd like to have use close (or have a plan to close) the location & timing01:07
zehicledo we have quorum to do that here?01:07
purpChecked in with mtreinish; he's looking at late July/early August. Trying to sync with infra midcycle01:07
zehicleWe've got some block out times: OSCON & OpenStack BoD01:08
eglutezehicle regarding quorum, we had some people last week that said they would travel, some are not here right now01:08
zehicleyy01:08
zehicleI suspect that we cannot close it tonight.  if so, can we get it down to two choices?01:08
zehiclemaybe 301:09
purpSeems reasonable.01:09
eglutemy concern with waiting too long is that then we are at timeline July 27 (Summit - 3 months)01:09
* zehicle gets his calendar out01:09
egluteBoD is on July 28th (Tuesday), oscon week before that01:09
purpWeek of July 6?01:10
purpToo early?01:10
zehicleI'm on vacation th week after01:10
zehicleand traveling the week of July 601:10
zehicleSo, 7/13 week01:10
zehicleCould we plan it like this:01:10
zehicle1) SJC week of 7/1301:11
zehicle2) PDX week of 7/2001:11
zehicle3) ATX week of 7/2701:11
zehiclewith a target dates of Wed-Thurs01:11
egluteworks for me.01:11
purpI can't make 13 Jul - 13 Aug. But we knew that.01:11
*** fnaval has quit IRC01:11
egluteso doodle to the mailing list with the dates?01:12
*** Swami_ has quit IRC01:12
zehiclethat'01:12
eglute#action eglute send out doodle to the mailing list with date options01:12
zehicle#topic v1.3 schema01:13
*** openstack changes topic to "v1.3 schema (Meeting topic: DefCore)"01:13
zehicleso we merged the v1.3 schema with some discussion still potentially open01:13
egluteyes, i think there were some things that were missed.01:14
zehiclemarkvoelker, were you OK w/ the latest HACKING or did we jump the gun?01:14
eglutelots of comments on  https://review.openstack.org/#/c/185158/, so if something was missed, please submit a new patch01:14
hogepodge#link  https://review.openstack.org/#/c/185158/01:14
markvoelkerSo, I think the thing we may have overlooked was the bit where we removed the ability to drop tests completely...01:14
eglutei think there was at least one thing missed, need to find the new patch that was created that called it out01:15
egluteyeah01:15
zehicleIt looks like we've started the discussion on the new patch01:15
eglute#link https://review.openstack.org/#/c/189961/01:15
eglute^^ new patch01:15
markvoelkerI wasn't sure if that was intentional or not though01:15
eglutenot intentional!01:16
hogepodgeyup, we need to be able to drop tests from next. I had proposed a change to do that, but it didn't make it in.01:16
hogepodgewhich is part of the point of next, to resolve outstanding flags.01:16
markvoelkerOk, so that should be relatively easy to correct01:16
markvoelkerShall I submit a patch for it, or does someone already have one in the works?01:16
eglutethe previous patch ended up with too many comments and i could not tell that something was still not resolved. so yes, we need to fix it01:17
hogepodgemarkvoelker: you should feel free to do that01:17
eglute#action markvoelker submit a patch to fix process for removing tests01:17
hogepodgeI don't have one in the works that's ready to go01:17
zehicleI'd like to make sure that the patch w/ the flags stays about flags01:17
eglute+101:17
zehicledo we have tests that need to be removed?  where did they go?01:17
*** pshige has quit IRC01:18
markvoelkerzehicle: Yes, see https://review.openstack.org/#/c/189961/01:18
hogepodgezehicle: yes, there are tests that are hypervisor specific01:18
*** dims_ has joined #openstack-meeting-401:18
zehiclesoundn't we keep the tests but flag them?01:18
hogepodgeand this https://review.openstack.org/#/c/189979/01:18
hogepodgeIn next? No.01:19
zehicleI thought that was the purpose of the flags?01:19
eglutei think the hypervisor one should be dropped, based on the discussions01:19
zehicleI'm worried about having tests in the system that don't show up01:19
markvoelkerzehicle: these are tests for capabilities that never should have been DefCore in the first place b/c they fail Core Criteria01:19
zehicle+1 on that01:19
markvoelkerSo we could keep them...forever...01:19
zehicleexcept that they would be flags01:19
hogepodgeMy understanding is that a required test is something we want, and that the actions on a flag are to fix or remove.01:19
markvoelkerBut that would just create clutter and we'd have to re-evaluate them every cycle01:19
markvoelkerWhcih seems like a waste of resources01:19
zehiclenot if the flag reason was clear01:20
zehicleOR... could we put them into a capability?01:20
zehicleI'm worried that we're going to have them pop up every cycle for review01:20
eglutein hypervisor case, it would not meet the common use case01:20
zehicleI'd rather make a decision about them one time and let it ride01:20
hogepodgeconfusing to end users. I've been telling vendors that a flag means a capability is required, but has a problematic test.01:20
zehiclethat still seems like a "compute-hypervisor-vendor-specific" capability01:21
markvoelkerzehicle: so we had recently decided that we were going to re-evaluate all flagged tests at the beginning of every cycle.01:21
zehiclethen the cap is NOT required01:21
hogepodgezehicle: if that's the case I misunderstood the purpose then01:21
purpThis seems to point up the need for multiple flag types. No?01:21
zehicleI'01:21
markvoelkerSo if we just leave them in the flag list indefinitely we're going to be re-evaling them indefinitely01:21
markvoelkerAnd that list is going to get longer and longer01:21
zehicleI'm happy to discuss.... my understanding was that we'd eventually list _every_ test01:21
hogepodgezehicle: I thought that a capability couldn't be removed in a cycle, but could in the next.01:21
*** dims has quit IRC01:21
zehiclehogepodge, so we can flag them and move them01:21
hogepodgezehicle: but it shouldn't be in the required capability list01:22
*** fnaval has joined #openstack-meeting-401:22
markvoelkerzehicle: I don't think it's feasible to list every test.  That's a moving target.01:22
dwalleckDoes it make sense to have capabilities that are driver specific? As in, if you are using a certain driver, within that context the expected behaviors are <things>01:22
hogepodgezehicle: moving I'm ok with too01:22
markvoelkerEspecially when you consider non-tempest tests01:22
zehiclemarkvoelker, eventually, it would be good to have them all tracked somehow since we want the data from all of them01:22
zehicledwalleck, we can have all sorts of capabilities.  it's helpful to users to map functionality01:23
markvoelkerzehicle: I'm saying that eventually will never come though....the tests are moving much faster than we are.01:23
zehiclewe just don't have to require them01:23
hogepodgewe have a mechanism for listing all of the tests, it's the repository the test comes from01:23
egluteis this a topic we should leave for mid-cycle?01:24
zehicleI'm OK w/ this suggestion - I have some concerns based on earlier postures01:24
*** tobe has joined #openstack-meeting-401:24
zehicleif we're thinking it's not a big deal then I'm OK to remove01:24
zehiclesince we have a lot of tests that are not covered01:24
zehicleI just want to make sure that we don't keep trying to re-add them01:25
eglutei think for now, i vote +1 to remove01:25
markvoelkerSo, how about this: I'll just propose the patch and we can discuss it there.  I'm happy to be overruled if folks think differently01:25
purpmarkvoelker: +101:25
egluteworks for me01:25
markvoelker(in fact, I thought I had been overruled when the schema change with the procedure change landed! =p)01:25
markvoelker#action markvoelker to propose patch for test removal01:26
zehicleno, we wanted to split the discussion01:26
zehiclethat's why we want to make sure to cover it here01:26
zehiclebecause we suspected that the non v1.3 issues had not been resolved01:26
eglute+1 on splitting discussions in patches as appropriate. otherwise important issues get lost01:26
zehiclebased on discussion here, it seems like v1.3 is OK01:27
markvoelkerI'll get that patch up tomorrow morning so we can get moving on it and have decision soonish so Chris's patches can move forward or be refactored01:27
zehicleand we're aware that some of the issues in that patch need further discussion01:27
egluteyes01:27
zehiclemission accomplished01:27
zehicleother discussion on v1.3 patch and related skeltons unearthed?01:27
* zehicle thinks we unblocked a lot of good discussion around flagging01:28
hogepodgeneed a proper validating schema?01:28
eglutethe skeletons might be hiding in the next topic01:28
*** dwalleck has quit IRC01:28
hogepodgeAlso, gate job to ensure json is parsable?01:28
hogepodgeand correct?01:28
zehicle#topic capabilities subdivisions01:28
*** openstack changes topic to "capabilities subdivisions (Meeting topic: DefCore)"01:28
zehiclehogepodge, +101:28
zehiclegetting more critical w/ each addition01:29
*** dwalleck_ has joined #openstack-meeting-401:29
zehicleVan was not going to make this meeting01:29
zehicleI had two items related01:30
egluteright, i think we skipped this topic last week as well01:30
zehicle1) who/when can we get the capabilities subsets done01:30
zehicle?01:30
zehicledoes someone have that list?01:30
hogepodgeIt's in a google sheet that I'm sure I can dig up a link for given enough time.01:30
zehiclethat has the correct subdivisions?01:30
zehiclehogepodge, will doing that break all your patches?01:31
hogepodgeVan and Catherine have been the primary contributors, and both aren't here (Catherine should be back next week)01:31
eglute#link https://docs.google.com/spreadsheets/d/15Fkt2n95WPPe7CYH-0WIKz3dhMeW3FW2gl5aSlamEeY/edit#gid=601:31
egluteright, i think Van will be as well01:31
hogepodgezehicle: I'm not worried about the patches, they can be rewritten if the schema updates. I wanted to reclassify the tests for discussion, and figured those patches would be long lived and require rebasing01:31
zehicleok01:32
egluteso skip this topic for now?01:32
zehicleso, can we get that subdivision done?01:32
hogepodgeIt's probably a matter of automation based on the list, so yes?01:33
zehicleI'm worried about it causing downstream work if we delay01:33
zehicleif you've got the material in that format01:33
zehicleit's really not that much data to tweak01:33
zehicleI'm thinking about 30 minutes tops01:34
zehicleso, likely less effort than automation01:34
*** xingchao has joined #openstack-meeting-401:34
zehiclethe cap list is not the question - it's the test membership01:34
zehiclethat's what was missing from the earlier patch01:34
eglutehogepodge is this something you can work on with Van and Catherine?01:35
hogepodgeI can01:35
eglutethank you hogepodge01:35
zehicleok, I see the list now01:35
eglute#action hogepodge work with Van and Catherine to subdivide capabilities01:35
*** jdziukx has quit IRC01:36
zehicledepending on the flags, they may actually be able to merge cleanly01:36
zehiclethe second part was just the we had a discussion about how to score capabilities in IRC01:37
zehiclein the #openstack-defcore channel01:37
zehiclethe short version is that Van suggested a way to vote that may work01:38
zehiclewe'll need to try it sometime soon01:38
egluteif everyone is looking at the spreadsheet, voting should work01:38
markvoelkerzehicle: got a link or a date when that happened?  Was probably while I was on PTO and I'd love to read...01:38
zehiclehogepodge, are there any new capabilities under consideration?01:38
markvoelkerI can dig in eavesdrop if not01:38
eglutemarkvoelker i think that happened over the phone?01:38
hogepodgezehicle: not that I know of immediately01:38
zehicleit was IRC01:38
zehicleyesterday I think - around 4pm Central01:39
markvoelkerOk, I'll dig and post a link if I can turn it up before end of topic01:39
zehiclewas a big burst of activity including patches around that time01:39
markvoelkerthanks01:39
eglutei missed then as well01:39
dwalleck_I'd be glad to help with capabilities as well. I should have the bandwidth01:39
*** xingchao has quit IRC01:39
zehiclewanted to make sure that people were are we'd dicussed it - we'll need to formally doc it before we try it01:39
eglutethank you dwalleck_ !01:40
zehicledwalleck_ and hogepodge I think you've got all the data you need to subdivide from the spreadsheet01:40
hogepodgemarkvoelker: https://etherpad.openstack.org/p/defcore_scoring is a log of that conversation01:40
markvoelker#link http://eavesdrop.openstack.org/irclogs/%23openstack-defcore/%23openstack-defcore.2015-06-09.log.html#t2015-06-09T20:04:0301:40
hogepodgemarkvoelker: or that too :-)01:40
markvoelker#link https://etherpad.openstack.org/p/defcore_scoring01:41
markvoelkerThanks hogepodge01:41
*** s3wong has quit IRC01:41
purpThanks hogepodge01:41
zehiclenext topic....01:41
zehicle#review hacking file (flag tests)01:41
zehicle#topic review hacking file (flag tests)01:41
*** openstack changes topic to "review hacking file (flag tests) (Meeting topic: DefCore)"01:41
zehicle20 minutes remaining and this could be the rest....01:41
zehicleother topics first?01:41
* zehicle reserves last few minutes to review the choice of time01:42
*** IlyaG has joined #openstack-meeting-401:42
eglutei think we need to resolve this... dont think other topics will be short either01:42
*** zehicle_IRL has joined #openstack-meeting-401:42
purpThis is the one I missed last week, yes?01:42
egluteyes i think so01:43
zehiclepurp, it's a long runniung thread01:43
eglutethere is a patch somewhere, let me find it01:43
* purp is jealous of the stereo zehicles.01:43
markvoelkerTo be clear, are we talking about this? https://review.openstack.org/#/c/18866101:43
zehicleyy01:43
zehicle#link https://review.openstack.org/#/c/188661/01:43
markvoelker#link https://review.openstack.org/#/c/18866101:43
egluteyes, thanks markvoelker01:43
markvoelkerSo IMHO there's not that much that's really controversial in the patch.  I made a few suggestions in the review.01:44
zehicleoh, can we cover #link https://review.openstack.org/#/c/182105/ first?01:44
markvoelkerThe big question for me is: is the list intended to be exhaustive?01:44
markvoelkerzehicle: sure01:44
zehiclemarkvoelker, I think so.  that's a good catch01:44
zehicleok, back to the 2015A patch for a minute01:44
markvoelker#link https://review.openstack.org/#/c/182105/01:45
hogepodgeOh, that's mine.01:45
zehicleI wanted to discuss my objections and make sure that we were on the same page01:45
zehicleyy, you were adding flag details to the 2015A process01:45
zehicleto an extent, we did not add those details there on purpose01:46
zehiclesince they were left to DefCore to manage01:46
zehicleI'm open to discussion that they should be part of the broader process01:46
*** IlyaG has quit IRC01:46
zehiclebut it would have to be 2015B in that case and go back to the board01:46
*** IlyaG has joined #openstack-meeting-401:47
markvoelkerYeah, I think this one predates some of the recent changes to HACKING that came in with schema 1.3.01:47
markvoelkerMuch of this is now covered there01:47
zehicleyou are correct markvoelker01:47
markvoelkerE.g. rule D307 covers what is required when flagging a test01:47
hogepodgeI'd like something to make flagging a harder thing to do01:47
hogepodgeif that's covered in hacking, fine.01:48
zehiclethat was the goal of getting written down in hacking01:48
* zehicle hacking is not the most obvious name for rules of engagement01:48
markvoelkerhogepodge: D307 basically says "everything in the current schema's flagging section is required", so I think we're good there01:48
markvoelkerI'm happy to obtain different opinions though. =)01:49
hogepodgemarkvoelker: I can't find what's in the schema though. I don't think it's documented01:49
markvoelkerhogepodge: https://github.com/openstack/defcore/tree/master/schema01:49
hogepodgemarkvoelker: ah, ok01:49
zehiclehogepodge, I moved it so we could track versions01:49
zehiclesince I was changing a lot of comments when I was fixing the readme01:50
*** belmoreira has quit IRC01:50
zehicleI just wanted to resolve if we felt there was a process change beyond hacking required01:50
hogepodgehacking needs more guidance along the lines of what I wrote, but is that part of what markvoelker is going to send up as part of his action item?01:51
markvoelkerhogepodge: guidance about when a flag can be removed, or...?01:52
zehicleI have no issues adding the rules01:52
zehiclemy concern was about where01:52
zehicle2015B would be the right place if we wanted it at the board level01:52
zehicleHacking is right if we think we can hold the line01:53
eglutesome flagging guidance should be in 2015B i think01:53
eglutebut maybe not as detailed01:53
markvoelkerzehicle: I'm of the opinion that this level of detail isn't of interest to the Board.  But then, I'm not on the Board. =)01:53
hogepodgeplus info about removing tests in next (or not)01:53
zehicle+101:53
zehiclethere are some items that the process leaves to defcore01:54
dwalleck_hackings have always been a good "how do I work within this project" place to me01:54
markvoelkerhogepodge: I'll definitely hit the removal of tests in .next in my patch01:54
egluteso sounds like everyone in favor of when to flag and what, when to remove to put hacking doc?01:54
purpAgree.01:54
zehicletest membership and flagging are both in that category01:54
egluteshould we create a separate flagging process doc?01:54
zehicleI01:55
zehicleI'm ok w/ them in hacking - since it's central01:55
egluteok01:55
zehiclelet's collect them there and see if we need more01:55
markvoelkereglute: I thought about that, but came around to kind of liking it in HACKING01:55
hogepodgefive minute warning01:55
zehicleas long as we all agree with the location, the name of the file works for me01:55
markvoelkerBasically b/c I suspect the flagging process is an area where people not routinely involved in DefCore will want to interact with us01:55
eglutemarkvoelker ok, that works for me if we have consensus. most important to have them somewhere :)01:55
markvoelkerand HACKING is, as dwalleck_ pointed out, where to look for info about how to interact with a project01:56
zehicleeasy enough to xlink in the readme01:56
egluteworks for me then01:56
zehicleok, my topic on that patch took most of the time.  sorry01:56
purp+1 HACKING01:56
zehiclemarkvoelker, +1 on adding a "list is comprehensive" statement01:56
zehiclewe don't want flag to be allowed because we did not think of a reason to block them01:57
zehicleif a new reason surfaces then we can discuss01:57
zehicleexcept for pixie dust01:57
zehiclenot up for discussion01:57
egluteflag neutron: because of pixie dust.01:58
zehicle#topic is this time working?01:58
*** openstack changes topic to "is this time working? (Meeting topic: DefCore)"01:58
zehiclejust a check01:58
markvoelkerzehicle: I'm also curious about the difference b/t D401 and D402.  Didn't really seem to be one?01:58
purpHard for PDT ... family dinner hour.01:58
zehicledid we get additional audience based on the time?01:59
egluteno, less people01:59
purpmarkvoelker: I read D401 as "inadequately tests" and D402 as "test fails inappropriately"01:59
markvoelkertime is ok for me...note that we have an AI to re-eval this in ~a month to see if it's working01:59
zehicledwalleck_, you are our rep from alternate time zone01:59
eglutedwalleck_ is in CST01:59
dwalleck_yup01:59
zehicleoh, sorry01:59
purpThat's pretty alternate. I've been there.01:59
dwalleck_Though the nice thing about this time is that it's not possible to conflict with anything else :)01:59
eglutewe do have someone from Australia02:00
zehiclewho was our02:00
hogepodgehughhalf: is in australian time zone02:00
dwalleck_well, work conflict02:00
markvoelkerpurp: hrm.  I guess I read both as "the test is borked". =)02:00
zehicleit was hughhalf02:00
*** qwebirc34788 has joined #openstack-meeting-402:00
eglutehughhalf what do you think?02:00
hogepodgeAEST - GMT+10 (Canberra Australia)02:00
hughhalfSorry, stepped away, one mo please02:00
zehicleI think you've answered the question02:00
hughhalfDoorbell rang! :)02:01
purpHeh.02:01
egluteok, we will try couple more times and then re-evaluate i think!02:01
*** marcusvrn has joined #openstack-meeting-402:01
zehicleeglute, +102:01
hogepodgeany meetings following this? please tell us to vacate if so.02:01
eglutewe agreed to give it a month02:01
hughhalfSo yes, this time is ok for me02:01
zehiclejust wanted to test it at the end02:01
zehiclenot suggesting a change02:01
* hughhalf nods02:01
purp#action purp will ping Robert to see what times work better (due before end of June)02:02
zehiclewe're done02:02
eglutethank you everyone!02:02
markvoelkerzehicle: did you want me to propose a new patchset for https://review.openstack.org/#/c/188661/3/HACKING.rst or did you want to?02:02
zehicleany addition discussion, we'll be on regular channel02:02
* hughhalf notest that fwiw a time that will work for Robert will likely work for most Oz folk too.02:02
hughhalfthanks all02:02
zehiclemarkvoelker, go ahead02:02
zehicleI was just getting it started02:02
zehicle#endmeeting02:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"02:02
openstackMeeting ended Thu Jun 11 02:02:48 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)02:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/defcore/2015/defcore.2015-06-11-01.02.html02:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/defcore/2015/defcore.2015-06-11-01.02.txt02:02
markvoelkerok, I'll tee that up for tomorrow after the other one then.  Thanks02:02
openstackLog:            http://eavesdrop.openstack.org/meetings/defcore/2015/defcore.2015-06-11-01.02.log.html02:02
*** KunalGandhi has quit IRC02:04
*** VW has joined #openstack-meeting-402:06
*** Sukhdev has quit IRC02:07
*** fallenpegasus has joined #openstack-meeting-402:07
*** Swami has joined #openstack-meeting-402:10
*** sbalukoff has quit IRC02:11
*** rhallisey|PTO has quit IRC02:13
*** amotoki has joined #openstack-meeting-402:21
*** rhallisey|PTO has joined #openstack-meeting-402:23
*** rhallisey|PTO has left #openstack-meeting-402:26
*** dwalleck_ has quit IRC02:30
*** IlyaG has quit IRC02:32
*** juggler has quit IRC02:33
*** dims_ has quit IRC02:33
*** juggler has joined #openstack-meeting-402:33
*** amotoki has quit IRC02:40
*** tobe has quit IRC02:46
*** tobe has joined #openstack-meeting-402:47
*** kenhui has quit IRC02:48
*** bknudson has left #openstack-meeting-402:49
*** tobe has quit IRC02:50
*** ajayaa has joined #openstack-meeting-402:51
*** tobe has joined #openstack-meeting-402:51
*** yamahata has quit IRC03:00
*** Swami_ has joined #openstack-meeting-403:02
*** david-lyle has joined #openstack-meeting-403:04
*** Swami has quit IRC03:05
*** dims has joined #openstack-meeting-403:34
*** Swami_ has quit IRC03:44
*** amotoki has joined #openstack-meeting-403:49
*** ajayaa has quit IRC03:58
*** tobe has quit IRC04:04
*** tobe has joined #openstack-meeting-404:13
*** ajayaa has joined #openstack-meeting-404:15
*** numan has joined #openstack-meeting-404:22
*** irenab has quit IRC04:23
*** marcusvrn has quit IRC04:24
*** markvoelker has quit IRC04:26
*** Swami has joined #openstack-meeting-404:42
*** ivar-laz_ has joined #openstack-meeting-404:44
*** ivar-lazzaro has quit IRC04:48
*** ivar-laz_ has quit IRC04:49
*** stevelle has left #openstack-meeting-404:49
*** ajayaa has quit IRC04:50
*** tobe has quit IRC04:56
*** sdake has joined #openstack-meeting-404:56
*** fnaval has quit IRC04:58
*** puranamr has joined #openstack-meeting-404:58
*** tobe has joined #openstack-meeting-405:01
*** ajmiller_ has quit IRC05:05
*** ajmiller has joined #openstack-meeting-405:06
*** puranamr has quit IRC05:07
*** VW has quit IRC05:07
*** lazy_prince has joined #openstack-meeting-405:11
*** simon-AS559 has joined #openstack-meeting-405:15
*** xingchao has joined #openstack-meeting-405:15
*** irenab has joined #openstack-meeting-405:20
*** belmoreira has joined #openstack-meeting-405:22
*** xingchao has quit IRC05:22
*** markvoelker has joined #openstack-meeting-405:27
*** markvoelker has quit IRC05:32
*** nkrinner has joined #openstack-meeting-405:34
*** aswadr has joined #openstack-meeting-405:34
*** belmoreira has quit IRC05:38
*** ajayaa has joined #openstack-meeting-405:44
*** dannywilson has joined #openstack-meeting-405:48
*** dannywilson has quit IRC05:48
*** dannywilson has joined #openstack-meeting-405:48
*** armax has quit IRC05:59
*** inc0 has joined #openstack-meeting-406:04
*** inc0 has quit IRC06:04
*** sdake has quit IRC06:08
*** Swami has quit IRC06:15
*** bharath has quit IRC06:20
*** markvoelker has joined #openstack-meeting-406:28
*** markvoelker has quit IRC06:32
*** aswadr has quit IRC06:35
*** simon-AS559 has quit IRC06:35
*** coldiso has quit IRC06:40
*** qwebirc34788 has quit IRC06:52
*** sbalukoff has joined #openstack-meeting-406:53
*** VW has joined #openstack-meeting-406:55
*** VW has quit IRC06:59
*** kei has quit IRC07:07
*** kei has joined #openstack-meeting-407:10
*** juggler has quit IRC07:17
*** matrohon has joined #openstack-meeting-407:20
*** ajayaa has quit IRC07:27
*** bradjones has quit IRC07:27
*** bradjones has joined #openstack-meeting-407:29
*** bradjones has quit IRC07:29
*** bradjones has joined #openstack-meeting-407:29
*** ajayaa has joined #openstack-meeting-407:30
*** coldiso has joined #openstack-meeting-407:32
*** dannywilson has quit IRC07:38
*** dannywilson has joined #openstack-meeting-407:46
*** dannywilson has quit IRC07:51
*** dannywilson has joined #openstack-meeting-407:51
*** dannywilson has quit IRC07:56
*** ajayaa has quit IRC08:03
*** mstachow has joined #openstack-meeting-408:07
*** xingchao has joined #openstack-meeting-408:11
*** markvoelker has joined #openstack-meeting-408:16
*** kei has quit IRC08:17
*** kei has joined #openstack-meeting-408:17
*** xingchao has quit IRC08:20
*** markvoelker has quit IRC08:21
*** kei has quit IRC08:23
*** BobBall has left #openstack-meeting-408:39
*** ajayaa has joined #openstack-meeting-408:42
*** yamahata has joined #openstack-meeting-409:06
*** kevsi_ has quit IRC09:17
*** bharath has joined #openstack-meeting-409:20
*** bharath has quit IRC09:25
*** yamahata has quit IRC09:35
*** rods has joined #openstack-meeting-409:38
*** pdb has quit IRC09:40
*** dims_ has joined #openstack-meeting-409:44
*** dims has quit IRC09:47
*** markvoelker has joined #openstack-meeting-410:05
*** markvoelker has quit IRC10:10
*** ajayaa has quit IRC10:12
*** ajayaa has joined #openstack-meeting-410:16
*** asselin has quit IRC10:20
*** VW has joined #openstack-meeting-410:32
*** jdziukx has joined #openstack-meeting-410:33
*** VW has quit IRC10:36
*** mfedosin has joined #openstack-meeting-410:39
*** kbyrne has joined #openstack-meeting-411:03
*** mstachow has quit IRC11:08
*** markvoelker has joined #openstack-meeting-411:21
*** markvoelker has quit IRC11:25
*** xingchao has joined #openstack-meeting-411:39
*** simon-AS559 has joined #openstack-meeting-411:42
*** xingchao has quit IRC11:48
*** VW has joined #openstack-meeting-411:52
*** markvoelker has joined #openstack-meeting-411:56
*** marcusvrn has joined #openstack-meeting-411:57
*** simon-AS559 has quit IRC12:00
*** rfolco has joined #openstack-meeting-412:10
*** ajmiller has quit IRC12:31
*** fnaval has joined #openstack-meeting-412:32
*** sdake has joined #openstack-meeting-412:33
*** amotoki has quit IRC12:50
*** tobe has quit IRC12:55
*** tobe has joined #openstack-meeting-412:57
*** bknudson has joined #openstack-meeting-412:57
*** klamath has joined #openstack-meeting-412:57
*** ajayaa has quit IRC12:58
*** klamath has quit IRC12:58
*** klamath has joined #openstack-meeting-412:58
*** ajayaa has joined #openstack-meeting-412:59
*** kenhui has joined #openstack-meeting-413:00
*** ajayaa has quit IRC13:01
*** tobe has quit IRC13:02
*** klamath has quit IRC13:02
*** klamath has joined #openstack-meeting-413:03
*** xingchao has joined #openstack-meeting-413:12
*** salv-orlando has quit IRC13:18
*** salv-orlando has joined #openstack-meeting-413:19
*** irenab has quit IRC13:22
*** salv-orl_ has joined #openstack-meeting-413:24
*** salv-orlando has quit IRC13:25
*** singlethink has joined #openstack-meeting-413:30
*** wojdev has joined #openstack-meeting-413:33
*** jdziukx_ has joined #openstack-meeting-413:43
*** VW has quit IRC13:43
*** VW has joined #openstack-meeting-413:44
*** jdziukx has quit IRC13:44
*** jdziukx_ is now known as jdziukx13:45
*** ivasilevskaya has joined #openstack-meeting-413:50
*** dashakhray has joined #openstack-meeting-413:50
*** jckasper has quit IRC13:50
*** dashakhray has quit IRC13:51
*** dshakhray has joined #openstack-meeting-413:51
*** asselin_ has quit IRC13:54
*** agalkin has joined #openstack-meeting-413:57
*** fnaval has quit IRC13:58
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, bpoulos13:59
*** asselin has joined #openstack-meeting-413:59
flaper87o/13:59
kragnizhey hey13:59
ivasilevskayao/13:59
nikhil_k#startmeeting Glance14:00
openstackMeeting started Thu Jun 11 14:00:01 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:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: Glance)"14:00
openstackThe meeting name has been set to 'glance'14:00
nikhil_k#link https://etherpad.openstack.org/p/glance-team-meeting-agenda14:00
*** ativelkov has joined #openstack-meeting-414:00
ativelkovo/14:00
kragnizo/14:00
mfedosino/14:00
nikhil_kWelcome all!14:00
jokke_o/14:01
nikhil_kWe have a short agenda today ; and looks like a decent turnout for it. So thanks!14:01
nikhil_kLet's get started14:01
nikhil_k#topic Updates14:01
*** openstack changes topic to "Updates (Meeting topic: Glance)"14:01
*** rosmaita has joined #openstack-meeting-414:01
rosmaitao/14:02
agalkino/14:02
dshakhrayo/14:02
*** xingchao has quit IRC14:02
nikhil_k#info Glance mid-cycle to be very likely co-located with Horizon and SearchLight mid-cycle on the week of July 21 for 2-3 days. Venue to be annouced soon. #link https://docs.google.com/spreadsheets/d/1w0eI6SPCA2IrOyHiEYC2uDO3fbYGzahZRUQSva0UD3Y/edit#gid=014:02
nikhil_kThe date was finalized so that people can start talking to their management for getting the travel approved.14:03
*** fallenpegasus has quit IRC14:03
flaper87why was the other week cancelled ?14:04
ativelkovApproval usually depends on budget, and budget depends on location :)14:04
nikhil_kWe tried to keep it earlier in the cycle however, the attempt to co-locate with Nova failed and then scheduling complications delayed the decision a lot more. After having more than an hour long chat with Horizon and SearchLight PTLs yesterday we were able to come up with a date.14:04
sabario/14:05
flaper87that's unfortunate, I won't be able to attend14:05
*** AlanClark has joined #openstack-meeting-414:05
nikhil_kI had made a full attempt to keep it on July 8 until last week however, the pre-conversation and then conversation with Nova team delayed things a bit14:05
flaper87Sorry for being so bold but, in this specific case, what would be the benefit of co-locating with Horizon and searchlight ?14:06
flaper87well, I see the point about searchlight14:06
flaper87is it the venue?14:06
nikhil_kAlso, keeping it later was seen as a failure to keep it mid-cycle and would reduce the value of the meetip a lot more14:06
nikhil_k'Mid' cycle *14:07
rosmaitamid-cycle sessions started as an experimental thing, but it looks like they are becoming almost mandatory ... maybe we should get th openstack foundation to start handling scheduling and stuff14:07
jokke_rosmaita: ++14:07
rosmaitathey could take into account "rival" conference conflicts14:07
nikhil_krosmaita: We had some converstion last cycle about this14:07
*** aventerav has joined #openstack-meeting-414:07
nikhil_kthe feedback was that these should not be conveyed as mandatory14:07
flaper87right but the discussions in the mid-cycle are very important14:08
rosmaitaflaper87: +114:08
flaper87the topics we discuss there are *mandatory* for our release and priorities14:08
nikhil_kfor various reasons -- like different team want to keep them at isolated venues, keep a different style andwant to get different things out of it14:08
rosmaitaflaper87: +114:08
flaper87and it's a real bummer and pain to not be able to attend to the mid-cycle14:08
flaper87since many times, for those not there, these comes down to "I've no freaking idea of what happened there"14:08
rosmaitai think if the foundation could take on scheduling, it would reduce the burden on PTLs trying to set thinkgs up14:09
flaper87unless you stay up 'til 2am to attend through phone calls14:09
rosmaitathey could still be "optional"14:09
flaper87(sorry, I don't mean to take it on anyone)14:09
nikhil_kflaper87: how about we bring this up in next weeks TC meeting? I actually would love to have a formal process for such important event but it was pushed back hard the last time14:09
rosmaitabut the foundation could find locations, etc, rotate where they are held, etc14:09
jokke_I just don't see the conflict between Foundation scheduled and non-mandatory14:10
rosmaitathe foundation should have administrative assistant support that projects don't14:10
rosmaitajokke_: +114:10
flaper87nikhil_k: I'll bring this up but this'll likely come down to "it's not mandatory and the foundation can't do anything about it"14:10
*** sigmavirus24_awa is now known as sigmavirus2414:10
flaper87it's really hard for companies to afford mid-cycles+summits14:10
flaper87and for people to travel to all those things and still be able to take care of their families14:10
flaper87so, it's a problem14:10
rosmaitaflaper87: then maybe propose changing to a 3 month release cycle14:10
nikhil_kThe point is when foundation handle it project preferences become secondary. The hard part is being able to co-locate14:11
flaper87as soon as the foundation weights in in any way, it'll change the meaning of the mid-cycle entirely (which already happened implicitly)14:11
*** fnaval has joined #openstack-meeting-414:11
flaper87rosmaita: well, nothing forbids us to do it14:11
flaper87ironic just did it :D14:11
nikhil_k3 month cycles would have a ton of overhead for release mgmt14:11
*** wojdev has quit IRC14:11
flaper87it'll be really hard to sync with other projects that depend on Glance14:12
nikhil_kwe would be in freeze a lot more14:12
rosmaitanikhil_k: i know, so supporting a mid-cycle meeting is much cheaper in comparison14:12
jokke_flaper87: but does it in the bad way ... I'd assume if it's Foundation "supported" event it's easier  for manager to justify the travel & time for it14:12
sigmavirus24not financially though ;)14:12
flaper87sigmavirus24: ++14:12
sigmavirus24also this is a bit orthogonal to the discussion14:12
flaper87sigmavirus24: LOL14:12
flaper87you're right14:12
sigmavirus24(whether the foundation handles midcycle planning or not)14:12
rosmaitaso we all agree that the midcycle meetings are good14:12
sigmavirus24(that's a TC decision ;))14:13
sigmavirus24rosmaita: I didn't say that =P14:13
rosmaitado we move htem to video only?14:13
nikhil_kMay be we need to decide on the location before the summit like Nova tried to do in Kilo-Liberty14:13
flaper87anyway, my point is that I'd like us to prioritize more on our team rather than co-location (unless I'm missing something, venue?)14:13
rosmaitai'm assuming the reason flaper87 is bummed about hte scheduling is that he wants to attend, so must be good14:13
jokke_flaper87: ++14:13
flaper87rosmaita: yeah, mostly. And this is the third time this happens to me14:13
flaper87:D14:13
rosmaitaif we do video only, then co-location is not a problem14:14
flaper87and you're all cool kids that I want to hangout with14:14
rosmaitawe just dont schedule at exactly the same time14:14
rosmaitaflaper87: :)14:14
flaper87anyway, I'd assume it's already too late to make changes this time14:14
rosmaitaand with video only, we can be more flexible about scheduling14:14
nikhil_kthe pre-liberty mini-summit did not have much participation in vidyo or was very difficult rather14:15
flaper87but lets keep it in mind for the next time14:15
jokke_video has it's own focus problems, but I'm ok for that. Let's just do it  for change for example UTC+3 ;)14:15
flaper87glance-team>co-location14:15
flaper87nikhil_k: and it was >=midnight here14:15
ativelkovjokke_ :)) nice idea14:15
*** kenhui has quit IRC14:15
nikhil_kwhy don't we do vidyo bi-weekly?14:15
flaper87nikhil_k: if there's a good agenda, I'd be ok14:16
nikhil_kI can definitely come up with one14:16
sigmavirus24"I can always come up with work for my minions" -- nikhil_k probably14:16
sigmavirus24;)14:16
sabarilol14:16
flaper87awesome, I think alternate participation is also acceptable so that'd be ok14:16
nikhil_kOk, I will come up with a plan and propose it on ML with hopes of not getting push back that we are not using irc as primary means of communication14:16
flaper87if it is open to everyone, I don't see the problem14:17
flaper87also, we can take minutes14:17
flaper87actually, we should take minutes14:17
nikhil_kyeah, I feel that we need cross-sub-team and cross-timezone participation every so often14:17
flaper87(if it isn't logged, it ain't true)14:17
rosmaitawe could log minutes in irc during the mtg14:18
flaper87rosmaita: ++14:18
nikhil_kflaper87: would you want to be a scheduling liaison if not burnt out? or may be rosmaita ?14:18
rosmaitado vidyo & irc at the same time14:18
nikhil_kco-liaison :)14:18
flaper87nikhil_k: sure14:19
nikhil_kif we have <10 participants then we can record/hangout on air and publish it thus keeping up with openness principle14:19
sigmavirus24as long as jokke_ doesn't mind being recorded ;)14:19
* flaper87 goes to get vidyo working on his laptop14:19
sigmavirus24(which google probably does anyway =P14:19
flaper87)14:19
* flaper87 just saved sigmavirus24 from a SyntaxError14:20
nikhil_kcan I get a quick vote here to see the possiblity of delaying the mini-summit by a week?14:20
rosmaitai think we can record vidyo also with >10 participants?14:20
jokke_meeting is one thing, but the problem is that I just can't  do it in the office ... so  I'll be at best on irc on those14:20
nikhil_kI actually had created another column for it14:20
sigmavirus24thanks flaper87. you're my hero14:20
jokke_and I don't think I'm the only one with that problem14:20
nikhil_ksigmavirus24: lol, yeah14:20
sigmavirus24jokke_: get a better firewall14:21
sigmavirus24problem solved :P14:21
nikhil_k#startvote Would you prefer mid-cycle to be from Jul 28-30 vs Jul 21-23 ?14:21
openstackBegin voting on: Would you prefer mid-cycle to be from Jul 28-30 vs Jul 21-23 ? Valid vote options are Yes, No.14:21
openstackVote using '#vote OPTION'. Only your last vote counts.14:21
sigmavirus24#vote Yes14:21
flaper87#vote Yes14:22
sabari#vote Yes14:22
jokke_#vote  probably neither works14:22
nikhil_kThere are no gurantees and I will try my best14:22
kragniz#vote meh14:22
ativelkovno opinion from my side14:22
mfedosin#vote Yes14:22
*** xingchao has joined #openstack-meeting-414:22
nikhil_kOk, let me make the column a bit more official14:23
flaper87nikhil_k: when do you think you'll be able to have an answer about this?14:23
flaper87no preassure but the sooner the better14:23
flaper87(I got another meeting/trip to arrange around those dates and I'd like to prioritize)14:23
nikhil_k#endvote14:23
openstackVoted on "Would you prefer mid-cycle to be from Jul 28-30 vs Jul 21-23 ?" Results are14:23
nikhil_kflaper87: I think next week14:23
sabarinikhil_k: Do you mean 28-30 or 29 - 31? The latter is Wed-Fri.14:24
nikhil_kflaper87: I will keep you or rosmaita in sync and ping if anyone if online when that conversation happens14:24
sigmavirus24heh14:24
nikhil_kSince we say many yes for that vote, please14:24
flaper87nikhil_k: awesome, thanks!14:24
nikhil_k#action add your preference about the date on https://docs.google.com/spreadsheets/d/1w0eI6SPCA2IrOyHiEYC2uDO3fbYGzahZRUQSva0UD3Y/edit#gid=014:24
nikhil_ksigmavirus24: This scheduling stuff is very tricky ;-)14:25
nikhil_ksabari: I meant 28-30 as it helps avoid flying on weekend and is preferred by many a folks14:25
sigmavirus24Yeah I just have little faith that I won't be scheduled into a sprint during the midcycle and told I can't have the time to go to it14:26
nikhil_ks/say/saw/g14:26
flaper87nikhil_k: are you going to try co-locating it ?14:26
flaper87because if not, then I'd say we should reconsider 8-10 :P14:27
sabarinikhil_k: hmm, ok14:27
* flaper87 confuses nikhil_k even more14:27
nikhil_kflaper87: Actually co-locating helps from many other reasons. Lesser travel for overlaps for those who work on more than one project, easier to get budget, interest from other companies who are just joining the project, opportunity of companies to host many project etc14:28
nikhil_ks/from/for/g14:28
flaper87nikhil_k: fair enough.14:28
nikhil_kflaper87: 8-10 would be very hard to get budget approved you see and we may end up being less than a donez hanging out in a game room or something14:29
flaper87nikhil_k: game room sounds good14:29
flaper87:P14:29
flaper87(joking)14:29
jokke_nikhil_k: I don't see anything wrong with that ;P14:30
nikhil_kBlacksburg it is then for the venue :P14:30
nikhil_kjk :-)14:30
rosmaitawe can go bowling14:30
nikhil_kwe've a nice game room with guitar hero14:30
sigmavirus24lol14:31
sigmavirus24is that place in minnesota still an option?14:31
nikhil_kI know sigmavirus24 is thinking about coming to Bburg now, even more than before :P14:31
sigmavirus24I swear, I hear wonderful things about that place14:31
sigmavirus24And I want to see it14:31
nikhil_ksigmavirus24: no, Nova said strict no unless there was some discussion on ML about horizon wanting to co-locate with them14:31
sigmavirus24Ah okay14:32
sigmavirus24Guess I'm off to join the Nova team then =P14:32
nikhil_k:)14:32
nikhil_kHope that resolves concerns..14:32
nikhil_kMoving to next one..14:33
nikhil_k#topic Cross project awareness14:33
*** openstack changes topic to "Cross project awareness (Meeting topic: Glance)"14:33
nikhil_k#link https://review.openstack.org/#/c/186635/14:33
nikhil_kPlease provide input on the same. If we go with direct pins, there would be more pressure on the glance (project) developers to write stuff according to the requirements.14:33
nikhil_kThat may create more hacks and add project side maintenance load14:34
nikhil_kvs. not going that route means more work on packaging side and harder to converge14:35
nikhil_kthat does involve fixing bug(ish) code in the project14:35
sigmavirus24hm14:35
nikhil_kThat's it from my end..14:35
sigmavirus24So as I understood that spec, this was only for testing. The official requirements will still be ranges. This is too smooth over testing14:36
sigmavirus24Which is not to say your points aren't valid. I actually agree with them, to be honest.14:36
flaper87sigmavirus24: yes, that's the way I read it as well14:37
flaper87and yes, nikhil_k are valid14:37
*** jwagner_away is now known as jwagner14:37
*** agalkin has quit IRC14:37
sigmavirus24On the one hand, if we get stuck with super old dependencies that are in those ranges, then yes we'll have to do a lot of stuff to smooth over differences in libraries14:38
nikhil_kAgreed, just for testing. Though, I kinda agree with Doug that it makes projects looks second class citizen however, with a lesser intensity and intent to push back14:38
*** MarkAtwood has joined #openstack-meeting-414:39
nikhil_kOne thing that would have made me think a lot more if it was project wise was security impact of libraries and harder upgrades14:39
nikhil_kwith testing that can be quarantined in other ways14:39
nikhil_kunless there are deployments that don't agree with such approch14:40
nikhil_kOk, we can hope to get more feedback on the review14:41
sigmavirus24Yeah14:41
nikhil_kMoving on..14:41
sigmavirus24I'll try to give some feedback tonight14:41
nikhil_kThanks!14:41
*** lazy_prince has quit IRC14:41
nikhil_k#topic Refactor: HTTP Store onto requests14:41
*** openstack changes topic to "Refactor: HTTP Store onto requests (Meeting topic: Glance)"14:41
nikhil_k#link https://review.openstack.org/#/c/189537/414:42
nikhil_ksigmavirus24: all yours14:42
flaper87the title sounds amazing already14:42
sigmavirus24oh right14:42
sigmavirus24I forgot that was on the agenda14:42
nikhil_k:)14:42
sigmavirus24tl;dr I started refactoring this before the summit but failed to write a spec until the other night14:42
sigmavirus24I need to update it some, but the updates are mainly around the threat model which I'm using as reasoning for the refactor14:43
*** lazy_prince has joined #openstack-meeting-414:43
*** nkrinner has quit IRC14:43
sigmavirus24That said, I'm talking about adding 2 new config options which I want everyone's input on14:43
sigmavirus24And if anyone can think of other config problems we might run into using something that isn't as lazy as httplib, they should provide feedback14:43
sigmavirus24There's a patch up without the config options14:43
sigmavirus24https://review.openstack.org/#/c/168507/14:44
*** GB21 has joined #openstack-meeting-414:44
sigmavirus24I can rebase it sometime this week and y'all can test it out if you're using an HTTP store and give feedback14:44
sigmavirus24It should be functionally equivalent (except that it breaks if there's a verification error)14:44
nikhil_khmm, we may have a use isecure conn kinda flag in glance14:44
sigmavirus24nikhil_k: that's one of the config options14:44
sigmavirus24I'd rather glance not pass insecure=False all the time, that defeats the purpose of the refactor14:44
flaper87sigmavirus24: I'm good with this spec, FWIW14:45
sabarisigmavirus24: and sorry I haven't reviewed the spec yet :) thought I reviewed your code long back :)14:45
nikhil_ksigmavirus24: yeah, +1 on glance not passing14:45
sabarithough*14:45
sigmavirus24I'll also be writing a spec to make the checksum configurable14:45
nikhil_kooh14:45
sigmavirus24sabari: yes you did. Your reviews were excellent14:45
sigmavirus24nikhil_k: yeah14:45
sigmavirus24I'm that guy this cycle14:45
nikhil_kthat's a tricky one14:45
nikhil_kok14:45
nikhil_k:D14:46
sigmavirus24tricky siggy14:46
*** fallenpegasus has joined #openstack-meeting-414:46
nikhil_krosmaita: you know any api/filtering constraints for configurable checksum?14:46
jokke_sigmavirus24: I think that insecurity needs to be the default 'though14:46
nikhil_kand may be brianna has more input there14:46
sabarisigmavirus24: should the spec also cover VMware driver since you started that refactor too ? https://review.openstack.org/#/c/168540/314:47
rosmaitanikhil_k: not aware of any, except the schema says 32 maxlength string, description says md5 hash14:48
*** zehicle has quit IRC14:48
sigmavirus24sabari: I'm thinking of writing a separate spec for that14:48
sigmavirus24but we could14:48
sigmavirus24rosmaita: right14:48
nikhil_kyeah, we would need to document/educate if that becomes consifugrable!14:48
sigmavirus24jokke_: please comment on the review14:49
*** zehicle_IRL has quit IRC14:49
nikhil_krosmaita: but if not api constraints, then I guess it shouldn't take us more than one cycle..14:49
sabarisigmavirus24: hmm, thanks.14:49
sigmavirus24the database does validate the length of the checksum and inessa was adding validation to the API about it14:49
*** zehicle has joined #openstack-meeting-414:49
sigmavirus24The reason we need to make the checksum configurable is so people stop -1'ing bpoulos' spec14:50
sigmavirus24And they're right that this needs to be done, but wrong about the order of operations relative to bpoulos' spec14:50
sigmavirus24Anyway, that's all I have14:50
sigmavirus24=P14:50
nikhil_kumm14:50
nikhil_k#topic Open Discussion14:51
*** openstack changes topic to "Open Discussion (Meeting topic: Glance)"14:51
nikhil_kwe can continue or discuss something else..14:51
nikhil_kI was gunna ask if we should officially register a Drivers' meeting?14:51
nikhil_kso that feedback can be synchronously and async-ly possible14:52
nikhil_kAttendance would not be mandatory14:52
nikhil_kbut would be good/great for awareness14:52
flaper87o/14:52
sigmavirus24I would attend14:52
nikhil_k30 mins?14:52
nikhil_k45 or 60, or more?14:53
flaper87I'd like to bring this spec to your attention: https://review.openstack.org/#/c/188388/14:53
sigmavirus24should probably take it to the ML to decide. I think we're missing drivers from this meeting14:53
nikhil_k<open to all>14:53
*** praveens has joined #openstack-meeting-414:53
flaper87I need to update it with latests discussions I had with sabari but early comments are appreciated14:53
sigmavirus24I would say between 30 and 45 minutes would be sufficient14:53
*** wko has joined #openstack-meeting-414:54
rosmaitamaybe start with 30 and see if we need more?14:54
rosmaitanikhil_k: only v2 api constraint on checksum is that you can use it to filter an image list14:55
nikhil_kok, I will send email to ML and get more feedback. As this would be a place for open feedback and track progress and do prioritization outside of sprints like mid-cycle14:55
nikhil_krosmaita: awesome, thanks!14:55
nikhil_kWe can decide on dates/time there14:56
nikhil_kweekly would be nice but may be bi-weekly if needed14:56
nikhil_k(or not needed)14:56
*** jckasper has joined #openstack-meeting-414:58
*** mmedvede has quit IRC14:58
*** TravT_ has joined #openstack-meeting-414:58
nikhil_kDo we need more active cores? We do need a policy and cleanup of the core-list soon-ish possibly before mid-cycle. May be we can chat about it next weekly mtg..14:58
nikhil_kIf nothing else ..14:59
nikhil_kThanks all!14:59
rosmaitaending 33 sec early14:59
nikhil_k#endmeeting14:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:59
openstackMeeting ended Thu Jun 11 14:59:47 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-06-11-14.00.html14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-06-11-14.00.txt14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-06-11-14.00.log.html14:59
nikhil_kTravT_: hi, just in time14:59
*** dhruvdhody has joined #openstack-meeting-415:00
TravT_Hey nikhil_K15:00
nikhil_k#startmeeting openstack-search15:00
openstackMeeting started Thu Jun 11 15:00:21 2015 UTC and is due to finish in 60 minutes.  The chair is nikhil_k. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: openstack-search)"15:00
openstackThe meeting name has been set to 'openstack_search'15:00
rosmaitao/15:00
nikhil_kTravT_: you avaliable to chair?15:00
nikhil_kI think I can use the #chair option to reassign that15:00
nikhil_kUntil we hear from him15:01
TravT_i am, but if you want to run it today, go ahead!15:01
nikhil_k#link https://etherpad.openstack.org/p/search-team-meeting-agenda15:01
nikhil_k#chair TravT_15:01
openstackCurrent chairs: TravT_ nikhil_k15:01
*** zehicle_IRL has joined #openstack-meeting-415:01
nikhil_ko/15:01
*** ativelkov has left #openstack-meeting-415:01
nikhil_kTravT_: feel free to take over15:01
TravT_in the past, we used meeting name of openstack search15:01
*** dims_ has quit IRC15:02
TravT_will the meeting bot still pick it up regardless of name?15:02
nikhil_kTravT_: oops15:02
TravT_it does it based on time and room, right?15:02
*** yamahata has joined #openstack-meeting-415:02
*** dims has joined #openstack-meeting-415:02
nikhil_kTravT_: Ah I read the _ incorrectly over here http://eavesdrop.openstack.org/meetings/openstack_search/15:02
TravT_http://eavesdrop.openstack.org/meetings/openstack_search/2015/15:02
TravT_yeah, i shouldn't have used the space...15:03
*** galstrom_zzz is now known as galstrom15:03
TravT_maybe we should end it and start it again just in case?15:03
nikhil_ksure15:03
nikhil_k#endmeeting15:03
sigmavirus24o/15:03
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:03
openstackMeeting ended Thu Jun 11 15:03:49 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-06-11-15.00.html15:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-06-11-15.00.txt15:03
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-06-11-15.00.log.html15:03
sigmavirus24sorry, spaced out on the glance meeting15:03
nikhil_k#startmeeting openstack search15:04
openstackMeeting started Thu Jun 11 15:04:06 2015 UTC and is due to finish in 60 minutes.  The chair is nikhil_k. Information about MeetBot at http://wiki.debian.org/MeetBot.15:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:04
*** openstack changes topic to " (Meeting topic: openstack search)"15:04
openstackThe meeting name has been set to 'openstack_search'15:04
*** sjmc7 has joined #openstack-meeting-415:04
nikhil_k#chair TravT_15:04
openstackCurrent chairs: TravT_ nikhil_k15:04
*** bpoulos has joined #openstack-meeting-415:04
*** bpoulos has left #openstack-meeting-415:04
nikhil_k#link https://etherpad.openstack.org/p/search-team-meeting-agenda15:04
rosmaitao/ (again)15:04
nikhil_ko/15:04
TravT_i guess we can see what happened in the logs.15:04
TravT_fun test15:04
TravT_good morning, anyway15:04
*** carl_baldwin has joined #openstack-meeting-415:04
sjmc7morning!15:04
nikhil_kIt went fine15:05
nikhil_klogs still there http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-06-11-15.00.html15:05
TravT_ok, cool.15:05
sigmavirus24either one works15:05
sigmavirus24logs are live updating here too: http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-06-11-15.04.log.txt15:06
sigmavirus24=P15:06
nikhil_kLatest ones (this mtg logs) http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-06-11-15.04.log.txt15:06
sigmavirus24nikhil_k: ^515:06
TravT_cool15:06
TravT_#topic We have a project!15:06
*** openstack changes topic to "We have a project! (Meeting topic: openstack search)"15:06
sjmc7yay!15:06
TravT_https://review.openstack.org/#/c/188014/15:06
nikhil_k\o\ \o/ /o/15:07
TravT_So, virtual cheers to everybody!15:07
nikhil_k(with a bit of drama of course)15:07
TravT_you mean the gate failing....15:07
TravT_:)15:07
nikhil_kyeah15:08
*** blahRus has joined #openstack-meeting-415:08
*** qwebirc61721 has joined #openstack-meeting-415:08
sigmavirus24lol15:08
sigmavirus24that was lifeless' fault15:08
sigmavirus24He's always trying to cause drama =P15:08
sigmavirus24Breaking gates and whatnot15:08
TravT_lol15:08
TravT_#topic OpenStack repo import status (kragniz)15:09
*** openstack changes topic to "OpenStack repo import status (kragniz) (Meeting topic: openstack search)"15:09
nikhil_kI remember the dialogue from Batman Begins .. why do we fall Mr. Bruce?15:09
TravT_kragniz are you around today?15:09
kragnizhey15:09
kragnizready to go (almost)15:10
kragnizhttps://review.openstack.org/#/c/190278/415:10
sigmavirus24do or do not, there is no almost15:10
sigmavirus24=P15:10
TravT_looks like just waiting for checks to pass?15:10
kragnizand some +2s from people15:11
sigmavirus24so15:11
sigmavirus24do we want python3.4 to be a non-voting job for searchlight?15:11
sjmc7yeah, let's do it from the start15:12
* sigmavirus24 is just asking since it was mentioned yesterday15:12
TravT_sigmavirus24: i think we do.15:12
* sigmavirus24 is not trying to make Louis' job harder15:12
sjmc7we'll have to do it sometime and i don't want to have to go and fix a bunch of stuff later15:12
kragnizsjmc7: do you know if the py34 job currently runs?15:12
sigmavirus24s/not//g15:12
sigmavirus24kragniz: does not15:12
sigmavirus24-python-jobs is only python215:12
nikhil_kand we just need 2715:12
nikhil_k?15:12
TravT_in the cross project meeting, there was a lot of discussion on moving to py 34.15:13
kragnizsigmavirus24: I mean if you do to -e py34, does it do horrible things15:13
sigmavirus24you have to add check:\n  - gate-searchlight--python3415:13
kragniztox -e15:13
sigmavirus24kragniz: oh yeah15:13
sigmavirus24no clue15:13
sjmc7there ARE non-voting python 3 jobs though15:13
sigmavirus24right15:13
sigmavirus24if we have an express goal of being able to run on 3.4 then we should add it15:13
kragnizwe can add it when we have something that runs (okayishly)15:13
nikhil_ksigmavirus24: experimental: ,I think vs. check:15:13
sigmavirus24if it's just going to be a "nice to have" for liberty, then I say no15:13
kragnizI think we should have it from the start15:13
sjmc7i do too15:14
sigmavirus24nikhil_k: the way I did it for bandit was adding it to check and defining it as non-voting15:14
sjmc7while the test suite is relatively small15:14
sigmavirus24yeah the codebase is also small15:14
sjmc7make it non voting until it passes15:14
sigmavirus24so it should be easy to work on15:14
sigmavirus24then make it voting to annoy people15:14
sigmavirus24;)15:14
TravT_+1 ^15:14
kragnizwe're going to have to port anyway, so we should keep the amount of legacy stuff small from the start15:14
sjmc7yeah... i've been on projects that have ported to 3, it's a real pain once you have significant code15:14
kragnizyup15:14
TravT_anybody have that link handy that I shared in the room yesterday?15:15
nikhil_kgiven 34 is a real thing now15:15
kragnizI think we should aim for a voting job in liberty, anyway15:15
nikhil_kunless 33 last year15:15
TravT_just wanted to link it from here15:15
nikhil_kunlike*15:15
kragnizbut that can come later, with a non-voting job first15:15
nikhil_kplease no15:15
nikhil_kwho deploys 34!?15:15
*** singleth_ has joined #openstack-meeting-415:16
sigmavirus24nikhil_k: I will if I have to15:16
nikhil_k+1 on non-voting but voting should be only in-use production ready15:16
sigmavirus24nikhil_k: I think you overestimate how hard it is to get a code-base to be production ready on Python 315:16
nikhil_kotherwise patches will have tendency to get stuck that may break stuff in real world15:16
sigmavirus24^ can you expound on this?15:16
nikhil_ksigmavirus24: I am just saying..15:17
nikhil_kif no one is using py34 in real world, it does not make sense to mark the job voting15:17
kragniznikhil_k: but who deploys searchlight?15:17
nikhil_kwe can continue to monitor it as responsible developers15:17
kragnizwe're a new project, so we can be more cutting-edge15:18
nikhil_kI hope that was a joke15:18
kragnizanyway, we can talk about this later in the cycle15:18
TravT_FYI on some discussion on py 3 yesterday: #link http://eavesdrop.openstack.org/meetings/crossproject/2015/crossproject.2015-06-09-21.01.log.html#l-12315:18
sigmavirus24nikhil_k: IMO, if we don't gate on Python 3, no one will fix their broken patches unless we block them until they do15:18
sigmavirus24That shouldn't be the reviewer's job, that should be the gate's job15:18
sigmavirus24And for all the gloom and doom that everyone predicts about Python 3, I can speak from years of experience, that it isn't that bad15:19
sigmavirus24And it's constantly getting a lot better15:19
*** singlethink has quit IRC15:19
sigmavirus24Many of the biggest libraries in use are production ready for Python 315:19
nikhil_kIt's just about porting your N K servers to use py34 after you've just spent months porting from py26->py2715:20
sigmavirus24That will only happen when openstack drops 2.715:20
nikhil_kBut I don't want to hold back the meeting15:20
* nikhil_k shuts up15:20
sigmavirus24And in many cases, if they're using debian or ubuntu, they wont' have a choice15:20
sigmavirus24Python 3 is becoming the default real soon15:20
sigmavirus24Red Hat will be left supporting 2.x customers and that's what they're good at15:20
* sigmavirus24 shuts up15:20
TravT_i think this is a good discussion.  My vote is that we enable it as a non-voting job.15:21
TravT_and revisit making it voting15:21
kragnizit should certainly be a non-voting job at first15:21
kragnizTravT_: +115:21
sjmc7aye15:21
david-lyle+115:21
*** sdake has quit IRC15:21
TravT_so kragniz, i guess you should go ahead and add it to the patch.15:21
* sigmavirus24 is always happy to discuss Python 3 outside of meetings15:22
sigmavirus24=P15:22
kragnizyeah, I guess so15:22
TravT_next up15:23
TravT_#topic Brainstorming Session15:23
*** openstack changes topic to "Brainstorming Session (Meeting topic: openstack search)"15:23
TravT_#link https://etherpad.openstack.org/p/liberty-searchlight-brainstorming15:23
*** dannywilson has joined #openstack-meeting-415:23
TravT_thank you everybody that attended15:23
TravT_i thought it was a very useful session!15:23
nikhil_k+115:24
*** dannywilson has quit IRC15:24
TravT_there were a few actions out of it.15:24
*** dannywilson has joined #openstack-meeting-415:24
TravT_one was the discussion we just had with kragniz^15:24
rosmaitaTravT_: an interesting point came up in today's glance meeting, viz., that we could record minutes of the meeting into the logged openstack-serach channel15:25
rosmaitaTravT_: live, during the meeting, i mean15:25
TravT_rosmaita, you mean as a supplement to the etherpad?15:25
rosmaitayes15:26
TravT_seems like a pretty good idea.15:26
nikhil_kyeah, I wanted to get reasoning behind that if we have time15:26
TravT_sure, go ahead15:26
nikhil_kAny specific reason we prefer openstack logs over etherpad?15:26
*** Bjoern__ has joined #openstack-meeting-415:27
nikhil_kOr can we just link a etherpad during the meeting? Not sure what helps.. We may need someone dedicated notes taker for irc logs..15:27
nikhil_k(seems like folks who want it are not here)15:28
rosmaitaetherpad is ephemeral by nature15:28
rosmaitaand not discoverable15:28
sigmavirus24^^15:28
sigmavirus24logs are not ephemeral15:28
sigmavirus24also, they're immutable15:29
sigmavirus24etherpads can supplement the logs, but can't exactly replace them15:29
nikhil_ktrue, otoh more collaboratiev and async (good for offline feedback etc)15:29
rosmaitasigmavirus24: ty, that's what i was trying to say15:29
sigmavirus24yep15:29
nikhil_kgotcha15:29
nikhil_kthanks15:29
sigmavirus24nikhil_k: I don't think this should be a discussion of 1 or the other15:29
sigmavirus24I think having both is really good15:29
rosmaitayes, let's use all the tools!15:29
nikhil_kok, as long someone DOES IT15:30
sigmavirus24I wouldn't have been able to participate yesterday (in any capacity) without an etherpad15:30
rosmaitanikhil_k: i guess i can volunteer as minute-taker15:30
rosmaita(it will force me to pay attention)15:30
*** numan has quit IRC15:30
nikhil_kheh, thanks!15:30
rosmaitaTravT_: what do you think?15:30
sigmavirus24rosmaita: thanks for not making me volunteer ;)15:30
* nikhil_k too15:30
TravT_i'm happy for you to take notes rosmaita. :P15:30
*** mmedvede has joined #openstack-meeting-415:31
rosmaitaok, put me down as minutes-taker for the out-of-normal-schedule meetings15:31
TravT_thanks, rosmaita!15:31
*** praveens1 has joined #openstack-meeting-415:31
TravT_i guess we can ask for volunteers next time we have such a thing15:31
nikhil_k+115:32
TravT_so another action from the meeting was getting #openstack-searchlight logged15:32
TravT_kragniz, david-lyle, is that done?15:32
*** praveens has quit IRC15:32
kragnizTravT_: I think that's done15:32
david-lyleI got the channel added this morning15:32
nikhil_kI didn't want to put rosmaita in that position either and was just trying to get more feedback and reduce my multi-tasking responsiblity15:32
kragnizI think the patch merged15:32
sigmavirus24no bots in there15:32
david-lyleso the log should start15:32
TravT_ok, thanks!15:33
rosmaitacool, having the channel logged is a dependency for minutes!15:33
*** ajmiller has joined #openstack-meeting-415:33
TravT_so this means everybody should be on good behavior in there now!15:33
nikhil_knot yet on the channel logs15:33
david-lyleif a log doesn't appear soon, I'll dig into why15:33
TravT_thanks david-lyle15:33
TravT_i sent a message back to the attorney re: trademark.15:34
*** salv-orlando has joined #openstack-meeting-415:34
TravT_no response15:34
david-lylelooks like it's written once a day15:34
*** salv-orl_ has quit IRC15:34
* nikhil_k doesn't mind enjoying the name until someone pushes back15:34
TravT_yeah, i like it15:35
kragnizdavid-lyle: I think I know why15:35
sigmavirus24david-lyle: the logs are live updated =P15:35
nikhil_kdavid-lyle: oh, you mean written to create one?15:35
kragnizI'll write a patch15:35
david-lylekragniz: ok thanks15:35
kragniz(needs a system-config change)15:36
TravT_ok, the next thing is we agreed that people should start opening blueprints for the areas they are working on which brings us to15:36
TravT_#topic launchpad15:36
*** openstack changes topic to "launchpad (Meeting topic: openstack search)"15:36
TravT_    OpenStack release management tracked based on the blueprints closed: http://status.openstack.org/release/15:36
david-lyleoh yeah, I always forget about system-config and hard coded lists15:36
TravT_in order for us to show up on the release management board, we do need blueprints15:37
*** xingchao has quit IRC15:37
*** agalkin has joined #openstack-meeting-415:38
TravT_in previous discussions, we decided that we will use as lightweight as possible15:38
david-lyleeavesdrop.pp15:38
TravT_but there is a template that you can look at filling out.  https://blueprints.launchpad.net/searchlight/+spec/searchlight-blueprint-template15:38
TravT_mainly, just share some information. if we need more we'll ask for it.15:38
nikhil_kpick and choose, I guess15:38
TravT_for API discussions and changes, we do want that to be more stringent15:39
sjmc7this is one area where a specs repo is nice, it formalizes that "you need to provide more info" aspect15:39
nikhil_k+115:39
sjmc7for now though, perhaps we're small enough that we can do it more informally?15:39
sjmc7so if my blueprint's too scanty, tell me in IRC and i'll fix it15:39
nikhil_kAlso, specs.openstack.org links can be a part of the release notes for that cycle15:40
sigmavirus24sjmc7: you betcha15:40
sigmavirus24=P15:40
sjmc7i think this template's good to read while you're writing them though15:40
nikhil_kBP can be changed rather easily and thus may contain bad data15:40
TravT_what about creating docs in our docs directory?15:41
TravT_so, if you are working on nova plugin, you will create a doc on the nova plugin15:41
sjmc7so my vote's not to be crazy formal about it, but feel free to demand more information from people if BP's aren't clear enough15:41
TravT_it is rst. it can be reviewed for more info.15:41
sjmc7that won't work for all BPs15:42
*** dwalleck has joined #openstack-meeting-415:42
sjmc7i guess ultimately i don't really mind as long as it's clear what the intent is15:42
nikhil_k+1 on small BPs and good info on API15:42
TravT_my belief is this.  we need documentation.15:42
TravT_whether it specs or in our docs section of our repo15:43
*** yamahata has quit IRC15:43
sjmc7since we have to do BPs for project purposes, i'd vote for as much info in there as is useful to implement and then docutmation as part of the implementation15:43
nikhil_k+1 docs section15:43
* rosmaita has not talked to docs team yet, is writing email now15:43
TravT_blueprints usually don't work so well when it gets complicated, because they don't have proper review tools15:43
nikhil_kand history/timelogs isn't preserved :P15:44
*** ivasilevskaya has left #openstack-meeting-415:44
nikhil_k#action nikhil: write BPs for his assigned tasks15:45
TravT_ok, well, for now, please just create your blueprint15:45
TravT_so we have something to show...15:46
TravT_need to move on.15:46
TravT_#topic midcycle meetup15:46
*** openstack changes topic to "midcycle meetup (Meeting topic: openstack search)"15:46
TravT_probably nikhil_k already covered this with glance15:46
nikhil_kTravT_: yeah, and received some feedback15:47
sjmc7i *think* i have clearance to travel15:47
TravT_do you want to repeat yourself nikhil_k15:47
*** singleth_ has quit IRC15:47
*** armax has joined #openstack-meeting-415:47
nikhil_ksure15:47
* nikhil_k will try to be quick15:47
nikhil_kPeople (and a few of those in specific) were a little worried that mid-cycles are harder to schedule and get travel approved15:48
rosmaitahow about http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-06-11-14.00.log.html15:48
nikhil_kSo there were 2 requests15:48
*** dhruvdhody has quit IRC15:48
*** stevelle has joined #openstack-meeting-415:49
nikhil_k1. Look at the possiblity of preferring the team (so that people from that team can attend) -- that meaning specific dates, venue etc15:49
nikhil_k2. Look at the possiblity of Video conf. only mid-cycle (or ask Foundation to schedule these events)15:49
nikhil_kdid I get your concern right rosmaita ?15:50
nikhil_kBasically, I made no promises to change in schedule15:50
nikhil_khowever, wanted to consider the possiblity of mid-cycle during Jul 28-30 preferred over Jul 21-23. And many online participants voted yes15:50
nikhil_kI also added the column in #link https://docs.google.com/spreadsheets/d/1w0eI6SPCA2IrOyHiEYC2uDO3fbYGzahZRUQSva0UD3Y/edit#gid=0 for respective date range15:51
rosmaitamy concern is just that these mid-cycle meetings are sufficiently important, and scheduling is so difficult, that the foundation should give administrative assistant support to help scheduling15:51
rosmaitathe chosen week conflicts with europython conf15:51
david-lylerosmaita: the foundation wants midcycles to go away15:51
david-lyleso I doubt support is an option15:51
nikhil_kyep15:51
david-lylethis is the reason for all the changes to the summit structure15:52
david-lyleto attempt to remove the perceived need for more f2f meetings15:52
TravT_nikhil_k, it doesn't look like anybody really updated the https://docs.google.com/spreadsheets/d/1w0eI6SPCA2IrOyHiEYC2uDO3fbYGzahZRUQSva0UD3Y/edit#gid=015:52
nikhil_kyeah15:52
rosmaitahmmm ... whatever happend to bottom-up governance?15:52
TravT_are people supposed to go vote on that other week now?15:52
david-lylecompanies at the top don't like them15:52
david-lyle$$$15:53
rosmaitadavid-lyle: that is a problem15:53
*** alextricity_h has joined #openstack-meeting-415:53
*** mmedvede has quit IRC15:53
rosmaitawe just have to stop having summits in exotic locales15:53
*** zehicle has quit IRC15:54
nikhil_kTravT_: only if we think it's feasible. The only thing I mentioned is if we decide to consider a different date then some others may be online to provide more feedback15:54
*** zehicle_IRL has quit IRC15:54
nikhil_krosmaita: expensive locale ?15:54
TravT_#action everybody here, go ahead and indicate in the spreadsheet if you can attend the 28 - 30th on the spreadsheet15:55
TravT_#link https://docs.google.com/spreadsheets/d/1w0eI6SPCA2IrOyHiEYC2uDO3fbYGzahZRUQSva0UD3Y/edit#gid=015:55
*** zehicle_IRL has joined #openstack-meeting-415:55
rosmaitahong-kong, paris, tokyo ... would be way cheaper in florida during august15:55
*** zehicle has joined #openstack-meeting-415:55
sjmc7i am NOT going to florida in august15:55
sjmc7the horror!15:55
rosmaitasjmc7: it would be cheap!15:55
TravT_they could probably do two meetups in north dakota for the price of a single paris15:55
kragnizsjmc7: +1 to that!15:55
sjmc7there's a reaosn it's cheap! i would go to dakota!15:56
rosmaitadakota during february15:56
*** s3wong has joined #openstack-meeting-415:56
nikhil_kFoundation needs adoption across the globe, I think15:56
TravT_ok, so for now... the plan is still july 21-2315:56
nikhil_khaving in ND might not interest many15:56
TravT_nikhil?15:57
rosmaitanikhil_k: there must be a european equivalent of north dakota15:57
nikhil_kTravT_: yes15:57
*** lazy_prince has quit IRC15:57
TravT_ok, we're nearly out of time.15:57
*** praveens has joined #openstack-meeting-415:57
*** GB21 has quit IRC15:57
TravT_so kragniz, i guess we defer on client for another week15:57
sigmavirus24rosmaita: that would be cheap for US people15:57
sigmavirus24;)15:58
TravT_although there was some discussion yesterday on it.15:58
sigmavirus24nikhil_k: I'd go to the dakotas ;)15:58
nikhil_ksigmavirus24: if you are there, then so am I :)15:58
* sigmavirus24 likes cold weather15:58
sigmavirus24And I have all of last year's vacation time + this year's15:58
TravT_want to mention, i'll be out June 16th - 24th15:58
sigmavirus24so might as well spend it on midcycles15:58
sigmavirus24TravT_: enjoy yourself15:59
TravT_#topic open discussion15:59
*** openstack changes topic to "open discussion (Meeting topic: openstack search)"15:59
TravT_since we already were15:59
TravT_any other vacations in the next week or two we should know about?15:59
*** praveens1 has quit IRC15:59
*** GB21 has joined #openstack-meeting-415:59
rosmaitai will be gone june 24-july 815:59
sigmavirus24unlikely I'll be able to take a vacation in the next 3 weeks16:00
sigmavirus24if I can find one after that I'll let you all know16:00
* TravT_ pictures sigmavirus24 being chained to desk.16:00
*** b3rnard0 has joined #openstack-meeting-416:00
TravT_i guess we're out of time.16:00
sigmavirus24more or less16:00
sigmavirus24=P16:00
TravT_thanks everybody16:00
nikhil_kThanks!16:00
sigmavirus24htanks travis16:00
kragnizTravT_: yeah16:00
TravT_#end meeting16:00
TravT_#endmeeting16:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:01
openstackMeeting ended Thu Jun 11 16:01:00 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-06-11-15.04.html16:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-06-11-15.04.txt16:01
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_search/2015/openstack_search.2015-06-11-15.04.log.html16:01
*** rosmaita has left #openstack-meeting-416:01
sigmavirus24oh look my next meeting is in the same room!16:01
sigmavirus24=P16:01
nikhil_kansible this week?16:01
sigmavirus24yep16:01
sigmavirus24e'ry week16:01
*** sjmc7 has left #openstack-meeting-416:01
nikhil_kok, I will attend wg16:01
sigmavirus24which wg?16:01
nikhil_khuh16:01
nikhil_kapiwg16:01
*** praveens has quit IRC16:01
sigmavirus24that was 0000 UTC today16:01
sigmavirus24aka last night for US people16:02
sigmavirus24miguelgrinberg: was anyone there?16:02
nikhil_kalternate week?16:02
stevelleyes16:02
sigmavirus24nikhil_k: yes16:02
sigmavirus24next week it'll be at this time in meeting-316:02
cloudnullhello16:02
sigmavirus24hello cloudnull16:02
nikhil_kah16:02
cloudnull#startmeeting16:02
d34dh0r53o/16:02
openstackcloudnull: Error: A meeting name is required, e.g., '#startmeeting Marketing Committee'16:02
d34dh0r53b3rnard0 bot fail16:03
b3rnard0lol16:03
sigmavirus24needs #startmeeting openstack ansible or wahtever16:03
cloudnullthis is why we need an adult16:03
sigmavirus24b3rnard0: how do you adult?16:03
sigmavirus24b3rnard0: plz16:03
cloudnull#startmeeting OpenStack Ansible Meeting16:03
*** odyssey4me has joined #openstack-meeting-416:03
openstackMeeting started Thu Jun 11 16:03:26 2015 UTC and is due to finish in 60 minutes.  The chair is cloudnull. Information about MeetBot at http://wiki.debian.org/MeetBot.16:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:03
b3rnard0oh my, ms outlook what?16:03
*** openstack changes topic to " (Meeting topic: OpenStack Ansible Meeting)"16:03
openstackThe meeting name has been set to 'openstack_ansible_meeting'16:03
cloudnullboom suck it b3rnard016:03
*** rromans has joined #openstack-meeting-416:03
odyssey4meo/16:03
d34dh0r53lol16:03
rromans...16:03
*** agalkin has quit IRC16:03
cloudnull#topic Agenda & rollcall16:04
*** openstack changes topic to "Agenda & rollcall (Meeting topic: OpenStack Ansible Meeting)"16:04
b3rnard0i be here16:04
stevellehowdy16:04
cloudnull#kick b3rnard016:04
odyssey4me\o16:04
sigmavirus24o/16:04
sigmavirus24\o/16:04
d34dh0r53o\16:04
*** Sam-I-Am has joined #openstack-meeting-416:05
Sam-I-Ammoo.16:05
palendaeo/16:05
*** praveens has joined #openstack-meeting-416:06
jwagnero/16:06
*** KunalGandhi has joined #openstack-meeting-416:07
*** VW has quit IRC16:07
cloudnullso lets get started16:07
*** TravT_ has left #openstack-meeting-416:07
cloudnull#topic To BigTent or not to BigTent that is the question?16:07
*** openstack changes topic to "To BigTent or not to BigTent that is the question? (Meeting topic: OpenStack Ansible Meeting)"16:07
cloudnullso we have an etherpad going talking about this16:08
cloudnull#link https://etherpad.openstack.org/p/osad-openstack-naming16:08
cloudnullI'd like for people to chime in here regarding the move16:08
cloudnulland if there are any glaring things that we need to take care of before we apply, if we agree that we should apply.16:09
*** asselin_ has joined #openstack-meeting-416:09
odyssey4mecloudnull do we have any idea from ansible regarding whether we're allowed to use their name?16:09
cloudnullno.16:10
cloudnullbut when we send the request out to the ML we'll cc them to get them on the record16:10
cloudnullbut pulling from prior art it we'll likely need to change it16:10
odyssey4meok cool - then I think we should try for 'openstack-ansible' first16:11
Sam-I-Amdoesnt puppet use puppet?16:11
sigmavirus24Sam-I-Am: puppet-openstack16:11
sigmavirus24I think16:11
sigmavirus24or they used to16:11
palendaehttp://lists.openstack.org/pipermail/openstack-dev/2015-April/061712.html16:11
Sam-I-Amseems like having the name of the deployment system makes sense16:11
odyssey4meansible doesn't seem to be sticky about the trademark - almost every role I find on github uses 'ansible-' in the name16:11
palendaeSam-I-Am: It does, so long as we don't have TM issues16:11
palendaeodyssey4me: Yeah, I think ansible *wants* the name there16:12
cloudnullyes, but the official project name is marionette or something similar16:12
Sam-I-Amguess it boils down to ansible's legal, and hoping they aren't dense.16:12
palendaeYeah, that email makes it sound like Puppet, Inc was the issue, not Openstack16:13
palendaeBut it's worth taking into consideration, and working with Ansible, Inc on16:13
palendaeWe don't have a rep from there here, do we? Would be nice if Greg could make some of these meetings16:13
*** Bjoern__ is now known as BjoernT16:14
Sam-I-Amalternatives would be something like what puppet did... a name that is related to puppet. ansible has a few, but most of them arent easy to spell.16:14
*** yamahata has joined #openstack-meeting-416:14
odyssey4meSam-I-Am +1, but it's hard to find something like that - I like the idea of the sci-fi theme, but we've yet to find a good name16:15
Sam-I-Amit'd take some good digging. i'd call up the sci-fi oracle, karin :)16:16
cloudnullso moving into that space.16:16
cloudnull#topic BigTent project code name16:16
*** openstack changes topic to "BigTent project code name (Meeting topic: OpenStack Ansible Meeting)"16:16
palendaeodyssey4me: Just cause we haven't yet doesn't mean we won't :p16:16
cloudnullif we rename, i'd like a list in the etherpad which we can +1 / -1 and then move forward by EOW .16:16
palendaeSounds reasonable to me16:17
*** kenhui has joined #openstack-meeting-416:20
*** yamahata has quit IRC16:20
cloudnullso do we have any issues with the move to big tent ?16:20
Sam-I-Amas long as its air-conditioned16:20
Sam-I-Amand there's some docs now16:20
cloudnulljust need some more ascii diagrams16:21
Sam-I-Amha nooooo16:21
Sam-I-Amjust like we need more OVS16:21
Sam-I-Amfair trade16:21
palendaeI am +1 on big tent16:22
*** krtaylor has quit IRC16:22
odyssey4meme too +116:23
odyssey4medo we deal with the RAX tech debt before-hand? we'll have to move those branches I guess?16:23
*** gregdek has joined #openstack-meeting-416:24
* gregdek hullos16:24
gregdekI hear you've got some naming considerations, hm?16:24
cloudnull#link https://etherpad.openstack.org/p/osad-openstack-naming16:24
* gregdek is the Ansible guy16:24
cloudnullgregdek:  for prez16:24
cloudnull:)16:24
gregdekOh, no.16:25
gregdekNo, I don't do elected governance. ;)16:25
*** sean-k-mooney has joined #openstack-meeting-416:25
cloudnullodyssey4me:  ideally we'd keep osad in stackforge and move master / kilo forward .16:25
sigmavirus24+1 here on big tent16:25
gregdekGimme a sec to read over the etherpad and I'll comment if I have any.16:25
sigmavirus24welcome gregdek16:25
*** sean-k-mooney has quit IRC16:25
gregdekcowstack would be pretty awesome, I gotta say. :)16:27
Sam-I-Amyeah, i like cows.16:27
Sam-I-Amthey're trendy too16:27
Sam-I-Amalthough that theory didn't work for gateway computer16:28
d34dh0r53moo.stack16:28
palendaeSam-I-Am: Hey, they're still around!16:28
palendaeOpenMoo16:28
Sam-I-Ami hear the nebula name might be available16:29
Sam-I-Amthats sciency, right?16:29
gregdekI think broadly it's "be descriptive" (ansible-openstack) or "be fun" (cow-based).16:29
odyssey4melol, sies Sam-I-Am16:29
palendaeI bet the investors woiuld gladly sell it16:29
Sam-I-Amto soon?16:29
gregdek(wow. that's harsh.)16:29
palendaegregdek: So, as far as you know, no legal issues with having ansible in the name?16:29
*** matrohon has quit IRC16:29
palendaeI think there's concern about whether Ansible, Inc would condone it16:29
Sam-I-Aman5ible ... there, no trademark problems16:29
palendaeansistack16:29
gregdekpalendae: if there are, that ship has kinda sailed, since Ansible is already in OSAD.16:30
odyssey4mes/legal/trademark/16:30
gregdekAnd we basically endorsed that with all kinds of press. :)16:30
palendaeodyssey4me: Trademarks are legal :p16:30
d34dh0r53intergalacticstack16:30
palendaeopenstack-erector-set16:30
odyssey4mesounds fair enough :)16:30
gregdekSo long as what $newcowproject is using is stock Ansible, legal should be ok.16:30
palendaeOk16:30
palendaeBasically if we're not forking and calling it Ansible16:31
sigmavirus24Queue E Em Ewe16:31
palendaePostgreStack16:31
* odyssey4me kicks palendae :p16:31
gregdekThere's a potential political issue down the road: what happens if some other Ansible-based install project gets a head of steam?16:31
sigmavirus24palendae: but trademark has to be enforced16:31
*** singlethink has joined #openstack-meeting-416:31
sigmavirus24And Ansible Inc could have enforced that before endorsing os-ansible-deployment16:31
gregdekBut from my perspective, because OSAD planted the flag, OSAD has the name.16:32
gregdekWhen does the decision need to be made?16:32
palendaecloudnull was talking about EOW16:32
palendaeSo, tomorrow16:32
gregdekBecause the paranoid side of me says I should probably sit down with counsel to make superdupersure.16:32
palendaeTotally fair and reasonable to me16:32
stevellethat seems like a good idea16:32
gregdekOK, I'll go do that.16:32
gregdekAre we using a bot in here for action items?16:33
cloudnullgregdek:  im going to put through the governance commit likely today , but that doesn't need to be finalized by tomorrow16:33
cloudnullyes16:33
gregdekSomeone feel free to action me then :)16:33
cloudnull#action gregdek talk to legal people about using the ansible name in the OSAD project for OpenStack governance.16:34
gregdekOf course, this assumes the final vote is ansible-openstack and not $funcowname...16:34
gregdek...which obviously doesn't require our help. :)16:34
cloudnullthis is true.16:34
gregdekPart of me wants to stonewall you to make you choose $funcowname!16:34
gregdek(But I won't actually do that.)16:34
cloudnulli respect that :)16:35
gregdekIs it openstack-ansible or ansible-openstack? If legal has a preference, do you care?16:35
palendaeOur IRC channell is #openstack-ansible now16:36
cloudnullgregdek: ^16:36
sigmavirus24moosible openstack16:36
palendaeSo we do have some precedence, but I suppose that could be changed16:36
cloudnullso ill submit the governance change today. and we'll circle back on the name if needed.16:36
gregdekOK. Simple enough. I'll have an answer soon.16:36
cloudnull#action commit governance change to https://github.com/openstack/governance16:37
cloudnullgregdek:  is it ok if i cc you on the ML post for the change ?16:37
*** xingchao has joined #openstack-meeting-416:38
cloudnullso moving on.16:39
cloudnull#Blueprints16:39
cloudnull#topic Blueprints16:39
*** openstack changes topic to "Blueprints (Meeting topic: OpenStack Ansible Meeting)"16:39
*** praveens has left #openstack-meeting-416:41
*** xingchao has quit IRC16:42
*** Swami has joined #openstack-meeting-416:42
cloudnullhahaha16:43
cloudnullwrong channel16:43
palendaegj16:43
*** qwebirc61721 has quit IRC16:43
cloudnulljust to recap because im an idiot16:44
cloudnull[11:37] <palendae> That's happening. Only stones-- is tomorrow16:44
cloudnull[11:38] <cloudnull> https://review.openstack.org/#/c/189938/ needs further approval when someone gets a chance16:44
cloudnull[11:39] <palendae> cloudnull: was in process, should be ready soon16:44
b3rnard0i guess i know what i'm doing next week16:44
cloudnull[11:40] <cloudnull> palendae:  this spec was merged so i think we're good there. https://review.openstack.org/#/c/173155/16:44
cloudnull[11:41] <palendae> cloudnull: Yeah, just making sure I go over the scripty parts16:44
cloudnull[11:41] <cloudnull> ok.16:44
cloudnull[11:42] <cloudnull> palendae:  is there any blockers into further implementation ?16:44
cloudnull[11:42] <cloudnull> anything that you need to make it go?16:44
cloudnull[11:42] <palendae> cloudnull: Of docs? Getting healthy again :p16:44
cloudnull[11:43] <cloudnull> #action palendae needs to get healthy again16:44
cloudnull[11:43] <palendae> I need to re-review what's in the list in the BP and get to writing the rest of the sections16:44
cloudnull[11:43] <cloudnull> ok16:44
palendaewow the pings16:44
palendaeBut basically yes, the developer docs BP has stalled while I deal with health issus.16:45
cloudnullok16:45
cloudnullSam-I-Am: https://review.openstack.org/#/c/181544/ this spec has been stalled a bit too16:46
cloudnullcan we get some reviewers on it so that we can make it go.16:46
cloudnullseems like that leads us to the path of config validation16:46
sigmavirus24yes16:47
andymccrugh yeh i need to adjust my link to look for open specs too16:47
sigmavirus24which I need to find time to work on16:47
palendaeYeah, schema validation should be broken out16:47
cloudnullagreed.16:47
palendaeNot sure if that should be a hard prereq or not, but it does certainly make implementation of this easier16:48
cloudnullif someone has some cycles it would be great to get that spec written up . i think it will be of realy value for deployers.16:48
cloudnull*real16:48
sigmavirus24the cli works just fine, we just need schema(s?) written for the various config files16:49
sigmavirus24And I'm thinking of making the schema be able to be YAML16:49
sigmavirus24so that it's YAML schema for YAML files16:49
sigmavirus24Instead of having to write JSON16:49
palendaeOne thing that could put a wrench in that is extended config files. e.g. rpc-openstack has it's own16:50
palendaeNot sure if those would just go un-checked or what16:50
sigmavirus24palendae: the spec should have an opinion on when validation happens16:50
sigmavirus24Either as a pre-req to running the playbooks, as an optional part of running them, or as part of the playbooks somehow16:50
sigmavirus24I leave that decision as an exercise for the spec author16:51
stevelleI forget was linting going to be broken out or lumped into that16:51
stevelleI know there was discussion16:51
* svg just got home16:51
*** salv-orl_ has joined #openstack-meeting-416:52
*** sarob has joined #openstack-meeting-416:53
palendaestevelle: I don't remember. I could see it being included16:53
cloudnulllinting should remain stand alone imo16:53
*** s3wong has quit IRC16:54
*** yamahata has joined #openstack-meeting-416:54
*** salv-orlando has quit IRC16:54
cloudnullbut alas it also could be lumped in. im with sigmavirus24 the writer of the spec should sort that.16:54
sigmavirus24And it'll get yak shaved anyway16:55
sigmavirus24So16:55
sigmavirus24YOLO16:55
*** VW has joined #openstack-meeting-416:55
palendaeSure16:55
cloudnullSo in the last few min id like a quick pull of people , this meeting time seems to be less that ideal for a fair amout of folks,16:55
cloudnulldo we want to change it ?16:55
sigmavirus24I was going to bring that up in #openstack-ansible16:55
b3rnard0+116:55
palendae+1 from me. It's over the noon hour during DST16:55
sigmavirus24lol16:55
sigmavirus24+116:55
cloudnulland do we want to hold rotating meeting times for various time zones ?16:55
sigmavirus24rotating meetings work well for some projects16:56
sigmavirus24usually lends to confusion and frustration the largeer the project gets though16:56
b3rnard0+116:56
cloudnullok.16:56
andymccrfrom uk perspective, 5pm is often a time ppl need to leave for one reason or another. usually its ok for me personally but yeh i'd +116:56
sigmavirus24so it should work now, but we should be open to reconsidering in a few months16:56
odyssey4me+1 to rotation16:56
*** qwebirc1003062 has joined #openstack-meeting-416:56
cloudnullso when would be best?16:56
*** s3wong has joined #openstack-meeting-416:56
d34dh0r53should we -1 hour from the start time during DST?16:57
stevelleI would say move 1 hour earlier and call it done16:57
andymccr-1 hour would be good for uk i think, but not sure how that impacts on west coasters!16:57
stevelleif you can find a room16:57
Sam-I-Amcloudnull: er, yeah i need to work on that spec16:58
Sam-I-Amcloudnull: sort of had some higher priorities16:58
stevelleas a west-coaster, any more than 1h earlier is gonna hurt16:59
cloudnullso when do we want to do this in UTC?16:59
*** cathy_ has joined #openstack-meeting-416:59
Sam-I-Amcloudnull: maybe 2 meetings?16:59
stevelleI feel if we are going for governance, do meeting in UTC16:59
Sam-I-Ammeetings need to be in utc16:59
Sam-I-Amotherwise people's calendars get b3rnard0'd when DST happens in different locales17:00
cathy_#startmeeting SFC project17:00
openstackcathy_: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.17:00
*** johnsom has joined #openstack-meeting-417:00
b3rnard0Sam-I-Am: just give me a diagram17:00
Sam-I-Amlooks like we need to take this back to o-a17:00
*** LouisF has joined #openstack-meeting-417:00
cloudnull#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
cloudnullsorry17:00
openstackMeeting ended Thu Jun 11 17:00:43 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-06-11-16.03.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-06-11-16.03.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2015/openstack_ansible_meeting.2015-06-11-16.03.log.html17:00
cloudnullwe're out. sorry cathy_17:00
*** Sam-I-Am has left #openstack-meeting-417:01
cathy_$startmeeting SFC project17:01
cathy_#startmeeting SFC project17:01
openstackMeeting started Thu Jun 11 17:01:23 2015 UTC and is due to finish in 60 minutes.  The chair is cathy_. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:01
*** openstack changes topic to " (Meeting topic: SFC project)"17:01
openstackThe meeting name has been set to 'sfc_project'17:01
johnsomo/17:01
cathy_hi everyone17:01
qwebirc1003062Hi Cathy, This is Ramanjaneya..from vikram team17:01
pcarverhi17:01
igordcard_cathy_: hello17:01
igordcard_hi all17:01
*** alextricity_h has left #openstack-meeting-417:01
*** b3rnard0 has left #openstack-meeting-417:01
LouisFhi Ramanjaneya17:01
cathy_ok let's start17:02
*** Slower has quit IRC17:02
*** lazy_prince has joined #openstack-meeting-417:02
cathy_#topic update on action items of last meeting17:02
*** openstack changes topic to "update on action items of last meeting (Meeting topic: SFC project)"17:02
*** stevelle has left #openstack-meeting-417:02
*** nbouthors has joined #openstack-meeting-417:02
cathy_So the repository for this feature development is being created.17:03
Swamihi17:03
cathy_armax: are you there?17:03
cathy_Swami: hi17:03
armaxhi17:03
nbouthorshello17:03
cathy_For the network controller driver, I have updated the slide for that17:04
cathy_nbouthors: hi17:04
cathy_armax: do you have if the repository has been created or the infra team is still reviewing it?17:05
cathy_I means do you know?17:05
armaxcathy_: it’s still in progress…I suspect the infra team is busy dealing with a few project renames17:05
armaxcathy_: it’ll be a little while longer17:05
cathy_armax: ok, thanks17:06
*** bnemec has joined #openstack-meeting-417:06
*** puranamr has joined #openstack-meeting-417:06
cathy_here is the link to the slides https://docs.google.com/presentation/d/1SpVyLBCMRFBpMh7BsHmpENbSY6qh1s5NRsAS68ykd_0/edit?usp=sharing17:07
cathy_any comment or questions on the action items?17:07
armaxcathy_: let me reply to your question regarding agentless architecture in this forum17:08
cathy_Ok, let's go to the next topic17:08
armax?17:08
*** fitoduarte has joined #openstack-meeting-417:08
cathy_#topic Neutron port chain API17:08
*** openstack changes topic to "Neutron port chain API (Meeting topic: SFC project)"17:08
*** Slower has joined #openstack-meeting-417:08
cathy_armax: go ahead17:09
Swamicathy_: can you post your question here for the benefit of the audience.17:09
fitoduarte.17:09
LouisFarmax: go ahead17:10
armaxcathy_: ok17:10
*** dwalleck has quit IRC17:10
armaxI am assuming that in slide 217:10
armaxthat the component running the ovs agent is compute host?17:11
armaxor can it be something else?17:11
Swamiarmax: Yes it is the compute host.17:11
LouisFarmax: yes17:11
cathy_armax: yes17:12
armaxhaving said that, I was asking if you guys had considered making the interaction between the controller node and the compute node without relying on the ovs agent17:12
yamahataBoth traffic classifier and SFF?17:12
cathy_what do you mean by the controller node?17:12
Swamicontroller node is the neutron server node.17:12
LouisFarmax: can you give more details and perhaps and exmaple of where this is done?17:12
LouisFan example17:13
armaxanyhow some for thought, I think it’s premature to talk about the architecture if we don’t first finalize whe most rudimentary API we want to implement this cycle17:13
armaxLouisF: well, we don’t necessily need to talk to the ovs agent, that’s all17:13
SwamiLouisF: for example in the current OVN architecture there is no agent in the compute node. So in future if we want to adopt such technology, we should be able to go agentless. That is what armax is pointing out.17:14
*** lazy_prince has quit IRC17:14
cathy_In existing OVS, it talks to the neutron Server through OVS agent. Are you suggesting to change this?17:14
armaxall I am saying is that OVS can be controlled remotely17:15
armaxjust like other solutions do17:15
armaxcathy_: I am simply asking if you had considered it17:16
armaxcathy_: I am not suggesting anything right now :)17:16
*** jwagner is now known as jwagner_away17:16
*** marcusvrn1 has joined #openstack-meeting-417:16
LouisFsonds like that is worthwile considering17:16
cathy_armax: it is a possible option in the future17:17
*** nbouthors_ has joined #openstack-meeting-417:17
*** odyssey4me has left #openstack-meeting-417:17
armaxcathy_: I wouldn’t rule it out completely, and consider it a ‘future’ option17:17
cathy_Will the OVN architecture available in L release?17:18
armaxcathy_: because until we figure out what interaction is required with the vswitch everything is fair game17:18
armaxcathy_: OVN has nothing to do with what I am saying17:18
*** nbouthors has quit IRC17:18
cathy_I see that Swami said that you are referring to OVN architecture.17:19
Swamicathy_: I just gave an example for LouisF.17:19
armaxSwami: no I wasn't17:19
cathy_Maybe it is better to discuss this in the email to clarify what you have in mind. Let's move on to next topic17:20
cathy_armax: OK with you?17:21
armaxcathy_: yss17:21
*** Mohankumar_ has joined #openstack-meeting-417:21
pcarvercathy_: other examples would be Contrail and Nuage. Nothing specific to OVN, just lots of options out there that either do or will support service chaining17:21
pcarverThe service chaining API shouldn't be tied tightly to any one implementation17:22
armaxpcarver: noone is saying otherwise as far as I can tell :)17:22
LouisFpcarver: agree, there should drivers for a wide variety of backend implementations17:22
cathy_So if you are talking about different types of SDN controller, then it is through controller driver which is separate from the OVS driver. how about we discuss this in the email since the meeting time is short.17:22
LouisFshould be17:22
cathy_$topic Neutron port chain API for SFC17:23
cathy_#topic 2.Neutron port chain API for SFC17:23
*** openstack changes topic to "2.Neutron port chain API for SFC (Meeting topic: SFC project)"17:23
armaxcathy_: I recall that vikram was going to respin https://review.openstack.org/#/c/17794617:23
armaxcathy_: any news on that? I have seen nothing popping up17:23
*** jwarendt has joined #openstack-meeting-417:23
armaxis vikram around?17:24
Mohankumar_HI cathy ..17:24
Mohankumar_mohan here from vikram team17:24
LouisFarmax: i will be updating, vikram is on vavation17:24
LouisFvacation17:24
cathy_armax: vikram is on vacation. Louis will take care of this17:24
Mohankumar_we started neutron client changes17:24
armaxLouisF: ok, thanks, I think ultimately that spec will have to be moved over to the repo for SFC once we have it up and running17:24
LouisFarmax: yes thanks17:25
armaxLouisF: but for now, let’s iterate on that patch17:25
LouisFarmax: agree17:25
cathy_We will update the spec incorporating all the comments/input17:25
*** dhruvdhody has joined #openstack-meeting-417:25
qwebirc1003062Hi I'm Ramanjaneya from vikram team..17:25
qwebirc1003062on behalf of vikram, Mohan started neutron client changes..17:25
cathy_let's now discuss the API and see if any questions/comments?17:26
armaxqwebirc1003062: the neutron client changes are the last thing you wan’t to do17:26
armax*want17:27
cathy_I know quite some people have given comments on that spec. Any issue/input that we can discuss in this meeting?17:27
cathy_To move forward and make it for the L release, we need to reach consensus on the API and finalize the API17:28
LouisFwe need to get conensus and agreement  on the api first before making any changes17:28
Mohankumar_agree17:28
cathy_maybe we should put a time line on finalizing the API17:28
cathy_?17:29
armaxcathy_: reviewing the API in the current status of the spec is a bit painful17:29
armaxcathy_: as the wrong diff gets in the way17:29
armaxthis might deter some people from reviewing perhaps?17:29
LouisFarmax: what do you mean by that?17:30
cathy_armax: what do you mean by wrong diff?17:30
armaxLouisF: https://review.openstack.org/#/c/177946/17:30
armaxit shows that patch 177946 depends on an abandoned patch17:30
armaxand the actual diff includes two modified files and a deleted one17:30
armaxfor something that should be freshly proposed that hardly makes any sense17:30
armaxthe diff is: +124, -51017:31
armaxwhen it should simply be only additions17:31
cathy_armax: yes, that is a confusing. Louis could you fix that?17:31
LouisFarmax: ok17:31
cathy_so Louis will clean that up. Quite come people have given comments and there are multiple updated versions. I would suggest that everyone goes to the link and check the latest version and see if you have any more comments.17:33
*** dhruvdhody has quit IRC17:33
armaxcathy_: yes, I’d give us one more week to see if we can pull it together17:34
cathy_How about we get the review completed in two weeks from today so that we can start developing the code?17:34
*** praveens has joined #openstack-meeting-417:34
cathy_armax: one week is OK with me17:35
armaxcathy_: once the repo is set up and we move the spec over there, we can have one final push and start iterating on the code itself17:35
LouisFarmax: i will put the spec in the networking-sfc repo17:35
armaxcathy_: do we know of anyone who has started coding on a skeleton of the architecture that you put together with Sw?17:36
armax*Swami17:36
*** qwebirc1003062 has quit IRC17:36
Swamiarmax:hi17:36
cathy_armax: Ok, so let's get the review done in one week and then we will have the spec over the new repo and start implementing it17:36
cathy_some people have contacted me to sign up for development of different pieces of the architecture, We will cover this later in this meeting.17:37
armaxcathy_: cool17:37
cathy_that is one of our meeting topics too17:37
cathy_now let's go to next topic17:38
cathy_#topic Unified API and data model for flow classifier that can be used for SFC, QoS, Packet forwarding etc.17:38
*** openstack changes topic to "Unified API and data model for flow classifier that can be used for SFC, QoS, Packet forwarding etc. (Meeting topic: SFC project)"17:38
*** s3wong has quit IRC17:39
cathy_Since Yujin can not join this IRC meeting and Vikram has signed up on driving this and Vikram is on vacation. let's move this topic to next meeting.17:39
Swamicathy_: Here is the link to the spec. #link https://review.openstack.org/#/c/186663/17:40
cathy_So let's go to next topic17:40
armaxcathy_: although I am in favor of this initiative, I am not sure it’s the most sensible thing to do right now17:40
armaxcathy_: I wonder if it’s better striving for some unification once we got some practical experience on how all these initiatives play out17:41
cathy_Swami: the flow classifier in https://review.openstack.org/#/c/186663/ is very similar to the flow classifier proposed in https://review.openstack.org/#/c/177946/17:41
LouisFarmax: is would be useful to have a common api for a flow classifier17:41
cathy_armax: agree17:41
*** dwalleck has joined #openstack-meeting-417:41
*** s3wong has joined #openstack-meeting-417:42
armaxcathy_: especially if these initiatives are tacked separately, it may be difficult to coordinate who does what17:42
armaxLouisF: agree17:42
cathy_Since what Yujin proposed and wanted for packet forwarding is very close to what is proposed by the SFC spec https://review.openstack.org/#/c/177946/, let's implement the flow classifier in this SFC project but make it a independent module which cna be used or extended for other use case17:43
Swamicathy_: have you communicated to Yujin on this.17:44
*** radek_ has joined #openstack-meeting-417:44
cathy_Agree with Armax that let's first play it out and get some practical experience.17:44
cathy_Swami: I will via email17:44
cathy_Swami: it will be confusing to propose very similar API and data model in two separate spec. Let's merge it into one spec17:45
Swamicathy_: agree17:45
cathy_Shall we move to the next topic?17:45
LouisFlets suggest that to Yuji17:45
*** sdake has joined #openstack-meeting-417:46
cathy_LouisF: yes17:46
*** s3wong_ has joined #openstack-meeting-417:46
cathy_#topic : functional module breakdown and Module development ownership sign-up17:46
*** openstack changes topic to ": functional module breakdown and Module development ownership sign-up (Meeting topic: SFC project)"17:46
*** dwalleck has quit IRC17:46
cathy_let's reference to the slide and I will go one by one17:47
*** igordcard has joined #openstack-meeting-417:47
*** s3wong has quit IRC17:47
cathy_slide 417:47
cathy_1. repo creation, Armax has taken this. Thanks Armax!17:48
cathy_2 Integration with Neutron/devstack, CLI, Horizon, Heat, Anyone wants to take this?17:48
*** banix has joined #openstack-meeting-417:48
cathy_Mohankumar_: would you like to take this work?17:49
Mohankumar_yes cathy17:50
cathy_great, Thanks Mohankumar_ !17:50
cathy_now Service chain API Extension. Anyone takes this?17:50
LouisFi can take that17:50
cathy_Thanks Louis!17:50
Mohankumar_thanks :)17:51
cathy_Service chain Plugin: API handling and Data Base. Anyone?17:51
LouisFi'l do that also17:51
cathy_I can take this17:51
cathy_Thanks Louis!17:51
cathy_OVS Driver  ?17:52
LouisFwe need to also have a driver manager17:52
cathy_LouisF: do you mean the common service chain API shim layer?17:53
LouisFto handle the different backend drivers eg ovs, odl....17:53
*** dannywil_ has joined #openstack-meeting-417:53
LouisFyes17:53
cathy_common service chain API shim layer. Anyone wants to take this piece?17:53
LouisFi will look at that17:54
*** IlyaG has joined #openstack-meeting-417:54
cathy_ok, thanks louis!17:54
cathy_OVS agent on Host. Anyone taking this piece?17:54
armaxcathy_: it’s probably better to ask what LouisF doesn’t want to do :)17:54
*** sdake_ has joined #openstack-meeting-417:54
cathy_armax: :-)17:55
armaxcathy_: for that I’d wait a little longer, as we might not  even need it17:55
LouisFplease volunterer and i am glad to hand off17:55
LouisFyou mean use ovn?17:55
cathy_armax: OK, let's go to the next piece17:55
armaxthis task assigment is going to be in flux anyway…in my experience people come and go so we’d need to be prepared to step in :)17:55
*** bharath has joined #openstack-meeting-417:55
armaxLouisF: forget about OVN :)17:55
armaxLouisF: I never mentioned it and blame Swami for putting it in people’s mind17:56
armaxs17:56
SwamiLouisF: If you want me to take up the ext and plugin part I can take it.17:56
LouisF:]17:56
cathy_armax: 100% agree with that we need to be prepared to step in.17:56
Swamiarmax: I swear that I just gave an example17:56
cathy_Service chain Classifier on host. Anyone?17:56
armaxSwami: I know, I know :)17:57
*** dannywilson has quit IRC17:57
IlyaGHi! anyone tried to run CI on top of Fuel Juno using ESX?17:57
*** mmedvede has joined #openstack-meeting-417:57
LouisFmay nicolas?17:57
LouisFmaybe17:57
cathy_I know that Nicolos will take this piece. He has told me that17:57
*** SumitNaiksatam has joined #openstack-meeting-417:57
cathy_Service function forwarder with NSH Type 2 encapsulation. Anyone?17:58
cathy_Swami: would you like to take this?17:58
*** sdake has quit IRC17:58
*** s3wong has joined #openstack-meeting-417:58
*** s3wong_ has quit IRC17:58
cathy_I can help with this piece too17:58
cathy_Swami: ?17:59
*** VW has quit IRC17:59
Swamicathy_: sorry I was looking at some other information.17:59
igordcardWhat are you going to use as NSH-aware VNFs?17:59
nbouthors_ cathy: we can provide a service classifier17:59
Swamicathy_: yes i am here17:59
Swamicathy_: I can help with the classifier.18:00
cathy_igordcard: not NSH-aware VNF for the first release18:00
cathy_let's wrap the meeting up.18:01
cathy_and continue in next meeting.18:01
cathy_Thanks everyone. Bye now18:01
igordcard bye18:01
armaxbye18:01
Mohankumar_bye !18:01
cathy_#endmeeting18:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:01
openstackMeeting ended Thu Jun 11 18:01:48 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/sfc_project/2015/sfc_project.2015-06-11-17.01.html18:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/sfc_project/2015/sfc_project.2015-06-11-17.01.txt18:01
openstackLog:            http://eavesdrop.openstack.org/meetings/sfc_project/2015/sfc_project.2015-06-11-17.01.log.html18:01
Swamibye18:01
*** VW has joined #openstack-meeting-418:02
*** ivar-lazzaro has joined #openstack-meeting-418:04
*** cathy_ has quit IRC18:06
*** jwagner_away is now known as jwagner18:08
*** LouisF has quit IRC18:10
*** praveens has quit IRC18:13
*** krtaylor has joined #openstack-meeting-418:18
*** sigmavirus24 is now known as sigmavirus24_awa18:19
*** banix has quit IRC18:19
*** salv-orl_ has quit IRC18:20
*** salv-orlando has joined #openstack-meeting-418:21
*** Mohankumar_ has quit IRC18:23
*** salv-orlando has quit IRC18:26
*** s3wong has quit IRC18:27
*** kenhui has quit IRC18:31
*** kenhui has joined #openstack-meeting-418:32
*** kenhui has quit IRC18:32
*** Kiall has quit IRC18:37
*** wko has quit IRC18:42
*** singleth_ has joined #openstack-meeting-418:52
*** singlethink has quit IRC18:55
*** sjmc7 has joined #openstack-meeting-418:57
*** dannywil_ has quit IRC18:59
*** dannywilson has joined #openstack-meeting-419:01
*** VW_ has joined #openstack-meeting-419:02
*** igordcard has quit IRC19:03
*** VW has quit IRC19:04
*** VW_ has quit IRC19:10
*** VW has joined #openstack-meeting-419:10
*** nbouthors_ has quit IRC19:15
*** marcusvrn has quit IRC19:24
*** VW has quit IRC19:25
*** salv-orlando has joined #openstack-meeting-419:26
*** puranamr has quit IRC19:29
*** VW has joined #openstack-meeting-419:31
*** banix has joined #openstack-meeting-419:36
*** VW has quit IRC19:39
*** VW has joined #openstack-meeting-419:42
*** AlanClark has quit IRC19:44
*** simon-AS5591 has joined #openstack-meeting-419:44
*** sdake_ has quit IRC19:53
*** sdake has joined #openstack-meeting-419:55
*** banix has quit IRC20:03
*** BjoernT has left #openstack-meeting-420:14
*** xingchao has joined #openstack-meeting-420:21
*** matrohon has joined #openstack-meeting-420:24
*** Sukhdev has joined #openstack-meeting-420:25
*** xingchao has quit IRC20:27
*** GB21 has quit IRC20:29
*** bknudson has quit IRC20:45
*** marcusvrn1 has quit IRC20:49
*** jwagner is now known as jwagner_away20:52
*** puranamr has joined #openstack-meeting-420:54
*** singleth_ has quit IRC20:55
*** singlethink has joined #openstack-meeting-420:55
*** rfolco has quit IRC20:59
*** dannywil_ has joined #openstack-meeting-420:59
*** dannywilson has quit IRC21:02
*** jwarendt has quit IRC21:04
-openstackstatus- NOTICE: Gerrit has been restarted to terminate a persistent looping third-party CI bot21:07
*** banix has joined #openstack-meeting-421:10
*** s3wong has joined #openstack-meeting-421:18
*** radek_ has quit IRC21:24
*** puranamr has quit IRC21:26
*** Slower has quit IRC21:34
*** puranamr has joined #openstack-meeting-421:35
*** puranamr has quit IRC21:38
*** Slower has joined #openstack-meeting-421:41
*** dims_ has joined #openstack-meeting-421:44
*** dims has quit IRC21:46
*** puranamr has joined #openstack-meeting-421:47
*** bknudson has joined #openstack-meeting-421:47
*** puranamr has quit IRC21:54
*** dannywil_ has quit IRC21:54
*** rods has quit IRC21:54
*** dannywilson has joined #openstack-meeting-421:56
*** galstrom is now known as galstrom_zzz21:57
*** singleth_ has joined #openstack-meeting-421:57
*** johnsom has left #openstack-meeting-421:58
*** bharath has quit IRC21:59
*** bharath has joined #openstack-meeting-421:59
*** singlethink has quit IRC22:00
*** VW has quit IRC22:00
*** puranamr has joined #openstack-meeting-422:00
*** matrohon has quit IRC22:03
*** mitchjameson has joined #openstack-meeting-422:05
*** agalkin has joined #openstack-meeting-422:11
*** ivar-lazzaro has quit IRC22:11
*** ivar-lazzaro has joined #openstack-meeting-422:13
*** klamath has quit IRC22:16
*** jckasper has quit IRC22:16
*** Sukhdev has quit IRC22:25
*** simon-AS5591 has quit IRC22:29
*** VW has joined #openstack-meeting-422:31
*** singleth_ has quit IRC22:33
*** guimaluf has quit IRC22:33
*** bnemec has quit IRC22:34
*** salv-orlando has quit IRC22:34
*** puranamr has quit IRC22:40
*** aventerav has quit IRC22:49
*** VW has quit IRC22:49
*** padkrish has joined #openstack-meeting-422:59
*** puranamr has joined #openstack-meeting-423:01
*** krtaylor has quit IRC23:04
*** puranamr has quit IRC23:06
*** fallenpegasus has quit IRC23:09
*** MarkAtwood has quit IRC23:10
*** puranamr has joined #openstack-meeting-423:11
*** markvoelker has quit IRC23:11
*** carl_baldwin has quit IRC23:14
*** Sukhdev has joined #openstack-meeting-423:19
*** sigmavirus24_awa is now known as sigmavirus2423:39
*** blahRus has quit IRC23:44
*** salv-orlando has joined #openstack-meeting-423:49
*** salv-orlando has quit IRC23:53
*** Swami has quit IRC23:57

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