18:56:41 #startmeeting refstack 18:56:42 Meeting started Mon Mar 30 18:56:41 2015 UTC and is due to finish in 60 minutes. The chair is davidlenwell. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:56:44 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:56:46 The meeting name has been set to 'refstack' 18:58:54 o/ 18:59:08 o/ 18:59:17 o/ 18:59:56 for the record I am going to repeat this.. officially .. I hate day light savings time.. 19:00:04 o/ 19:00:21 davidlenwell: ++ 19:00:25 o/ 19:00:29 well lets get started.. 19:01:05 Today's agenda: 1) Status of implementation of agreed action items of Feb f2f meeting. 2) refstack.net / ui / access to servers.. 3) Any design session for refstack for Vacouver summit 4) Pending review 19:01:43 o/ 19:02:21 #topic Status of implementation of agreed action items of Feb f2f meeting. 19:02:31 #link https://etherpad.openstack.org/p/refstack_f2f_feb_2015 19:03:24 o/ 19:03:29 I don't think we need to rehash anything in this list by typing it into chat.. but I'd like everyone to take a minute today and review our status and make sure anything waiting on you is up to date. 19:04:33 any comments or questions? 19:05:47 okay .. lets move on.. save anything about work items for the end durring open discussion 19:05:49 #topic refstack.net / ui / access to servers.. 19:06:13 Catherine and I have been planning what to do with the ui end of our story.. 19:06:59 at the moment.. the short plan is to create a simple web ui.. starting with a home page that is rendered from the readme.md file in the root of refstacks repository. 19:07:17 pvaneck: is prototying the code for that currently.. 19:07:33 pvaneck: do you have any updates on that? I know we just talked about on friday. 19:08:10 right, I've been looking at storyboard-webclient for an idea on structure and angularjs usage 19:08:29 but nothing concrete just yet 19:08:44 fyi, it looks like storyboard is being mothballed (since pvaneck mentioned it) 19:08:45 I think that is a good place to start.. however feel free to use the angular beginer manual and make some of your own choices 19:09:07 yes.. hogepodge .. I had an in depth conversation with mordred about that over the weekend.. 19:09:07 yes, haha, going through some tutorials 19:09:08 pvaneck: Do you have any experience with angularjs? 19:09:37 sslypushenko__: only started lookning at it recently 19:09:44 they havn't fully pulled the trigger on that yet .. but they don't have the development staff to being it to the level we need it to be.. so they are exploring options. 19:09:55 pvaneck: :( 19:10:07 sslypushenko__: are you expieranced with angular? 19:10:17 No 19:10:25 I was hoping to broaden pvaneck's skills a little 19:10:30 its pretty easy to pick up 19:10:51 interesting enough to learn 19:10:56 angular + bootstrap is a pretty powerful mix when making front end 19:11:07 I wiil see soon) 19:11:21 okay .. lets move on and talk about hosting 19:11:43 previously we planned to create a script that keeps refstack.net up to date with trunk code 19:12:19 it would be my preference for no user to ever log into the refstack.net web server.. in fact I'd like the entire hosting exp to be as automated as possible.. 19:12:27 davidlenwell: I think we have story writeen for that ... 19:12:34 We need some automatical deployment system 19:12:34 we do 19:12:53 yes .. which as I remember I volunteered to take on before I ran into employment issues.. 19:13:08 Maybe cores can have access in case of automation failures or needed updates? 19:13:13 I will pick that back up this week.. plan to have it working on monday 19:13:30 hogepodge: indeed .. however .. I like to get it off my personal hp cloud account as soon as we can 19:13:43 the plan has always been for infra to host this for us.. 19:14:08 +1 on getting off personal hosting ... 19:14:09 they keep things up todate differently than I woulld .. again storyboard is a good example of this .. they merge stuff and it goes live 19:14:38 we need a plan to move refstack.net to an official place ... 19:14:58 the question is still is Defcore going to use us as the official testing channel or not? 19:15:26 if they are then I can see an argument for having infra host us.. if they are not then we should explore other options and plan for a way to fund or get donated hosting 19:15:45 I'm sure we could donate an instance for this 19:15:51 thanks clee 19:15:53 (DreamHost, I mean) 19:15:57 clee: thanks 19:15:59 yes .. I gathered that 19:16:24 in case infra doesn't want to host it, and nobody from Rackspace volunteers :) 19:16:44 Before the Vancouver summit, no. Our plan is to have vendors submit test results manually as there are still outstanding account and usability needs refstack needs to address. Plus there are a small set of flagged tests that need to either be explicitly excluded or manually checked. 19:17:10 is there a list of those someplace? 19:17:22 sorry I've been checked out of the defcore meetings lately 19:17:40 The flagged tests are just now being proposed. 19:17:44 hogepodge: where do they submit result to? 19:17:55 #topic surprise addition Defcore update 19:17:55 Me. 19:18:16 hogepodge: so you will submit refstack? so you can view? 19:18:19 hogepodge: can you give us a general update from the foundation and defcore please.. 19:19:13 The board approved the latest Defcore capabilities, 2015.03. Capabilities are now identified by date of approval rather than release to better track versionless Tempest and reduce confusion about what tests can be run against. 19:19:37 The new testing standards go into effect today for new products. 19:19:57 Last week I was in NYC with the openstack-qa team working on patching problematic tests and finding other workarounds. 19:20:12 hogepodge: what is the new testing standards? 19:20:43 catherineD: To qualify for the mark new products need to pass defcore 2015.03 or later tests (2015.05 expected to be approved in Vancouver) 19:21:12 good to know 19:21:31 Question: is 2015.03 a proposed or final? 19:21:40 Test failures from network attachments have been fixed. Some outstanding work on accounts needs to be done. 19:21:42 hogepodge: got it thx ... later we can talk about this ... Paul just update refstack to use 2015.03 https://review.openstack.org/#/c/168512/ 19:22:03 Rockyg: 2015.03 is final, with flagged tests under review based on recent work. 19:22:35 Thank hogepodge.. its important we stay informed.. 19:22:49 Out of the 127 required defcore tests I can pass over 110 of them on a non-devstack cloud, and around 10 tests are known false negatives. 19:23:05 (don't have exact numbers in front of me) 19:23:12 hogepodge: Thanks 19:23:39 okay.. lets move on for now.. . 19:23:46 #topic hosting 19:24:19 lets revisit a perminate hosting solution next week.. I'll talk to some folks and see what our real options are and we can make an imformed decision 19:24:30 #topic design session 19:24:54 hogepodge: are there any DefCore session that you are aware of? 19:25:49 Not that I'm aware of. We can find out in the next DefCore meeting. 19:25:50 davidlenwell: sorry should wait until open discussion for the question ... 19:25:59 kk 19:26:02 hogepodge: thx 19:26:07 actually I think that was on topic 19:26:40 usually I get an email with a call for design session submission .. however I have not seen it yet.. Does anyone know the submission deadline? 19:26:50 or the window.. 19:27:26 No email so far. A bunch of projects have announced their sessions etherpads, though. 19:28:19 well lets get ours started.. I think we need another session with q/a 19:28:32 I want to talk about cleaning up after tempest with them directly 19:28:44 I have an idea for that. 19:28:49 oh? 19:29:07 and idea for a solution or on the submission copy? 19:29:16 s/and/an 19:29:16 I think that test resources should be postfixed with the test idempotent_id, that way anything not cleaned up can be paired to a test immediately. 19:29:51 (or n bytes of the idempotent id for brevity, where n helps guarantee againt collision) 19:29:52 we have a story for that https://storyboard.openstack.org/#!/story/2000117 19:30:27 hogepodge: should we plan for a design session? 19:30:39 okay . 19:30:41 #link https://etherpad.openstack.org/p/refstack-qa-vancouver-design-session 19:30:44 lets put it here 19:31:16 davidlenwell, hogpodge: ++ 19:31:18 lets try to get most of our copy in this etherpad this week 19:31:32 so when submission open we can get it in without rushing it 19:32:04 ++ we can also review next week 19:32:07 checking on that 19:32:10 awesome 19:32:13 thanks hogepodge 19:32:24 okay for the sake of time lets move forward.. 19:32:28 #topic Pending review 19:32:52 let discuss https://review.openstack.org/#/c/168512/ first 19:33:08 this one updates refstack to use 2015.03 .... 19:33:35 catherineD: let me get this on my dev box and see it with my own eyes before I vote on it in review 19:33:54 I have one discuss item for this one ... 19:33:58 okay 19:34:03 lets hear it 19:34:21 previously, the capability file reside in refstack ... now 2015.03 is in defcore ... 19:34:40 do we mirror the file? if so how do we know it is update to dae? 19:34:43 date 19:35:08 there are a number of ways around this.. I'll leave some comments with some examples for paul 19:35:40 +1 ... or also hogepodge: how do we want to display the flagged test? 19:36:01 sill the flagged tests be listed in the json file? 19:36:30 the flagged tested are listed in both "flaggeg-test" and "test" 19:36:34 The decision by the committee was that flagged tests are a subset of approved tests 19:36:35 okay 19:37:18 hogepodge: how do we want to flagged the test in the UI is my question? Currently UI only display test .. 19:37:36 I'd like to discuss in channel in greater detail on what that means exactly .. lots of questions.. perheps I just need to call rob and brain dump 19:37:54 ok... next IRC meeting? 19:38:02 It's kind of a funny spot. Some tests are flagged because of bugs in tests, others are flagged because they don't belong. There's no way distinguish between them. I think they should be highlighted in some way in the UI. 19:38:05 or shoudl we have a separte meeting .. 19:38:32 lets have an entire longer discussion about this topic .. dont' want to rush to a decision here 19:38:43 any other pending reviews? 19:38:59 separated 19:39:35 I'll catch up on the review queue this afternoon.. 19:39:38 Vladiskuz --> https://review.openstack.org/#/c/166247/ 19:39:59 I am reviewing it .. 19:40:30 I'll make some refactoring, but in general it's work 19:41:09 great .. 19:41:18 lets move into open discussion 19:41:22 practically we have about 4-5 weeks to Vancouver ... we should plan to have all Fef f2f items implemented by mid April? 19:41:46 as many as we can .. we might need to do some reprioritizaton 19:41:59 catherineD: lets have a phone call later in the week and go over the items one by one 19:42:06 ok 19:42:30 So many of you might have noticed my absense the last couple of weeks.. 19:42:59 I've been on so many interviews and phone interviews in the last couple of weeks.. that many of them are a blur.. 19:43:27 I spent a lot of time searching for a new employer who would genuinly support my efforts on refstack and upstream in general.. 19:43:54 That search has come to and end.. in the middle of the month I'll officially be starting with Akanda.. 19:44:01 oh, sweet! 19:44:05 davidlenwell: congrats :) 19:44:08 thanks .. 19:44:25 davidlenwell: congrats .. 19:44:28 for those who don't know akanda is a spin off company from dreamhost 19:44:29 Congratulations! Never heard of them. What do they do? 19:44:33 Good news! 19:44:47 they are productizing some stuff dreamhost has been doing.. 19:44:58 networking related.. 19:45:19 my new boss insures me that they thing refstack is important and want to support my efforts here.. 19:45:26 Congrats! 19:45:52 thanks all.. I'm very happy with the decision .. 19:46:12 being able to continue my work here was a large part of that entire change.. 19:46:47 I don't offically start for two weeks.. but I will be active on refstack related things.. feel free to reach out to me with anything.. 19:47:13 anyone have anything else to discuss? final thoughts .. questions? 19:47:29 davidlenwell: what're you gonna do for two weeks? Europe trip? :) 19:47:41 davidlenwell: refstack :-) 19:47:57 My son is turning 12.. we're going to be building a robot with my 3d printer and some arduino stuff 19:48:04 he's also on spring break 19:48:09 nice! 19:48:11 I think we really need to put together a prioritized list of where/how we need to interact with QA design/code efforts 19:48:14 which is why I'm delaying my start 19:48:27 sounds like a pretty good reason. 19:48:49 Rockyg: thats why we started etherpad.. lets dump our initial thougths on that . we'll get them more concise over the comming weeks. 19:48:53 Rockyg: +1 19:49:25 do we want to vote on a date and time for the phone call this weeks? 19:50:00 catherineD: sure .. when is good for you? 19:50:02 phone call? 19:50:04 we could do it today if you want 19:50:29 hogepodge: not a big one.. I just to verbally review the action items from our face to face and re-priorities 19:50:35 hogepodge: earlier we talk about UI ....and davidlenwell: suggest a phone call will be better 19:50:38 so we have realistic goals for the summit 19:50:49 who else is gonna be at the summit? 19:50:54 I will be 19:50:58 * clee has already booked his flight and airbnb 19:51:26 Is this open topic? 19:51:30 yes 19:51:44 we have 9 more minutes.. bring up anything 19:51:52 Catherine and I had our talk for testing accepted. We'll be speaking on Tuesday at 11:15 at the summit. 19:52:12 Yay! 19:52:14 awesome! lets make sure we keep promoting that here and on other channels 19:52:32 I'm sure you'll pack the house 19:54:27 okay folks.. lets move any further discussion in #refstack.. catherineD I'll pm you about times we can chat 19:54:29 for the phone call let's do it on Wednesday ... let every one has a chance to look at https://review.openstack.org/#/c/168512/ 19:54:36 sure .. 19:54:39 lets do that 19:54:48 wednesday works for me 19:54:56 #endmeeting