Skip to content
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

[pb] enable connection to proxybuffer service #24

Open
2 tasks
timothytrippel opened this issue Sep 29, 2024 · 0 comments
Open
2 tasks

[pb] enable connection to proxybuffer service #24

timothytrippel opened this issue Sep 29, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@timothytrippel
Copy link
Collaborator

timothytrippel commented Sep 29, 2024

Prior versions of this infrastructure used a proprietary proxy buffer service, noted in the code as the RegistryBuffer. The infrastructure should be updated to:

  • have the PA launch the opensource ProxyBuffer service client
  • have K8 pod configuration launch the ProxyBuffer container
@timothytrippel timothytrippel added the enhancement New feature or request label Sep 29, 2024
@timothytrippel timothytrippel self-assigned this Sep 29, 2024
timothytrippel added a commit to timothytrippel/opentitan-provisioning that referenced this issue Oct 1, 2024
The registry buffer service was removed, and will soon be replaced with
the proxybuffer service. However, the enablement flag within the PA was
still defaulting to true. This is updated to default to false until lowRISC#24
can be fixed.

Signed-off-by: Tim Trippel <[email protected]>
timothytrippel added a commit that referenced this issue Oct 1, 2024
The registry buffer service was removed, and will soon be replaced with
the proxybuffer service. However, the enablement flag within the PA was
still defaulting to true. This is updated to default to false until #24
can be fixed.

Signed-off-by: Tim Trippel <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant