>
>
>
>
> From: Mike Scherbakov [mailto:mscherba...@mirantis.com]
> Sent: vendredi 21 novembre 2014 12:52
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Fuel] Fuel extension with VXLAN support
>
>
>
> Samuel, Vladimir,
?
Or should we create a new one?
From: Mike Scherbakov [mailto:mscherba...@mirantis.com]
Sent: vendredi 21 novembre 2014 12:52
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Fuel] Fuel extension with VXLAN support
Samuel, Vladimir,
I see a little
Samuel, Vladimir,
I see a little issue with blueprint and real use cases.
Currently we do not collect use cases. Can we start doing this in some
section of whether design doc, or in blueprint itself? We've got linux
bonds, vxlan, multiple ranges for mgmt network, etc.
On Fri, Nov 21, 2014 at 2:26
Hi, Samuel
I think the case that you are talking about is an ability to use arbitrary
interfaces for different purposes. AFAIK, this use case is covered by
https://blueprints.launchpad.net/fuel/+spec/advanced-networking blueprint.
On Fri, Nov 21, 2014 at 12:04 PM, wrote:
> Hello,
>
>
>
> I hav
