-
Notifications
You must be signed in to change notification settings - Fork 114
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
conformance-test: Filter NIC by environment variable #514
Conversation
Thanks for your PR,
To skip the vendors CIs use one of:
|
475b628
to
5fbefa6
Compare
Thanks for your PR,
To skip the vendors CIs use one of:
|
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 really like it!
I have one idea let me know what you think about.
we can have a device with the same name but on two different nodes for example:
node0 -> eno1 -> mlx
node1 -> eno1 -> intel
to over come this I will like to propose to extend the env variable to something like
<node>:<device>
both regex support
let me know what do you think
test/util/cluster/cluster.go
Outdated
} | ||
} | ||
return nil, fmt.Errorf("unable to find sriov devices in node %s", node) | ||
|
||
return filteredDevices, nil | ||
} | ||
|
||
// FindSriovDevices retrieves all valid sriov devices for the given node. |
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.
nit please update the function comment
It sounds good to me |
5fbefa6
to
d59f8c6
Compare
Thanks for your PR,
To skip the vendors CIs use one of:
|
Pull Request Test Coverage Report for Build 6456540272
💛 - Coveralls |
test/util/cluster/cluster.go
Outdated
// Name of environment variable to filter which decives can be discovered by FindSriovDevices and FindOneSriovDevice. | ||
// The filter is a regexp matched against node names and device name in the form <node_name>:<device_name> | ||
// | ||
// For example, givend the following devices in the cluster: |
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.
givend
LGTM |
d59f8c6
to
9e9a4fe
Compare
Thanks for your PR,
To skip the vendors CIs use one of:
|
9e9a4fe
to
62e148f
Compare
Thanks for your PR,
To skip the vendors CIs use one of:
|
In order to verify a specific NIC works well with the operator, the user who runs the test suite should be able to select involved devices. This commit introduces the environment variable `SRIOV_NODE_AND_DEVICE_NAME_FILTER` to implement the selection behavior. Signed-off-by: Andrea Panattoni <[email protected]>
62e148f
to
09c94a1
Compare
Thanks for your PR,
To skip the vendors CIs use one of:
|
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
In order to verify a specific NIC works well with
the operator, the user who runs the test suite should be able to select involved devices.
This commit introduces the environment variable
SRIOV_DEVICE_NAME_FILTER
to implement the selection behavior.examples:
SRIOV_DEVICE_NAME_FILTER=ens1f1
tells the test suite to use a specific device selecting it by its nameSRIOV_DEVICE_NAME_FILTER="ens1*"
tells the test suite that every device whose name starts with "ens1" can be used by the tests.