Launch testpmd and trex with an infinite loop entrypoint #92
+40
−62
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ramperher
force-pushed
the
dpdk-summit-2024
branch
from
8909940 to
b861677
Compare
|
from change #92: |
ramperher
force-pushed
the
dpdk-summit-2024
branch
from
b861677 to
8bf1e5a
Compare
|
from change #92: |
ramperher
force-pushed
the
dpdk-summit-2024
branch
2 times, most recently
from
9d64f73 to
8106fa1
Compare
|
from change #92: |
ramperher
force-pushed
the
dpdk-summit-2024
branch
from
8106fa1 to
cb0807d
Compare
|
from change #92: |
|
This work is finished, closing this |
|
Retaking this to test grout integration |
ramperher
force-pushed
the
dpdk-summit-2024
branch
from
cb0807d to
2a3eff3
Compare
|
from change #92: |
|
from change #92: |
|
from change #92: |
|
from change #92: |
ramperher
force-pushed
the
dpdk-summit-2024
branch
from
2a3eff3 to
5515318
Compare
tonyskapunk
reviewed
Nov 27, 2024
| ENTRYPOINT ["/usr/local/bin/example-cnf/testpmd-wrapper"] | ||
| #ENTRYPOINT ["/usr/local/bin/example-cnf/testpmd-wrapper"] | ||
| ## Make the container to live forever without executing testpmd-wrapper, we'll run it manually | ||
| ENTRYPOINT ["/usr/local/bin/example-cnf/run/infinite.sh"] |
There was a problem hiding this comment.
why not use sleep infinity instead?
There was a problem hiding this comment.
I think I tried in the past and had troubles with that. Anyway I don't intend to merge this change, this is just for troubleshooting
ramperher
force-pushed
the
dpdk-summit-2024
branch
from
60fb1c3 to
0e3ec09
Compare
|
from change #92: |
ramperher
force-pushed
the
dpdk-summit-2024
branch
from
0e3ec09 to
b25bfca
Compare
|
from change #92: |
ramperher
force-pushed
the
dpdk-summit-2024
branch
from
b25bfca to
e9519f1
Compare
|
from change #92: |
ramperher
force-pushed
the
dpdk-summit-2024
branch
from
e9519f1 to
7f7a2af
Compare
|
from change #92: |
|
from change #92: |
ramperher
force-pushed
the
dpdk-summit-2024
branch
from
00ffe56 to
8383fa9
Compare
|
from change #92: |
|
from change #92: |
|
from change #92: |
ramperher
force-pushed
the
dpdk-summit-2024
branch
from
5638d82 to
75169e4
Compare
|
from change #92: |
|
Discarded in favour of #111 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Not intended to be merged, this is just for experimenting for DPDK Summit 2024 presentation and for grout integration.
The idea of this change is to launch testpmd and trex with an infinite loop as entrypoint, so that we can manually launch the commands to run both tools. For this, we need to remove lifecycle commands and probes to avoid the pod to be restarted.