mirror of
https://github.com/openvswitch/ovs
synced 2025-08-22 09:58:01 +00:00
b49c106ef0
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>
14 lines
257 B
Desktop File
14 lines
257 B
Desktop File
[Unit]
|
|
Description=Open vSwitch
|
|
After=syslog.target network.target openvswitch-nonetwork.service
|
|
Requires=openvswitch-nonetwork.service
|
|
|
|
[Service]
|
|
Type=oneshot
|
|
ExecStart=/bin/true
|
|
ExecStop=/bin/true
|
|
RemainAfterExit=yes
|
|
|
|
[Install]
|
|
WantedBy=multi-user.target
|