Multi-Boot Instance Naming

Registered by Brian Waldon on 2012-10-17

Based on this bug https://bugs.launchpad.net/nova/+bug/1054212:

When creating more than one instance in the scope of a single API call, Nova should automatically do something to make sure that the host names are unique. Not doing so effectively makes the min/max options useless for anyone who wants to add their VMs into a DNS domain.

Blueprint information

Status:
Complete
Approver:
Vish Ishaya
Priority:
Medium
Drafter:
Brian Waldon
Direction:
Needs approval
Assignee:
Russell Bryant
Definition:
Approved
Series goal:
Accepted for grizzly
Implementation:
Implemented
Milestone target:
milestone icon 2013.1
Started by
Russell Bryant on 2013-02-06
Completed by
Russell Bryant on 2013-02-18

Related branches

Sprints

Whiteboard

Random notes ...

You create multiple instances using the 'min_count' parameter to a server create request. This is part of the os-multiple-create extension.

Here's the interesting code in nova.compute.api:

            for i in xrange(num_instances):
                options = base_options.copy()
                instance = self.create_db_entry_for_new_instance(
   context, instance_type, image, options,
                        security_group, block_device_mapping)
                instances.append(instance)
                instance_uuids.append(instance['uuid'])

The fix would be to munge the display_name parameter before calling create_db_entry_for_new_instance()

Gerrit topic: https://review.openstack.org/#q,topic:bp/multi-boot-instance-naming,n,z

Addressed by: https://review.openstack.org/20443
    Naming unique hostname when booting multi instances.

Unassigned since the posted patch was abandoned. Anyone want to pick this up? --Russell

Addressed by: https://review.openstack.org/21386
    Assign unique names with os-multiple-create.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.