matthew/sonic-buildimage
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity
cf33a50c57
sonic-buildimage/files/build_templates/sflow.service.j2

21 lines
481 B
Plaintext
Raw Normal View History

[sflow]: Build infrastructure changes to support sflow docker and utilities (#3251) Introduce a new "sflow" container (if ENABLE_SFLOW is set). The new docker will include: hsflowd : host-sflow based daemon is the sFlow agent psample : Built from libpsample repository. Useful in debugging sampled packets/groups. sflowtool : Locally dump sflow samples (e.g. with a in-unit collector) In case of SONiC-VS, enable psample & act_sample kernel modules. VS' syncd needs iproute2=4.20.0-2~bpo9+1 & libcap2-bin=1:2.25-1 to support tc-sample tc-syncd is provided as a convenience tool for debugging (e.g. tc-syncd filter show ...)
2019-09-14 22:27:09 -05:00
[Unit]
Description=sFlow container
[services] sflow service sets swss service as Requisite=, not Requires= (#3819) The sflow service should not start unless the swss service is started. However, if this service is not started, the sflow service should not attempt to start them, instead it should simply fail to start. Using Requisite=, we will achieve this behavior, whereas using Requires= will cause the required service to be started.
2019-12-03 11:50:49 -06:00
Requisite=swss.service
[sflow] Fix race-condition seen with mVRF configured (#6102) Under certain conditions, the sFlow service can start before interface configurations are sucessfully applied. This will cause hsflowd to get a socket error. This fix ensures all interface configurations are successfully applied before the sFlow service (hsflowd) starts. During testing we saw this error from hsflowd if interface configs were not successfully applied before hsflowd started. ERR sflow#hsflowd: socket sendto error: Network is unreachable no FLOW samples can be seen. This can be consistently reproducible if you force sFlow service to start before interface-config.service. Signed-off-by: Garrick He <garrick_he@dell.com>
2020-12-03 03:33:10 -06:00
After=swss.service syncd.service hostcfgd.service
[services] introduce sonic.target (#5705) - Why I did it Group all SONiC services together and able to manage them together. Will be used in config reload command as much simpler and generic way to restart services. - How I did it Add services to sonic.target - How to verify it Together with Azure/sonic-utilities#1199 config reload -y Signed-off-by: Stepan Blyshchak <stepanb@nvidia.com>
2021-02-25 06:26:24 -06:00
BindsTo=sonic.target
After=sonic.target
[sflow]: Build infrastructure changes to support sflow docker and utilities (#3251) Introduce a new "sflow" container (if ENABLE_SFLOW is set). The new docker will include: hsflowd : host-sflow based daemon is the sFlow agent psample : Built from libpsample repository. Useful in debugging sampled packets/groups. sflowtool : Locally dump sflow samples (e.g. with a in-unit collector) In case of SONiC-VS, enable psample & act_sample kernel modules. VS' syncd needs iproute2=4.20.0-2~bpo9+1 & libcap2-bin=1:2.25-1 to support tc-sample tc-syncd is provided as a convenience tool for debugging (e.g. tc-syncd filter show ...)
2019-09-14 22:27:09 -05:00
Before=ntp-config.service
[Services] Restart Sflow service upon unexpected critical process exit. (#3751) Signed-off-by: Yong Zhao <yozhao@microsoft.com>
2019-11-25 15:02:00 -06:00
StartLimitIntervalSec=1200
StartLimitBurst=3
[sflow]: Build infrastructure changes to support sflow docker and utilities (#3251) Introduce a new "sflow" container (if ENABLE_SFLOW is set). The new docker will include: hsflowd : host-sflow based daemon is the sFlow agent psample : Built from libpsample repository. Useful in debugging sampled packets/groups. sflowtool : Locally dump sflow samples (e.g. with a in-unit collector) In case of SONiC-VS, enable psample & act_sample kernel modules. VS' syncd needs iproute2=4.20.0-2~bpo9+1 & libcap2-bin=1:2.25-1 to support tc-sample tc-syncd is provided as a convenience tool for debugging (e.g. tc-syncd filter show ...)
2019-09-14 22:27:09 -05:00
[Service]
User={{ sonicadmin_user }}
ExecStartPre=/usr/bin/{{docker_container_name}}.sh start
ExecStart=/usr/bin/{{docker_container_name}}.sh wait
ExecStop=/usr/bin/{{docker_container_name}}.sh stop
[Services] Restart Sflow service upon unexpected critical process exit. (#3751) Signed-off-by: Yong Zhao <yozhao@microsoft.com>
2019-11-25 15:02:00 -06:00
Restart=always
RestartSec=30
[sflow]: Build infrastructure changes to support sflow docker and utilities (#3251) Introduce a new "sflow" container (if ENABLE_SFLOW is set). The new docker will include: hsflowd : host-sflow based daemon is the sFlow agent psample : Built from libpsample repository. Useful in debugging sampled packets/groups. sflowtool : Locally dump sflow samples (e.g. with a in-unit collector) In case of SONiC-VS, enable psample & act_sample kernel modules. VS' syncd needs iproute2=4.20.0-2~bpo9+1 & libcap2-bin=1:2.25-1 to support tc-sample tc-syncd is provided as a convenience tool for debugging (e.g. tc-syncd filter show ...)
2019-09-14 22:27:09 -05:00
[Install]
[services] introduce sonic.target (#5705) - Why I did it Group all SONiC services together and able to manage them together. Will be used in config reload command as much simpler and generic way to restart services. - How I did it Add services to sonic.target - How to verify it Together with Azure/sonic-utilities#1199 config reload -y Signed-off-by: Stepan Blyshchak <stepanb@nvidia.com>
2021-02-25 06:26:24 -06:00
WantedBy=sonic.target
Reference in New Issue Copy Permalink