Disable Host feature may not work based on hostname #220

Closed
breu opened this Issue Mar 19, 2013 · 1 comment

1 participant

@breu

Moving this from rcbops/opencenter#445

@doublerr
https://privatecloudforums.rackspace.com/viewtopic.php?f=4&t=361

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.

@GeoKM
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-)

@breu breu was assigned Mar 19, 2013
@breu

Notes:

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.

http://docs.python.org/2/library/socket.html#socket.gethostname

@breu breu closed this Mar 19, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment