Open Stack

Hello,

Thanks for informations. As I wrote on openstack-dev list also, I don't need 
new network type with different L2 technology. In fact I'm trying to do 
something different (and I know that is not exactly L2). I want to have 
external network called for example bgp (it should be similiar to flat network) 
but when I assign IP from this network to instance than this IP should be 
added to announcing on bgp router (so I don't know arping or something like 
that from host).
I think that I can "hack" openvswitch agent which is running on compute host 
and add there some code which will be doing that. Maybe You know what exactly 
is happend in flat network when I assign IP from this network to instance (what 
methods are then running on host and where I should search it)?

--
Best regards
Sławek Kapłoński

Dnia środa, 19 lutego 2014 08:47:46 Robert Kukura pisze:
> On 02/18/2014 10:12 AM, Sławek Kapłoński wrote:
> > Hello,
> > 
> > I'm trying to make something with neutron and ML2 plugin. Now I need to
> > add my own external network type (as there are "Flat", "VLAN", "GRE" and
> > so on). I searched for manuals for that but I can't found anything. Can
> > someone of You explain me how I should do that? Is it enough to add own
> > type_driver and mechanism_driver to ML2? Or I should do something else
> > also?
> 
> Hi Sławek,
> 
> In general, all that should be needed to extend ML2 with new drivers is:
> 
> 1) Add the new driver class(es)
> 2) Add the new driver entry points to neutron.ml2.type_drivers and/or
> neutron.ml2.mechanism_drivers in setup.cfg.
> 3) When using the new drivers, list their entry points in type_drivers
> and/or mechanism_drivers in the [ml2] section of
> etc/neutron/plugins/ml2/ml2_conf.ini, and add any other needed
> configuration for those drivers.
> 
> I think discussing the specifics of what you are trying to accomplish
> with these new drivers on openstack-dev, at the upcoming design summit,
> at the weekly ML2 IRC meeting, and/or in a blueprint, would pay off,
> since adding new drivers may or may not be the best solution. Generally,
> type drivers should correspond to specific virtual network segmentation
> methods, or maybe to variations on the way those are managed (i.e.
> tunnel endpoint management).
> 
> Hope this helps,
> 
> -Bob
> 
> > Thanks in advance
> 
> _______________________________________________
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to     : openstack at lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack