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
AWS Deployment improvements #522
Conversation
metavar='DATA_ABSTRACTION_LAYER', action='store', | ||
help="Deploys containers on all running servers. Valid abstraction layers " \ | ||
"are DFS and S3") | ||
parser.add_argument('-w', '--worker_limit', type=int, action='store', default=0) |
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.
This is inconsistent with workers-only and deployment-credentials which use -, not _
aws/aws.py
Outdated
help="Deployed workers will connect to this master instead of deploying " \ | ||
"a new one on AWS.") | ||
parser.add_argument('--workers-only', action='store_true', default=False, | ||
help="When this flag is set we will only create and deploy to workers" ) |
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.
Why is workers only needed when we have master-ip?
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.
When creating new instances we don't need a master IP. So if you wanted to create 20 new instances without providing a master yet you would have to run aws.py -c 20 -m <random-unused-data>
. I felt that it was neater to have it as aws.py -c 20 --workers-only
, but i'm fine with removing it if you disagree.
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.
Ah okay, makes sense.
4b5d47b
to
9f782d1
Compare
Multiple improvements and changes to the AWS deployment script.
Added the following flags: