From 4aff0fb3f718ee0e55f39f5d0663feb22a14e9a3 Mon Sep 17 00:00:00 2001 From: Robert Collins 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 --- nova-compute-instance.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'nova-compute-instance.yaml') diff --git a/nova-compute-instance.yaml b/nova-compute-instance.yaml index 3abd3216..4b6a8a05 100644 --- a/nova-compute-instance.yaml +++ b/nova-compute-instance.yaml @@ -90,7 +90,7 @@ Resources: Ref: ComputeUser NovaCompute0CompletionCondition: Type: AWS::CloudFormation::WaitCondition - DependsOn: notcompute + DependsOn: notCompute0 Properties: Handle: {Ref: NovaCompute0CompletionHandle} Count: '1' -- cgit 1.2.3-korg