Aws fastpath deploy #240
Open
Aws fastpath deploy #240
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This server was running out of memory trying to bring up the fastpath docker container. I changed the instance type from one with 0.5gb of ram to one with 1gb of ram
If you don't the first time you run this notebook it will crash with "permission required" whenever you try to run a docker command
Terraform Run Output 🤖Format and Style 🖌
|
| Pusher | @LDiazN |
| Action | pull_request |
| Environment | dev |
| Workflow | .github/workflows/check_terraform.yml |
| Last updated | Thu, 03 Jul 2025 14:25:55 GMT |
Ansible Run Output 🤖Ansible Playbook Recap 🔍Ansible playbook output 📖
|
| Pusher | @LDiazN |
| Action | pull_request |
| Working Directory | |
| Workflow | .github/workflows/check_ansible.yml |
| Last updated | Thu, 03 Jul 2025 14:27:27 GMT |
hellais
reviewed
Jun 27, 2025
| dest: "/opt/{{fastpath_user}}/backend" | ||
| # TODO Change to `master` when https://github.com/ooni/backend/pull/935 is merged | ||
| version: support-deploying-fastpath-as-docker-container | ||
| force: yes |
There was a problem hiding this comment.
It would be ideal if we did this using the same pattern as the reset of the services. That would be building the docker image upon each commit in backend automatically and then we do the deploy using the tag.
It otherwise makes it harder to test something in dev and then deploy it inside of prod.
What we would ideally like to do is make a build, tag a version, test it in dev and then when the test passes we can deploy it to prod.
Can you make changes to run this as part of the CD pipeline?
|
We are also missing another piece to get fastpath fully working and that is handling measurement upload. It's necessary to extract the api-uploader systemd unit and component over to fastpath (see: https://github.com/ooni/backend/blob/master/api/debian/ooni-api-uploader.timer). Other relevant docs are for these pieces are here: https://docs.ooni.org/backend/systemd-timers/#ooni-api-uploader-timer I guess we have 2 options on how to handle this:
|
|
I will probably go with 2, but I will address it in a follow up PR with that and setting up the access to s3 and clickhouse |
The previous version would crash when the docker was already running, this version will skip running the container if already present and will check for variations in configurations
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR will add an ansible role to deploy the fastpath as an EC2 isntance using Docker.
The ansible role will:
Known issues
For now this setup has an issue with the Docker installation where the docker role will try to reboot the SSH connection to apply docker group settings, but this seems to crash the next command:
There's also another issue where the Docker deployment fails because it can't create a network for the docker compose. This is fixed by manually rebooting the docker daemon:
systemctl restart docker(see https://stackoverflow.com/questions/54380847/failed-to-setup-ip-tables-unable-to-enable-nat-rule)To solve this issue we have to ensure that docker is rebooted before starting the docker compose
This should be solved by
devops/ansible/roles/fastpath/tasks/main.yml
Line 45 in 4b148c6
Update
After the last review I added the following features:
closes #239