Refactor configuration code in LAVA dispatcher

Registered by Spring Zhang on 2011-06-24

As a release tester, I want to setup LAVA dispatcher configuration one time in my machine then it can keep even after LAVA upgrading and don't want to modify the python code from time to time.
As a LAVA dispatcher user, I want to deploy a local LAVA environment and I can keep all the configurations during the upgrading so that it's easy to use.

Blueprint information

Status:
Complete
Approver:
Paul Larson
Priority:
Medium
Drafter:
Paul Larson
Direction:
Approved
Assignee:
Paul Larson
Definition:
Approved
Series goal:
Accepted for linaro-11.11
Implementation:
Implemented
Milestone target:
milestone icon 2011.09
Started by
Paul Larson on 2011-08-11
Completed by
Paul Larson on 2011-09-23

Related branches

Sprints

Whiteboard

[fboudra, Sep 1 2011] Headline and acceptance criteria is missing.
[pwlars, Sep 6 2011] Headline and Acceptance criteria added.
[fboudra, Sep 23 2011] Move the ssh and qemu clients testing to a new blueprint

Headline: Local configuration data for lava-dispatcher is now stored in config files.

Acceptance: Config files are read for config data rather than defining things like test machines in the code.

(?)

Work Items

Work items:
Decide on config format: DONE
Specify how to split up files between board configs and board type configs: DONE
[david-schwarz] Write config loader: DONE
[david-schwarz] add support for config loader to existing clients: DONE
[david-schwarz] convert existing config information to example config files: DONE
merge and test existing branches with linaro image job: DONE
Merge and test existing branches with android job: DONE
Update ssh client to use new config code: DONE
Update qemu client to use new config: DONE
[mwhudson] factor out run_cmd api improvements and land separately: DONE

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.