Skip to content
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.

Sign up for GitHub

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

Jump to bottom

elasticsearch_autoscale jobs currently using static IP allocation, but should be using dynamic IP allocation ? #187

Open
fbonelle opened this issue Sep 28, 2015 · 1 comment
Open

elasticsearch_autoscale jobs currently using static IP allocation, but should be using dynamic IP allocation ? #187

fbonelle opened this issue Sep 28, 2015 · 1 comment

Comments

@fbonelle
Copy link
Contributor

Hi,

Why elasticsearch_autoscale jobs are using static IP? As I understand this job, it's used to increase the number of elasticsearch nodes easily. Parser nodes are using bosh dynamic allocation and it makes it easier to increase the number of jobs.

Thanks
@fbonelle fbonelle changed the title elasticsearch_autoscale jobs using static IP elasticsearch_autoscale jobs currently using static IP, but should be using dynamic IP allocation ? Sep 28, 2015
@fbonelle fbonelle changed the title elasticsearch_autoscale jobs currently using static IP, but should be using dynamic IP allocation ? elasticsearch_autoscale jobs currently using static IP allocation, but should be using dynamic IP allocation ? Sep 28, 2015
@dpb587
Copy link
Contributor

dpb587 commented Oct 5, 2015

I don't think there's a particular reason - those sample templates were composed from some of our original test deployments a long time ago. I guess it depends on your deployment strategies as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dpb587 @fbonelle