-
Notifications
You must be signed in to change notification settings - Fork 735
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Arista/show module #194
Arista/show module #194
Conversation
Value TYPE (\S+) | ||
Value MODEL (\S+) | ||
Value SERIAL_NUM (\S+) | ||
Value Fillup MAC_ADD (\S+\s+-\s+\S+) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we make this two different entries? It seems to me like sub-optimal data model'ing, e.g. trying to express two things in one field.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@itdependsnetworks , It is a range of mac-address for a card and should be single entry as per me
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let me enlist others, @jmcgill298 and @jedelman8 any thoughts? to me a single data field should represent a single piece of information.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would rather see MAC_START
and MAC_END
. It is easier to recompile data that is parsed with more granularity than to parse data that contains multiple pieces of information.
Start | ||
^Module\s+Ports.+ | ||
^-.+ | ||
^${MODULE}\s+${PORTS}\s+${CARD}\s+${TYPE}\s+${MODEL}\s+${SERIAL_NUM} -> Record |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I would rather see something like:"
Value CARD (.+)
^${MODULE}\s+${PORTS}\s+${CARD}\s+${TYPE}\s+${MODEL}\s+${SERIAL_NUM}$$ -> Record
Ensuring that there is port in there, is not likely to work for other modules.
ISSUE TYPE
COMPONENT
adding arista_eos_show_module.template
SUMMARY
adding arista_eos_show_module.template