Closed fmanco closed 11 years ago
If you have one working fine without it, it means that it is not necessary ! Logically speaking, it should be binded to 0.0.0.0 if it's a multinode install (and 127.0.0.1 if it's a single node install)
I will investigate this further more and thank you for your contribution :)
Found the problem. I completely forgot that on the setup that is failing I am also run nova-compute on the controller node. That's why I need to bind to 0.0.0.0
. On the controller node 127.0.0.1
is fine.
And on the compute node ? Does it need to bind to 0.0.0.0 ?
2013/4/15 Filipe Manco notifications@github.com
Found the problem. I completely forgot that on the setup that is failing I am also run nova-compute on the controller node. That's why I need to bind to 0.0.0.0. On the controller node 127.0.0.1 is fine.
— Reply to this email directly or view it on GitHubhttps://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/pull/16#issuecomment-16412716 .
Bilel Msekni | IT Engineer Mobile: +33 6 49 52 42 17
My last comment is wrong. I should have tested this a little further before comment, sory.
Now I tested this with the following setup
The one that needs to bind to 0.0.0.0 is the controller node. That's because (AFAIK) the quantum metadata agent on the network node needs to connect to the nova metadata server on the controller node. For the compute node it doesn't really matter because if you check the LISTEN sockets you don't see any on 8775.
So I think you can in fact merge my pull request.
Filipe Manco http://about.me/fmanco
2013/4/16 SkiBLE notifications@github.com
And on the compute node ? Does it need to bind to 0.0.0.0 ?
2013/4/15 Filipe Manco notifications@github.com
Found the problem. I completely forgot that on the setup that is failing I am also run nova-compute on the controller node. That's why I need to bind to 0.0.0.0. On the controller node 127.0.0.1 is fine.
— Reply to this email directly or view it on GitHub< https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/pull/16#issuecomment-16412716>
.
Best regards,
Bilel Msekni | IT Engineer Mobile: +33 6 49 52 42 17
— Reply to this email directly or view it on GitHubhttps://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/pull/16#issuecomment-16428176 .
Can you please correct things out and send the merge request. Once you have closed it it's gone actually :)
regards, Bilel
2013/4/16 Filipe Manco notifications@github.com
My last comment is wrong. I should have tested this a little further before comment, sory.
Now I tested this with the following setup
- 1 controller node
- 1 compute node
- 1 network node
The one that needs to bind to 0.0.0.0 is the controller node. That's because (AFAIK) the quantum metadata agent on the network node needs to connect to the nova metadata server on the controller node. For the compute node it doesn't really matter because if you check the LISTEN sockets you don't see any on 8775.
So I think you can in fact merge my pull request.
Filipe Manco http://about.me/fmanco
2013/4/16 SkiBLE notifications@github.com
And on the compute node ? Does it need to bind to 0.0.0.0 ?
2013/4/15 Filipe Manco notifications@github.com
Found the problem. I completely forgot that on the setup that is failing I am also run nova-compute on the controller node. That's why I need to bind to 0.0.0.0. On the controller node 127.0.0.1 is fine.
— Reply to this email directly or view it on GitHub<
https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/pull/16#issuecomment-16412716>
.
Best regards,
Bilel Msekni | IT Engineer Mobile: +33 6 49 52 42 17
— Reply to this email directly or view it on GitHub< https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/pull/16#issuecomment-16428176>
.
— Reply to this email directly or view it on GitHubhttps://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/pull/16#issuecomment-16436376 .
Bilel Msekni | IT Engineer Mobile: +33 6 49 52 42 17
I reopened. Think you can merge now.
Please anyone can confirm this is necessary.
I have a setup that only works this way and other that works fine without this. Any clues?