LLee Yarwoodhack: Run bazel-race
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
hack: Run bazel-race Signed-off-by: Lee Yarwood <lyarwood@redhat.com> | 8 个月前 | |
net, passt: Introduce passtRepairManager Introduce infrastructure to execute the passt-repair binary to completion, and replace the stub call with concrete implementation. The execution of passt-repair is done in a dedicated one-off goroutine running in parallel to ongoing migration process. The goroutine returns once passt-repair completes its operation, or context times out. Currently, passt-repair gets executed multiple times per migration target, due to consecutive reconciliation cycles. Make sure it only runs once per vmi, and skip execution if already running. On migration source, the repair socket must pre-exist since it is created by passt when it stars. In this case the argument for passt-repair should be the full path to the socket. On the other hand, migration target execution occurs before passt execution and the socket file is not expected to exit. Then passt-repair receives the path to the directory where it is expected, for passt-repair to listen on the FS capturing the socket creation event. Signed-off-by: Nir Dothan <ndothan@redhat.com> | 11 个月前 | |
net, passt: Introduce passtRepairManager Introduce infrastructure to execute the passt-repair binary to completion, and replace the stub call with concrete implementation. The execution of passt-repair is done in a dedicated one-off goroutine running in parallel to ongoing migration process. The goroutine returns once passt-repair completes its operation, or context times out. Currently, passt-repair gets executed multiple times per migration target, due to consecutive reconciliation cycles. Make sure it only runs once per vmi, and skip execution if already running. On migration source, the repair socket must pre-exist since it is created by passt when it stars. In this case the argument for passt-repair should be the full path to the socket. On the other hand, migration target execution occurs before passt execution and the socket file is not expected to exit. Then passt-repair receives the path to the directory where it is expected, for passt-repair to listen on the FS capturing the socket creation event. Signed-off-by: Nir Dothan <ndothan@redhat.com> | 11 个月前 | |
net, passt: Introduce passtRepairManager Introduce infrastructure to execute the passt-repair binary to completion, and replace the stub call with concrete implementation. The execution of passt-repair is done in a dedicated one-off goroutine running in parallel to ongoing migration process. The goroutine returns once passt-repair completes its operation, or context times out. Currently, passt-repair gets executed multiple times per migration target, due to consecutive reconciliation cycles. Make sure it only runs once per vmi, and skip execution if already running. On migration source, the repair socket must pre-exist since it is created by passt when it stars. In this case the argument for passt-repair should be the full path to the socket. On the other hand, migration target execution occurs before passt execution and the socket file is not expected to exit. Then passt-repair receives the path to the directory where it is expected, for passt-repair to listen on the FS capturing the socket creation event. Signed-off-by: Nir Dothan <ndothan@redhat.com> | 11 个月前 | |
net, passt: Introduce passtRepairManager Introduce infrastructure to execute the passt-repair binary to completion, and replace the stub call with concrete implementation. The execution of passt-repair is done in a dedicated one-off goroutine running in parallel to ongoing migration process. The goroutine returns once passt-repair completes its operation, or context times out. Currently, passt-repair gets executed multiple times per migration target, due to consecutive reconciliation cycles. Make sure it only runs once per vmi, and skip execution if already running. On migration source, the repair socket must pre-exist since it is created by passt when it stars. In this case the argument for passt-repair should be the full path to the socket. On the other hand, migration target execution occurs before passt execution and the socket file is not expected to exit. Then passt-repair receives the path to the directory where it is expected, for passt-repair to listen on the FS capturing the socket creation event. Signed-off-by: Nir Dothan <ndothan@redhat.com> | 11 个月前 |