17:01:30 <jaypipes> #startmeeting qa
17:01:31 <openstack> Meeting started Thu Oct 25 17:01:30 2012 UTC.  The chair is jaypipes. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:01:32 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:01:33 <openstack> The meeting name has been set to 'qa'
17:02:08 <jaypipes> whatup QAers?
17:02:29 <davidkranz> jaypipes: Hi Jay.
17:02:33 <torandu> Hello all
17:02:39 <Ravikumar_hp> Hi Jay
17:02:55 <nati_ueno> Hi All
17:03:17 <jaypipes> #topic https://review.openstack.org/#/q/status:open+project:openstack/tempest,n,z
17:03:29 <jaypipes> Open reviews... looks like there is only 1 not WORKINPROGRESS
17:03:47 <jaypipes> I reviewed it yesterday, if others could (EC2 tests), that would be great
17:03:55 <jaypipes> dwalleck: https://review.openstack.org/#/q/status:open+project:openstack/tempest,n,z
17:04:00 <dwalleck> Sorry, network issues
17:04:18 <jaypipes> dwalleck: no worries. if you get a chance to review the last outstanding review (on EC2) that would be great
17:04:25 <dwalleck> Sure, can do
17:04:45 <davidkranz> Of course the next step will be to test ec2 creating servers :)
17:04:46 <jaypipes> cheers
17:04:58 <jaypipes> yes, right davidkranz
17:05:07 <dwalleck> But that's enabled by default in devstack, correct?
17:05:22 <davidkranz> Any progress from any one on the parallel run stuff?
17:05:42 <jaypipes> dwalleck: is EC2 API enabled you mean? yes it is by default
17:05:58 <jaypipes> dwalleck: I think davidkranz was just remarking that the only tests in the patch so far are for EC2 keypairs
17:06:19 <davidkranz> jaypipes: Right. The slow tests to follow...
17:06:23 <jaypipes> davidkranz: :)
17:06:45 <jaypipes> so, I don't know of any pgroess on parallel exec
17:06:54 <dwalleck> I haven't tried testtools yet. I did accidentally do something similar to parallel runner with just unittest, so it's a good sign that that type of solution would work
17:06:56 <davidkranz> So now we will have volume/cinder x osapi/ec2 x xml/json :(
17:07:08 <jaypipes> I have done some reading into testtools, and things there look excellent. just have not had time to code it up
17:07:54 <clarkb> https://review.openstack.org/#/c/14611/ is a conversion on a relatively simple project
17:07:54 <torandu> I need to read up on testtools. I'll make time for it this week
17:08:15 <jaypipes> I did, however, make some progress toward a tool to describe openstack environments. hopefully should be able to push that out to the ML next week
17:08:27 <davidkranz> jaypipes: Great.
17:08:33 <dwalleck> awesome!
17:08:40 <davidkranz> I have started looking at ceilometer.
17:09:04 <davidkranz> Now that it is incubated I wanted to give it a kick-start.
17:09:19 <davidkranz> THe first step is to make it really work in devstack and then provide some simple tempest tests.
17:09:31 <dwalleck> That'd be great
17:09:35 <jaypipes> ++
17:10:05 <davidkranz> That group may be tired of me already :)
17:10:11 <jaypipes> :)
17:11:06 <jaypipes> #link https://bugs.launchpad.net/tempest
17:11:09 <davidkranz> I got am email from a guy at Mirantis and I will follow up about getting the tempest-extensions from cisco if we can.
17:11:10 <jaypipes> #topic bug triage
17:11:22 <jaypipes> davidkranz: awesome news. thx!
17:11:24 <dwalleck> It's important stuff. I'm testing that type of thing from messages in rabbitmq, but having a nice interface would be much better
17:11:32 <jaypipes> ++
17:12:07 <jaypipes> OK, so I was hoping that today and tomorrow, our team can do some cleanup of the 73 Open bugs in tempest.
17:12:19 <davidkranz> dwalleck: Which "type of thing"?
17:13:05 <dwalleck> davidkranz: usage/monitoring type info
17:13:44 <davidkranz> jaypipes: A lot of those bugs were ones that I sent an email about a few months ago to the list.
17:14:18 <jaypipes> davidkranz: understood. just want to make another go at them...
17:14:20 <davidkranz> jaypipes: They were things that had not been touched since early this year and I threatened to close them if there was no response.
17:14:30 <dwalleck> I need to go through and either triage or close any that belong to me
17:14:51 <davidkranz> dwalleck: That is what I had requested from bug owners.
17:14:53 <jaypipes> davidkranz: ok, so are you saying you will do the needful and close out the ones you threatened to close?
17:15:08 <jaypipes> davidkranz: otherwise, I'm happy to do it.
17:15:10 <jaypipes> just let me know
17:15:10 <davidkranz> jaypipes: Yes, after dwalleck tells me he is sone.
17:15:16 <davidkranz> ^^ done
17:15:16 <uvirtbot> davidkranz: Error: "^" is not a valid command.
17:15:18 <jaypipes> davidkranz: k
17:15:47 <davidkranz> dwalleck: So just let me know. Feel free to close any others while you're at it.
17:16:18 <davidkranz> jaypipes: I also have a concern that we have file some serious nova bugs that have not been looked at.
17:16:45 <jaypipes> davidkranz: which ones?
17:16:51 <davidkranz> jaypipes: I would also like to find a way to get priority on the bugs that will make a clean tempest run show no errors in the logs.
17:17:08 <jaypipes> ok, I can get behind that
17:17:15 <davidkranz> jaypipes: I have to dig them out.
17:17:49 <davidkranz> jaypipes: I will send an email to the developer list with the bugs that should get some action.
17:18:17 <jaypipes> davidkranz: ty
17:19:01 <jaypipes> Ravikumar_hp: do you know if Antoni has had a chance to look into testtools?
17:19:39 <Ravikumar_hp> jaypipes: not yet. I will ping him and will get it prioritized
17:20:19 <jaypipes> Ravikumar_hp: cool. just have him hop on IRc and coordinate with torandu, who is also researching
17:20:34 <Ravikumar_hp> sure
17:20:58 <jaypipes> unless anyone has anything to bring up, I'm moving to close the meeting early and get back to the grind. Any objections?
17:21:04 <torandu> how much effort do you estimate for a switch to testtools? how will it affect work now, in the short-term?
17:21:26 <mtreinish> jaypipes: I was hoping someone could take a look at my coverage stuff soon
17:21:27 <jaypipes> torandu: don't know the answers... that's what we're investigating :)
17:21:28 <torandu> referring to test work in the current framework
17:21:34 <torandu> jaypipes: got it
17:21:39 <jaypipes> mtreinish: hi! link?
17:21:49 <jaypipes> https://review.openstack.org/#/c/14530/
17:21:54 <dwalleck_> If it just runs the test classes in parallel, hopefully not much to none
17:21:56 <SamDanes> Jay, I have the list of test classifications more or less done, where should I post it? On the openstack wiki somewheres?
17:21:57 <SamDanes> :-)
17:22:02 <mtreinish> jaypipes: sure: https://review.openstack.org/#/c/14468/ https://review.openstack.org/#/c/14530/
17:22:03 <torandu> where can I jump in now on bugs and/ or other investigation?
17:22:22 <jaypipes> mtreinish: will do today.
17:22:26 <mtreinish> jaypipes: thanks
17:23:24 <jaypipes> torandu: I think replacing base class inheritance from unittest.TestCase to testtools.TestCase and then fixing the way that fixtures at the module and package level are handled is a good start
17:23:48 <jaypipes> torandu: basically, all the setup_package() calls need to be made in the style of the fixtures/testtools way.
17:24:04 <torandu> jaypipes: ok. I'll start on that
17:24:25 <jaypipes> torandu: lifeless is the author and hangs out in #openstack-infra. I'm sure he would be happy to assist. also, clarkb just did a conversion of the python-keystoneclient to use testtools, in parallel, successfully
17:24:45 <clarkb> *novaclient, but yes
17:24:53 <torandu> jaypipes: kk. thx
17:25:09 <lifeless> oh hai
17:25:12 <davidkranz> SamDanes: We'll get to you.
17:25:13 <jaypipes> clarkb: oh, oops, sorry :)
17:25:42 <jaypipes> so... where to put SamDanes classification stuff? hmm...
17:25:48 <clarkb> jaypipes: I sort of have nova running http://paste.openstack.org/show/22202/ shows the time differences on the same VM
17:26:02 <clarkb> but its really ugly at the moment
17:26:13 <davidkranz> jaypipes: There isn't even a qa page in the wiki. I suggest we start at the top and work down to a page with this stuff.
17:27:00 <davidkranz> jaypipes: QA should be a "Common Project" on the home wiki page IMO.
17:27:05 <jaypipes> davidkranz: I know this may be cumbersome, but I think I would prefer to do it as git-managed changes to the openstack-qa docs, which automatically get uploaded to qa.openstack.org
17:27:20 <Ravikumar_hp> davidkranz: qa.openstack.org - the correct one may be outdated
17:27:25 <jaypipes> davidkranz: that way we can work with RST docs and have things published and controlled just like tempest source
17:27:31 <Ravikumar_hp> we can start fron there
17:27:34 <davidkranz> jaypipes: Works for me.
17:28:16 <jaypipes> SamDanes: the repo is here: https://github.com/openstack-dev/openstack-qa
17:28:22 <davidkranz> Perhaps Sam's stuff could just go in http://qa.openstack.org/integration.html or a link from there.
17:28:23 <lifeless> jaypipes: btw, for clarity - jml is the testtools maintainer, I'm an enthusiastic co-maintainer, but he is the bdfl for it [and we have a similar, reversed relationship for e.g. subunit]
17:28:29 <jaypipes> SamDanes: feel free to close and update docs there?
17:28:45 <jaypipes> lifeless: ah, good to know. thx for the correction!
17:29:01 <jaypipes> lifeless: you are still awesome, though :)
17:29:05 <lifeless> oh, I know :)
17:29:11 <jaypipes> lmap
17:29:12 <SamDanes> Excellent. I'll start with the classification document in the next day or so
17:29:22 <jaypipes> SamDanes: much appreciated!
17:30:07 <dwalleck_> That page needs to be updated period. That info is very old --> http://qa.openstack.org/integration.html
17:30:12 <davidkranz> jaypipes: Where is the repo for openstack-qa docs?
17:30:31 <jaypipes> davidkranz: see link above.
17:30:50 <jaypipes> dwalleck_: very much agreed!
17:31:05 <jaypipes> ok folks, please do review mtreinish's branch (https://review.openstack.org/#/c/14530/) as well as the EC2 patch (https://review.openstack.org/#/c/14689/)
17:31:15 <jaypipes> anything else before we wrap up?
17:31:56 <jaypipes> alrighty... ciao!
17:32:00 <jaypipes> #endmeeting