Hello, Please find some answers below,
Alex On Tue, Dec 3, 2013 at 9:45 PM, Ravi Chintakunta < [email protected]> wrote: > > ---------- 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? > Toaster needs to be configured with the available BEs. In the default, shipping configuration, a single BE would be configured, the "localhost". This BE is the same as what user gets when running "source oe-init-build-env". Customized BE configuration / interfacing code would have to be created by each user, according to their infrastructure and objectives. > > 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? > Currently, we envision sending a list of GIT repo URLs that can be accessed by BE, together with SHA1 of HEAD commits. The BE controller would clone the GIT repositories and create the layers.conf prior to lunching the bitbake server. > > 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? > The BE has to be released explicitly by Toaster building module. In this regard, the BE and artifacts can be maintained as long as needed for detailed inspection. A set of important assets would be copied over to permanent storage on build completion. The definitions of "important" and "permanent storage" are up to debate. Please send in your thoughts. > > 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 > -- Alex Damian Yocto Project SSG / OTC
_______________________________________________ toaster mailing list [email protected] https://lists.yoctoproject.org/listinfo/toaster
