| commit | a2bfe4591be3be4e82f1c06d25ee03d7f0f13dec | [log] [tgz] |
|---|---|---|
| author | Paul J. Davis <paul.joseph.davis@gmail.com> | Wed Dec 11 11:47:22 2019 -0600 |
| committer | Paul J. Davis <paul.joseph.davis@gmail.com> | Wed Dec 11 11:47:22 2019 -0600 |
| tree | b813d301ee3e6599b2dd174b463e0ca351a04986 | |
| parent | 731dd9c716fc552145f80627cb1b42b85d961983 [diff] |
Updated scripts and configuration
This repository contains Ansible scripts for managing our VM testing infrastructure.
$ virtualenv venv $ source venv/bin/activate $ pip install -r requirements.txt
Create a ~/.couchdb-infra-cm.cfg file that contains the following options:
[ibmcloud] api_key = <REDACTED>
The tools/gen-inventory script can then be used to generate our production inventory file:
$ ./tools/gen-inventory > production
Once the a new VM has been added into the production inventory whoever provisioned the VM will need to execute the first Ansible run so that the CouchDB infra group has access (where infra group is defined as the list of GitHub users in roles/common/tasks/main.yml).
$ ansible-playbook -i production ci_agents.yml
Once this playbook finishes the new VM should be configured to be usable as a Jenkins agent.
Once Ansible has run against a new VM configuring it as an agent in Jenkins is fairly straightforward. You can just copy an existing node's configuration and update the SSH host IP address.