17:00:02 <jlvillal> #startmeeting ironic_qa
17:00:03 <openstack> Meeting started Wed Mar  9 17:00:02 2016 UTC and is due to finish in 60 minutes.  The chair is jlvillal. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:04 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:07 <openstack> The meeting name has been set to 'ironic_qa'
17:00:16 <jlvillal> Hello everyone.
17:00:28 <jlvillal> As always the agenda is at: https://wiki.openstack.org/wiki/Meetings/Ironic-QA
17:00:33 <[1]cdearborn> o/
17:00:50 <jlvillal> #topic Announcements
17:01:10 <jlvillal> I don't have any announcements. Does anyone else have anything?
17:01:29 <sambetts> o/
17:01:34 <mgould> o/
17:01:57 <jlvillal> UK in the house :)
17:02:03 <jlvillal> Okay, moving on ...
17:02:14 <jlvillal> #topic Grenade testing of Ironic
17:03:13 <jlvillal> #info Work continues. Currently at stage where we see failures in booting the bare-metal node.
17:03:33 <jlvillal> So mgould and I have both seen in the bare-metal node where it fails to network boot.
17:04:10 <mjturek1> \o
17:04:35 <jlvillal> #info Patch submitted in master to fix regression in stable/liberty. Once lands in master, will propose backport to stable/liberty: https://review.openstack.org/279270
17:05:18 <jlvillal> #info Patch submitted to place bare-metal log files into the log directory for /opt/stack/old/ logfiles.  https://review.openstack.org/290171
17:05:49 <jlvillal> So work continues, but slowly. Each run takes about 30-60 minutes depending on the system it runs on.
17:06:02 <jlvillal> I don't have anything else to add.  Any questions or comments?
17:06:25 * mgould has nothing to add - mostly been working on other things for the last few days
17:06:55 <jlvillal> mgould: Thanks for your help though. As John McClane says in Die Hard, "Welcome to the party pal" :P
17:07:12 * jlvillal will do old 80's movie references...
17:07:19 <jlvillal> Okay moving on...
17:07:37 <jlvillal> #topic Functional testing of Ironic
17:07:44 <jlvillal> Anyone have any updates?
17:07:46 <mjturek1> I hate to sound like a skipping record but still not much progress on functional. One thing I did do was look for a tempest test that might work as a good starting point for functional testing.
17:08:05 <mjturek1> that being said, I'm not sure there is one, it's a lot of api testing and the big deployment test
17:08:32 <jlvillal> #info Not much progress this week. Some research was done by mjturek1 on tempest tests.
17:08:36 <mjturek1> does anyone have any suggestions here as to a test that could excercise the api and conductor? maybe port-update?
17:09:01 <jlvillal> mjturek1: I'm not sure. I haven't looked at them closely. Might be a good question for the general channel.
17:09:12 <mjturek1> jlvillal: will do
17:09:18 <jlvillal> mjturek1: I would imagine dtantsur or lucasgomes would be good resources.
17:09:30 <jlvillal> Okay, moving on.
17:09:32 <mjturek1> cool cool
17:09:33 <mjturek1> thanks
17:09:41 <jlvillal> #topic 3rd Part CI (krtaylor)
17:09:52 <krtaylor> o/  sorry I 'm late
17:10:06 <krtaylor> no progress to report this week
17:10:12 <jlvillal> krtaylor: I noticed someone had posted a question to the mailing list on 3rd Party CI. Did you have time to respond?
17:10:25 <krtaylor> yes, I saw that, will respond today
17:10:43 <jlvillal> Thanks.
17:10:51 <krtaylor> although, it does beg the question
17:11:07 <krtaylor> how are we going to verify that they can receive events
17:11:07 <jlvillal> #info No updates for this week.  krtaylor will respond to email question about 3rd Party CI
17:11:21 <jlvillal> krtaylor: blind faith on our part?
17:11:36 <krtaylor> hehheh, yeah
17:11:52 <sambetts> krtaylor: you can se we are ;)
17:11:57 <jlvillal> I'm not sure. Since we can't tell until they actually respond to the events.
17:12:22 <jlvillal> Like the (in)famous Cisco 3rd Party CI ;)
17:12:33 <krtaylor> right, sandbox it the place unless they already have a reporting system, still not a bad idea to start there
17:13:02 <jlvillal> krtaylor: Anything else?
17:13:09 <krtaylor> nope, not this week
17:13:19 <jlvillal> Okay moving on
17:13:27 <jlvillal> #topic Open Discussion / General QA topics
17:13:33 <jlvillal> The floor is open.
17:13:37 <jlvillal> Anyone have anything?
17:14:00 <jlvillal> #info If anyone wants to work on Grenade testing, feel free to contact jlvillal
17:14:42 <jlvillal> I'll give it one more minute of silence before ending meeting.
17:14:49 <[1]cdearborn> At Dell, we're ready to start on the next milestone for 3rd party CI
17:15:07 <jlvillal> Oh great.  krtaylor ^^^
17:15:15 <[1]cdearborn> and wondering if anyone has pointers to docs on network config, how to run tests, etc
17:15:38 <sambetts> [1]cdearborn: what sort of info do you need?
17:15:59 <krtaylor> [1]cdearborn, we have just gone through all this in our team
17:16:07 <[1]cdearborn> well, for the hardware setup, how many networks are required, any special HW config
17:16:22 <krtaylor> [1]cdearborn, I am trying to get it documented
17:16:35 <krtaylor> mjturek1, maurosr ^^^
17:16:38 <[1]cdearborn> that would be great! thx
17:16:49 <mjturek1> [1]cdearborn: are you testing on actual hardware as targets?
17:17:01 <[1]cdearborn> yes, that is the objective
17:17:17 <mjturek1> okay cool, yeah we're planning to get the documentation moving for that scenario
17:17:33 <krtaylor> you also might be interested in what we are doing for baremetal pool management
17:17:35 <sambetts> I have 3 physical networks in my testing infrastructure
17:17:39 <[1]cdearborn> we got a pile of new hardware and our lab guy wan't to know how it needs to be wired up/configed
17:18:21 <[1]cdearborn> krtaylor, absolutely!
17:19:05 <sambetts> I'm running an openstack nodepool provider for managing all my devstack VMs, which are each handed a real server to try to boot
17:19:12 <sambetts> using Ironic
17:19:55 <sambetts> We are very nearly running, the jobs keep running into issues install the python packages while running devstack at the moment tough
17:19:58 <sambetts> though
17:19:59 <[1]cdearborn> sambetts, that sounds similar to the setup that we currently have - nodepool on a VM
17:20:12 <mjturek1> [1]cdearborn: networking wise, you'll need your management interface hooked up for each node and an interface to deploy to
17:20:32 <mjturek1> by management interface, I mean ipmi capable interface
17:20:45 <[1]cdearborn> mjturek1, ok, so 2 networks: ipmi & provisioning
17:20:50 <mjturek1> yep yep
17:21:04 <[1]cdearborn> so what are the tests that are run?
17:21:06 <sambetts> you also need a network so that jenkins can talk to the slave
17:21:19 <sambetts> unless thats going to run over one of the other two networks
17:21:28 <mjturek1> [1]cdearborn: api tests on the dsvm then a big deployment test
17:21:52 <sambetts> mjturek1: are you using the tempest suite?
17:22:08 <mjturek1> sambetts: we're using ironic's tempest plugin
17:22:11 <maurosr> we are, all the tests migrated from tempest to ironic's tree
17:22:30 <sambetts> I was aiming to run the same jobs as run by the Ironic gate, but just with the driver swapped out
17:22:59 <jlvillal> mgould: https://bugs.launchpad.net/bugs/1554908   Makes me wonder....
17:22:59 <openstack> Launchpad bug 1554908 in Ironic "baremetal machine fail in local boot in virtualbox " [Undecided,New] - Assigned to bin Yu (froyo-bin)
17:23:03 <[1]cdearborn> sambetts, yes, that makes sense - does the gate just run some tempest ironic tests?
17:23:24 <mjturek1> sambetts: not sure that will work with the current upstream tree. We had to patch a bunch and some of those are still in review
17:23:28 <mjturek1> right maurosr ^?
17:23:37 <jlvillal> mgould: But not sure. As we are inside virtualbox and we are using QEMU I think. So not virtualbox inside virtualbox.
17:23:43 <sambetts> [1]cdearborn: yes, they run the tempest suite with the regex baremetal or ironic
17:24:09 <[1]cdearborn> sambetts, thx
17:24:32 <maurosr> yeah, using devstack, made us do some customizations in devstack and ironic mainly
17:24:43 <sambetts> mjturek1: Oh interesting, do they do driver specific things then?
17:25:25 <mjturek1> sambetts: 'they' being the patches? or the tests?
17:25:33 <sambetts> the tests
17:25:59 <mgould> jlvillal, yep, we're using QEMU inside virtualbox
17:26:16 <sambetts> I've been running devstack with the IRONIC_IS_HARDWARE=True flag to get my devstack setup running
17:26:17 <maurosr> well one of the test is deployment scenario, so it does driver specific things
17:26:18 <mgould> or QEMU inside QEMU
17:26:23 <maurosr> using pxe and ipmitool
17:26:44 <maurosr> the changes we need on driver level were made here: https://review.openstack.org/#/c/185987/
17:26:56 <sambetts> maurosr: I thought that it would just do a deployment? e.g. nova boot, wait for active, check for ssh
17:27:20 <[1]cdearborn> thx very much all, this gives me a base understanding and a place to start.  Much appreciated!
17:27:21 <mjturek1> maurosr: these changes were power specific I thought
17:27:25 <mgould> jlvillal, I'll look to see if I get the same error on QEMU-inside-QEMU...
17:27:28 <maurosr> mjturek1: it is
17:27:37 <maurosr> (I think I'm missunderstanding somethign here)
17:27:51 <jlvillal> mgould: Thanks. My gut feeling is probably not an issue for us.
17:28:05 <mjturek1> sambetts: you're deploying to x86 hardware, am I mistaken?
17:28:13 <sambetts> mjturek1: yup
17:28:27 <mjturek1> okay cool, so test wise I think everything is merged
17:28:37 <sambetts> [1]cdearborn: feel free to ping me if you've got any questions, I'm still working through ours but I'm getting a pretty good understanding
17:28:43 <mgould> jlvillal, yeah, that doesn't look like our issue
17:28:59 <mjturek1> what I think isn't merged is some devstack stuff
17:29:16 <mjturek1> maurosr: we should get a list together of what needs to merge for baremetal testing
17:29:22 <mjturek1> (on baremetal targets that is)
17:29:25 <maurosr> just a second
17:30:16 <vdrok> mgould, jlvillal local boot works fine in qemu, just tried that today
17:30:45 <sambetts> mjturek1, maurosr: these changes sound interesting, I'd like to see them if possible, I've been planning an addtion to ironic devstack to aid in alternate driver deployments so I'd like to make sure I'm not duplicating anything
17:30:47 <jlvillal> vdrok: Thanks
17:31:10 <mjturek1> sambetts, definitely. we'll work on getting you a list of patches we're using
17:31:19 <sambetts> mjturek1: awesome :D
17:32:15 <jlvillal> I'm going to go ahead and end the meeting. Feel free to keep discussing things.
17:32:21 <mjturek1> sambetts: actually that shouldn't be too hard. We have them in our pre_test_hook
17:32:25 <maurosr> right, given our last build (http://dal05.objectstorage.softlayer.net/v1/AUTH_3d8e6ecb-f597-448c-8ec2-164e9f710dd6/pkvmci/ironic/47/290547/1/check-silent/gate-tempest-dsvm-ironic-pxe_ipmitool/c966bf4/ ) I would say we need this patches : http://paste.openstack.org/show/489887/ which are not merged
17:32:27 <jlvillal> But I want to let people feel free to leave if they so wish.
17:32:32 <mjturek1> jlvillal: sure
17:32:37 <jlvillal> #endmeeting