17:00:15 #startmeeting vmwarepi 17:00:16 Meeting started Wed Apr 9 17:00:15 2014 UTC and is due to finish in 60 minutes. The chair is tjones. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:17 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:20 The meeting name has been set to 'vmwarepi' 17:00:42 hi folks - im running the meeting for hartsocks for the next 2 weeks 17:00:46 anyone here? 17:00:49 tjones: Does the typo in the meeting name matter? 17:00:55 ugh 17:01:00 oops 17:01:10 what's it supposed to be? 17:01:14 hi 17:01:26 * mdbooth doesn't know if it matters 17:01:35 hi 17:01:40 vmwarepi -> vmwareapi 17:01:48 heh 17:01:53 don't think it matters 17:02:06 lets get started. 17:02:12 #topic blueprints 17:02:26 anyone have a BP to discuss? 17:02:39 #link https://blueprints.launchpad.net/openstack?searchtext=vmware 17:02:45 tjones: i think that we have a few that are in review in the specs 17:02:52 yes we do 17:02:55 hold on 17:03:34 not sure how to filter on vmware here 17:03:50 we've got quite a few here 17:04:10 present :D 17:04:11 #link https://review.openstack.org/#/q/status:open+project:openstack/nova-specs,n,z 17:04:57 obvioulsy getting #link https://review.openstack.org/#/c/84307/ approved is critical cause we have a number of activities gated on it 17:05:26 any others that need specific attention? 17:05:43 i really hope that that gets approved soon. 17:05:58 im not sure what the hold up is 17:06:55 i think that we need to try and get cores to look at it. maybe russellb, dansmith and johnthetubaguy can take a look. the sooner it is approved the sooner we can start to get this in action 17:07:08 tjones: https://review.openstack.org/#/q/status:open+project:openstack/nova-specs+message:VMware,n,z 17:07:09 * mdbooth is still trying to open it 17:07:15 https://review.openstack.org/#/c/84307/ 17:07:32 browne: thanks 17:07:33 and http://docs-draft.openstack.org/07/84307/6/check/gate-nova-specs-docs/3cd7dff/doc/build/html/specs/juno/vmware-spawn-refactor.html 17:07:51 hey, can I help? blueprint issues? 17:07:58 +2's :) 17:08:12 johnthetubaguy: there is a post for the spawn refactor 17:08:16 https://review.openstack.org/#/c/84307/ 17:08:42 hi johnthetubaguy. we are just discussing getting approval on some critical BP. ^^ 17:09:03 right, totally swamped by the reviews at the moment, generally taking 15mins to an hour each, but we are getting some through now 17:09:48 johnthetubaguy: im hoping that one is pretty close. hartsocks has been working with dansmith on it quite a bit 17:10:29 tjones: yeah, I certainly did a few early revisions, its looking close 17:10:36 :-D 17:11:01 any other BP we need to discsuss? this is what we have outstanding #link https://review.openstack.org/#/q/status:open+project:openstack/nova-specs+message:VMware,n,z 17:11:23 tjones: i think that one and the oslo port are the two pressing ones 17:11:34 #link https://review.openstack.org/#/c/85469/ 17:12:06 that one could really use some reviews 17:12:47 i agree - getting those 2 moving would really help with future work 17:13:10 waiting for people typing…. before moving on 17:14:40 #topic bugs 17:14:49 anyone have a pressing bug for discussion? 17:15:12 we need to do a little triage i see 17:15:18 #link https://bugs.launchpad.net/nova/+bugs?field.tag=vmware 17:15:28 yeah, there are far too many open at the moment 17:15:46 yeah and also undecided prio and unconfirmed etc 17:16:02 i am looking into https://bugs.launchpad.net/nova/+bug/1296948 but i need minesweeper for that one. 17:16:03 Launchpad bug 1296948 in nova "VMware: Instance fails to spawn due to "Concurrent modification by another operation"" [Undecided,New] 17:16:23 sadly it is not up and running properly yet (i hope soon) 17:16:31 speaking of - it's still down 17:16:40 painful!! 17:16:48 do you know anyone who works on openstack that can look into it :) 17:16:52 what's the issue? 17:17:01 lol - i know a few 17:17:10 the upgrade from grizzly to havana broke a few things 17:17:15 browne: still issues after the upgrade 17:17:23 not to self - never upgrade before rc 17:17:41 yeah, we really need to learn that lesson for the next one :) 17:17:44 so we may have a quick meeting today. no more bugs?? 17:18:22 *fingers tapping* 17:18:45 there are the reviews at https://review.openstack.org/#/q/message:vmware+OR+message:vcenter+OR+message:vsphere+OR+message:esx+OR+message:vcdriver+OR+message:datastore,n,z for fixes. 17:18:58 Can I guauge the level of interest in moving to pyvmomi when we get to aob? 17:19:09 mdbooth: sure 17:19:16 lets finish up bugs 1st 17:19:38 ones importnat for rc are https://review.openstack.org/#/c/75788/ and https://review.openstack.org/#/c/80284/ 17:19:46 they are pending minesweeper 17:20:09 yeah they are running manually right?? 17:20:39 tjones: not sure. i'll ping sreeram and ryan 17:20:41 at least they were yesterday 17:20:47 yeah better ping 17:20:54 ok if no more bugs we can move on?? 17:21:14 #topic open-discussion 17:21:17 mdbooth: go! 17:21:23 heh 17:21:26 pyvmomi: is anybody interested? 17:21:30 yes! 17:21:34 I know hartsocks is very keen on it 17:21:44 Has anybody given it any specific thought, yet? 17:21:54 specific == code/bp 17:22:24 mdbooth: other than #link https://review.openstack.org/#/c/69964/ 17:22:52 it's just been talk so far 17:23:02 but there is interest by a number of folks 17:23:02 Ok 17:23:04 Well I am interested in taking up the pyvmomi 17:23:22 @mdbooth oslo.vmware was kinda of a stepping stone towards a common library. 17:23:28 i think its very much worth exploring 17:23:48 vuil: Yeah, but it's still pretty much the old code 17:23:58 assuming we fix up the interfaces, the next thing we can do is to swap a lot of the guts underneath with pyvmomi. 17:24:00 mdbooth: you mean oslo.vmware right? 17:24:15 I was thinking it might be possible to add pyvmomi to olso.vmware and make it possible to use both in parallel 17:24:21 Which would avoid a flag day 17:24:28 tjones: Yes 17:24:49 i.e. New or refactored code would use pyvmomi 17:24:56 Old code could continue for a bit 17:25:02 mdbooth: flag day = fire drill ? 17:25:14 flag day = all projects have to change at once 17:25:24 as a means for transition, sure, but no reason why the old code cannot be converted over as well. 17:25:40 mdbooth: ideally the api's should remain the same, the implementation with the backend driver will be updated 17:25:47 vuil: It can, but we're no longer the only user 17:25:50 vuil: i think he's just talking incremental changes which would be good 17:25:54 garyk: The api is broken ;) 17:26:18 but the same broken api's should continue to function in the same way 17:26:26 garyk: Agreed, yes 17:26:31 (providing enterprise grade solutions to customers :)) 17:26:36 until we replace all the code which uses it 17:27:02 correct 17:27:27 we need to avoid situations where different sets of functionality lies in suds/pymomi land. 17:27:42 crossing between those two may be more trouble than it is worth. 17:28:20 If they both use the same session, the only problem I see is caching 17:29:11 we could come up with a parallel implementation for oslo.vmware that provides the same functionality with the same interface 17:29:14 well you may end up having to translate objects in one world to the other. 17:29:22 but done in pyvmomi 17:30:11 Ok, I'm good. There's significant interest and no code. I'm happy to look at this in more detail and flesh out the bp with a proposal. 17:30:52 mdbooth: great! 17:30:59 anything else for open discussion? 17:33:40 sounds like the answer is no…… short meeting today then 17:34:29 #endmeeting