Hi Belén, You write: "In a Toaster instance connected to a build farm, a user of Toaster should not be able to override any variables that impact how hardware runs builds and where artifacts are stored."
I would think of this in the opposite manner. Proposed wording: "In a Toaster instance connected to a build farm, the remote build instance will _always_ override any variables that impact how hardware runs builds and where artifacts are stored, regardless of any default bitbake settings or explicit user settings." Here is my reasoning: * The remote build instance's manager/configuration will need to dynamically set these values regardless and in all cases, based on its current resources and environment, whether they are previously defined or not. * We cannot prevent the user from manually setting the values no matter what we do, as per your mention of the free form "add variables" option. * We can think of this class of variables as "preferences". If it is a local build then these values will be used (not overridden) and user will get what they expect. If it is a remote build then the values will be expected to be overridden by design and again the user will get what they expect. * With this model there are no surprises, both workflows are easily covered, and everyone is happy. - David > -----Original Message----- > From: Barros Pena, Belen [mailto:[email protected]] > Sent: Wednesday, July 09, 2014 9:42 AM > To: [email protected] > Cc: Wymore, Farrell; Reyna, David; Lerner, Dave > Subject: [RFC] Configuration variables in Toaster > > Some discussion happened today about the list of variables that Toaster > should expose (see below from previous thread). It was observed that, for > cases when you are in control of the build hardware, it would be handy to > be able to set variables like PARALLEL_MAKE, BB_NUMBER_THREADS and > SSTATE_DIR. I took out those variables from the list because they impact > how hardware runs builds and where build artifacts are stored, which are > things that a user of a Toaster instance connected to a build farm should > probably not touch. > > It was suggested that maybe the list of variables could change if Toaster > is running on the same machine that runs the builds. There is also the > "add variables" option, which is free form and that will allow you to type > any variable and any value you want. So that option would in theory allow > you to set PARALLEL_MAKE or anything else you might want to set. > > Now: that brings up a question about variable handling. In a Toaster > instance connected to a build farm, a user of Toaster should not be able > to override any variables that impact how hardware runs builds and where > artifacts are stored. If the user adds PARALLEL_MAKE = "8" to a Toaster > project configuration, that should have no effect on the PARALLEL_MAKE > value that a build server in a farm is supposed to use, and that should > have been set by whomever administers that farm. Same goes for SSTATE_DIR, > SSTATE_MIRRORS, DL_DIR, etc. Maybe I am just not looking at this in the > right way, or there is something I don't fully understand, but it seems to > me that Toaster could become a liability otherwise. > > Any thoughts on how this should be handled would be much appreciated. > > Thanks! > > Belén > > On 08/07/2014 15:40, "Barros Pena, Belen" <[email protected]> > wrote: > > >That's the Toaster page that allows you to edit the project local.conf > >file. I am trying to come up with a final list of the variables that will > >be listed in that page. > > > >Looking at the default local.conf file, and excluding stuff that should be > >defined by the Toaster instance (things like SSTATE_MIRRORS or DL_DIR), > >this is what I'm left with: > > > >PACKAGE_CLASSES > >SDKMACHINE > >EXTRA_IMAGE_FEATURES > >USER_CLASSES > >TEST_IMAGE > >OE_TERMINAL > >PATCHRESOLVE > >PACKAGECONFIG_pn-qemu-native (for Qemu configuration) > >ASSUME_PROVIDED (for Qemu configuration) > >CONF_VERSION > > > >Of the above, I am not sure we should expose the Qemu configuration stuff > >or CONF_VERSION, but I could be wrong. > > > > > >Hob also allows you to set: > > > >INCOMPATIBLE_LICENSE > >IMAGE_FSTYPES > >IMAGE_EXTRA_SPACE > >TOOLCHAIN_BUILD > >LINGUAS_INSTALL > >plus proxy configuration variables (http_proxy, https_proxy, ftp_proxy, > >all_proxy, CVS_PROXY_HOST, CVS_PROXY_PORT) > > > >Should we list this Hob stuff as well (except the proxy variables, I > >guess)? > > > >Apart from the above, there will be a way to set IMAGE_INSTALL_append, and > >also an option to add any other variable (free text kind of thing). > > > >Any thoughts on this list? > > > >Thanks! > > > >Belén > > > >-- > >_______________________________________________ > >toaster mailing list > >[email protected] > >https://lists.yoctoproject.org/listinfo/toaster > -- _______________________________________________ toaster mailing list [email protected] https://lists.yoctoproject.org/listinfo/toaster
