Monday, 2014-06-30

*** openstack has joined #openstack-meeting-313:49
*** ChanServ sets mode: +o openstack13:49
*** jackib has quit IRC13:51
*** jackib has joined #openstack-meeting-314:08
*** otherwiseguy has quit IRC14:10
*** kenhui has quit IRC14:11
*** kenhui has joined #openstack-meeting-314:11
*** jackib has quit IRC14:12
*** MaxV has quit IRC14:27
*** MaxV has joined #openstack-meeting-314:27
*** otherwiseguy has joined #openstack-meeting-314:30
*** otherwiseguy has quit IRC14:34
*** iovadia has quit IRC14:36
*** carl_baldwin has joined #openstack-meeting-314:44
*** yamamoto has quit IRC14:46
*** iovadia has joined #openstack-meeting-314:49
*** jackib has joined #openstack-meeting-314:53
*** salv-orlando has quit IRC14:54
*** NikitaKo_ has joined #openstack-meeting-314:59
ttxo/15:02
krotscheck#startmeeting storyboard15:02
openstackMeeting started Mon Jun 30 15:02:38 2014 UTC and is due to finish in 60 minutes.  The chair is krotscheck. Information about MeetBot at http://wiki.debian.org/MeetBot.15:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:02
*** openstack changes topic to " (Meeting topic: storyboard)"15:02
openstackThe meeting name has been set to 'storyboard'15:02
NikitaKo_o/15:02
ttxo/15:02
krotscheckGood morning, everyone!15:02
* krotscheck failed at updating the agenda in time.15:03
krotscheckSo in the interests of keeping things up to date, I’m going to edit it during the meeting.15:03
krotscheck#topic Specifications15:03
*** openstack changes topic to "Specifications (Meeting topic: storyboard)"15:03
krotscheckttx, you’ve got another comment on tags, anything interesting?15:04
ttxI did a new version of it, just got a review asking for adependency to be added15:05
ttxIf that's the only feedback i'll run a new version with that rolled in15:05
ttxkrotscheck: made progress on your alternate proposal ?15:06
krotscheckttx: I think that’s the only thing. I had some time to consider the alternate proposal last week, and I ran a quick performance test, and it’s pretty much the worst idea in the world.15:06
krotscheckSo I’m going to pass on my alternate proposal.15:06
ttxit's technically attractive, but yeah, i can see how it can quickly get out of control15:06
krotscheckYeah, a single table for all indexes is a bit harsh.15:07
ttxOK, then I'll push a new patchset to address Nikit'as concern15:07
krotscheckAlrightey.15:07
krotscheckNikitaKo_: Did you see my updates to the use cases in search?15:08
NikitaKo_I've seen that15:08
NikitaKo_The spec is more clear about browse vs search now15:08
NikitaKo_and that's great15:08
krotscheckYeah. Which brings us back to the question of ‘is search global or resource-specific’?15:08
*** jpich has joined #openstack-meeting-315:09
krotscheckBecause ultimately, that UI I put together I’d like to eventually pull aside into a ‘Query builder” with which people can design their own dashboards.15:09
krotscheckAnd leave search to be true search, more freeform.15:09
krotscheckAnd that can either be global or resource specific.15:10
NikitaKo_I think it's more natural when one endpoint returns one type of resource15:10
NikitaKo_so I'd prefer to keep them separately15:11
*** sbalukoff has quit IRC15:11
krotscheckNikitaKo_: I agree. ttx?15:11
NikitaKo_The UI however should query all of them by default15:11
ttxkrotscheck: +115:11
krotscheckAlright, that settles it.15:12
ttxI think that UI will shine in advanced searchg15:12
*** nati_ueno has joined #openstack-meeting-315:12
NikitaKo_one more question here is what are those resources?15:12
krotscheckTo be honest, writing up the use cases for search really let me focus in on what the UI should be doing.15:12
NikitaKo_Now we have stories tasks and users15:12
krotscheckNikitaKo_: And projects?15:12
NikitaKo_yep and projects15:12
NikitaKo_do we need search for events or comments?15:13
krotscheckRight. So that’s an interesting question. Let’s say we search for something which is semantically a subresource: Example, comments on a story. Should we be searching stories? Or should we be searching on comments?15:13
krotscheckActually, better question: What should the API do vs. what should the client do?15:14
mordredo/15:14
ttxkrotscheck: I'd say if you search stories, you'd query subresources15:15
krotscheckI feel that the API contract should be consistent across all primary resources. It’s subresources I’m not certain of.15:15
mordredkrotscheck: hrm. excellent question - my old zope background would say "comments are owned by stories, so you should search stories"15:15
ttxbut if you eoecifically search comments, you should not search stories as well ?15:15
ttxspecifically*15:15
mordredkrotscheck: but my non-zope present says "that means I have to know too much about the data model to use the API"15:16
* ttx needs a new keyboard15:16
* jeblair boxes up a model-m for ttx15:16
krotscheck…oh man, those things are indestructible.15:17
krotscheckOk, so any disagreement with all primary resources having the same API contract (barring differences in filter fields)?15:17
ttxjeblair: i could certainly use one :)15:18
*** david-lyle has joined #openstack-meeting-315:18
*** jcoufal has quit IRC15:18
ttxkrotscheck: no15:18
krotscheckI feel that the use case here would be: “I am searching for a thing, and that thing may be in a comment somewhere”. From  a UI perspective I’m going to take the user straight to the story on which that comment is, preferably with an autoscroll to that same comment.15:19
ttxkrotscheck: +115:19
NikitaKo_krotscheck: +!15:19
mordred++15:19
krotscheckRighto.15:20
krotscheckSo given that from a UI perspective, I don’t know what story I’m searching on when I issue the search, I need either one of two things:15:21
krotscheck1- comments as a primary resource that I can search on, and extract the story ID from the comment15:21
krotscheck2- Story search index includes comments.15:21
krotscheckBut even then....15:21
krotscheckHow important is it to indicate that a search hit was on a comment rather than on a story?15:21
krotscheckConsider the UI: “Hey we found our search on a comment”15:22
*** erecio has quit IRC15:22
krotscheckAlso there’s the whole “What’s easy to do right now”, because comments might end up on more than one resource type.15:23
*** yamamoto has joined #openstack-meeting-315:23
ttxkrotscheck: I think it's hinier if you autoscroll, but it's also OK if you don't15:23
NikitaKo_My vote is for 1 here15:23
ttxshinier15:23
mordredI think ultimately 1 sounds richer - because as you said, there may be more things that have comments15:24
NikitaKo_the comments endpoint is pretty similar to any other, and since there is going to be a SqlAlchemy implementation it should be pretty easy15:24
krotscheckI have no disagreements with 1.15:25
krotscheckYeah, actually, the more I think about it the more I prefer it.15:25
krotscheckSo, it sounds like search is a feature of all primary resources, and ‘subresource’ implementations end up more as convenience filters?15:26
krotscheck(which makes everything a primary resource)15:26
*** Kadence has joined #openstack-meeting-315:26
jeblairkrotscheck: i think the presentation of the results can help with that15:27
jeblairkrotscheck: before displaying the story and autoscrolling to the comment15:27
jeblairkrotscheck: you're probably going to display a list of results, and in that, i'm bettinng you can make it clear the hit was on a story or comment or ...15:27
*** yamamoto has quit IRC15:27
jeblairkrotscheck: (i'm slightly laggy and responding to several minutes old text)15:28
*** cjellick has joined #openstack-meeting-315:28
krotscheckI think everyone should go look at the new search/browse UI :)15:28
krotscheckThis one: https://review.openstack.org/#/c/99975/15:28
*** otherwiseguy has joined #openstack-meeting-315:29
ttxkrotscheck: ok, added to todo15:29
NikitaKo_krotscheck: I've already did, and it looks great15:29
krotscheckNikitaKo_: Yeah, and after the discussion this morning I’m way happier with having comments.15:30
krotscheck(Fair warning for everyone, I’ve since built on that UI to add things like auto-tab-focus)15:30
krotscheckjeblair: No worries. Honestly, we’ll test the autoscroll and see how people respond before approving that.15:31
krotscheckjeblair: Autoscroll to me is one of those ‘It could be awesomely bad if built incorrectly’ features.15:31
krotscheckjeblair: The new search UI actually clearly separates the resources on which you got a hit.15:31
krotscheckAnyway: Any more comments on search? I think we know where we’re going at the moment.15:32
krotscheckNikitaKo_: Do you still want me to add comments as a blank resource, given that the UI won’t ever show that section if the results are hardcoded to []?15:33
NikitaKo_krotscheck: I guess no15:33
jeblairthat's a very big change15:33
*** otherwiseguy has quit IRC15:33
krotscheckjeblair: Believe me, I tried to break it up.15:33
NikitaKo_the browse.js means it does browsing through resources, we will need something like search.js to handle them15:34
NikitaKo_and actually to query search endpoints when they are ready15:34
NikitaKo_The WIP change is here btw https://review.openstack.org/#/c/101476/15:35
*** otherwiseguy has joined #openstack-meeting-315:35
*** NikitaKo_ has quit IRC15:37
krotscheckOk....15:37
*** NikitaKo_ has joined #openstack-meeting-315:37
krotscheckOh good, he’s back15:37
NikitaKo_something strange is going on with my irc client15:37
krotscheckIt’s probably MI-615:38
krotscheckAny more comments on specifications?15:38
krotscheckElse we can move on to ongoing work.15:38
NikitaKo_There is a new one15:38
NikitaKo_https://review.openstack.org/#/c/103106/15:39
* krotscheck makes a note to look at that.15:39
NikitaKo_This is for teams API15:39
NikitaKo_The main idea there is that user teams could be synced from Gerrit15:39
krotscheckHrm...15:40
krotscheckDoes this include some of the original permissions spec?15:40
NikitaKo_krotscheck: are you referring to the etherpad with permissions?15:41
krotscheckYeah15:41
NikitaKo_It does not right now, but it's a good idea to add that stuuff15:42
jeblairwe used to sync launchpad and gerrit teams, and then we stopped15:43
NikitaKo_jeblair: why?15:43
jeblairit was extremely difficult to do correctly15:43
jeblairand as it turns out we needed different teams in the different tools15:43
jeblairthe closest thing to an overlap where the tools might use the same teams are using gerrit core reviewers when dealing with security bugs15:45
jeblairttx: what's the current thinking on that? ^15:45
jeblair(but in generaly, bug triagers are not necessarily core reviewers, and vice-versa)15:45
NikitaKo_is there any other source to get core members except Gerrit group?15:46
ttxjeblair: the only thing we use launchpad groups for is now for subscription to private bugs and permissions granting15:46
jeblairand drivers (people who can set milestone targets on bugs or blueprints [stories]) don't have much to do in gerrit15:46
* krotscheck makes a note to transfer permissions specification to infra-specs15:46
ttxand those are largely disjoint from gerrit groups15:46
ttxso the pain of syncing was no longer worth the benefit15:46
ttxerr... the other way around15:47
*** nati_ueno has quit IRC15:47
jeblairmy inclination would be that we should make sure that we have a good api so that people (maybe us in the future, even) can sync mebership automatically with external tools...15:47
jeblairbut not to depend on them directly, and not expect us to do any automated syncing in the near future15:47
NikitaKo_then we need to decide which kind of groups StoryBoard should have15:48
NikitaKo_more Gerrit-like, or Launchpad-like15:48
*** armax has joined #openstack-meeting-315:48
krotscheckSo, what is a group?15:48
NikitaKo_A group of users with a set of permissions15:49
ttxkrotscheck: I'd say, an entity permissions can be granted to15:49
ttxAND a set of people you'd like to add to a private bug ACL15:49
ttxbut that's not the immediate use case15:49
NikitaKo_possibly assign a task to a group?15:50
ttxand that can be considered a "permission" too15:50
ttxNikitaKo_: I'm not sure we want to encourage that15:50
ttxNikitaKo_: but yes, that was possible in LP15:50
krotscheckSounds like we need to do some requirements gathering on this. Can I ask everyone to write up their concept of what a “team” and/or “group” is and send it to NikitaKo_ ?15:50
ttxI can take that15:50
krotscheckAlright15:50
krotscheckSend it to ttx then :)15:51
ttxunless you need it for tomorrow15:51
krotscheckI dunno, NikitaKo_: When do you need it by?15:51
ttxTC handling bogged me down last week15:51
*** yamamoto has joined #openstack-meeting-315:51
NikitaKo_By the moment we start protected tags or something like that15:51
ttxNikitaKo_: ok15:52
*** nacim has quit IRC15:52
ttxshould that be a specs, or more a wiki page ?15:52
krotscheckttx: Eeehhh,… I’m leaning more wiki right now? Spec is more detailed and implementation specific.15:53
ttxkrotscheck: ++15:53
krotscheckI want the eventual output to be sortof like the use case section I added to NikitaKo_ ’s search spec.15:53
ttxlet's call it a brainstorming wikipage15:53
krotscheckAwesome.15:53
krotscheckAny other specs thoughts?15:54
krotscheck#topic Ongoing work!15:55
*** openstack changes topic to "Ongoing work! (Meeting topic: storyboard)"15:55
krotscheckEveryone gets a minute!15:55
krotscheckReverse alphabetical order!15:55
ttxhmm, that may mean me15:55
krotscheckYolanda got her momentjs things merged, awesome!15:55
krotscheckttx is next!15:55
*** yamamoto has quit IRC15:55
* ttx managed to do some reviews, and pushed a new version of the Tag spec, but that's about it15:56
*** jackib has quit IRC15:56
ttxblame Defcore15:56
ttxnext15:56
NikitaKo_I've started that Teams spec15:56
*** MaxV has quit IRC15:56
NikitaKo_And there is a change setting up oslo.messaging for notifications15:57
NikitaKo_https://review.openstack.org/#/c/102842/15:57
krotscheckAwesome.15:57
NikitaKo_It is based on TimeLine events we already have15:57
NikitaKo_Work on my local rabbit pretty nicely15:57
krotscheckNoce.15:57
krotscheckNice15:57
krotscheckNice nice15:58
NikitaKo_So that's all from me15:58
krotscheckI wrote out use cases for search, which I then promptly incorporated into my UI work. Did an ad-hoc UX test with a random person I met at a coffeeshop which also helped me refine the UI on the search page.15:58
krotscheckAlso a bit of work on the storyboard puppet module after a bunch of good comments from reviewers.15:59
* krotscheck is trying to get rabbit onto storyboard.openstack.org15:59
*** jackib has joined #openstack-meeting-315:59
krotscheckMaxV disconnected right when we were about to get to him.15:59
krotscheckAishwarya is stuck in HP background checks, but I’m meeting up with her in an hour.16:00
krotscheckAnd that’s it!16:00
ttxyay16:00
krotscheck#endmeeting16:00
*** openstack changes topic to "Services’ integration (Meeting topic: networking_policy)"16:00
openstackMeeting ended Mon Jun 30 16:00:30 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/storyboard/2014/storyboard.2014-06-30-15.02.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/storyboard/2014/storyboard.2014-06-30-15.02.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/storyboard/2014/storyboard.2014-06-30-15.02.log.html16:00
NikitaKo_thanks everyone16:00
*** sankarshan is now known as sankarshan_away16:00
*** NikitaKo_ has quit IRC16:00
*** jpich has left #openstack-meeting-316:07
*** erecio has joined #openstack-meeting-316:11
*** shakamunyi has joined #openstack-meeting-316:15
*** shakamunyi has quit IRC16:15
*** shakamunyi has joined #openstack-meeting-316:16
*** shakamunyi has quit IRC16:17
*** shakamunyi has joined #openstack-meeting-316:17
*** shakamunyi has quit IRC16:18
*** shakamunyi has joined #openstack-meeting-316:18
*** iovadia has quit IRC16:19
*** Longgeek has joined #openstack-meeting-316:33
*** briancurtin has joined #openstack-meeting-316:34
*** MaxV has joined #openstack-meeting-316:34
*** briancurtin has quit IRC16:34
*** briancurtin has joined #openstack-meeting-316:34
*** safchain has quit IRC16:43
*** sarob has joined #openstack-meeting-316:44
*** NikitaKo_ has joined #openstack-meeting-316:48
*** sarob has quit IRC16:51
*** yamamoto has joined #openstack-meeting-316:51
*** sarob has joined #openstack-meeting-316:51
*** coolsvap|afk is now known as coolsvap16:52
*** NikitaKo_ has quit IRC16:53
*** jtomasek has quit IRC16:55
*** yamamoto has quit IRC16:56
*** jackib has quit IRC16:57
*** sarob has quit IRC16:58
*** sarob has joined #openstack-meeting-316:58
*** jackib has joined #openstack-meeting-317:01
*** NikitaKo_ has joined #openstack-meeting-317:03
*** pballand has joined #openstack-meeting-317:04
*** gduan has quit IRC17:04
*** MaxV has quit IRC17:05
*** MaxV_ has joined #openstack-meeting-317:06
*** lenrow has joined #openstack-meeting-317:06
*** NikitaK__ has joined #openstack-meeting-317:07
*** NikitaKo_ has quit IRC17:07
*** beyounn has joined #openstack-meeting-317:10
*** NikitaK__ has quit IRC17:11
*** NikitaKo_ has joined #openstack-meeting-317:13
*** nati_ueno has joined #openstack-meeting-317:14
*** clu_ has joined #openstack-meeting-317:15
*** clu_ has left #openstack-meeting-317:15
*** ivar-lazzaro has joined #openstack-meeting-317:17
*** Sukhdev has joined #openstack-meeting-317:23
*** jackib has quit IRC17:23
*** MaxV_ has quit IRC17:25
*** MaxV has joined #openstack-meeting-317:25
*** NikitaKo_ has quit IRC17:25
*** otherwiseguy has quit IRC17:29
*** jackib has joined #openstack-meeting-317:29
*** otherwiseguy has joined #openstack-meeting-317:30
*** ivar-lazzaro has quit IRC17:32
*** MaxV has quit IRC17:34
*** kenhui has quit IRC17:34
*** kenhui has joined #openstack-meeting-317:34
*** ivar-lazzaro has joined #openstack-meeting-317:37
*** Sukhdev has quit IRC17:45
*** otherwiseguy has quit IRC17:46
*** thomasem has quit IRC17:48
*** otherwiseguy has joined #openstack-meeting-317:51
*** yamamoto has joined #openstack-meeting-317:51
*** thomasem has joined #openstack-meeting-317:51
*** erecio has quit IRC17:54
*** erecio has joined #openstack-meeting-317:55
*** yamamoto has quit IRC17:56
*** sbalukoff has joined #openstack-meeting-317:57
*** sarob has quit IRC18:09
*** salv-orlando has joined #openstack-meeting-318:11
*** salv-orlando has left #openstack-meeting-318:12
*** garyduan has joined #openstack-meeting-318:14
*** SumitNaiksatam has joined #openstack-meeting-318:18
*** coolsvap is now known as coolsvap|afk18:24
*** lsmola__ has joined #openstack-meeting-318:31
*** Sukhdev has joined #openstack-meeting-318:35
*** gduan has joined #openstack-meeting-318:38
*** garyduan has quit IRC18:39
*** lsmola__ has quit IRC18:50
*** yamamoto has joined #openstack-meeting-318:51
*** otherwiseguy has quit IRC18:53
*** pballand has quit IRC18:53
*** yamamoto has quit IRC18:56
*** lsmola__ has joined #openstack-meeting-319:03
*** lsmola__ has quit IRC19:08
*** thomasem has quit IRC19:09
*** thomasem has joined #openstack-meeting-319:11
*** nati_ueno has quit IRC19:11
*** nati_ueno has joined #openstack-meeting-319:12
*** markmcclain has joined #openstack-meeting-319:14
*** pballand has joined #openstack-meeting-319:17
*** kenhui has quit IRC19:24
*** otherwiseguy has joined #openstack-meeting-319:27
*** julim has quit IRC19:30
*** julim has joined #openstack-meeting-319:33
*** amitpp has joined #openstack-meeting-319:35
*** briancurtin is now known as briancurtin_away19:38
*** markmcclain has quit IRC19:49
*** yamamoto has joined #openstack-meeting-319:51
*** shakamunyi has quit IRC19:52
*** shakamunyi has joined #openstack-meeting-319:53
*** yamamoto_ has joined #openstack-meeting-319:53
*** shakamunyi has quit IRC19:53
*** nati_ueno has quit IRC19:55
*** nati_ueno has joined #openstack-meeting-319:55
*** yamamoto has quit IRC19:56
*** yamamoto_ has quit IRC19:57
*** MaxV_ has joined #openstack-meeting-319:58
*** julim has quit IRC20:00
*** MaxV_ has quit IRC20:00
*** briancurtin_away is now known as briancurtin20:01
*** julim has joined #openstack-meeting-320:02
*** jackib has quit IRC20:11
*** amitpp has quit IRC20:14
*** sarob has joined #openstack-meeting-320:14
*** sarob has quit IRC20:16
*** alexpilotti has quit IRC20:16
*** sarob has joined #openstack-meeting-320:17
*** sarob has quit IRC20:26
*** Longgeek has quit IRC20:28
*** overlayer has quit IRC20:30
*** johnthetubaguy is now known as zz_johnthetubagu20:34
*** Sukhdev has quit IRC20:35
*** markmcclain has joined #openstack-meeting-320:36
*** SumitNaiksatam has quit IRC20:38
*** catherine_d has joined #openstack-meeting-320:38
*** amotoki has quit IRC20:47
*** cjellick_ has joined #openstack-meeting-320:47
*** amotoki has joined #openstack-meeting-320:47
*** amotoki has quit IRC20:47
*** amotoki has joined #openstack-meeting-320:48
*** cjellick has quit IRC20:50
*** ttrifonov is now known as ttrifonov_zZzz20:51
*** yamamoto has joined #openstack-meeting-320:51
*** Sukhdev has joined #openstack-meeting-320:52
*** tomoe_ has joined #openstack-meeting-320:55
*** yamamoto_ has joined #openstack-meeting-320:56
*** yamamoto has quit IRC20:56
*** jackib has joined #openstack-meeting-321:00
*** yamahata has joined #openstack-meeting-321:02
*** catherine_d has left #openstack-meeting-321:02
*** thomasem has quit IRC21:03
*** catherine_d has joined #openstack-meeting-321:05
*** SumitNaiksatam has joined #openstack-meeting-321:06
*** davidlenwell_ is now known as davidlenwell21:07
*** catherine_d has left #openstack-meeting-321:08
*** sarob has joined #openstack-meeting-321:15
*** markmcclain has quit IRC21:20
*** julim has quit IRC21:21
*** HenryG_ has joined #openstack-meeting-321:26
*** nati_uen_ has joined #openstack-meeting-321:27
*** jackib1 has joined #openstack-meeting-321:28
*** yamahata__ has joined #openstack-meeting-321:29
*** erecio has quit IRC21:30
*** overlayer has joined #openstack-meeting-321:31
*** sarob has quit IRC21:34
*** jackib has quit IRC21:34
*** ttrifonov_zZzz has quit IRC21:34
*** HenryG has quit IRC21:34
*** safchain has joined #openstack-meeting-321:35
*** ttrifonov_zZzz has joined #openstack-meeting-321:35
*** csd has quit IRC21:35
*** nati_ueno has quit IRC21:35
*** kevinbenton has quit IRC21:35
*** yamahata has quit IRC21:35
*** peristeri has quit IRC21:35
*** csd has joined #openstack-meeting-321:36
*** lblanchard has quit IRC21:36
*** kevinbenton has joined #openstack-meeting-321:36
*** tomoe_ has quit IRC21:37
*** tomoe_ has joined #openstack-meeting-321:38
*** sarob has joined #openstack-meeting-321:42
*** peristeri has joined #openstack-meeting-321:43
*** peristeri has quit IRC21:43
*** pgpus has quit IRC21:46
*** cjellick_ has quit IRC21:49
*** cjellick has joined #openstack-meeting-321:50
*** fcarpent_ has joined #openstack-meeting-321:53
*** chuckC has quit IRC21:58
davidlenwell#startmeeting refstack22:00
openstackMeeting started Mon Jun 30 22:00:33 2014 UTC and is due to finish in 60 minutes.  The chair is davidlenwell. Information about MeetBot at http://wiki.debian.org/MeetBot.22:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:00
*** openstack changes topic to " (Meeting topic: refstack)"22:00
openstackThe meeting name has been set to 'refstack'22:00
davidlenwellroll call?22:02
*** pballand has quit IRC22:02
fcarpent_o/22:03
*** amotoki has quit IRC22:03
davidlenwellFirst week of new meeting time .. we'll give everyone a few minutes before giving up on them all22:04
*** lcheng has quit IRC22:05
zehicleo/22:07
davidlenwelllets wait a few more minutes to see if catherine/rocky show22:07
zehicleand there was a request to move the meeting back to 10 am already (keep on Monday22:07
davidlenwellby whome?22:08
*** armax has left #openstack-meeting-322:08
zehiclethe Mirantis contractors22:08
zehiclethis time is super bad for them22:08
davidlenwellI feel like we are playing musical meetings22:08
zehiclemy mistake for miscaculating22:08
zehicleyy22:08
zehicleI can proxy for them22:09
davidlenwellnobody is showing up for this meeting anyways.. I feel like if we change it again we'll have low attendance again22:09
davidlenwellbut I'm open to discussing it22:09
*** lcheng has joined #openstack-meeting-322:09
*** catherine_d has joined #openstack-meeting-322:10
*** sarob has quit IRC22:10
zehicleagree22:10
davidlenwellalright im going to start..22:10
zehiclethis time is ok but not great for me22:10
zehicle+122:10
zehiclelet;s roll22:10
*** catherine_d has left #openstack-meeting-322:10
*** sarob has joined #openstack-meeting-322:10
*** catherine_d has joined #openstack-meeting-322:10
*** catherine_d has left #openstack-meeting-322:10
*** catherine_d has joined #openstack-meeting-322:11
*** pballand has joined #openstack-meeting-322:11
*** catherine_d has quit IRC22:11
*** catherine_d has joined #openstack-meeting-322:12
davidlenwellagenda: api status, schema migration, sqlite, graphs for defcore, dell contractors22:12
zehicle+122:12
davidlenwell+ meeting time22:12
davidlenwell#topic api status22:12
*** openstack changes topic to "api status (Meeting topic: refstack)"22:12
davidlenwellI'm very close to commiting a patch that will give us full api functionlity that meets the v1 api spec.22:13
zehicle:)22:13
zehiclethe Mirantis guys say that they are looking at unit tests for it22:13
zehicleI'll check w/ them tomorrow22:13
davidlenwellI am still missing unit tests..22:13
*** beyounn has quit IRC22:13
*** sarob has quit IRC22:15
*** catherine_d has quit IRC22:16
davidlenwellI'd preffer to just write the api unit tests myself and leave the schema and migration unit tests to the contractors .. but we'll get back to that in a bit when theya re the topic22:16
*** HenryG_ has quit IRC22:16
zehicleok, that would be better22:16
zehicleagree22:16
davidlenwellokay .. so we're on the same page here.. next topic22:17
davidlenwell#topic schema change22:17
*** openstack changes topic to "schema change (Meeting topic: refstack)"22:17
davidlenwellwith the exception of zehicle's -1 because of "the allowable types should be documented with a safe default given (0=unknown). Also, there should be a field test to limit the values to the know values."22:18
zehiclekk22:18
davidlenwellI think its in good shape to merge once the api stuff is finished.. I was hoping catherine would be around to give an opinion on that but she seems to be having connectivity issues.22:18
*** catherine_d has joined #openstack-meeting-322:18
zehicle+1 agree22:18
davidlenwell(these meetings go a lot faster when nobody shows up ;) )22:19
davidlenwell#topic sqlite22:19
*** openstack changes topic to "sqlite (Meeting topic: refstack)"22:19
davidlenwellsqlite migration has been a bit painful... alembic doesn't deal well with its special edge cases. And I hate that someone on our team would need to write a bunch of extra code to make sqlite happy everytime we want to change the name of a feild.22:20
davidlenwellI would like to continue to have an open discussion about why / if we should continue to support it at all.22:20
*** HenryG has joined #openstack-meeting-322:21
*** HenryG has quit IRC22:21
zehicleI'm ok to NOT have sqlite22:21
davidlenwellso far my pros are; easier to get a dev env going...22:21
*** tomoe_ has quit IRC22:21
davidlenwellcons are: poor sql support, poor alembic support .. pain in the ass migrations22:21
davidlenwellso you can see which way I am leaning22:21
davidlenwellI can table this till next week when more folks show up at the meeting and can offer an opinion..22:22
davidlenwellfcarpent_: Do you have any opinions on removing sqlite support?22:22
*** HenryG has joined #openstack-meeting-322:22
fcarpent_not without better understanding the alternatives22:22
*** fcarpent_ is now known as fcarpenter22:22
davidlenwellfcarpenter: the alt is to only support mysql / postgres22:23
davidlenwellbecause they can migrate cleaner22:23
fcarpenterat first blush it doesn't sound like a "need to have" for v122:23
davidlenwellokay .. well lets agree to pick up this discussion in another week.22:23
davidlenwell#agree we'll pick up the sqlite discussion in a week.22:23
davidlenwell#topic graphs for defcore22:24
*** openstack changes topic to "graphs for defcore (Meeting topic: refstack)"22:24
davidlenwellSo last week joshua and I did some brain storming.22:24
zehiclegraphs = the screen casts22:24
davidlenwellWe'd like to go a slightly diff direction on the graphs and reporting for defcore than the current proposed spec describes22:24
*** jaypipes has quit IRC22:24
zehicleok, happy to see alternatives22:25
davidlenwellI am going to sit down with joshua in the next couple of days to submit a review on an updated spec clearly describing the idea.. this way you can all have input22:25
davidlenwellhe's also volunteered to do the coding becuase he's excited about this type of graphing tool.22:25
zehicleok22:26
davidlenwellI'd like more code out of him if we can get it22:26
catherine_dHidHi22:26
zehiclethat's fine w/ me22:27
*** catherine_d has quit IRC22:27
davidlenwellcool .. spec to follow22:27
zehiclejust send me a picture of what he's thinking22:27
*** catherine_d has joined #openstack-meeting-322:27
davidlenwellzehicle: I want a spec because the visualizations them selves are a lot more flexible than the underlying data it self..22:27
zehiclesure22:27
davidlenwellSo the spec will describe clearly how we are going to store stuff.. which we are currently missing22:28
zehiclethe data is the harder thing to get22:28
davidlenwellits a giant hole in our architecture22:28
zehiclewe'll learn what we want to show as we have data22:28
davidlenwellopen .. moving right along ..22:28
zehicleI owe everyone the spec on the JSON & flows22:28
zehicleI've got drafts of them, just need to write the spec22:28
zehiclethe flow is being reviewed by defcore22:28
davidlenwellvery good22:28
davidlenwellwhen is the next defcore meeting ?22:29
zehiclenot scheduled22:29
zehiclethere are community ones 7/922:29
zehicleand a TC interlock tomorrow22:29
zehicle1pm PT22:29
davidlenwellgood to know22:29
zehicleI suggest bringing some popcorn to watch the fireworks22:29
davidlenwellgood advice22:30
*** catherine_d has quit IRC22:30
davidlenwell#topic dell contractors22:30
*** openstack changes topic to "dell contractors (Meeting topic: refstack)"22:30
zehicleI'm making sure my asbestos suit is back from the cleaners22:30
zehicle+1 Dell Contractors22:30
davidlenwellI know we need to do some work to plan things so that we can keep the contractors busy while they are engadged22:30
zehiclethey were able to get Refstack working and explored the code22:31
davidlenwellwe can start with having them tackle our test coverage22:31
zehiclethey are making plans about how to improve coverage22:31
davidlenwellwhile they do that I'll review all the open stories22:31
zehicleI asked them to focus on API & upload22:31
davidlenwellhmm .. well since I am doing that you can refocus them22:31
zehiclewould be helpful if we had stories that I can point them to22:31
zehicle+122:31
davidlenwellwe have a ton of open stories22:31
davidlenwellneed to be tretriaged22:32
zehicleI meet w/ the contractors tomorrow early22:33
davidlenwellI'll make that a priority in the next couple of days22:33
zehicleany direction is helpful22:33
davidlenwellzehicle: define early22:33
zehicle7am central22:33
davidlenwellwow thats early22:33
davidlenwellI might still be awake then22:33
zehiclelast week it was 5:3022:33
*** tedchang has joined #openstack-meeting-322:33
*** shakamunyi has joined #openstack-meeting-322:33
zehiclebut that was just because I was at the airport anyway22:33
*** sarob has joined #openstack-meeting-322:33
davidlenwellDo you want me to try to make an apearance for that meeting?22:34
davidlenwellmanaging developers by proxy is hard22:34
davidlenwellI'd like to get an idea of strengths and stuff22:34
*** pballand has quit IRC22:34
zehicleI have their backgrounds - I'll forward 1x122:34
davidlenwellsounds good22:35
*** safchain has quit IRC22:35
tedchangHi This is Catherine using Ted's machine ... Having problem with my IRC22:35
zehiclethat's why I was suggesting moving the meeting time back to 10 am22:35
zehicleso you'd have direct contact22:35
davidlenwellzehicle: alright .. that seems to be the next topic anyway22:35
zehiclemy goal is to have them operate in community, not act as puppets for me22:35
davidlenwell#topic meeting time22:35
*** openstack changes topic to "meeting time (Meeting topic: refstack)"22:35
davidlenwellzehicle has asked that we move the meeting to monday at 10am pdt .. any objections?22:36
*** catherine_d has joined #openstack-meeting-322:36
zehiclemy apologies > I mis-spoke about the time zone needs for our EU people22:36
zehiclethis time is 2 am for them22:36
*** catherine_d has left #openstack-meeting-322:36
tedchang10 am on Monday works for me22:36
zehicleentirely my fault when we were discussing before22:37
*** catherine_d has joined #openstack-meeting-322:37
* davidlenwell thanks zehicle for granade jumping 22:37
fcarpenter10am is fine for me22:37
zehiclebetter for me than 5 central22:37
davidlenwellokay lets do 10am on mondays.. I'll update things again in the wiki22:37
zehiclethanks22:37
zehicleI'll let them know tomorrow AM22:38
*** tedchang has quit IRC22:38
davidlenwell#agree meeting to change to 10am pdt mondays22:38
*** pballand has joined #openstack-meeting-322:38
davidlenwell#agreed meeting to change to 10am pdt mondays22:38
*** pballand has quit IRC22:38
davidlenwell#topic mid cycle meeting in Darmstadt germany22:39
*** openstack changes topic to "mid cycle meeting in Darmstadt germany (Meeting topic: refstack)"22:39
davidlenwellI will be attending the q/a, infra mid-cycle thing in germany in two weeks.. I will most likely still be available for the monday meetings .. but if I am absent zehicle will moderate the meetings in my place22:40
zehicle+1 can do22:40
zehicleI will have a conflict on the OSCON week22:40
davidlenwellI'll be back for that22:41
davidlenwell#topic open discussion22:41
*** openstack changes topic to "open discussion (Meeting topic: refstack)"22:41
davidlenwellzehicle: are you going to oscon?22:41
zehicleyy22:41
zehicleboardmeeting and presenting DefCore at the cloud day22:41
davidlenwellhappy birthday openstack22:41
catherine_dCould we talk about coding work ...22:41
davidlenwellcatherine_d: you missed half the meeting .. we talked about a lot of stuff..22:42
davidlenwellwe have 18 minutes for open discussion now.. we can talk about whatever you like.22:42
catherine_dwe need the code for https://review.openstack.org/#/c/98914/22:42
davidlenwellyes we do22:42
catherine_dto get us going with local refstack for Icehouse22:42
davidlenwellyes ..22:43
davidlenwellSo is that code you want to tackle catherine_d?22:43
davidlenwellI know we talked about that before22:44
catherine_dyes we can22:44
davidlenwellI'm good with that22:44
davidlenwellcatherine_d: I am not sure if we put the work items from that spec into story board yet.. I'll make sure they are in storyboard today22:44
davidlenwelland as you make commits could you keep story board up to date ..that way I know the status of things22:45
catherine_dgreat.. also once we have that code ... we will need some update the web.py ... do you want us to update the old code or should we only use the new V1 API?22:45
davidlenwellcatherine_d: that is going to require some discussion22:45
davidlenwellwe also have an issue with two different testers22:46
davidlenwellcatherine_d: Do you have time next week for a face to face?22:46
catherine_dyes we do ...22:46
*** carl_baldwin has quit IRC22:47
davidlenwellit might be more productive to lock our selves in a room and work out how we are going to do this stuff22:47
davidlenwellwith whiteboards22:47
catherine_dhow about you pick one tester then we can use that tester and identify what else needed22:47
davidlenwellthe newer tester is prefered22:47
catherine_dagree ..22:47
davidlenwellbut it kinda breaks the way you were driving tests/config from the web ui22:47
catherine_dshould we have a face-2-face ... I really want to get refstack local to work with Icehouse22:48
davidlenwellI'm free next monday,tuesday,wednesday22:48
catherine_dLet's be it ... refstack is not worlking with Icehoiuse any way .. and I am not sure we want to do much work on Havana22:48
davidlenwellwe don't22:49
davidlenwellSo lets talk offline about when we can have facetime22:49
catherine_dgreat let's do that ...22:49
davidlenwelldoes anyone have anything else to discuss?22:49
catherine_dAbout pushing data ..22:50
catherine_dright now we have an API to push with keystone UUID ...22:51
catherine_dhow about API with tester ID... we we plan to use the same API or update the current API?22:51
*** Sukhdev has quit IRC22:51
davidlenwellsame function for both22:52
davidlenwellits all detailed int he spec22:52
davidlenwellI'm also almost finished with the working api code.. trying to get it in today.. just working out a bug in the validation22:52
catherine_dI did not see the test id option in https://review.openstack.org/#/c/99752/22:53
*** sarob has quit IRC22:54
*** Kadence has quit IRC22:54
davidlenwellits called job_id22:55
catherine_dic22:55
davidlenwell {11922:55
davidlenwell     'cpid': '2fd4e1c67a2d28fced849ee1bb76e7391b93eb12',12022:55
davidlenwell     'duration_seconds': 23445234,12122:55
davidlenwell     'job_id': '3fd4e1c67a2d28fced849ee1bb76e7391b93eb13', /*optional*/12222:55
davidlenwell     'results': {} /* to be defined */12322:55
davidlenwell    }22:55
catherine_dgreat22:55
davidlenwellSo a few things have been renamed .. but that functionality was preserved22:56
davidlenwellokay .. so thats all the time we have for today boys and girls.. until next week22:56
davidlenwell#endmeeting22:57
*** openstack changes topic to "Services’ integration (Meeting topic: networking_policy)"22:57
openstackMeeting ended Mon Jun 30 22:57:05 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/refstack/2014/refstack.2014-06-30-22.00.html22:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/refstack/2014/refstack.2014-06-30-22.00.txt22:57
openstackLog:            http://eavesdrop.openstack.org/meetings/refstack/2014/refstack.2014-06-30-22.00.log.html22:57
*** fcarpenter has left #openstack-meeting-322:57
*** banix has quit IRC22:57
*** armax has joined #openstack-meeting-323:00
*** MaxV_ has joined #openstack-meeting-323:04
*** armax has left #openstack-meeting-323:05
*** tomoe_ has joined #openstack-meeting-323:08
*** TravT has joined #openstack-meeting-323:08
*** MaxV_ has quit IRC23:09
*** sarob has joined #openstack-meeting-323:10
*** yamamoto_ has quit IRC23:13
*** MaxV_ has joined #openstack-meeting-323:15
*** chuckC has joined #openstack-meeting-323:17
*** MaxV_ has quit IRC23:19
*** tomoe_ has quit IRC23:21
*** yamahata__ has quit IRC23:23
*** MaxV_ has joined #openstack-meeting-323:23
*** sankarshan_away is now known as sankarshan23:26
*** markmcclain has joined #openstack-meeting-323:26
*** markmcclain has quit IRC23:30
*** lcheng has quit IRC23:31
*** markmcclain has joined #openstack-meeting-323:34
*** david-lyle has quit IRC23:36
*** nelsnelson has quit IRC23:38
*** jackib1 has quit IRC23:40
*** jackib has joined #openstack-meeting-323:47
*** overlayer has quit IRC23:50
*** shakamunyi has quit IRC23:52
*** MaxV_ has quit IRC23:53
*** shakamunyi has joined #openstack-meeting-323:53
*** shakamunyi has quit IRC23:53
*** tomoe_ has joined #openstack-meeting-323:59
*** tomoe_ has quit IRC23:59

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