Monday, 2015-02-02

*** wuhg has joined #storyboard01:58
*** mase_x200 has joined #storyboard02:01
*** mase_x200 has quit IRC04:13
*** alexismonville has joined #storyboard06:23
*** alexismonville has quit IRC06:39
*** alexismonville has joined #storyboard06:47
*** jcoufal has joined #storyboard07:00
*** jcoufal_ has joined #storyboard07:49
*** jcoufal has quit IRC07:52
*** jtomasek has joined #storyboard08:06
*** MaxV has joined #storyboard08:57
*** MaxV has quit IRC09:02
*** MaxV has joined #storyboard09:13
*** mase_x200 has joined #storyboard10:57
*** mrmartin has joined #storyboard11:11
yolandattx, i was reading your comments, they make a lot of sense. But do you still want to keep this step, maybe calling that "merged" stories, or shall we create a wider one about story relationships?11:32
yolandabtw, how was your Storyboard presentation?11:33
nibalizeryolanda: he killed it11:35
nibalizerpackjed room, i coukdnt get in11:35
nibalizerbut heard a lot of good things11:35
yolandanice, great to have that interest on the project11:35
yolandait motivates us to work harder11:36
yolandanibalizer, did you hear feedback from people, requests, usability problems, etc?11:36
mrmartinhi11:39
mrmartinthere was a great interest, but some guys want to use jira instead :)11:39
nibalizeryolanda: buzz mostly11:41
nibalizerand ttx's talk was about a bunch of infra toola11:41
nibalizernot just sb11:41
yolandahow long were the talks?11:41
mrmartinthere was some video recording I guess11:42
mrmartinthey not published the videos, but will be here: http://video.fosdem.org11:43
yolandai want to watch it11:44
yolandamm, tons of interesting topics there11:44
mrmartinjust a small part was about storyboard, but the people noticed that. I think most of them had problems with lp previously11:44
mrmartinbut all of our Infra sessions was great11:45
mrmartinnibalizer's presentation about upstream/downstream usage at hp was awesome11:45
yolandai should have posted some conf proposals, maybe they could have accepted one11:46
mrmartinbasically the event was overcrowded11:46
mrmartina lot of rooms was simply full, it was impossible to get in11:46
yolanda It’s not a bug, it’s an environment problem.11:47
yolandanibalizer, we could tell taht!11:47
yolandawe could close tons of jira tickets with that answer11:47
*** miqui_away has quit IRC12:21
openstackgerritAleksey Ripinen proposed openstack-infra/storyboard: Delete created_at and updated_at fields from requests  https://review.openstack.org/15164113:35
openstackgerritAleksey Ripinen proposed openstack-infra/storyboard: Reject false creator_id from requests  https://review.openstack.org/15165013:38
openstackgerritNikita Konovalov proposed openstack-infra/storyboard: Fix status code on delete  https://review.openstack.org/15160314:12
ttxyolanda: we should have a longer discussion about it14:15
ttxI'm travelling right now, so not optimal for a long discussion14:15
ttxI'll miss the Storyboard meeting btw14:15
yolandaok, we can do it other day, that's no urgent item14:15
ttxMaybe ping me later this week ?14:15
ttxmrmartin: I see you're safely back home14:16
mrmartinhi ttx14:16
mrmartinyeap :)14:16
yolandasure, i'll ping you this week when i see you online14:16
*** mase_x200 has quit IRC14:27
*** rcarrillocruz has quit IRC14:35
*** ongk has quit IRC14:38
*** rcarrillocruz has joined #storyboard14:38
*** ongk has joined #storyboard14:41
openstackgerrityolanda.robla proposed openstack-infra/storyboard-webclient: Fix in project groups validation  https://review.openstack.org/15213314:42
openstackgerritNikita Konovalov proposed openstack-infra/storyboard: Fix NotFound errors  https://review.openstack.org/15213714:46
*** openstackgerrit has quit IRC14:52
*** openstackgerrit has joined #storyboard14:52
openstackgerritAleksey Ripinen proposed openstack-infra/storyboard: Added branches to storyboard  https://review.openstack.org/15044715:03
krotscheckaripinen, NikitaKonovalov: I’m seeing two different ways of handling error code responses in the API. One is abort(400), the other is something like raise exc.NotFound(). Does it make sense for us to use both ways, or should we stick to one method of handling errors?15:21
openstackgerritMerged openstack-infra/storyboard: Fix stories put method  https://review.openstack.org/15164315:24
openstackgerritMerged openstack-infra/storyboard: Whitelisted bash in the tox configuration  https://review.openstack.org/15129315:28
openstackgerritMerged openstack-infra/python-storyboardclient: Stories and Tasks support  https://review.openstack.org/15006715:29
yolandakrotscheck, ah, i had same question, i posted on a review15:33
yolandaabout the abort or custom validation15:33
NikitaKonovalovkrotscheck: abort or raise exception is pretty much the same thing15:34
NikitaKonovalovabort call is shorter though15:34
krotscheckNikitaKonovalov: Do we care about keeping our calls consistent in our codebase?15:35
* krotscheck doesn’t care that much.15:35
NikitaKonovalovme neither, but what I care about is make sure that the correct code is set everywhere15:36
NikitaKonovalovthat's why I did that NotFound patch and delete15:36
NikitaKonovalovdelete handling I mean15:36
krotscheckNikitaKonovalov: Makes sense. I’ll go in and +2 that patch15:36
NikitaKonovalovthere are also a few places where something like response.status_code=400; return response; I'll fix those too.15:37
krotscheckStoryboard meeting in #openstack-meeting-316:00
*** tteggel_ is now known as tteggel16:04
krotscheckArgh, not enough time for technical discussions :/17:00
rcarrillocruzheh17:00
rcarrillocruzso yeah17:00
rcarrillocruztwo use cases17:00
rcarrillocruz'reconnect' and 'replay'17:00
rcarrillocruzfirst for ocassional and short connection drops17:01
rcarrillocruzwe can leave consumer queues to stay live for 2-5minutes17:01
*** aripinen has quit IRC17:02
rcarrillocruz'replay' use case i don't think we should use amqp queues. We should rather handle that in the backend with SQL by querying the events table... and make sure the events shown back to the client appear in the same format as normal rabbitmq events17:02
rcarrillocruzso the client doesn't see any difference17:02
krotscheckIs replay part of the pubsub spec?17:03
* rcarrillocruz searching the spec...17:06
krotscheckAFK for an hour or so, have to get my run in and get to the office.17:06
rcarrillocruzit is17:07
rcarrillocruzhttps://review.openstack.org/#/c/105252/6/specs/storyboard_automated_pub_sub.rst17:07
rcarrillocruzline 24017:07
*** wuhg has quit IRC17:09
*** coolsvap is now known as coolsvap|afk17:12
*** MaxV has quit IRC17:30
*** jcoufal_ has quit IRC17:46
*** coolsvap|afk is now known as coolsvap17:52
*** reed has joined #storyboard19:01
*** coolsvap is now known as coolsvap|afk19:36
*** MaxV has joined #storyboard19:51
openstackgerritMichael Krotscheck proposed openstack-infra/storyboard: Explicit Hook Priorities  https://review.openstack.org/15225319:51
openstackgerritMichael Krotscheck proposed openstack-infra/storyboard: Explicit Hook Priorities  https://review.openstack.org/15225319:54
openstackgerritMerged openstack-infra/storyboard: Delete created_at and updated_at fields from requests  https://review.openstack.org/15164119:55
*** alexismonville has quit IRC20:23
*** MaxV has quit IRC20:36
*** cody-somerville has joined #storyboard21:15
*** cody-somerville has quit IRC21:15
*** cody-somerville has joined #storyboard21:15
*** cody-somerville has quit IRC21:39
*** mrmartin has quit IRC21:51
*** jtomasek has quit IRC22:24
*** greghaynes has joined #storyboard22:25
openstackgerritMichael Krotscheck proposed openstack-infra/storyboard: Explicit Hook Priorities  https://review.openstack.org/15225322:38
openstackgerritMichael Krotscheck proposed openstack-infra/storyboard: Pass the old entity values in the NotificationHook  https://review.openstack.org/15164522:38
openstackgerritMichael Krotscheck proposed openstack-infra/storyboard: API events now include resource before/after state.  https://review.openstack.org/15231822:38
krotscheckrcarrillocruz: ^^ I made a couple of changes to your patch. I rebased it on top of the hook priority patch that I put out, and pulled the mapping logic into a reusable internal method so it can be used in before() and in after()22:38
greghaynespecan hook priorities are wierd22:58
greghayneskrotscheck: is the idea of them to basically get a hook order within one of the possible hook states22:59
greghayneslike an ordering from within on_before22:59
*** reed has quit IRC23:00
krotscheckgreghaynes: Yeah, especially since you can have hooks in controllers, at the app level, etc etc.23:00
greghaynescool. Another Q - whats your dev setup like?23:01
greghaynesoh, youre a mac user arent you ;)23:03
greghaynesaye, tox py3* test isnt happy because Mysql-Python23:08
krotscheckMine?23:25
krotscheckYep23:25
krotscheckgreghaynes: Is there a reasonably clean path to get us to 3*? I’m unfamiliar with the migration.23:26
greghayneskrotscheck: yea, review inbound23:26
greghayneskrotscheck: well, for the mysql fix23:26
krotscheckOh, nice.23:26
greghayneswhich is just to juse pymysql23:26
krotscheckgreghaynes: Implications?23:27
* krotscheck seems to remember a reason we used mysql-python, but can’t remember specifics.23:28
greghayneskrotscheck: mostly positive implications. really the only downside is pymysql is slightly slower, but no in a way that should matter23:28
greghaynesits basically just a pure python implementation23:29
greghaynesand a drop in replacement23:29
krotscheckgreghaynes: Oh, hah. Yeah, well, the major issue in our DB interaction speed is that every query gets its own connection. This might just make it painful enough to force someone to fix that.23:29
greghaynesfun23:30
greghaynesif it comes up I might poke at it :)23:30
*** cody-somerville has joined #storyboard23:34
openstackgerritgreghaynes proposed openstack-infra/storyboard: Switch from mysql-python to PyMySQL  https://review.openstack.org/15233923:37
*** mase_x200 has joined #storyboard23:40
krotscheckgreghaynes: Is that patch going to require updates to the configuration files on deployed instances?23:45
krotschecki.e. will I have to update the puppet module?23:45
greghaynesthat is a good question23:45
greghaynesI would say very likely23:45
greghayneswell, actually, I dont think 'require'23:46
greghaynesif youre using the same connect string as before and you have mysql-python installed it should work the same as before23:46
greghaynesWe should probably include a deprecated warning or somesuch though23:47
*** gforcada_ has joined #storyboard23:48
greghayneskrotscheck: where does the puppet code live for the deployed instance?23:48
gforcada_hi all, is ther any sysamdin around? I'm trying to log in but I keep getting a "500 Internal Server Error"23:49
gforcada_should I just wait until tomorrow?23:49
krotscheckhiya23:51
krotscheckgforcada_: Let me check for ya.23:51
gforcada_krotscheck: thanks!23:51
krotscheckgforcada_: I can repro. Checking localhost.23:52
krotscheckgforcada_: Broken on master, working on a patch.23:53
krotscheckgreghaynes: https://review.openstack.org/#/q/status:open+project:openstack-infra/puppet-storyboard,n,z23:53
gforcada_krotscheck: thanks a lot, will wait for the fix then23:57

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