|
|---|
Confidence Level Moderate This article includes input from several JPLers. Multiple subject matter experts can indicate that a page is more frequently reviewed and updated.This guide describes how to create an auto-scaling fleet queue within HySDS.
Log into the Mozart instance and navigate to the sds config file.
vi ~/.sds/config
Add an entry for your new auto-scaling queue within the config file following this format:
-QUEUE_NAME: <YOUR_QUEUE_NAME>
INSTANCE_TYPES: -<DESIRED_AWS_INSTANCE_TYPES>
e.g.- QUEUE_NAME: aria-standard_product-enumerator INSTANCE_TYPES: - r4.8xlarge - r4.16xlarge - r5a.large
3. Stop the Mozart instance. Note that active jobs will be lost.
sds stop mozart -f
4. Update the Mozart instance. This will rewrite the supervisord.conf on Mozart to include the syncer
scripts for your new queues/ASGs so that autoscaling can kick in.
sds update mozart -f
5. Propagate custom settings.
fab -f ~/.sds/cluster.py -R mozart,factotum update_aria_packages
6. Creates code-config bundles for all ASG’s.
sds ship
7. Restart Mozart.
sds start mozart -f
8. Create the ASG.
sds cloud asg create
9. Go to the AWS console and confirm the ASG was created by selecting the ASG dashboard. Your queue should appear on this dashboard. Make sure to set the desired and maximum number of instances for this ASG.
Troubleshooting: Reference your ASG sync log for more insight:
e.g.
tail -f ~/mozart/log/sync_ec2_target_tracking_metric-aria-standard_product-enumerator.log
|
Anyone can join our public Slack channel to learn more about HySDS. JPL employees can join #HySDS-Community
|
JPLers can also ask HySDS questions at Stack Overflow Enterprise
|
Have Questions? Ask a HySDS Developer:
🚀 Page Information: |
|---|
Was this page useful? |
Contribution History:
|
Subject Matter Expert: |
Find an Error? Is this document outdated or inaccurate? Please contact the assigned Page Maintainer: |
