> ---------- Forwarded message ---------- > From: *Damian, Alexandru* > Date: Tuesday, November 12, 2013 > Subject: toaster builder design proposal - RFC > To: "[email protected]" <[email protected]> > > > Hello all, > > I've prepared a design proposal for the building mode for Toaster. > I'm attaching it here. > > Can you please review and comment by replying to this mailing list ? > > Cheers, > -- > Alex Damian > Yocto Project > SSG / OTC >
Hi Alex, Thanks for the design doc. This is my understanding: Toaster will allow managing projects and builds that are local and remote. Local means the Toaster web server and the Build Environment - "BE" (thanks for terming this) are on the same machine and Remote means Toaster and BE are on different machines. And Toaster will be able to manage more than one BEs. I have a few questions: 1. How will Toaster know which BE it has to talk to. Does the BE register with Toaster? Or is Toaster configured with the available BEs? 2. In 3.1.1, you said that it should be possible to send a list of layers to be made available in the BE. How will Toaster know the complete list of supported layers? 3. The build status and artifacts are local to the BE and they will be lost if the BE is gone. It would be nice if the build artifacts are available even after BE is gone. Can we make BE transient and the build artifacts persistent? I am catching up with Yocto, so please guide me if these have been answered in a different document. Thanks, Ravi _______________________________________________ toaster mailing list [email protected] https://lists.yoctoproject.org/listinfo/toaster
