mir/ovs
2
0
Fork 0
mirror of https://github.com/openvswitch/ovs synced 2025-08-22 09:58:01 +00:00
Code Issues Releases Wiki Activity
ovs/rhel/usr_lib_systemd_system_openvswitch.service

18 lines
401 B
SYSTEMD
Raw Normal View History

build: Add support for building RPMs for Fedora Linux Add RPM specfiles for building OVS for Fedora Linux. This allows users of the upstream project the ability to generate RPMs for their Open vSwitch needs. Signed-off-by: Ralf Spenneberg <ralf@spenneberg.net> [kmestery@cisco.com made substantial changes including writing documentation] Signed-off-by: Kyle Mestery <kmestery@cisco.com> Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-10-02 14:31:55 -04:00
[Unit]
Description=Open vSwitch
rhel-systemd: Delay shutting down the services During testing it was found that systemd would consider the openvswitch service as a part of networking component, but the dependent services of ovs-vswitchd and ovsdb-server were not likewise considered. This leads to some strange race conditions, observed when using NFS over TCP, while shutting down systems. Fixes: 84ad12083491 ("rhel: Improved Systemd Integration") Co-authored-by: Flavio Leitner <fbl@redhat.com> Signed-off-by: Aaron Conole <aconole@redhat.com> Signed-off-by: Flavio Leitner <fbl@redhat.com> Signed-off-by: Russell Bryant <russell@ovn.org>
2016-10-07 13:36:45 -04:00
Before=network.target network.service
rhel: make openvswitch service start return when ready In OVS 2.6 openvswitch systemd service was changed to use BindsTo instead of Requires for sub-services but also removed them from After This made main openvswitch service return before sub-services were ready breaking scripts which assumed everything is ready after systemctl start e.g. in OpenStack CI infra [1] is calling ovs-vsctl immediately after service start exposing a race in virtualized CI environment: 2017-02-09T23:11:12.498Z|00007|bridge|INFO|ovs-vswitchd (Open vSwitch) 2.6.1 but ovs-ctl tried to access it few msec too early: 2017-02-09 23:11:12.352493 | ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory) Solution is to add ordering dependencies, BindsTo/Requires do not ensure it [2] [1] https://github.com/openstack-infra/devstack-gate/blob/c435a724bd257b22a2e39e8e9125c11302a8c81d/functions.sh#L1057-L1078 [2] https://www.freedesktop.org/software/systemd/man/systemd.unit.html#Requires= Fixes: 84ad120 ("rhel: Improved Systemd Integration") Signed-off-by: Alan Pevec <alan.pevec@redhat.com> Acked-by: Aaron Conole <aconole@redhat.com> Signed-off-by: Russell Bryant <russell@ovn.org>
2017-02-10 19:03:19 -05:00
After=network-pre.target ovsdb-server.service ovs-vswitchd.service
rhel: Improved Systemd Integration This commit builds upon some of the recent ovs-ctl changes to build a more integrated systemd setup. A new service (ovs-vswitchd) is added to track the ovs-vswitchd, and ovsdb-server service is reserved for the ovsdb-server daemon. The systemd scripts still use ovs-ctl to actually initialize the daemons. Signed-off-by: Aaron Conole <aconole@redhat.com> Acked-by: Markos Chandras <mchandras@suse.de> Acked-by: Flavio Leitner <fbl@redhat.com> Signed-off-by: Russell Bryant <russell@ovn.org>
2016-07-25 14:03:53 -04:00
PartOf=network.target
rhel-systemd: Restart openvswitch service if a daemon crashes Currently if either ovsdb-server or ovs-vswitchd is crashing the daemon is not restarting leaving the system in faulty state. This patch will detect the daemon crash and will restart the openvswitch service. Here is a (bit to wide) table showing the behavior before and after the patch. Note that only the Crash behavior has changed: Before patch: | Process Status | systemctl <> status | | ovs-vswitchd | ovsdb-server | openvswitch | ovs-vswitchd | ovsdb-server | +--------------+--------------+--------------+--------------+--------------+ systemctl start openvswitch* | started | started |active,exited |active,running|active,running| Crash vswitchd | crashed | stopped |inactive, dead|failed |inactive,dead | Crash ovsdb | stopped | crashed |inactive, dead|inactive,dead |failed | systemctl restart openvswitch | re-started | re-started |active,exited |active,running|active,running| systemctl restart ovs-vswitchd | re-started | re-started |active,exited |active,running|active,running| systemctl restart ovsdb-server | re-started | re-started |active,exited |active,running|active,running| systemctl stop openvswitch | stopped | stopped |inactive, dead|inactive,dead |inactive,dead | systemctl stop ovs-vswitchd | stopped | stopped |inactive, dead|inactive,dead |inactive,dead | systemctl stop ovsdb-server | stopped | stopped |inactive, dead|inactive,dead |inactive,dead | systemctl start ovs-vswitchd* | started | started |inactive, dead|active,running|active,running| systemctl start ovsdb-server* | not started | started |inactive, dead|inactive, dead|active,running| With patch: | Process Status | systemctk <> status | | ovs-vswitchd | ovsdb-server | openvswitch | ovs-vswitchd | ovsdb-server | +--------------+--------------+--------------+--------------+--------------+ systemctl start openvswitch* | started | started |active,exited |active,running|active,running| Crash vswitchd | crash,started| re-started |active,exited |active,running|active,running| Crash ovsdb | re-started | crash,started|active,exited |active,running|active,running| systemctl restart openvswitch | re-started | re-started |active,exited |active,running|active,running| systemctl restart ovs-vswitchd | re-started | re-started |active,exited |active,running|active,running| systemctl restart ovsdb-server | re-started | re-started |active,exited |active,running|active,running| systemctl stop openvswitch | stopped | stopped |inactive, dead|inactive,dead |inactive,dead | systemctl stop ovs-vswitchd | stopped | stopped |inactive, dead|inactive,dead |inactive,dead | systemctl stop ovsdb-server | stopped | stopped |inactive, dead|inactive,dead |inactive,dead | systemctl start ovs-vswitchd* | started | started |inactive, dead|active,running|active,running| systemctl start ovsdb-server* | not started | started |inactive, dead|inactive, dead|active,running| * These commands where executed when no ovs related processes where running. All other commands where executed when OVS was successfully running. Signed-off-by: Eelco Chaudron <echaudro@redhat.com> Acked-by: Markos Chandras <mchandras@suse.de> Acked-by: Aaron Conole <aconole@redhat.com> Acked-by: Flavio Leitner <fbl@sysclose.org> Signed-off-by: Russell Bryant <russell@ovn.org>
2017-02-27 15:56:41 -05:00
Requires=ovsdb-server.service
Requires=ovs-vswitchd.service
build: Add support for building RPMs for Fedora Linux Add RPM specfiles for building OVS for Fedora Linux. This allows users of the upstream project the ability to generate RPMs for their Open vSwitch needs. Signed-off-by: Ralf Spenneberg <ralf@spenneberg.net> [kmestery@cisco.com made substantial changes including writing documentation] Signed-off-by: Kyle Mestery <kmestery@cisco.com> Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-10-02 14:31:55 -04:00
[Service]
Type=oneshot
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
ExecStart=/bin/true
rhel: Add support for "systemctl reload openvswitch" The reload procedure will trigger a script that saves the flows and tlv maps (using ovs-save) then it restarts ovsdb-server, it stops ovs-vswitchd, it sets other_config:flow-restore-wait=true (to wait till flow restore is finished), it starts ovs-vswitchd, it restore the backupped flows/tlv maps and it removes other_config:flow-restore-wait=true (logic mostly ripped from ovs-ctl). It uses systemctl with --job-mode=ignore-dependencies to restart ovsdb-server and stop and start ovs-vswitchd in order to avoid systemd to restart the other components due to dependencies (as explained in rhel/README.RHEL.rst). Signed-off-by: Timothy Redaelli <tredaelli@redhat.com> Signed-off-by: Ben Pfaff <blp@ovn.org> Acked-by: Flavio Leitner <fbl@sysclose.org>
2017-11-03 21:39:17 +01:00
ExecReload=/usr/share/openvswitch/scripts/ovs-systemd-reload
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
ExecStop=/bin/true
build: Add support for building RPMs for Fedora Linux Add RPM specfiles for building OVS for Fedora Linux. This allows users of the upstream project the ability to generate RPMs for their Open vSwitch needs. Signed-off-by: Ralf Spenneberg <ralf@spenneberg.net> [kmestery@cisco.com made substantial changes including writing documentation] Signed-off-by: Kyle Mestery <kmestery@cisco.com> Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-10-02 14:31:55 -04:00
RemainAfterExit=yes
[Install]
WantedBy=multi-user.target
Reference in New Issue Copy Permalink