Fedora 20
sudo yum -y install openvswitch python-openvswitch
sudo service openvswitch stop
sudo ovsdb-tool create /etc/openvswitch/conf.db /usr/share/openvswitch/vswitch.ovsschema
sudo ovsdb-tool create /etc/openvswitch/vtep.db /usr/share/openvswitch/vtep.ovsschema
sudo mkdir -p /var/run/openvswitch
sudo mkdir -p /var/log/openvswitch
sudo ovsdb-server --pidfile --log-file --detach \
--remote=punix:/var/run/openvswitch/db.sock \
--remote=ptcp:6640 \
/etc/openvswitch/conf.db /etc/openvswitch/vtep.db
sudo ovs-vswitchd --log-file --detach \
--pidfile unix:/var/run/openvswitch/db.sock
udo ovs-vsctl add-br br0
sudo ovs-vsctl add-port br0 eth0
sudo vtep-ctl add-ps br0
sudo vtep-ctl add-port br0 eth0
sudo vtep-ctl set Physical_Switch br0 tunnel_ips=192.168.0.3
sudo /usr/share/openvswitch/scripts/ovs-vtep \
--log-file=/var/log/openvswitch/ovs-vtep.log \
--pidfile=/var/run/openvswitch/ovs-vtep.pid --detach br0
sudo vtep-ctl set-manager ptcp:6640
sudo ovsdb-client dump hardware_vtep
sudo vtep-ctl list-ps
sudo vtep-ctl list-ports br0
Run the IT
02:27:13.398 [main] TRACE o.o.o.l.j.JsonRpcEndpoint - {"id":"b734b0f4-dd2e-4aaf-bc14-1fb2dd7c3fcd","method":"list_dbs","params":[]}
02:27:13.431 [nioEventLoopGroup-2-1] TRACE o.o.o.l.j.JsonRpcEndpoint - Response : {"id":"b734b0f4-dd2e-4aaf-bc14-1fb2dd7c3fcd","result":["hardware_vtep","Open_vSwitch"],"error":null}
Hey buddy, fixed a few typos and added the mvn command.
https://gist.github.com/Mierdin/0c42b5fd06b545a8d791
Just out of curiosity, this is far simpler than getting the docker stuff set up, but obviously less flexible from an OVS version perspective. Would you recommend I get that working, now that hardware vtep is included?