Create deployment script for multiple payload machines

[gerkey]

Assuming that you're on the VPN, rsync a locally available tactics repo to all payload machines, set env vars as necessary and then spawn vehicles. We might want to make the spawning step available in the cloudsim UI in addition to or instead of via a script.

The script would take the set of vehicle IDs to be spawned. It'll decide how to parcel out the work over the available payload machines then write that configuration onto each one.

Also offer spawn script that will ssh into each payload and spawn the earlier configured vehicles.

[gerkey]

@tfoote and I made a plan today to develop two scripts, one to deploy and the other to spawn.

Deployment

deploy_blue --hosts <num_hosts> -i </path/to/key.pem> </path/to/my/local/working/copy>
deploy_gold --hosts <num_hosts> -i </path/to/key.pem> </path/to/my/local/working/copy>

where:

• num_hosts is how many payload machines are available for you to use in this round. It will compute the IPs using our standard scheme based on the script name and args; e.g., deploy_blue --hosts 2 will try to contact 192.168.2.10 and 192.168.2.11
• /path/to/key/key.pem is the SSH private key to be used
• /path/to/my/local/working/copy is a local path to what is assumed to be a cloned fork of the scrimmage-templates repo

The script will ssh/rsync the local working copy to a known location on each of the indicated machines, then exit.

Spawning

rspawn_blue --hosts <num_hosts> -i </path/to/key.pem> <vehicle_ids...>
rspawn_gold --hosts <num_hosts> -i </path/to/key.pem> <vehicle_ids...>

where:

• is a space-separated list of the vehicle IDs that you want to spawn. E.g., it could be '1 2 25 26'.

The script will spread the load of the requested vehicles across the available machines, sshing to each one and running the appropriate local spawn_blue or spawn_gold command. The script will hold all the SSH connections open and keep running until given Ctrl-C by the user, at which point it will tear everything down, including the remote processes.

[tfoote]

First work here: 8057d25dbdf1d0c05155d52580973aa8df2e2cbe

[tfoote]

sasc_deploy is working now for payloads. Only a single entry point for all payloads.