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?
In the attached links I couldn't find any help for my other question
regarding VLANs. Is it possible to configure the bridge and/or the
vlan so that the connection remains after a reboot of the compute
node? Currently this is not the case, I have to call "brctl addif
<bridge> <VLAN-device>" after every reboot to enable SSH login. Isn't
there an easier way to establish this permanently?
Thanks!
Eugen
Zitat von Rossella Sblendido
On 06/16/2015 01:45 PM, Eugen Block wrote:
Hi everyone,
I'm working with SUSE OpenStack Cloud 5 and have a question regarding the network configuration. I'm not sure if this is the right mailing list, but I'll give it a try. We have a three node environment, 1 Admin node (SLES11-SP3),1 Control node (SLES11-SP3) and 1 Compute node (SLES12). After some problems we managed to set up a working cloud environment, except the network configuration is not quite clear yet. We deployed the Neutron barclamp with linuxbridge and have our physical network divided into VLANs. So the question is: how is the whole network setup supposed to be? What am I supposed to see on Control and/or Compute Node?
You can find details information here [1] .
If I understand the documentation correctly, I should be able to log into a running instance via ssh. But this only works, if we manually set up a vlan on the compute node and attach it to the corresponding bridge (floating network), but this configuration only exists until the next reboot. I don't want to ask too many questions, so I would be really happy if someone could explain to me, what I should see on the nodes. A similar question is here: https://forums.suse.com/showthread.php?6490-running-instances-in-external-VL....
I'm not very familiar with VLANs, bridges etc., so please don't answer to complicated for me ;-)
To be able to ssh in a VM from outside the cloud you have to assign a floating up to the VM and then ssh using the floating ip. You can find the right commands to use there [2]. You can also use horizon to do that. These are the basic operations:
1) create a router 2) set it as a gatway 3) connects the network that the VM belongs to to the router 4) create a floating IP 5) assign it to the VM
Make sure that the security group assigned to the VM allows TCP on port 22 otherwise ssh won't work.
cheers,
Rossella
Thanks a lot!
Best regards, Eugen
[1] http://docs.openstack.org/admin-guide-cloud/content/under_the_hood_linuxbrid... [2] http://docs.openstack.org/admin-guide-cloud/content/l3_workflow.html -- 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