Monday, 2014-11-24

*** banix has joined #openstack-meeting-300:23
*** armax has joined #openstack-meeting-300:24
*** sarob has quit IRC00:28
*** salv-orlando has quit IRC00:29
*** emagana has joined #openstack-meeting-300:29
*** emagana has quit IRC00:34
*** banix has quit IRC00:38
*** armax has quit IRC00:42
*** banix has joined #openstack-meeting-300:44
*** SridharRamaswamy has joined #openstack-meeting-301:08
*** banix has quit IRC01:09
*** Ark has joined #openstack-meeting-301:15
*** Ark is now known as Guest8123601:15
*** superdan is now known as dansmith01:23
*** emagana has joined #openstack-meeting-301:23
*** lhcheng has quit IRC01:24
*** dboik has joined #openstack-meeting-301:24
*** dboik_ has joined #openstack-meeting-301:26
*** emagana has quit IRC01:28
*** dboik has quit IRC01:29
*** SridharRamaswamy has quit IRC01:31
*** MaxV has joined #openstack-meeting-301:46
*** wuhg has joined #openstack-meeting-301:47
*** MaxV has quit IRC01:51
*** banix has joined #openstack-meeting-301:56
*** Guest81236 has quit IRC02:05
*** sigmavirus24_awa is now known as sigmavirus2402:12
*** emagana has joined #openstack-meeting-302:17
*** emagana has quit IRC02:22
*** lhcheng has joined #openstack-meeting-302:24
*** lhcheng has quit IRC02:28
*** baojg has joined #openstack-meeting-302:33
*** armax has joined #openstack-meeting-302:40
*** dboik_ has quit IRC02:48
*** MaxV has joined #openstack-meeting-302:58
*** MaxV has quit IRC03:02
*** emagana has joined #openstack-meeting-303:12
*** Ark has joined #openstack-meeting-303:16
*** Ark is now known as Guest4798303:16
*** emagana has quit IRC03:16
*** Guest47983 has quit IRC03:20
*** sarob has joined #openstack-meeting-303:29
*** sarob has quit IRC03:33
*** shwetaap has joined #openstack-meeting-303:37
*** baoli has quit IRC03:37
*** baoli has joined #openstack-meeting-303:38
*** baojg has quit IRC03:39
*** banix has quit IRC03:39
*** baojg has joined #openstack-meeting-303:40
*** baojg has quit IRC03:44
*** sigmavirus24 is now known as sigmavirus24_awa03:45
*** banix has joined #openstack-meeting-303:46
*** armax has quit IRC03:58
*** armax has joined #openstack-meeting-303:59
*** armax has quit IRC04:00
*** emagana has joined #openstack-meeting-304:06
*** emagana has quit IRC04:10
*** armax has joined #openstack-meeting-304:20
*** banix has quit IRC04:20
*** baojg has joined #openstack-meeting-304:24
*** jacalcat has joined #openstack-meeting-304:28
*** jacalcat has left #openstack-meeting-304:29
*** armax has quit IRC04:36
*** baojg has quit IRC04:43
*** baojg has joined #openstack-meeting-304:43
*** baojg has quit IRC04:44
*** baojg has joined #openstack-meeting-304:45
*** baojg has quit IRC04:49
*** baoli has quit IRC05:06
*** SridharRamaswamy has joined #openstack-meeting-305:13
*** armax has joined #openstack-meeting-305:16
*** SridharRamaswamy has quit IRC05:21
*** Longgeek has joined #openstack-meeting-305:21
*** baojg has joined #openstack-meeting-305:23
*** Longgeek has quit IRC05:27
*** armax has quit IRC05:28
*** k4n0 has joined #openstack-meeting-306:00
*** baojg has quit IRC06:05
*** baojg has joined #openstack-meeting-306:06
*** SridharRamaswamy has joined #openstack-meeting-306:06
*** baojg has quit IRC06:10
*** baojg has joined #openstack-meeting-306:22
*** mrunge has joined #openstack-meeting-306:53
*** Longgeek has joined #openstack-meeting-307:05
*** belmoreira has joined #openstack-meeting-307:19
*** mrmartin has joined #openstack-meeting-307:38
*** jgallard_ has joined #openstack-meeting-307:40
*** SridharRamaswamy has quit IRC07:42
*** belmoreira has quit IRC07:42
*** jtomasek has joined #openstack-meeting-307:42
*** salv-orlando has joined #openstack-meeting-307:42
*** emagana has joined #openstack-meeting-307:44
*** belmoreira has joined #openstack-meeting-307:45
*** ivar-lazzaro has quit IRC07:46
*** emagana has quit IRC07:49
*** baojg has quit IRC08:02
*** baojg has joined #openstack-meeting-308:03
*** ttrifonov is now known as zz_ttrifonov08:04
*** baojg has quit IRC08:08
*** stanzgy has quit IRC08:09
*** stanzgy has joined #openstack-meeting-308:10
*** iovadia has joined #openstack-meeting-308:14
*** baojg has joined #openstack-meeting-308:27
*** zz_ttrifonov is now known as ttrifonov08:29
*** bauzer is now known as bauzas08:31
*** jcoufal has joined #openstack-meeting-308:31
*** sergef has joined #openstack-meeting-308:38
*** emagana has joined #openstack-meeting-308:38
*** MaxV has joined #openstack-meeting-308:41
*** emagana has quit IRC08:43
*** matrohon has joined #openstack-meeting-308:56
*** pkoniszewski has joined #openstack-meeting-309:00
*** nfedotov has joined #openstack-meeting-309:02
*** hareeshp has joined #openstack-meeting-309:20
*** pkarikh has joined #openstack-meeting-309:22
*** hareeshp has quit IRC09:25
*** hareeshp has joined #openstack-meeting-309:26
*** safchain has joined #openstack-meeting-309:30
*** emagana has joined #openstack-meeting-309:33
*** lhcheng has joined #openstack-meeting-309:34
*** Longgeek has quit IRC09:35
*** emagana has quit IRC09:37
*** yamamoto has joined #openstack-meeting-309:39
*** Longgeek has joined #openstack-meeting-309:51
*** jcoufal has quit IRC09:51
*** lhcheng_ has joined #openstack-meeting-309:54
*** belmoreira has quit IRC09:55
*** lhcheng has quit IRC09:56
*** belmoreira has joined #openstack-meeting-310:26
*** VineetMenon is now known as mathew10:26
*** mathew is now known as mathew198810:26
*** mathew1988 is now known as mvineet10:27
*** emagana has joined #openstack-meeting-310:27
*** mvineet is now known as vineetmenon10:31
*** emagana has quit IRC10:31
*** yamamoto has quit IRC10:36
*** baojg has quit IRC10:44
*** baojg has joined #openstack-meeting-310:45
*** stanzgy has quit IRC10:49
*** yamamoto has joined #openstack-meeting-310:49
*** baojg has quit IRC10:51
*** jcoufal has joined #openstack-meeting-310:53
*** shwetaap has quit IRC10:54
*** yamamoto has quit IRC11:07
*** MaxV has quit IRC11:08
*** yamamoto has joined #openstack-meeting-311:10
*** MaxV has joined #openstack-meeting-311:12
*** jgallard_ has quit IRC11:15
*** emagana has joined #openstack-meeting-311:21
*** emagana has quit IRC11:25
*** MaxV has quit IRC11:27
*** hareeshp has quit IRC11:29
*** hareeshp has joined #openstack-meeting-311:30
*** dkehn has quit IRC11:56
*** hareeshp has quit IRC11:56
*** dkehn has joined #openstack-meeting-311:57
*** vkmc has joined #openstack-meeting-312:22
*** vkmc has quit IRC12:22
*** vkmc has joined #openstack-meeting-312:22
*** baojg has joined #openstack-meeting-312:25
*** baojg has quit IRC12:26
*** baojg has joined #openstack-meeting-312:27
*** MaxV has joined #openstack-meeting-312:27
*** baojg has quit IRC12:31
*** b3nt_pin is now known as beagles12:39
*** baojg has joined #openstack-meeting-312:47
*** baojg has quit IRC12:48
*** baojg_ has joined #openstack-meeting-312:48
*** jcoufal_ has joined #openstack-meeting-312:51
*** jcoufal has quit IRC12:54
*** baojg_ has quit IRC12:58
*** baojg has joined #openstack-meeting-312:59
*** k4n0 has quit IRC13:00
*** baojg_ has joined #openstack-meeting-313:01
*** baojg has quit IRC13:01
*** hareeshp has joined #openstack-meeting-313:04
*** jaypipes has joined #openstack-meeting-313:05
*** emagana has joined #openstack-meeting-313:09
*** emagana has quit IRC13:13
*** hareeshp has quit IRC13:15
*** baoli has joined #openstack-meeting-313:22
*** baoli has quit IRC13:22
*** baoli has joined #openstack-meeting-313:23
*** shwetaap has joined #openstack-meeting-313:23
*** jacalcat has joined #openstack-meeting-313:23
*** jacalcat has left #openstack-meeting-313:23
*** jraim has quit IRC13:24
*** shwetaap1 has joined #openstack-meeting-313:24
*** zhiyan has quit IRC13:24
*** jraim has joined #openstack-meeting-313:25
*** sweston_ has quit IRC13:25
*** sweston_ has joined #openstack-meeting-313:25
*** zhiyan has joined #openstack-meeting-313:27
*** shwetaap has quit IRC13:28
*** asahlin has quit IRC13:29
*** julim has joined #openstack-meeting-313:33
*** thomasem has joined #openstack-meeting-313:34
*** thomasem has quit IRC13:34
*** matrohon has quit IRC13:34
*** matrohon has joined #openstack-meeting-313:35
*** sigmavirus24_awa is now known as sigmavirus2413:38
*** thomasem has joined #openstack-meeting-313:39
*** alexpilotti has joined #openstack-meeting-313:43
*** thomasem has quit IRC13:49
*** jgallard_ has joined #openstack-meeting-313:50
*** alexpilotti has quit IRC13:52
*** jgallard_ has quit IRC13:53
*** jgallard_ has joined #openstack-meeting-313:53
*** jgallard_ has quit IRC13:53
*** thomasem has joined #openstack-meeting-313:54
*** thomasem has quit IRC13:56
*** thomasem has joined #openstack-meeting-313:57
*** iovadia1 has joined #openstack-meeting-313:58
*** mrunge has quit IRC13:58
*** xuhanp has joined #openstack-meeting-313:59
*** asahlin has joined #openstack-meeting-314:00
*** shwetaap1 has quit IRC14:00
*** shwetaap has joined #openstack-meeting-314:00
*** iovadia has quit IRC14:02
*** otherwiseguy has joined #openstack-meeting-314:03
*** emagana has joined #openstack-meeting-314:04
*** iovadia1 has quit IRC14:06
*** iovadia has joined #openstack-meeting-314:08
*** emagana has quit IRC14:09
*** shwetaap has quit IRC14:10
*** lhcheng_ is now known as lhcheng14:24
*** belmoreira has quit IRC14:31
*** dboik has joined #openstack-meeting-314:44
*** zhipeng has joined #openstack-meeting-314:47
*** shwetaap has joined #openstack-meeting-314:52
*** emagana has joined #openstack-meeting-314:53
*** wuhg has quit IRC14:53
*** obondarev has quit IRC14:56
*** obondarev has joined #openstack-meeting-314:57
*** jpomero_ is now known as jpomero14:58
*** xuhanp has quit IRC15:02
*** xuhanp has joined #openstack-meeting-315:08
*** xuhanp has quit IRC15:09
*** zz_jgrimm is now known as jgrimm15:15
*** iovadia has quit IRC15:17
*** dboik_ has joined #openstack-meeting-315:27
*** peristeri has joined #openstack-meeting-315:28
*** iovadia has joined #openstack-meeting-315:30
*** dboik has quit IRC15:30
*** hurgleburgler has joined #openstack-meeting-315:33
*** asahlin has quit IRC15:37
*** asahlin_ has joined #openstack-meeting-315:37
*** gholler has joined #openstack-meeting-315:38
*** asahlin_ is now known as asahlin15:40
*** iovadia has quit IRC15:41
*** banix has joined #openstack-meeting-315:47
*** emagana has quit IRC15:47
*** emagana has joined #openstack-meeting-315:47
*** ycombinator_ has joined #openstack-meeting-315:47
*** carl_baldwin has joined #openstack-meeting-315:51
*** mattfarina has joined #openstack-meeting-315:52
*** dboik_ has quit IRC15:55
*** dboik has joined #openstack-meeting-315:56
*** dboik has quit IRC15:57
*** dboik has joined #openstack-meeting-315:57
krotscheck#startmeeting StoryBoard16:00
openstackMeeting started Mon Nov 24 16:00:22 2014 UTC and is due to finish in 60 minutes.  The chair is krotscheck. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: StoryBoard)"16:00
openstackThe meeting name has been set to 'storyboard'16:00
*** yolanda has joined #openstack-meeting-316:00
krotscheckAgenda: https://wiki.openstack.org/wiki/StoryBoard#Agenda16:00
krotscheckAlthough to be honest, that agenda is starting to get a bit out of hand. I’m going to rework the wiki a tad.16:01
ttxo/16:01
krotscheck#action krotscheck Reorganize agenda wiki.16:01
krotscheck#topic Actions from last week: Migration16:01
*** openstack changes topic to "Actions from last week: Migration (Meeting topic: StoryBoard)"16:01
*** SotK has joined #openstack-meeting-316:02
krotscheckOk, so migration bugs were fixed, infra was migrated, email was sent, and things are more or less wrapped on that topic.16:02
ttxwoohoo16:02
krotscheckIndeed :)16:02
*** shwetaap has quit IRC16:02
krotscheckWe’ve also got… two confirmed downstream users of storyboard now.16:03
*** shwetaap has joined #openstack-meeting-316:03
krotscheckSo no more breaking downstream.16:03
NikitaKonovalovo/16:03
NikitaKonovalovfinally back from summit and vacation16:03
jeblairyay!16:03
krotscheckWoo vacation!16:04
ttxNikitaKonovalov: welcome back!16:04
krotscheck#topic Urgent Items16:04
*** openstack changes topic to "Urgent Items (Meeting topic: StoryBoard)"16:04
krotscheckAnything urgent?16:04
*** enikanorov has quit IRC16:04
NikitaKonovalovnothing from me16:04
krotscheckI have a not-really-urgent-but-omg-annoying thing.16:05
krotscheckThe webclient is super chatty - as in it makes a lot of unecessary API calls.16:05
krotscheckI did some work last week to fix that.16:05
krotscheckOr, at least, mitigate it.16:05
krotscheckANd those reviews are up16:05
yolandathe caching changes? i'm still not very confident about that, but it can help16:05
krotscheckOk, let’s talk about that in discussion, if you have concerns let’s raise ‘em.16:06
krotscheckAny other urgent items?16:07
krotscheckAnything from our users? (jeblair that’s you)16:07
jeblairkrotscheck: i haven't been back enough from my own vacation to be on top of that feedback.  i will endeavor to be so asap.  :)16:07
krotscheckjeblair: You got it :)16:08
krotscheckWe got a bunch of comments in the channel on wed/thur, and those have spawned a few stories.16:08
krotscheckBut nothing super crazy16:08
jeblairawesome, just what we wande16:08
krotscheckMore I want features, When will this happen, etc kind of questions.16:08
jeblairwanted16:08
krotscheckAnyway16:08
krotscheck#topic Discussion: Core Reviewers16:08
*** openstack changes topic to "Discussion: Core Reviewers (Meeting topic: StoryBoard)"16:08
*** jedimike has joined #openstack-meeting-316:09
fungiit's been working great so far16:09
krotscheckSo, this topic was raised by yolanda last week. She’s been doing a lot of code reviews, and has been asking a lot of really good questions, and she was curious as to what it takes to be a storyboard core.16:09
krotscheckAnd I didn’t have an answer!16:09
yolandayes, i've been really interested in the project, i love working on it and i really want to be core of it16:10
krotscheckSo what I’d like to do is figure out what we as a team want a storyboard core to be.16:10
jeblairkrotscheck: one good first order approximation is this: when you see a +1 or -1 from a person, do you start to treat it as a +/-2 in your mind16:10
ttxthen you bend the spoon16:11
krotscheckjeblair: That’s a good one.16:11
*** enikanorov has joined #openstack-meeting-316:11
ttxthen there is no spoon16:11
krotscheckjeblair: What about seeing a +2 and treating it like a +1? ;)16:11
jeblairare you confident that person understands the code well enough to identify problematic code before it merges, understands the road map well enough to take it in the direction the project should go, and engaged enough that the investment will be worthwhile16:12
krotscheckMind if I copy that verbatim into the wiki?16:12
jeblairkrotscheck: not at all16:12
krotscheckCoool16:13
jeblairkrotscheck: and about the +2 as a +1, that's a concern too.  most people with +2 should know when they are reviewing something out of their area of expertise16:13
jeblairkrotscheck: and should generally downgrade their own votes accordingly16:13
krotscheckjeblair: Well, we’re in a weird position on that one, since there’s a lot of +2’s that we inherit from infra.16:13
jeblairkrotscheck: so actually, understanding that that person knows their own limits is a good thing to look for in a potential core reviewer as well16:13
jeblairkrotscheck: if you feel like we are overstepping bounds, i'm happy to talk about it16:13
ttxalso we don't have that many cores, so if I started to say +1 when I'm not sure, we would stall :)16:14
krotscheckjeblair: If it becomes a thing I’ll let you know :)16:14
krotscheckYeah, that too.16:14
fungiyeah, i've so far tried to only +2 storyboard changes i feel like i understand the ramifications of16:14
ttxthat said once we have a solid team, I'm happy to un-core myself and become a very opinionated stakeholder16:14
*** bpokorny has joined #openstack-meeting-316:15
ttxsince I can't seem to get enough time to become angular-fluent16:15
krotscheckttx: Well, I think at that point we’ll be able to ACL prioritization on storyboard, meaning you can go make changes there :)16:15
krotscheckOk, so what I’ve got so far:16:16
krotscheck- Demonstration that the individual understands the codebase well enough to identify problems.16:16
krotscheck- Demonstration that the individual understands and contributes to the roadmap.16:16
krotscheck- Demonstration of engagement16:17
krotscheck- Demonstration that the person knows their limits.16:17
krotscheckThese all feel quite fluffy to me.16:17
krotschecka little subjective, but I do like them.16:17
jedimikeit is subjective though16:17
SergeyLukjanovsounds fair16:18
yolandayes, these are subjective criteria but if it's a shared opinion it can become more valid16:18
NikitaKonovalovsounds fair for me as well16:18
jeblairkrotscheck: i have semi-objective ways of evaluating those that i'm happy to share (but this may not be the best time)16:18
jeblairbut yeah, the subjectiveness is a feature :)16:18
SergeyLukjanovbtw there is a nova core team page - https://wiki.openstack.org/wiki/Nova/CoreTeam with some formal workds16:19
krotscheckBah. Why can’t humans be binary.16:19
*** nfedotov has quit IRC16:19
jedimikeyolanda, that's why cores are voted in :)16:19
SergeyLukjanovkrotscheck, ternary can16:19
*** pballand has joined #openstack-meeting-316:19
krotscheckSergeyLukjanov: Thanks for that :)16:19
krotscheckI don’t see any disagreement on those four, and it seems like a good starting point.16:19
krotscheckSo de/elevation of cores then can be a consensus thing, since everything in openstack is consensus.16:20
krotscheckConsensus among cores?16:21
krotscheckStoryboard cores + infra cores?16:21
krotscheckStoryboard cores + infra PTL?16:21
krotscheckAll the cores in openstack?16:21
SergeyLukjanovIMO infra cores + sb cores works ok16:22
NikitaKonovalovkrotscheck: as StoryBoard is part of an Infra programe Infra cores should vote16:22
SergeyLukjanovfor me, for example, I'm not able to contribute something to code directly, but I'm able to verify and review at list server (and then python client) side16:22
krotscheckI disagree on that. I haven’t seen any infra cores actively contribute to the codebase, though they’ve been useful to get reviews when people go on vacation.16:23
*** Longgeek has quit IRC16:23
krotscheckTo me, infra core feels more like an advisory panel of experts than people who meet the four storyboard core criteria.16:24
krotscheckjeblair: Opinions?16:25
jeblairkrotscheck: what are you disagreeing with?16:25
yolandawell, i think the most people having an opinion, the better should be. Allowing everyone to vote cannot be bad16:25
yolandaeveryone that knows the project and have a relevant opinion16:25
krotscheckjeblair: I disagree with SergeyLukjanov and NikitaKonovalov’s desire to make elevation of cores a SB Core + All Infra Core consensus.16:25
krotscheckI personally prefer SB Core + PTL.16:26
krotscheckAlso, because I have vested interest in having Mirantis dedicate more of NikitaKonovalov’s time to the project :)16:27
NikitaKonovalovkrotscheck: if an Infra core member does not have an opinion, they should not be forced to vote16:27
jeblairkrotscheck: i think infra-core has quite a bit to contribute here.  just as people contribute differently to different kinds of reviews and changes, there's an opportunity to involve infra-core, but not in a way that oversteps bounds.16:27
krotscheckSo it sounds to me like it’s more of a straight vote than  consensus?16:28
jeblairkrotscheck: i'd prefer the consensus process for core to be inclusive, but i suspect that people in infra-core who are not equipped to evaluate a member will not obstruct the process16:28
*** bpokorny has quit IRC16:28
jeblairkrotscheck: here's the general process:16:28
*** armax has joined #openstack-meeting-316:29
jeblairkrotscheck: nomination to list; invitation to +1 or -1, stays open for a week.  people chime in with opinions, after a week if no significant opposition is observed, it happens16:29
jeblairkrotscheck: so it's not really a formal vote16:29
jeblairkrotscheck: it's more of, who's the group from which you are willing to consider objections16:30
SergeyLukjanovyup, and -1 is veto16:30
*** carl_baldwin has quit IRC16:30
jeblairthat pretty much never happens by the time we actually get to the proposal stage16:30
jeblaireveryone wants more cores, and we try not to propose people who aren't ready (handling a rejection like that could be awkward)16:31
krotscheckOk, so how does that work for de-elevation?16:31
krotscheckIt all sounds good to me :)16:32
yolandacool, sounds fair to me16:32
*** rcleere_away is now known as rcleere16:32
jedimike+1 from me16:32
jeblairusually the ptl makes the decision and announces a de-elevation16:32
jeblairgenerally that only happens because someone has stopped reviewing code16:33
*** emagana has quit IRC16:33
jeblairand it's usually apparent to everyone that it's time16:33
jeblairbut nonetheless, we don't ask people to publicly "+1" removing someone from core16:33
jeblairbecause again, that could be awkward16:33
*** emagana has joined #openstack-meeting-316:33
jeblairi think there may be some morke text about this on the wiki somewhere16:34
krotscheckRighto.16:35
*** mrmartin has quit IRC16:35
krotscheckOk, so let’s stay with Infra + SB cores for now and see how that works out for us.16:35
*** bpokorny has joined #openstack-meeting-316:35
*** mrmartin has joined #openstack-meeting-316:35
jeblairoh yeah, it's in that nova core team page16:35
jeblair2nd par of 'adding or removing members'16:35
krotscheckyolanda: As far as I’m concerned, you have my +1, but you’ll have to go talk to others :)16:36
krotschecknext topic?16:36
krotscheck#agreed Core elevation to be “consensus” of Infra + Storyboard Cores.16:37
krotscheck#topic Story Types.16:37
*** openstack changes topic to "Story Types. (Meeting topic: StoryBoard)"16:37
yolandahow is the proposal to the mailing list sent? who needs to send that? the interested in being core?16:37
krotscheckoops16:37
krotscheck#topic Discussion: Core Reviewres16:37
*** openstack changes topic to "Discussion: Core Reviewres (Meeting topic: StoryBoard)"16:37
*** emagana has quit IRC16:37
yolandasorry, typed too slow16:37
krotscheckI’d say, pick whatever communication medium you prefer (IRC, Email, etc)16:38
krotscheckAnd at the very least get existing SB Cores on board.16:38
jeblairyolanda: actually...16:38
krotscheckAnd then talk to jeblair16:38
*** lhcheng has left #openstack-meeting-316:38
jeblairyolanda: by convention the proposal usually comes from the ptl; i think in this case we could say it's okay for a proposal to come from a storyboard core though, yeah?16:39
jeblairbut i don't think we should ask people who want to be core to publicly propose themselves.  i think it's better for the core team to make the invitation16:40
krotscheckI agree16:40
jeblairbut people interested in being core should definitely talk to those on the core team to help get them ready16:40
*** baojg_ has quit IRC16:40
krotscheckThat too.16:40
jeblairyolanda: so you're definitely doing the right thing here :)16:40
krotscheckPersonally, what I love about yolanda’s reviews is that she’s EXTREMELY cautions about things.16:41
*** baojg has joined #openstack-meeting-316:41
ttxindeed!16:41
krotscheckShe’s more or less the opposite of me.16:41
krotscheck:D16:41
*** emagana has joined #openstack-meeting-316:41
*** david-lyle_afk is now known as david-lyle16:41
yolandaheh, that can be good and bad :)16:42
* krotscheck has also been noticing wendar doing a lot of reviews for us.16:42
jeblairyay!16:42
*** Piet has joined #openstack-meeting-316:42
krotscheckyolanda: So did that answer your question?16:42
yolandayes, sure16:42
krotscheckAwesome.16:43
krotscheck#topic Discussion: Story Types16:43
*** openstack changes topic to "Discussion: Story Types (Meeting topic: StoryBoard)"16:43
* krotscheck has not reviewed that spec.16:43
* krotscheck goes to sit in a corner.16:43
ttxI won't write another spec until that one is reviewed :)16:44
* ttx can't only handle one spec at a time :)16:44
ttxAlso nothing like a good excuse for not doing it16:44
* krotscheck thinks that ttx’s reaction is the right one.16:44
krotscheckCan we get everyone to reviewing https://review.openstack.org/#/c/129267/ this week?16:45
jedimikewhat's the link to the spec? I can't see it linked from the wiki16:45
krotscheckjedimike: ^^16:45
*** pkoniszewski has quit IRC16:45
jedimikeaha :)16:45
* krotscheck is updating the wiki16:45
*** baojg has quit IRC16:46
*** stanzgy has joined #openstack-meeting-316:46
jeblairi think this looks like a good one for the broader infra audience to see...16:46
jeblairi can highlight it in the infra meeting if you like16:46
krotscheckjeblair: That’d be awesome.16:47
krotscheck#action krotscheck review https://review.openstack.org/#/c/129267/16:47
krotscheck(Others can add their own actions)16:47
krotscheckOk, moving on:16:47
krotscheck#topic Discussion: Documentation16:47
*** openstack changes topic to "Discussion: Documentation (Meeting topic: StoryBoard)"16:47
*** alexpilotti has joined #openstack-meeting-316:47
krotscheckpersia: You here?16:47
krotscheckHrm. Ok, so it’s been 3 weeks with noshows from him. I’ll ping him directly.16:48
*** jacalcat has joined #openstack-meeting-316:48
krotscheck#topic Product Evangelism16:49
*** openstack changes topic to "Product Evangelism (Meeting topic: StoryBoard)"16:49
krotscheckDitto on rainya16:49
krotscheck#action krotscheck contact rainya and persia about the items they agreed to at the summit.16:49
krotscheck#topic MVP 1.216:49
*** openstack changes topic to "MVP 1.2 (Meeting topic: StoryBoard)"16:49
*** etoews has joined #openstack-meeting-316:50
NikitaKonovalovI've started the python client task16:50
krotscheckYay!16:50
krotscheckNikitaKonovalov: You saw the user token issue api that I built, yes?16:50
NikitaKonovalovAs soon as the repo and all infra around is ready16:50
NikitaKonovalovkrotscheck: I've seen that16:50
NikitaKonovalovand it will be very usefull16:51
krotscheckIs that an acceptable way of having the python client authenticate, or do you want something more sophisticated?16:51
SergeyLukjanovI've created client on pypi and CR for adding new repo is near to be finished16:51
* krotscheck is thinking of allowing OAuth password flow in addition to launchpad.16:51
krotscheck#topic MVP 1.2: Client Library16:52
*** openstack changes topic to "MVP 1.2: Client Library (Meeting topic: StoryBoard)"16:52
NikitaKonovalovI had an idea of a client making a request to a public endpoint, which will then result in a question to a user "Allow this client to authenticate or not"16:52
SergeyLukjanovprobably use the same approach of approving tokens in Web UI like launchpad?16:52
SergeyLukjanovit's the same as NikitaKonovalov said16:52
NikitaKonovalovI think I'll describe the full flow in a spec16:52
krotscheckGood idea.16:52
krotscheckThat feels more like traditional OAuth flow, good thinking.16:52
NikitaKonovalovbut for now I'll make it work with a provided token16:53
SergeyLukjanovkrotscheck, +116:53
NikitaKonovalovboth as a python module and CLI16:53
krotscheckCool.16:53
krotscheckDoes openstack have a standard for how to structure the CLI arguments?16:53
jeblair++spec.  fwiw, that approach is great for real users and really hard to use with non-interactive accounts16:53
SergeyLukjanovjeblair, provided token for non-interactive?16:54
jeblairer, are we sure we want to conflate the cli and python api client?16:54
NikitaKonovalovbtw, oslo apiclient appeared to be pretty handy16:54
jeblairi think that has worked out very poorly for openstack16:54
NikitaKonovalovjeblair: openstack clients usually do16:54
SergeyLukjanovjeblair, I think for us it'll not be an issue mix them in one repo16:54
jeblairwhich is why currently the python-*clients are heading in the direction of being internal api only, the "sdk" project is heading toward being a python api client, and the 'openstackclient' project is aiming for a command line client16:55
NikitaKonovalovI think CLI is low priority for SB16:55
NikitaKonovalovso there is time to figure out16:56
jeblairNikitaKonovalov: agreed; i think the api client is much more important16:56
jeblair(at the moment)16:56
ttxmost cli users would be apiclient users anyway16:56
jeblairSergeyLukjanov: [going back a bit] yeah, a way to have a provided token for non-interactive is better (something we can put in hiera for puppet, etc)16:57
*** otherwiseguy has quit IRC16:57
SergeyLukjanovjeblair, yup16:57
krotscheckI think we’re all on the same page.16:57
krotscheckAnd we’re getting low on time.16:57
krotscheckMost of my work has been on fixing annoying UI things.16:58
krotscheckLike inline editing of tasks.16:59
krotscheckSo not really roadmap things, so I don’t have anything to contribute here.16:59
krotscheckWell, that’s a lie. The reason I fixed that is because I was trying to get the 1.2 things into storyboard and the UI made my eyes blee.d16:59
krotscheckAnyway: Anything else?16:59
*** ttrifonov is now known as zz_ttrifonov16:59
krotscheckjedimike? yolanda?16:59
krotscheckYou’ve got less than a minute :)16:59
krotscheck(sorry)17:00
jedimikedid we come to a solution with results paging?17:00
jedimike(sorry for the highly controversial thread ;)17:00
krotscheckjedimike: Ugh. No. I don’t think we have the time to discuss that in the meeting though, bounce over to channel?17:00
jedimikecool17:00
krotscheckAlright, thanks everyone!17:00
krotscheck#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Mon Nov 24 17:00:52 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/storyboard/2014/storyboard.2014-11-24-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/storyboard/2014/storyboard.2014-11-24-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/storyboard/2014/storyboard.2014-11-24-16.00.log.html17:00
*** sarob has joined #openstack-meeting-317:01
*** yolanda has left #openstack-meeting-317:02
*** MaxV has quit IRC17:02
*** jacalcat has left #openstack-meeting-317:02
*** carl_baldwin has joined #openstack-meeting-317:03
Pietjaromir, are you running the UX meeting?17:03
*** etoews has quit IRC17:03
*** jedimike has left #openstack-meeting-317:04
*** MaxV has joined #openstack-meeting-317:05
*** etoews has joined #openstack-meeting-317:06
Piet#startmeeting UX17:09
openstackMeeting started Mon Nov 24 17:09:12 2014 UTC and is due to finish in 60 minutes.  The chair is Piet. Information about MeetBot at http://wiki.debian.org/MeetBot.17:09
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:09
*** openstack changes topic to " (Meeting topic: UX)"17:09
openstackThe meeting name has been set to 'ux'17:09
PietIf no one objects, I'll go ahead and get the UX meeting started17:09
david-lyleo/17:11
PietHas everyone had an opportunity to join Invision to help review mocks?  If not, feel free to reach-out to Ju, Liz, Jaromir or myself to get an invitation.17:11
david-lyleseen a lot of reviews, so I think most people are in17:14
*** tsufiev has joined #openstack-meeting-317:14
*** emagana has quit IRC17:15
*** shwetaap has quit IRC17:15
*** emagana has joined #openstack-meeting-317:15
*** shwetaap has joined #openstack-meeting-317:16
PietI want to reinforce that this tool is not just for designers, but for anyone doing working on Horizon including development, design or documentation.  You can also post your own projects if you want them reviewed.17:16
PietAlso, wanted the group to know that we are running a usability study on the launch instance workflow.17:18
*** hinnant_ has joined #openstack-meeting-317:19
PietThis will be a remote/unmoderated study using usertesting.com so you will not be able to watch in real time.  However, the videos from the study will be made available to the community.17:19
*** emagana has quit IRC17:20
*** alexpilotti has quit IRC17:20
*** safchain has quit IRC17:21
PietLet's take a roll call and see if anyone is listening.17:22
david-lyleo/17:22
david-lyle\o17:22
david-lyle\o/17:23
david-lyleseems a bit sparse17:23
david-lylelet's call this one and send an email to openstack-dev before the next one. I think we broke cadence along the way and this has fallen off people's radar17:24
david-lylealso update the agenda on https://wiki.openstack.org/wiki/Meetings/UX17:24
david-lyleotherwise the meeting seems like it's been abandoned17:25
*** ivar-lazzaro has joined #openstack-meeting-317:25
krotscheckohai17:25
krotscheckOops, too late.17:26
david-lylekrotscheck: Piet hasn't actually closed the meeting yet17:26
david-lylebut there are now 3 of us17:26
*** ivar-lazzaro has quit IRC17:26
david-lyle:-)17:26
krotscheckWell, three of us where one of us doesn’t really work on Horizon ;)17:27
PietHi Michael17:27
krotscheckAlthough I hear good things about y’all moving to angular :D17:27
*** ivar-lazzaro has joined #openstack-meeting-317:27
david-lyleUX is more than Horizon, even if all it's attention seems to go there17:27
krotscheckPoint17:27
david-lylekrotscheck: yeah, we're starting to make some progress17:27
PietOne other thing - I have a pre-test for a card sort activity that needs ten participants.  It would be awesome if some of you folks could complete it.17:28
krotscheckSure! Is this an online thing?17:28
Pietyeah17:28
Piethttps://i2471lxv.optimalworkshop.com/optimalsort/002h4457-017:28
PietI'm getting a lot of drop-offs and wondering why17:29
*** matrohon has quit IRC17:29
* krotscheck goes to do that.17:30
david-lyledo you want grammar feedback17:31
david-lyle?17:31
PietYeah, grammar feedback is good17:31
david-lylequestion two, "you company"17:32
PietAlso, want to make sure the definitions for the panels are accurate.17:32
david-lylequestion four "the the description"17:32
Pietk17:32
david-lyleplus tense and other things on 417:32
Pietk17:33
PietKind of relief its a pre-study17:33
david-lylelast question end with period on 1st page17:34
PietNote that I can't make changes to the pre-study because it's active, but will update for final one17:35
krotscheckMemo to self. Never accidentally hit the back button17:35
*** dboik has quit IRC17:35
PietDoes that clear the results?17:37
*** emagana has joined #openstack-meeting-317:38
krotscheckYep.17:38
krotscheckWell, the work that I did is gone.17:38
krotscheckAlso, I kindof feel like some of these have tasks for Ops people and task for users.17:38
PietWow - that's fun! (in a sarcastic tone)17:38
krotscheckLike, a distinction between cloud ops and customer ops.17:38
david-lylewhere are the vpn, firewall, sahara, and trove items?17:39
PietWhat do you mean?17:39
*** dboik has joined #openstack-meeting-317:39
david-lylehypervisors, baremetal17:39
david-lylebaremetal, would be nice because we're about to add that in17:39
david-lylewhere should it go17:39
PietDavid - we can add them.  Are they intended for end users or admins?17:39
david-lyleit becomes a contest17:40
Pietk17:40
david-lyleall are end user except hypervisors17:40
PietMichael - any comments?17:40
david-lylecan I add new panels in groups17:40
david-lylealso missing object store17:41
krotscheckNone directly.17:41
*** baojg has joined #openstack-meeting-317:41
david-lyleor containers17:41
PietYou can also leave comments on the Google doc17:41
Piethttps://docs.google.com/document/d/1lk-ohyNRWEpApEVy-jht36V3jMhqMX8gxjU5VBXIOnI/edit?usp=sharing17:41
krotscheckI like how the columns and rows are unlabeled.17:41
*** mwang2 has joined #openstack-meeting-317:42
*** bpokorny_ has joined #openstack-meeting-317:43
*** otherwiseguy has joined #openstack-meeting-317:43
*** mikedillion has joined #openstack-meeting-317:44
PietMichael - In the Card Sort?17:44
david-lylealso missing the "Projects" panel that currently lives in the Identity dashboard17:44
david-lylePiet, so for Sahara "Data Processing" there are 9 panels in that panel group currently17:46
PietDavid, wow17:46
david-lylein the Database panel group, there are 2 panels17:46
*** baojg has quit IRC17:47
*** bpokorny has quit IRC17:47
david-lylenot sure you need people to sort the 9 panels17:47
PietDavid, Let me schedule some time with you to review with Tiff17:47
david-lylemaybe just the high level Data Processing group17:47
*** ycombinator_ has quit IRC17:47
*** shwetaap has quit IRC17:47
david-lyleDatabase is more interesting because it's Instances and Backups for Databases17:48
PietDavid/Michael, glad we go the card sort in front of you before rolling-out to a huge group of people17:48
david-lyleit's plausible that if you split storage into a group that Database Backups would be there17:48
*** mwang2_ has joined #openstack-meeting-317:48
*** shwetaap has joined #openstack-meeting-317:49
david-lylenot sure though17:49
david-lyleI guess that's why we have a study17:49
PietYup17:51
PietI'm going to end the meeting if no one objects17:51
PietAny final things to discuss?17:51
*** mwang2 has quit IRC17:52
Pietok - have an awesome couple of weeks until we meet again!17:52
Piet#endmeeting17:53
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:53
openstackMeeting ended Mon Nov 24 17:53:09 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ux/2014/ux.2014-11-24-17.09.html17:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ux/2014/ux.2014-11-24-17.09.txt17:53
openstackLog:            http://eavesdrop.openstack.org/meetings/ux/2014/ux.2014-11-24-17.09.log.html17:53
david-lyleThanks Piet17:54
*** bpokorny_ has quit IRC17:54
*** mikedillion has quit IRC17:54
*** Piet has quit IRC17:56
*** bpokorny has joined #openstack-meeting-317:57
*** sarob has quit IRC18:01
*** emagana has quit IRC18:01
*** sweston_ is now known as sweston18:02
*** emagana has joined #openstack-meeting-318:02
*** tsufiev has left #openstack-meeting-318:04
*** emagana has quit IRC18:06
*** shwetaap has quit IRC18:22
*** shwetaap has joined #openstack-meeting-318:22
*** MaxV has quit IRC18:27
*** bpokorny_ has joined #openstack-meeting-318:28
*** viscious is now known as vishy18:29
*** shwetaap has quit IRC18:30
*** shwetaap1 has joined #openstack-meeting-318:30
*** SridharRamaswamy has joined #openstack-meeting-318:31
*** bpokorny has quit IRC18:31
*** markmcclain has joined #openstack-meeting-318:40
*** etoews has quit IRC18:43
*** emagana has joined #openstack-meeting-318:43
*** bpokorny has joined #openstack-meeting-318:46
*** shwetaap1 has quit IRC18:47
*** otherwiseguy has quit IRC18:47
*** shwetaap has joined #openstack-meeting-318:47
*** bpokorny_ has quit IRC18:49
*** etoews has joined #openstack-meeting-318:49
*** marun has joined #openstack-meeting-318:53
*** naohirot has joined #openstack-meeting-318:53
*** flwang has quit IRC18:58
*** garyduan has quit IRC19:03
*** emagana has quit IRC19:03
*** emagana_ has joined #openstack-meeting-319:06
*** emagana_ has quit IRC19:09
*** emagana has joined #openstack-meeting-319:09
*** flwang has joined #openstack-meeting-319:11
*** shwetaap has quit IRC19:12
*** shwetaap has joined #openstack-meeting-319:12
*** s3wong has joined #openstack-meeting-319:13
*** sarob has joined #openstack-meeting-319:14
*** shwetaap has quit IRC19:15
*** shwetaap has joined #openstack-meeting-319:15
*** jcoufal_ has quit IRC19:15
*** alexpilotti has joined #openstack-meeting-319:15
*** MaxV has joined #openstack-meeting-319:16
*** shwetaap has quit IRC19:17
*** shwetaap has joined #openstack-meeting-319:18
*** stanzgy has quit IRC19:24
*** garyduan has joined #openstack-meeting-319:26
*** alexpilotti has quit IRC19:27
*** alexpilotti has joined #openstack-meeting-319:27
*** baojg has joined #openstack-meeting-319:30
*** markmcclain has quit IRC19:31
*** markmcclain has joined #openstack-meeting-319:31
*** matrohon has joined #openstack-meeting-319:32
*** MarkAtwood has joined #openstack-meeting-319:33
*** baojg has quit IRC19:35
*** SumitNaiksatam has quit IRC19:40
*** garyduan has quit IRC19:40
*** emagana has quit IRC19:40
*** SumitNaiksatam has joined #openstack-meeting-319:40
*** SridharRamaswamy has quit IRC19:41
*** garyduan has joined #openstack-meeting-319:41
*** emagana has joined #openstack-meeting-319:41
*** jacalcat has joined #openstack-meeting-319:44
*** emagana has quit IRC19:45
*** zz_ttrifonov is now known as ttrifonov19:47
*** mrmartin has quit IRC19:47
*** SridharRamaswamy has joined #openstack-meeting-319:47
*** mrunge has joined #openstack-meeting-319:49
*** otherwiseguy has joined #openstack-meeting-319:50
*** jacalcat has left #openstack-meeting-319:51
*** matrohon has quit IRC19:55
*** ycombinator_ has joined #openstack-meeting-319:57
*** hinnant_ has quit IRC19:58
*** sarob has quit IRC19:59
*** MaxV has quit IRC19:59
*** sarob has joined #openstack-meeting-320:00
*** banix has quit IRC20:07
*** MaxV has joined #openstack-meeting-320:07
*** SridharRamaswamy has quit IRC20:11
*** ycombinator_ has quit IRC20:15
*** sarob has quit IRC20:17
*** etoews_ has joined #openstack-meeting-320:18
*** ilyashakhat has quit IRC20:21
*** banix has joined #openstack-meeting-320:21
*** etoews has quit IRC20:22
*** ilyashakhat has joined #openstack-meeting-320:22
*** shwetaap has quit IRC20:23
*** otherwiseguy has quit IRC20:23
*** otherwiseguy has joined #openstack-meeting-320:24
*** baoli has quit IRC20:24
*** alexpilotti has quit IRC20:24
*** emagana has joined #openstack-meeting-320:25
*** matrohon has joined #openstack-meeting-320:27
*** SridharRamaswamy has joined #openstack-meeting-320:29
*** johnbelamaric has joined #openstack-meeting-320:29
*** bobmel_ has joined #openstack-meeting-320:38
*** johnbelamaric has left #openstack-meeting-320:40
*** bpokorny_ has joined #openstack-meeting-320:44
*** bobmel_ has quit IRC20:45
*** baoli has joined #openstack-meeting-320:45
*** SridharRamaswamy has quit IRC20:46
*** bpokorny has quit IRC20:46
*** baoli has quit IRC20:46
*** baoli has joined #openstack-meeting-320:47
*** flwang has quit IRC20:49
*** marun_ has joined #openstack-meeting-320:54
*** flwang1 has joined #openstack-meeting-320:58
flaper87flwang1: vkmc kragniz zhiyan around ?20:59
vkmcsure thing20:59
flwang1o/20:59
vkmco/20:59
*** bobmel_ has joined #openstack-meeting-320:59
flaper87#startmeeting Zaqar21:00
openstackMeeting started Mon Nov 24 21:00:00 2014 UTC and is due to finish in 60 minutes.  The chair is flaper87. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: Zaqar)"21:00
openstackThe meeting name has been set to 'zaqar'21:00
flaper87#topic Roll Call21:00
*** openstack changes topic to "Roll Call (Meeting topic: Zaqar)"21:00
vkmco/21:00
flaper87o/21:00
flwang1o/21:00
*** amotoki has joined #openstack-meeting-321:00
flaper87I guess kgriffs will show up later21:00
*** MaxV has quit IRC21:00
flaper87lets move on21:00
flaper87#topic Finalize specs review21:01
*** openstack changes topic to "Finalize specs review (Meeting topic: Zaqar)"21:01
flaper87#topic Previous meeting actions21:01
*** openstack changes topic to "Previous meeting actions (Meeting topic: Zaqar)"21:01
flaper87actually21:01
flaper87#undo21:01
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x184a050>21:01
flaper87#undo21:01
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x184a1d0>21:01
flaper87#topic Previous meeting actions21:01
*** openstack changes topic to "Previous meeting actions (Meeting topic: Zaqar)"21:01
flaper87:P21:01
* flaper87 is perfectionist21:01
flaper87vkmc to add cpallares as a secondary contact21:01
flaper87vkmc: ^21:01
vkmcdone https://review.openstack.org/#/c/134567/21:01
flaper87#info cpallares has been added as a second contact to https://review.openstack.org/#/c/134567/21:02
flaper87vkmc to evaluate serialization protocols for the websocket transport21:02
flaper87vkmc: ^21:02
vkmcdone https://etherpad.openstack.org/p/zaqar-serialization-protocol-ws21:02
flaper87#info Serialization protocols evaluated here: https://etherpad.openstack.org/p/zaqar-serialization-protocol-ws21:03
flaper87vkmc: AFAIR, msgpack won21:03
vkmc#info spoiler alert: msgpack wins21:03
flaper87right?21:03
vkmcright21:03
flaper87#info msgpack will be used as the serialization protocol21:03
flaper87flaper87 to clarify how notifications will be pushed to clients21:03
* flaper87 can't remember21:04
flaper87AFAIK, that's done21:04
vkmcask flaper8721:04
* flaper87 asks flwang121:04
flaper87erm21:04
* flaper87 asks flaper8721:04
flwang1lol21:04
flaper87ah yeah, that was the workers thingy21:04
flaper87it's done21:04
flwang1taskflow, IIRC?21:04
flaper87#info Workers specification added to the spec https://review.openstack.org/#/c/129192/21:05
flaper87flwang1: yeah21:05
flaper87ok, we did everything21:05
vkmc\o/21:05
flaper87#topic Finalize specs review21:05
*** openstack changes topic to "Finalize specs review (Meeting topic: Zaqar)"21:05
flaper87#link https://review.openstack.org/#/c/129192/21:05
flaper87flwang1: that's notifications21:05
flaper87AFAIK, you already started working on it21:05
flaper87vkmc: could you take a final look?21:05
flwang1flaper87: yep21:05
flaper87flwang1: already +1'd it21:05
vkmcflaper87, of course21:06
*** beagles has left #openstack-meeting-321:06
*** marun_ has quit IRC21:06
*** beagles has joined #openstack-meeting-321:06
flaper87kgriffs hasn't gotten back to it but we need to move it forward21:06
flaper87we can edit it later if really needed21:06
*** beagles has left #openstack-meeting-321:06
*** marun_ has joined #openstack-meeting-321:06
flwang1flaper87: agree21:07
vkmc+1 flaper8721:07
flaper87vkmc: awesome21:07
flwang1flaper87: for some details, we can improve them during code review21:07
flaper87vkmc: I don't see your +121:07
flwang1for the overall design, it looks good for me21:07
flaper87flwang1: agreed21:08
vkmcflaper87, I'll read it carefully after the meeting21:08
flaper87vkmc: ah lol21:08
flaper87now I understood your +1 thing21:08
flaper87hahaha, it was about my last message21:08
* flaper87 slaps himself21:08
flaper87ok, moving on21:08
flaper87#link https://review.openstack.org/#/c/134567/21:08
vkmcyeah :) haha21:08
flaper87vkmc: that's persistent transports21:08
vkmcI see that21:08
vkmcok so... kgriffs made a good point there21:09
flaper87I'm 80% against socketio, socketjs and adabahnanadshdasawhatever21:09
vkmcwe didn't clarify what we are going to do in case there is no support for websockets21:09
flaper87The reasons are expressed there21:09
vkmcgreat, its good to count on your experience to make this decision21:09
flaper87There were some good reasons to block websocket when it first came out21:10
flaper87I'd like to understand what are nowadays motivations to do so21:10
vkmcso.. the other options are tornado and ws4p21:10
vkmcy21:10
flaper87ws4p is just websocket21:10
flaper87it doesn't have support for long-polling21:10
vkmcbeyond that, there are browsers that doesn't support it21:10
flaper87very old browsers you mean, right?21:10
flaper87http://caniuse.com/websockets21:11
*** matrohon has quit IRC21:11
flaper87even IE has support for it21:11
vkmchere is a list21:11
*** kgriffs has joined #openstack-meeting-321:11
vkmchttp://tavendo.com/blog/post/websocket-why-what-can-i-use-it/21:11
vkmcof where it works21:11
* kgriffs joins21:11
flwang1what's IE?21:12
*** sarob has joined #openstack-meeting-321:12
vkmcbetter... this is the source http://caniuse.com/#search=websockets21:12
vkmcyeah please flaper87, clear that up21:12
vkmcwhat does IE stands for?21:12
flaper87IE = Internet Explorer21:12
flwang1i'm kidding21:12
vkmcstill no clue21:12
flaper87LOL21:12
flaper87:D21:12
vkmc:D21:12
flaper87kgriffs: discussing persistent transports spec21:12
flaper87What I'd like to understand is why would an OPs guy block websocket nowadays21:13
flaper87there were some good reasons in the past21:13
flaper87but I don't think those are valid anymore21:13
flaper87I'm curious to know if there are new good reasons21:13
flaper87the good thing aboud long-polling is that it plays well with LB21:14
flaper87but again, the whole fallback thing doesn't work as it says it does21:14
kgriffssome thoughts on blocking websocket21:14
kgriffsfirst, is some firewalls and stuff are configured to kill http connections after a certain amount of time21:15
kragnizo/21:15
*** marun_ has quit IRC21:15
* kragniz lurks some21:15
kgriffsthere is a real cost to persistent connections on networking gear, although that cost is going down, still significant21:15
kgriffsso, i have that first-hand from talking with ops people21:16
flaper87kgriffs: ok, that's a good reason21:16
kgriffsthe second one is more speculation21:16
kgriffssome people may be paranoid from a security standpoint and they will kill any traffic over port 80 or 443 that doesn't look like HTTP21:16
flaper87kgriffs: right but deplying Zaqar + websocket is a manual process21:17
*** SridharRamaswam1 has joined #openstack-meeting-321:17
flaper87which means OPs know they'll need it to be enabled in the firewall21:17
kgriffsyes, but that is only one side21:18
flaper87and they'll have to support long-living connections21:18
kgriffswhat I mean is that you can have one org or company talking to another org or company and you have to have both parties agree to let this traffic through21:19
flaper87yup21:19
kgriffsnowdays I expect it to work most of the time, but sometimes it won't.21:19
flaper87yeah, that's true21:19
vkmcthat makes sense, but if they are deploying a messaging service like Zaqar I guess that is something they have to consider21:20
flwang1kgriffs: +121:20
flaper87I don't have counter-arguments to that21:20
*** vishwana_ has joined #openstack-meeting-321:20
flaper87I honestly see the long-poling transport as a separate one21:20
flaper87once we have the websocket one setup, it should be fairly simple21:20
*** marun_ has joined #openstack-meeting-321:20
*** jpomero has quit IRC21:20
* kgriffs is catching up on the comments on the spec21:21
flaper87I'm concerned that falling back to long-polling if websocket is not enabled won't be as simple as it sounds from a pub-sub stand point21:21
flaper87We'll have to implement the cross-api thingy before finilizing the transport itself21:21
flaper87is this something we can revisit later?21:21
kgriffscan we just fall back to short polling for now, and look at adding long-polling support later?21:22
flaper87kgriffs: I mentioned before you joined that I'm 80% against fallback strategies for this specific thing but I'm happy to change my mind if we see it  can be done/maintained easily21:22
kgriffsflaper87: oic21:22
flaper87with that I'm not saying that if I don't change my mind we won't do it21:22
flaper87it's just my personal opinion21:22
flaper87kgriffs: +1 for falling back to short-polling but that's handled by the client21:22
flaper87What I'm not happy with is having 1 transport that supports 2 different protocols21:23
vkmcwe have to make sure we deliver the simplest, fully functional, version of this transport soon21:23
*** marun_ has quit IRC21:23
kgriffsflaper87: oic21:23
kgriffsala socket.io or SockJS21:23
flaper87kgriffs: right21:23
flaper87If the client fallsback to something else, I'm ok with that21:23
kgriffsit's a question of where you want the fallback abstraction to live21:23
vkmcof course, if not having a decent fallback is not acceptable then we have to plan things based on that21:24
flaper87but again, it's a personal opinion a bit based on previous experiences that might not even be valid anymore21:24
*** baoli has quit IRC21:24
kgriffsI looked at socket.io21:24
kgriffsI agree it isn't a great fit for us21:24
kgriffsSockJS is more like what we might want21:24
kgriffsbut, as I said, it doesn't have a non-JS client library, so you have to just use raw websocket and then do your own fallback (to the REST API?) anyway, so it doesn't seem like you gain much from using the library21:25
vkmcsockjs doesn't have the abstraction level socketio has21:25
vkmcsocketio is more like autobahn and wamp21:25
*** marun_ has joined #openstack-meeting-321:25
*** jpomero has joined #openstack-meeting-321:26
flaper87kgriffs: right, at that point I'd rather use w4py which supports asyncio21:26
flaper87and it also has a websocket client for python21:26
flaper87ok, we need to agree on something there21:27
vkmcw4py +121:27
flaper87we can revisit it later if needed21:27
flaper87We need to start on the cross-api thingy anyway21:27
flaper87so, we still have some time for last minute reviews21:27
*** matrohon has joined #openstack-meeting-321:28
flaper87kgriffs: flwang1  ?21:28
flwang1i'm ok21:28
vkmchttps://ws4py.readthedocs.org/en/latest/sources/performance/21:28
flaper87we can contribute back to the library21:29
flaper87and help making it faster, I guess21:29
vkmck21:29
flwang1flaper87: oh, really? are we doing to do that?21:29
flaper87https://github.com/methane/wsaccel21:29
kgriffsif we want to use our persistent transport outside the browser, I think it makes sense to use raw websocket and have the client fallback to short-polling the REST API21:29
flaper87kgriffs: +121:30
flaper87ok, I think we can approve that spec them. Would you guys mind casting your votes there?21:30
kgriffswe should be able to abstract that away in the client, so apps don't care, other than that things go faster when websockets is available21:30
*** asahlin has quit IRC21:30
flaper87I'll approve after the meeting21:30
flaper87kgriffs: agreed21:31
vkmck21:31
*** Sukhdev has joined #openstack-meeting-321:31
kgriffsI just know someone is going to ask about why we didn't use those other things, so be ready with a good reply. :p21:31
*** marun_ has quit IRC21:31
flwang1kgriffs: lol21:31
flaper87Btw, I'm assuming the specs those specs depend on are ok and I'll also approve them21:31
flaper87I'm trying to take the most out of the time we have21:32
flaper87kgriffs: yeah, I'm sure they will21:32
flaper87vkmc: would you mind sumirizing this convo in a wiki page?21:32
flaper87Websocket FAQ ?21:32
flaper87or in the FAQ itself21:32
vkmcflaper87, of course21:32
flaper87vkmc: awesome21:32
vkmcI'll start that ASAP so we can start with the implementation as well21:32
flaper87#action vkmc to write a small FAQ of why we chose raw websocket over socketio sockjs21:32
flaper87thanks a lot, girl!21:33
flaper87Moving on21:33
vkmcnp21:33
flaper87#link https://review.openstack.org/#/c/125986/21:33
flaper87That's FIFO21:33
flaper87kgriffs: I addressed your last comment21:33
kgriffsquestion21:33
kgriffsactually. nevermind21:33
flaper87LOL21:33
flaper87:D21:33
flaper87don't be shy21:33
flaper87flwang1: I also need your review on that spec21:34
flaper87is there something you guys want to discuss about that spec?21:34
flwang1flaper87: done21:34
flwang1flaper87: I think most of the stuff about that have been touched on summit design session21:34
flaper87flwang1: right21:35
kgriffsflaper87: so, looking at the work items...21:35
kgriffsFirst comment is just to keep in mind that capabilities may include whether or not claiming and deleting are supported (for Symantec's use case)?21:36
kgriffsmeaning, there are capabilities that have to do with guarantees and also that have to do with supported features21:36
kgriffss/features/operations21:37
flaper87kgriffs: right21:37
flaper87do we want to separate them ?21:37
flaper87This is a draft of the storage capabilities thing: https://review.openstack.org/#/c/135637/21:37
kgriffsflaper87: no, just that capabilities should be flexible enough to describe all kinds of things21:38
flaper87#link https://review.openstack.org/#/c/135637/21:38
flaper87kgriffs: yeah, although they are implementation specific21:38
flaper87as in, the capabilities of the redis driver are hard-coded21:38
flaper87I haven't worked on a way to make that dynamic yet21:38
kgriffsok, so that was my next question21:39
kgriffsthe last work item on the spec is: "Add a way to pass capabilities down to the driver"21:39
flaper87but as the first step, I thought that's fair21:39
*** mwang2_ has quit IRC21:39
kgriffsare you saying that some drivers can be configurable as far as capabilities?21:40
flaper87kgriffs: I think that's not worded correctly. What I mean there is that we should pass flavor's capabilities down to the driver level so that the right implementation can be loaded21:40
flaper87I'll clarify21:40
flaper87For example21:40
*** pballand has quit IRC21:41
flaper87The capabilities of a flavor will be the interesection of the capabilities of all the nodes in the pool21:41
flaper87Which means, we need to load the storage based on that21:41
flaper87Load can mean multiple things here21:41
flaper87Either importing the right implementation or just enabling/disabling things21:42
flaper87this really depends on the driver21:42
*** sergef has quit IRC21:42
kgriffslet me play devil's advocate and ask why allow a flavor to be made up of heterogeneous nodes in the first place?21:43
flaper87does that make sense?21:43
*** marun_ has joined #openstack-meeting-321:43
flaper87kgriffs: that's a good question21:43
flaper87kgriffs: the first thing that comes to my mind is that it'd be easier to allow that than forbidding it.21:43
flaper87kgriffs: it gives more flexibility to OPs21:43
flaper87and we'd have to pass the flavor down to the storage anyway21:44
flaper87also21:44
flaper87Say I have a storage that doesn't have support for FIFO and one that does21:45
flaper87but I don't care about FIFO21:45
flaper87forbidding me to put them together wouldn't be nice21:45
flaper87But I'm just making this up without any empirical research21:45
kgriffshmmm21:45
kgriffsok, so suppose I have those two drivers21:46
kgriffsand I want to use both in the same flavor21:46
*** ttrifonov is now known as zz_ttrifonov21:47
kgriffsidk why I would do that in the first place, because they would have different characteristics - one might be slower, for example21:47
flaper87right21:47
flaper87so, lets do this21:47
kgriffsnow my users have different emergent behavior depending on which node they end up for a given flavor21:47
flaper87I would hate us to overengineer things so, lets just forbid it for now and enable it in the future21:47
flaper87if people think it makes sense21:47
flaper87it'll be easier to enable it in the future than removing it21:48
flaper87does that sound good?21:48
flaper87I'll update the spec if it does21:48
kgriffsyes, just a few more thoughts real quick21:48
flaper87kgriffs: sure21:48
*** emagana has quit IRC21:48
kgriffsif we enforce that a flavor is made up of nodes that basically use the same drivers with the same configuration/capabilities settings21:49
*** emagana has joined #openstack-meeting-321:49
*** SridharRamaswam2 has joined #openstack-meeting-321:49
kgriffsthen you don't have to try and figure out the least-common denominator of capabilities21:50
flaper87right, that wouldn't be needed anymore21:50
kgriffsi just think it will actually be easier for ops to reason about the system by forcing homogenous pools21:50
flaper87kgriffs: +2, I'm now convinced of that21:50
kgriffslike you say, we can allow it later if people ask for it21:50
flaper87+221:50
kgriffsflaper87: so what is the workflow?21:51
kgriffsSusan the operator creates a flavor21:51
flaper87Susan creates a pool21:51
flaper87Then Susan creates a flavor21:51
flaper87Then the user Pippo creates a queue that uses that flavor21:51
flaper87Pippo posts messages21:51
*** SridharRamaswam1 has quit IRC21:52
flaper87Internally, when the queue creation happens, a new queue is registered in the catalog21:52
*** SumitNaiksatam has quit IRC21:52
* flaper87 reminds everyone we've 8 mins left21:52
*** SumitNaiksatam has joined #openstack-meeting-321:53
kgriffsok, real quick...21:53
*** emagana has quit IRC21:53
flwang1kgriffs: btw, could you please revisit the notification spec at your most convenience?21:53
kgriffsthe thing then to figure out is how to ensure that when adding new nodes to a pool, they all have the same capabilities21:53
flwang1kgriffs: it's a good question21:54
*** emagana has joined #openstack-meeting-321:54
kgriffsif that can be ensured21:54
flaper87kgriffs: that can be ensured when the node is added by introspecting the capabilities21:54
*** SridharRamaswam1 has joined #openstack-meeting-321:54
kgriffsthen it shouldn't be hard to express those capabilities in the flavor21:54
flaper87the driver is loaded based on the configs and node connection uri21:54
kgriffsso the flavor just reports up the capabilities introspected from the lower layer21:54
flaper87it shouldn't be hard to enforce this thing21:55
*** bobmel_ has quit IRC21:55
flaper87kgriffs: right, that's the idea21:55
kgriffskk21:55
flaper87kgriffs: is it ok if I update the spec with your latest comments and approve it?21:55
flaper87or do you have other things you'd like to discuss?21:55
*** MarkAtwood has quit IRC21:55
kgriffsflwang1: I've asked for some feedback from some other Rackspace folks, hopefully people will comment. I will take another look as well if I can steal some time.21:55
*** marun_ has quit IRC21:56
kgriffsflaper87: that's all I had to discuss21:56
flwang1kgriffs: cool, cheers21:56
flaper87flwang1: FWIW, I think I'll go ahead and approve the notifications spec, we can update it if needed21:56
*** SridharRamaswam2 has quit IRC21:56
flaper87I think we all agree on the basis21:56
flwang1i'm ok if kgriffs is ok :)21:56
flaper87that's enough for flwang1 to start working on it21:56
flwang1flaper87: it's true :)21:56
flaper87For the more specific things, we can revisit them21:57
flaper87or even change some things during the review21:57
flaper87ok, 3 mins left21:57
flaper87#topic Open Discussion21:57
*** asahlin has joined #openstack-meeting-321:57
*** asahlin has quit IRC21:57
*** openstack changes topic to "Open Discussion (Meeting topic: Zaqar)"21:57
flaper87anything to share?21:57
vkmcyes... if someone see some technical debt in the code, please report the bug21:58
flaper87vkmc: +221:58
*** asahlin has joined #openstack-meeting-321:58
vkmclately we have been fixing stuff without reporting21:58
vkmcand it makes harder to keep track of changes21:58
flaper87Also, I'm almost done with fixing our functional gate for the client21:58
*** MarkAtwood has joined #openstack-meeting-321:58
flaper87but we should test the client better21:58
vkmcand don't allow new people to get stuff to do21:58
flaper87there are too few bugs21:58
vkmcyeah21:58
flaper87vkmc: +221:58
*** asahlin has quit IRC21:59
flaper87ok, that's it folks21:59
*** asahlin has joined #openstack-meeting-321:59
vkmc:)21:59
flaper87flwang1: kgriffs vkmc thank you all for attending. tty next week!21:59
flwang1flaper87: I can create more bugs in notifications code so that the new comer can get something to work21:59
flaper87who am I kidding? tty in 2 secs21:59
flaper87flwang1: +221:59
vkmchaha21:59
vkmc+2 flwang121:59
flwang1back to zaqar channel21:59
flaper87:P21:59
flaper87#endmeeting21:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:59
openstackMeeting ended Mon Nov 24 21:59:57 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/zaqar/2014/zaqar.2014-11-24-21.00.html22:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/zaqar/2014/zaqar.2014-11-24-21.00.txt22:00
openstackLog:            http://eavesdrop.openstack.org/meetings/zaqar/2014/zaqar.2014-11-24-21.00.log.html22:00
vkmcthanks guys22:00
* vkmc picks the minutes22:00
flaper87vkmc: <322:00
*** jtomasek has quit IRC22:00
vkmcflaper87, (:3 (gummybear)22:01
*** mikedillion has joined #openstack-meeting-322:06
*** emagana has quit IRC22:06
*** emagana has joined #openstack-meeting-322:07
*** emagana has quit IRC22:09
*** emagana has joined #openstack-meeting-322:09
*** jtomasek has joined #openstack-meeting-322:11
*** SumitNaiksatam has quit IRC22:11
*** SumitNaiksatam has joined #openstack-meeting-322:12
*** ycombinator_ has joined #openstack-meeting-322:12
*** mattfarina has quit IRC22:12
*** thomasem has quit IRC22:14
*** mwang2 has joined #openstack-meeting-322:16
*** johnbelamaric1 has joined #openstack-meeting-322:19
*** johnbelamaric has joined #openstack-meeting-322:19
*** gholler has quit IRC22:21
*** mrunge has quit IRC22:22
*** johnbelamaric1 has quit IRC22:23
*** emagana has quit IRC22:23
*** banix has quit IRC22:23
*** mwang2_ has joined #openstack-meeting-322:24
*** emagana has joined #openstack-meeting-322:24
*** emagana has quit IRC22:24
*** jtomasek has quit IRC22:24
*** emagana has joined #openstack-meeting-322:25
*** baoli has joined #openstack-meeting-322:25
*** mwang2 has quit IRC22:25
*** dboik has quit IRC22:28
*** johnbelamaric has quit IRC22:33
*** matrohon has quit IRC22:33
*** peristeri has quit IRC22:38
*** carl_baldwin has quit IRC22:41
*** zhipeng has quit IRC22:45
*** carl_baldwin has joined #openstack-meeting-322:46
*** ChuckC has quit IRC22:47
*** bpokorny has joined #openstack-meeting-322:54
*** shakamunyi_ has joined #openstack-meeting-322:55
*** bpokorny_ has quit IRC22:57
*** banix has joined #openstack-meeting-322:57
*** carl_baldwin has quit IRC22:58
*** ChuckC has joined #openstack-meeting-323:00
*** sarob has quit IRC23:01
*** baojg has joined #openstack-meeting-323:04
*** shakamunyi_ has quit IRC23:04
*** otherwiseguy has quit IRC23:05
*** baojg has quit IRC23:10
*** banix has quit IRC23:11
*** vishwana_ has quit IRC23:14
*** rms_13 has quit IRC23:15
*** emagana has quit IRC23:19
*** jgrimm is now known as zz_jgrimm23:20
*** emagana has joined #openstack-meeting-323:20
*** emagana has quit IRC23:21
*** emagana has joined #openstack-meeting-323:21
*** MaxV has joined #openstack-meeting-323:24
*** Sukhdev has quit IRC23:31
*** bpokorny_ has joined #openstack-meeting-323:33
*** banix has joined #openstack-meeting-323:34
*** bpokorny has quit IRC23:36
*** ycombinator_ has quit IRC23:36
*** bpokorny_ has quit IRC23:37
*** marun has quit IRC23:37
*** MaxV has quit IRC23:39
*** flwang has joined #openstack-meeting-323:39
*** banix has quit IRC23:41
*** kgriffs has left #openstack-meeting-323:42
*** aleksandr_null has quit IRC23:44
*** aleksandr_null has joined #openstack-meeting-323:45
*** armax has quit IRC23:46
*** stanzgy has joined #openstack-meeting-323:49
*** MaxV has joined #openstack-meeting-323:50
*** banix has joined #openstack-meeting-323:54
*** sarob has joined #openstack-meeting-323:58

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