From e3530a06c4d84e101e07bbe22075a0e2b3a72086 Mon Sep 17 00:00:00 2001
From: Mike Milner <mike.milner@canonical.com>
Date: Thu, 23 Feb 2012 15:13:51 -0400
Subject: Include launch_index when creating instances.

Fixes bug 934534.

The launch_index column in the database is used as the ami-launch-index value
provided by the metadata service.

If launch_index is not specified it defaults to 1. This is incorrect for the
single instance case (should be 0) and doesn't correctly handle multi-instance
starts.

This branch changes the default launch_index to 0 (to handle the single
instance case) and adds the launch_index in the schedulers for multi-instance
starts.

Change-Id: Ifc45abf4cd9f50f732ba4a4b68c0a6242a6c9710
---
 Authors | 1 +
 1 file changed, 1 insertion(+)

(limited to 'Authors')

diff --git a/Authors b/Authors
index ec0e28b06..24595be6c 100644
--- a/Authors
+++ b/Authors
@@ -121,6 +121,7 @@ Matthew Hooker <matt@cloudscaling.com>
 Michael Gundlach <michael.gundlach@rackspace.com>
 Michael Still <mikal@stillhq.com>
 Mike Lundy <mike@pistoncloud.com>
+Mike Milner <mike.milner@canonical.com>
 Mike Pittaro <mikeyp@lahondaresearch.org>
 Mike Scherbakov <mihgen@gmail.com>
 Mikyung Kang <mkkang@isi.edu>
-- 
cgit