Conversation
Refactor to use a dummy interface instead of wasting a dut. This not only simplifies the test but also increases test coverage on test rigs with a single DUT. Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
GitHub now publishes a sha256 checksum for each release asset, so the separately generated .sha256 files are redundant. Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
Not needed anymore. Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
Reorder the README so newcomers see the product before the philosophy: CLI demo and web UI up top, a "Try it in 5 minutes" section linking the GNS3 and build-from-source guides, then hardware and the rest. Tone down the remaining marketing prose in the hardware and use-case lists. Rename CODE-OF-CONDUCT.md to CODE_OF_CONDUCT.md so GitHub recognises it as the community code of conduct, and link the .github/ health files from the README. Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
The per-port PHY temperature sensors on Marvell DSA switches show up in 'show hardware' with the name the kernel derives from the full device tree path, e.g. cp0busbusf2000000mdio12a200switch2mdio01, which honestly is completely unreadable and also overruns the value column. Name each sensor after the front-panel port it serves (e1, e2, ...) by matching the PHY's device-tree phandle against each interface's phy-handle. Also: - show system: report a representative SoC temperature on CN913x by matching the ap-* and cp<N>-* thermal zones, hottest wins. - cli-pretty: truncate over-long sensor names so they can never spill into the value column again. Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
Previously at least one end of a veth pair had to remain in the host namespace, because that end created and destroyed the pair. Assigning both ends to containers left no one to create it. Select a deterministic primary end so exactly one side creates the pair. When the primary is itself a container interface, create the pair in the host namespace before the container starts; CNI host-device then moves each end into its container. Teardown is deferred to the container removal script so the pair does not linger and block re-creation. Drop the now-obsolete limitation notes from the documentation and YANG, and add a regression test connecting two containers over a veth pair. Fixes: #941 Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
show hardwareandshow systemon Marvell devicesThe new CLI output looks like this:
Checklist
Tick relevant boxes, this PR is-a or has-a: