-
Notifications
You must be signed in to change notification settings - Fork 111
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
[switchdev 4/x] split systemd service to two parts #602
[switchdev 4/x] split systemd service to two parts #602
Conversation
Thanks for your PR,
To skip the vendors CIs use one of:
|
Description=Configures SRIOV NIC - pre network configuration | ||
DefaultDependencies=no | ||
After=network-pre.target systemd-udev-settle.service systemd-sysusers.service systemd-sysctl.service | ||
Before=network.target NetworkManager.service systemd-networkd.service ovs-vswitchd.service ovsdb-server.service |
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.
Note: If a service defined in After or Before section is not exist it will be simply ignored.
Thanks for your PR,
To skip the vendors CIs use one of:
|
ca39739
to
6da8431
Compare
Thanks for your PR,
To skip the vendors CIs use one of:
|
6da8431
to
e3fd1c8
Compare
Thanks for your PR,
To skip the vendors CIs use one of:
|
Pull Request Test Coverage Report for Build 7842844986
💛 - Coveralls |
e3fd1c8
to
67155e3
Compare
Thanks for your PR,
To skip the vendors CIs use one of:
|
67155e3
to
00c277e
Compare
Thanks for your PR,
To skip the vendors CIs use one of:
|
00c277e
to
67f69ff
Compare
Thanks for your PR,
To skip the vendors CIs use one of:
|
Signed-off-by: Yury Kulazhenkov <ykulazhenkov@nvidia.com>
67f69ff
to
7e39e9b
Compare
Thanks for your PR,
To skip the vendors CIs use one of:
|
PR updated to add tests for systemd service |
7e39e9b
to
9884bbc
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!
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.
Left a few comments. I'm finding a little bit difficult to read the service.go
file with that phase
variable read in many places.
Have you considered the option of creating two functions runServiceCmdPre()
and runServiceCmdPost()
called at the very beginning of runServiceCmd()
? That way we have a bunch of duplicated code, but we'd get rid of many if/else
statments. WDYT?
bindata/manifests/sriov-config-service/kubernetes/sriov-config-service.yaml
Outdated
Show resolved
Hide resolved
The service has required argument "phase" Two phases are supported now: * pre - before the NetworkManager or systemd-networkd * post - after the NetworkManager or systemd-networkd "sriov-config" systemd unit is responsible for starting the service in the "pre" phase mode. "sriov-config-post-network" systemd unit starts the service in the "post" phase mode. The service may use different plugins for each phase and call different initialization flows. The "post" phase checks the completion status of the "pre" phase by reading the sriov result file. The "pre" phase should set "InProgress" status if it succeeds or "Failed" otherwise. If the result of the "pre" phase is different than "InProgress", then the "post" phase will not be executed and the execution result will be forcefully set to "Failed". Signed-off-by: Yury Kulazhenkov <ykulazhenkov@nvidia.com>
The first part is executed before the NeworkManager or systemd-networkd starts on the host. The second part is triggered after the network configuration is complete. This change is required to support hw offload use-case with systemd service. Signed-off-by: Yury Kulazhenkov <ykulazhenkov@nvidia.com>
9884bbc
to
7faea56
Compare
Thanks for your PR,
To skip the vendors CIs use one of:
|
Thanks for the review @zeeke. |
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
split systemd service to two parts:
The first part is executed before the
NeworkManager or systemd-networkd
starts on the host.
The second part is triggered after the
network configuration is complete.
This change is required to support hw offload
use-case with systemd service.
cc @adrianchiris @zeeke @SchSeba