-
Notifications
You must be signed in to change notification settings - Fork 192
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
Add InfiniBand (IPoIB) support (LP: #1848471) #283
Conversation
e0e6113
to
e0aae0c
Compare
474aa2d
to
4fb1990
Compare
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 only have one holdout about this, which is the use of a generic string in the data model. However, since we already do it elsewhere you can disregard the comment entirely, I won't hold it against you ;-)
|
I'm not in a position to review this - I don't know C and don't have access to Infiniband |
V2: store ib_mode as enum type
4fb1990
to
6826cb1
Compare
Alright @sparkiegeek, I just wanted to keep you in the loop as this feature request originated from a MAAS context a while ago. We already got @schopin-pro's review (thanks for that!) and I adopted the remarks accordingly. Let's try to get the new |
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.
LGTM with the new changes :)
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.
As noted - am an interested end-customer but not qualified to review :)
ACK. We're waiting for schema review of the new |
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.
Proposed schema additions look ok, with one question inline (and a minor editorial fix requested).
| ethernets: | ||
| ib0: | ||
| match: | ||
| macaddress: "11:22:33:44:55:66:77:88:99:00:11:22:33:44:55:66:77:88:99:00" |
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.
Is this the preferred format for representing infiniband mac addresses? It doesn't seem very readable. It does seem to be the format that NM uses, but are there alternatives in common use that we should consider?
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.
Yes, I couldn't find any other common format for infiniband mac addresses. In general, "XX-XX-XX-XX-XX-XX" or "XXXXXXXXXXXX" are other common mac address formats, but those aren't any more readable if extended to 20 bytes.
It is also the format that has been proposed (and requested) at other places:
V2: fixup run-on sentence
V2: use ib_mode as enum type
6826cb1
to
e5cde84
Compare
Thanks, I've added the "schema ok" label. Fixed your documentation remark and commented on the MAC address format. This should be good for merging now, if no further remarks are added. |
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.
LGTM!
|
Merging. I think all comments have been addressed. If we'd want to support an additional format in the future, we can still add this as a follow-up. |
Description
InfiniBand (IPoIB) devices have a long-form HWADDR, as opposed to the 'normal' 6-byte ethernet HWADDR. When trying to use this HWADDR in a netplan config, it errors out expecting a 6-byte HWADDR. Example:
a0:00:02:20:fe:80:00:00:00:00:00:00:ec:0d:9a:03:00:15:e2:c1infiniband-mode: datagram|connectedto enable IB mode configuration.Example:
Checklist
make checksuccessfully.make check-coverage).