21:04:32 <zehicle> #startmeeting RefStack 21:04:33 <openstack> Meeting started Thu Mar 20 21:04:32 2014 UTC and is due to finish in 60 minutes. The chair is zehicle. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:04:34 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:04:35 <rockyg> had to find the room and forgot the exact name... 21:04:37 <openstack> The meeting name has been set to 'refstack' 21:04:38 <davidlenwell> there it goes 21:05:16 <zehicle> agenda for today? 21:05:37 <davidlenwell> code merge, documentation, front page of website, tcup 21:05:53 <zehicle> +1 21:06:00 <zehicle> #topic code_merge 21:06:33 <davidlenwell> so first on the list is this .. https://review.openstack.org/#/c/81670/ 21:07:47 <davidlenwell> RaymondWong: you -1'd this patch .. I thought you could go into it now .. tell us your main problems with it 21:09:19 <zehicle> yes please - some of these requests are going to be addressed by work that I'm doing 21:09:33 <RaymondWong> as of now, the code in the master branch works and we can kick off tempest test. if this code get merge, i don't think the code will run. 21:09:52 <davidlenwell> zehicle: can you submit a patch on top of this review that addresses them .. 21:10:00 <davidlenwell> RaymondWong: I won't merge this until we are sure that it will 21:10:10 <davidlenwell> I will personally cherry pick and test before merging it 21:10:33 <davidlenwell> zehicle: I'd like to keep things going in the same review if you can .. 21:10:41 <zehicle> I'd rather have it in trunk and merge than keep working off jmc's branch 21:10:58 <davidlenwell> zehicle: I'd rather not keep working that way .. we have this workflow for a reason 21:11:04 <davidlenwell> other wise it gets very hard to manage 21:11:14 <davidlenwell> if you need support in working in this work flow I am happy to help you 21:11:15 <zehicle> I can do that 21:11:25 <davidlenwell> thank you 21:11:45 <zehicle> I'll reach out if I have questions, I suspect I just need to pull against Josh's branch 21:12:10 <zehicle> or check it out directly 21:12:12 <davidlenwell> zehicle: you can pull against that review id 21:12:18 <davidlenwell> super easy 21:12:23 <davidlenwell> okay .. moving on ... https://review.openstack.org/#/c/81402/ 21:12:30 <davidlenwell> catherineD: 21:12:50 <catherineD> yes sir 21:13:08 <davidlenwell> i am going to work on a patch set for this review before it can get merged 21:13:16 <catherineD> that is great 21:13:21 <davidlenwell> there are some python tools that do some of the things you built all those nested loops for 21:13:46 <davidlenwell> in general .. I want you and your team to re-read the pep8 manual 21:13:55 <rockyg> +1 for upstreamed tools 21:14:16 <davidlenwell> stop using single character variable names for things .. and don't use CamelCase for function names 21:14:20 <rockyg> got a link for that manual? 21:14:31 <fcarpenter> http://legacy.python.org/dev/peps/pep-0008/ 21:14:34 <davidlenwell> http://legacy.python.org/dev/peps/pep-0008/ 21:14:42 <rockyg> Thanks! 21:14:53 <catherineD> sure .. 21:15:12 <davidlenwell> I know you guys are more java in your background and thats the standard in java .. but its considered bad practice in python 21:15:34 <davidlenwell> which is the only reason I didn't approve this one ted .. https://review.openstack.org/#/c/81653/ 21:16:01 <davidlenwell> I know it seems trivial .. but in general the openstack community strictly follows pep8 .. and we should too 21:16:17 <RaymondWong> sure. will do. 21:16:27 <davidlenwell> thank you guys 21:16:27 <catherineD> that is no problem at all .. 21:16:51 <davidlenwell> good .. I know sometimes it sounds like I am being nit picky about it .. and I don't want to discourage future contributions from any of you 21:17:08 <davidlenwell> okay .. moving right along .. 21:17:12 <davidlenwell> documentation.. 21:17:21 <rockyg> Yo! 21:17:28 <davidlenwell> someone set the topic? 21:17:32 <catherineD> Once the subunit stuff is in ... we will work withj davidlenwell: on report 21:17:37 <rockyg> #topic Documentation 21:17:51 <davidlenwell> Ithink zehicle has to do it 21:18:00 <zehicle> #topic documentation 21:18:03 <rockyg> Yah. You're right. 21:18:04 <davidlenwell> there we go 21:18:25 <davidlenwell> so rockyg would you be up for coming up to piston at the end of next week for some face to face time on documentation ? 21:18:26 <zehicle> I've got some docs changes in my pending pull 21:18:43 <rockyg> So, tomorrow or next week? 21:18:44 <zehicle> I'll see if I can split it out 21:18:53 <davidlenwell> rockyg: next friday 21:19:00 <davidlenwell> tomorrow im moving into my apartment in oakland 21:19:01 <rockyg> Sure. No problem. 21:19:02 <davidlenwell> hopfully 21:19:17 <davidlenwell> okay .. we'll set up an invite and make it official 21:19:35 <zehicle> I'm going to be in town later in April (and bring Alex w/ me this time). April 14-15. should we plan another f2f then too? 21:19:53 <zehicle> That's a Monday 21:19:54 <davidlenwell> I might be in canada .. I'll let you know 21:19:59 <rockyg> Another team just published a requirements wiki doc. I'm looking at mimicing it 'cause it looks good. 21:19:59 <davidlenwell> I think I get back on monday night 21:20:00 <zehicle> kk 21:20:17 <davidlenwell> zehicle: we can do tuesday I think 21:20:18 <zehicle> Alex could be available, but I've got RH summit on 15th 21:20:18 <rockyg> We can do a f2f with the rest of the folks. 21:20:27 <davidlenwell> sure .. 21:20:32 <davidlenwell> I can always skype in 21:20:44 <zehicle> let's plan for Tues 21:20:57 <davidlenwell> okay .. we'll settle it next meeting with times and places 21:21:23 <rockyg> Monday is definitely out for me. 21:21:28 <rockyg> So Tuesday is it. 21:21:34 <davidlenwell> done .. 21:21:36 <zehicle> 4/15 then 21:21:48 <zehicle> back to docs... 21:21:50 <davidlenwell> so between now and then I'll spit out some shiny new graphs and diagrams 21:22:12 <davidlenwell> and I'll communicate with defcore people to make sure we are meeting the use case requirements 21:22:19 <zehicle> I created a /doc directory and moved the RefStack and TCUP setup into those 21:22:37 <rockyg> Can we get them to review and update if possible? 21:22:42 <zehicle> yy 21:22:52 <zehicle> they had been part of my pull 21:23:07 <davidlenwell> we need ; a developer quickstart , install quide, high level arch. 21:23:10 <zehicle> you want me to split them or just base on topic of the existing JMC patch? 21:23:20 <davidlenwell> split them 21:23:25 <davidlenwell> try to keep reviews to a single topic 21:23:40 <rockyg> Yes. 21:23:51 <davidlenwell> we don't want to act like congress and squeeze in last minute changes to reviews 21:24:02 <davidlenwell> that are totally unrelated 21:24:08 <fcarpenter> congress does code reviews? 21:24:26 <zehicle> +1 (JMC has some doc changes already, that's why I asked) 21:24:42 <davidlenwell> zehicle: yes .. but you know how hard he is to nail down on submitting code 21:24:46 <rockyg> Yes. all those funky numbers. codification of law, I think they call it. 21:25:00 <zehicle> davidlenwell, agreed 21:25:12 <davidlenwell> so .. next topic .. front page of website 21:25:19 <zehicle> #topic front page 21:25:40 <davidlenwell> right now we don't do a very good job of really communicating what refstack is or what its used for on the website 21:25:43 <davidlenwell> we need to fix that 21:25:54 <rockyg> Yes. 21:26:14 <davidlenwell> rockyg: we can tack that on to the face to face next week 21:26:21 <rockyg> Great! 21:26:41 <davidlenwell> I'll try to steel some cycles from a designer at piston to help .. if not I'm sure we can get through it 21:27:28 <davidlenwell> zehicle: can you be available on skype that day for input 21:27:30 <rockyg> Depends on what it was written in, but these days, should be not too difficult to modify the code beneath. 21:27:49 * zehicle checking 21:27:59 <davidlenwell> rockyg: im less worried about the coding and more worried about the design astetic 21:28:06 <davidlenwell> *spelling 21:28:16 * zehicle blocked out 3/28 21:28:22 <rockyg> might not be too pretty until we get a designer to clean up. 21:28:42 <zehicle> can we do a lighthouse theme? 21:28:46 <rockyg> Unless we can come up with a mockup earler and we just add URLs/links 21:28:49 <davidlenwell> I've done my fair share of website design 21:28:59 <rockyg> Kewl. 21:29:17 <davidlenwell> so lets deal with the details/requirements for that next meeting 21:29:21 <rockyg> Get us a wallpaper photo;-) 21:29:36 <catherineD> what is the time for f2f on 3/28? 21:29:53 <davidlenwell> catherineD: lets plan for after lunch .. say 1 or 2 pm 21:29:55 <rockyg> Yeah. The more the merrier 21:30:05 <catherineD> sure .. thx 21:30:11 <zehicle> later is harder for me on a Friday 21:30:21 <rockyg> Carpool? 21:30:24 <davidlenwell> earlier is hard to reserve time at piston 21:30:31 <davidlenwell> BART 21:30:34 <zehicle> can we try to 1? 21:30:38 <davidlenwell> yes 21:30:41 <davidlenwell> 1 I can do 21:31:20 <rockyg> the carpool was for catherineD 21:31:29 <davidlenwell> rockyg: I was teasing 21:32:01 <rockyg> k. anything else on this? I can review site and list out some of my issues/suggestion in a list email 21:32:13 <davidlenwell> I think thats it on the website 21:32:18 <davidlenwell> next .. TCUP 21:32:44 <davidlenwell> lets identify what is missing for the defcore team to all be able to install and run it by next friday 21:33:07 <zehicle> I'm updating the wkii Meetings page #link https://wiki.openstack.org/wiki/Meetings#DefCore_.2F_RefStack_Development_Meeting 21:33:27 <zehicle> #topic TCUP 21:33:47 <RaymondWong> if they download the whole refstack, they can run it now without seeing the report. 21:33:50 <zehicle> I've got the basics of TCUP running 21:34:04 <rockyg> I'll probably be late for the 4/15 meeting. First DAY of Passover. and Hangover. 21:34:05 <davidlenwell> so what is missing is mostly displaying the results 21:34:26 <catherineD> yes that is why we need the subunit stuff .. 21:34:33 <davidlenwell> which means catherineDand I need to finish the parser and I need to finish the display portion of that 21:34:34 <zehicle> I have not been able to create a good config file to run the tests 21:34:36 <RaymondWong> you got the code to save the subunit in db already... so, just need to display that in html. 21:35:00 <davidlenwell> should be doable by next week ] 21:35:02 <davidlenwell> :) 21:35:50 <catherineD> Once the subunit stuff is in, we then need to map back to capacity ... 21:35:51 <davidlenwell> technically speaking if we stay on schedule tomorrow closes out the last sprint.. I think we mostly accomplished what we set out to .. however .. probably some better project manament is required moving forward 21:35:54 <zehicle> RaymondWong, I'm a little confused. what are we trying to dusplay? 21:36:08 <rockyg> We should provide a list of what someone would need and what info they need to run it against a devstack. 21:36:40 <zehicle> it sounds like you are running the code outside of the container? 21:36:56 <RaymondWong> zehicle: I am talking about running from the refstack web GUI, I can kick off tempest test, and recevice back the results stream. 21:36:57 <catherineD> we are not running tempest outside of container 21:37:17 <RaymondWong> the web GUI shows test done, but does not display the results. 21:37:19 <davidlenwell> zehicle: they are talking about displaying the results from the web gui 21:37:21 <catherineD> tempest is running inside a docker container 21:38:08 <rockyg> and I'm talking about a prereqs list. 21:38:10 <zehicle> ok, there's more working here than I was thinking 21:38:33 <rockyg> Yay, team! 21:38:38 <davidlenwell> yay .. 21:38:49 <davidlenwell> okay .. I'm happy to end now so we can all go get back to work 21:38:50 <zehicle> are there docs that show how to setup the webserver for this? 21:39:11 <davidlenwell> no .. but there will be 21:39:22 <davidlenwell> basically the readme does tell you how to get it working 21:41:41 <rockyg> That readme is all there is to it to build/run the default? 21:41:54 <davidlenwell> So we have the board room reserved here at piston for next friday from 1-3:30 21:42:47 <catherineD> I just build an ubuntus to host refstack yesterday. I can send out my note after this .. pretty simple 21:43:04 <rockyg> Thanks 21:43:06 <RaymondWong> rockyg: the readme has the command to create the db, and start refstack app server. 21:43:53 <rockyg> Yeah. It didn't look like it has enough yet to really make all the magic happen. 21:46:24 <davidlenwell> rockyg: we'll nail down a cleaner howto next week 21:46:40 <rockyg> Good. Thanks. 21:47:07 <davidlenwell> what is the mailing address list? 21:47:14 <davidlenwell> I'll invite the whole list 21:47:50 <fcarpenter> ack, i joined it but don't remember ;) 21:47:57 <zehicle> defcore-committee 21:48:10 <rockyg> fits@lists.openstack.org 21:48:17 <fcarpenter> that one! 21:48:19 <davidlenwell> thats what I was looking for 21:48:21 <davidlenwell> yes 21:48:44 <rockyg> And, it can be on the slow side. We need to make sure it gets' flushed regularly. 21:49:00 <davidlenwell> fcarpenter: can you invite that .. I don't seem to be able to add people to the invite 21:50:01 <davidlenwell> alright .. talk to you guys later on 21:50:08 <fcarpenter> davidlenwell Done 21:50:23 <rockyg> Thanks everyone. 21:50:31 <zehicle> ok, wrapping up 21:50:35 <zehicle> #endmeeting