I`m back after a long break and will follow up on this feature.
Here is a summary of things that have happened since the last update:
1. In my absence, the feature testing got broken as a result of migrating from the `mininet` to the `munet` framework From debugging, I have identified a root cause to be - bpf fs was not inherited by the `munet` router. The solution is to hop into the router mount namespace for the test run.
Because there is a long-running development for operation data retrieval, we can postpone this ticket until an effort is finished.
Then, I can open a feature request or visit the yang meeting and start a discussion about the data pagination functionality.
Currently, my idea is to simulate pagination at the fs level by having a split of requested JSON.
This solution involves:
vtysh -c "show yang operational-data /frr-vrf:lib/vrf[name='default']/frr-zebra:zebra/ribs zebra" > big.json
jq -c '."frr-vrf:lib" .vrf[0] ."frr-zebra:zebra" .ribs .rib[0] .route[]' big.json | split -l 100 -d
Now, UI can display 1 of the resulting files at a time. These files may be regenerated on page refresh.
Such a solution will utilize extra disk space, although it can be avoided by using pipes and other
streaming utilities like awk/sed
PR for Sagitta: https://github.com/vyos/vyos-1x/pull/2478
PR for Sagitta: https://github.com/vyos/vyos-1x/pull/2478
PR for Sagitta: https://github.com/vyos/vyos-1x/pull/2478
I'll hava a lab with PIM SSM and BFD , I'll update our documentation with those feature with example.
Will be tracked via PR https://github.com/vyos/vyos-1x/pull/2476 as it's realted to the ongoing PIM/PIM6 CLI extension
In T5167#164447, @JeffWDH wrote:What about using nginx which seems to be already leveraged by the web API?
I would vote for that (using nginx as backend since it already exists).
What about using nginx which seems to be already leveraged by the web API?
PR for VyOS 1.5 https://github.com/vyos/vyos-1x/pull/2476
Instead of "file-server" I think "http-server" would be a better name or even "web-server" in this context.
Will be implemented via T5733
This also implements https://github.com/vyos/vyos-1x/pull/2411
That is my first PR; please, let me know if you need something else.
@twan it was backported https://github.com/vyos/vyos-1x/pull/2400
Will this feature be backported to 1.4?
Here is another candidate, although msmtp still looks like a better choice:
https://wiki.debian.org/nullmailer
@indrajitr could you recheck smoketests?
DEBUG - ---------------------------------------------------------------------- DEBUG - Ran 3 tests in 7.616s DEBUG - DEBUG - OK DEBUG - Running Testcase: /usr/libexec/vyos/tests/smoke/cli/test_service_dns_dynamic.py DEBUG - test_01_dyndns_service_standard (__main__.TestServiceDDNS.test_01_dyndns_service_standard) ... ok DEBUG - test_02_dyndns_service_ipv6 (__main__.TestServiceDDNS.test_02_dyndns_service_ipv6) ... ok DEBUG - test_03_dyndns_service_dual_stack (__main__.TestServiceDDNS.test_03_dyndns_service_dual_stack) ... ok DEBUG - test_04_dyndns_rfc2136 (__main__.TestServiceDDNS.test_04_dyndns_rfc2136) ... ok DEBUG - test_05_dyndns_hostname (__main__.TestServiceDDNS.test_05_dyndns_hostname) ... ok DEBUG - test_06_dyndns_web_options (__main__.TestServiceDDNS.test_06_dyndns_web_options) ... ok DEBUG - test_07_dyndns_vrf (__main__.TestServiceDDNS.test_07_dyndns_vrf) ... ERROR DEBUG - test_07_dyndns_vrf (__main__.TestServiceDDNS.test_07_dyndns_vrf) ... FAIL DEBUG - DEBUG - ====================================================================== DEBUG - ERROR: test_07_dyndns_vrf (__main__.TestServiceDDNS.test_07_dyndns_vrf) DEBUG - ---------------------------------------------------------------------- DEBUG - Traceback (most recent call last): DEBUG - File "/usr/libexec/vyos/tests/smoke/cli/test_service_dns_dynamic.py", line 304, in test_07_dyndns_vrf DEBUG - self.cli_set(['vrf', 'name', vrf_name, 'table', vrf_table]) DEBUG - File "/usr/libexec/vyos/tests/smoke/cli/base_vyostest_shim.py", line 68, in cli_set DEBUG - self._session.set(config) DEBUG - File "/usr/lib/python3/dist-packages/vyos/configsession.py", line 150, in set DEBUG - self.__run_command([SET] + path + value) DEBUG - File "/usr/lib/python3/dist-packages/vyos/configsession.py", line 139, in __run_command DEBUG - raise ConfigSessionError(output) DEBUG - vyos.configsession.ConfigSessionError: Number is not in any of allowed ranges DEBUG - DEBUG - DEBUG - DEBUG - VRF routing table must be in range from 100 to 65535 DEBUG - Value validation failed DEBUG - Set failed DEBUG - DEBUG - DEBUG - ====================================================================== DEBUG - FAIL: test_07_dyndns_vrf (__main__.TestServiceDDNS.test_07_dyndns_vrf) DEBUG - ---------------------------------------------------------------------- DEBUG - Traceback (most recent call last): DEBUG - File "/usr/libexec/vyos/tests/smoke/cli/test_service_dns_dynamic.py", line 50, in tearDown DEBUG - self.assertTrue(process_running(DDCLIENT_PID)) DEBUG - AssertionError: False is not true DEBUG - DEBUG - ----------------------------------------------------------------------
Yes I mean sudo ip vrf exec FOO /usr/sbin/conntrackd -C /run/conntrackd/conntrackd.conf
It has been a while since I had setup the HA VRF. I attached the interfaces on both routers to use this VRF but then conntrack-sync wasn't woking anymore. Do you mean if I had also tried to manually start the service and configure it to use this VRF?
PR https://github.com/vyos/vyos-1x/pull/2469
set service file-server listen-address 0.0.0.0 set service file-server port 8000 set service file-server directory '/tmp'