Moving this from rcbops/opencenter#445
This is similar to the issue of how hostnames are leveraged in opencenter. The issue is that depending on the hostnames, openstack may store a different hostname (short vs. FQDN) than opencenter. In the case where they are different, disable host adventure will fail.
I think if Opencentre could check which type of data the openstack nova environment is using (ie. what appears in "nova-manage service list" and then use that value (short or FQDN) for all nova-manage commands that should fix it 8-)
OpenStack uses socket.gethostname() for the name of the node which isn't guaranteed to return the FQDN of the node so our code shouldn't use the FQDN when manipulating the nova services.
Use hostname instead of FQDN for manipulating service state