Ephemeral runners for dev purposes #382
Merged
Conversation
This file contains 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
|
@baumstern Would you like to give an eye on this if you have any spare time? Thank you in advance! |
vplasencia
approved these changes
Feb 19, 2024
0xjei
approved these changes
Feb 20, 2024
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.
Description
With this PR you can trigger a workflow that deploys bandada on an ephemeral EC2 instance. From the moment you launch the instance through to its (auto)termination, the uptime is 6h. Each user has the option to spawn only one running instance, regardless of the deployment branch; there is also the possibility to re-deploy a newer version. In this scenario the old instance is destroyed, and a new one is launched.
The instance' s IP address appears during the workflow execution, allowing access to bandada via a web browser and/or connecting to the instance via SSH. VPN access is required for both cases (to receive the SSH key, please DM me).
Please keep in mind that bandada deployment takes between 20-30' after workflow execution and the ephemeral instance specs consist of 2vCPUS, 8GB of RAM and 32G HDD.
The workflow is scheduled to execute every 6h in order to terminate any instances that hung for any reason.
Related Issue
No
Does this introduce a breaking change?
Other information
Not available