-
Notifications
You must be signed in to change notification settings - Fork 7
Extend NetworkInterface status with LLDP neighbor information
#492
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
Conversation
5dd20f9 to
a61fd4d
Compare
|
From our discussion: This PR should take information from the registry, provided by #452 and update the Example: |
a61fd4d to
bcc6740
Compare
bcc6740 to
89be777
Compare
nagadeesh-nagaraja
left a comment
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.
#452 is still part of this PR, I though the plan was to merge it separately?
|
@xkonni can you please rebase this PR? |
NetworkInterface status with LLDP neighbor information
89be777 to
be35045
Compare
71b76be to
4436472
Compare
4436472 to
b47555e
Compare
b47555e to
422d470
Compare
422d470 to
06a9b9c
Compare
|
rebased, updated with our discussed changes and more robust lldpctl output parsing. |
- add fields to registry - handle new registry fields and update crd
06a9b9c to
1a1b513
Compare
7cef02e to
1a91410
Compare
Proposed Changes
This PR allows the metal-api to hold more information about the server. It is based on #452 and the first commit is actually from that PR, as it was not yet merged.
metalprobe(inventory) #452