Open Stack

Samuel,

VXLAN was moved to 7.0, as you noted it won't make 6.1. Mirantis has
identified this as a high priority for 7.0 so it should get more attention
this time. However any assistance in CR / Testing is always appreciated.

On Thu, May 28, 2015 at 1:38 PM Samuel Bartel <samuel.bartel.pro at gmail.com>
wrote:

> Hi Sean,
>
> I understand and share you point of view. The best and cleaner solution
> would  be to have the vxlan support out of the box. Unfortunatly it is not
> the case for 6.0 and I doubt this feature can be available before HCF for
> 6.1 (planned in the next upcoming days).
>  That's why in my initial message I asked if  help is needed to ship this
> feature in 7.0
>
> Having a vxlan plugin is a workaround, an ugly one, but the only
> workaround which make the job in 6.0 and 6.1.
> My actual vxlan plugin modify ml2 neutron plugin configuration in order to
> switch segmentation type to vxlan and restart neutron services or neurton
> crm ressources. The only issue, I have for  the moment is to recreate net04
> network and corresponding subnet as you can't redefine an already defined
> resource in puppet.
>

The plugin tasks run as separate puppet jobs so they are not bound by this
restriction. Going forward with granular tasks, this will only be a problem
within the specific task.


> About the fact to choose GRE and having vxlan. it will be the same with
> contrail, nuage cinder netapp, nfs nova nfs glance plugins for example.  In
> the create env form you choose a configuration. But you can choose in
> settings tab by activating a particular plugin to override initial network
> or storage configuration. In every case, It will be done on purpose.
>
> --
> Regards,
> Samuel Bartel,
> IRC #samuelbartel
>
>
> 2015-05-28 21:42 GMT+02:00 Sean M. Collins <sean at coreitpro.com>:
>
>> On May 28, 2015 2:51:56 PM EDT, Andrey Danin <adanin at mirantis.com> wrote:
>>>
>>> Hi, Sean,
>>>
>>> A plugin cannot modify Fuel UI but it actually can change a segmentation
>>> type after deployment. On UI it's still GRE but in fact it will be VxLAN. I
>>> know, it's ugly, but should work.
>>>
>>> On Thu, May 28, 2015 at 7:47 PM, Sean M. Collins <sean at coreitpro.com>
>>> wrote:
>>>
>>>> VxLAN support cannot be made as a plugin because plugins cannot modify
>>>> the initial networking wizard (based on conversations I've had in
>>>> #fuel-dev) where the choices between Neutron VLAN, Neutron GRE, and
>>>> nova-network are shown to the user.
>>>>
>>>> I am currently working on this blueprint and have a WIP patch for
>>>> fuel-web. Please contact me if you want to help contribute to the work.
>>>>
>>>> --
>>>> Sean M. Collins
>>>>
>>>>
>>>> __________________________________________________________________________
>>>> OpenStack Development Mailing List (not for usage questions)
>>>> Unsubscribe:
>>>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>>
>>>
>>>
>>>
>> I don't think that's a good way to go about it, we'd be giving someone a
>> surprise if they actually wanted to deploy GRE only to discover it deployed
>> VXLAN.
>> --
>> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>>
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150602/9d084789/attachment.html>