| 5a9931c8571d8ff019760a9da4d16ceb710fca47 |
|
30-Dec-2012 |
Chris Sosa <sosa@chromium.org> |
Check-in lab_deploy -- a tool for syncing and deploying infrastructure changes.
This is my first attempt with the design at how deployment should work. There
are still some open questions but the program has 3 components -- 2 of which
have been implemented in this CL.
1) A bootstrap script that ssh's to the autotest master based on everyone's
config. This means if we want to test deployment changes, one could easly
modify their shadow_config and change their SERVER:host pair.
2) A script that is run on the autotest master. This farms out the work
as chromeos-test to all the machines.
3) A component that actually does the syncs/restarts.
3 isn't done. The reason is the more I thought about this the more it made
sense to re-use our puppet deployment scripts we already have because
we already have knowledge of where the devservers are stored based on the
puppet config on these machines.
I've left stubs in place of these applies to get implemented later.
BUG=chromium-os:26171
TEST=Ran it.
Change-Id: I36114be2359f06e004de2911129c76d3c031fd3e
Reviewed-on: https://gerrit.chromium.org/gerrit/40294
Commit-Queue: Chris Sosa <sosa@chromium.org>
Reviewed-by: Chris Sosa <sosa@chromium.org>
Tested-by: Chris Sosa <sosa@chromium.org>
/external/autotest/site_utils/deploy_autotest/lab_deploy_helper.py
|