fuel-dev team mailing list archive

[Jesse Pretorius <jesse.pretorius@xxxxxxxxx>]

On 11 August 2014 00:15, Dmitriy Novakovskiy <dnovakovskiy@xxxxxxxxxxxx>
wrote:

> 1) Am I right assuming that right now in Fuel there's no way to configure
> >1 Public L2 network? The only option is a single L2 network, may be
> tagged, and all Public rangers should be within it?
>
> Any hacks/workarounds available to bypass this?
>

Can you clarify whether you mean 'Public' or 'External' (aka Floating)
networks?

Fuel's current deployment method is to include Public & Floating within a
single CIDR with the option of multiple ranges within that CIDR for the
purpose of the Public (ie access to the API's and Horizon) and
External/Floating (ie public addresses to associate with instances)
addresses.

There is a blueprint to separate the two, but that will only be worked on
in Fuel 6.x. I do have a functional UI patch to do this and will try to
figure out during the course of this week whether it can be done through
the modification of the deployment instead of through code changes.

2) What is needed in order to use vxlan tunnels w/ Neutron+OVS? If i'm not
> mistaken it's just a switch of setting in config from GRE to VXLAN, or not?
>

I have no personal experience with this, but perhaps these references help?

http://www.opencloudblog.com/?p=300
http://www.gossamer-threads.com/lists/openstack/dev/38537
http://openstack.redhat.com/Using_VXLAN_Tenant_Networks