Include launch_index when creating instances.

Code Issues Proposed changes

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

This commit is contained in:

Mike Milner

2012年02月23日 15:13:51 -04:00

parent 7c4e31e639

commit e3530a06c4

8 changed files with 114 additions and 6 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

1
Authors

View File

@@ -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>

Include launch_index when creating instances.

1 Authors Unescape Escape View File

1
Authors

View File