3cb0aad164
In case of configuration changes it's better to reload FRR rather then perform restart. Actions towards FRR lead to networking downtime until connection is established and required routes reconciled. To reduce the downtime let's reload FRR in case of simple config changes Change-Id: I83746f3a101dc0f678a4a82d02160fc1fa8d8e52
34 lines
941 B
YAML
34 lines
941 B
YAML
---
|
|
# Copyright 2020, VEXXHOST, Inc.
|
|
#
|
|
# Licensed under the Apache License, Version 2.0 (the "License");
|
|
# you may not use this file except in compliance with the License.
|
|
# You may obtain a copy of the License at
|
|
#
|
|
# http://www.apache.org/licenses/LICENSE-2.0
|
|
#
|
|
# Unless required by applicable law or agreed to in writing, software
|
|
# distributed under the License is distributed on an "AS IS" BASIS,
|
|
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
# See the License for the specific language governing permissions and
|
|
# limitations under the License.
|
|
|
|
- name: Restart frr
|
|
become: true
|
|
become_user: root
|
|
service:
|
|
name: frr
|
|
state: restarted
|
|
enabled: true
|
|
register: frr_restart
|
|
|
|
- name: Reload frr
|
|
become: true
|
|
become_user: root
|
|
service:
|
|
name: frr
|
|
state: reloaded
|
|
enabled: true
|
|
when:
|
|
- frr_restart is not defined or (frr_restart is defined and frr_restart is skipped)
|