[EOS] Add the OS architecture in facts#2317
Open
lodpp wants to merge 1 commit into
Open
Conversation
…oth 32 and 64 bits flavor. A given hardware might be capable to run both flavor. However some hw limitation might impose to use one of the other. Getting that information from fact can help in software lifecycle. Signed-off-by: Nicolas Piatto <nicolas.piatto@gandi.net>
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
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.
Hi,
Following the issue I created here, here is a PR to add the os architecture in the EOS fact list.
Since a while now, Arista is proposing their EOS in multiple flavors. I could see at least 3 flavors in the wild:
i686,x86_64andaarch64.My usecase was toward the EOS running on their hardware routers and switches. A given hardare may be able to run both the 32bits or 64bits ( i686 vs x86_64). The choice to use one or the other depends on hardware limitation and usage.
To help manage the software lifecycle, the OS version alone is not enough as it can run in both 32/64bits.
I want to use napalm to retrieve that data and update our source of truth, but also part of a compliance tool to validate/check drift between source of truth and the production.
This PR might might not be the best-in-class and I'm all ears on the community wisdom on how to make it better.
Here is a sample output running on 3 differents device type ( CCS-710P-16P, DCS-7280SR3K-48YC8-F and cEOS on macos arm64 (mac->linux vm->containerlab)
DCS-7280SR3K-48YC8-F running a x86_64 flavor
CCS-710P-16P running an i686 flavor
cEOS running an aarch64 flavor
Thanks for any input/ideas/tips you can give !
++
Nico