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

How does storage work in the kubernetes setup? #153

Open
GRVYDEV opened this issue Nov 12, 2024 · 1 comment
Open

How does storage work in the kubernetes setup? #153

GRVYDEV opened this issue Nov 12, 2024 · 1 comment

Comments

@GRVYDEV
Copy link

GRVYDEV commented Nov 12, 2024

I have a question regarding the relationship between frontend, scheduler and storage in the kubernetes setup. I am currently using buildbarn as a remote build server for chromium. My main question is with regards to caching. By default if I am sending build requests to the frontend are the actions automatically cached or do I need to tweak the config there? Thanks!

(BTW this is an awesome project Ive been able to get chromium builds down to around 30 minutes)

@moroten
Copy link
Collaborator

moroten commented Nov 14, 2024

The Execute requests are passed through the frontend to the scheduler. The scheduler then pass the request to one bb-worker. When finished, the result is uploaded by the bb-worker to the AC (action cache) and outputs are uploaded to the CAS (content adressable storage), unless ExecuteRequest.do_not_cache=true.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants