feat: use additional volume for upload logs #313
Merged
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.
d741e1b chore: vary base mount point for striped volume
I want to use this role to mount a volume on the uploaders too, so the base mount point may be
different.
I renamed the role to something a bit more specific that I think captures the purpose.
I've also taken out a role being applied to the playbook that formatted a disk if we were using AWS
as the provider. We will hopefully move to AWS soon, but for the time being this was causing a bit
of confusion and I don't think it will be used; we'll probably need the striped volume setup for AWS
too.
ed609e7 chore: apply retries for service restarts
I've seen these fail during deployments and unfortunately they will cause the workflow run to fail.
A simple restart should prevent the failure. These have been applied to other service restarts that
fail occasionally and they seem to work.
6f5d955 feat: use additional volume for upload logs
If we want to launch testnets with extended and verbose logging for uploads, we will run out of disk
space very quickly. For this reason, we will use an additional volume and have the upload logs
output here.