> I thought about it a bit more: > > Maybe a better approach would be to have the global_config module find > the ini file in job.autodir (so on a client it would show up in the > client/ dir, and on the server in the "true" top-level dir) and then > add support to Autotest.run so that it copies over the server's copy > of the config to the client before launching a client job? > > So that way it would "just work", and changes to the server config > would automatically get pushed out to client jobs. All without moving > the file that users running a server need to edit. And it's not too > complex of a design; the Autotest.run code already needs to copy over > a few files by hand like control files so copying over the config too > isn't too much of a burden.
Sounds good to me. > The only concern I have is that this still might not play well with a > multi-server setup. If the servers have different configs I'm not sure > that it works all that well (although I still don't know that this > introduces any "new" problems, so I don't think it makes things any > messier in that case then they already are). I cc'ed Scott and Steve > in case they can comment on that. By multi-server setup, do you mean multiple copies of the autotest server code on the same tree? Or a master with drones? -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
