|author||Nick Vatamaniuc <firstname.lastname@example.org>||Mon Jun 27 13:43:59 2022 -0400|
|committer||Nick Vatamaniuc <email@example.com>||Mon Jun 27 13:43:59 2022 -0400|
Replace PPC64LE worker with a new VM
This repository contains Ansible scripts for managing our VM testing infrastructure.
$ python3 -m venv venv $ source venv/bin/activate $ pip install -r requirements.txt
On BigSur Mac may have to do:
$ env LDFLAGS="-L$(brew --prefix firstname.lastname@example.org)/lib" CFLAGS="-I$(brew --prefix email@example.com)/include" pip install -r requirements.txt
The basic steps to provisioning a new Jenkins agent node are:
Node names should follow this pattern:
There should be a single bastion VM setup for each subnet. We just use the cheapest cx2-2x4 instance for these nodes so that we can jump to the other hosts.
Provisioning a bastion VM is much the same as for a ci_agent though should happen much more rarely. Currently the assumption is that each subnet has exactly one bastion. The
./tools/gen-config script will complain if this assumption is violated so it should be obvious if we get this wrong. It will also complain if we have a subnet that is missing a bastion box.
The steps for provisioning a new bastion box are:
Bastion names should follow this pattern:
~/.couchdb-infra-cm.cfg file that contains the following options:
[ibmcloud.<environment>] api_key = <REDACTED> api_url = https://us-south.iaas.cloud.ibm.com/v1 crn = crn:v1:... instance_id = 123-abc... [extra.<instancename>] ip_addr = x.y.z.w arch = s390x num_cpus = 4 ram = 8
<environment> is a tag used to differentiate multiple environments. It allows fetching instances from more than one IBM Cloud accounts. If
api_url is provided, it will be used to fetch VPC instances. By default is uses
crn field will be added as a
CRN: <crn> header if provided.
instance_id is used only by the
power environment. (See
Power Instances section for more details).
extra.<instancename> can be an extra unmanaged manually added instance which is not discoverable via cloud.ibm.com with an API key.
tools/gen-config script can then be used to generate our
production inventory and
This script requires access to the
https://cloud.ibm.com account that hosts the VMs so not everyone will be able to run this script. However this is only important when provisioning new nodes. Modifying ansible scripts and apply changes to existing nodes can be done by any CouchDB PMC member that's been added to the CI nodes via this repository.
$ ansible-playbook bastions.yml $ ansible-playbook ci_agents.yml
% ansible -i production ci_agents -a "sudo sv restart jenkins" % ansible -v -i production ci_agents -a "sudo apt list --upgradable" % ansible -v -i production ci_agents -a "sudo unattended-upgrade -v"
(Assuming the generated
ssh.cfg was included in
If you want to ssh directly to a node, you can do:
$ ssh $hostname
$ ssh couchdb-worker-x86-64-debian-dal-1-01