17:02:33 #startmeeting vmwareapi 17:02:35 Meeting started Wed Jan 22 17:02:33 2014 UTC and is due to finish in 60 minutes. The chair is hartsocks. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:02:36 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:02:39 The meeting name has been set to 'vmwareapi' 17:02:44 hey folks, had my head in another meeting. 17:02:47 Who's around? 17:02:51 hi 17:03:00 hi, Eric's here 17:04:50 today might be a light day… lots of folks are busy with other things today... 17:05:25 hi 17:06:13 #link https://wiki.openstack.org/wiki/Meetings/VMwareAPI#Agenda 17:07:19 #link https://wiki.openstack.org/wiki/Icehouse_Release_Schedule 17:07:36 So the icehouse 2 deadline is tomorrow. 17:08:05 #link https://etherpad.openstack.org/p/vmware-subteam-icehouse-2 17:08:31 Last meeting I know I said we'd spend some time on bugs, but ... 17:08:53 garyk, how's your BP looking "vmware-hot-plug" for icehouse-2? 17:09:09 hartsocks: it was completed 2 weeks ago and is waiting for review 17:09:29 all of the bluepreints that i was working on for i-2 were completed at the beginning of the month 17:09:31 #link https://blueprints.launchpad.net/nova/+spec/vmware-hot-plug 17:09:40 they occasionally have rebases but no chnages 17:09:44 you're currently targeted at icehouse-3 17:09:50 Is that new? 17:10:10 i did not change it. maybe russellb went over all of the bps. not sure though 17:10:43 I'm targeted for icehouse-3 as well on autowsdl-repair… so that would be my guess. 17:11:12 i think that the problem that we have with these bps is we do not have core reviewers who are sponsoring us 17:11:24 pretty much. 17:11:26 correct 17:11:33 i deferred everything not merged 17:11:50 as i-2 was getting cut today 17:12:31 garyk: over 90% of the blueprints don't have core sponsors fwiw ... the sponsor thing isn't really being done at all. just making sure you know you're not singled out 17:13:03 russellb: thanks for the clarification 17:13:15 russellb: I think there was a fair bit of other stuff going on in i-2 anyway around gate and performance issues... 17:13:22 yes 17:13:23 i just hope that they get a few review cycles. some are features for parity 17:13:30 quite a small number of bps made it 17:13:57 russellb: is there anything we can do to try and help get more reviews through? 17:14:14 did the network objects at least make it or will they be in the gate for the next month (it is about 3 days to get on once approved) 17:14:15 not that i can think of really 17:14:27 network objects are not merged 17:14:34 :( 17:15:00 we're trying really hard to fix the gate 17:15:04 that's primary focus for me 17:15:34 not if it is worth anything but the minesweeper has been pretty stable the last few days - we had some hiccups last week. 17:15:47 definitely worth something :) 17:15:49 that's good to hear 17:15:53 you're ahead of the pack on that 17:16:17 I did get an update that the Minesweeper guys are ready to turn on −0 voting this week. 17:16:36 So, much kudos to our Minesweeper team. They have been working nights and weekends. 17:16:45 i think there was a mail on the list not to have the third party ci's do −1's etc 17:17:01 I used the phrase "-0" 17:17:15 to indicate that it would be a "-1" but we're not doing −1 yet. 17:17:25 ok 17:17:29 It's a "not positive" result. 17:17:59 … also as trivia if memory serves you can have a Floating point with a −0 representation in IEEE notation... 17:18:16 even though a negative sign doesn't make sense on a 0. 17:18:30 * hartsocks admits he's a math geek. 17:18:49 okay so there's nothing to discuss on BP this round. 17:19:19 I was waiting for i-2 to pass before I tried cutting code on the service validation BP for Nova. 17:19:21 just a quick update regarding the oslo progress. 17:19:38 vipin has broken the patch up into a number of small ones. 17:19:40 Vipin has broken his patch into 3 parts... 17:19:47 Oh… :-) 17:19:53 you wanted to give the update. 17:19:58 that is, the patch set for the common vmware driver code shared by cinder, nova, glance and soon to be ceilometer 17:20:22 There was some talk about making the Oslo incubated code a regular library. 17:20:28 I'm not sure what that means. 17:20:56 I know it means we get to test the code in the gate as opposed to moving through incubation. 17:21:24 Anybody here have anything to comment on that? 17:22:23 I take the silence as a no comment. 17:22:39 Anyone from Glance or Cinder here? 17:23:19 Can you paste the patch set link for moving common driver code? 17:23:29 1 sec... 17:23:43 #link https://blueprints.launchpad.net/oslo/+spec/vmware-api 17:23:53 #link https://review.openstack.org/#/q/topic:bp/vmware-api,n,z 17:23:56 Thanks 17:23:59 you can look at https://review.openstack.org/#/dashboard/9171 that has the patches posted by vipin 17:24:54 kirankv: looks like this is also i-3 at the soonest. 17:25:12 Any other BP we can talk about? 17:26:00 hartsocks: Thanks 17:26:25 #topic bugs 17:26:46 So, bugs still targeted at i-2 17:27:08 #link http://goo.gl/Qhe5Lt 17:27:15 … that was a nasty query 17:28:37 I got merge approval for #link https://bugs.launchpad.net/nova/+bug/1252400 and then I had to rebase :( 17:28:43 what is good is that they are all in progress 17:29:02 hmm... 17:29:14 which means that they need reviews 17:29:52 Yeah. Pretty much *no* progress. 17:29:53 why do you lost approvals if there are no conflicts for rebase? 17:30:11 rgerganov: if I remember correctly... 17:30:18 rgerganov: if the rebase is trivial then jenkins add in the reviews 17:30:28 feel free to ping the guys who reviewed and approved the code. 17:30:41 garyk, ok I will do that 17:30:59 it is a trivial fix sitting for 3 months ... 17:31:02 okay, I don't type fast enough. That's all I was going to say. :-) 17:31:05 most of the rebasing was my fault - i changed the test file names. humble apoligies 17:31:28 garyk, yes that was the reason for rebase 17:31:35 but I didn't get any conflicts 17:31:38 sorry 17:31:54 I wonder why this is not considered "trivial" by Jenkins 17:32:27 my guess is the patch's hash changed. 17:32:37 you couls always as on #openstack-infra - sure somethere will be able to explain or fix if it is a bug :) 17:33:07 fungi or joe gordon ,ay know 17:33:56 well… the trivial rebase code is here: 17:34:02 https://www.codeaurora.org/patches/quic/la/gerrit/trivial_rebase.py 17:34:23 so… the precise reason is somewhere in that… :-) 17:34:49 "'identical' (determined via git-patch-id) and reapply reviews onto the new" 17:35:12 git-patch-id is a hash of your patch's contents… so… if 1 character changes… different hash. 17:35:37 it's not very smart :-( 17:35:52 the review process is a real pain IMO 17:36:12 hartsocks, thanks for explaining this though 17:36:36 rgerganov: it has its advantages and disadvantages 17:36:45 Nova's currently got some problems that unfortunately affect the whole stack and as far as I can tell that's soaking up a *lot* of attention right now. 17:36:47 basic rule of thumb - is review and your code will be reviewed 17:37:42 a few cycles ago i think that vish would joke and say a bp would be approved if someone would give x reviews 17:38:11 about all we can do is review each other's code. 17:38:27 I would encourage the team to also review code outside the drivers. 17:38:50 We should also be building skills so that we can eventually help with the Nova level bugs that are putting the gate in trouble. 17:39:10 #topic open discussion 17:39:18 Since were' there in open discussion anyhow. 17:39:57 i-2 was pretty unsatisfying. 17:40:36 Personally I looked at this SSH timeout bug a few weeks ago. I know garyk also looked at a few weeks after me. I was never able to make any progress. How did that go? 17:41:01 i posted 2 patches which would help isolate the issues. they are still in review 17:41:17 #link https://etherpad.openstack.org/p/nova-gate-issue-tracking 17:41:22 i also posted one which break the gate for neutron - still in review…. 17:41:44 garyk: how do you know your patch fixes the issue? 17:42:16 i did not say that they fix problems, they help identify problems. 17:42:24 garyk: okay. 17:42:33 say for example with the ssh - we know if the server or the guest networking is the problem 17:42:44 it is mainly the wiring of the guests that causes the problems 17:43:07 problem with the gate is that there are moving targets. 17:43:20 #link https://review.openstack.org/#/c/66201/ 17:43:23 once it is networking, one it is virtual disks, one it is a race that got through the gate…. 17:43:26 wip 17:43:31 you have an interesting comment there… 17:43:55 ah, now i see the -1 17:43:58 "Since this change is, reasonably for this case, a change to not use exponential backoff that variable should be like 'wait_time' and not be a fraction." 17:44:03 This is interesting... 17:44:13 because I think we have a 1.0 in our wait time. 17:44:25 if they did the mat then they would see that the exponentional timeout is 1 sec every time 17:44:30 that is wrong 17:45:08 In general, from my days as an embedded C programmer I remember use of floating point is to be frowned upon. 17:45:13 i'll address the comment. thanks for pointing the −1 put 17:46:02 That's because FP calculations aren't smooth … that is you have gaps in IEEE representations between 0.0 and 1.0 17:46:42 … so in a system where you are doing lots of math on fractional values you can get non-integral representations of numbers as they move through certain hard to represent fractional values. 17:46:50 But... 17:46:54 this is Python. 17:47:16 so… we have different number representations. 17:47:18 :-) 17:47:23 math geek. remember. 17:47:50 anyway… in my gut, I feel like these time representations should never be fractional anyway. 17:48:17 thanks, i am going to drop the floating no. 17:48:37 You always have a discrete monotonic representation of time in a computer. It's the clock cycle. :-) 17:48:54 okay. 17:49:13 well, we have lots of time for open discussion or we can sign off. 17:49:20 any other topics? 17:50:50 we're on #openstack-vmware if people need to chat. 17:52:14 I'm going to try and cut a version of the service validation code over the next two weeks. I want it available for reaction at https://wiki.openstack.org/wiki/Nova/IcehouseCycleMeetup 17:52:42 I figure if I'm in person in front of folks they can throw eggs, or otherwise give feedback. 17:52:56 If nobody has another topic that's it today. 17:53:34 #endmeeting