mirror of
https://github.com/certbot/certbot.git
synced 2026-06-05 06:42:10 -04:00
d3b82a4e8e
[As discussed in Mattermost](https://opensource.eff.org/eff-open-source/pl/yhtp4qu4zpfczm5wxmzxhndrto), our Apache test farm tests are failing because the CA certificate in the old version of boulder we have pinned expired over the weekend. This PR fixes that by running a local Pebble instance instead of an external boulder instance. * switch from external boulder to local pebble * add --http-01-port to run_acme_server
70 lines
3 KiB
Markdown
70 lines
3 KiB
Markdown
# letstest
|
|
Simple AWS testfarm scripts for certbot client testing
|
|
|
|
- Launches EC2 instances with a given list of AMIs for different distros
|
|
- Copies certbot repo and puts it on the instances
|
|
- Runs certbot tests (bash scripts) on all of these
|
|
- Logs execution and success/fail for debugging
|
|
|
|
## Notes
|
|
- Some AWS images, e.g. official CentOS and FreeBSD images
|
|
require acceptance of user terms on the AWS marketplace
|
|
website. This can't be automated.
|
|
- AWS EC2 has a default limit of 20 t2/t1 instances, if more
|
|
are needed, they need to be requested via online webform.
|
|
|
|
## Installation and configuration
|
|
These tests require Python 3, awscli, boto3, PyYAML, and fabric 2.0+. If you're
|
|
on a Debian based system, make sure you also have the python3-venv package
|
|
installed. If you have Python 3 installed, you can use requirements.txt to
|
|
create a virtual environment with a known set of dependencies by running:
|
|
```
|
|
python3 -m venv venv3
|
|
. ./venv3/bin/activate
|
|
pip install --requirement requirements.txt
|
|
```
|
|
|
|
You can then configure AWS credentials and create a key by running:
|
|
```
|
|
>aws configure --profile <profile name>
|
|
[interactive: enter secrets for IAM role]
|
|
>aws ec2 create-key-pair --profile <profile name> --key-name <key name> --query 'KeyMaterial' --output text > whatever/path/you/want.pem
|
|
```
|
|
Note: whatever you pick for `<key name>` will be shown to other users with AWS access.
|
|
|
|
When prompted for a default region name, enter: `us-east-1`.
|
|
|
|
## Usage
|
|
To run tests, activate the virtual environment you created above and run:
|
|
```
|
|
>python multitester.py targets.yaml /path/to/your/key.pem <profile name> scripts/<test to run>
|
|
```
|
|
|
|
You can only run up to two tests at once. The following error is often indicative of there being too many AWS instances running on our account:
|
|
```
|
|
NameError: name 'instances' is not defined
|
|
```
|
|
|
|
If you see this, you can run the following command to shut down all running instances:
|
|
```
|
|
aws ec2 terminate-instances --profile <profile name> --instance-ids $(aws ec2 describe-instances --profile <profile name> | grep <key name> | cut -f8)
|
|
```
|
|
|
|
It will take a minute for these instances to shut down and become available again. Running this will invalidate any in progress tests.
|
|
|
|
A folder named `letest-<timestamp>` is also created with a log file from each instance of the test and a file named "results" containing the output above.
|
|
The tests take quite a while to run.
|
|
|
|
## Scripts
|
|
Example scripts are in the 'scripts' directory, these are just bash scripts that have a few parameters passed
|
|
to them at runtime via environment variables. test_apache2.sh is a useful reference.
|
|
|
|
Note that the <pre>test_letsencrypt_auto_*</pre> scripts pull code from PyPI using the letsencrypt-auto script,
|
|
__not__ the local python code. test_apache2 runs the dev venv and does local tests.
|
|
|
|
See:
|
|
- https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html
|
|
- https://docs.aws.amazon.com/cli/latest/userguide/cli-ec2-keypairs.html
|
|
|
|
Main repos:
|
|
- https://github.com/letsencrypt/letsencrypt
|