-
Notifications
You must be signed in to change notification settings - Fork 27
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/use ssm (🚨change in private clusters) #6361
🎨Clusters keeper/use ssm (🚨change in private clusters) #6361
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #6361 +/- ##
=========================================
+ Coverage 84.5% 88.2% +3.6%
=========================================
Files 10 1507 +1497
Lines 214 62485 +62271
Branches 25 2070 +2045
=========================================
+ Hits 181 55140 +54959
- Misses 23 7025 +7002
- Partials 10 320 +310
Flags with carried forward coverage won't be shown. Click here to find out more.
|
be264e8
to
f72d38c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
read the description not the code, ask if I shall read through it (serious offer).
Also, kudos on going from the 16k limit to the 64k limit 🍡
f72d38c
to
3d2ed1b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Blocked until release is done
services/clusters-keeper/src/simcore_service_clusters_keeper/api/health.py
Show resolved
Hide resolved
services/clusters-keeper/src/simcore_service_clusters_keeper/api/health.py
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thx!
services/clusters-keeper/src/simcore_service_clusters_keeper/core/settings.py
Show resolved
Hide resolved
...ices/clusters-keeper/src/simcore_service_clusters_keeper/modules/clusters_management_core.py
Outdated
Show resolved
Hide resolved
services/clusters-keeper/src/simcore_service_clusters_keeper/constants.py
Show resolved
Hide resolved
3d2ed1b
to
8d03db6
Compare
Quality Gate failedFailed conditions |
What do these changes do?
Currently when private clusters are created, a new EC2 is created called the primary or manager instance. The current workflow is as follows:
All these custom bash scripts are passed to the EC2 as so-called UserData (special text that is run on start). The UserData is limited to 16 KB and we are hitting this limit.
This PR changes this behaviour by splitting the part in UserData and the part run via AWS SSM service:
AFTER:
In order to make this work, the clusters-keeper now waits for the EC2 to connect to the SSM server, and then send the SSM command. This might slightly reduce performances but is expected to be not noticeable.
NOTE:
NOTE2: This will allow to correctly setup graylog in computational clusters,
NOTE3: This will allow to correctly setup registry mirroring in computational clusters,
NOTE4: This will allow to add more machine types without breaking the limit,
Related issue/s
How to test
Dev-ops checklist
new ENV: