Open Stack

Hi Ilkka,

As Mathieu suggested there is a blueprint submission and revision
process put in place since the Juno release. Also, since Icehouse, to
incorporate a new plugin/mechanism driver into the Neutron source
tree, and to be designated as compatible, such a plugin/driver must be
accompanied by external third party CI testing (more details in [1]).

This means that, once the blueprint work has been approved, the code
must be submitted through the same review process adopted for the
blueprint, as detailed in [2], and accompanied by validation through
third party CI.

This sounds like a lot of work, but it is aimed at ensuring all the
usual ilities of the software being part of the official source tree.

That said, you are not alone and you can tap into the usual channels,
like the mailing list or IRC ([3]). If there is anything vmware
specific that you would like to address, we are here to help, so feel
free to direct your questions to #openstack-vmware.

Keep up the good work!

Cheers,
Armando

[1] - https://wiki.openstack.org/wiki/Neutron_Plugins_and_Drivers
[2] - https://wiki.openstack.org/wiki/Gerrit_Workflow
[3] - https://wiki.openstack.org/wiki/IRC

On 6 May 2014 01:17, Mathieu Rohon <mathieu.rohon at gmail.com> wrote:
> Hi IIkka,
>
> this is a very interesting MD for ML2. Have you ever tried to use your
> ML2 driver with VMWare drivers on the nova side, so that you could
> manage your VM with nova, and its network with neutron.
> Do you think it would be difficult to extend your driver to support
> vxlan encapsulation?
>
> Neutron has a new process to validate BP. Please follow those
> instructions to submit your spec for review :
> https://wiki.openstack.org/wiki/Blueprints#Neutron
>
> regards
>
> On Mon, May 5, 2014 at 2:22 PM, Ilkka Tengvall
> <ilkka.tengvall at cybercom.com> wrote:
>> Hi,
>>
>> I would like to start a discussion about a ML2 driver for VMware distributed
>> virtual switch (dvSwitch) for Neutron. There is a new blueprint made by Sami
>> Mäkinen (sjm) in
>> https://blueprints.launchpad.net/neutron/+spec/neutron-ml2-mech-vmware-dvswitch.
>>
>> The driver is described and code is publicly available and hosted in github:
>> https://blueprints.launchpad.net/neutron/+spec/neutron-ml2-mech-vmware-dvswitch
>>
>> We would like to get the driver through contribution process, what ever that
>> exactly means :)
>>
>> The original problem this driver solves for is is the following:
>>
>> We've been running VMware virtualization platform in our data center before
>> OpenStack, and we will keep doing it due existing services. We also have
>> been running OpenStack for a while also. Now we wanted to get the most out
>> of both by combining the customers networks on the both plafroms by using
>> provider networks. The problem is that the networks need two separate
>> managers, neutron and vmware. There was no OpenStack tools to attach the
>> guests on VMware side to OpenStack provider networks during instance
>> creation.
>>
>> Now we are putting our VMware under control of OpenStack. We want to have
>> one master to control the networks, Neutron. We implemented the new ML2
>> driver to do just that. It is capable of joining the machines created in
>> vSphere to the same provider networks the OpenStack uses, using dvSwitch
>> port groups.
>>
>>
>> I just wanted to open the discussion, for the technical details please
>> contact our experts on the CC list:
>>
>> Sami J. Mäkinen
>> Jussi Sorjonen (freenode: mieleton)
>>
>>
>> BR,
>>
>> Ilkka Tengvall
>>  Advisory Consultant, Cloud Architecture
>>  email:  ilkka.tengvall at cybercom.com
>>  mobile: +358408443462
>>  freenode: ikke-t
>>  web:    http://cybercom.com - http://cybercom.fi
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev