Open Stack

Hi Miko,
it is possible to develop a neutron extension for achieveing your goal.
Indeed for a customer we developed a ML2 driver that creates the needed
portgroups and connect them to the right vlan in vCenter and hence when
VMware VMs are created connect them to the create portgroups. The solution
in this case is very simple, i.e. all the traffic goes through the
controller nodes (no dvr, for example using the vmware proxy compute).
Unfortunately, I don't think we can share the code (the customer retained
the IPR on it) :(

my suggestion is:
- have a look on how to create a ML2 plugin
- understand vCenter APIs

Br,
Federico

--
Future Internet is closer than you think!
http://www.fiware.org

Official Mirantis partner for OpenStack Training
https://www.create-net.org/community/openstack-training

-- 
Dr. Federico M. Facca

CREATE-NET
Via alla Cascata 56/D
38123 Povo Trento (Italy)

P  +39 0461 312471
M +39 334 6049758
E  federico.facca at create-net.org
T @chicco785
W  www.create-net.org

On Thu, Sep 24, 2015 at 11:01 AM, Miko Bello <openstack at mikebeauty.com>
wrote:

> Hi Folks,
> i would like to know if anybody has tried to implement a neutron solution
> with vsphere without using NSX-like solutions.
> I mean, my lab environment is composed of :
>
>  - 1 network node ( neutron )
>  - 1 controller node
>  - 2 compute node ( kvm)
>  - 1 compute node linked to a cluster vsphere 6.0
>
> i tried, without success ;( to deploy an instance on vsphere node with a
> network configuration of type VLAN; ( obviously, in this configuration,i
> have not the ambition of a ovs solution type :) )
> so my questions are: it's' possible to implement a network neutron
> solution of type VLAN ? if yes how can i do?
> Thanks in advantage.
> Miko Bello
>
>
>
>
>
>
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20150924/e589be49/attachment.html>