17:00:45 <tjones> #startmeeting vmwareapi
17:00:45 <openstack> Meeting started Wed Oct  8 17:00:45 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:46 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:48 <openstack> The meeting name has been set to 'vmwareapi'
17:00:52 <tjones> hi folks
17:00:56 <thangp> o/
17:00:56 <arnaud> hi
17:00:56 <rgerganov> hello
17:01:27 <tjones> lets get started
17:01:32 <tjones> #topic BP for kilo
17:01:51 <tjones> #link https://review.openstack.org/#/q/status:abandoned+project:openstack/nova-specs+message:vmware,n,z
17:02:02 <tjones> we have a number of abandoned BP here
17:02:34 <tjones> if you want to resurect - it's probably a good time to do so
17:03:42 <tjones> here's our current list for kilo BP - https://etherpad.openstack.org/p/VMwareapi-kilo
17:04:04 <tflower> o/
17:04:21 <tjones> we don't have garyk here (yet) some are here
17:04:51 <tjones> tfldid you have a chance to sync with arnaud on your image optimization bp?
17:05:51 <tjones> sorry that was tflower
17:06:00 <tjones> not sure how that happened...
17:06:19 <tflower> tjones, actually we're just talking
17:06:46 <tflower> Hopefully I can make a bit of a start next week
17:07:01 <tjones> i'd like for the BP we are proposing to be in decent shape *before* the summit this time
17:07:32 <tflower> I'll do my best
17:07:35 <tjones> i.e. written, reviewed by us, and socialized on the ML.  Im hoping this will help us
17:07:37 <arnaud> +1 tjones
17:08:05 <rgerganov> I will propose two blueprints related to VM consoles
17:08:06 <tflower> tjones, does that include code or just the blueprint + specs? (just trying to figure out the process)
17:08:17 <tjones> rgerganov: can you add them to the etherpad?
17:08:40 <tjones> tflower: BP in nova-specs.  code if you have it, but not necessary
17:08:51 <tflower> ok, thanks
17:09:01 <rgerganov> tjones: I will
17:09:07 <tjones> currently this is our only proposed spec - https://review.openstack.org/#/q/status:open+project:openstack/nova-specs+message:vmware,n,z
17:10:21 <tjones> we don't have a ton of time - so by next week if we just had a skelton of BP we are working on up on nova specs then we see how to prioritize the list
17:10:44 <tjones> does that sound reasonable?
17:11:01 <tflower> sounds good to me
17:11:40 <tjones> ok anything anyone want to discuss on kilo?
17:12:57 <tjones> ok lets move on then
17:12:59 <johnthetubaguy> hey, maybe I could reach out about specs?
17:13:11 <tjones> ok sure - go ahead johnthetubaguy
17:13:12 <johnthetubaguy> we had some stuff that was a near miss in juno
17:13:24 <johnthetubaguy> happy to help try and express that into kilo-1
17:13:30 <tjones> thanks!!
17:13:40 <johnthetubaguy> so reach out to on IRC, and lets do this thing
17:13:46 <johnthetubaguy> I am doing the same for the hyper-v folks
17:14:01 <tjones> ok thanks a lot - that would be awesome.  I think there are just 4 but i'll check
17:14:08 <johnthetubaguy> you have both had a rough time of it, so trying to make sure I can get you through any red tape as fast as possible!
17:14:17 <tjones> we areally appreciate this!
17:14:22 <tjones> and really too
17:14:28 <johnthetubaguy> np
17:14:49 <johnthetubaguy> certainly want the already written code to get up for review and through all the policy stuff ASAP
17:14:50 <tjones> i'll reach out to the BP owners of those and let them know
17:14:57 <johnthetubaguy> cool, thanks
17:15:22 <johnthetubaguy> I will run off now, I just happen to see specs mentioned, and wanted to reach out to you folks
17:15:33 <tjones> thanks see ya
17:15:37 <johnthetubaguy> cools
17:15:40 <tjones> anything else on BP guys before we do bugs?
17:16:12 <tjones> #topic bugs
17:16:16 <tjones> we have a bunch
17:16:17 <tjones> http://tinyurl.com/p28mz43
17:17:13 <tjones> anything we think is going to hit a customer putting openstack in production should be assigned to someone actively working on it.
17:17:58 <tjones> we are actually in decent shape - except for a couple
17:18:00 <tjones> #link https://bugs.launchpad.net/nova/+bug/1255317
17:18:02 <uvirtbot> Launchpad bug 1255317 in nova "VMware: can't boot from sparse image copied to volume " [High,Triaged]
17:18:27 <tjones> #link https://bugs.launchpad.net/nova/+bug/1325789
17:18:29 <uvirtbot> Launchpad bug 1325789 in nova "VMware: should not take the first host found in the cluster to perform iSCSI related operations" [High,Confirmed]
17:18:55 <tjones> and this one is critical and needs reviews #link https://bugs.launchpad.net/nova/+bug/1345460
17:18:56 <uvirtbot> Launchpad bug 1345460 in nova "VMware: resize fails when there is more than one compute node" [Critical,In progress]
17:19:15 <tjones> this one also needs reviews #link https://bugs.launchpad.net/nova/+bug/1226543
17:19:16 <uvirtbot> Launchpad bug 1226543 in nova "VMware: attaching a volume to the VM failed" [High,In progress]
17:19:32 <tjones> actually - a bunch need review
17:19:50 <tjones> looking at this link - http://54.201.139.117/nova-bugs.html  but vmware in the search box and select ready for review
17:19:52 <rgerganov> I don't like the patch proposed for bug 1226543
17:19:58 <uvirtbot> Launchpad bug 1226543 in nova "VMware: attaching a volume to the VM failed" [High,In progress] https://launchpad.net/bugs/1226543
17:20:03 <tjones> if you guys can spare some cycles on reviewing the high it would be good
17:20:05 <browne> i'll try to help out with some reviews
17:20:33 <tjones> thangp: is here - rado can you explain your concern?
17:20:51 <rgerganov> tjones: sure
17:21:29 <rgerganov> my thinking is that we should allow attaching scsci volumes to instances having root disks on ide controller
17:21:44 <thangp> so danpb commented on it
17:21:53 <thangp> it's a compromise
17:22:02 <thangp> we have to look at disk_bus for the volume
17:22:15 <thangp> if it is = scsi, then we add the controller
17:22:20 <thangp> otherwise throw an error
17:22:29 <rgerganov> oh, I haven't seen the comment from danpb
17:22:31 <thangp> i'm going to work on a patch for that later today
17:22:42 <rgerganov> thangp: thanks, this is great
17:22:43 <tjones> https://review.openstack.org/#/c/122251/2/nova/virt/vmwareapi/volumeops.py
17:22:48 <thangp> :)
17:22:51 <tjones> great
17:22:58 <tjones> any other bugs needing discussion?
17:24:04 <tjones> #topic open discussion
17:24:32 <tjones> if nothing we can end early
17:26:03 <tjones> i just want to reiterate - please post your BP in nova-specs by next meeting.  Not necessary to have everything complete - at least a skeleton.  That way we as a team can review and decide on our priorities for kilo.  we know not everything gets in - so we should have decide what is critical for us and focus there.
17:26:12 <tjones> any comments on that?
17:27:17 <tjones> *listens*
17:27:23 <tjones> *thinking we will end early*
17:27:26 <browne> do we have an etherpad of possible nova-specs
17:27:36 <tjones> https://etherpad.openstack.org/p/VMwareapi-kilo
17:27:47 <browne> tjones: thx
17:28:04 <rgerganov> tjones: do we need to file both blueprints *and* specs by the next meeting or only blueprints?
17:28:05 <tjones> they need to end up here https://review.openstack.org/#/q/status:open+project:openstack/nova-specs+message:vmware,n,z
17:28:17 <tjones> specs
17:28:21 <tjones> BP is in the spec - right?
17:28:35 <rgerganov> I thought that we need both
17:28:38 <rgerganov> nevermind
17:29:01 <tjones> not that i am aware of - the process changed in juno - just post your spec in nova-specs.  that is the BP
17:29:14 <tjones> anyone disagree with that??
17:29:49 <tjones> now i am confused too
17:30:08 <arnaud> no tha'ts correct
17:30:25 <tjones> ok - so JUST specs for next week
17:30:30 <rgerganov> ok :)
17:30:34 <tjones> :-D
17:30:42 <arnaud> :)
17:31:07 <tjones> ok lets end early then
17:31:10 <tjones> thanks folks
17:31:21 <browne> bye
17:31:26 <tjones> #endmeeting