Thanks, Adam and Rossella.
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.
That was exactly my thought: if eth0 has no IP, how am I supposed to communicate with the VM? I tried an image which has DHCP enabled, still no success without changing it manually. I created that SLES11-SP3 image with virt-manager from scratch, it had an IP assigned in the admin network during installation. Interesting is: when I upload that image to glance and start a VM, it has no IP on eth0. I really don't get it at this point.
In your previous email you said you added a vlan in the compute node and connected it to the floating network > bridge. You don't need to do these steps. The compute node (unless you are using DVR) has no access to the external network. The network node has access to it and this is configured automatically by SUSE Cloud. You don't need to manually set up VLANs or linux bridges. VMs should be accessible if you assign them a floating IP and if you allow ssh in the security groups.
The network configuration is still the same, so maybe we'll have to
change it and give it a try.
But it is still not clear to me, how our network settings have to look
like. You say, I don't have to configure anything on the compute node,
so what do I have to do on control node? Before the current
installation we had a setup without VLAns on Compute Node and it
didn't work either. Now we are stuck and don't know what's right and
what's wrong in our environment. Any further help would be really
appreciated!
Regards,
Eugen
Zitat von Adam Spiers
Rossella Sblendido
wrote: On 06/17/2015 02:38 PM, Eugen Block wrote:
Hi Rossella,
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. -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org
-- Eugen Block voice : +49-40-559 51 75 NDE Netzdesign und -entwicklung AG fax : +49-40-559 51 77 Postfach 61 03 15 D-22423 Hamburg e-mail : eblock@nde.ag Vorsitzende des Aufsichtsrates: Angelika Mozdzen Sitz und Registergericht: Hamburg, HRB 90934 Vorstand: Jens-U. Mozdzen USt-IdNr. DE 814 013 983 -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org