Re: [openstack-dev] [Fuel] vxlan support
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 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 : > >> On May 28, 2015 2:51:56 PM EDT, Andrey Danin 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 >>> 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-requ...@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-requ...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Fuel] vxlan support
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. 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 : > On May 28, 2015 2:51:56 PM EDT, Andrey Danin 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 >> 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-requ...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Fuel] vxlan support
On May 28, 2015 2:51:56 PM EDT, Andrey Danin 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 >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-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > > >-- >Andrey Danin >ada...@mirantis.com >skype: gcon.monolake > > > > >__ >OpenStack Development Mailing List (not for usage questions) >Unsubscribe: >openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Fuel] vxlan support
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 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-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Andrey Danin ada...@mirantis.com skype: gcon.monolake __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Fuel] vxlan support
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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Fuel] vxlan support
Hi Samuel, VXLAN has critical status in Backlog for 7.0. We are going to include this segmentation type out of the box in 7.0. Meanwhile, you may create plugin for 6.1. Your help will be appreciated. I'll be glad to help you with plugins if you have any questions. -- Best regards, Sergii Golovatiuk, Skype #golserge IRC #holser On Tue, May 26, 2015 at 10:29 AM, Samuel Bartel wrote: > Hi folks, > > I have a question about implementation of vxlan for neutron. > there is a blueprint on that topic in launchpad from 2014/03/21: > https://blueprints.launchpad.net/fuel/+spec/neutron-vxlan-support > > several fixes have been pushed but all of them have been abandonned or > refused. > > Is there any technical reason to not having vxlan support on fuel or is it > just not a priority for product manager? > In fuel 5.0 and 5.1 we customize fuel in order to have this segmentation > type. > starting from fuel 6.0, I have made a plugin for vxlan but not totally > satisfied by that way to process. It will be cleaner to having vlxan > directly ship into fuel core. > So if there is no technical issue and if it not already shiped into the > advanced network topic, I can work on a fix to add this feature in fuel 7.0 > > regards > > Samuel > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Fuel] vxlan support
Hi folks, I have a question about implementation of vxlan for neutron. there is a blueprint on that topic in launchpad from 2014/03/21: https://blueprints.launchpad.net/fuel/+spec/neutron-vxlan-support several fixes have been pushed but all of them have been abandonned or refused. Is there any technical reason to not having vxlan support on fuel or is it just not a priority for product manager? In fuel 5.0 and 5.1 we customize fuel in order to have this segmentation type. starting from fuel 6.0, I have made a plugin for vxlan but not totally satisfied by that way to process. It will be cleaner to having vlxan directly ship into fuel core. So if there is no technical issue and if it not already shiped into the advanced network topic, I can work on a fix to add this feature in fuel 7.0 regards Samuel __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
