22:16:57 #startmeeting RefStack 22:16:58 Meeting started Thu Feb 13 22:16:57 2014 UTC and is due to finish in 60 minutes. The chair is rockyg. Information about MeetBot at http://wiki.debian.org/MeetBot. 22:16:59 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 22:17:01 The meeting name has been set to 'refstack' 22:17:12 OK. We're Started. 22:17:25 CatherineD is here 22:18:33 #link http://eavesdrop.openstack.org/meetings/refstack/2014/refstack.2014-02-13-22.07.html 22:19:17 Roll call again to get it in the minutes: catherineD? 22:19:30 Here 22:19:30 RaymondWong 22:19:33 Anyone Else? 22:19:37 o/ 22:19:46 :) 22:19:58 Excellent. Let's start with Status. Tcup? 22:20:07 #topic Tcup 22:20:52 Catherine, Raymond, Alex_H, any status on Tcup, tempest, etc? 22:21:05 t-cup (Docker) working last step is to call API and script to ship data from container to Refstack 22:21:40 Now configure with a number of testcases that only take 33 sec to finish for debug 22:21:43 Cool. so this is the connect with Davidlenwell s stuff 22:21:56 yes 22:22:00 Hi everyone 22:22:37 Hey, davidlenwell, did you catch the last from catherineD? 22:23:17 catherineD and I synced earlier today .. so we should be on teh same page 22:23:26 Where does the code live? 22:23:45 And can anyone build it? 22:24:00 Alex has the code, but he needs direction on where to put it 22:24:20 I instructed him to make a git hub repo weeks ago 22:24:34 he may need more help, where do you want it 22:24:44 And that was an action item from last week: Will it go to stackforge or directly into openstack? 22:24:52 neither for now 22:24:54 I can work w/ him 1x1 22:25:22 I'd like it if it was a stand alone repository called docker-tempest or something to that effect 22:25:45 we could do that 22:25:50 catherineD and I talked earlier about keeping scripts in the refstack repository for now 22:25:56 what about refstack-tcup? 22:26:01 there is a scripts directory I believe .. it could just be put there 22:26:27 davidlenwell, I think I'd rahter keep it in the refstack for now 22:26:35 I like that 22:26:38 OK. I really think that we should get it into stackforge. A colleague I plan to introduce next week can help tie it into the CI. We can do no voting until we call it. Until then, one of the existing refstack repositories. I agree with refstack. 22:26:44 so, it would be controlled by the gates 22:26:47 rockyg, +1 22:26:47 so what he should do is fork refstack from me 22:26:55 I type too much. 22:26:59 I will show him how to do that 22:26:59 rockyg: we will .. 22:27:15 zehicle_at_dell: then have him add the script .. commit and send a pull request 22:27:25 Rigjt now we are working on building config file from default file .. once that is done any one can run t-cup 22:27:28 :) time he learned how to do that anyway 22:27:32 Great. 22:27:42 rockyg: I absolutely want this in stackforge .. but we are a little too dissorgiized just yet 22:27:49 David should we show the doc that we discuss this morning .. 22:27:53 I am hoping by the begining of march we can do that 22:28:16 catherineD: perhaps . 22:28:28 Raymond could you ping the link ... 22:28:34 catherineD and I had a phone conversation earlier and identified the area they can contribute to 22:28:44 that way we can ping point the script that need to be written .. 22:28:59 Jerry, the guy I mentioned, just got one of our projects working in Stackforge. He shephearded along from just a repository to running unit tests now. voting but not blocking. 22:29:18 we don't have tests yet 22:29:27 https://drive.google.com/file/d/0Bw1YqO1DEg6SbUxwQ1NraFpFaXc/edit?usp=sharing 22:29:32 and we are about to rewrite a lot of things .. which I guess is fine to do in stackforge 22:29:42 So, no need for the test stuff, but still CI. 22:30:46 Just skimmed the doc. I'll review it this week and maybe comment. Looks good, at the high level, though 22:31:48 How about we get the current code all into repositories and the structure we want and when CatherineD, RaymondWong and davidlenwell say it's good enough, we do the transfer? 22:32:04 rockyg: +1 22:32:34 #ActionItem Tcup and API devs provide repository location and date to transfer to Stackforge. 22:33:20 We'll need to know how many repositories and names to go with them for stackforge. 22:33:36 if we keep it all in the same repo that gets easier 22:33:44 +1 22:33:49 we can always split things off later on 22:33:57 Ready for next topic? API and DB okay? 22:34:29 sure 22:34:44 #topic API and DB 22:35:45 I kinda hope someone is typing status or something in;-) 22:36:13 So the api and cb are in the same state as last week .. 22:36:43 I was told I could stop working on this spike I've been on .. then the next day our ceo said no dice .. get back on it .. honestly its stressing me out a bit because refstack is my baby 22:37:45 davidlenwell: OK. It looks like a review of the API calls in the google doc posted above would be good if you haven't already. That gives us some;-) 22:38:38 yeah .. we talked about that one the phone today with catherineD and RaymondWong... some of those aren't needed .. and we've planned some facetime next week while I am in town.. so i imagine we'll nail them down 22:38:49 I think as long as you can keep providing some mentoring to the rest, we're doing fine. 22:39:00 yeah .. progress is happening 22:39:04 which makes me happy 22:39:16 Ready for next topic? Documentation ok? 22:39:20 sure 22:39:32 #topic Documentation 22:39:41 let's add a topic for meetings 22:39:45 We discussed with David. In the Google doc we will work on the Test and Results processsing but need the dependency section ... 22:40:22 Great. I'm itching to glue all these bits of information together. 22:41:05 If it's OK by everybody, I'll start a RefStack page on the OpenStack Wiki and start some wordsmithing and capturing all the links. 22:41:09 I am all for writing as much documentation abotu this stuff as possible .. and we can go in depth but what I feel like is missing is the intro to refstack higher level document 22:41:19 rockyg: please do 22:41:27 I created a stub for that last meeting 22:41:43 Agreed. Cool. Not the one under governance? 22:41:53 #link https://wiki.openstack.org/wiki/Governance/DefCoreCommittee/RefStack 22:42:07 I saw the governance one .. not one for high level engineering .. or intro to 22:42:59 OK. I think Governance is the even higher level. Mission, etc. I'll link more technical homepage to that one so once this one is found, you can follow to techy stuff if you want. 22:43:20 let's start w/ something and we can divide as we go 22:43:28 I'll also put the skeleton into the governance one to match what is expected. 22:43:28 sounds good 22:43:30 governance will be tied to DefCore, so that should be interested 22:43:32 interesting 22:43:54 yeah, been following that discussion;-) 22:44:13 OK, ready for meeting topic? 22:44:20 sure 22:44:31 #topic Meetings 22:44:53 are we talking about meetings like this one .. or some face time in the bay area? 22:44:55 BTW, since Raymond will be working on Tempest Result processing ... Has DefCore had any mapping among capability and testcases? 22:45:09 yes 22:45:20 We need a modlel to start coding 22:45:45 #link https://docs.google.com/spreadsheet/ccc?key=0Av62KoL8f9kAdEJTWnFWejJySnFXZmxWdnowTDhUSVE&usp=drive_web#gid=0 22:45:56 we have the capabilities map per test 22:46:05 mapping: there are a couple of PTLs that will be starting on that real soon now 22:46:09 working on picking the must-pass (that's a lot of work) 22:46:23 would be GREAT to have help 22:47:38 You betcha. How about we have a meeting and pick out some obvious need to haves and start building strawman model? 22:48:04 rockyg, yes! I will set one up. We're overdue to a criteria meeting 22:48:17 will likely be 2 hours next week. 22:48:27 what is column I in the spreadsheet 22:48:32 you're welcome to review in that spread sheet 22:49:03 # of tests in the capability (I think) 22:49:09 I did J->W 22:49:57 I'm not seeing *any* of those columns ;-( 22:50:04 :-( 22:50:50 see? Score Stable Complete Discoverable IaaS Tools Clients Foundation Future Doc'd Legacy Cluster Base Public 22:50:55 row 2? 22:51:27 Doh! The grey tabs at the bottom. 22:52:28 So this original spreadsheet was from me. Column G through W was added. We just need to understand what it means so that we can process the test results. We will take a look and send out question in email 22:52:49 yy, I added them 22:53:02 sorry, troytoman-away added G-I 22:53:32 perfect we need this to start coding once we understand it ... 22:53:46 #ActionItem Criteria meeting to follow weekly meeting on 2/20 22:54:31 We're meeting at Piston on 2/19 (Still on davidlenwell?) and can also do some prep work. 22:54:49 great! can we have a dial in? 22:54:51 let me email the group about that later today .. I need to make sure I have the conf room that day 22:54:54 of course 22:55:13 but I am pretty sure we can make it work .. refstack is very important to piston 22:55:29 If you don't we could do it down in Santa Clara. I can get a room. 22:55:39 I'm sure we'll be fine 22:55:59 I just confirmed with the schedule .. should be fine 22:56:07 we also have the 3/3 meeting 22:56:09 Great, I think that will be productive .. 22:56:11 I'll email an invite 22:56:15 Better food up where you are. 22:56:16 davidlenwell, is Piston hosting that one too? 22:56:28 zehicle_at_dell: not sure on that .. 22:56:42 I haven't even booked my travel for that one yet 22:57:10 Let us know. We can scrounge rooms down the peninsula way. 22:57:21 I'm planning to be there 22:57:36 I'll plan my travel next week while I am up in the office 22:58:04 we'd be happy to host .. but it would depend on the dead count and scheduling 22:58:25 Great! Micky Hart gonna join us? 22:58:25 zombies count in that? 22:58:27 head count 22:58:42 I always count zombies 22:58:47 :-) 22:59:00 And members of the band;-) 22:59:27 I'll check w/ Josh 22:59:44 we're planning a more general DefCore meeting at the same time 22:59:51 josh and I also are participating in an ironic sprint thing that is supposed to be that week also 22:59:52 we are at the Top of the hour 23:00:00 OK. Anything else for meetings? I think I can capture what we've got here into more cogent notes. 23:00:12 I think we've covered everything 23:00:35 Dang! I wanted to talk about all these other efforts that are also planning to use Tempest (Rally, etc) and whether there might be synergy. 23:00:35 I'm ok 23:00:44 thanks all, sorry about the late start 23:00:45 thx everyone! 23:00:46 I'll put it on the agenda for next week. 23:00:54 sounds good 23:01:01 Anything else? 23:01:15 #endmeeting