-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[PINS] Build P4RT container for PINS #9083
Conversation
7747b5a
to
199c245
Compare
cc: @rhalstea |
62af37f
to
33042a6
Compare
@lguohan please take a look at the new Dockerfiles and make files for the P4RT container. We will update the submodules after all of the dependencies are merged. |
2527194
to
d135388
Compare
0f1712c
to
bfc824f
Compare
there are quite a few docker-slave build failures, can you check? |
bfc824f
to
8657203
Compare
@lguohan, this issue is that pre-built Bazel binaries are not available for For now, I have disabled P4RT for Tests are re-running now. Thanks! |
a60a692
to
02b459f
Compare
/azpw run Azure.docker-slave-bullseye |
/AzurePipelines run Azure.docker-slave-bullseye |
Azure Pipelines successfully started running 1 pipeline(s). |
/azpw run Azure.sonic-buildimage |
/AzurePipelines run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
/azpw run Azure.sonic-buildimage |
/AzurePipelines run Azure.sonic-buildimage |
Thanks for the review @prsunny @qiluo-msft , PTAL. I pushed an update addressing the comments. |
/azpw run Azure.docker-slave-bullseye |
/AzurePipelines run Azure.docker-slave-bullseye |
Azure Pipelines successfully started running 1 pipeline(s). |
- Add INCLUDE_PINS to config to enable/disable container - Add Docker files and supporting resources - Add sonic-pins submodule and associated make files Submission containing materials of a third party: Copyright Google LLC; Licensed under Apache 2.0 Co-authored-by: Runming Wu <runmingwu@google.com> Co-authored-by: Robert J. Halstead <rhalstea@google.com> Co-authored-by: Srikishen Pondicherry Shanmugam <kishanps@google.com> Co-authored-by: Brian O'Connor <bocon@opennetworking.org> Signed-off-by: Brian O'Connor <bocon@opennetworking.org>
Co-authored-by: Prince Sunny <prince.sunny@microsoft.com>
Update: Nevermind, it was a typo in the package name. Fixed and re-running tests. |
19872df
to
ed9d8e8
Compare
/azpw run Azure.docker-slave-bullseye |
/AzurePipelines run Azure.docker-slave-bullseye |
Azure Pipelines successfully started running 1 pipeline(s). |
@qiluo-msft All required tests have passed can we get this merged now? |
- Add INCLUDE_PINS to config to enable/disable container - Add Docker files and supporting resources - Add sonic-pins submodule and associated make files Submission containing materials of a third party: Copyright Google LLC; Licensed under Apache 2.0 #### Why I did it Adds P4RT container to SONiC for PINS The P4RT app is covered by this HLD: https://github.com/pins/SONiC/blob/master/doc/pins/p4rt_app_hld.md #### How I did it Followed the pattern and templates used for other SONiC applications #### How to verify it Build SONiC with INCLUDE_P4RT set to "y". Verify that the resulting build has a container called "p4rt" running. You can verify that the service is up by running the following command on the SONiC switch: ```bash sudo netstat -lpnt | grep p4rt ``` You should see the service listening on TCP port 9559. #### Which release branch to backport (provide reason below if selected) None #### Description for the changelog Build P4RT container for PINS
Submission containing materials of a third party:
Copyright Google LLC; Licensed under Apache 2.0
Co-authored-by: Runming Wu runmingwu@google.com
Co-authored-by: Robert J. Halstead rhalstea@google.com
Co-authored-by: Srikishen Pondicherry Shanmugam kishanps@google.com
Co-authored-by: Brian O'Connor bocon@opennetworking.org
Why I did it
Adds P4RT container to SONiC for PINS
The P4RT app is covered by this HLD:
https://github.com/pins/SONiC/blob/master/doc/pins/p4rt_app_hld.md
How I did it
Followed the pattern and templates used for other SONiC applications
How to verify it
Build SONiC with INCLUDE_P4RT set to "y".
Verify that the resulting build has a container called "p4rt" running.
You can verify that the service is up by running the following command on the SONiC switch:
sudo netstat -lpnt | grep p4rt
You should see the service listening on TCP port 9559.
Which release branch to backport (provide reason below if selected)
None
Description for the changelog
Build P4RT container for PINS