Add arista_eos_ssh driver for Arista EOS over SSH - #419
Open
jvanderaa wants to merge 3 commits into
Open
Conversation
jvanderaa
requested review from
jeffkala,
pke11y and
pszulczewski
as code owners
August 11, 2026 01:58
jvanderaa
force-pushed
the
feature/arista-eos-ssh
branch
from
August 11, 2026 01:59
144d1ce to
a27d80c
Compare
Adds EOSSSHDevice for environments where eAPI is not enabled. It subclasses EOSDevice and overrides only the transport surface (__init__, open, close, show, config, reboot, vlans) plus a native_ssh alias, so the fact properties, boot-option handling, install_os and the whole file-transfer family are inherited unchanged. Structured data comes from the CLI's '| json' pipe, which renders the same document eAPI returns; the pipe is a CLI feature and does not require 'management api http-commands'. The pipe is gated on '^show' because EOSDevice routes five EXEC/config commands through show(raw_text=False), and per-command read timeouts are resolved from the command text so show()'s signature stays identical to EOSDevice.show(). Validated against a DCS-7050TX-64-R running EOS 4.28.5M; the unit fixtures are that capture, sanitised. Public API parity with EOSDevice is enforced by test rather than by convention, and a further test feeds both drivers the same document and requires identical facts.
jvanderaa
force-pushed
the
feature/arista-eos-ssh
branch
from
August 11, 2026 12:29
a27d80c to
5190325
Compare
Contributor
|
Ran some additional manual testing on real hardware as well.
|
Contributor
|
@jvanderaa - Does this need to be supported by os upgrades? |
jtdub
approved these changes
Aug 11, 2026
jtdub
left a comment
jtdub
left a comment
Contributor
There was a problem hiding this comment.
LGTM! I ran the integration tests against the device in the lab.
I'm in the process of creating a Jira issue to wrap up anything else that would allow us to use this driver in OS Upgrades.
Contributor
yes |
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
3 participants
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.
Adds EOSSSHDevice for environments where eAPI is not enabled. It subclasses EOSDevice and overrides only the transport surface (init, open, close, show, config, reboot, vlans) plus a native_ssh alias, so the fact properties, boot-option handling, install_os and the whole file-transfer family are inherited unchanged.
Structured data comes from the CLI's '| json' pipe, which renders the same document eAPI returns; the pipe is a CLI feature and does not require 'management api http-commands'. The pipe is gated on '^show' because EOSDevice routes five EXEC/config commands through show(raw_text=False), and per-command read timeouts are resolved from the command text so show()'s signature stays identical to EOSDevice.show().
Validated against a DCS-7050TX-64-R running EOS 4.28.5M; the unit fixtures are that capture, sanitised. Public API parity with EOSDevice is enforced by test rather than by convention, and a further test feeds both drivers the same document and requires identical facts.