[openstack-dev] [vmware] VMwareAPI sub-team status update

Shawn Hartsock hartsocks at vmware.com
Fri Jun 14 15:49:45 UTC 2013


Greetings programmers!

This is a regular report I'll be sending out on the status of the Nova Compute driver for VMware API. (The product family is called vSphere and covers the ESX, ESXi, and vCenter products which all use the same API by the way.) If you have a patch you want me to track, review, or mention, please put me as a reviewer: http://i.imgur.com/XLINkt3.png

== Reviews ==

Open Reviews: 9
Recently Closed: 2 

Reviews *ready* for core developer attention:
https://review.openstack.org/#/c/29552/
https://review.openstack.org/#/c/30036/
https://review.openstack.org/#/c/30822/
https://review.openstack.org/#/c/31593/
... these have had a number of +1 reviews from the VMwareAPI community (people known to have VMware API expertise) so they are ready for some core-developer review! Let's solicit some attention from them only when appropriate and only after we can agree that this code is good from a VMwareAPI perspective.

Reviews needing *vmware* expert attention:
https://review.openstack.org/#/c/29396/
https://review.openstack.org/#/c/29453/
https://review.openstack.org/#/c/30282/
https://review.openstack.org/#/c/30628/
... these have *not* been looked at by enough non-core reviewers with VMware API expertise. We need folks listed on this email's "CC" block to come and spend some time on these. If you are doing VMware related work and need reviews, reach out to me, and I'll try to coordinate some help for you.

Closed reviews: (celebrate the victories!)
https://review.openstack.org/#/c/30545/
https://review.openstack.org/#/c/31454/
... these were closed very quickly (relatively speaking) so they are worth studying and learning from. Small patches. Directed fixes. Clear and straight-forward changes.

Is your review not listed?
* add me as a reviewer http://i.imgur.com/XLINkt3.png

Is your review not listed *ready* for core?
* get more +1 from the VMware API maintainers and trusted VMware API experts in the OpenStack community!

== Blueprints ==
see: https://blueprints.launchpad.net/openstack?searchtext=vmware
Of the 10 proposed blueprints, only 3 have commitments. Only 1 has "good progress" ... many of us are still dedicated to "fire-fighting" activities. 

* https://blueprints.launchpad.net/nova/+spec/multiple-clusters-managed-by-one-service
** Multiple VMware vCenter Clusters managed using single compute service
** Target: Havana-2 (July 18th)
** review: https://review.openstack.org/#/c/30282/ (listed as needs attention by VMwareAPI experts)

We need VMwareAPI people to spend some time discussing this. This is currently not anywhere near ready for the core developers to look at.


* https://blueprints.launchpad.net/nova/+spec/improve-vmware-disk-usage
** Enhance vmware Hyper vm disk usage
** Target: Havana-2 (July 18th)
** review: [none]

We currently do not know what this is, no one has discussed it. It has been accepted by someone. We don't know why. Good progress, however. I'm sure it's important for some reason.

* https://blueprints.launchpad.net/glance/+spec/hypervisor-templates-as-glance-images
** VMware vCenter templates available as glance images
** Target: Havana-2 (July 18th)
** review: [none] 

I am aware, that currently, there is some debate on how best to add this feature. Some proposed solutions may "break" Glance while others allow vCenter to act as a Glance storage device by creating a Glance level plugin which our Nova compute Driver can then use extra meta-data to short-cut the copy process saving network bandwidth by handling the template copy inside vCenter. I've not seen code. I would like to see this listed as "in Discussion" but I lack the authority to move these around.

* https://blueprints.launchpad.net/nova/+spec/live-snapshots
** Add ability to create live snapshot for VMs
** Target: [none]
** review: [none]
** see: http://eavesdrop.openstack.org/meetings/nova/2013/nova.2013-06-06-21.00.log.html#l-18

This is a *new* feature OpenStack core wants to add. Technically speaking, it looks easy for us to do in VMwareAPIs but I'm not sure we have bandwidth to make this happen quickly. Is there anyone who thinks they could tackle this in a timely manner? I can probably start on this task in late July or early August but I'm booked solid right now.

Personally, I look forward to the day we've managed to kill off the 10 critical/high priority bugs we have open and start to work on forward looking features to improve OpenStack + VMware. Which brings me to BUGS!
== Bugs ==
see: https://bugs.launchpad.net/nova/+bugs?field.tag=vmware

That "vmware" tag is critical. If you want my attention or the attention of other VMware folks you need to tag! If you are working but haven't submitted code, make a comment, let us know you are working!

Just the critical/high priority bugs:
https://bugs.launchpad.net/nova/+bug/1105032 (active in the last 7 days)
https://bugs.launchpad.net/nova/+bug/1180044 (active)
https://bugs.launchpad.net/nova/+bug/1183192 (no action since May 24th!!!)
High priority...
https://bugs.launchpad.net/nova/+bug/1104994 (active)
https://bugs.launchpad.net/nova/+bug/1177993 (no action since May 16th!!!)
https://bugs.launchpad.net/nova/+bug/1178369 (active)
https://bugs.launchpad.net/nova/+bug/1180471 (active)
https://bugs.launchpad.net/nova/+bug/1180779 (active)
https://bugs.launchpad.net/nova/+bug/1180897 (active)
https://bugs.launchpad.net/nova/+bug/1183452 (fix comitted! good work!)

I'm happy to say *all* these bugs currently have *someone* working on them. Several are related to the patches listed above. There are a few where I will be writing the bug's owners directly to make sure they are still available to create a fix for the bug in a timely manner. If I don't hear from them by next Friday I will assign new people to the bugs and we'll keep moving. I would *love* to see *all* these closed by the Havana-2 deadline but I don't want to rush people. Let's see where people are in 7 days.

We have a lot of work to do! Let's get to it!

BTW: sorry for the long email. Future updates will be shorter since there will be less to cover.

Meeting info: https://wiki.openstack.org/wiki/Meetings/VMwareAPI
We maintain a channel for general discussion of VMwareAPI on freenode IRC at #openstack-vmware I try to hang out there regularly.

Outside meetings, I encourage people to communicate! If you are working on something let us know otherwise, how can we help you?

# Shawn Hartsock, VMware's Nova Compute driver maintainer



More information about the OpenStack-dev mailing list