use FQDN for hostnames of services

[Christian Berendt]

at the moment a running service registers in the database using it's short hostname. i would prefer it to see the FQDN in the database to have an unique identifier for a host. the shortname of two hosts could be the same in a bigger enviroment working with several availability zones.

shortname could be used if the fqdn is not available on a system.

mysql> select host from services;
+--------+
| host |
+--------+
| os0007 |
| plum |
| plum |
| fig |
| fig |
+--------+
5 rows in set (0.01 sec)

[Christian Berendt (berendt)]

The parameter "host" in /etc/nova/nova.conf can be used to manually set the identifier of a host where a service is running on.

But I still would prefer to set the value to the FQDN and not to the shortname of a system by default. I don't want to add the parameter "host" to every /etc/nova/nova.conf.

[Christian Berendt (berendt)]

Using socket.getfqdn() looks good to me (http://docs.python.org/library/socket.html)

If socket.getfqdn() doesn't return the FQDN it fails back to socket.gethostname() (that's the state of the art in flags.py).

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/6556

[Thierry Carrez (ttx)]

Review was abandoned, would you consider reviving it ?

[Joe Gordon (jogo)]

This approach was attempted but caused some issues: please see https://review.openstack.org/#/c/24080/