Re: BuildStream Embarks on Remote Execution

[Laurence Urhegyi <Laurence Urhegyi codethink co uk>]

Hi Finn,

I've just done a bit of googling and there is already a BuildGrid out there, 
although it's nothing to do with building software - https://buildgrid.com

There's a twitter hashtag for BuildGrid too, which seems unrelated to the above 
- https://twitter.com/hashtag/BuildGrid?src=hash

Not sure if this will matter later later on if we try to get the domain, but I 
don't feel the above things should block us from choosing that name, really.

There's also a Conduit out there, funnily enough it's a GNOME application - 
https://wiki.gnome.org/Projects/Conduit

And there's a Conflux, too - https://directory.fsf.org/wiki/Conflux

So I guess those two should be avoided (but i'm happy to be corrected if others 
feel strongly).

Faucet doesn't seem to be taken, but I'm not sure that's a great name...

Obviously I didn't find anything for BREWS (BuildStream Remote Execution and 
Worker Services).

Thanks,
Laurence


On 21/05/18 17:44, finn wrote:
> Hi,
>
> Here at BuildStream <https://buildstream.gitlab.io/buildstream/about.html>, we 
> are developing a Free Software tool for building and integrating software 
> stacks. Buildstream is designed to work with a set of YAML files which describe 
> the targets and dependencies, evaluates the various build instructions and 
> deploys the resulting targets. It supports multiple build-systems and can output 
> in a range of formats.
>
> We are interested in creating a remote execution service by implementing the 
> Remote Execution API 
> <https://docs.google.com/document/d/1s_AzRRD2mdyktKUj2HWBn99rMg_3tcPvdjx3MPbFidU/edit?usp=sharing> 
> (REAPI) and the Remote Workers API 
> <https://docs.google.com/document/d/1s_AzRRD2mdyktKUj2HWBn99rMg_3tcPvdjx3MPbFidU/edit?usp=sharing> 
> (RWAPI), taking inspiration from the Bazel 
> <https://github.com/bazelbuild/bazel-buildfarm>and Uber 
> <https://github.com/uber/bazel-buildfarm> implementations. Buildstream's 
> sandboxing and action model differs from Bazel in that the actions (e.g `make` 
> of a third party module) are executed in a sandbox that doesn't have access to 
> host tools or libraries. The planned implementation will be designed to work 
> well with this and will not be designed to be BuildStream specific.
>
> A rough plan 
> <https://docs.google.com/presentation/d/1hX9fH-Rx5-Kjq5gqpZyeMVLlGj6oe73xFUaIOB_isZ0/edit#slide=id.p> 
> is in the pipeline which shows an initial outline to be implemented in Python 
> with the design to be expanded on in the future. The first focus will be a 
> simple implementation of the REAPI. This will register workers, consult the 
> action cache and queue actions ready for workers to request. The details of the 
> implementation of the RWAPI are still being worked on.
>
> Currently though, we are blocked by the name. We want a name distinct from 
> BuildFarm, here are some notable suggestions thus far:
>
> [*] Conflux
> [*] Conduit
> [*] BuildGrid
> [*] Faucet
>
> Please reply if you have any comments, suggestions, need clarification of any of 
> the points or have any ideas for what to call this implementation.
>
> Thanks,
> Finn
>
>
> _______________________________________________
> Buildstream-list mailing list
> Buildstream-list gnome org
> https://mail.gnome.org/mailman/listinfo/buildstream-list

--
Laurence Urhegyi
Codethink Ltd
http://www.codethink.co.uk/
We respect your privacy.   See https://www.codethink.co.uk/privacy.html