VyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos/vyos-1x.git) https://git.amelek.net/vyos/vyos-1x.git/atom?h=feature%2FT9082-codeql-cpp 2022-05-01T16:43:47+00:00 2022-05-01T16:43:47+00:00 Christian Poessinger christian@poessinger.com 2022-05-01T16:43:47+00:00 urn:sha1:e6af32344b1647f59543cbc659704bb9ef08be5f 2022-04-29T17:52:46+00:00 Christian Poessinger christian@poessinger.com 2022-04-29T17:52:46+00:00 urn:sha1:8ec6910fb8386a6c9a70aeef85f3b1fa3b7279d2 2022-04-25T18:30:26+00:00 Christian Poessinger christian@poessinger.com 2022-04-25T18:30:26+00:00 urn:sha1:85d6c8f7c62f7a52fbae5d0eaddd1f8803bd8014 When VyOS is booting and an interface is brought up (PPPoE) which requires a user callback script that is executed asynchronously when the interface is up we can not use Config(). The problem is, Config() is not available when the system starts and the initial commit is still processed. We need to move to ConfigTreeQuery() which was build for this exact same purpose. TO reduce side effects and also dependencies on the entire vyos.configdict library the set_level()/get_level() calls got eliminated from within the library. All calls to functions like: * get_removed_vlans() * is_node_changed() * leaf_node_changed() * is_mirror_intf() * ... Now require that the full config path to the node is passed. 2022-02-19T20:16:17+00:00 Viacheslav Hletenko v.gletenko@vyos.io 2022-02-19T18:06:27+00:00 urn:sha1:cf36ced75094a519682875e0e73571824f34b6ec Ability to attach host devices to the container It can be disk, USB device or any device from the directory /dev set container name alp01 device disk source '/dev/vdb1' set container name alp01 device disk destination '/dev/mydisk' 2022-01-11T03:23:20+00:00 Mathew Inkson 627767+imathew@users.noreply.github.com 2022-01-11T03:23:20+00:00 urn:sha1:142c976ca4b37fbae9ec44487d146b2a8319391c The bug was partially fixed with this commit: https://github.com/vyos/vyos-1x/commit/358f0b481d8620cad4954e3fe418054b9a8c3ecd The earlier commit introduced a startup retry (up to 10 times) to allow the OS to settle before the container is started. However, it only applies if host networking is NOT used. This change applies the same for containers where host networking is employed. Since the retry portion of the code (written in the earlier commit) is now referenced twice, it has been moved to its own function. 2021-11-25T19:58:06+00:00 Viacheslav v.gletenko@vyos.io 2021-11-25T19:58:06+00:00 urn:sha1:26af96f2d4c9212467a9ca98c0eddc50042ccbb3 2021-11-04T19:56:34+00:00 Christian Poessinger christian@poessinger.com 2021-11-04T19:56:34+00:00 urn:sha1:999398c6ba191a03e0c879953579326eb3be96ab 2021-11-04T19:41:30+00:00 Christian Poessinger christian@poessinger.com 2021-11-04T19:41:28+00:00 urn:sha1:358f0b481d8620cad4954e3fe418054b9a8c3ecd As it takes time for the OS to settle while booting up the first time a container is started after image upgrade it will fail big time. To prevent this we try to start the container up to 10 times before we generate a hard error. This makes error-free image upgrade possible again when using containers. 2021-11-04T15:52:33+00:00 Viacheslav v.gletenko@vyos.io 2021-11-04T15:52:33+00:00 urn:sha1:52f4a8571ad29b6b3afd3a73af243811496e8157 2021-10-15T18:18:39+00:00 Viacheslav v.gletenko@vyos.io 2021-10-15T18:18:39+00:00 urn:sha1:a633bdd2ed65971b2f137d5f985f8f3d85b9acfc