Hi Jeremy, Yep, I saw it. Unfortunately, because Fuel deployment scenarios is about setting up OVS too, it could be kinda freaky to provide overlay networking for OVS on OVS. That's why I was looking on other L2 overlays (kernel space mcast vxlan was in scope too).
But yes, we still can use this method (with l23network or multinode scripts for some cases). -- With best regards, Vladimir Eremin, Fuel Deployment Engineer, Mirantis, Inc. > On May 10, 2016, at 5:39 PM, Jeremy Stanley <[email protected]> wrote: > > On 2016-05-10 15:54:34 +0300 (+0300), Vladimir Eremin wrote: > [...] >> 1. Automate overlay networking setup. I've used >> https://www.tinc-vpn.org/ <https://www.tinc-vpn.org/> as a L2 >> switching overlay, but OpenVPN could be tool of choice. Action >> items: >> - overlay networking setup should be integrated in fuel-devops > [...] > > Just to be sure, you've seen the ovs_vxlan_bridge() implementation > in devstack-gate where we set up an overlay L2 network using > OVS/VXLAN? The same design also works fine with GRE (we used it for > a while but ran into some service providers blocking IP protocol 47 > on their LANs). > > http://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/multinode_setup_info.txt > http://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/functions.sh#n1050 > -- > Jeremy Stanley > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
