Comment 18 for bug 1175211

Jack, that problem could be solved by including multiple DNS names that map to the same internal IP. Only one name will be sent as the hostname but both names can be resolved in DNS. Essentially, the 10-10-20-5.openstacklocal name will always map to the IP regardless.

Could the global defaut for use_port_name_for_host_name be overridden on a network-by-network basis?

What happens if the nova display name doesn't qualify as an allowable dns name because of some mismatch in constraints. Should we define a mapping that will map any valid nova display name to a valid dns name?

Second, what is this about duplicates? Is the nova display name not constrained to be unique? If someone decides to turn on use_port_name_for_host_name and has duplicate display names on the same network what should be done?

In my opinion, we need to resolve these questions. Some of you may not like the idea of using nova display names as DNS names but end users want it. They don't want to have to name their instances twice and they want to be able to get to their instances by name using dns.

This should be designed in a blueprint.