Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clusters-keeper: WORKERS_EC2_INSTANCES_ALLOWED_TYPE is not passing 16KB limit for EC2 instances #5290

Closed
2 of 3 tasks
Tracked by #950
sanderegg opened this issue Feb 1, 2024 · 1 comment
Closed
2 of 3 tasks
Tracked by #950
Assignees
Labels
High Priority a totally crucial bug/feature to be fixed asap
Milestone

Comments

@sanderegg
Copy link
Member

sanderegg commented Feb 1, 2024

When the primary machine is created via Clusters-Keeper, it passes a bunch of text via the EC2 User-Data field.
This field is limited to 16KB which is too small for what we use it for.
Currently that field contains a bash script which:

  • pre-pulls images
  • runs custom script as defined in PRIMARY_EC2_INSTANCES_ALLOWED_TYPES for the primary machine type
  • create a docker swarm
  • transmits a docker-compose file
  • start a docker-compose file with a bunch of ENV variables + among other WORKERS_EC2_INSTANCES_ALLOWED_TYPES which is typically huge

All in all the complete resulting text file is > 16KB and that is not sustainable.

Tasks

Preview Give feedback
@sanderegg sanderegg self-assigned this Feb 1, 2024
@sanderegg sanderegg transferred this issue from ITISFoundation/osparc-issues Feb 1, 2024
@sanderegg sanderegg added the High Priority a totally crucial bug/feature to be fixed asap label Feb 1, 2024
@sanderegg
Copy link
Member Author

fixed together with #5294

The new AMI allows to only call a pre-baked script that takes care of most of the work. only the pre-pull images have to be transfered, thus reducing the size by a huge amount.
In need even the docker-compose files could be pre-baked.

@sanderegg sanderegg added this to the Schoggilebe milestone Feb 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
High Priority a totally crucial bug/feature to be fixed asap
Projects
None yet
Development

No branches or pull requests

1 participant