packages/net/openvswitch/files/openvswitch.config

config ovs ovs
	option disabled 1

config ovn_northd north
	option disabled 1

config ovn_controller controller
	option disabled 1

config ovs_bridge
	option disabled 1
	option name 'my-bridge'
	option controller 'tcp:192.168.0.1'
	option datapath_id ''

config ovs_port
	option disabled 1
	option bridge 'my-bridge'
	option port 'ovs-port1'
	option ofport '1'
	option tag '123'
	option type 'internal'
openvswitch: rework packaging New scheme mainly provides three packages: openvswitch, openvswitch-ovn-north, openvswitch-ovn-controller. These should fit most usage scenarios. Other subpackages like openvswitch-libXXX etc. are there for dependency management and are hidden from the menu. Many python and shell scripts are removed in this revision. Most of them cannot run out of box at all for lack of dependencies. Others being legacy ones are not that useful now. Add them back at later time when real need appears Below are a simple listing of additions - initscript now incorporate also ovn north and controller support - ovn-ctl and ovs-ctl can be invoked directly from within $PATH Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com> 2018-05-28 10:21:38 +00:00			`config ovs ovs`
			`option disabled 1`

			`config ovn_northd north`
			`option disabled 1`

			`config ovn_controller controller`
			`option disabled 1`
openvswitch: adds new UCI section ovs_bridge This new config section in package openvswitch supports creating a named bridge, and setting its' OpenFlow controller end-point. An example config is included in /rom/etc/config/openvswitch Signed-off-by: Simon Kinane <skinane@fb.com> 2020-07-26 19:58:53 +00:00
			`config ovs_bridge`
			`option disabled 1`
			`option name 'my-bridge'`
openvswitch: allow complex port configurations The current way to add ports to an Open vSwitch bridge does not allow complex port configurations. Use a dedicated uci config section per port instead of the current port:type syntax. This way we can easily support more features like setting the VLAN tag or the OpenFlow port number. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be> 2021-07-20 14:07:52 +00:00			`option controller 'tcp:192.168.0.1'`
openvswitch: support setting OpenFlow datapath ID By default, Open vSwitch will generate the OpenFlow datapath ID of a bridge based on the MAC address of one of its ports. Due to this, it's possible that the datapath ID changes when new ports are added. When the datapath ID changes, Open vSwitch disconnects from the controller, as there is no way to notify the controller that the datapath ID has changed. Add an option to set the datapath ID so that the above situation can be avoided. The option takes either exactly 16 hex characters, or when prefixed with 0x, between 1 and 16 hex characters. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be> 2021-07-26 16:04:19 +00:00			`option datapath_id ''`
openvswitch: allow complex port configurations The current way to add ports to an Open vSwitch bridge does not allow complex port configurations. Use a dedicated uci config section per port instead of the current port:type syntax. This way we can easily support more features like setting the VLAN tag or the OpenFlow port number. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be> 2021-07-20 14:07:52 +00:00
			`config ovs_port`
			`option disabled 1`
			`option bridge 'my-bridge'`
			`option port 'ovs-port1'`
			`option ofport '1'`
			`option tag '123'`
			`option type 'internal'`