mir/ovs
2
0
Fork 0
mirror of https://github.com/openvswitch/ovs synced 2025-08-23 02:17:42 +00:00
Code Issues Releases Wiki Activity
ovs/rhel/usr_share_openvswitch_scripts_systemd_sysconfig.template

35 lines
1.1 KiB
Plaintext
Raw Permalink Normal View History

fedora package: fix systemd ordering and deps. There is a chicken and egg issue where common OVS configuration uses a controller which is only accessible via the network. So starting OVS before network.target would break those configurations. However, the network doesn't come up after boot because OVS isn't started until after the network scripts tries to configure the ovs. This is partially fixed by commits: commit: 602453000e28ec1076c0482ce13c284765a84409 rhel: Automatically start openvswitch service before bringing an ovs interfa commit: 3214851c31538e8690e31f95702f8927a8c0838b rhel: Add OVSREQUIRES to automatically bring up OpenFlow interface dependencies But still there is the dependency issue between network.target and openvswitch which this patch fixes it. It provides two systemd service units. One to run at any time (openvswitch-nonetwork.service) which runs 'ovs-ctl start' and the other one (openvswith.service) to run after network.target which works as a frontend to the admin. The openvswitch-nonetwork.service is used internally by the 'ifup-ovs/ifdown-ovs' scripts when adding or removing ports to the bridge or when the openvswitch.service is enabled by the admin. Signed-off-by: Flavio Leitner <fbl@redhat.com> Signed-off-by: Gurucharan Shetty <gshetty@nicira.com>
2014-01-09 01:04:33 -02:00
### Configuration options for openvswitch
#
rhel: Specify that force-corefiles is enabled by default Currently in /etc/sysconfig/openvswitch it's not clear that force-corefiles is enabled by default. This patch adds a comment explaining that force-corefiles is, by default, set to yes. Signed-off-by: Timothy Redaelli <tredaelli@redhat.com> Signed-off-by: Ben Pfaff <blp@ovn.org>
2018-05-11 19:13:10 +02:00
# Enable core files.
# This option should be set to "yes" or "no". The default is "yes".
fedora package: fix systemd ordering and deps. There is a chicken and egg issue where common OVS configuration uses a controller which is only accessible via the network. So starting OVS before network.target would break those configurations. However, the network doesn't come up after boot because OVS isn't started until after the network scripts tries to configure the ovs. This is partially fixed by commits: commit: 602453000e28ec1076c0482ce13c284765a84409 rhel: Automatically start openvswitch service before bringing an ovs interfa commit: 3214851c31538e8690e31f95702f8927a8c0838b rhel: Add OVSREQUIRES to automatically bring up OpenFlow interface dependencies But still there is the dependency issue between network.target and openvswitch which this patch fixes it. It provides two systemd service units. One to run at any time (openvswitch-nonetwork.service) which runs 'ovs-ctl start' and the other one (openvswith.service) to run after network.target which works as a frontend to the admin. The openvswitch-nonetwork.service is used internally by the 'ifup-ovs/ifdown-ovs' scripts when adding or removing ports to the bridge or when the openvswitch.service is enabled by the admin. Signed-off-by: Flavio Leitner <fbl@redhat.com> Signed-off-by: Gurucharan Shetty <gshetty@nicira.com>
2014-01-09 01:04:33 -02:00
# --force-corefiles=yes
#
# Set "nice" priority at which to run ovsdb-server:
# --ovsdb-server-priority=-10
#
# Set "nice" priority at which to run ovsdb-vswitchd:
# --ovs-vswitchd-priority=-10
#
# Pass or not --mlockall option to ovs-vswitchd.
# This option should be set to "yes" or "no". The default is "yes".
# Enabling this option can avoid networking interruptions due to
# system memory pressure in extraordinary situations, such as multiple
# concurrent VM import operations.
# --mlockall=yes
#
# Use valgrind:
# --ovs-vswitchd-wrapper=valgrind
# --ovsdb-server-wrapper=valgrind
#
rhel: Add an example to specify custom options Add an example to specify custom options of ovs-vswitchd and ovsdb-server. In the example, the log level for file and console destinations is set to dbg. Signed-off-by: Timothy Redaelli <tredaelli@redhat.com> Signed-off-by: Ben Pfaff <blp@ovn.org>
2019-02-11 19:55:53 +01:00
# Specify additional options, for example to start with debug logs:
# --ovs-vswitchd-options='-vconsole:dbg -vfile:dbg'
# --ovsdb-server-options='-vconsole:dbg -vfile:dbg'
#
ovs-ctl: Fix inability to set custom options for ovs-monitor-ipsec. Commit in the fixes tag added support for using custom ipsec.conf with ovs-monitor-ipsec, but it didn't provide a way to use those options via ovs-ctl. This makes it not possible to use these options from a systemd unit, for example. Fix that by adding --ovs-monitor-ipsec-options knob to ovs-ctl and allowing OPTIONS to be passed via sysconfig. Our Debian units are using StrongSwan, so they do not need these Libreswan-specific options, however, it's better to keep systemd integration similar to Fedora/RHEL. There is at least one other option that can be used with StrongSwan. Only the Debian init file is updated, because we don't have IPsec support for init in Fedora/RHEL. There is a line length warning in the example, but it's hard to split it into multiple lines, and I think, it's a good configuration example to provide. Fixes: 09d7c5ac0054 ("ipsec: Add support for using non-root ipsec.conf.") Acked-by: Frode Nordahl <fnordahl@ubuntu.com> Signed-off-by: Ilya Maximets <i.maximets@ovn.org>
2025-01-15 15:00:15 +01:00
# Or to start with non-root IPsec config file:
# --ovs-monitor-ipsec-options='--ipsec-conf=/etc/ipsec.d/ovs.conf --root-ipsec-conf=/etc/ipsec.conf'
#
fedora package: fix systemd ordering and deps. There is a chicken and egg issue where common OVS configuration uses a controller which is only accessible via the network. So starting OVS before network.target would break those configurations. However, the network doesn't come up after boot because OVS isn't started until after the network scripts tries to configure the ovs. This is partially fixed by commits: commit: 602453000e28ec1076c0482ce13c284765a84409 rhel: Automatically start openvswitch service before bringing an ovs interfa commit: 3214851c31538e8690e31f95702f8927a8c0838b rhel: Add OVSREQUIRES to automatically bring up OpenFlow interface dependencies But still there is the dependency issue between network.target and openvswitch which this patch fixes it. It provides two systemd service units. One to run at any time (openvswitch-nonetwork.service) which runs 'ovs-ctl start' and the other one (openvswith.service) to run after network.target which works as a frontend to the admin. The openvswitch-nonetwork.service is used internally by the 'ifup-ovs/ifdown-ovs' scripts when adding or removing ports to the bridge or when the openvswitch.service is enabled by the admin. Signed-off-by: Flavio Leitner <fbl@redhat.com> Signed-off-by: Gurucharan Shetty <gshetty@nicira.com>
2014-01-09 01:04:33 -02:00
OPTIONS=""
redhat: allow arbitrary user:group Under rpm based distributions, the only user:group that the rhel daemons run as is 'root:root'. This is fine as a default, but as part of a security procedure, users may want to run as an alternate uid/gid. This commit adds an OVS_USER_ID environment variable for systemd, which defaults to root:root, but can be overridden by changing the /etc/sysconfig/openvswitch environment file. Acked-by: Markos Chandras <mchandras@suse.de> Signed-off-by: Aaron Conole <aconole@redhat.com> Signed-off-by: Russell Bryant <russell@ovn.org>
2017-08-04 13:00:53 -04:00
# Uncomment and set the OVS User/Group value
#OVS_USER_ID="openvswitch:openvswitch"
Reference in New Issue Copy Permalink