19:00:21 #startmeeting refstack 19:00:22 Meeting started Mon Apr 20 19:00:21 2015 UTC and is due to finish in 60 minutes. The chair is davidlenwell. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:00:23 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 19:00:25 The meeting name has been set to 'refstack' 19:00:26 o/ 19:00:52 Today's agenda: 1) Recap last week agreements 2) Use case for signed request 3) Refstack Wiki update 4) Refstack UI status and review 5) pending review 6) open discussion 19:00:57 o/ 19:01:14 o/ 19:02:15 Last week we agreed to update refstack-client to SHA 7c8fcc67. 19:02:31 #topic 1) Recap last week agreements 19:02:49 o/ 19:03:35 Last week we agreed to update refstack-client to SHA 7c8fcc67. ... sslypushenko__: had submitted https://review.openstack.org/#/c/173090/ which had been merged. 19:03:51 awesome 19:03:54 o/ 19:05:06 any other agreements? 19:05:16 We also discussed where to host Refstack server 19:05:34 From last week's meeting, Rocky will contact infra team for a heads up that Refstack team investigating the possibility to push a patch to host Refstack server at infra. 19:06:25 I can follow up on that 19:07:06 great so we will revisit this topic next week? 19:07:11 sure 19:08:00 Sounds good! 19:08:07 okay .. anything else? 19:08:13 also last week we deferred "design session planning" to this week ... but I still do not see any entry 19:08:33 #link https://www.youtube.com/watch?t=134&v=_zgbXbnuRNM 19:08:46 sorry wrong one 19:09:11 catherineD's youtube debute 19:09:14 wrong link :-) 19:09:36 I meant to get the eitherpad link 19:09:44 I don't know anything about wrong links. :-D 19:10:05 lol 19:10:20 #link https://etherpad.openstack.org/p/refstack-qa-vancouver-design-session 19:11:29 As much as I'd like to take up time on the schedule durring the summit for refstack.. we haven't had the cycles to prepair .. 19:11:47 I'd like us to be discussing the ui 19:12:00 +1 19:13:14 since we aren't prepped to talk about it now.. we must defer 19:13:23 ok 19:13:31 lets move on.. 19:13:32 that is all from last week 19:13:36 #topic 2) Use case for signed request 19:14:21 I thought we discussed this last week? 19:14:34 last wednesday 19:14:36 are there any outstanding questions about the reasoning behind this change? 19:15:14 For those who did not attend last week Wed IRC meeting sslypushenko__: has very nice document at 19:15:25 #link https://docs.google.com/presentation/d/1v7exKKL1zSA102Xu8FkY1u9rMVUE6BjwUCoWGYYvbaI/edit#slide=id.g3005a843b_0_11 19:16:33 I started discussion about this document in openstack-infra. If anybody has some ideas, you can shared it there 19:16:39 sslypushenko__: may I request you to add the data upload workflow in #link https://docs.google.com/drawings/d/1y76mYyFl-iOqH4OQYT27Xcyh9QSPatXkuSag4zdHr5w/edit to the above link so we have all in on doc .. 19:17:36 catherineD I think that upload is not a specific case, but I can add it here 19:18:08 I don't think this is still an outstanding issue.. lets move on for now 19:18:33 #topic 4) Refstack UI status and review 19:18:35 davidlenwell: ok ... I can talk with sslypushenko__: on #refstack later .. 19:18:44 this topic is going to be more time consuming I believe 19:19:07 catherineD agreed 19:19:30 pvaneck: can you walk us through your status on the ui prototype? 19:19:47 sure 19:20:21 currently I have a results page that essentially just has a paginated table, showing the list of results 19:20:48 CPID, Upload Date, Test ID 19:20:55 Can filter by cpid 19:21:17 clicking on the test id will lead to a test output page 19:21:40 awesome! 19:21:41 the API needs the CORS patch in order for the UI to be able to retrieve data from the api 19:21:56 I'm reviewing that now 19:21:58 Sounds great! 19:22:26 the patch is currently under review with sslypushenko__ already +2ing it 19:23:15 It is LGTM, davidlenwell or catherineD can merge it 19:23:25 okay 19:23:34 I was still looking at it when the meeting started 19:23:55 when we're done I'll merge if its right 19:24:31 so just to clarify, it is fine to show the cpid in the list of all submitted test results? 19:24:36 so once pvaneck: pushes the next patch ... The refstack server UI is ready (without auth) 19:25:13 auth should be a high priority now that we have the basic framework in place 19:25:53 pvaneck: the reason for not showing the cpid is because we want the data to be anomymous ? 19:26:01 and we need to revisit the ux for assosiating users with vendors 19:26:01 pvaneck It is a good question about cpid. May be we shouldn't display cpid as shared data? 19:26:29 sslypushenko__: exactly ... 19:26:46 cpod should only show with auth ... 19:26:57 I think that for now it is ok. But we should think about it 19:27:15 so do we agree to show or not to show the cpid? 19:27:34 with no auth.. don't show it 19:27:51 It is reasonable... +! 19:27:53 once we werk out a registration flow and vendor assosiation we can revisit that 19:27:59 +1 19:28:00 #agreed do not show cpid without auth 19:28:04 okay 19:29:21 #agreed David to follow up with infra team on the possibility for Refstack server hosting at infra 19:29:29 I'd like to plan a ui design session with our group.. either at the summit or sometime face to face in the bay area 19:29:40 davidlenwell: +1 19:29:55 more of us will be at the summit.. 19:30:11 sslypushenko__: vladiskuz|2: we will have voice and video this time ... 19:30:42 catherineD Thx! 19:30:43 davidlenwell: not sure how the facility is at the summit ... 19:30:56 catherineD: great! 19:31:13 akanda has an air bnb two blocks from the venue we can use if need be 19:32:04 ha that is the company name ... Rocky asked .. 19:32:08 davidlenwell: +1 19:32:40 it was all over twitter last week.. I think she follows me 19:33:26 davidlenwell: if we are done on this topic ... we should revisit #3 ... 19:33:51 #agreed we will find a time to set aside at the summit to discuss the api in better detail. 19:34:03 sure.. 19:34:29 #topic revisit signed use case 19:35:13 Wiki update 19:35:29 ahh .. sorry I did skip one didn't I 19:35:34 #topic wiki update 19:35:50 our wiki is embarassingly out of date 19:36:12 I think our first measure should be to remove all current wiki pages and replace them with our current readme text 19:36:20 our Wiki is very out-of-date and need update 19:36:38 thoughts? 19:37:13 davidlenwell: +1 at least update to current readme 19:37:23 agreed 19:37:37 who can do that? Any special credential to update Wiki? 19:37:40 the current readme is the most updated piece of text we have on the project and our progress 19:37:50 anyone whos of the foundation can 19:37:55 a foundation member 19:37:58 not employee 19:38:07 so any of us who are contributers can update it 19:38:13 ic 19:38:32 I can do it if nobody else has time 19:39:24 I have a few cycles for refstack this week.. and this is important .. 19:39:30 davidlenwell: I take the you will do it :-) ... I have never done wiki update before ... 19:39:56 especially now we also have the workflow that sslypushenko__: has document ... 19:40:06 documented 19:40:25 I'll take care of it 19:40:31 If it is necessary I can redraw it in proper format 19:40:39 #agreed David will update the refstack wiki 19:40:42 sslypushenko__: I can export 19:40:48 davidlenwell: thx 19:41:26 sslypushenko__: thx for redraw if needed .. 19:41:58 Please mail me, if needed 19:42:07 okay .. I think that covers that topic for now . 19:42:13 #topic 5) pending review 19:43:01 we are doing good ... only 2 outstanding patches ... 19:43:50 davidlenwell: you are reviewing pvaneck: 's https://review.openstack.org/#/c/174951/ ? 19:44:19 yes 19:45:01 I think we should review sslypushenko__: https://review.openstack.org/#/c/161315/ 19:45:57 since the latest DefCore test schema will include UUID .. 19:46:37 I should say the schema patch is submitted by hogepodge: and is under reviewed .. 19:46:42 I think we can review it because idempotent_id works for qa team, and they don't want change them 19:46:55 sslypushenko__: ++1 19:47:36 works for me 19:47:45 me too .. 19:48:00 so we will review that patch ... 19:49:07 okay.. lets change to open discussion 19:49:14 I'd like to get the qa team to see the value of accepting your patch sslypushenko__ 19:49:24 It may be a longer discussion though. 19:49:31 hogepodge Thx 19:49:49 #topic 6) open discussion 19:50:27 #link qa discussion topics, open until the 30th 19:50:28 https://etherpad.openstack.org/p/liberty-qa-summit-topics 19:53:07 so next Refstack IRC meeting is the last chance for us to discuss any topic we want to submit to qa discussion topics... 19:54:32 Has anyone contacted infra about refstack hosting? 19:54:36 That was on the agenda last week. 19:55:31 rocky was supposed to follow up on that .. however since she is not here.. I am going to check in with them this week 19:56:33 covered that earlier 19:56:44 any other topics to discuss? we are running short on time. 19:57:49 okay.. lets move it on out of here.. we can chat in #refstack if anything else comes up .. 19:57:50 #endmeeting