-
Notifications
You must be signed in to change notification settings - Fork 14
Disable EC2 Public Address lookup #1
Comments
Hi joshjdevl, the reason is that we were using Amazon EC2 instances to test out the storm-docker project and the public IP addresses of Amazon EC2 instances can only be accurately determined using the link you pasted. These 3 parts of the code should clarify things a little:
You do have a point though - this is redundant when the machines involved are not on Amazon EC2. I could work on a patch to turn this on/off but the earliest I can start doing that will be this coming Monday. Thanks for your interest in the storm-docker project =) |
Hi, Thanks, an option would be nice. When I run this on a non ec2 machine it fails to startup. For now, I have deleted the lines of code. |
This partially addresses #1 Disabling the running of the `curl` command is done by setting the `all_machines_are_ec2_instances` field in the `config/storm-setup.yaml` file to False or omitting the field. Signed-off-by: Pang Yan Han <[email protected]>
Hi joshjdevl, I've just committed a patch that partially resolves this issue: 2ca3a4f Simple set the
Tell me what you think of this change. |
Yes, this appears to work. Thanks! |
Is there a particular reason that when starting the storm cluster it is trying to access http://169.254.169.254/latest/meta-data/public-ipv4 ? This is the URL for EC2 instances to lookup their Public DNS address. Though why is it running automatically?
The text was updated successfully, but these errors were encountered: