Monday, 2015-01-19

*** salv-orl_ has joined #openstack-meeting-300:22
*** salv-orlando has quit IRC00:25
*** emagana has joined #openstack-meeting-300:51
*** emagana has quit IRC00:53
*** emagana has joined #openstack-meeting-300:54
*** emagana has quit IRC00:58
*** salv-orl_ has quit IRC00:59
*** seizadi has joined #openstack-meeting-301:04
*** qwebirc77639 has joined #openstack-meeting-301:06
*** tomoe has joined #openstack-meeting-301:09
*** tomoe has quit IRC01:10
*** tomoe has joined #openstack-meeting-301:10
*** tomoe has quit IRC01:12
*** julim has joined #openstack-meeting-301:35
*** julim has quit IRC01:40
*** stanzgy has joined #openstack-meeting-301:45
*** salv-orlando has joined #openstack-meeting-302:00
*** salv-orlando has quit IRC02:06
*** stanzgy has quit IRC02:07
*** stanzgy has joined #openstack-meeting-302:07
*** HenryG has joined #openstack-meeting-302:44
*** asahlin_ has quit IRC02:44
*** asahlin has joined #openstack-meeting-302:46
*** carl_baldwin has joined #openstack-meeting-302:50
*** salv-orlando has joined #openstack-meeting-302:53
*** salv-orlando has quit IRC02:54
*** carl_baldwin has quit IRC03:04
*** carl_baldwin has joined #openstack-meeting-303:07
*** carl_baldwin has quit IRC03:08
*** seizadi has quit IRC03:12
*** carl_baldwin has joined #openstack-meeting-303:22
*** carl_baldwin has quit IRC03:48
*** carl_baldwin has joined #openstack-meeting-303:49
*** coolsvap|afk is now known as coolsvap03:56
*** ivar-lazzaro has joined #openstack-meeting-303:59
*** carl_baldwin has quit IRC04:05
*** baoli has joined #openstack-meeting-304:06
*** carl_baldwin has joined #openstack-meeting-304:11
*** baoli has quit IRC04:11
*** baoli has joined #openstack-meeting-304:12
*** Longgeek has joined #openstack-meeting-304:15
*** tellesnobrega_ has joined #openstack-meeting-304:16
*** carl_baldwin has quit IRC04:17
*** tellesnobrega_ has quit IRC04:24
*** pullareddy009 has joined #openstack-meeting-304:27
*** pullareddy009 has left #openstack-meeting-304:31
*** qwebirc77639 has quit IRC04:36
*** eghobo has joined #openstack-meeting-304:39
*** salv-orlando has joined #openstack-meeting-304:43
*** salv-orlando has quit IRC04:50
*** salv-orlando has joined #openstack-meeting-304:56
*** baoli_ has joined #openstack-meeting-304:59
*** baoli has quit IRC04:59
*** armax has joined #openstack-meeting-305:00
*** salv-orlando has quit IRC05:01
*** armax has quit IRC05:14
*** emagana has joined #openstack-meeting-305:34
*** anish has joined #openstack-meeting-305:38
*** anish has left #openstack-meeting-305:38
*** emagana has quit IRC05:42
*** amotoki has joined #openstack-meeting-306:00
*** Sukhdev has joined #openstack-meeting-306:05
*** baoli_ has quit IRC06:16
*** Sukhdev has quit IRC06:19
*** Sukhdev has joined #openstack-meeting-306:22
*** eghobo has quit IRC06:37
*** Sukhdev has quit IRC06:42
*** Sukhdev has joined #openstack-meeting-306:45
*** salv-orlando has joined #openstack-meeting-306:51
*** belmoreira has joined #openstack-meeting-306:57
*** salv-orlando has quit IRC06:57
*** mrunge has joined #openstack-meeting-307:08
*** mrunge has quit IRC07:08
*** mrunge has joined #openstack-meeting-307:08
*** mrmartin has joined #openstack-meeting-307:17
*** Sukhdev has quit IRC07:19
*** salv-orlando has joined #openstack-meeting-307:20
*** salv-orlando has quit IRC07:21
*** salv-orlando has joined #openstack-meeting-307:22
*** Sukhdev has joined #openstack-meeting-307:22
*** pkoniszewski has joined #openstack-meeting-307:28
*** scheuran has joined #openstack-meeting-307:32
*** Sukhdev has quit IRC07:40
*** baoli has joined #openstack-meeting-307:48
*** baoli has quit IRC07:52
*** sahid has joined #openstack-meeting-308:05
*** wdutch has joined #openstack-meeting-308:21
*** amotoki has quit IRC08:26
*** zz_ttrifonov is now known as ttrifonov08:26
*** amotoki has joined #openstack-meeting-308:33
*** devvesa has joined #openstack-meeting-308:37
*** iovadia has joined #openstack-meeting-308:39
*** iovadia has left #openstack-meeting-308:39
*** gilllliard is now known as gilliard08:43
*** JeanBriceCombebi has joined #openstack-meeting-308:49
*** jcoufal has joined #openstack-meeting-308:51
*** pkarikh has joined #openstack-meeting-308:54
*** bauwser is now known as bauzas09:01
*** MaxV has joined #openstack-meeting-309:01
*** matrohon has joined #openstack-meeting-309:02
*** ttrifonov is now known as zz_ttrifonov09:06
*** zz_ttrifonov is now known as ttrifonov09:12
*** watanabe_isao has quit IRC09:15
*** zz_johnthetubagu is now known as johnthetubaguy09:22
*** eghobo has joined #openstack-meeting-309:22
*** eghobo has quit IRC09:28
*** mrunge has quit IRC09:29
*** mrunge has joined #openstack-meeting-309:36
*** baoli has joined #openstack-meeting-309:37
*** baoli has quit IRC09:42
*** jtomasek has joined #openstack-meeting-309:58
*** belmoreira has quit IRC10:02
*** scheuran has quit IRC10:05
*** pavel_bondar has joined #openstack-meeting-310:13
*** scheuran has joined #openstack-meeting-310:19
*** stanzgy has quit IRC10:55
*** pkoniszewski has quit IRC11:13
*** baoli has joined #openstack-meeting-311:25
*** vkmc_ has joined #openstack-meeting-311:26
*** baoli has quit IRC11:31
*** igordcard has joined #openstack-meeting-311:31
*** scheuran has quit IRC11:42
*** igordcard has quit IRC11:52
*** scheuran has joined #openstack-meeting-311:58
*** pkoniszewski has joined #openstack-meeting-312:16
*** Sukhdev has joined #openstack-meeting-312:16
*** baoli has joined #openstack-meeting-312:26
*** belmoreira has joined #openstack-meeting-312:27
*** belmoreira has quit IRC12:29
*** baoli has quit IRC12:30
*** JeanBriceCombebi has quit IRC12:35
*** rustlebee is now known as russellb12:58
*** Networkn3rd has joined #openstack-meeting-313:08
*** JeanBriceCombebi has joined #openstack-meeting-313:14
*** vkmc_ has quit IRC13:14
*** xuhanp has joined #openstack-meeting-313:23
*** thomasem has joined #openstack-meeting-313:26
*** baoli has joined #openstack-meeting-313:27
*** baoli has quit IRC13:32
*** thomasem has quit IRC13:34
*** thomasem has joined #openstack-meeting-313:34
*** pkoniszewski has quit IRC13:36
*** ozamiatin has quit IRC13:38
*** stanzgy has joined #openstack-meeting-313:48
*** mrunge has quit IRC13:51
*** lblanchard has joined #openstack-meeting-313:55
*** weiting has joined #openstack-meeting-313:56
*** huichun has joined #openstack-meeting-313:56
*** JeanBriceCombebi has quit IRC14:02
*** JeanBriceCombebi has joined #openstack-meeting-314:04
*** huichun has quit IRC14:04
*** julim has joined #openstack-meeting-314:06
*** kchen has joined #openstack-meeting-314:07
*** kchen has left #openstack-meeting-314:07
*** Networkn3rd has quit IRC14:07
*** Networkn3rd has joined #openstack-meeting-314:07
*** huichun has joined #openstack-meeting-314:07
*** julim has quit IRC14:08
*** huichun has quit IRC14:08
*** Sukhdev has quit IRC14:09
*** julim has joined #openstack-meeting-314:11
*** enikanorov has joined #openstack-meeting-314:13
*** stanzgy has quit IRC14:19
*** stanzgy has joined #openstack-meeting-314:19
*** JeanBriceCombebi has quit IRC14:24
*** baoli has joined #openstack-meeting-314:25
*** JeanBriceCombebi has joined #openstack-meeting-314:26
*** peristeri has joined #openstack-meeting-314:27
*** iovadia has joined #openstack-meeting-314:28
*** iovadia has left #openstack-meeting-314:30
*** baoli has quit IRC14:30
*** stanzgy has quit IRC14:37
*** stanzgy has joined #openstack-meeting-314:38
*** wdutch has left #openstack-meeting-314:44
*** VW_ has joined #openstack-meeting-314:52
*** jpomero has joined #openstack-meeting-314:52
*** xuhanp has quit IRC14:53
*** pkoniszewski has joined #openstack-meeting-314:59
*** VW__ has joined #openstack-meeting-315:03
*** VW_ has quit IRC15:04
*** iovadia has joined #openstack-meeting-315:07
*** iovadia has left #openstack-meeting-315:07
*** Networkn3rd has quit IRC15:08
*** sigmavirus24_awa is now known as sigmavirus2415:08
*** Networkn3rd has joined #openstack-meeting-315:08
*** VW__ has quit IRC15:12
*** VW_ has joined #openstack-meeting-315:12
*** igordcard has joined #openstack-meeting-315:20
*** baoli has joined #openstack-meeting-315:26
*** coolsvap is now known as coolsvap|afk15:30
*** jcoufal_ has joined #openstack-meeting-315:31
*** jcoufal has quit IRC15:33
*** jtomasek_ has joined #openstack-meeting-315:38
*** jtomasek_ has quit IRC15:39
*** jtomasek has quit IRC15:39
*** jtomasek has joined #openstack-meeting-315:39
*** yolanda has joined #openstack-meeting-315:41
*** weiting has quit IRC15:49
*** igordcard has quit IRC15:52
*** VW_ has quit IRC15:58
*** VW_ has joined #openstack-meeting-316:00
krotscheck#startmeeting Storyboard16:01
openstackMeeting started Mon Jan 19 16:01:23 2015 UTC and is due to finish in 60 minutes.  The chair is krotscheck. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: Storyboard)"16:01
openstackThe meeting name has been set to 'storyboard'16:01
NikitaKonovalovo/16:01
SergeyLukjanovo/16:01
krotscheckSo, before I post an agenda, what quorum do we actually need?16:02
*** sigmavirus24 has left #openstack-meeting-316:02
*** CTtpollard has joined #openstack-meeting-316:02
krotscheckWe’ve got 3/4 cores here.16:02
krotscheckThat works for me.16:02
krotscheckAgenda: https://wiki.openstack.org/wiki/StoryBoard#Agenda16:03
krotscheck#topic Actions from last week16:03
*** openstack changes topic to "Actions from last week (Meeting topic: Storyboard)"16:03
krotscheckNone!16:03
*** rcarrillocruz has joined #openstack-meeting-316:03
rcarrillocruzhey16:03
rcarrillocruzso16:03
krotscheckHey!16:03
*** jedimike has joined #openstack-meeting-316:03
rcarrillocruzit seems there's a bunch of people off today?16:03
jedimikeo/16:03
rcarrillocruzwasn't aware of US being bank holiday, what is it?16:03
krotscheckrcarrillocruz: There aren’t. ttx is on a plane, that’s the only person we’re missing.16:03
jedimikei'm here, but lagging, builders are here doing things to the house16:04
krotscheckIt’s Martin Luther King day in the U.S.16:04
krotscheck#topic Urgent Items: Truncated OAuth Tokens Work (rcarrillocruz)16:04
*** openstack changes topic to "Urgent Items: Truncated OAuth Tokens Work (rcarrillocruz) (Meeting topic: Storyboard)"16:04
rcarrillocruzah ok16:04
yolandahi16:04
yolandawas in wrong window...16:05
krotscheckrcarrillocruz: Any progress on that?16:05
CTtpollardhi16:05
rcarrillocruznope, haven't looked at it yet, sorry16:06
krotscheckAlrightey, postponed to next week.16:06
krotscheck#topic User Feedback16:06
*** openstack changes topic to "User Feedback (Meeting topic: Storyboard)"16:06
krotscheckAny new user feedback?16:06
krotscheckHonestly, the UI has been pretty stagnant. We’ve got a large backlog of UI issues and I’m still tied up with email :/16:06
CTtpollardmy work allocation for our internal storyboard instance has dried up atm so I don't have any new feedback16:07
krotscheckNo worryes, CTtpollard16:07
krotscheckSo we’ll move on.16:07
krotscheck#topic Discussion Topics16:07
*** openstack changes topic to "Discussion Topics (Meeting topic: Storyboard)"16:07
krotscheckNothing on the agenda, anyone have something they want to discuss?16:07
rcarrillocruzyeah16:07
*** ruhe has joined #openstack-meeting-316:07
krotscheckThe floor is yours.16:08
rcarrillocruzi wanted to show the deferred queue/replay events16:08
rcarrillocruzso, rabbitmq has something called exchange to exchange binding16:08
*** jaypipes has joined #openstack-meeting-316:08
rcarrillocruzi.e., you can bind an exchange to another exchange16:08
krotscheckyep16:08
rcarrillocruzso, in order to have a queue that logs all events (deferred queue for processing) and websocket clients the ability to replay events16:08
rcarrillocruzwe can do something like this:16:09
rcarrillocruzhttp://stackoverflow.com/questions/6148381/rabbitmq-persistent-message-with-topic-exchange16:09
rcarrillocruz(look at the diagram)16:09
rcarrillocruza fanout exchange that we push all events to, and that's abound to a queue that logs ALL events16:09
rcarrillocruzand to another topic exchange, where we create on-demand queues with the given filters (i want just tasks, with id 1 for example)16:10
rcarrillocruzwhat do you think?16:10
rcarrillocruzif a websocket clients triggers 'replay history', we bind the client to the deferred queue16:10
*** Networkn_ has joined #openstack-meeting-316:10
krotscheckI like it. We already have a topic exchange, however the topic format won’t yet allow us to subscribe to specific events.16:10
rcarrillocruzand upon binding, all events are pushed to the client. We could filter on the websocket client that only events meeting a date criteria is shown16:10
krotscheckAll it filters on right now is type.16:11
*** Networkn3rd has quit IRC16:11
rcarrillocruzyeah, that topic format needs to be changed to address the pubsub spec16:11
rcarrillocruzall good then?16:11
NikitaKonovalovrcarrillocruz: is all the history relayed on request?16:12
krotscheckYeah, let’s talk a bit more about that though. We may be able to add some kind of an ack/nack layer to websocket clients so they themselves can manage which events they’ve handled.16:12
NikitaKonovalovit clould be a huge amount of data then16:12
rcarrillocruzNikitaKonovalov: yes, so we need some filtering mechanism, since a 'replay' would contain a param saying 'just replay since day X from time Y'16:12
krotscheckRather than thinking of it from a ‘replay history’ perspective, we could think of it from an atomic level and assert that individual messages were received.16:13
krotscheckThat way we can forget about anything that wasn’t received.16:13
krotscheckSorry16:14
krotscheckThat way we can forget about anything that WAS received.16:14
rcarrillocruzso you mean keeping a list of what's being sent per client connection?16:14
rcarrillocruzso when the client triggers 'replay' we only send what was NOT sent?16:15
krotscheckrcarrillocruz: Well, I say create a persistent queue that collects messages and has some nice high upper bound, one that can store messages through a day or so of zuul being down.16:15
rcarrillocruzah16:15
rcarrillocruzi think rabbitmq queues have a TTL16:15
krotscheckAnd on our version of rabbit that’ll slowly but surely accumulate, until a client connects and starts acknowledging that it’s consuming messages.16:15
rcarrillocruzi.e. keep stuff just for X days16:15
* rcarrillocruz digging16:16
rcarrillocruzhttps://www.rabbitmq.com/extensions.html16:16
krotscheckI figure, that way we make rabbit do all of the history management for us, and don’t have to implement some crazy on-disk cache.16:16
rcarrillocruzcheck for Per-Queue Message TTL16:16
rcarrillocruzyep16:17
rcarrillocruzso let's agree that, sure, a client can trigger replay on-demand, but not since the beginning of mankind16:17
rcarrillocruzjust up to a day or something (obv configurable)16:17
krotscheckrcarrillocruz: I don’t think it’s our job to cache messages in case a client dies horribly.16:18
rcarrillocruznod16:18
krotscheckAll we can reqally guarantee is that we’ll send them every message, and assume they can handle it sanely16:18
krotscheckrcarrillocruz: But with that said, we can definitely create two queues, one as a replay cache and the other as the consumer cache. I’m just concerned about memory16:20
rcarrillocruzyeah, i thought about that also16:20
rcarrillocruzcreating a 'backup' queue upon websocket opened and normal queue is created16:20
rcarrillocruzbut this is twice memory...so if we have a lot of consumers it can quickly kill the instance16:21
NikitaKonovalovwell, then we could keep only a very short history, so that the client can recover from a short outage or a network issue16:21
rcarrillocruzso lean towards having a global replay queue, that is capped (as you say a day or something)16:21
NikitaKonovalovI dont see a case where a client needs events for a whole day16:21
krotscheckI think we have two use cases here. One is replay of already-handled messages, while the other is guaranteed delivery.16:21
rcarrillocruzand it's the client that says 'ok, replay me everthing from last 3 hours)16:21
krotscheckrcarrillocruz: That makes sense.16:22
rcarrillocruzok, i think we have a plan here16:22
rcarrillocruzsecond topic: refresh tokens. The more i think about it, the more I think i should not handle this (i'm only working on the backned thing)16:23
krotscheckrcarrillocruz: If there’s a global replay queue, how do we guarantee that the queue will remain full for other clients, if one client drains it?16:23
rcarrillocruzi think there's a persistence setting for messages for that16:24
krotscheckkk16:24
rcarrillocruzbut it's a good point16:24
rcarrillocruzlet's put a work item for me to have a POC on this idea16:24
krotscheckYou got it16:24
rcarrillocruzand i get back to you next week on the meeting16:24
*** sbalukoff has quit IRC16:24
NikitaKonovalovI thought a persistent qeue means the messages are kept until TTL16:24
krotscheck#action rcarrillocruz Figure out global replay queue edge cases.16:25
krotscheckNikitaKonovalov: I think none of us actually know the actual behavior of the system right now :)16:25
krotscheckrcarrillocruz: So, refresh tokens.16:25
rcarrillocruzheh, indeed16:25
rcarrillocruzso yeah16:25
krotscheck#topic Discussion: Subscription API Refresh Tokens16:25
*** openstack changes topic to "Discussion: Subscription API Refresh Tokens (Meeting topic: Storyboard)"16:25
rcarrillocruzrefresh tokens: i think that should be handled on the frontend, not backend (which is i'm working right now)16:26
rcarrillocruzi've been looking at the code and the refresh code is mainly done in the SB-webclient16:26
krotscheckThat mostly makes sense. What cases are we looking at here?16:26
rcarrillocruzi.e. request contains a refresh token from OAuth endpoint, then token expires, it uses it to get a new token16:26
rcarrillocruzbut nothing on the backend16:26
rcarrillocruzthe backend simply cares about tokens16:27
rcarrillocruzthat is a Bearer , it's on the db storage and it's valid16:27
krotscheckOk, so if I connect with a valid token and get a socket, and then that token expires…16:27
rcarrillocruzthis raises another thing:16:27
rcarrillocruzwe should have a section in the SB webclient for streaming16:27
rcarrillocruz:-)16:27
rcarrillocruzsomething i have no clue thre, not a frontend guy16:27
NikitaKonovalovif a client notices that his token expires soon, it may refresh it through REST and reestablish connection16:27
*** emagana has joined #openstack-meeting-316:28
krotscheckNikitaKonovalov: I agree. What should happen on the socket connection handler serverside though? Should it drop the connection?16:28
rcarrillocruzyolanda: would you work on this with me?16:28
krotscheckIf we have ack/nack on the client, a suddenly dropped connection wouldn’t result in data loss.16:28
zarohi16:28
yolandarcarrillocruz, sure16:28
*** sigmavirus24 has joined #openstack-meeting-316:28
* yolanda cannot attend 100% to this meeting, tied with on-call issues16:29
rcarrillocruzkrotscheck: so the way i have it right now it's to close the websocket if check_access_token is not cool16:29
krotscheckyolanda: NO worries.16:29
rcarrillocruzso, access tokens, but i don't check anything on the backend for refresh tokens16:30
krotscheckAnd then leave it for the webclient to get a good token.16:30
rcarrillocruzyep16:30
NikitaKonovalovkrotscheck: what about sending a warning while a token is valid16:30
rcarrillocruzNikitaKonovalov: good point16:30
NikitaKonovalovif a client does not care it will be disconnected16:30
krotscheckYeah, building a streaming handler for oauth tokens is basically trying to rewrite the oauth spec. Let’s not do that.16:30
rcarrillocruzwe can check for token validity, if it's going to expire we return to the websocket client 'hey, your token is gonna die'16:30
rcarrillocruzbut dunno...i think we should leave that to the frontend16:31
rcarrillocruza web browser websocket thingy can handle this16:31
rcarrillocruzfor command line websocket clients, we can leave that to implementors16:31
NikitaKonovalovrcarrillocruz: sure the consumer should care, not the backend16:31
krotscheckNikitaKonovalov: I don’t even think that’ll be necessary. If a client is disconnected, they’ll try to reconnect, get a 401, trigger the refresh token flow, then reconnect and keep consuming where it left off.16:31
rcarrillocruzi really think it's out of the scope16:31
krotscheckAnd as long as the server queue remembers where we left off, we’re good.16:32
NikitaKonovalovkrotscheck: then let's sent a "Disconnectin for expired token" message before the connection is physically dropped16:32
*** sigmavirus24 has left #openstack-meeting-316:33
NikitaKonovalovso  it would not like an unexpected error16:33
rcarrillocruzkrotscheck: so, that implies we have a grace period for a websocket connection death. meaning, we leave the associated queue open for some time, just in case they reconnect?16:33
krotscheckNikitaKonovalov: That’s fair. That way the APi explains itself.16:33
krotscheckrcarrillocruz: Is that something the client could ask for when they connect?16:34
krotscheckA queue TTL perhaps?16:34
* krotscheck ponders this.16:34
krotscheckThat’s going to get dangerous :/16:34
rcarrillocruzrcarrillocruz: it could be done. When the websocket is opened and the queue is created, we can return to the client 'ok, this is your queue ID'16:34
rcarrillocruzso if the websocket dies, the client at least knows the id to bind to again when the connection is done again...16:34
rcarrillocruzbut we must weigh how long we keep those queues around....to not have leaked queues filling the instance memory...16:35
krotscheckExactly, that’s what worries me.16:36
krotscheckThat would fix our replay queue problem though :)16:36
NikitaKonovalovrcarrillocruz: is it an expensive operation to create a queue, if not than it makes more sense to drop and recreate every time16:36
NikitaKonovalovand reply will help if some messages were missed16:37
rcarrillocruzhmm16:37
rcarrillocruzlet's see if the client drain of the global replay queue is doable16:37
rcarrillocruzif not, we can look at keeping on-demand queues around upon websocket die...16:37
rcarrillocruzdecisions decisions...16:37
rcarrillocruz:-)16:37
krotscheckHave fun with that :). Shall we move on?16:38
*** emagana has quit IRC16:38
*** jaypipes has quit IRC16:38
*** jaypipes_ has joined #openstack-meeting-316:38
rcarrillocruzyeah, sorry to hijack, thx folks!16:38
yolandai wanted feedback for that16:38
yolandahttps://review.openstack.org/14710516:38
*** etoews has joined #openstack-meeting-316:38
yolandaso that's a button to remove all recent events, question raised if there is a need to open a confirmation box or not16:39
* krotscheck doesn’t have an opinion, but can appreciate the frustration of an accidentaly click.16:39
NikitaKonovalovyolanda: what about a confirmation box with "No ask me again option"?16:40
*** emagana has joined #openstack-meeting-316:40
yolandaNikitaKonovalov, and store the pref in user settings?16:40
NikitaKonovalovyes, that's the good place to store options16:40
yolandai was thinking on the modalbox but i also appreciate the situation where you have to clean tons of events and clicking on a modal box all the time16:40
zaroyolanda: maybe work on that as separate change?16:41
yolandazaro, an incremental change looks fine to me , yes16:41
yolandabut i wanted to know feedback of people16:41
krotscheckIt feels like we’re undecided, because none of us know how it would feel to use it.16:42
yolandattx would have an opinion too16:42
*** ivar-laz_ has joined #openstack-meeting-316:42
zaroyeah, that would me my preference.  just merge this one and work on user preference as another change.16:42
yolandaso i can close the change without any confirmation then wait for feedback, sounds good16:43
krotscheckkk16:43
krotscheckI’m ok with that16:43
NikitaKonovalovI'm ok also16:43
yolandai'm on call this week but i'll try to find a hole to finish that16:43
rcarrillocruz+116:43
krotscheckI’ve got a couple of thoughts on improving the event list now that we have story_id’s in all relevant events.16:43
*** amotoki has quit IRC16:43
krotscheckWhat if we group the results we get from the server by story.16:44
krotscheckAnd then say: Here’s all the changes that happened in story X.16:44
krotscheckSomeone commented, someone updated status, etc etc.16:44
NikitaKonovalovkrotscheck: sounds good16:44
krotscheckAnd then only offer one ‘remove’ button which flushes all relevant events.16:44
NikitaKonovalovand ui could have a hide/show toggle so the resuls are displayed in a more compac way then16:45
krotscheckyep16:45
*** ivar-lazzaro has quit IRC16:45
krotscheck12 things happened to story X: (show more)16:45
yolandasounds good to me, yes16:45
krotscheckCoool. Any other discussion topics?16:45
yolandawhat do you think about sorting that? by story id?16:46
yolandaby latest update of some event?16:46
krotscheckI’d start with just sorting by the order they arrive in.16:47
zaroi like that.16:47
NikitaKonovalovyolanda: I think the story with the latest event should be on top, so yes by update times16:47
*** bpokorny has joined #openstack-meeting-316:47
krotscheckWhich is chronologically by date.16:47
zaroi almost want an entire page dedicated to events that i can sort and chop up anyway i want16:47
NikitaKonovalovyep16:47
yolandamakes sense to me, but first have something simple in the dashboard then we could add an independent events screen16:48
krotscheckyep16:48
*** emagana has quit IRC16:48
krotscheckOk, let’s move on to ongoing work.16:48
zaroso why fuss over how it should look or return, just leave it up to user defined.16:49
krotscheckzaro: I guess I don’t understand what you mean by that.16:49
krotscheckBecause to be able to have a user define something, the UI has to be able to render it that way first.16:49
zaroleave as is.  make something that users can sort and filter whichever data they want out of it16:50
*** seizadi has joined #openstack-meeting-316:50
krotscheckzaro: Ok, do you want to take a stab at putting that together?16:51
zarohmm, good point, not atm16:51
krotscheck:D16:51
krotscheckAlright, moving on.16:51
krotscheck#topic Ongoing Work (rcarrillocruz)16:51
*** openstack changes topic to "Ongoing Work (rcarrillocruz) (Meeting topic: Storyboard)"16:51
krotscheckWe more or less covered your stuff in discussion, anything else you want to add?16:51
rcarrillocruzwhat was commented earlier , nothing else, nope16:51
krotscheckCoool16:52
krotscheck#topic Ongoing Work (jedimike)16:52
*** openstack changes topic to "Ongoing Work (jedimike) (Meeting topic: Storyboard)"16:52
krotscheckEaten by bandits?16:52
*** scheuran has quit IRC16:52
krotscheckI guess he’s not here.16:53
krotscheck#topic Ongoing Work (NikitaKonovalov)16:53
*** openstack changes topic to "Ongoing Work (NikitaKonovalov) (Meeting topic: Storyboard)"16:53
krotscheckHow’s the client API coming?16:53
NikitaKonovalovThe Stories/Tasks support is in progress16:53
NikitaKonovalovwhat I've noticed is that we cannot access tasks as a story subresource16:54
NikitaKonovalovso I'm now refactoring API controllers to support both /tasks and /stories/id/tasks enpoints16:54
NikitaKonovalovat lease the API will look more consistent16:55
krotscheckNikitaKonovalov: Ironic does something interesting with that, you might want to talk to that team to see how they have automatically nested resources.16:55
*** emagana has joined #openstack-meeting-316:55
*** iovadia has joined #openstack-meeting-316:55
NikitaKonovalovkrotscheck: we already have this in a lot of places like teams/users and project_groups/projects16:55
NikitaKonovalovand those work fine16:56
krotscheckWorks for me.16:56
NikitaKonovalovso there is no reason why tasks would not work16:56
NikitaKonovalovAlso I've finally updated the tags change16:56
*** baoli has quit IRC16:56
krotscheckThey managed to work some magic where any controller ended up being magically embedded as a subcontroller for every other controller16:56
NikitaKonovalovkrotscheck: I'll have a look16:57
krotscheckYay tags!16:57
*** jcoufal_ has quit IRC16:57
NikitaKonovalovlink for tags https://review.openstack.org/#/c/114217/16:57
*** jcoufal has joined #openstack-meeting-316:57
krotscheckNikitaKonovalov: It might be too much magic.16:57
NikitaKonovalovmost comments resolved I hope16:57
krotscheckYay tags :)16:57
krotscheckIs that all?16:58
NikitaKonovalovall from me16:58
krotscheck#topic Ongoing Work (yolanda)16:58
*** openstack changes topic to "Ongoing Work (yolanda) (Meeting topic: Storyboard)"16:58
*** sarob has joined #openstack-meeting-316:58
*** banix has joined #openstack-meeting-316:58
yolandakrotscheck, sorry, on 2 conversations at same time16:58
*** jtomasek has quit IRC16:59
yolandasomething is on fire here16:59
krotscheckOk, we’ll let you pass then :)16:59
krotscheck#topic Ongoing Work (krotscheck)16:59
*** openstack changes topic to "Ongoing Work (krotscheck) (Meeting topic: Storyboard)"16:59
krotscheckI’ve been working on various utilities necessary for email & simplification.16:59
*** emagana has quit IRC16:59
krotscheckThe email templateing engine is up, and I’ve written a new, tested algorithm to evaluate the correct list of subscribers for a given resource.16:59
krotscheckI’ve also got a new UI where you can actually see which story a given comment was left on.17:00
krotscheckSmall change, but omg so much better.17:00
krotscheckAnyway, my next big push is going to be to build an email outbox handler that just sends emails.17:01
krotscheckAfter that I’ll build the digest and the individual email consumers.17:01
krotscheckAnd now we’re out of time.17:01
krotscheckDOH17:01
krotscheckThanks everyone!17:01
krotscheck#endmeeting17:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:01
rcarrillocruzthx folks17:01
openstackMeeting ended Mon Jan 19 17:01:55 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:01
*** emagana has joined #openstack-meeting-317:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/storyboard/2015/storyboard.2015-01-19-16.01.html17:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/storyboard/2015/storyboard.2015-01-19-16.01.txt17:01
openstackLog:            http://eavesdrop.openstack.org/meetings/storyboard/2015/storyboard.2015-01-19-16.01.log.html17:02
*** rcarrillocruz has left #openstack-meeting-317:02
*** amotoki has joined #openstack-meeting-317:02
*** ttrifonov is now known as zz_ttrifonov17:02
*** iovadia has left #openstack-meeting-317:04
*** JeanBriceCombebi has quit IRC17:04
*** iovadia has joined #openstack-meeting-317:05
*** CTtpollard has left #openstack-meeting-317:05
*** JeanBriceCombebi has joined #openstack-meeting-317:07
*** coolsvap|afk is now known as coolsvap17:10
*** seizadi has quit IRC17:11
*** jaypipes_ is now known as jaypipes17:13
*** pkoniszewski has quit IRC17:13
*** ivar-laz_ has quit IRC17:13
*** armax has joined #openstack-meeting-317:15
*** armax has quit IRC17:17
*** devvesa has quit IRC17:19
*** eghobo has joined #openstack-meeting-317:20
*** iovadia has quit IRC17:21
*** sahid has quit IRC17:24
*** jaypipes has quit IRC17:25
*** MaxV has quit IRC17:28
*** jaypipes has joined #openstack-meeting-317:35
*** armax has joined #openstack-meeting-317:44
*** ruhe has left #openstack-meeting-317:45
*** etoews has quit IRC17:46
*** etoews has joined #openstack-meeting-317:46
*** carl_baldwin has joined #openstack-meeting-317:49
*** yamahata has joined #openstack-meeting-317:51
*** amotoki has quit IRC17:51
*** sunny has joined #openstack-meeting-317:54
*** carl_baldwin has quit IRC17:54
*** Sukhdev has joined #openstack-meeting-317:55
*** baoli has joined #openstack-meeting-317:57
*** matrohon has quit IRC17:58
*** sarob has quit IRC18:01
*** baoli has quit IRC18:01
*** s3wong has joined #openstack-meeting-318:02
*** MaxV has joined #openstack-meeting-318:08
*** sunny has quit IRC18:09
*** tellesnobrega_ has joined #openstack-meeting-318:10
*** Networkn_ has quit IRC18:11
*** Networkn3rd has joined #openstack-meeting-318:11
*** jcoufal_ has joined #openstack-meeting-318:14
*** sunny has joined #openstack-meeting-318:14
*** carl_baldwin has joined #openstack-meeting-318:15
*** eghobo has quit IRC18:15
*** jcoufal has quit IRC18:17
*** ivar-lazzaro has joined #openstack-meeting-318:18
*** eghobo has joined #openstack-meeting-318:18
*** ivar-lazzaro has quit IRC18:20
*** ivar-lazzaro has joined #openstack-meeting-318:21
*** bpokorny_ has joined #openstack-meeting-318:29
*** jcoufal_ has quit IRC18:30
*** bpokorny has quit IRC18:32
*** sunny has quit IRC18:34
*** bpokorny has joined #openstack-meeting-318:35
*** nelsnelson has joined #openstack-meeting-318:35
*** sunny has joined #openstack-meeting-318:35
*** nelsnels_ has joined #openstack-meeting-318:37
*** bpokorny_ has quit IRC18:38
*** nelsnelson has quit IRC18:40
*** bpokorny_ has joined #openstack-meeting-318:44
*** carl_baldwin has quit IRC18:45
*** sunny has quit IRC18:47
*** Longgeek has quit IRC18:47
*** bpokorny has quit IRC18:47
*** sreshetnyak has quit IRC18:47
*** coolsvap is now known as coolsvap|afk18:49
*** baoli has joined #openstack-meeting-318:58
*** baoli has quit IRC19:02
*** sunny has joined #openstack-meeting-319:03
*** marcelodieder has joined #openstack-meeting-319:20
*** sbalukoff has joined #openstack-meeting-319:21
*** marcelodieder has quit IRC19:22
*** johnthetubaguy is now known as zz_johnthetubagu19:25
*** stanzgy has quit IRC19:27
*** Rockyg has joined #openstack-meeting-319:28
*** Rockyg has quit IRC19:29
*** Rockyg has joined #openstack-meeting-319:29
*** etoews has quit IRC19:33
*** amotoki has joined #openstack-meeting-319:40
*** tellesnobrega_ has quit IRC19:41
*** amotoki has quit IRC19:44
*** tellesnobrega_ has joined #openstack-meeting-319:54
*** Sukhdev has quit IRC19:55
*** matrohon has joined #openstack-meeting-319:55
*** Networkn3rd has quit IRC20:05
*** Networkn3rd has joined #openstack-meeting-320:05
*** Networkn3rd has quit IRC20:05
*** Networkn3rd has joined #openstack-meeting-320:06
*** carl_baldwin has joined #openstack-meeting-320:09
*** jedimike has quit IRC20:10
*** pavel_bondar has quit IRC20:17
*** sunny has quit IRC20:18
*** isviridov has quit IRC20:18
*** isviridov has joined #openstack-meeting-320:19
*** sarob has joined #openstack-meeting-320:21
*** Rockyg has quit IRC20:25
*** sunny has joined #openstack-meeting-320:28
*** etoews has joined #openstack-meeting-320:29
*** sarob has quit IRC20:37
*** jaypipes has quit IRC20:38
*** amotoki has joined #openstack-meeting-320:41
*** tellesnobrega_ has quit IRC20:42
*** amotoki has quit IRC20:46
*** nati_ueno has joined #openstack-meeting-320:47
*** baoli has joined #openstack-meeting-320:47
*** amotoki has joined #openstack-meeting-320:48
*** matrohon has quit IRC20:48
*** sarob has joined #openstack-meeting-320:48
*** matrohon has joined #openstack-meeting-320:49
*** jaypipes has joined #openstack-meeting-320:50
*** baoli has quit IRC20:52
*** marg7175 has joined #openstack-meeting-320:52
*** sarob has quit IRC20:53
*** JeanBriceCombebi has quit IRC20:54
*** JeanBriceCombebi has joined #openstack-meeting-320:56
*** sunny has quit IRC20:57
*** cpallares has joined #openstack-meeting-321:01
*** cpallares has left #openstack-meeting-321:02
*** VW_ has quit IRC21:03
*** VW_ has joined #openstack-meeting-321:04
*** VW_ has quit IRC21:04
*** mrmartin has quit IRC21:04
*** nati_ueno has quit IRC21:08
*** sarob has joined #openstack-meeting-321:08
*** nati_ueno has joined #openstack-meeting-321:09
*** VW_ has joined #openstack-meeting-321:09
*** baoli has joined #openstack-meeting-321:10
*** sarob has quit IRC21:13
*** nati_ueno has quit IRC21:13
*** carl_baldwin has quit IRC21:15
*** tellesnobrega_ has joined #openstack-meeting-321:16
*** MaxV has quit IRC21:19
*** jaypipes has quit IRC21:32
*** julim has quit IRC21:32
*** Sukhdev has joined #openstack-meeting-321:34
*** Networkn3rd has quit IRC21:38
*** matrohon has quit IRC21:39
*** jaypipes has joined #openstack-meeting-321:43
*** peristeri has quit IRC21:45
*** banix has quit IRC21:45
*** baoli has joined #openstack-meeting-321:48
*** lsmola_ has quit IRC21:55
*** sunny has joined #openstack-meeting-321:58
*** jaypipes has quit IRC21:58
*** sunny has quit IRC22:03
*** lsmola_ has joined #openstack-meeting-322:08
*** sarob has joined #openstack-meeting-322:10
*** sunny has joined #openstack-meeting-322:14
*** sarob has quit IRC22:14
*** stanzgy has joined #openstack-meeting-322:23
*** etoews has quit IRC22:26
*** stanzgy has quit IRC22:28
*** VW_ has quit IRC22:28
*** lblanchard has quit IRC22:36
*** amotoki has quit IRC22:36
*** VW_ has joined #openstack-meeting-322:40
*** sunny has quit IRC22:40
*** sunny_ has joined #openstack-meeting-322:40
*** sunny_ has quit IRC23:05
*** tellesnobrega_ has quit IRC23:12
*** sunny_ has joined #openstack-meeting-323:12
*** akira-y has joined #openstack-meeting-323:13
*** tellesnobrega_ has joined #openstack-meeting-323:17
*** akira-y has quit IRC23:18
*** mwagner_lap has quit IRC23:18
*** akira-y has joined #openstack-meeting-323:18
*** akira-y has quit IRC23:23
*** jpomero has quit IRC23:26
*** VW_ has quit IRC23:27
*** s3wong has quit IRC23:29
*** s3wong has joined #openstack-meeting-323:30
*** s3wong has quit IRC23:30
*** watanabe_isao has joined #openstack-meeting-323:30
*** Sukhdev has quit IRC23:33
*** seizadi has joined #openstack-meeting-323:38
*** sarob has joined #openstack-meeting-323:41
*** sarob has quit IRC23:45
*** sarob has joined #openstack-meeting-323:50
*** armax has quit IRC23:54
*** sarob has quit IRC23:55
*** sunny_ has quit IRC23:56
*** thomasem has quit IRC23:58

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