<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-1x.git/smoketest/scripts/cli/test_system_sflow.py, branch rolling</title>
<subtitle>VyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos/vyos-1x.git)
</subtitle>
<id>https://git.amelek.net/vyos/vyos-1x.git/atom?h=rolling</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-1x.git/atom?h=rolling'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/'/>
<updated>2025-10-21T19:03:16+00:00</updated>
<entry>
<title>T7948: always call setUp() and tearDown() base class methods</title>
<updated>2025-10-21T19:03:16+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2025-10-20T16:52:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=4995a58f998d3bdd055e49e919945bc0aa939be4'/>
<id>urn:sha1:4995a58f998d3bdd055e49e919945bc0aa939be4</id>
<content type='text'>
While working on task T7664 (FRR 10.4 upgrade), I identified the need for
additional validation and safeguards around the FRR management daemon. The
most appropriate place for this logic is in the setUp() and tearDown() methods
of the smoketest base class, VyOSUnitTestSHIM.

However, during implementation, it became apparent that test cases do not
consistently invoke the base class's setup and teardown methods. This
inconsistency complicates the process of capturing the FRR mgmtd PID at the
start of a test and verifying that it remains unchanged by the end - a key step
in detecting crashes or unexpected terminations (e.g., SIGSEGV) of the FRR
management daemon during tests.
</content>
</entry>
<entry>
<title>smoketest: T7858: make failfast main argument dynamic</title>
<updated>2025-09-30T15:19:06+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2025-09-22T18:49:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=2c521f1356378904e3d3a744960de68e8c5b62dc'/>
<id>urn:sha1:2c521f1356378904e3d3a744960de68e8c5b62dc</id>
<content type='text'>
When smoketest debugging is enabled (by creating the file
/tmp/vyos.smoketest.debug), all available smoketests will fail fast instead
of running to completion. This helps reduce test time when something is
broken or undergoing refactoring, as it avoids waiting for the full test suite
to finish.
</content>
</entry>
<entry>
<title>T7591: remove copyright years from source files</title>
<updated>2025-06-28T21:16:52+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2025-06-28T18:51:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=1478516ae437f19ebeb7d6ff9b83dd74f8e76758'/>
<id>urn:sha1:1478516ae437f19ebeb7d6ff9b83dd74f8e76758</id>
<content type='text'>
The legal team says years are not necessary so we can go ahead with it, since
it will simplify backporting.

Automatically removed using: git ls-files | grep -v libvyosconfig | xargs sed -i -E \
's/^# Copyright (19|20)[0-9]{2}(-[0-9]{4})? VyOS maintainers.*/# Copyright VyOS maintainers and contributors &lt;maintainers@vyos.io&gt;/g'

In addition we will error-out during "make" if someone re-adds a legacy
copyright notice
</content>
</entry>
<entry>
<title>T6895: Merge the hsflowd-based sFlow and uacctd-based sFlow (#4310)</title>
<updated>2025-01-21T09:19:27+00:00</updated>
<author>
<name>Nataliia S.</name>
<email>81954790+natali-rs1985@users.noreply.github.com</email>
</author>
<published>2025-01-21T09:19:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=832ed9122a0a602cadabe24457e9d64272a3d861'/>
<id>urn:sha1:832ed9122a0a602cadabe24457e9d64272a3d861</id>
<content type='text'>
</content>
</entry>
<entry>
<title>T6199: drop unused Python imports</title>
<updated>2024-04-02T22:15:43+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2024-04-02T22:15:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=274b2da242acd1f1f64ff1dee471e34295137c5f'/>
<id>urn:sha1:274b2da242acd1f1f64ff1dee471e34295137c5f</id>
<content type='text'>
found using "git ls-files *.py | xargs pylint | grep W0611"
</content>
</entry>
<entry>
<title>sflow: T5968: add VRF support</title>
<updated>2024-01-22T07:12:21+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2024-01-22T07:12:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=64473fa6f320375fb3d3de4de9e729f456ee5ae2'/>
<id>urn:sha1:64473fa6f320375fb3d3de4de9e729f456ee5ae2</id>
<content type='text'>
Add support to run hsflowd in a dedicated (e.g. management) VRF.

Command will be "set system sflow vrf &lt;name&gt;" like with any other service
</content>
</entry>
<entry>
<title>T5195: vyos.util -&gt; vyos.utils package refactoring (#2093)</title>
<updated>2023-07-14T20:18:36+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2023-07-14T20:18:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=d1ca536da448749dff557f13ecae97b124026e96'/>
<id>urn:sha1:d1ca536da448749dff557f13ecae97b124026e96</id>
<content type='text'>
* T5195: move run, cmd, call, rc_cmd helper to vyos.utils.process

* T5195: use read_file and write_file implementation from vyos.utils.file

Changed code automatically using:

find . -type f -not -path '*/\.*' -exec sed -i 's/^from vyos.util import read_file$/from vyos.utils.file import read_file/g' {} +
find . -type f -not -path '*/\.*' -exec sed -i 's/^from vyos.util import write_file$/from vyos.utils.file import write_file/g' {} +

* T5195: move chmod* helpers to vyos.utils.permission

* T5195: use colon_separated_to_dict from vyos.utils.dict

* T5195: move is_systemd_service_* to vyos.utils.process

* T5195: fix boot issues with missing imports

* T5195: move dict_search_* helpers to vyos.utils.dict

* T5195: move network helpers to vyos.utils.network

* T5195: move commit_* helpers to vyos.utils.commit

* T5195: move user I/O helpers to vyos.utils.io</content>
</entry>
<entry>
<title>T5125: Add op-mode for sFlow based on hsflowd</title>
<updated>2023-03-31T13:09:21+00:00</updated>
<author>
<name>Viacheslav Hletenko</name>
<email>v.gletenko@vyos.io</email>
</author>
<published>2023-03-31T13:09:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=657f5c1a08351c7740ff74cc112321d8f4e2155c'/>
<id>urn:sha1:657f5c1a08351c7740ff74cc112321d8f4e2155c</id>
<content type='text'>
Add op-mode for sFlow based on hsflowd "show sflow"
Add machine readable format '--raw' and formatted output
</content>
</entry>
<entry>
<title>T5086: Fix sflow fix default values for server</title>
<updated>2023-03-17T18:56:47+00:00</updated>
<author>
<name>Viacheslav Hletenko</name>
<email>v.gletenko@vyos.io</email>
</author>
<published>2023-03-17T18:56:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=9d3f88170fabd2211d51a56a642b388529ec385a'/>
<id>urn:sha1:9d3f88170fabd2211d51a56a642b388529ec385a</id>
<content type='text'>
We drop default values 'port' but don't set it again per server
Fix it
</content>
</entry>
<entry>
<title>T5086: Add sFlow drop-monitor-limit option</title>
<updated>2023-03-17T12:43:13+00:00</updated>
<author>
<name>Viacheslav Hletenko</name>
<email>v.gletenko@vyos.io</email>
</author>
<published>2023-03-17T12:38:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=57c06dcd78f9b711c4fb46e6657b0a496059a685'/>
<id>urn:sha1:57c06dcd78f9b711c4fb46e6657b0a496059a685</id>
<content type='text'>
hsflowd will export the headers of dropped packets (along with the
name of the function in the Linux kernel where that skb was dropped)
as part of the standard sFlow feed.
This measurement complements the sFlow packet sampling and
counter-telemetry well because it provides visibility into the
traffic that is not flowing.
Very helpful for troubleshooting.
The limit (a rate limit max of N drops per second sent out in the
sFlow datagrams) is the parameter you would set in the CLI.

set system sflow drop-monitor-limit 50
</content>
</entry>
</feed>
