On Fri, Apr 4, 2014 at 11:12 AM, Neil Schneider <[email protected]> wrote: > > > On Thu, April 3, 2014 5:27 pm, Gurucharan Shetty wrote: >> On Thu, Apr 3, 2014 at 5:11 PM, Neil Schneider <[email protected]> >> wrote: >>> I've been working with openvswitch with ovs-vsctl setting up bridges and >>> ports and everything works fine. I used the --no-wait option and I made >>> sure that all my configuration got written into the database, using >>> ovsdb-client dump and I see all the configurations in the database. >>> Everything I've read says it should persist through a reboot. It >>> doesn't. >>> >>> I must be missing some option, or there's a script that is stripping the >>> database on reboot. >>> >>> # cat /etc/redhat-release >>> CentOS release 6.5 (Final) >>> >>> ovs-vsctl -V >>> ovs-vsctl (Open vSwitch) 2.1.0 >>> Compiled Mar 25 2014 11:02:38 >>> >>> I built rpms and installed them. I prefer this method because it's >>> easier >>> to maintain. >> >> Are you using the redhat network scripts for openvswitch bridges as >> explained in the git repo's >> rhel/README.RHEL ? > > I went through all my configurations again, and made sure they were set up > properly. Set ONBOOT=yes and restarted networking. Everything seems to be > working properly, except DHCP doesn't work on boot. Not a major problem, I > just set it to static as it will be in production.
Okay. Just so that you know, you can get rid of those network scripts if you want to control everything using "ovs-vsctl" and expect to have your database remain as-is across boots. The disadvantage is that you cannot use those scripts to set your IP addresses every time during boot. DHCP should work fine, with proper configuration on a OVS bridge. If you understand shell scripts and interested in debugging your config, you can look at /etc/sysconfig/network-scripts/ifup-ovs > > Thanks for pointing me to the README. It forced me to revisit all the > config files, looking for errors. It looks like setting a vlan tag on the > interface connected to the network may block my connectivity, too. I think very recently a commit was made to 2.1 that lets you use DHCP on a vlan interface too (provided that vlan interface is a OVS internal interface) > > I'll continue to read the list to pick up more tips. > > Thanks for your help. > > > -- > Neil Schneider pacneil_at_linuxgeek_dot_net > > This is your life. Do what you love, and do it often. If you don't like > something, change it. If you don't like your job, quit. If you don't have > enough time, stop watching TV. If you are looking for the love of your > life, stop; they will be waiting for you when you start doing things you > love." > _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
