Monday, 2015-01-26

*** banix has joined #openstack-meeting-300:07
*** sunny_ has joined #openstack-meeting-300:17
*** sunny__ has joined #openstack-meeting-300:19
*** sunny_ has quit IRC00:19
*** sunny__ has quit IRC00:23
*** xuhanp has quit IRC00:36
*** banix has quit IRC00:39
*** banix has joined #openstack-meeting-300:40
*** sbalukoff has joined #openstack-meeting-300:43
*** mwagner_lap has joined #openstack-meeting-300:47
*** banix has quit IRC00:47
*** lazy_prince has quit IRC00:52
*** marg7175 has quit IRC00:53
*** killer_prince has joined #openstack-meeting-300:53
*** killer_prince is now known as lazy_prince00:54
*** seizadi has quit IRC01:03
*** MaxV has joined #openstack-meeting-301:13
*** yamamoto_ has joined #openstack-meeting-301:18
*** MaxV has quit IRC01:18
*** sunny_ has joined #openstack-meeting-301:20
*** lazy_prince has quit IRC01:23
*** sunny_ has quit IRC01:24
*** killer_prince has joined #openstack-meeting-301:24
*** killer_prince is now known as lazy_prince01:25
*** lazy_prince has quit IRC01:29
*** killer_prince has joined #openstack-meeting-301:30
*** killer_prince is now known as lazy_prince01:30
*** banix has joined #openstack-meeting-301:37
*** yamahata has joined #openstack-meeting-301:41
*** lazy_prince has quit IRC01:57
*** killer_prince has joined #openstack-meeting-301:58
*** killer_prince is now known as lazy_prince01:59
*** etoews has joined #openstack-meeting-302:00
*** etoews has quit IRC02:04
*** Networkn3rd has joined #openstack-meeting-302:08
*** rcleere is now known as rcleere_away02:11
*** Guest18013 is now known as b3nt_pin02:14
*** rcleere_away is now known as rcleere02:14
*** etoews has joined #openstack-meeting-302:16
*** sunny_ has joined #openstack-meeting-302:16
*** sunny_ has quit IRC02:20
*** Networkn3rd has quit IRC02:22
*** rcleere is now known as rcleere_away02:26
*** VW_ has joined #openstack-meeting-302:29
*** alexpilotti has joined #openstack-meeting-302:33
*** seizadi has joined #openstack-meeting-302:34
*** marg7175 has joined #openstack-meeting-302:36
*** mestery has joined #openstack-meeting-302:40
*** lazy_prince has quit IRC02:44
*** killer_prince has joined #openstack-meeting-302:46
*** killer_prince is now known as lazy_prince02:47
*** seizadi has quit IRC02:59
*** MaxV has joined #openstack-meeting-303:02
*** carl_baldwin has joined #openstack-meeting-303:06
*** MaxV has quit IRC03:07
*** lazy_prince has quit IRC03:07
*** killer_prince has joined #openstack-meeting-303:10
*** killer_prince is now known as lazy_prince03:10
*** banix has quit IRC03:13
*** lazy_prince has quit IRC03:15
*** killer_prince has joined #openstack-meeting-303:17
*** killer_prince is now known as lazy_prince03:17
*** banix has joined #openstack-meeting-303:21
*** etoews_ has joined #openstack-meeting-303:23
*** etoews has quit IRC03:23
*** MaxV has joined #openstack-meeting-303:25
*** alexpilotti has quit IRC03:27
*** etoews_ has quit IRC03:28
*** MaxV has quit IRC03:30
*** yamahata has quit IRC03:34
*** dboik has joined #openstack-meeting-303:40
*** baoli has joined #openstack-meeting-303:52
*** etoews has joined #openstack-meeting-303:53
*** amotoki has joined #openstack-meeting-303:53
*** etoews has quit IRC03:58
*** julim_ has quit IRC04:01
*** lazy_prince has quit IRC04:03
*** killer_prince has joined #openstack-meeting-304:05
*** killer_prince is now known as lazy_prince04:05
*** dboik has quit IRC04:10
*** dboik has joined #openstack-meeting-304:15
*** rcleere_away is now known as rcleere04:19
*** lazy_prince has quit IRC04:20
*** killer_prince has joined #openstack-meeting-304:21
*** killer_prince is now known as lazy_prince04:22
*** mattgriffin has joined #openstack-meeting-304:23
*** Longgeek has joined #openstack-meeting-304:24
*** mattgriffin has quit IRC04:26
*** seizadi has joined #openstack-meeting-304:29
*** banix has quit IRC04:40
*** banix has joined #openstack-meeting-304:41
*** Longgeek_ has joined #openstack-meeting-304:47
*** carl_baldwin has quit IRC04:50
*** Longgeek has quit IRC04:50
*** carl_baldwin has joined #openstack-meeting-304:52
*** banix has quit IRC04:57
*** marg7175 has quit IRC05:09
*** baoli has quit IRC05:10
*** Networkn3rd has joined #openstack-meeting-305:23
*** seizadi has quit IRC05:25
*** Networkn3rd has quit IRC05:27
*** rcleere is now known as rcleere_away05:30
*** lazy_prince has quit IRC05:30
*** killer_prince has joined #openstack-meeting-305:31
*** killer_prince is now known as lazy_prince05:31
*** VW_ has quit IRC05:33
*** rcleere_away is now known as rcleere05:47
*** dboik has quit IRC05:59
*** sbalukoff has quit IRC06:09
*** rcleere is now known as rcleere_away06:11
*** stanzgy_ has joined #openstack-meeting-306:13
*** stanzgy has quit IRC06:17
*** jcoufal has joined #openstack-meeting-306:19
*** carl_baldwin has quit IRC06:21
*** lazy_prince has quit IRC06:44
*** killer_prince has joined #openstack-meeting-306:46
*** killer_prince is now known as lazy_prince06:46
*** dboik has joined #openstack-meeting-307:00
*** dboik has quit IRC07:04
*** mrunge has joined #openstack-meeting-307:08
*** marg7175 has joined #openstack-meeting-307:10
*** marg7175 has quit IRC07:14
*** stanzgy has joined #openstack-meeting-307:18
*** salv-orlando has joined #openstack-meeting-307:20
*** mrmartin has joined #openstack-meeting-307:20
*** stanzgy_ has quit IRC07:20
*** sbalukoff has joined #openstack-meeting-307:23
*** jtomasek has joined #openstack-meeting-307:27
*** amotoki_ has joined #openstack-meeting-307:39
*** amotoki has quit IRC07:39
*** evgenyf has joined #openstack-meeting-307:40
*** scheuran has joined #openstack-meeting-307:41
*** MaxV has joined #openstack-meeting-307:53
*** belmoreira has joined #openstack-meeting-307:55
*** dboik has joined #openstack-meeting-308:01
*** devvesa has joined #openstack-meeting-308:03
*** iovadia has joined #openstack-meeting-308:03
*** matrohon has joined #openstack-meeting-308:05
*** dboik has quit IRC08:06
*** MaxV has quit IRC08:07
*** MaxV has joined #openstack-meeting-308:08
*** salv-orlando has quit IRC08:11
*** sahid has joined #openstack-meeting-308:11
*** safchain has joined #openstack-meeting-308:12
*** MaxV has quit IRC08:14
*** marg7175 has joined #openstack-meeting-308:17
*** pkoniszewski has joined #openstack-meeting-308:18
*** marg7175 has quit IRC08:19
*** marg7175 has joined #openstack-meeting-308:19
*** marg7175 has quit IRC08:24
*** marg7175_ has joined #openstack-meeting-308:24
*** pkarikh has joined #openstack-meeting-308:25
*** marg7175_ has quit IRC08:29
*** sergef has joined #openstack-meeting-308:35
*** watanabe_isao has quit IRC08:37
*** marg7175 has joined #openstack-meeting-308:39
*** pkoniszewski has quit IRC08:47
*** obondarev has joined #openstack-meeting-308:49
*** MaxV has joined #openstack-meeting-308:49
*** obondarev has quit IRC08:51
*** ilyashakhat has joined #openstack-meeting-309:02
*** dboik has joined #openstack-meeting-309:03
*** dboik has quit IRC09:08
*** salv-orlando has joined #openstack-meeting-309:11
*** obondarev has joined #openstack-meeting-309:11
*** JeanBriceCombebi has joined #openstack-meeting-309:13
*** salv-orlando has quit IRC09:16
*** JeanBriceCombebi has quit IRC09:19
*** JeanBriceCombebi has joined #openstack-meeting-309:21
*** Guest66252 is now known as d0ugal09:22
*** d0ugal has quit IRC09:23
*** d0ugal has joined #openstack-meeting-309:23
*** tteggel_ is now known as tteggel09:26
*** tteggel has quit IRC09:26
*** tteggel has joined #openstack-meeting-309:26
*** Longgeek has joined #openstack-meeting-309:30
*** Longgeek_ has quit IRC09:33
*** bradjones has joined #openstack-meeting-309:39
*** yamamoto_ has quit IRC09:41
*** Adri2000 has quit IRC09:56
*** Adri2000 has joined #openstack-meeting-309:58
*** scheuran has quit IRC10:02
*** dboik has joined #openstack-meeting-310:04
*** amotoki_ has quit IRC10:06
*** marg7175 has quit IRC10:08
*** dboik has quit IRC10:09
*** marg7175 has joined #openstack-meeting-310:09
*** scheuran has joined #openstack-meeting-310:17
*** salv-orlando has joined #openstack-meeting-310:19
*** scheuran has quit IRC10:22
*** salv-orlando has quit IRC10:23
*** igordcard has joined #openstack-meeting-310:27
*** scheuran has joined #openstack-meeting-310:38
*** sergef has quit IRC10:47
*** sergef has joined #openstack-meeting-310:47
*** stanzgy has quit IRC10:55
*** evgenyf has quit IRC11:25
*** salv-orlando has joined #openstack-meeting-311:35
*** salv-orlando has quit IRC11:39
*** mwagner_lap has quit IRC11:43
*** tellesnobrega_ has joined #openstack-meeting-311:54
*** gillllliard is now known as gilliard12:03
*** akamyshnikova has joined #openstack-meeting-312:08
*** tellesnobrega_ has quit IRC12:43
*** sandr8 has joined #openstack-meeting-312:50
*** salv-orlando has joined #openstack-meeting-312:50
*** redrobot has quit IRC12:51
*** NikitaKonovalov has quit IRC12:51
*** devvesa_ has joined #openstack-meeting-312:51
*** SergeyLukjanov has quit IRC12:51
*** SergeyLukjanov has joined #openstack-meeting-312:52
*** sandr8_ has quit IRC12:52
*** redrobot has joined #openstack-meeting-312:53
*** NikitaKonovalov has joined #openstack-meeting-312:53
*** redrobot is now known as Guest3647312:53
*** devvesa has quit IRC12:54
*** salv-orlando has quit IRC12:55
*** mwagner_lap has joined #openstack-meeting-313:02
*** alexpilotti has joined #openstack-meeting-313:03
*** dboik has joined #openstack-meeting-313:07
*** dboik has quit IRC13:12
*** devvesa_ has quit IRC13:14
*** devvesa has joined #openstack-meeting-313:14
*** ff has joined #openstack-meeting-313:24
*** thomasem has joined #openstack-meeting-313:25
*** wojdev has joined #openstack-meeting-313:30
*** yapeng has quit IRC13:31
*** thomasem has quit IRC13:32
*** thomasem has joined #openstack-meeting-313:32
*** tellesnobrega_ has joined #openstack-meeting-313:34
*** baoli has joined #openstack-meeting-313:39
*** dboik has joined #openstack-meeting-314:00
*** baoli has quit IRC14:00
*** baoli has joined #openstack-meeting-314:01
*** lazy_prince has quit IRC14:03
*** killer_prince has joined #openstack-meeting-314:05
*** killer_prince is now known as lazy_prince14:05
*** julim has joined #openstack-meeting-314:10
*** tellesnobrega_ has quit IRC14:11
*** victor_lowther has quit IRC14:14
*** tellesnobrega_ has joined #openstack-meeting-314:14
*** victor_lowther has joined #openstack-meeting-314:15
*** jraim has quit IRC14:15
*** jraim has joined #openstack-meeting-314:15
*** tellesnobrega_ has quit IRC14:21
*** tellesnobrega_ has joined #openstack-meeting-314:21
*** rcleere_away is now known as rcleere14:22
*** peristeri has joined #openstack-meeting-314:27
*** ff has quit IRC14:27
*** VW_ has joined #openstack-meeting-314:31
*** lblanchard has joined #openstack-meeting-314:33
*** wojdev has quit IRC14:35
*** mattfarina has joined #openstack-meeting-314:36
*** dboik has quit IRC14:37
*** xuhanp has joined #openstack-meeting-314:38
*** mattgriffin has joined #openstack-meeting-314:38
*** bknudson has joined #openstack-meeting-314:40
*** dboik has joined #openstack-meeting-314:45
*** dboik has quit IRC14:47
*** dboik has joined #openstack-meeting-314:48
*** jpomero has joined #openstack-meeting-314:49
*** thangp has joined #openstack-meeting-314:54
*** Networkn3rd has joined #openstack-meeting-314:58
*** nelsnelson has joined #openstack-meeting-314:59
*** tellesnobrega_ has quit IRC15:03
*** jgrimm is now known as zz_jgrimm15:04
*** dboik has quit IRC15:06
*** dboik has joined #openstack-meeting-315:08
*** tellesnobrega_ has joined #openstack-meeting-315:09
*** etoews has joined #openstack-meeting-315:10
*** dboik has quit IRC15:10
*** sigmavirus24_awa is now known as sigmavirus2415:12
*** Longgeek has quit IRC15:13
*** dboik has joined #openstack-meeting-315:14
*** yapeng has joined #openstack-meeting-315:20
*** tellesnobrega_ has quit IRC15:20
*** marun has joined #openstack-meeting-315:23
*** yapeng has quit IRC15:25
*** xuhanp has quit IRC15:25
*** banix has joined #openstack-meeting-315:31
*** JeanBriceCombebi has quit IRC15:32
*** JeanBriceCombebi has joined #openstack-meeting-315:34
*** baoli has quit IRC15:41
*** alexpilotti has quit IRC15:51
*** carl_baldwin has joined #openstack-meeting-315:54
*** yolanda has joined #openstack-meeting-315:57
*** lazy_prince has quit IRC15:59
*** killer_prince has joined #openstack-meeting-315:59
*** killer_prince is now known as lazy_prince15:59
krotscheck#startmeeting Storyboard16:00
openstackMeeting started Mon Jan 26 16:00:29 2015 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
*** JeanBriceCombebi has quit IRC16:00
*** openstack changes topic to " (Meeting topic: Storyboard)"16:00
openstackThe meeting name has been set to 'storyboard'16:00
yolandahi16:00
krotscheckAgenda: https://wiki.openstack.org/wiki/StoryBoard#Agenda16:00
krotscheckNo actions from last week.16:00
krotscheck#topic Urgent Items: StoryBoard Validation is broken16:01
*** openstack changes topic to "Urgent Items: StoryBoard Validation is broken (Meeting topic: Storyboard)"16:01
yolandaso that's due to the validation that was merged16:01
krotscheckSo from what I gather, the client is sending data that the app is not passing, yes?16:01
yolandai proposed a revert here16:01
yolandahttps://review.openstack.org/15003516:01
yolandawell, not really that16:01
ttxo/16:01
yolandathe backend is passing that data, it automatically passes date_created, date_updated...16:02
yolandabut then it doesn't accept them on the response16:02
*** CTtpollard has joined #openstack-meeting-316:02
krotscheckRight. And the client doesn’t make assumptions about the data format it gets, it just sends whatever it receives right back.16:02
yolandayep16:02
krotscheckyolanda: Was that a clean revert? As in, no conflicts?16:03
yolandakrotscheck, yes, tests passing and looks fine, no conflict16:03
*** jeblair has joined #openstack-meeting-316:03
NikitaKonovalovkrotscheck: The revert is not merged yet16:03
yolandaneeds to be approved16:04
krotscheckkk16:04
NikitaKonovalovbut I think we can do that right now16:04
krotscheckIs Aleksey here?16:04
*** JeanBriceCombebi has joined #openstack-meeting-316:04
*** banix_ has joined #openstack-meeting-316:04
yolandadon't see him on the channel16:04
*** maurosr- has joined #openstack-meeting-316:04
krotscheckWhat’s his handle? I keep forgetting16:05
yolandathere are 2 points here: the date_created, date_updated, creator_id extra fields sent even from the backend. And we also don't send data properly,as we don't have to send the "id" field on the payload, but on the url, on posts16:05
NikitaKonovalovit should be aripinen16:05
* NikitaKonovalov looking around to find him16:05
krotscheck+216:05
*** vishy has quit IRC16:05
ttx+1/apprved16:05
krotscheckk16:06
ttx+2 I mean16:06
krotscheckCool, it should have recovered by the end of the meeting, we’ll keep an eye on it16:06
*** Guest36473 is now known as redrobot16:06
krotscheckAnything else that needs to be done right now before we move on?16:06
*** vishy has joined #openstack-meeting-316:06
*** zz_jgrimm has quit IRC16:06
yolandavalidation was crashing as well, not sure if related to this as well16:06
yolandaerrors about dupes, minimum length, etc...16:06
*** banix has quit IRC16:06
*** banix_ is now known as banix16:06
krotscheckFun16:07
yolandathis was showing the error on the xhr call but nothing shown on the client16:07
krotscheckHappy monday, everyone :)16:07
krotscheckThat usually indicates a catastrophic error on the server that causes a truncation of the response.16:07
*** maurosr has quit IRC16:07
*** maurosr- is now known as maurosr16:07
krotschecki.e. it never gets CORS headers because everything blew up.16:07
yolandakrotscheck, i saw the response correctly sent by server, a json response telling "xxx is to short", or something like that16:08
krotscheckAlright, I’ll spend today trying to get things stable again, and see where the two aren’t talking to one another.16:08
yolandabut client wasn't showing that16:08
krotscheckhun16:08
krotscheckhun16:08
krotscheckhuhn16:08
yolandabut if we revert the json schema thing, it can be related16:08
*** zz_jgrimm has joined #openstack-meeting-316:08
krotscheck#action krotscheck Get Storyboard back to a happy place.16:08
krotscheckOk, so that just erged, we should see it going in in about 10 minutes or so16:09
*** tellesnobrega_ has joined #openstack-meeting-316:09
krotscheckLet’s be patient and move on.16:09
krotscheck#topic urgent: Auth Tokens validate on truncated tokens16:09
*** openstack changes topic to "urgent: Auth Tokens validate on truncated tokens (Meeting topic: Storyboard)"16:09
krotscheckrcarillocruz was working on that, I seem to recall that it merged.16:09
NikitaKonovalovI've done the fix16:09
NikitaKonovalovso now it should work fine16:09
krotscheckCool16:09
krotscheckMoving on16:09
krotscheckUrgent Items: Working Directory Cron Fail16:10
krotscheckSo this took down storyboard last monday, which required another revert.16:10
krotscheckI’ve since revisited the issue and altered my approach to generating a working directory space.16:10
krotscheckSo that the cron system won’t even start up if it doesn’t have one.16:10
krotscheckPatch is here: https://review.openstack.org/#/c/149454/16:11
krotscheckAnd appears to have +416:11
krotscheckSo we’ll rebase and go from there.16:11
krotscheckAny other urgent items?16:11
yolandaproject groups was broken as well16:11
yolandai did a fix16:11
krotscheckpatch?16:11
yolandahttps://review.openstack.org/15002716:11
krotscheckLooks good.16:12
* NikitaKonovalov needs to check that16:12
krotscheckGImme a sec, going to update the agenda with all the urgent items.16:13
*** lazy_prince has quit IRC16:13
*** killer_prince has joined #openstack-meeting-316:13
*** killer_prince is now known as lazy_prince16:13
krotscheck#topic Urgent: Why All The Explosions16:14
*** openstack changes topic to "Urgent: Why All The Explosions (Meeting topic: Storyboard)"16:14
yolandanice topic :)16:14
*** baoli has joined #openstack-meeting-316:15
yolandai miss an integration test here16:15
yolandasomething to check how changes in the backend afect to the client, and test if all together work16:15
krotscheckOk, server was down twice in two weeks. I don’t feel we need to take drastic action here, but what’s missing going forward?16:15
NikitaKonovalovkrotscheck: I guess it's because running SB locally and in production is a bit different16:15
NikitaKonovalovthe cron failed due to permissions16:15
krotscheckNikitaKonovalov: True. That was definitely the case for working directory.16:15
NikitaKonovalovwe could not predict it locally16:15
krotscheckNikitaKonovalov: But even then I could have taken a different approach that made things not take down the rest of the server.16:16
krotscheckNikitaKonovalov: The validation thing though seems like something we could have done testing for.16:16
yolandakrotscheck, problem i see is that we do tests for the features in backend and for the ones in frontend16:16
yolandabut nothing together16:16
krotscheckRight, no gating.16:16
*** markvoelker has joined #openstack-meeting-316:16
krotscheckAnd the integration tests in the frontend don’t really exist.16:17
yolandabut even if we do tests in the frontend, we are doing that against the master branch16:17
yolandaof the backend16:17
krotscheckThe client gates on the backend. The backend does not gate on the client :/16:17
yolandaa common integration tests run for each feature in the frontend and backend  will make sense16:18
jeblairif you can come up with an integration tests that uses both, i'd be happy to set up the job to correctly do the zuul git checkouts so that things are tested together in the gate16:18
*** lazy_prince has quit IRC16:18
*** mrunge is now known as mrunge_afk16:18
yolandai can take a look at it this week, what do you think that could be a good approach?16:19
krotscheckjeblair: We _sortof_ already have it. That’ll take more work.16:19
krotscheckthe client currently installs the backend to run integration tests against it, but that’s only against master.16:19
*** devvesa has quit IRC16:19
jeblairkrotscheck: which job is that?16:19
krotscheckjeblair: gate-storyboard-webclient-js-test-integration I think16:20
krotscheckIt’s been a year since I et that up though16:20
*** killer_prince has joined #openstack-meeting-316:21
*** killer_prince is now known as lazy_prince16:21
krotscheckyolanda: Want to take that on? Gating our components against each other is going to become important.16:21
jeblairkrotscheck: okay, so probably we just need that job to checkout the zuul refs of both projects then run on changes to both projects; sound right?16:21
*** alexpilotti has joined #openstack-meeting-316:21
yolandakrotscheck, jeblair, i'm happy to doit16:21
krotscheckjeblair: Yep. Right now we use pip though I think. I don’t think it’ll be that simple.16:21
krotscheckAwesome16:22
mrmartinre16:22
krotscheck#action yolanda Figure out how to have our projects gate on each other.16:22
jeblairkrotscheck, yolanda: yeah, there's a thing called zuul-cloner that does what needs to be done for git trees16:22
krotscheckjeblair: Wait, so it can clone the gatekeeper and the keymaster?16:22
jeblairyou do need both16:22
mrmartinguys, what you think about using a storyboard-dev, and do frequent releases to prod only if everything seems to be stable ?16:23
yolandajeblair, i saw that on the zuul code but never used, sounds like a handy tool16:23
krotscheckmrmartin: We’re working on that, actually. The puppet module needs to not default to https, and then we can push it.16:23
krotscheckmrmartin: Want to take a stab at that?16:23
mrmartinwe did something similar for groups portal16:24
jeblairkrotscheck: you intend to stop deploying production cd?16:24
krotscheckjeblair: Eventually. Not yet.16:24
mrmartinthe other side, that you really need to do client - server integration test :)16:25
krotscheckjeblair: Right now we want storyboard-dev so the draft client doesn’t present a security hole.16:25
krotscheckjeblair: Moving from there to adding versioning seems a sane next step, and then we can talk about To-CD-Or-Not-To-CD16:25
krotscheckmrmartin: Yes. That16:26
jeblairkrotscheck: yes, we should talk about it.  i would like to continue doing cd.16:26
krotscheckOk, we’re going off into the weeds right now. The big thing the recent downtimes have revealed is a need to test the client against the api.16:26
krotscheckjeblair: I would too. But I acknowledge that some people get scared when versions update.16:26
krotscheckAnd yolanda has taken responsibility for that, so unless there’s another urgent item, let’s move on.16:27
krotscheckAny other urgent items?16:27
*** marun has quit IRC16:28
yolandawe had enough :)16:28
*** salv-orlando has joined #openstack-meeting-316:28
krotscheckAlllrightey16:28
krotscheck#topic User Feedback16:28
*** openstack changes topic to "User Feedback (Meeting topic: Storyboard)"16:28
krotscheckANything new other than “It’s broken"?16:28
*** ctracey has quit IRC16:29
*** ctracey has joined #openstack-meeting-316:29
*** zz_jgrimm is now known as jgrimm16:30
mrmartinI'm trying to use storyboard, and my largest pain point are the missing email notifications.16:31
krotscheckOk, looks like StoryBoard is healthy again, I was just able to create a story: https://storyboard.openstack.org/#!/story/200013116:31
mrmartinbut I know it is coming :)16:31
krotscheckmrmartin: I’ll talk about that in ongoing work :)16:31
yolandaah krotscheck, we did a fix to create stories before the revert16:31
krotscheckI have a user feedback: There are two yolanda robla’s in storyboard :)16:31
yolandaoh yes16:31
*** SridharRamaswamy has joined #openstack-meeting-316:32
krotscheckI wonder how that would work if there’s more than one john smith16:32
mrmartinhttps://storyboard.openstack.org/#!/project_group/5816:32
mrmartinthis page is listing stories not related to project groups16:32
*** salv-orlando has quit IRC16:33
*** david-ly_ is now known as david-lyle16:33
krotscheckmrmartin: Right, we know about that one.16:33
* krotscheck feels sheeping about not fixing all the client issues :/16:34
krotscheck*sheepish16:34
* krotscheck also wants to write javascript again. It’s been so long!16:34
ttxkrotscheck: I know that feeling. not.16:34
krotscheckOk, so story for my issue: https://storyboard.openstack.org/#!/story/200013216:34
krotscheckSTory for mrmartin: https://storyboard.openstack.org/#!/story/200004316:34
*** armax has joined #openstack-meeting-316:35
krotscheckAnything else?16:35
mrmartinand a UX one: when I select a story from group, what is the proper way to navigate back to stories page?16:35
*** lucasagomes has joined #openstack-meeting-316:35
mrmartinso16:35
mrmartinagain16:35
krotscheckmrmartin: Back arrow?16:36
*** SridharRamaswamy has quit IRC16:36
jeblairkrotscheck: gerrit includes email addresses in mouseover text for user links to help disambiguate.  (to whatever degree that helps)16:36
*** SridharRamaswamy has joined #openstack-meeting-316:36
mrmartinWhen I select a story from a project, how can I navigate back to the project page agian.16:36
mrmartinyeap, back arrow can be an option. don't you plan to implement some breadcrumbs?16:36
yolandaah, jeblair , i just added the same comment16:36
yolandain my case i think it's same user but different openids16:36
krotscheckmrmartin: Breadcrumbs are a difficult question when you navigate to a story that can have N>1 projects it’s associated with.16:37
mrmartinkrotscheck: ok, so now when I click on a project link of a task, it displays the inline editor16:38
yolandaah, that's a thing that needed to be solved16:39
mrmartinI think we want to navigate more often, than edit the project assigned to a task16:39
yolandakrotscheck, mrmartin, we talked about it on prev meetings right?16:39
jeblairmrmartin: i think there may be a story for that...16:39
jeblairyolanda: yes, i think we did16:39
krotscheckYep.16:39
mrmartinok.16:39
jeblairlemme see if i can find it16:39
krotscheckjeblair filed a story.16:40
*** wojdev has joined #openstack-meeting-316:40
jeblairkrotscheck: there's no "stories i filed" page is there? :)16:40
krotscheckjeblair: Nope. User feedback? :)16:40
jeblairkrotscheck: will file a story ;)16:40
krotscheck:D16:40
krotscheckSounds like we have our work cut out for us this week :)16:42
krotscheckAlright, moving on.16:42
krotscheck#topic Discussion Topics.16:42
*** openstack changes topic to "Discussion Topics. (Meeting topic: Storyboard)"16:42
krotscheckAnyone have something big they want to bring up?16:42
krotscheck(Agenda is empty)16:42
*** matrohon has quit IRC16:43
krotscheckAlright, weekly update time!16:44
krotscheck#topic Streaming API16:44
*** openstack changes topic to "Streaming API (Meeting topic: Storyboard)"16:44
krotscheckrcarrillocruz isn’t here, moving on.16:44
krotscheckNeither is jedimike16:44
jeblairmrmartin: https://storyboard.openstack.org/#!/story/200009516:44
yolandalet me ping them16:44
krotscheck#topic Ongoing work (NikitaKonovalov)16:44
jeblairmrmartin: also related https://storyboard.openstack.org/#!/story/17916:44
*** openstack changes topic to "Ongoing work (NikitaKonovalov) (Meeting topic: Storyboard)"16:44
mrmartinjeblair: thanks.16:45
NikitaKonovalovOk16:45
NikitaKonovalovI've finally solved a routing issue for tasks16:45
*** jedimike has joined #openstack-meeting-316:45
NikitaKonovalovwhich now allows a client to do something like story.tasks.list()16:45
jedimikeo/16:45
krotscheckNice!16:46
NikitaKonovalovand get the correct result16:46
krotscheckI really like how that’s coming together.16:46
NikitaKonovalovhttps://review.openstack.org/#/c/150052/ this one is for the backednd16:46
NikitaKonovalovand this is the client https://review.openstack.org/#/c/150067/16:47
krotscheckHrmmmm.....16:47
krotscheckThat would break the search API16:47
krotscheckAnd the criteria listing.16:47
NikitaKonovalovsohuld not  because /tasks still works16:47
krotscheckAhhh, gotcha16:47
NikitaKonovalovnext steps for me adding comments, timeline  to stories in client16:48
NikitaKonovalovthen subscriptions16:48
NikitaKonovalovonce that is complete I'll switch to CLI16:48
krotscheckCool16:49
krotscheck#topic Ongoing Work (jedimike)16:49
*** openstack changes topic to "Ongoing Work (jedimike) (Meeting topic: Storyboard)"16:49
NikitaKonovalovAnd I guess tags are pretty close to getting merged16:49
krotscheckOops, sorry.16:49
krotscheckAccidentally hit return16:49
NikitaKonovalovthat' s all the update actually16:49
krotscheck#topic Ongoing Work (NikitaKonovalov016:49
*** openstack changes topic to "Ongoing Work (NikitaKonovalov0 (Meeting topic: Storyboard)"16:49
krotscheckOk, ok16:50
krotscheck#topic Ongoing Work (jedimike)16:50
*** openstack changes topic to "Ongoing Work (jedimike) (Meeting topic: Storyboard)"16:50
krotscheckHey there! How’s life?16:50
jedimikeI haven't had any time to work on anything but getting our pypimirror and CI working properly again, and I'm back on support again this week, so chances of getting anything done are minimal :(16:50
krotscheckAlright then, moving on.16:50
krotscheck#topic Ongoing Work (yolanda)16:51
*** openstack changes topic to "Ongoing Work (yolanda) (Meeting topic: Storyboard)"16:51
yolandathis is pending from discussion16:51
yolandahttps://review.openstack.org/13779816:51
krotscheckRight!16:52
krotscheckI keep trying to review that.16:52
*** rloo has joined #openstack-meeting-316:52
krotscheckWhat usually happens is I look at it and think: There has _got_ to be a better way to do this, and hten I lose myself in research.16:52
*** ihrachyshka has joined #openstack-meeting-316:53
yolandai feel i miss a bit on the promises, but i didn't find a better way to do it with the current backend16:53
yolandamaybe if we had some backend that returns logged user details and prefs together?16:53
*** dtantsur has joined #openstack-meeting-316:54
krotscheckThe current user could return a hash of preferences maybe?16:54
* krotscheck isn’t certain he likes that idea.16:54
*** ihrachyshka has left #openstack-meeting-316:54
yolandaa hash?16:54
krotscheckuser: {id: foo, preferences: { one: two, three: four}}16:54
*** iovadia has quit IRC16:54
krotscheckHash. Java terminology. A dict.16:54
yolandai was thinking in md5 :)16:54
yolandayes, i meant that16:55
krotscheckHow do others feel about this?16:55
krotscheckI guess no real opinions.16:56
*** naohirot has joined #openstack-meeting-316:56
mrmartin+1 for hash16:57
mrmartinHash16:57
krotscheckyolanda: Even so, you run into the issue that the preferences may age out, and you need preferences INSIDE the services API to get the page limit.16:57
krotscheckAnd that’s where most caching usually falls down, because we don’t really want to trigger two API calls for every call16:57
*** trown has joined #openstack-meeting-316:57
mrmartinadd a cache TTL16:57
yolandathe way i was doing now is using angular cache, and if i had no cache, i queried again for prefs16:58
krotscheckmrmartin: We have one.16:58
krotscheckyolanda: We’ve already got a TTL baked into the angular caching layer, it should be transparent to $resource16:58
*** mgoddard has joined #openstack-meeting-316:58
*** stelfer has joined #openstack-meeting-316:58
*** clif_h has joined #openstack-meeting-316:59
mrmartindo we have a cache invalidate http header in the backend response?16:59
yolandakrotscheck, i found the problem in testing, if i had some javascript error on the client for some reason, cache was lost16:59
krotscheckyolanda: Interesting.16:59
mrmartinif the user prefs are changed, you can notifiy the client to refetch the user prefs.16:59
krotscheckWe’re running out of time.16:59
*** Nisha has joined #openstack-meeting-316:59
yolandamrmartin , and i was manually updating prefs if there was some change, i mean, i was manually updating the user prefs object16:59
krotscheckOk, we’ll pick up with pref caching next week.17:00
krotscheckThanks everyone!17:00
*** romcheg has joined #openstack-meeting-317:00
krotscheck#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Mon Jan 26 17:00:40 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/storyboard/2015/storyboard.2015-01-26-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/storyboard/2015/storyboard.2015-01-26-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/storyboard/2015/storyboard.2015-01-26-16.00.log.html17:00
NobodyCamthank you krotscheck17:00
NobodyCamwho's here for the Ironic meeting17:01
trowno/17:01
JoshNango/17:01
stelferhello o/17:01
Nishao/17:01
dtantsuro/17:01
lucasagomeso/17:01
rlooo/17:01
romchego/17:01
naohiroto/17:01
clif_ho/17:01
NobodyCam:) devananda may be just a couple of minutes late logging in17:01
*** fischerw has joined #openstack-meeting-317:01
lucasagomes:30417:01
lucasagomesops17:01
NobodyCamso17:01
mgoddardhi all17:01
jroll\o17:02
NobodyCam#startmeeting Ironic17:02
NobodyCam#chair devananda17:02
NobodyCamWelcome everyone to the Ironic meeting.17:02
openstackMeeting started Mon Jan 26 17:02:06 2015 UTC and is due to finish in 60 minutes.  The chair is NobodyCam. Information about MeetBot at http://wiki.debian.org/MeetBot.17:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:02
*** openstack changes topic to " (Meeting topic: Ironic)"17:02
openstackThe meeting name has been set to 'ironic'17:02
openstackCurrent chairs: NobodyCam devananda17:02
NobodyCamOf course the agenda can be found at:17:02
NobodyCam#link https://wiki.openstack.org/wiki/Meetings/Ironic#Agenda_for_next_meeting17:02
*** CTtpollard has left #openstack-meeting-317:02
NobodyCamstatus of course can be found on the white board17:02
NobodyCam#link https://etherpad.openstack.org/p/IronicWhiteBoard17:03
*** wanyen has joined #openstack-meeting-317:03
*** yamahata has joined #openstack-meeting-317:03
devanandamorning, all17:03
NobodyCammorning devananda :)17:03
devanandaI'm sort of here (actually in a car right now, but not driving)17:03
NobodyCamyou are already a chair17:03
wanyengood morning17:03
NobodyCamwas just about to jump into announcements17:04
devanandacarry on then :)17:04
NobodyCam#topic announcements:17:04
*** openstack changes topic to "announcements: (Meeting topic: Ironic)"17:04
*** yolanda has left #openstack-meeting-317:04
NobodyCamLots of mid cycles and EE comming up17:05
devanandaonly annoucement from me is about the midcycle sprints -- just that we're having them and such17:05
rloowhat is EE?17:05
* naohirot EE?17:05
NobodyCamFF17:05
NishaFF?17:05
devanandafeature freeze17:05
dtantsur:D17:05
lucasagomesfeature freeze17:05
lucasagomesyeah17:05
NobodyCamyep17:06
NobodyCam:-p17:06
jrolllol17:06
rloofeature freeze or feature spec freeze?17:06
wanyenwhenis ff?17:06
devanandaMarch 5th is the date when most projects, Ironic included, will stop accepting new features17:06
NobodyCammarch 5th17:06
devanandait's all up on https://wiki.openstack.org/wiki/Kilo_Release_Schedule17:06
*** Guest3482 is now known as dansmith17:06
devanandanot really an announcement ...17:06
NobodyCamhowever that does not give the coders a whole lot of time to land the code17:06
NobodyCambut well cover that in a bit17:07
naohirotNobodyCam: Is march 5th deadline of submitting a new bp?17:07
NobodyCamnaohirot: yes17:07
*** bradjones has quit IRC17:07
devanandalets move on to the status check17:07
NobodyCam#topic Status updates17:08
*** openstack changes topic to "Status updates (Meeting topic: Ironic)"17:08
devananda#topic subteam status reports17:08
*** openstack changes topic to "subteam status reports (Meeting topic: Ironic)"17:08
NobodyCamlol17:08
*** jedimike has left #openstack-meeting-317:08
naohirotNobodyCam: I think it's very difficult to go through review from Match 5th, right?17:08
NobodyCamnaohirot: yes17:08
NobodyCamany questions on the status17:08
naohirotNobodyCam: Okay17:08
*** yapeng has joined #openstack-meeting-317:09
NobodyCam(As of Mon, 26 Jan 11:45 UTC) Open: 122 (0). 4 new (0), 32 in progress (+1), 1 critical (+1), 16 high (+2) and 6 incomplete17:09
*** sahid has quit IRC17:09
*** etoews has quit IRC17:09
NobodyCamour bug list is growing17:09
devanandalooks like there is progress on both ilo and irmc drivers, but more reviews are still needed17:10
dtantsurI'm not sure all 32 bugs are _actually_ in progress. probably I should start poking people again...17:10
rloowrt oslo. Doesn't seem like we've gotten anything there. It'd be useful to know 1. what oslo changes could be done, even if they aren't done yet.17:10
*** igordcard has quit IRC17:10
devanandaI'd like to also remind folks that, when reviewing code for third-party drivers, we need to trust the authors / maintainers of those drivers17:10
*** bradjones has joined #openstack-meeting-317:10
*** bradjones has quit IRC17:10
*** bradjones has joined #openstack-meeting-317:10
wanyenyes. pls continue to review ilo specs.17:10
NobodyCamdid we ever got to have our bug scrub?17:10
*** marun has joined #openstack-meeting-317:10
devanandaI havent seen any updates from GheRivero on the oslo stuff in a while17:11
devanandaand afaik he is not coming to our sprint next week17:11
NobodyCamdo we know if he'll make the SF meetup?17:11
devanandaNobodyCam: yah. several folks worked on bugs for a day (I had to miss it, unfortunatey)17:11
devanandaNobodyCam: he will not17:11
NobodyCam:(17:11
*** yamahata has quit IRC17:11
dtantsurNobodyCam, we did :)17:11
NobodyCamgreat I also missed it :(17:11
dtantsurit's worth repeating from time to time anyway :)17:12
jrolldevananda: "we need to trust the authors / maintainers of those drivers" what do you mean by this?17:12
*** yamahata has joined #openstack-meeting-317:12
NobodyCamdevananda: do you want to save that for the review section17:12
devanandai spoke with dhellmann last week briefly about the oslo.objects refactoring. it was/is bocked on something else in oslo, and at this point, doesn't seem like a priority for this cycle for anyone17:12
lucasagomes:/17:13
devanandajroll: let's come back to that in the next section ...17:13
jrollok17:13
*** baoli has quit IRC17:13
NobodyCamanything else on staus updates?17:13
devanandanot from me17:14
NobodyCamif not I'm going to shuffel the oder listed on the agenda, for time.17:14
devanandaNobodyCam: do it :)17:14
*** yapeng has quit IRC17:14
NobodyCam#topic IPMI retry timeout value17:14
*** openstack changes topic to "IPMI retry timeout value (Meeting topic: Ironic)"17:14
NobodyCamtrown: that you17:14
trownyep17:14
NobodyCam:)17:14
trownso, I picked up this bug as it was marked "low hanging fruit"17:15
*** baoli_ has joined #openstack-meeting-317:15
*** armax has quit IRC17:15
trownthe change is pretty trivial, however, I need some help with determining what the "best" value is17:15
NobodyCam#link https://review.openstack.org/#/c/131296/17:15
* jroll is checking...17:15
trownis there operator opinion/consensus on this?17:16
lucasagomesyeah it would be good to get an operator opnion on that17:16
devanandaI'm not sure that a single default can cover all hardware17:16
devanandaas different hardware may have problems at different retry timings17:16
devanandathe current default is overly conservative IMO, though17:16
NobodyCamcould we half it to 30?17:17
devananda10?17:17
lucasagomesright, also maybe as part of that bug we could put a NOTE at the deployer's doc17:17
*** sbalukoff has quit IRC17:17
jrollwe're using 60 at rackspace, it's been fine, though we're also vigilant at tracking down bad BMCs and putting them in maintenance mode17:17
devanandaI'd like some input from the tripleo rack as well, as they were the folks who originally filed / fixed that issue17:17
lucasagomesto call attention to that option17:17
rloohow would one go about getting operator opinion? wouldn't that be a good first step?17:17
trown"Too low -> we can inadvertantly knock over some (fragile) BMCs and require a hard-reset of the BMC (not the node) to unbrick it. " <--- how low does this happen at?17:17
jrollwe also haven't played with different values17:17
*** scheuran has quit IRC17:17
devanandatrown: that totally depends on the hardware, unfortunately17:18
devanandatrown: I've definitely seen reports of that happening around 5 seconds17:19
trownah ok17:19
devanandawith older HP hardware17:19
trownso 60 is really conservative then17:19
devanandaand I believe victor_lowther had pointed out his experiences on some hardware with that, a while back as well17:19
*** baoli_ has quit IRC17:20
rloohttps://review.openstack.org/#/c/82668/ changed it from 10 to 60.17:20
jrollfwiw, I'd rather have my power sync loop be slow than brick a bmc17:20
devanandajroll: exactly17:20
NobodyCamyes17:20
lucasagomesright17:20
jrollwatch for slow bmcs and maintenance them as needed17:20
*** safchain has quit IRC17:20
NobodyCamso how about 30 and if that causes not issues than half it again to 1517:21
lucasagomesso should we mark the bug as invalid? Or would be updating the deployer docs to call more attention to that option a valid "fix"17:21
rloothis is a default value, so every time we change it, we could be breaking backwards compat.17:21
devanandahttps://review.openstack.org/#/c/96558/ added the minimum time interval17:21
*** eghobo has joined #openstack-meeting-317:21
trownI like the "update the deployer docs" approach17:21
trownconservative defaults are not a bad thing17:22
devanandain resposne to https://bugs.launchpad.net/ironic/+bug/1320513 filed by tripleo team17:22
jrollI also like the documentation fix, maybe add more notes on it to the actual config optino as well17:22
NobodyCamjroll: ++17:22
lucasagomesyeah, since there's no best default17:22
jrollright17:22
devanandaso 10 and doc changes?17:22
devanandathat would work for me17:23
jrollno17:23
jrollI think leave it at 6017:23
lucasagomesI would say leave as-is17:23
devanandaah, ok17:23
trownya ++17:23
lucasagomesto be conservative, but update the docs17:23
devanandasounds good17:23
NobodyCamyea!17:23
jrollfwiw, when we deployed initial production17:23
rloo++17:23
lucasagomesput a NOTE or even a WARNING there17:23
devanandawho's going to do the doc patch?17:23
jrollwe didn't notice slow BMCs slowing things down until around 5-600 nodes17:23
trowndevananda: I can do the doc patch17:23
lucasagomestrown, ? since he's the one assigned to the bug?17:23
lucasagomesif he wants17:23
lucasagomesah ok17:23
devananda#agreed keep the current default, but improve documentation17:24
NobodyCam:)17:24
devananda#action trown to add or improve documentation around ipmi retry timing options17:24
NobodyCamin code (conf file) and wiki right?17:24
*** baoli has joined #openstack-meeting-317:25
*** baoli has quit IRC17:25
NobodyCamany thing else on timeout17:25
trownNobodyCam: that seems good17:25
*** baoli has joined #openstack-meeting-317:25
NobodyCamok then17:25
NobodyCam#topic Prioritize Spec and code reviews17:25
*** openstack changes topic to "Prioritize Spec and code reviews (Meeting topic: Ironic)"17:25
NobodyCamoh thats me17:25
*** baoli has quit IRC17:26
NobodyCamOk we are approching FF and still have a bunch of specs and code out that needs reviewing17:26
JayF.17:26
*** baoli has joined #openstack-meeting-317:26
NobodyCamI've seen a trend of our reviews esp. on spec to be getting more and more nit picky17:27
*** egallen has joined #openstack-meeting-317:27
wanyenspecs need to be approved by FF?17:27
*** wojdev has quit IRC17:27
* devananda has seen this too17:27
devanandaand we already have many specs approved and blocked on other work17:27
NobodyCamI think we all have trust in each other to be able to do the work we say we will17:27
devanandaand code reviews are taking an increasing amount of time, even for essential things (ie, patches that block feature work)17:28
JayFOverall review bandwidth seems to be down over the last month17:28
NobodyCamI am suggesting that we lossen the review criteria17:28
JayFif you look at statistics17:28
devanandaNobodyCam: that's where my comment earlier about trusting driver authors comes in17:28
lucasagomesJayF, yeah noticed that too17:28
jrolldo you notice this more with cores or non-cores or both?17:28
devanandaJayF: indeed it is17:28
devanandajroll: both. but cores should be setting the better example17:28
rlooloosen review criteria for both specs and code?17:28
NobodyCamboth, even I am guilty of this17:28
jrollI'm sure I am too17:29
devanandaa few suggestions for us all (myself, too)17:29
NobodyCamrloo: mainly for specs17:29
NobodyCambut code needs to land faster17:29
devananda- for code nits, just add a follow on patch yuorself,a nd +2/+A it if you would other wise +A the original patch17:29
devanandalike, if I spot a spelling ereror in a comment string, I will start +2/+A'ing my own patch, just so the original patch author doesn't have to do anothe rrev17:30
devananda(and we dont have to wait for it)17:30
NobodyCamI like that Idea17:30
wanyen++17:30
devananda- for driver changes, if its from the driver maintainer, and you don't know that hardware, please give them teh benefit of the doubt17:30
*** lazy_prince has quit IRC17:30
wanyen:)17:31
NobodyCamas a little background I started the thread because I was reviewing a spec for a vendor passthru method17:31
*** killer_prince has joined #openstack-meeting-317:32
*** JeanBriceCombebi has quit IRC17:32
*** killer_prince is now known as lazy_prince17:32
dtantsurNobodyCam, as you know I don't agree on _this_ particular one17:32
NobodyCamIf I recall the Vendor passthru is a area where vendors can add functions that they can perform with their hardware that the generic drivers can not do17:32
NobodyCamdtantsur: thats why I wanted to chat about17:33
NobodyCamit17:33
*** salv-orlando has joined #openstack-meeting-317:33
NobodyCamall code has to go thru code review17:33
dtantsurvendor passthru is an API, however we call it. that's why I think we should not be too easy about it...17:33
NobodyCamso I would expect any glaring coding errors would be cought there17:33
* lucasagomes I think I reviewed that spec... looks again17:34
*** baoli has quit IRC17:34
dtantsurI though the biggest point of the spec process was to agree on important things like API17:34
*** baoli has joined #openstack-meeting-317:34
NobodyCamwhen we came up with teh VP aPI it was to allow vendors to be able to dothere own thing17:34
* devananda goes afk to walk into the nova meeting17:34
dtantsurbecause once published, they're hard to change17:34
jrollI mean, people weren't -1'ing the spec because there might be coding errors...17:35
jroll#link https://review.openstack.org/#/c/149383/17:35
*** baoli_ has joined #openstack-meeting-317:35
jrolllucasagomes: ^17:35
*** SridharRamaswamy has quit IRC17:35
lucasagomesyeah... looking again, didn't recheck the replied17:35
lucasagomesreplies*17:35
NobodyCamI recall us talking about reviewing the VP methods and if we found several drivers doing the same thing then we would look at moving that code to a standard api for all the drivers17:35
dtantsurif we make exception about vendor passthru's, namely 1. allow to break backward compatibilty without warning, 2. allow it to screw everything including breaking hardware, we have to communicate it very clearly.17:36
jrolldtantsur: nothing about that spec does either of those17:36
dtantsurmost concerning point for me about this spec is that it allows deploy to happen in the middle of bios update17:36
jrolloh?17:36
dtantsurjroll, how does it prevent ^^^17:36
NobodyCamdtantsur: my thought behind this was that it is in the vendors best intress to ensure their code works17:36
jrollI mean17:36
jrollit could lock the node17:37
jrollpretty simple17:37
jrollI would assume it would lock the node while performing the firmware update17:37
NobodyCamdtantsur: would that have been cought in a review of the code?17:37
dtantsurmaybe it's only me, but it's hard for me to watch both high-level and low-level things while looking at the code17:38
rlooNobodyCam: not necessarily (caught in code review)17:38
dtantsurNobodyCam, but again, why we have spec process at all? everything can be caught during code review :D17:38
dtantsurI think spec is a chance to think about such corner cases17:38
lucasagomesright, replies on that spec looks good to me. But idk... I don't think the reviews were nitpicky in that case17:38
lucasagomesthey were more suggestions and ideas17:38
*** baoli has quit IRC17:39
jrollsure, but the comments on that spec is "let's just do real zapping instead". when zapping has been bumped to L.17:39
*** MaxV has quit IRC17:39
* dtantsur didn't know zapping was bumped17:39
NobodyCammy goal is to imporve our volisity on reviews both code and spec17:39
jrollso "just make zapping steps" doesn't solve the problem17:39
jrollwell, hardware capability stuff was bumped, which zapping kind of depends on AIUI17:39
lucasagomes+ I understand VP doens't need to be super "consistent" but, we depend on VP methods as today to deploy any machine with PXE for example17:39
*** rcleere is now known as rcleere_away17:40
dtantsurjroll, I guess it should be an explicit decision, I didn't think we can't make zapping states _at all_ without capabilities17:40
JoshNangyeah i think zapping will have to be bumped17:40
dtantsurlike in this case: we could call it zapping17:40
NobodyCammy understanding is zapping did get bumped17:40
dtantsurbut I don't insist, I really didn't realize that it's pretty much decided, sorry for that folks :)17:41
rloowhen was it mentioned to the group that zapping got bumped?17:41
NobodyCamon the nova side I think17:41
jrolldtantsur: sure, we should talk about it, idk, maybe it isn't officially bumped17:41
* devananda is back17:41
dtantsurdevananda, was zapping _officially_ bumped to L?17:41
lucasagomesdtantsur, it's all good. I mean, we should say it if we think it's important... and you can have ur -1 there even if the spec is merged17:41
JoshNangrloo: i don't think it's officially bumped yet.17:41
wanyenI didn'tknow zapping is bumped.17:42
*** amotoki has joined #openstack-meeting-317:42
*** amotoki has quit IRC17:42
* lucasagomes neither do I17:42
JoshNangi could write and land most of the code, but doing zapping you can't schedule against seems...less useful17:42
wanyenwe need raid config17:42
dtantsurJoshNang, the spec in question is a use case, raid stuff as well17:43
wanyenscheduling does not depends on capability spec17:43
rlooi admit that I don't always know when something is a nit or not. I like it when dtantsur and lucasagomes comment, so I would hate to dissuade them from doing so (or others). maybe gentle reminders or something? eg ping me if you disagree?17:43
devanandadtantsur: I do not recall that zapping was bumped17:43
jrollso look at it this way: do we actually think we can land a zapping spec and implementation, in time that victor_lowther could build the drac raid stuff on top?17:44
NobodyCamsome how I thought it was17:44
devanandajroll: nope17:44
jrollright.17:44
JoshNangand zapping requires tne cleaning implementation17:44
lucasagomesrloo, yeah, well I'm always in the channel and ppl can ping me to discuss whatever17:44
jrollthe VP api is for vendors to build things that aren't generic yet17:44
devanandaso without going into all the detail about specific state transitions17:44
jrollzapping/raid is not generic17:44
devanandawhich I'm the only one working on actually implementing17:44
jrollyet17:44
rloowe seem to be digressing...17:44
devanandaand which took a lot of time to get anyone to review17:44
jrollrloo++17:44
devanandaand yes i'm frustrated about that17:45
devanandawe have totally gone off topic17:45
devanandawhich was -- how do we improve OVERALL velocity17:45
NobodyCamyep17:45
devanandaby not nit picking17:45
devanandaand then dtantsur brought up why we have specs at all17:45
devanandawhich I'd like to decompose a bit17:45
rlooi think the example (spec) given about 'nit picking' wasn't considered nit picking by others17:46
NobodyCam15 minuts btw17:46
devanandadtantsur: do you feel that specs provide you, as a code reviewer, with any meaningful context?17:46
*** Shrews has joined #openstack-meeting-317:46
*** julim has quit IRC17:46
*** belmoreira has quit IRC17:46
naohirotI'm just wondering, in order to accelerate review process, can't we set a deadline for each spec review?17:46
dtantsurdevananda, I feel like it allows me to become acknowledged with high-level idea, before diving into (possibly a lot of) code17:46
devanandarloo: NobodyCam also brought up the vendor_passthru question, which I agree, doesn't sound like a nit. but it IS related to how deeply we scrutinize drivers17:46
dtantsurdevananda, so yes17:46
* Shrews forgot about the meeting... apologizes17:46
rlooso how deeply do we scrutinize drivers?17:47
jrollI've heard this often recently: "as a code reviewer, does this spec give you enough information to tell you if the implementation is done" and I don't think that should be the intention of specs because "tell you if it's done" means different things to different people17:47
dtantsurI was assuming that API (and other use visible) changes are the most important to agree and be clear on17:47
devanandadtantsur: cool. I'm glad. that's what I beleive specs should do (help to flesh out a high-level idea enough to agree on the direction)17:48
devanandaalso, yes, changes to API (both external and internal) need more detailed review than other things17:48
devanandawhen they are part of the core APIs17:48
devanandavendor_passthru is vendor specific17:48
*** sunny_ has joined #openstack-meeting-317:49
devanandait's supposed to be an area for vendors to do new things17:49
NobodyCamI have been thinking along the lines of "if the change impacts a common area or more then one driver."17:50
devanandalet me ask: what's teh impact to the project if a driver decides to break their vendor_passthru's backwards compatibility?17:50
lucasagomesdepend on the driver17:50
*** ivar-lazzaro has joined #openstack-meeting-317:50
devanandait's clearly a higher impact if that is IPA or the pxe/iscsi driver ... beacuse these are common drivers we all rely on17:50
lucasagomesfor the continue_deploy VP of the PXE driver17:50
lucasagomesit can be problematic17:50
jrollI guess it depends on the passthru api17:50
dtantsurdevananda, people coming to a channel asking us to fix it :)17:51
devanandabut iLO? DRAC? iRMC? -- if they break an experimental feature in vendor_passthru17:51
rloodevananda: let me ask you, are we OK if a driver breaks their vendor_pasthru's backwards compatibility? cuz I personally don't care if it is a third-party driver, but... what would our users think?17:51
*** rcleere_away is now known as rcleere17:51
jrolldevananda: didn't nova-bm teach us that nothing is experimental? :)17:51
devanandajroll: indeed. except when it is.17:51
*** tellesnobrega_ has quit IRC17:51
dtantsurI remember us arguing about backward compatibility of an ILO driver_info option between commits in the middle of cycle17:51
dtantsuri.e. ilo_username vs ipmi_username vs username17:52
*** lazy_prince has quit IRC17:52
dtantsurand we decided that we don't wanna break even this compatibility17:52
devanandadtantsur: that's not venor passthru17:52
*** ivar-lazzaro has quit IRC17:52
devanandathat is the basic interface for node.driver_info17:52
devanandachanging that would break the whole driver17:52
devanandanot just vendor_passthru/method=my_experimental_feature17:52
dtantsurthat's what people has much less chances to be broken by. now we're talking about API's17:53
NobodyCamrloo: most of the vendor bmc's can also fall back to generic ipmi if the vendor driver was not working17:53
lucasagomesyeah it's complicated... I think that we can be more soft on vendor passthru. But again, I'm looking at the comments on that spec, and I think that suggestions are valid. That's spec is all about adding VP methods17:53
rloodevananda: so you are saying that vendor_passthru == vendor specific and as such, 'experimental'17:53
dtantsursorry, I don't recall us having notion of 'experimental' API17:53
*** ivar-lazzaro has joined #openstack-meeting-317:53
lucasagomesif we can't suggest, if it's totally up to the vendor then we don't need a spec17:53
lucasagomesas NobodyCam commented17:53
devanandaperhaps we should have a separate /experimental section?17:53
dtantsure.g. in discoverd I have API's that are only enabled by a configuration option, saying that it's experimental17:53
*** stevedoll has joined #openstack-meeting-317:54
*** killer_prince has joined #openstack-meeting-317:54
lucasagomesdevananda, or just have the code itself adding methods to the VP methods17:54
*** killer_prince is now known as lazy_prince17:54
dtantsurdevananda, ++ for anything clearly telling people: this can eat your laundry :D17:54
NobodyCamdevananda: or verdor contrib area17:54
NobodyCam++17:54
lucasagomesif it's not touching any core parts, it's not impacting on DB or core API etc17:54
devanandavendor_passthru is vendor contributed ...17:54
devanandalucasagomes: that's exactly what vendor passthru should be doing ...17:54
lucasagomesyeah17:54
NobodyCamtrue17:54
lucasagomesso maybe not requiring specs for vendor passthru bits?17:54
lucasagomesjust send code17:55
NobodyCam++17:55
NobodyCamwith a good commit message17:55
lucasagomesin the code we can decide whether things simple like a return code for a vendor does make sense or not17:55
lucasagomesand suggest something, but that's imlementation so it's even easier to do when reviewing the code17:55
lucasagomesnot the spec17:55
NobodyCamhow does that sound ^^^^17:55
NobodyCamvote?17:55
*** eghobo has quit IRC17:55
* devananda feels like this still strayed far afield from the original topic of review velocity17:55
naohirothow did we prioritize the spec review?17:56
naohirotwhy can't we set a deadline for each review?17:56
*** julim has joined #openstack-meeting-317:56
NobodyCamnaohirot: our reviewers are also very busy17:56
jrolldevananda: it seems we've managed to eliminate one source of slowness, at least17:56
rlooreview velocity == both reviewers (core or not) and committer doing their part. (apart from nits if we can clarify what nits are).17:56
*** ivar-laz_ has joined #openstack-meeting-317:57
dtantsurNobodyCam, lucasagomes, -0 until we have way to distinguish experimental (might break and be broken) and normal ones...17:57
jrollnaohirot: what happens if deadlines are not met? pay cuts? :P17:57
* rloo gets tired of asking why a comment in a previous revision wasn't addressed. 17:57
dtantsurrloo, ++17:57
devanandarloo: me too17:57
jrollyep17:57
NobodyCamdtantsur: I like the invers of that.. tag drivers as production ready17:57
devanandaNobodyCam: who decides what's production ready?17:58
devanandaNobodyCam: the TC is getting out of that business ...17:58
naohirotIn order to proceed next step, a little by little, we need a little bit fine, small granularity schedule, I think.17:58
NobodyCamahh17:58
NobodyCamtwo minutes17:58
devananda#topic open discussion17:58
rloomaybe we could get feedback from people submitting patches, if they have suggestions to speed things up.17:58
*** openstack changes topic to "open discussion (Meeting topic: Ironic)"17:58
*** ivar-laz_ has quit IRC17:58
*** ivar-laz_ has joined #openstack-meeting-317:59
*** baoli_ has quit IRC17:59
devanandarloo: or perhaps rather than gathering more feedback, we could just all do code reviews, based on the project's priorities17:59
NobodyCamanyting for OD?17:59
devanandaand if the priorities aren't clear, then that's my fault, and I'll put more effort into communicating them17:59
* rloo been trying but /me wonders how to improve patches etc so fewer iterations17:59
NobodyCamcontinue in channel?17:59
jrolldevananda: that TODO.rst helps, but I'd love if we got together and decided priorities for the rest of this cycle18:00
lucasagomesyeah channel is it18:00
devanandathanks, all. see (some of) you next week in Grenoble18:00
jrollyeah18:00
* jroll reposts there18:00
NobodyCamhtank you all18:00
lucasagomesjroll, +1!18:00
naohirotjroll: If review didn't ended by the deadline, then we have to go to the next step.18:00
devananda#endmeeting18:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:00
lucasagomesthanks all18:00
openstackMeeting ended Mon Jan 26 18:00:25 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ironic/2015/ironic.2015-01-26-17.02.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ironic/2015/ironic.2015-01-26-17.02.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/ironic/2015/ironic.2015-01-26-17.02.log.html18:00
*** dtantsur has left #openstack-meeting-318:00
*** ameade_ has quit IRC18:00
*** Shrews has left #openstack-meeting-318:00
wanyenone suggestion- if most reviewers canreview the same spec one the same week it will likely to reduce numbe rof revs as authors can get all commetns at the same time and address them all togehter18:00
*** ivar-lazzaro has quit IRC18:00
*** ameade_ has joined #openstack-meeting-318:00
*** alexpilotti has quit IRC18:01
*** mgoddard has quit IRC18:01
*** baoli_ has joined #openstack-meeting-318:01
*** stelfer has left #openstack-meeting-318:01
*** julim_ has joined #openstack-meeting-318:02
*** wanyen has quit IRC18:02
*** trown has left #openstack-meeting-318:03
*** jaypipes has joined #openstack-meeting-318:03
*** alexpilotti has joined #openstack-meeting-318:04
*** julim has quit IRC18:05
*** wojdev_ has joined #openstack-meeting-318:06
*** wojdev_ has quit IRC18:06
*** alexsyip has joined #openstack-meeting-318:06
*** pkoniszewski has joined #openstack-meeting-318:08
*** ttrifonow is now known as zz_ttrifonow18:08
*** romcheg has quit IRC18:11
*** rcleere is now known as rcleere_away18:12
*** stevedoll has quit IRC18:16
*** armax has joined #openstack-meeting-318:17
*** VW_ has quit IRC18:19
*** rcleere_away is now known as rcleere18:19
*** yamahata has quit IRC18:22
*** yamahata has joined #openstack-meeting-318:24
*** jcoufal has quit IRC18:37
*** naohirot has quit IRC18:38
*** VW_ has joined #openstack-meeting-318:39
*** zhiyan has quit IRC18:40
*** zhiyan has joined #openstack-meeting-318:40
*** ivar-laz_ has quit IRC18:41
*** ivar-lazzaro has joined #openstack-meeting-318:42
*** ivar-lazzaro has quit IRC18:44
*** ivar-lazzaro has joined #openstack-meeting-318:45
*** lucasagomes is now known as lucas-dinner18:46
*** lucas-dinner has left #openstack-meeting-318:46
*** SridharRamaswamy has joined #openstack-meeting-318:49
*** SridharRamaswamy has quit IRC18:51
*** Nisha has quit IRC18:51
*** rloo has left #openstack-meeting-318:54
*** devlaps has joined #openstack-meeting-318:55
*** yapeng has joined #openstack-meeting-318:58
*** armax has quit IRC18:58
*** armax has joined #openstack-meeting-318:59
*** yapeng has quit IRC19:02
*** stevedoll has joined #openstack-meeting-319:03
*** peristeri has quit IRC19:04
*** reed has joined #openstack-meeting-319:04
*** alexpilotti has quit IRC19:05
*** stevedoll has quit IRC19:05
*** lazy_prince has quit IRC19:08
*** killer_prince has joined #openstack-meeting-319:10
*** killer_prince is now known as lazy_prince19:10
*** etoews has joined #openstack-meeting-319:13
*** baoli_ has quit IRC19:14
*** s3wong has joined #openstack-meeting-319:15
*** peristeri has joined #openstack-meeting-319:15
*** david-lyle is now known as david-lyle_afk19:15
*** b3nt_pin is now known as beagles19:21
*** alexpilotti has joined #openstack-meeting-319:25
*** salv-orlando has quit IRC19:32
*** armax has quit IRC19:32
*** armax has joined #openstack-meeting-319:42
*** salv-orlando has joined #openstack-meeting-319:42
*** alexpilotti has quit IRC19:49
*** sunny_ has quit IRC19:52
*** thangp has quit IRC19:53
*** julim_ has quit IRC19:55
*** julim has joined #openstack-meeting-319:57
*** VW_ has quit IRC20:04
*** yamahata has quit IRC20:07
*** armax has quit IRC20:09
*** matrohon has joined #openstack-meeting-320:11
*** dboik has quit IRC20:11
*** julim has quit IRC20:14
*** sbalukoff has joined #openstack-meeting-320:17
*** stevedoll has joined #openstack-meeting-320:18
*** sunny_ has joined #openstack-meeting-320:22
*** armax has joined #openstack-meeting-320:24
*** sunny_ has quit IRC20:28
*** stevedoll has quit IRC20:31
*** mwagner_lap has quit IRC20:33
*** lblanchard has quit IRC20:35
*** tellesnobrega_ has joined #openstack-meeting-320:35
*** pkoniszewski has quit IRC20:38
*** belmoreira has joined #openstack-meeting-320:39
*** tellesnobrega_ has quit IRC20:44
*** sunny_ has joined #openstack-meeting-320:45
*** sergef has quit IRC20:47
*** salv-orlando has quit IRC20:49
*** mrunge_afk has quit IRC20:58
*** markvoelker has quit IRC21:00
*** VW_ has joined #openstack-meeting-321:03
*** stevedoll has joined #openstack-meeting-321:06
*** salv-orlando has joined #openstack-meeting-321:08
*** vishwanathj has joined #openstack-meeting-321:10
*** vishwanathj has quit IRC21:11
*** iovadia has joined #openstack-meeting-321:12
*** plaurin_ has quit IRC21:12
*** aweeks has quit IRC21:12
*** baoli has joined #openstack-meeting-321:16
*** baoli has quit IRC21:17
*** baoli has joined #openstack-meeting-321:17
*** baoli has quit IRC21:19
*** baoli has joined #openstack-meeting-321:19
*** jtomasek has quit IRC21:22
*** julim has joined #openstack-meeting-321:30
*** mwang2 has joined #openstack-meeting-321:35
*** banix has quit IRC21:37
*** aweeks has joined #openstack-meeting-321:38
*** david-lyle_afk is now known as david-lyle21:40
*** mwagner_lap has joined #openstack-meeting-321:41
*** plaurin_ has joined #openstack-meeting-321:44
*** armax has quit IRC21:53
*** igordcard has joined #openstack-meeting-321:57
*** dboik has joined #openstack-meeting-321:58
*** armax has joined #openstack-meeting-321:58
*** dboik_ has joined #openstack-meeting-321:59
*** ChuckC has joined #openstack-meeting-322:00
*** mrmartin has quit IRC22:00
*** ChuckC_ has quit IRC22:00
*** dboik has quit IRC22:03
*** igordcard has quit IRC22:03
*** ChuckC_ has joined #openstack-meeting-322:04
*** igordcard has joined #openstack-meeting-322:05
*** ChuckC has quit IRC22:08
*** ctlaugh_ has quit IRC22:13
*** sunny_ has quit IRC22:13
*** igordcard has quit IRC22:13
*** banix has joined #openstack-meeting-322:15
*** banix has quit IRC22:15
*** ChuckC has joined #openstack-meeting-322:17
*** ChuckC_ has quit IRC22:18
*** dboik_ has quit IRC22:25
*** bknudson has quit IRC22:30
*** alexpilotti has joined #openstack-meeting-322:32
*** VW_ has quit IRC22:33
*** yapeng has joined #openstack-meeting-322:35
*** VW_ has joined #openstack-meeting-322:37
*** etoews has quit IRC22:38
*** jgrimm is now known as zz_jgrimm22:38
*** mattfarina has quit IRC22:39
*** yapeng has quit IRC22:40
*** cbader has quit IRC22:40
*** matrohon has quit IRC22:41
*** carl_baldwin has quit IRC22:41
*** VW_ has quit IRC22:42
*** dboik has joined #openstack-meeting-322:42
*** eghobo has joined #openstack-meeting-322:43
*** yapeng has joined #openstack-meeting-322:46
*** dboik has quit IRC22:48
*** dboik has joined #openstack-meeting-322:50
*** VW_ has joined #openstack-meeting-322:51
*** salv-orlando has quit IRC22:52
*** alexpilotti has quit IRC22:54
*** jpomero has quit IRC22:54
*** VW__ has joined #openstack-meeting-322:54
*** VW_ has quit IRC22:55
*** alexpilotti has joined #openstack-meeting-322:59
*** VW__ has quit IRC23:06
*** Sukhdev has joined #openstack-meeting-323:08
*** banix has joined #openstack-meeting-323:11
*** sunny_ has joined #openstack-meeting-323:14
*** sunny_ has quit IRC23:19
*** banix has quit IRC23:26
*** dboik has quit IRC23:26
*** nelsnelson has quit IRC23:27
*** armax has quit IRC23:29
*** tellesnobrega_ has joined #openstack-meeting-323:29
*** dboik has joined #openstack-meeting-323:30
*** david-lyle is now known as david-lyle_afk23:31
*** alexpilotti has quit IRC23:38
*** sigmavirus24 is now known as sigmavirus24_awa23:44
*** watanabe_isao has joined #openstack-meeting-323:44
*** yapeng has quit IRC23:47
*** sigmavirus24_awa is now known as sigmavirus2423:47
*** armax has joined #openstack-meeting-323:49
*** sunny_ has joined #openstack-meeting-323:49
*** VW_ has joined #openstack-meeting-323:50
*** sunny_ has quit IRC23:54
*** stevedoll has quit IRC23:56
*** carl_baldwin has joined #openstack-meeting-323:59

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