[openstack-dev] [oslo] VMware tools in oslo-incubator or straight to oslo.vmware

Vipin Balachandran vbalachandran at vmware.com
Thu Jan 30 17:48:00 UTC 2014

This library is highly specific to VMware drivers in OpenStack and not a
generic VMware API client. As Doug mentioned, this library won't be useful
outside OpenStack. Also, it has some dependencies on openstack.common code
as well. Therefore it makes sense if we make this code as part of OSLO.


By the way, a work in progress review has been posted for the VMware
cinder driver integration with the OSLO common code
(https://review.openstack.org/#/c/70108/). The nova integration is
currently under progress.





From: Doug Hellmann [mailto:doug.hellmann at dreamhost.com] 
Sent: Wednesday, January 29, 2014 4:06 AM
To: Donald Stufft
Cc: OpenStack Development Mailing List (not for usage questions); Vipin
Subject: Re: [openstack-dev] [oslo] VMware tools in oslo-incubator or
straight to oslo.vmware




On Tue, Jan 28, 2014 at 5:06 PM, Donald Stufft <donald at stufft.io> wrote:

On Jan 28, 2014, at 5:01 PM, Julien Danjou <julien at danjou.info> wrote:

> On Tue, Jan 28 2014, Doug Hellmann wrote:
>> There are several reviews related to adding VMware interface code to
>> oslo-incubator so it can be shared among projects (start at
>> https://review.openstack.org/#/c/65075/7 if you want to look at the
>> I expect this code to be fairly stand-alone, so I wonder if we would be
>> better off creating an oslo.vmware library from the beginning, instead
>> bringing it through the incubator.
>> Thoughts?
> This sounds like a good idea, but it doesn't look OpenStack specific, so
> maybe building a non-oslo library would be better.
> Let's not zope it! :)

+1 on not making it an oslo library.


Given the number of issues we've seen with stackforge libs in the gate,
I've changed my default stance on this point.


It's not clear from the code whether Vipin et al expect this library to be
useful for anyone not working with both OpenStack and VMware. Either way,
I anticipate having the library under the symmetric gating rules and
managed by the one of the OpenStack teams (oslo, nova, cinder?) and VMware
contributors should make life easier in the long run.


As far as the actual name goes, I'm not set on "oslo.vmware" it was just a
convenient name for the conversation.





> --
> Julien Danjou
> # Free Software hacker # independent consultant
> # http://julien.danjou.info

> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140130/524a6540/attachment.html>

More information about the OpenStack-dev mailing list