Identical hostnames when creating >1 instance

Bug #1054212 reported by Phil Day on 2012-09-21
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Low
Brian Waldon

Bug Description

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.

When creating only instance its possible that the user wants to duplicate a name (they might be going on different networks and domains), but in the multiple instance case where all other parameters are identical its hard to see any advantage to having all instances start with the same hostname.

Ideally the suffix would be configurable in some way by the user, but that would require an API change or extension, rasing this to the status of a blueprint.

Changed in nova:
status: New → Confirmed
importance: Undecided → Wishlist
Michael Still (mikal) wrote :

This is true in the case where an instance with that name exists already as well, right?

Michael Still (mikal) on 2012-10-02
tags: added: canonistack ops
Michael Still (mikal) on 2012-10-16
Changed in nova:
importance: Wishlist → Low
Brian Waldon (bcwaldon) wrote :

I'm going to fix this as a blueprint since it seems like we're going to add new functionality to enable unique naming of instances.

Changed in nova:
assignee: nobody → Brian Waldon (bcwaldon)
status: Confirmed → Invalid
Kapil Thangavelu (hazmat) wrote :

for reference it appears the blueprint referenced is
https://blueprints.launchpad.net/nova/+spec/multi-boot-instance-naming

which appears to be unimplemented (ie bug is still valid).

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers