17:26:44 #startmeeting refstack 17:26:45 Meeting started Mon Jul 7 17:26:44 2014 UTC and is due to finish in 60 minutes. The chair is davidlenwell. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:26:46 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:26:48 The meeting name has been set to 'refstack' 17:27:30 roll call? 17:27:45 o/ 17:27:47 o/ 17:29:38 topics... marantis intros, meeting times again, api/swagger, wednesday f2f, open discussion 17:30:12 ok 17:30:20 should have a DefCore update too 17:30:27 okay .. sounds good 17:30:41 zehicle: do you want to introduce your contractors? 17:31:10 Hi alL, from Mirantis team! 17:31:24 hello! 17:31:26 Hello Serg_Slipushenko 17:31:38 hello! 17:32:34 they should introduce themselves. 17:32:45 I can give the background about Dell bringing them into the project 17:32:50 I think they just did 17:32:52 +1 17:33:03 Basically, Dell is helping fund work on Refstack 17:33:27 we're especially interested in helping drive the data collection (TCUP) to upload and display chain 17:33:53 awesome.. We'll be able to keep them busy in that regard for sure. 17:34:02 sounds good 17:34:08 I'm Julia, working as a QA in Mirantis, have same expiriance in Tempest 17:34:15 *some 17:34:28 since we are on limited time.. lets move on to the main topic of the timing of this meeting. 17:34:37 #topic meeting time 17:36:05 I can live with the meeting at this time if it is the only time our friends at marantis can join us. 17:36:40 but I'll warn you in advance that I hate mondays.. and I hate mornings.. but I will do my best to bring my all to each meeting. 17:37:11 I think 10am PT is the only workable time slot for our time zones 17:37:18 appreciate it 17:37:31 happy to (re)consider other days 17:37:41 No.. Im sick of moving this around 17:37:45 +1 17:37:46 We can move meeting on two hours later 17:38:11 + 17:38:24 we'll stick to this time.. like I said we've moved out meeting too much and I don't want to loose any further attendance 17:38:29 works for me 17:38:31 ok 17:38:41 I'll cope 17:38:43 ;) 17:39:17 #topic api/swagger 17:40:09 So we had decided early on to use swagger with our api.. doing so proved to be a little more work than I anticipated with flask as the api engine.. however I've found a workable solution and I am close to having it working. 17:41:04 the default way to use swagger with flask requires ussage of the flask-restless extension 17:41:13 which we aren't going to use. 17:41:34 it makes too many api design assuptions. 17:42:12 instead I am in the process of turning this into a package because it better suits our needs. https://github.com/dlenwell/flask-sillywalk 17:42:40 plus I think the name is fun.. 17:43:18 any thoughts? objections? input? 17:44:12 I'm ok with it - don't want it to take away from getting Tempest working 17:44:35 so far swagger has put me three working days off target with landing the api 17:45:04 but I think having swagger docs and an auto genereated python client are worth the spike 17:45:50 #topic wednesday f2f 17:46:23 wednesday catherine and possibly others are going to make their way up to the piston offices so that we can work out face to face how to clean up the tester code and consolidate. 17:46:58 I think Alex is planning to be there too 17:47:09 awesome!! 17:47:37 okay 17:47:42 #topic Defcore update 17:48:35 go ahead with zehicle when you are ready 17:48:45 ok 17:49:01 We're looking at at DefCore meeting this Wed 17:49:24 the last TC meeting was a bit of a surprise for me - TC decided to not name designated sections 17:49:36 wants the board to take lead on making that decision 17:49:52 I don't think it directly impacts refstack 17:50:04 I think you are correct 17:50:17 but DefCore will have to decide how to proceed. It likely impacts timelines 17:50:32 what time wednesday ? 17:50:34 TC agreed with the basics of capabliities & tests 17:50:36 TBD 17:50:38 I'd like to attend meetings 17:50:42 looks like 2 PT 17:50:43 but wednesday we have ftf 17:50:50 not related 17:51:13 if it effects refstack timelines I feel like it might be related 17:51:33 if anything, will push back 17:51:46 but that meeting will be higher level. timelines will be impacts later 17:52:08 dont distrupt dev collaboration for a defcore meeting 17:52:19 well if it comes up durring the meeting .. ping me and I'll jump on the call 17:52:24 kk 17:52:35 it's not on the agenda 17:52:41 okay 17:52:59 #topic opendiscussion 17:53:50 spec for json format changes > I'd like to just do a pull against the current files instead 17:54:12 and not try to include the flow chart at this point 17:54:26 okay 17:54:48 as long as the person who ends up having to program the thing that crunches data for score cards understands what to do with it 17:55:29 good point 17:55:40 thinking 17:56:10 I can see the point of wanting a doc for the file. I'll add a readme to the directory. 17:56:23 sounds good 18:00:16 Can I ask a couple questions? I want to clarify our(Mirantis team) goals... 18:00:33 can you pop over toi #refstack and we can talk about it 18:00:38 also want to talk about https://review.openstack.org/#/c/104908/ 18:01:17 #endmeeting