From d0d41a185f03eed79b419bd1c1f20eb1e6a8399e Mon Sep 17 00:00:00 2001
From: Michael Marineau <michael.marineau@coreos.com>
Date: Tue, 15 Jul 2014 12:12:43 -0700
Subject: [PATCH] ami: configure etcd with public addresses

When I created the new AMI build host I just accepted the default
'wizard' security group which seems to have placed the host in a VPC.
There doesn't seem to be a way to fix this and as-is the build host
cannot access the private addresses on the test VMs it launches.
Switching to the public ones work fine though. Didn't notice this at
first because it is only a problem when etcd sends a redirect.
---
 oem/ami/test_ami.sh | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/oem/ami/test_ami.sh b/oem/ami/test_ami.sh
index 21bbfa5a80..7570f22539 100755
--- a/oem/ami/test_ami.sh
+++ b/oem/ami/test_ami.sh
@@ -96,8 +96,8 @@ userdata="#cloud-config
 coreos:
     etcd:
         discovery: $discovery
-        addr: \$private_ipv4:4001
-        peer-addr: \$private_ipv4:7001
+        addr: \$public_ipv4:4001
+        peer-addr: \$public_ipv4:7001
     units:
       - name: etcd.service
         command: start