Bug 13589

Summary: Document sstate cache mirror best practices
Product: [Documentation] Reference Reporter: Paul Eggleton <bluelightning>
Component: handbookAssignee: Antonin Godard <antonin.godard>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: Medium+ CC: mark.morton, michael.opdenacker, poky.doc.watcher, poky.watcher, randy.macleod, srifenbark, tim.orling
Version: unspecified   
Target Milestone: 6.1 M1   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Yes (doc changes required)

Description Paul Eggleton 2019-10-09 20:56:27 UTC 
It would be useful to have a section in the docs that discusses the practical aspects of setting up and maintaining an sstate cache mirror, since there are a few gotchas. Some points to consider:

* How to configure it
* How to share it
* Arrangement of machines for a build farm or team of developers
* Keeping size under control (multiple approaches?)
* Ensuring siginfo files are synced before tarballs
* Troubleshooting issues (e.g. how to recognise host contamination - at least make people aware that it can be exposed more readily)
* Other services that need to be alongside e.g. PR server, hash equivalency, etc.
* Limitations
Comment 1 Paul Eggleton 2019-10-09 20:57:45 UTC 
I meant to mention - I thought we had a section similar to this already but I could not find it in the reference or development manuals.
Comment 2 Scott Rifenbark 2019-10-10 14:56:00 UTC 
We don't have this Paul.  Someone could provide some rough info and I can get it in.

Scott
Comment 3 Randy MacLeod 2024-10-24 15:04:00 UTC 
Bulk move of 5.1 M4 to 5.2 M2 as approved by AlexB.
Comment 4 Antonin Godard 2025-06-06 07:42:31 UTC 
Bulk move of bugs I am assigned to from Milestone 5.2M4 to 5.3M1.
Comment 5 Antonin Godard 2026-07-22 12:59:19 UTC 
Sent a series to document this: https://lore.kernel.org/r/20260722-sstate-mirrors-doc-v1-0-570baeb41c32@bootlin.com