Re: [openstack-dev] [fuel] [vmware] Two hypervisors in one cloud

2015-01-25 Thread Kevin Benton
Yes, you are correct that the suggestion is to have the integration layer in Neutron backed by 3rd party testing. However, there is nothing technical preventing you from specifying an arbitrary python path to load as a driver/plugin. If there is a lot of demand for vDS support, it might be worth

Re: [openstack-dev] [fuel] [vmware] Two hypervisors in one cloud

2015-01-25 Thread Romil Gupta
Hi Andrey, We do a have a opensource Neutron based solution for VMware vCenter-oriented environment in Kilo, please have look in the links below: https://github.com/stackforge/networking-vsphere(For Kilo release woking in progress) https://github.com/hp-networking/ovsvapp(With Juno stable) On

Re: [openstack-dev] [fuel] [vmware] Two hypervisors in one cloud

2015-01-25 Thread Romil Gupta
With correct links: https://github.com/stackforge/networking-vsphere/tree/master/specs/kilo https://github.com/stackforge/networking-vsphere/ https://github.com/hp-networking/ovsvapp On Sun, Jan 25, 2015 at 7:28 PM, Romil Gupta romilgupt...@gmail.com wrote: Hi Andrey, We do a have a

Re: [openstack-dev] [fuel] [vmware] Two hypervisors in one cloud

2015-01-24 Thread Andrey Danin
I agree. But, as far as I know [2], there should be a some kind of ML2 integration layer for each plugin, and it should be in Neutron code base (see [1] for example). There is no vDS ML2 driver in Neutron at all and FF will become soon. So, it seems we cannot manage to adjust a blueprint spec [3],

Re: [openstack-dev] [fuel] [vmware] Two hypervisors in one cloud

2015-01-23 Thread Kevin Benton
It's worth noting that all Neutron ML2 drivers are required to move to their own repos starting in Kilo so installing an extra python package to use a driver will become part of the standard Neutron installation workflow. So I would suggest creating a stackforge project for the vDS driver and