Feature/aws setup - [WIP]#523
Open
dos65 wants to merge 36 commits into
Open
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? |
Contributor
|
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. |
Contributor
|
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 file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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-settingssection and allow contexts to use themmanual-launcher- the similar like we have for workers