Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: OpenStack: Dev

[Nova] hostname vs hostIP in live-migration

 

 

OpenStack dev RSS feed   Index | Next | Previous | View Threaded


hzwangpan at corp

Aug 20, 2012, 1:01 AM

Post #1 of 2 (78 views)
Permalink
[Nova] hostname vs hostIP in live-migration

Hi all,
I have a doubt about the configuration of live-migration, when we want to use the live-migration feature, we show change /etc/hosts on every host, so they can establish connection with each other by "hostname", if we don't of forget to do this, the live-migration will fail. and also I have look into the source code of nova, it uses hostname everywhere instead of hostIP.
So my questions are listed below,
1. Why nova use hostname instead of hostIP ?
2. If there are many compute Nodes, we should change the /etc/hosts on every node, and if we want to add one compute Node, we also need to change the /etc/hosts of every node, I think this isn't flexible or convenient, is there any good ideas? should I configure a DNS server instead of modifing the /etc/hosts?
3. I want to modify the source code to change the original implementation by add the hostIP to the table 'services' in nova database, so I can get the hostIP by querying this table using 'host' as the filter, then I needn't to modify the /etc/hosts or add a DNS server to support live-migration. is this a feasible plan?

Many Thanks,
Wangpan


_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack [at] lists
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp


marek.ruzicka at t-systems

Aug 20, 2012, 1:12 AM

Post #2 of 2 (78 views)
Permalink
Re: [Nova] hostname vs hostIP in live-migration [In reply to]

Hi Wangpan,

2.
We were dealing with same thing few weeks ago...
Solved it by running another instance of dnsmasq as dns resolver on our control-node.
As long as you have small environment as we do, it is pretty simple to keep one /etc/hosts up to date.

Regards,

Marek Ruzicka
System Engineer (Storage)
T-Systems Slovakia s.r.o.
www.t-systems.sk

-----Original Message-----
From: openstack-bounces+marek.ruzicka=t-systems.sk [at] lists [mailto:openstack-bounces+marek.ruzicka=t-systems.sk [at] lists] On Behalf Of Wangpan
Sent: 20. augusta 2012 10:02
To: openstack
Subject: [Openstack] [Nova] hostname vs hostIP in live-migration

Hi all,
I have a doubt about the configuration of live-migration, when we want to use the live-migration feature, we show change /etc/hosts on every host, so they can establish connection with each other by "hostname", if we don't of forget to do this, the live-migration will fail. and also I have look into the source code of nova, it uses hostname everywhere instead of hostIP.
So my questions are listed below,
1. Why nova use hostname instead of hostIP ?
2. If there are many compute Nodes, we should change the /etc/hosts on every node, and if we want to add one compute Node, we also need to change the /etc/hosts of every node, I think this isn't flexible or convenient, is there any good ideas? should I configure a DNS server instead of modifing the /etc/hosts?
3. I want to modify the source code to change the original implementation by add the hostIP to the table 'services' in nova database, so I can get the hostIP by querying this table using 'host' as the filter, then I needn't to modify the /etc/hosts or add a DNS server to support live-migration. is this a feasible plan?

Many Thanks,
Wangpan


_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack [at] lists
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack [at] lists
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp

OpenStack dev RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.