vagrant-aws icon indicating copy to clipboard operation
vagrant-aws copied to clipboard

Published 20 hours ago • verified publisher icon mitchellh

We want to attach existing elastic IPs!

Open mark-rushakoff opened this issue 11 years ago • 35 comments
trafficstars

There's @madhurranjan who opened PR #129 and seems to have implemented the feature. @vkojuharova is asking for this feature in Issue #178. @tonnydourado opened issue #166 about the elastic_ip option not being documented - I banged my head against that for a couple hours trying to figure out why assigning my desired elastic ip to aws.elastic_ip in my Vagrantfile wasn't working.

My project really wants to assign an existing elastic IP to a new Vagrant box too -- we're interested in spending some engineering time for a new pull request if that's what needed. We really don't want to have to install a fork of the vagrant-aws plugin to work side-by-side with other projects using the main implementation.

If sharing some of our engineering time won't help us get this feature onto master, then is there anything else we can do to help?

mark-rushakoff avatar Jan 08 '14 06:01 mark-rushakoff

+1

benfrye avatar Feb 20 '14 16:02 benfrye

+1

skyshard avatar Feb 20 '14 20:02 skyshard

+1

hyperfocus1338 avatar Feb 23 '14 10:02 hyperfocus1338

+1

p4w3l avatar Mar 06 '14 11:03 p4w3l

+1

njam avatar Mar 11 '14 17:03 njam

+2

tomaszdurka avatar Mar 11 '14 17:03 tomaszdurka

+1

unclespeedo avatar Mar 12 '14 02:03 unclespeedo

+1

jesseangell avatar Mar 17 '14 07:03 jesseangell

+1

ttsuchi avatar Apr 01 '14 04:04 ttsuchi

+1

dawogfather avatar Apr 10 '14 01:04 dawogfather

:+1:

loginx avatar Apr 14 '14 18:04 loginx

+1

seamusabshere avatar Apr 16 '14 15:04 seamusabshere

+1

rossmeissl avatar Apr 16 '14 15:04 rossmeissl

+1

24601 avatar Apr 24 '14 17:04 24601

what's the status on this?

cmosguy avatar May 14 '14 03:05 cmosguy

+1

dotmilk avatar May 17 '14 21:05 dotmilk

+1

darrylb-github avatar May 24 '14 14:05 darrylb-github

+1

ankushnarula avatar May 27 '14 13:05 ankushnarula

+1 please

joncourt avatar May 28 '14 01:05 joncourt

+1 help! :)

seanmcl avatar Jun 04 '14 00:06 seanmcl

+1

danilogbotelho avatar Jun 20 '14 15:06 danilogbotelho

Mark's comments sound exactly like the ticket I was about to create. Any chance of this happening @mitchellh ?

fletchowns avatar Jul 23 '14 23:07 fletchowns

Yes please! +1

doobiwan avatar Aug 07 '14 00:08 doobiwan

+1

ghost avatar Aug 13 '14 11:08 ghost

+1

dkinzer avatar Aug 26 '14 20:08 dkinzer

I'm willing to work on this but since #129 didn't get merged what's the likelihood that anyone's pull request will get merged? It would just be a big waste of time.

dkinzer avatar Aug 26 '14 20:08 dkinzer

I emailed @rtyler on Aug 5th asking about the open pull requests on this repo and specifically the elastic ip pulls, but I never got a response.

fletchowns avatar Aug 26 '14 23:08 fletchowns

+1

frank-u avatar Sep 01 '14 20:09 frank-u

+1

markcwhitfield avatar Nov 04 '14 15:11 markcwhitfield

I'd like to add my vote for this feature also. When I'm using AWS boxes I want to assign a "known" IP address. This must be a hugely useful feature for a lot of people, as indicated by the comment trail here.

Would anybody please be in a position to comment on this and if it is in the works or likely to be available soon?

The README.md seems misleading on elastic_ip, it states...

elastic_ip - Can be set to 'true', or to an existing Elastic IP address. If true, allocate a new Elastic IP address to the instance. If set to an existing Elastic IP address, assign the address to the instance.

I've tried to explicitly set the ip as suggested...

aws.elastic_ip = "A.B.C.D"

And the logs seem to infer it has been picked up, but the actual elastic IP being allocated is a brand new one.

Launching an instance with the following settings...
-- Elastic IP: A.B.C.D

For reference I'm using what I believe to be the latest released vagrant-aws...

vagrant-aws (0.5.0)

dbrimley avatar Nov 25 '14 12:11 dbrimley