17:07:23 #startmeeting Refstack 17:07:24 Meeting started Thu Apr 10 17:07:23 2014 UTC and is due to finish in 60 minutes. The chair is rockyg. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:07:25 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:07:27 The meeting name has been set to 'refstack' 17:07:41 roll call 17:08:10 #topic progress updates 17:09:08 here but probably not of much use! 17:09:52 :-) catherineD, tedchang? 17:09:56 here 17:09:58 Here 17:10:27 fcarpenter waiman 17:11:09 pinging waiman 17:12:05 I guess I'll start. Been looking at sphinx and trying to get it to document the code. It finds the modules and sets up the docs partially, but won't do things like classes and stuff. 17:12:46 Plus, it won't capture comments, only stuff in the source files that have doubledouble-quotes. 17:13:20 And I expect I'll need to migrate to oslosphinx once I do get it working properly. 17:14:16 So, so far I have docs with headings but no content within the headings 17:15:06 That's it for me. catherine|2 and team? 17:15:23 ic Our practice is using doubledouble-quites for headers and # for in-line 17:15:42 We have been working closely with David .. 17:16:20 mostly updating to get ready for gearman 17:16:30 Yeah. I'd like to get at least some of the # stuff to be incorporated, but I don't see a way with the sphinx maekup 17:16:35 Raymond is stuck in traffic 17:17:01 Great. Gearman is going to be key, I think, for demos and discussion. 17:17:52 Do we have a working tcup implementation my colleagues can try? I thought we were there from what I've seen go by in reviews. 17:17:53 Raymond also working on enabling backend for report .. right now he is writing some very simple front-end 17:18:46 front-end for report? 17:19:20 yes but that is just sample code ... our focus is the back-end methods .. 17:20:14 Good. The back-end *is* the important part. Just need the simple to show human parsable results right now. 17:20:25 Lot's of coding discussionamong Ted, Raymond and David in the past few days .. 17:20:43 rockyg: exactly 17:20:54 Good. 17:21:26 btw, rocky the current implementation is using tcpu. 17:21:59 I've tried to extract the flows from the urls tedchang provided last week. Especially the man page. All I can get are images, though. 17:22:12 tedchang tcup ;-) 17:22:40 tcpu used to be a vms command to show realtime cpu usage 17:23:36 I'm putting the flow images into the architecture section of the wiki. Either links or images. I've done both for the moment. 17:23:50 hello guys 17:23:52 rockyg: Thx 17:24:06 Hey, Praveen! any staus updates? 17:24:08 i have tested the latest code,it just builts the docker container 17:24:09 praveen_dell: Hello 17:24:30 i am updating tcp.md file,will submit as a patch 17:24:43 excellent. 17:25:44 praveen_dell, read the roll-up. If you have any questions, ask as we move along. 17:25:59 sure 17:26:43 I think we've got the progress doc'ed here. What should the next topic be? 17:28:04 #topic Summit 17:28:32 wha is plan to collect data from various clouds? 17:28:49 We've got the proposal fleshed out. Thanks, guys. 17:29:09 rockyg: see the update .THANK YOU! 17:29:37 catherine|2: I thought DB. I think the the DB needs more thought and design discussion. 17:30:05 before we go to db, quick question: who will be at the summit? 17:30:19 yes that is one of the topic we have been discussing with David .. 17:30:54 We can only go after our session is approved 17:31:23 I am expecting to be there, bu my boss is travelling at the moment. 17:31:36 where is the summit? 17:31:46 Session aproval is still at least a week awy, I think. 17:31:57 Atlanta. 17:32:08 Georgia, USA 17:32:18 umm,no chance for me to attend 17:32:20 so far 17:32:27 Dang. 17:32:29 Refstack session link http://summit.openstack.org/cfp/details/197 17:33:16 are you guys planning to demo Tcup project? 17:34:03 I'm wondering if we should propose any others. Like some open discussions around refstack and defcore selesctions 17:34:45 We need a demo for the summit. Even if it's very choriographed. 17:34:55 rockyg: make sense .. 17:35:04 1+ 17:35:21 where would we demo? During the session? 17:35:30 Yes. 17:35:45 Hi 17:35:48 Maybe that should be a topic for next week ... when everyone is here 17:35:51 I can't open summit link 17:35:58 Hey davidlenwell! 17:36:14 I'm about to shut off my phone 17:36:28 Flight about to depart 17:37:03 you can read after. mostly status and there will be some action items 17:37:10 davidlenwell: Hello , so not much time? 17:37:48 davidlenwell: anything you want to say before you sign off? 17:38:06 Review my code ;) 17:38:17 Will do;-) 17:38:36 Although the others will be better for it;-) 17:38:46 davidlenwell: Raymond did ... and we also need to make some update .. 17:39:14 I'll take an action to put together a strawman for demo we can modify. 17:39:26 let's move to db topic 17:39:31 Ted also review 17:39:43 #topic Database discussions 17:40:35 I assume part of the discussions have been on the added complexity of private data vs public data? 17:42:59 is that mean user who are pushing tempest results to refstack UI can only compare with their previous set of results? 17:43:52 people need to be able to say whether data is "publishable" or not 17:44:13 okay 17:44:34 And prople can submit unofficial data tha could be used for aggregation, but can't be individually visible 17:44:43 ^people 17:46:13 And I would expect that people could elect to thow out the data from a specific run. Obviously right after the run completes, but what about some time after more runs have occurred? 17:47:02 catherine|2: are the discussions with davidlenwell on IRC, skype or phone conference? 17:47:47 mostly on IRC #refstack or in the review comments 17:49:05 Thanks. Maybe we should schedule a meeting so Praveen and others could join the discussion? Maybe once the design is closer or do you think more heads could help move it along? 17:50:02 II'm sure zehicle_at_dell would also like to contribute. 17:50:44 rockyg: +1 also for next week we should discuss about the summit session ...so we can prepare .. 17:51:00 Yes. 17:51:25 Thank you! 17:51:59 #action schedule meeting to discuss DB design based on privacy/security/use cases requirements 17:52:47 #action agenda for next week to include topic on summit session - topics, demo, etc 17:53:05 1+ 17:54:42 praveen_dell: what are you utc hours of availability? I think we at least need audio and either screen share or an etherpad 17:55:55 up to 6pm utc should be fine for me 17:56:52 So, 1800utc, which is 11am pdt 17:57:43 correct 17:58:26 I'm thinking 1700 utc to start, again. I'll get davidlenwell's availability and zehicle_at_dell and I think we might want joshuamckenty 17:59:24 1+ 17:59:34 when are you planning the meeting? 17:59:52 I think part of the key here is this needs to be more of a traditonal database than most of the ops dbs in OpenStack. So design is much more critical. 18:00:08 Not before Wednesday. 18:00:13 ok 18:01:21 is there anything to discuss now? 18:01:28 zehicle_at_dell has some schedule complexities next week, as does davidlenwell (still in Canada), so maybe mailing list to work out meeting times. Is the list even working? 18:02:19 Nope. Wrapping up. Last call for getting things on agenda. any more discussion should move to #refstack. 18:03:56 Hearing none, #endmeeting 18:04:06 yeah 18:04:16 #endmeeting