Feature changed by: Adrian Schröter (adrianSuSE) Feature #308836, revision 2 Title: performance: scaling ...
- Buildservice: New + Buildservice: Rejected by (adrianSuSE) + reject date: 2010-01-21 12:15:54 + reject reason: security concerns are much more critical as you describe + it here, since one package in any repo you have added can take over + your entire system. people would need to setup xen/kvm and would be + easily to allowed to inject packages with complete wrong content. + one can work out a concept to handle all these cases, but this is + beyond the scope of this faterequest. Priority Requester: Mandatory
Requested by: Michael Meeks (michael_meeks)
Description: Build performance should scale, in proportion to the number of users, and not the number of build nodes. Put another way - providing a means to apply local CPU horsepower to the channel, combined with some approach (eg. an xdelta to the previous built binary RPMS) to overcome the (typically) assymetric bandwidth availability in a typical DSL client - easy to download a reference to diff against, hard to up-load it. I would love to donate my CPU resource to help accelerate the projects I care about; as - no-doubt would others. Of course - this has security implications, which are (most likely) more or less meaningless. We ship binaries (re-)built from internal, signing servers anyway, and we have an authentication structure in place: if paranoia reigns, we could restrict that to a further subset of privileged users.