On Fri, 2012-03-23 at 11:54 -0700, Nishanth Aravamudan wrote: > On 22.03.2012 [02:28:17 -0300], Lucas Meneghel Rodrigues wrote: > > > - Many spots still need to be parameterized on the presence of the > > > xmlrpc URL in the global config > > > > I've noticed we could factor that code out to a library function. > > Also, we could have a similar function to verify whether the install > > server is up and running. > > Yes, that's a good idea. What is the best way to determine if the > install server is up & running? I mean, we can use http requests to see > if it responds, but that doesn't mean it's correctly configured. I > guess, if we do a dummy remote get_systems or something, that may be > sufficient?
A remote get_systems or a similar xml_rpc call that may serve as a heartbeat check looks good. > > > - In my environment, I always want to reinstall the machine before > > > running any tests, so I've modified the default client and server > > > control files to run machine_install. Perhaps this makes sense to add > > > via a global config option -- always_reinstall_host or something. If > > > that is added, then I think the verify-before-job job should be > > > avoided if that option is set. Such an option also only makes sense if > > > xmlrpc_url is set. > > > > Like we have talked over irc, I'm not sure whether such an option is a > > good idea, but I'm not ruling it out completely. It might have value > > to just install the test machines in a compulsory way, although it > > seems excessive to me. > > In considering all the use cases autotest already supports ... I think > it's probably better not to force this. So I'm going to add some changes > to add a "<do not install>" option to the drop down box at job creation > time. This sounds sensible, indeed. _______________________________________________ Autotest mailing list [email protected] http://test.kernel.org/cgi-bin/mailman/listinfo/autotest
