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.

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

elastic_ip documentation #268

Open
smaftoul opened this issue Mar 28, 2013 · 3 comments
Open

elastic_ip documentation #268

smaftoul opened this issue Mar 28, 2013 · 3 comments

Comments

@smaftoul
Copy link

I found some reference in issues and also had a look at elastic_ip.rb, but I'm not sure I understand how it works, and it's not documented.

I've tried:
cloud(:ec2).auto_elastic_ip 'xxx.xxx.xxx.xxx' in a facet that has only 1 instance, but I had some errors and the host didn't bootstrap (I can create an issue especially for this if you want to)

Also, looking at the code, issues and PRs I found an auto_elastic_ip 'first' , but I'm not sure how it works.

Is there somewhere some documention about this I missed ?

@UncleTallest
Copy link
Contributor

Okay, when I wrote the elastic ip code I had envisioned being able to use auto_elastic_ip 'first' to be able to just pull the first available address (or create a new eip if none are currently available) and use it when called this way. However, after looking through the code this morning I realized that it needs a method and trigger for that to be able to function as intended. For now, replace your code with

cloud(:ec2).elastic_ip 'xxx.xxx.xxx.xxx'

I will look into adding the missing bits this afternoon. This little feature was intended to obviate the need to know the 'actual' elastic ip ahead of time.

@UncleTallest
Copy link
Contributor

As additional information, the keyword 'first' is implied with .auto_elastic_ip so, at present, is unneeded when using the .auto_elastic_ip form. it's just not firing anything when you call it presently. Check back around 4pm CDT and I should, at least, have a pull request in waiting to address that.

@UncleTallest
Copy link
Contributor

Obviously I didn't get to it in time to finish when I specified above; the death of a drive can cause no end of grief. I'll have something for you once I get my system back to it's previous state and can actually work without interruptions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants