19:15:34 <davidlenwell> #startmeeting refstack 19:15:35 <openstack> Meeting started Mon Oct 20 19:15:34 2014 UTC and is due to finish in 60 minutes. The chair is davidlenwell. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:15:36 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 19:15:39 <openstack> The meeting name has been set to 'refstack' 19:15:59 <catherine_d> o/ 19:16:19 <davidlenwell> not a lot .. my head is down right now on the api.. should be usable and on the domain name in the next couple of -days.. then I'll turn my focus to content for website and wiki 19:17:17 <davidlenwell> mainly I need to know who I am blocking today .. so I can make sure everyone is on track 19:18:07 <sslypushenko__> Please, keep me on track... 19:18:53 <catherine_d> sslypushenko__: I assign a new refstack-client story for you to implement ... are you OK with that? 19:18:58 <davidlenwell> sslypushenko__: when is our time with you up ? 19:19:03 <sslypushenko__> Yep! 19:20:42 <sslypushenko__> I guess to middle of november 19:20:53 <davidlenwell> okay .. good to know 19:21:22 <davidlenwell> I am going to try to spend the first half of this week getting my head above water and planning what goes next. 19:22:40 <davidlenwell> sslypushenko__: what hours are you generally available? 19:23:01 <sslypushenko__> Let me calculate) 19:23:05 <davidlenwell> I want to coordinate with you over the next couple of days to land tests for the api that depend on my api functions landing. 19:23:30 <sslypushenko__> You can send me email any time you want 19:23:57 <davidlenwell> I would preffer to discuss things in channel in irc 19:25:43 <sslypushenko__> If we need a meeting we can schedule it to 20:00 UTC 19:26:08 <davidlenwell> okay 19:26:22 <davidlenwell> then if I want you in channel I'll ping you and also send you an email 19:26:35 <sslypushenko__> Okay! 19:26:37 <davidlenwell> catherine_d: are you blocked on anything other than the api ? 19:27:01 <catherine_d> so from refstack-client point of view ... once we have the upload API .. I think we are good .. we have 3 stories to implement (1 by sslypushenko__: and 2 by Paul) ... sslypushenko__: 19:27:15 <davidlenwell> excelent 19:27:34 <catherine_d> so the testing you mentioned is testing from refstack side or refstack-client ? 19:27:44 <davidlenwell> refstack api side 19:27:48 <davidlenwell> not the client 19:27:55 <davidlenwell> these are unit tests for gate mostly 19:28:01 <catherine_d> ok 19:29:00 <sslypushenko__> davidlenwell : You can find it usefull https://review.openstack.org/#/c/115939/ 19:29:12 <sslypushenko__> For API testing 19:29:16 <catherine_d> as said before refstack-client side looks good .... bur from refstack side ... other than API .... we need the site up .. that means we need content .. 19:30:02 <rockyg> ++ 19:30:04 <catherine_d> like layout of the homepages and its links ... 19:30:26 <davidlenwell> thats my only focus after landing the api 19:30:35 <davidlenwell> I am the only one among us with design expierance 19:30:50 <davidlenwell> I will for sure have it ready for paris 19:30:57 <davidlenwell> even if i am finalizing it on the flight over 19:31:26 <catherine_d> I know but from content (to render) what do we need ... 19:31:44 <davidlenwell> to render data from test results you mean ? 19:31:45 <rockyg> can we have a barebones skeleton with at least links before the flight, please? So we can at least test where things go to existing stuff? 19:31:46 <catherine_d> I am concentrating in reviewing the havanacore list ... 19:31:52 <davidlenwell> rockyg: sure 19:32:02 <davidlenwell> its going to be a one page scoller 19:32:15 <catherine_d> do we need her to work on the Icehouse core? etc ... 19:32:45 <davidlenwell> that can only be approved by defcore.. am I wrong? 19:32:53 <davidlenwell> where is rob when we need him? 19:33:58 <rockyg> He's on the board meeting call, doing the defcore preso 19:34:40 <davidlenwell> well the capabilites and the tests the cover them is something that we've agreed that someone from defcore must plus 1 before merging 19:34:51 <rockyg> I think there will likely be a first pass on getting capabilities with grouped tests listed so the scoring can start before or during Paris 19:35:05 <davidlenwell> I would hope so 19:35:22 <catherine_d> now once we have the core and API is available to upload data ... we we need to work on a piece of code to calcykate score ... 19:35:23 <rockyg> Right. There needs to be the list, then scoring, then TC and board aproval, then merging 19:35:36 <davidlenwell> not sure the tc cares 19:35:49 <davidlenwell> but yes 19:35:56 <davidlenwell> thats supposed to be the order for icehouse 19:36:06 <davidlenwell> we are at their mercy with timing 19:36:26 <rockyg> TC gets to verify test cases for capabilities 19:36:37 <rockyg> Otherwise, they want everything;-) 19:36:46 <davidlenwell> I'll stay out of the politics 19:37:16 <davidlenwell> just fyi.. the refstack position on this stuff is to stay agnostic and just creat testing tools that can be used by these groups. 19:37:17 <rockyg> Icehouse may be easy compared to Kilo if the functional tests get split out. 19:37:34 <davidlenwell> its also way to early to think about kilo 19:37:57 <rockyg> Yup. So all the capabilities grouped will be usable on RefStack. Whether part of Defcore definition or not, right? 19:38:17 <davidlenwell> refstack doesn't care about the capabilites or how they are mapped 19:38:23 <davidlenwell> to tests.. 19:38:26 <davidlenwell> at least not right now 19:38:55 <rockyg> good enough. Or as we used to say in band, close enough for jazz 19:39:01 <davidlenwell> lol 19:39:28 <davidlenwell> our main goal is data collection for interopability research 19:39:40 <davidlenwell> defcore is just using our tools.. 19:40:00 <rockyg> ++ 19:40:13 <davidlenwell> so is anyone else blocked on anything? 19:40:19 <catherine_d> sslypushenko__: your question earlier abou out put find demo you mean this http://sergslipushenko.github.io/capabilities.html 19:41:29 <catherine_d> I have reviewed http://sergslipushenko.github.io/capabilities.html.. and that patch https://review.openstack.org/#/c/111758/ was merged .. 19:42:07 <sslypushenko__> no 19:42:19 <catherine_d> davidlenwell: nothing blocked for now other than API which we have discussed /// 19:42:38 <sslypushenko__> I meant this page http://sergslipushenko.github.io/output.html 19:43:21 <sslypushenko__> Rob asked me to make prototype to refstack test result page 19:43:29 <davidlenwell> thanks sslypushenko__ 19:43:46 <davidlenwell> can you commit that to the codebase in the templates directory? 19:43:48 <davidlenwell> as is 19:44:04 <sslypushenko__> sure 19:44:30 <sslypushenko__> I can turn it to flask template 19:45:05 <davidlenwell> that would be excelent 19:45:14 <davidlenwell> please do .. however do not write any code to populate it just yet 19:45:36 <davidlenwell> I just want this in the review process 19:46:13 <sslypushenko__> I will add to you as reviewer 19:46:44 <davidlenwell> thank you 19:47:12 <sslypushenko__> But I'm waiting for peaces of advise what I should add to this page 19:47:27 <davidlenwell> thats fine 19:47:40 <davidlenwell> it should always be done throught he review process .. easier to track that way 19:48:01 <sslypushenko__> It is all ready on review 19:48:29 <sslypushenko__> https://review.openstack.org/#/c/129320/ 19:49:12 <davidlenwell> thanks 19:49:20 <davidlenwell> alright .. does anyone have anything else? 19:49:54 <catherine_d> I am good ... 19:53:15 <rockyg> Sounds like a take. 19:54:01 <catherine_d> sslypushenko__: what is particulary support? maybe we can IRC on #refstack to discuss .. 19:54:58 <sslypushenko__> Ok. Lets move to refstack channel 19:55:47 <davidlenwell> sounds good 19:55:50 <davidlenwell> #endmeeting