Re: [openstack-dev] [neutron][lbaas][fwaas][oslo] Common code between VMWare neutron plugin and services plugins

2014-12-15 Thread Kobi Samoray
It shouldn’t drag any additional dependencies - it’s REST API wrapper so 
nothing beyond XML/JSON/HTTP/threads should be used in these components.

> On Dec 15, 2014, at 18:23, Russell Bryant  wrote:
> 
> On 12/15/2014 11:20 AM, Kobi Samoray wrote:
>> 3. Add these components to oslo.vmware project: oslo.vmware contains, as of 
>> now, a wrapper to vCenter API. The components in discussion wrap NSX API, 
>> which is out of vCenter scope. Therefore it’s not really a part of 
>> oslo.vmware scope as it is defined today, but is still a wrapper layer to a 
>> VMWare product.
>> We could extend the oslo.vmware scope to include wrappers to VMWare 
>> products, in general, and add the relevant components under 
>> oslo.vmware.network.nsx or similar.
> 
> This option sounds best to me, unless the NSX support brings in some
> additional dependencies to oslo.vmware that warrant keeping it separate
> from the existing oslo.vmware.
> 
> -- 
> Russell Bryant
> 
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [neutron][lbaas][fwaas][oslo] Common code between VMWare neutron plugin and services plugins

2014-12-15 Thread Doug Wiegley


On 12/15/14, 8:20 AM, "Kobi Samoray"  wrote:

>Hi,
>Some files in neutron are common infrastructure to the VMWare neutron
>L2/L3 plugin, and the services plugins.
>These files wrap VMWare NSX and provide a python API to some NSX services.
>
>This code is common to:
>- VMWare L2/L3 plugin, which after the split should be held outside of
>openstack repo (e.g stackforge)
>- neutron-lbaas, neutron-fwaas repos, which will hold the VMWare services
>plugins
>
>With neutron split into multiple repos, in and out of openstack, we have
>the following options:
>1. Duplicate the relevant code between the various repos - IMO a pretty
>bad choice for obvious reasons.

Yeah, yuck.

>
>2. Keep the code in the VMWare L3/L4 plugin repo - which will add an
>import from the neutron-*aas repos to a repo which is outside of
>openstack.

Importing code from elsewhere, which is not in the requirements file, is
done in a few places for vendor libraries. As long as the mainline code
doesn’t require it, and unit tests similarly can run without that import
being present, I don’t see a big problem wit hit.

Doug


>
>3. Add these components to oslo.vmware project: oslo.vmware contains, as
>of now, a wrapper to vCenter API. The components in discussion wrap NSX
>API, which is out of vCenter scope. Therefore it’s not really a part of
>oslo.vmware scope as it is defined today, but is still a wrapper layer to
>a VMWare product.
>We could extend the oslo.vmware scope to include wrappers to VMWare
>products, in general, and add the relevant components under
>oslo.vmware.network.nsx or similar.
>
>Thanks,
>Kobi
>___
>OpenStack-dev mailing list
>OpenStack-dev@lists.openstack.org
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [neutron][lbaas][fwaas][oslo] Common code between VMWare neutron plugin and services plugins

2014-12-15 Thread Russell Bryant
On 12/15/2014 11:20 AM, Kobi Samoray wrote:
> 3. Add these components to oslo.vmware project: oslo.vmware contains, as of 
> now, a wrapper to vCenter API. The components in discussion wrap NSX API, 
> which is out of vCenter scope. Therefore it’s not really a part of 
> oslo.vmware scope as it is defined today, but is still a wrapper layer to a 
> VMWare product.
> We could extend the oslo.vmware scope to include wrappers to VMWare products, 
> in general, and add the relevant components under oslo.vmware.network.nsx or 
> similar.

This option sounds best to me, unless the NSX support brings in some
additional dependencies to oslo.vmware that warrant keeping it separate
from the existing oslo.vmware.

-- 
Russell Bryant

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev