17:00:35 <mtreinish> #startmeeting qa
17:00:39 <openstack> Meeting started Thu Sep 24 17:00:35 2015 UTC and is due to finish in 60 minutes.  The chair is mtreinish. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:40 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:43 <openstack> The meeting name has been set to 'qa'
17:00:48 <mtreinish> hi, who's here today?
17:00:52 <jordanP> o/
17:01:07 <mtreinish> #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Proposed_Agenda_for_September_24th_2015_.281700_UTC.29
17:01:11 <mtreinish> ^^^ today's agenda
17:01:11 <ylobankov> hi
17:01:12 <dwalleck> o/
17:02:06 <mtreinish> andreaf, sdague, dtroyer, mkoderer, dkranz: around?
17:02:22 <dkranz> o/
17:02:43 <timello> o/
17:02:50 <mtreinish> ok, lets get started
17:02:54 <rfolco> o/
17:03:02 <ddeva> o/
17:03:03 <andreaf> o/
17:03:06 <mtreinish> #topic Summit Prep
17:03:25 <mtreinish> so with the tokyo summit coming up pretty soon I created the etherpad to brainstorm ideas:
17:03:28 <mtreinish> #link https://etherpad.openstack.org/p/mitaka-qa-summit-topics
17:03:52 <mtreinish> if you've got an idea for a session topic just add it onto the etherpad
17:04:30 <mtreinish> we'll probably take a meeting in a couple of weeks to discuss which sessions we'll have
17:05:02 <mtreinish> that was all I really had on this one :)
17:05:09 <mtreinish> does anyone have anything to discuss on this topic?
17:05:15 <andreaf> mtreinish: I see I already have a session :D
17:05:31 <mtreinish> yes, you do :)
17:05:38 <jordanP> :D
17:05:48 <mtreinish> andreaf: it could be worse, oomichi_ already has 2...
17:06:07 <andreaf> heh
17:07:17 <mtreinish> ok, if there isn't anything else lets move on
17:07:28 <mtreinish> #topic Specs Reviews
17:07:40 <mtreinish> #link https://review.openstack.org/#/q/status:open+project:openstack/qa-specs,n,z
17:07:48 <mtreinish> does anyone have an open spec review to discuss?
17:08:10 <mtreinish> there haven't been any changes there in a couple weeks so I doubt there are any
17:09:20 <mtreinish> #topic Tempest
17:09:32 <mtreinish> ok does anyone have anything to discuss on tempest this week?
17:09:38 <jordanP> https://review.openstack.org/#/c/226375/ :)
17:09:41 <jordanP> Py 2.6
17:09:47 <mtreinish> jordanP: sigh...
17:09:51 <jordanP> :D
17:10:07 <jordanP> my point is, we should have been more conservative when dropping 2.6
17:10:36 <jordanP> Juno is compatible with 2.6, Juno is still supported, so Tempest should be 2.6 compatible
17:11:00 <mtreinish> jordanP: we dropped it over a cycle ago
17:11:06 <mtreinish> and juno is eol in like a month
17:11:14 <jordanP> this is the cost of being branchless, we must be conservative even in master branch
17:11:56 <jordanP> sure, but so far the only 2.7 feature we leverage is dict comprehension...
17:11:59 <dkranz> jordanP: branchless tempest means we run against older clouds I thought
17:12:29 <mtreinish> dkranz: right, it's only compat for running against older clouds, no co-installable with older clouds
17:12:45 <jordanP> yes. I agree this argument was a bit invalid
17:12:57 <dkranz> jordanP: So why can't you run tempest on a 2.7 node even if cloud is 2.6?
17:12:59 <mtreinish> you cant install tempest master on an all in one juno box the python reqs are incompatible
17:13:32 <jordanP> no. It works
17:13:34 <SamD> +1 dkranz
17:13:47 <jordanP> dkranz, because I want to install everything on the same box
17:13:52 <jordanP> using devstack
17:14:01 <jordanP> for my 3rd party ci
17:14:05 <dkranz> jordanP: run tempest in a container :)
17:14:08 <jordanP> lol
17:14:14 <dwalleck> I've started running Tempest in docker just to avoid Python version and similar issues
17:14:25 <dkranz> I was only half joking
17:14:44 <jordanP> but all it takes is a 8 line change to not use dict comprehension
17:14:52 <mtreinish> dkranz: well my suggestion was leverage the openstack cloud under test to spin up a vm and run tempest from that
17:15:15 <jordanP> I don"t want to learn kubernetes and what no :)
17:15:17 <mtreinish> jordanP: I thought there were more issues on py26 back when we dropped the support
17:16:13 <jordanP> well, with this small patch, testr --list-tests works (I didn"t run a full tempest run)
17:16:56 <jordanP> ok, this is taking too much time on this meeting. let's move on
17:17:00 <mtreinish> jordanP: that's part of it too we don't run any tests on py26 anywhere so we can never really know if it really works
17:17:07 <mtreinish> jordanP: ok :)
17:17:14 <mtreinish> is there anything else to discuss on tempest this week?
17:18:25 <mtreinish> ok, then lets move on
17:18:36 <mtreinish> #topic Devstack
17:18:56 <mtreinish> dtroyer, sdague: anything new from the land of devstack this week?
17:20:47 <mtreinish> does anyone else have anything to discuss on devstack this week?
17:20:49 <andreaf> mtreinish: I've got a devstack review :) it's not critical but it would be nice to have - it's for devstack with the v3 policy file: https://review.openstack.org/#/c/222038/1
17:21:12 <mtreinish> #link https://review.openstack.org/#/c/222038/1
17:21:36 <mtreinish> ok cool, that's probably a good thing to start doing
17:22:41 <mtreinish> andreaf: do we have a patch up that uses the v3 policy file anywhere?
17:23:33 <andreaf> mtreinish: good question
17:24:00 <mtreinish> because I've seen a bunch of fixes lately for that, but it would be good to test with it somewhere
17:24:00 <andreaf> mtreinish: probably yes but I need to look for it
17:24:09 <mtreinish> ok cool
17:24:23 <mtreinish> we can dig into that after the meeting
17:24:28 <mtreinish> ok is there anything else on devstack?
17:24:30 <andreaf> mtreinish: I know the keystone folks are also working on it, but I'll make sure we have one
17:25:35 <mtreinish> ok, lets move on
17:25:39 <mtreinish> #topic Grenade
17:26:06 <mtreinish> does anyone have anything to discuss about grenade?
17:27:15 <mtreinish> heh, I guess not :)
17:27:27 <mtreinish> then let's move on
17:28:06 <mtreinish> #topic OpenStack Health
17:28:24 <mtreinish> andreaf: you put this on the agenda, so I'll let you run with it :)
17:28:24 * andreaf welcomes the new entry :)
17:28:52 <jtrovo> cool topic :)
17:28:54 <andreaf> mtreinish: heh I thought we could use this space to discuss about current status and important reviews
17:29:12 <mtreinish> andreaf: ok
17:29:28 <andreaf> there is wip on the puppet module to deploy openstack-health
17:29:49 <andreaf> #link https://review.openstack.org/#/c/226545/
17:29:50 <jtrovo> we've been working on getting openstack-health deployed this week and also on some parts of the rest api
17:29:55 <andreaf> that's to get the repo in
17:29:56 <mtreinish> also, for people who haven't seen the new repo openstack-health is the project to try and get an overview dashboard of the state of test runs in the gate (and periodic too)
17:30:35 <jordanP> mtreinish, is there a demo somewhere ?
17:30:45 <jordanP> it's new to me
17:30:58 <andreaf> jordanP: not yet a running demo I believe
17:30:58 <ccarrara_> we've also had some progress on puppet-openstack-health, just waiting the repo creation to commit it.
17:31:06 <mtreinish> jordanP: not yet, the most right now is some mock pages up in the docs dir: https://github.com/openstack/openstack-health
17:31:07 <andreaf> jordanP: it started during the QA sprint
17:31:30 <jordanP> is it linked to stackviz ?
17:31:39 <jordanP> or is it the same thing ?
17:31:46 <mtreinish> jordanP: there are some wip patches up that let you do things locally, but it needs doc updates to explain how to do that
17:32:02 <mtreinish> jordanP: right now they're 2 separate things
17:32:15 <dwalleck> Sounds interesting
17:32:42 <mtreinish> jordanP: although at some point we might integrate stackviz as a view for a single run
17:32:46 <andreaf> #link https://etherpad.openstack.org/p/PuDfHylBgI
17:33:02 <andreaf> jordanP, dwalleck: ^^^ that's a good starting point
17:33:28 <jordanP> indeed. interesting
17:33:37 <andreaf> jordanP, dwalleck: and #link https://review.openstack.org/#/c/192253/
17:33:57 <andreaf> jordanP, dwalleck: you're very welcome to contribute!
17:34:13 <mtreinish> so just to come back to the status
17:34:40 <mtreinish> I've got subunit2sql patches up for review to add db apis needed for the rest side
17:34:52 <mtreinish> and wip patches up to openstack-health to use those
17:35:00 <dwalleck> thanks, I'll have a look
17:35:30 <mtreinish> it sounds like timothyb89 and others (I can't remember all the other irc nicks) are working on getting the js frontend to properly talk to the rest api
17:35:43 <mtreinish> and the puppet repo to deploy is still waiting on project-config approval
17:36:02 <mtreinish> oh and jhesketh has patches to work on getting a zuul mysql reporter added so we can leverage that as an additional data source
17:36:09 <mtreinish> did I miss anything?
17:36:35 <andreaf> mtreinish: one thing I wanted to ask - but perhaps it's more an openstack-infra question - is where are we going to run it
17:37:10 <mtreinish> andreaf: so when I discussed it with jhesketh before we'll likely have to get another server added to infra for the rest api piece
17:37:14 <andreaf> mtreinish: do we need an extra VM somewhere and what's the process to provision it
17:37:15 <mtreinish> which will come with the system-config patch
17:37:53 <andreaf> mtreinish: ok - I'll add that as a todo on the etherpad
17:38:02 <mtreinish> andreaf: it's pretty simple, but you need someone with infra-root to do the server deploy
17:38:24 <mtreinish> that'll happen right before the system-config patch is merged because they'll need to add the server info into hiera
17:38:51 <andreaf> mtreinish: ok
17:39:01 <mtreinish> ok, is there anything else on this topic?
17:39:08 <ccarrara_> mtreinish: are you thinking to deploy openstack-health api and frontend separately?
17:39:31 <mtreinish> ccarrara_: I hadn't really thought about it too much, but probably not
17:39:47 <ccarrara_> ok, thanks.
17:40:16 <andreaf> mtreinish: will it be running within the status.openstack.org name?
17:40:17 <mtreinish> I was just saying because of the expected amount of traffic for the rest api that'll need it's own server
17:40:34 <jtrovo> mtreinish probably it would be great to have the patches of subunit2sql that openstack-health depends on listed somewhere so we can keep a tracking of it
17:40:40 <SamD> I would think that you would want logical seperation of the API and the UI code base/logic but where deployed shouldn't matter aside from load right??
17:40:41 <mtreinish> whether we host the frontend from there or not doesn't really matter
17:40:45 <mtreinish> andreaf: yes probably
17:41:18 <mtreinish> jtrovo: all of them are in:
17:41:20 <mtreinish> #link https://review.openstack.org/#/q/status:open+project:openstack-infra/subunit2sql+branch:master+topic:add-db-api-tests,n,z
17:41:33 <mtreinish> I had to make it a giant branch for rebase concerns
17:41:44 <mtreinish> SamD: right
17:42:02 <andreaf> mtreinish: one last thing on this topic, is about extending the scope to the periodic tests
17:42:52 <andreaf> mtreinish: is this a good conversation to have in the openstack-infra meeting? I wanted to move forward on that and not wait for the summit
17:43:28 <mtreinish> andreaf: sure I think we can bring it up during the infra meeting
17:44:31 <mtreinish> there is a larger discussion there because there is a seperation of concerns on the DB
17:44:43 <mtreinish> right now it has value not just for a dashboard but also from a test analysis side
17:44:59 <mtreinish> and if we start adding things from outside the gate that potentially gets diluted
17:45:32 <mtreinish> ok, anywat I think we should move on
17:45:40 <andreaf> mtreinish: ok
17:45:50 <mtreinish> #topic Critical Reviews
17:45:51 <andreaf> mtreinish: that's all I had I think
17:46:05 <mtreinish> ok, does anyone have any reviews that they'd like to get extra eyes on?
17:46:49 <dwalleck> https://review.openstack.org/#/c/212691/ - I want my tests to run on Irix! :D
17:47:32 <mtreinish> dwalleck: heh, I can't blame you for that. I miss my indigo cube sometimes
17:47:43 <SamD> and my TRS-80
17:48:13 <jordanP> dwalleck, thanks for this patch. i remember when you opened this bug in launchpad
17:48:25 <jordanP> it's good you made it
17:48:26 <mtreinish> #link https://review.openstack.org/#/c/212691/
17:48:34 <dwalleck> Thanks!
17:48:53 <mtreinish> ok, are there any other patches this week?
17:49:16 <mtreinish> #link https://review.openstack.org/216873
17:49:39 <mtreinish> that's a migration from tempest -> tempest-lib of the idempotent_id decorator stuff
17:50:56 <mtreinish> ok, if there aren't any other reviews to bring up today lets open the floor
17:51:01 <mtreinish> #topic Open Discussion
17:51:14 <mtreinish> does anyone have any topics they'd like to discuss which weren't on the agenda?
17:52:31 <mtreinish> ok, if there isn't anything else I guess we'll end here today
17:52:33 <mtreinish> thanks everyone
17:52:35 <mtreinish> #endmeeting