-
Notifications
You must be signed in to change notification settings - Fork 68
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
Feature/aws setup - [WIP] #523
base: 1.0.0x
Are you sure you want to change the base?
Conversation
…ta/mist into feature/aws_setup
[feature/aws_setup] Fix dependency on default VPC and avoid recreating ingress rule.
Hi @dos65
I have kept the conf folder same as present in the release, just modified the context to pick up Any pointers? |
Could you please show your context.conf here? I think there might be some issues with that. |
Hi @blvp I am using following config:
and using 20func.conf as follows:
This is creating the function correctly and picking up the required context as well but fails on triggering the function with above error. |
Thank you. I will keep you in the loop. Also, could you please join gitter, so we communicate there istead of PR :) |
Yes @blvp! Thanks |
This is working implementation of built-in integration with EMR. Cluster configuration may be placed into context settings(examples) and mist can dynamically spawn EMR-clusters.
This requires introduces new mini-submodules:
agent
- simple application for running on EMR master node to guarantee shutdown cluster in case if mist instance was stoppedaws-init-setup
- performs initial AWS environment setup(creates if necessary roles, security groups, ssh keys) + generates mist config with this informationThis branch is ready for preview and already published here + cloudformation template.
What's left:
launcher-settings
section and allow contexts to use themmanual-launcher
- the similar like we have for workers