19:00:32 <davidlenwell> #startmeeting refstack
19:00:33 <openstack> Meeting started Mon Oct 27 19:00:32 2014 UTC and is due to finish in 60 minutes.  The chair is davidlenwell. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:00:34 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
19:00:36 <openstack> The meeting name has been set to 'refstack'
19:00:58 <hogepodge> Good afternoon.
19:01:04 <davidlenwell> good day
19:01:19 <davidlenwell> roll call
19:01:43 <pvaneck> o/
19:01:50 <hogepodge> o/
19:03:29 <catherine_d> o/
19:03:33 <davidlenwell> we'll let a few more folks filter in before starting
19:04:01 <davidlenwell> whois hogepodge? just curious
19:04:42 <hogepodge> davidlenwell, Chris Hoge, I was just hired by the OpenStack Foundation as their Interop Engineer, which in part means DefCore/RefStack
19:04:44 <davidlenwell> hard to remember everyones nick
19:04:56 <davidlenwell> oh thats right we met t openstack silicon valley
19:05:21 <sslypushenko__> o/
19:05:26 <davidlenwell> good .. very glad to see you here.. welcome!
19:05:45 <hogepodge> Thank you! It's exciting to be here.
19:06:21 <davidlenwell> okay .. lets just get started
19:06:58 <davidlenwell> #topic api
19:07:19 <davidlenwell> I am going to submit for review this afternoon the patch everyones been waiting for..
19:07:39 <catherine_d> davidlenwell: great
19:07:48 <davidlenwell> I've ended up refining the web service to not include all of the reporting features.
19:07:59 <davidlenwell> the event reporting I should say
19:08:32 <davidlenwell> without tests being triggered from the central database/api there isn't really a point in keeping track of the status of test runs
19:08:47 <davidlenwell> so look for that and review it ..
19:09:11 <davidlenwell> lets keep the review cycles fast.. I'd like to have this code hosted at api.refstack.org by thursday
19:09:33 <catherine_d> davidlenwell: will we have an web site up?
19:09:37 <davidlenwell> yes
19:09:48 <rockyg> O/
19:09:56 <davidlenwell> refstack.org will be up and api.refstack.org will host the api
19:10:17 <catherine_d> davidlenwell: +1 ..
19:10:44 <davidlenwell> so hogepodge and catherine_d and sslypushenko__ I will tag you all as reviewers on the api code..
19:11:10 <davidlenwell> next topic..
19:11:20 <catherine_d> sslypushenko__: have been working on  the DefCore results page  .. once the site is up we should host those page ..
19:11:20 <davidlenwell> #topic next weeks meeting
19:11:42 <davidlenwell> we obviously will not be having a meeting next week .. most of us will be in paris.
19:11:54 <zehicle_> o/ lurking
19:11:57 <davidlenwell> I plan on getting as much facetime with all of you as possible.
19:12:51 <davidlenwell> I also plan on crashing several of the q/a track design sessions in order to push our agenda for uuid's on tests
19:13:03 <sslypushenko__> DefCore results page can be used as a template for flask. So it will easy to intergrate it in refstack.org
19:13:04 <davidlenwell> catherine_d: you and I should coordinate on that
19:13:14 <davidlenwell> thank you sslypushenko__
19:13:16 <catherine_d> davidlenwell: do we have a time slot for UUID discussion
19:13:56 <davidlenwell> mtreinish (the tempest ptl) has told me he'll tollorate that being a topic for part of the track.. im not sure on the timing of it.. I'll try to coordinate with him accordingly
19:14:25 <mtreinish> davidlenwell: well it's a bit too late for the qa track now, it's pretty much locked down
19:14:40 <mtreinish> but we can discuss it during the friday contributor meetup
19:15:00 <davidlenwell> mtreinish: I might corner you in the dev lounch between tracks then ..
19:15:23 <davidlenwell> friday might be to late for the conversation to evolve into a solution before the end of the week
19:16:22 <catherine_d> mtreinish: this is a very important topic for refstack ... because of the complexity of the topic , we should discuss early in the week
19:17:19 <davidlenwell> mtreinish: I'll ping you offline and we can work this out
19:17:34 <mtreinish> davidlenwell: sure, although the advantage of friday is that it's all day
19:17:37 <mtreinish> davidlenwell: ok sure
19:17:48 <davidlenwell> thank you mtreinish
19:17:58 <davidlenwell> lets move along
19:18:19 <davidlenwell> any pending reviews im missing?
19:18:30 <davidlenwell> #topic pending reviews
19:18:48 <catherine_d> need a flow chart for the wiki page
19:19:15 <rockyg> +1
19:19:26 <davidlenwell> okay .. I've just writtent hat on my pre-travel list on my whiteboard
19:19:36 <catherine_d> davidlenwell: thx
19:20:06 <davidlenwell> it will be part of the website content that I am working on anyways
19:20:24 <catherine_d> refstack-client review is all update to date ... Paul is working on https://storyboard.openstack.org/#!/story/188
19:20:53 <catherine_d> sslypushenko__: are you working on https://storyboard.openstack.org/#!/story/309?
19:21:58 <sslypushenko__> I'm planing to do it tomorrow. I have been working on report page all week
19:22:09 <catherine_d> sslypushenko__:  +1 thx
19:22:24 <rockyg> Which is looking good.
19:22:43 <sslypushenko__> thx
19:23:00 <catherine_d> For refstrack , davidlenwell:    zehicle_: please review https://review.openstack.org/#/c/129320/ rockyg: and I have reviewed
19:23:43 <sslypushenko__> I think it is very close to final version
19:23:51 <davidlenwell> I don't want that merged just yet .. I just wanted in gerrit
19:24:57 <catherine_d> if refstack.org is up ... this is one set of content that refstack.org can render ....
19:25:29 <davidlenwell> its not going to render anything yet
19:25:30 <catherine_d> i mean the report from sslypushenko__: on https://review.openstack.org/#/c/129320/ ... looks good to me ..
19:25:35 <davidlenwell> thats a k1 goal
19:26:03 <davidlenwell> right now we're focused on data collection
19:26:24 <davidlenwell> showing report cards might make it seem like we are expressing an opinion about how to run openstack
19:26:46 <zehicle> davidlenwell, we need to be able to show people how they are doing vs. the capabilities list
19:26:51 <zehicle> that's a Foundation request
19:27:00 <davidlenwell> that said we do want this .. and we do want to show rendered test results .. its just not a pre-paris requirment
19:27:01 <zehicle> we don't have to make them public - self review first
19:27:22 <zehicle> we do need to show them that we got all the data
19:27:28 <catherine_d> davidlenwell: in any how we need some kind of demo so people can give feedback ...
19:27:38 <davidlenwell> sure
19:28:41 <davidlenwell> and like I said .. we sitll want this .. but as far as I understood from every previous converasation rendering of results wasn't a preparis feature
19:28:45 <rockyg> Maybe run tests against trystack as demo of the report?
19:29:02 <davidlenwell> rockyg: I think thats a tangent
19:29:05 <davidlenwell> lets stay on topic
19:29:16 <zehicle> rockyg, you need admin access to run the tests
19:29:32 <rockyg> Just want a filled report available to show in Paris
19:29:34 <davidlenwell> yes .. rockyg and zehicle thats true
19:29:37 <zehicle> davidlenwell, do we care if they run against Havana?
19:29:43 <davidlenwell> no we don't
19:29:47 <catherine_d> I can provide some sample data
19:29:48 <zehicle> I'd expect that uploading any test results would be OK
19:29:50 <davidlenwell> everyone is still running havana
19:29:58 <davidlenwell> and those are the dependancies we have finalized anyways
19:30:01 <zehicle> ouch, ok
19:30:11 <zehicle> I guess I should put that Juno demo back on the shelf
19:30:23 <davidlenwell> perheps
19:30:55 <davidlenwell> again the tester doesn't care what version your running
19:31:08 <davidlenwell> branchless tempest should test juno just as well as it tests havana
19:31:09 <zehicle> it seems like the #1 thing to demo is that someone can upload tempest results
19:31:10 <catherine_d> zehicle: we need Icehouse before Juno?
19:31:11 <davidlenwell> or icehouse
19:31:16 <davidlenwell> and we're only collecting the results
19:31:25 <davidlenwell> so I don't care what version of the cloud you run the test results against
19:32:19 <hogepodge> A juno demo may not be a bad idea. Havana is not officially supported upstream any more.
19:32:49 <davidlenwell> that said .. sslypushenko__ do you have the bandwidth this week to connect that template to some real data.. catherine_d can provide you with sample data to write the code with.
19:33:05 <sslypushenko__> sure
19:33:15 <davidlenwell> hogepodge: I'll leave that up to someone on defcore
19:33:52 <sslypushenko__> Just ping me in email
19:33:59 <zehicle> at this point it's about proving the API not the version of OpenStack
19:34:03 <davidlenwell> catherine_d: can you email him some real results
19:34:11 <catherine_d> davidlenwell: sure
19:34:13 <davidlenwell> zehicle: +1000000
19:34:25 <davidlenwell> catherine_d: thanks
19:34:30 <zehicle> i'd like to see if people can get their own tests working as part of this
19:34:47 <sslypushenko__> I can incorporate it in a minute
19:34:47 <davidlenwell> well I have bluebox trying to start using the refstack client right now
19:35:11 <davidlenwell> the hold up right now is that they were not generating configs durring deployment for tempest
19:35:23 <davidlenwell> and won't be for a little while
19:35:34 <davidlenwell> so our test engineer is having to step through getting a working config
19:36:11 <davidlenwell> So .. prerequisit when we are pushing that folks run the client is that we make it clear that they have to write the tempest config themselves
19:36:21 <sslypushenko__> No pain, no gain)
19:36:41 <davidlenwell> indeed
19:36:43 <catherine_d> to clarify ... I do not have havana data ... I only have IceHouse data ...
19:37:06 <davidlenwell> thats fine
19:37:09 <davidlenwell> render it with icehouse data
19:37:46 <catherine_d> sslypushenko__: 's code renders the results  with havanacore
19:38:03 <sslypushenko__> Yep
19:38:06 <catherine_d> and we do note have icehousecore.json yet
19:38:26 <catherine_d> so we will render Icehouse data with havanacore.json?
19:38:27 <sslypushenko__> unfortunately(
19:38:44 <rockyg> Yes but the tests will work for . Backward compatibility demo:-)
19:38:52 <davidlenwell> sslypushenko__: can you make a version of the template that doesn't compare it to the json and doesn't assign a score?
19:39:08 <rockyg> For ice house
19:39:19 <davidlenwell> I just want a raw output view
19:39:24 <davidlenwell> that doesn't have an opinion
19:39:28 <catherine_d> rockyg: tests are compatible but criteria is not ...
19:39:39 <sslypushenko__> Comparing to capabilities - it is a main feature
19:39:55 <davidlenwell> again the criteria in question is based on defcore and not any other sense of reality
19:40:04 <sslypushenko__> But raw output avaible to
19:40:12 <davidlenwell> start with raw output
19:40:12 <rockyg> ++ David
19:40:18 <davidlenwell> in a readable fashion
19:40:37 <catherine_d> davidlenwell: take a look at http://sergslipushenko.github.io/output_demo.html  ... that would be the plain list in thos page
19:40:51 <rockyg> Sorry. Doing this on phone. Auto correct sucks for IRC
19:41:36 <rockyg> Havana vote should be mostly s subset of ice house
19:42:06 <davidlenwell> we have to keep in mind that refstack and defcore are very different things
19:42:19 <sslypushenko__> no exactly
19:42:25 <catherine_d> zehicle: this just mena that we need an icehousecore.json fast ?
19:43:03 <juliashapovalova> no exactly.. but mostly
19:43:08 <davidlenwell> refstack is to test for interopability .. our results output should show the capabilies but not use the word "core" at all
19:43:14 <juliashapovalova> so we need approved havana first
19:43:28 <davidlenwell> I'm fine with defcore also having pages to render with scores
19:43:39 <davidlenwell> but we cannot have one before the other
19:44:40 <catherine_d> davidlenwell: http://sergslipushenko.github.io/output_demo.html can also show all if the "Show only core tests" check box is not checked
19:44:59 <davidlenwell> thats the problem I am having with the language on the page
19:45:16 <davidlenwell> I'll review the page and put down my opinions
19:45:23 <catherine_d> davidlenwell: +1
19:45:24 <davidlenwell> it will be easier to understand and cleaer
19:45:32 <davidlenwell> moving on .. anything else ?
19:45:50 <catherine_d> juliashapovalova: what else do you need for the wiki page?
19:46:16 <juliashapovalova> for now it has outdated diagrans
19:46:25 <juliashapovalova> and 3 brocken lincks
19:46:41 <juliashapovalova> couple for Rob's docs and refstack.org
19:46:57 <juliashapovalova> that's it
19:47:03 <davidlenwell> creating those diagrams is on my list for this week
19:47:12 <juliashapovalova> David promissed to take care on the flow chart
19:47:14 <davidlenwell> I'll share links to them in #refstack
19:47:24 <juliashapovalova> thanks!
19:47:36 <catherine_d> rockyg: will you be able to review the broken links?
19:47:38 <davidlenwell> after I get the api out tonight I'll be free to focus on message and all that
19:48:30 <davidlenwell> I'm actually really excited about designing and building a website and all the assets
19:49:03 <catherine_d> juliashapovalova: I will upload the new_havanacore.json ... you can review and update with the comments you send in the note earlier today so we have the log in review
19:49:43 <juliashapovalova> great
19:49:45 <rockyg> Removed some broken links.
19:49:53 <juliashapovalova> one more thing regarding the capabilities: I did one commit for  icehouse capabilities (it contains only new projects - to start reviews) please review it
19:50:26 <catherine_d> juliashapovalova: I will
19:50:47 <juliashapovalova> thank you
19:51:00 <rockyg> We need to move all reference docs into Openstack and out of Google
19:51:02 <catherine_d> final review of the core file will be from zehicle:
19:51:18 <zehicle> yy
19:51:31 <rockyg> ++
19:51:38 <catherine_d> zehicle: will ping when we are already for your review
19:51:51 <juliashapovalova> +1
19:51:51 <zehicle> let me know when ready
19:53:02 <catherine_d> zehicle: juliashapovalova: and I will do that ...
19:53:57 <davidlenwell> great
19:54:11 <davidlenwell> okay .. we're running out of time.
19:54:35 <davidlenwell> any final thoughts?
19:54:36 <juliashapovalova> I have an idea for demo - if David is concerning regardine the "core" list - we can use just full capabilities
19:54:51 <davidlenwell> juliashapovalova: +1
19:54:58 <juliashapovalova> it could be generated automaticaly for half an hour
19:55:33 <sslypushenko__> +1
19:56:00 <davidlenwell> okay .. lets end this ..
19:56:09 <davidlenwell> ping me in #refstack if anything is needed
19:56:16 <davidlenwell> #endmeeting