Hi.
This a brainstorm message. I'd like to hear your pros and cons on merging the scheduler and dashboard. For me the advantages outweigh the disadvantages:
Pros: * A simple model for tracking a result back to a job, without having to jump through javascript hoops and hard synchronization/availability issues (and back!) * A stronger case that lava-{dashboard,scheduler} has all the key models - devices, tests, results - all in one place. Easier for extension developers to target as their backend. * Less fuss for extension developers that don't really consider the implications of this distributed system * Easier workflow, one less component to release ;-) * We get to clean up dashboard_app and rename it to lava-*
Cons: * We may need to do a flag day when we have one big migration that will rename tables, etc * This will break sql-based reports (but I don't think that we really care about them anymore) * I'm not sure what we'd do with the lava-dashboard, lava-scheduler projects on launchpad
PS: We could move this a step forward and consider merging with lava-server (at the source code repo level) where we''d have clear separation from the core (server,scheduler,dashboard) and extensions that build on the core.
Thanks ZK