From 4aff0fb3f718ee0e55f39f5d0663feb22a14e9a3 Mon Sep 17 00:00:00 2001
From: Robert Collins <rbtcollins@hp.com>
Date: Wed, 29 Jan 2014 13:29:49 +1300
Subject: Prep work for a scalable control plane.

This is complete as far as it goes but it isn't enough to make running
a scaled out control plane actually work. Specifically, the constructs
to point at API hosts based on looking up a network address aren't
suirtable for scaled out - we need to be using the virtual IP or DNS
round robin or other such resilient configurations, but that is
largely / entirely orthogonal to making the template be ready for
scaling.

Change-Id: Ib9e6db5e7d5db84e4746afdabea046d2b8702bbb
---
 ssl-source.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'ssl-source.yaml')

diff --git a/ssl-source.yaml b/ssl-source.yaml
index 9127555a..4fdd0f3b 100644
--- a/ssl-source.yaml
+++ b/ssl-source.yaml
@@ -11,7 +11,7 @@ Parameters:
     Type: String
     NoEcho: true
 Resources:
-  notcomputeConfig:
+  notCompute0Config:
     Type: AWS::AutoScaling::LaunchConfiguration
     Metadata:
       stunnel:
-- 
cgit 1.2.3-korg