19:01:36 #startmeeting ironic 19:01:37 Meeting started Mon Jun 9 19:01:36 2014 UTC and is due to finish in 60 minutes. The chair is devananda. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:01:38 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 19:01:40 The meeting name has been set to 'ironic' 19:01:46 o/ 19:02:03 #chair NobodyCam 19:02:03 Current chairs: NobodyCam devananda 19:02:07 :) 19:02:09 #topic announcements 19:02:12 hi all! 19:02:17 o/ 19:02:20 as usual, the agenda can be found here: https://wiki.openstack.org/wiki/Meetings/Ironic 19:02:21 what a week! 19:02:30 o/ 19:02:41 biggest item is probably the current status 19:02:42 NobodyCam, +1 heh 19:02:43 We weren't able to land any patches last week, and in fact we haven't had any commits merge in 10 days! 19:03:03 last week's issues were due to https://bugs.launchpad.net/nova/+bug/1326289 19:03:04 Launchpad bug 1326289 in nova "Failing to launch instances : Filter ComputeCapabilitiesFilter returned 0 hosts" [Critical,Fix committed] 19:03:07 The fix for that (reverting the relevant nova change) landed this morning. We should be able to start approving patches again. 19:03:22 woo hoo! 19:03:41 great job babysitting the landing of that btw 19:03:43 however, the openstack gate is still having some issues -- it seems better than last week, but not great yet 19:03:56 devananda: but *should* you be approving patches? haven't seen anything from sdague saying "go for it" 19:04:05 * Shrews 2 seconds to late 19:04:32 I approved an IPA patch earlier today and it already made it through the gate. Looking at status.openstack.org/zuul it seems to be OK in a generic sense to approve patches. IDK about Ironic-proper though. 19:04:36 is there a plan for how we are going to deal with this once those nova changes merge again? 19:05:06 JayF: because IPA isn't co-gated with anything 19:05:36 JayF: which is because it's not beign tested with tempest/devstack/etc 19:05:51 yet :( 19:05:55 adam_g: roughly - yes, but nothing's formal afaik 19:06:42 adam_g: my rough plan is: land the nova cchange w/o changing the signature of HostState.__init__, in a backwards-compatible way 19:06:51 i suppose when the gate is better shape it will be easier to coordinate 19:07:04 cool 19:07:15 #action devananda to draft plan to re-land commit ce3f9e5fa9cd05f3ee3bb0cc7d06521d05901cf4 in a non-breaking way 19:07:50 we should be good to recehck things as needed now, and we should be able to trust Jenkins' votes again 19:08:18 that's it for the big status thing 19:08:25 #topic release cycle progress report 19:08:40 J1 milestone is this week ... 19:08:58 given that we have a lot of the refactoring and fixes we discussed at the summit *in flight* right now 19:09:25 it'd be great if we get those in ... but given the status of the gate, i'm not so sure 19:09:52 i have some ideas. anyone else want to jump in, feel free 19:10:14 devananda: J1 milestone is June 12. Don't they cut it two days before? So June 10? (tomorrow) 19:10:48 rloo: releases are being handled slightly differently this cycle. rather than cutting a branch, i'll just tell ttx what git SHA to use from master 19:10:58 are things stable enough to cut a release? 19:11:04 devananda: great. that buys us some more time. 19:11:08 rloo: and we have some leeway. Thursday would be best, but if it slips to next Monday, it's nto the end of the world 19:12:42 if we can, I think it would be great to do some quick reviewing of the backlog, rebase a bunch of really-nice-to-have cleanup and bug fixes, then push them through today and tomorrow (assuming the gate lets us land anything) 19:13:14 +1 19:13:23 cause we have a lot of high-priority bug fixes with patches up right now 19:13:24 +1, if gate gets better tomorrow we may want to have a review jam or something? to land things quickly 19:13:40 I'm in for a review jam 19:14:05 I too am up for jam 19:14:18 great, thanks 19:14:49 #info review jam tomorrow (Tuesday PST morning / GMT afternoon) 19:15:10 devananda: can we try to make that post-9am? :) 19:15:10 lucasagomes: anything you'd like to add on the overall code cleanup progress? 19:15:16 (PST) 19:15:20 jroll: nope 19:15:34 devananda, due the gate problems, we still waiting for the tempest and devstack patches to land 19:15:37 both has a +2 19:15:38 jroll: show up when you can -- i'll try to start at 6am myself 19:15:48 whoaaaaaa 19:15:56 jroll: which isn't exactly normal, but neither is the current situation :) 19:15:56 I can do that, but whoa. 19:15:58 that's some dedication 19:15:58 :) 19:16:05 i will try for 6 am 19:16:08 there's some discussion going on on the tempest patch right now, but I hope toget both of then in this week 19:16:15 totally fair dude, I'll shoot for 6am, may be 6:30 or so 19:16:34 devananda, is review jam using this IRC channel? 19:16:45 linggao: no - we use the normal #openstack-ironic channel 19:17:00 lucasagomes: anything we can do to help those tempest patches? 19:17:07 ok, 6am your time? 19:17:21 devananda, yes, if you guys could read the discussion and give ur opnion would be useful 19:17:23 #link https://review.openstack.org/95789 19:17:25 that's the patch 19:17:41 lucasagomes: thanks, will do 19:17:59 #topic subteam: integration testing 19:18:05 lucasagomes: good luck getting jenkins to approve them. I can't get my tempest changes past jenkins :( 19:18:12 nice segway into the next topic :) 19:18:18 Shrews, :/ 19:18:30 adam_g: any add'l updates on tempest from last week? 19:18:55 devananda, not too much 19:19:02 patches that were up last week still are, for obvious reasons 19:19:09 right 19:19:25 lifeless: hi! any updates on tripleo CI for Ironic? 19:21:01 ok, we can come back to lifeless any time if he's around 19:21:08 #topic subteam: bugs 19:21:19 dtantsur is on PTO for a few more days IIRC 19:21:34 I didn't get any summary from him before he left 19:21:45 I think he's on PTO this week and the next one 19:21:50 yes form what I recall he is out the rest of this week 19:21:54 but from what I can tell, he's been reviewing all the open bugs, adjusting status 19:22:17 devananda: hi 19:22:18 lucasagomes: ah, thanks for the clarification - didn't realize it extended past this week 19:22:35 devananda: uhm, no, I'm not driving that, just whinging about it 19:22:40 devananda, not 100% sure, lemme try to confirm that 19:22:57 devananda: I wish I had time to drive it. check with adam_g and NobodyCam who AFAIK were caring for the failing tripleo-ironic jobs 19:23:24 We might be able to sic pcrews on it too, from the tripleo end 19:23:52 lifeless: ack. your name ended up on that item in our agenda -- adam_g or NobodyCam, either of you want to give updaets on tripleo ci of ironic? 19:23:56 I was unable to get a lot done with the Ci job last week, I should have more time this week 19:24:38 the ironic dsvm jobs *should* be passing now. so any consistent failures should get a bug and we can take a look. 19:24:58 lifeless, NobodyCam - fwiw, this is also a good time to raise awareness of any particularly large issues that tripleo is hitting with ironic 19:24:59 im aware of the UCA GPG key error, and will see what infra thinks about caching that stuiff on the precise slave images 19:25:02 adam_g: not dvsm 19:25:09 adam_g: *tripleo*.*ironic.* 19:25:26 adam_g: even undercloud 19:25:42 oh my bad, i have not been involved there. 19:26:02 WRT major bugs that have been affecting our tripleO testing, https://bugs.launchpad.net/ironic/+bug/1320513 is probably the #1 for us right now 19:26:04 Launchpad bug 1320513 in ironic "IPMI commands are sent / queried too fast" [High,In progress] 19:26:29 ack. i have a fix proposed for that 19:26:36 adam_g: check-tripleo-ironic-undercloud-precise 19:26:47 adam_g: thats the one I handed off my patch about race conditions to you :) 19:26:52 for triple0, this needs approving (just rechecked it): https://review.openstack.org/96498 19:26:54 adam_g: [you can check your IRC logs :P] 19:26:57 96558 & 96902 address that 19:27:47 lifeless, right, the fix of which is still blocked on a refactor.. last week didn't help. 19:28:09 Shrews: ack. with that many +2's it shouldn't be a problem to land it today (if the gate lets us) 19:28:34 ok, let's move on as there's a few more items to cover 19:28:42 adam_g: (note that that might not be the cause, or the whole cause, it $whatever - what i needed to handoff was the 'sit on problem job and make damn thing work' 19:28:46 one quick note on bug triage in general 19:29:00 let's start using tags to categorize bugs we see 19:29:21 dtantsur proposed the "driver" tag. I'd like to propose a few different ones 19:29:39 anyone want to discuss those, let's talk after the meeting -- otherwise, I'll just put up a wiki page today 19:29:46 driver for the nova driver? or drivers in ironic itself (e.g pxe)? 19:29:54 lucasagomes: eactly. i'd like to clarify that sort of thing 19:30:00 ack 19:30:09 +1 to more tags 19:30:46 #action devananda to write a wiki on bug tags, link from our main wiki 19:31:04 #topic subteam: IPA 19:31:16 russell_h or jroll: either of you have any updates to share? 19:31:21 hi! 19:31:28 just a couple of things 19:31:43 1) I put up a spec for the agent driver on friday - please review :) https://review.openstack.org/#/c/98506/ 19:32:03 #link https://review.openstack.org/#/c/98506/ 19:32:06 :-p 19:32:10 #info spec for IPA's driver now available -- please review! https://review.openstack.org/#/c/98506/ 19:32:15 2) I've put up a high-level todo list, for the road to getting the agent stuff merged, and beyond: https://etherpad.openstack.org/p/ipa-todos 19:33:04 jroll: good stuff 19:33:07 our main goal right now is refactoring the agent driver as stated there 19:33:08 nice 19:33:39 I'd like to land that sometime before the mid-cycle 19:33:57 I think that's it from me 19:34:13 jroll: sort of serious, sort of joking -- does it work now? 19:34:47 jroll: it would be good to have a walkthrough in that etherpad showing other devs how to replicate/create an env to do a deploy using IPA 19:34:56 devananda: for some definition of 'work' 19:35:05 devananda: it's fairly reliable, honestly 19:35:08 jroll: is underselling it 19:35:28 we've been testing and things are typically happy 19:35:32 great 19:35:33 and yes, docs 19:35:35 * jroll adds to list 19:35:49 jroll: I have not looked, (and may have already asked) is there a DIB element for Ironic-IPA 19:35:53 jroll: russell_h: is dwalleck still working on tempest for ipa? 19:35:55 i'd like to also see a list of known missing things (after all, that's part of the plan) 19:36:10 NobodyCam: not today 19:36:21 jroll: by "missing" i mean compared to the PXE driver. I know ya'll have a lot more stuff planned that PXE wont do 19:36:21 NobodyCam: The existing agent image is built using coreos and run in a container. I'll gladly review additions of DIB elements. 19:36:24 devananda: missing for what? feature parity with pxe? 19:36:26 ok 19:36:29 right 19:37:00 NobodyCam: should be relatively trivial to do, given all the dependencies are documented in the Dockerfile in the root of the repo. 19:37:08 devananda: my goal is to make that an empty set before landing :) 19:37:19 jroll: ++ 19:37:30 ack... I can help with dib element, but will nned to get myself up to speed on IPA 19:37:37 jroll: would be good to have that gap outlined upfront, so that folks aren't surprised when reviewing it 19:37:53 devananda: of course, it's now on my todo list :) 19:38:15 anything else on IPA? 19:38:36 I think that's it 19:38:50 great, thanks for the updates! 19:38:54 #topic subteam: oslo 19:39:00 :) 19:39:02 GheRivero: hi! any updates? 19:39:09 nothing new. Like almost every other project, the gate issues blocked it. 19:39:46 some blocker patches were approved for oslo.db, but there are others in the queue 19:39:51 the same for oslo.i18n 19:40:20 actually I have something to point out - our DB migration code, which is largely based on oslo-incubator's db migration code, is badly broken 19:40:24 #link http://lists.openstack.org/pipermail/openstack-dev/2014-June/036950.html 19:40:33 * db migration test code, i mean 19:41:05 tldr; we're not running db migration tests in the check/gate queues currently 19:41:10 and we shouldn't enable them until this is fixed 19:41:12 :( 19:41:15 yeah 19:41:17 because they'll introduce random failures 19:41:55 if anyone is familiar with the oslo db migration code and wants to fix it locally -- that'd be best 19:42:24 #link http://lists.openstack.org/pipermail/openstack-dev/2014-June/036950.html 19:42:48 devananda email to the mailist ^ there's some info about the currently situation of the migration scripts 19:42:58 so 19:43:02 devananda: let me check my understanding 19:43:11 devananda: there is a single DB server - mysql/whatever 19:43:25 devananda: and multiple tests that can affect the schema on it, and they run concurrently? 19:43:45 lifeless: in one configuration, yes. 19:43:55 devananda: which configuration is that? 19:44:12 lifeless: the one that is currently being used by oslo-incubator and ironic 19:44:25 devananda: so the situation as I described it is the situation today? 19:44:30 if those tests were enabled 19:44:42 lifeless: i haven't looked at oslo.db, it may not be affected. nova is nto affected, because it's using older code (pre-oslo-incubator DB migration code) 19:45:02 devananda: do our other tests depend on that DB and schema? Or is this isolated to a small set of our tests? 19:45:46 lifeless: I believe it affects all our unit tests which use the DB (they share a single DB schema currently, AFAIUI) 19:46:10 lifeless: but I haven't looked at /that/ aspect yet 19:46:11 devananda: let me rephrase; do many of our unit tests use the DB, or is it mocked out for most of them ? 19:46:41 lifeless: not sure at the moment. that email was only referring to migration tests 19:46:46 yeah 19:46:53 ok so we can take this to the main channel 19:46:56 but I have a few suggestions 19:47:01 right, i have some too 19:47:09 good :) 19:47:21 suggestions at dawn, on the commons 19:47:38 i was mentioning it to draw attention to the fact that we're running db migration tests right now -- and we shouldn't just start running that test, cause it'll break 19:47:45 cool. moving on :) 19:47:52 #topic open discussion 19:48:00 12 minutes left! we're doign great today :) 19:48:27 devananda, what we are expecting to be covered on the mid-cycle with nova? 19:48:40 devananda, mostly about the nova ironic driver and the path to get it in? 19:48:47 oh! gah! of course Ishould have announced that 19:49:11 #info mid-cycle announced: details here: https://wiki.openstack.org/wiki/Sprints/BeavertonJunoSprint 19:49:46 lucasagomes: so we're co*located* with nova, but not having a joint summit 19:49:56 we'll be mostly doing our own thing in a separate room 19:50:08 with easy access back and forth, and probably daily meetings with them 19:50:16 to sort out landing the nova driver 19:50:24 right 19:50:43 lucasagomes: so we should have our own agenda 19:50:52 I've put some ideas in this etherpad 19:50:53 #link https://etherpad.openstack.org/p/juno-ironic-sprint 19:51:05 +1, wil take a look and put some ideas as well 19:52:23 aside from the nova driver and IPA, I think it's too early to know what code we'll all be hacking on at that point 19:52:33 If the Triple0 is the week before, does anyone plan to attend? 19:53:06 Shrews: I'll probably be at TripleO as well 19:53:28 devananda: cool. i might have to attend part of that one instead :( 19:53:36 lifeless: any thoughts on when you expect to have confirmation of the tripleo dates? 19:53:39 Shrews: noooo 19:55:28 devananda: today I hope 19:55:48 lifeless: ack 19:55:59 if there's nothing else, let's end a few minutes early 19:56:19 \o/ 19:56:30 wow 19:56:32 :) 19:56:36 Thank you all 19:57:01 thanks! 19:57:05 #endmeeting