Bug 1964540: Extend trunk configuration to port level in machineset#185
Conversation
|
As it currently stands, this patch brings us up to par with kubernetes-sigs/cluster-api-provider-openstack functionality: This make a deployment using kuryr but with SR-IOV ports not trunked impossible. |
|
/retest |
|
This functionality is being addressed upstream in pr kubernetes-sigs#934. |
da7e047 to
6455359
Compare
|
Looks good to me, but I'll leave the |
|
/uncc Fedosin |
|
/approve (just to be explicit) |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: adduarte The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
mandre
left a comment
There was a problem hiding this comment.
I think it should work - CI at least shows there is no regression. Were you able to test this patch?
|
I should have enough testing done locally to verify its functionality soon. |
6d8e493 to
b012228
Compare
|
@mandre just spend the day testing and it seems to work as expected. Made some trivial changes to name trunks consistently. |
|
@adduarte: This pull request references Bugzilla bug 1964540, which is invalid:
Comment DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/bugzilla refresh |
|
@mandre: This pull request references Bugzilla bug 1964540, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
Requesting review from QA contact: DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
@openshift-ci[bot]: GitHub didn't allow me to request PR reviews from the following users: eurijon. Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
52b7473 to
530bc77
Compare
|
Addressed comment about trunkName. See inline reply |
|
@dulek could you take a ,ook at the code that sets the name of the trunk. |
|
we should probably wait for the upstream patch to settle and merge before approving this, it seems like they are still addressing some comments. |
Keep in mind we're talking about downstream CAPO and we want to retire this code soon anyway. We don't have to wait for the upstream code to merge (we'll inherit it anyway once we move to MAPO), however we need to make absolutely sure the API is stable and agreed on upstream. This is what we must implement in this patch. |
With the introduction of new technologies, like SR-IOV, it is required that the user have the ability to configured trunked and not-trunked ports for the same machines using spec.ports.trunk. - Extended trunk support needed check to cover spec.port and spec.network - Makes ports inherit trunk setting from spec.Trunk if not specified. - Refactored trunking to its own function. Trunk name matches port name - Added trunking to spec.ports - Trunks created for instances are named after their parent port. OSASINFRA-2504 Co-authored-by: Martin André <m.andre@redhat.com>
|
the current version of this patch mimics upstream: |
true, as long as the upstream api is stable, I suppose its ok |
|
little nit pick, but otherwise lgtm |
Co-authored-by: Emilio Garcia <iamemilio@users.noreply.github.com>
|
/lgtm |
|
@adduarte: All pull requests linked via external trackers have merged: Bugzilla bug 1964540 has been moved to the MODIFIED state. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Extend trunk configuration to port level in machineset
With the introduction of new technologies, like SR-IOV,
it is required that the user have the ability to
configured trunked and not-trunked ports for the same machines
using spec.ports.trunk.
OSASINFRA-2504