Reorganize Launchpad Projects for Lava components
We should reorganize the Launchpad projects for the various Lava components to the following scheme:
- lava -- project group containing:
- lava-server -- contains the django settings file and templates
- this well mostly be extracted from what is lp:launch-control today
- lava-scheduler -- django application for scheduling jobs
- what exists for this is in lp:lava currently
- lava-dispatcher -- tool that runs tests on hardware
- this is also in lp:lava currently
- lava-dashboard -- django application for showing test results
- this is lp:launch-control currently
- lava-tool -- command line entry point and framework
- this actually exists already and has the right name!
- lava-dashboard-tool
- new name for launch-control-tool
- lava-test -- plugin for lava-tool that adds commands for running tests
- new name and refactoring for abrek
- lava-auth-tool -- plugin for lava-tool that adds commands for authenticating against validation.
- lava-scheduler-tool -- plugin for lava-tool that adds commands for interacting with the scheduler
- these last two don't actually exist
Is this too many projects?
The various server side projects all need to be the same license -- probably AGPL3?
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Zygmunt Krynicki
- Completed by
- Zygmunt Krynicki
Related branches
Related bugs
Sprints
Whiteboard
Rambles on Thursday of UDS: the changes that will allow us to rename projects without messing up stacking might happen very soon. So it might make sense to wait until that happens before we do the project renames.
most of the files that are now in launch-control will end up in lava-dashboard of course. But some (e.g. css) will end up in lava-server -- should lp:lava-server start off as a branch of launch-control?
