Rossella Sblendido
On 06/17/2015 07:26 PM, Adam Spiers wrote:
Rossella Sblendido
wrote: On 06/17/2015 02:38 PM, Eugen Block wrote:
thank you very much for your response. The steps you describe were already realized, we have a router that enables communication to the floating network, a floating IP is assigned to the instance (in Horizon or CLI) and it is possible to ping another instance in this network. But the VM itself has no IP assigned to eth0, when I call ifconfig there is no IP. I have to login to the VM and manually change the network settings and assign the floating IP I created in the previous step. This seems not very practical. I would assume that the same floating IP address should be assigned during VM-creation. But obviously this is not the case, am I right?
It's OK that the VM has no floating IP assigned to its eth0. It's by design. You don't need to manually assign the IP to the VM, floating IP are handled by Neutron.
But the VM's eth0 still needs an IP, right? Otherwise the VM's kernel has no way of communicating over IP. So it has to be configured via DHCP. It sounds to me like your VM's eth0 isn't configured to use DHCP.
The VM gets its private IP assigned to eth0. This is configured by dnsmasq whose config file is managed by the DHCP agent. The question was about floating IPs, those addresses are not assigned to the VMs interface. Floating IPs are managed only in the network node, they are assigned to a virtual interface that lives in the router namespace. They are NAT translated before they reach the compute nodes. Hope it's more clear now.
Sure. But Eugen said:
But the VM itself has no IP assigned to eth0, when I call ifconfig there is no IP.
so I still think his VM has an issue with its DHCP not working, because it doesn't even have a private IP. -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org