Re: [Openstack] private network issue ( kola-ansible pike/stable deployment )

2018-04-08 Thread s serge
Hello, Thanks, The problem was related to MTU. Actually, I have another installation which is configured to set 1450(1500 - 50 VxLAN header length) for guest VM interfaces. That setup runs in 'regular' network environments with 1500 MTU on host interfaces and use linuxbridge. There is a

Re: [Openstack] private network issue ( kola-ansible pike/stable deployment )

2018-04-06 Thread Bernd Bausch
So the situation is: * VM1 has a floating IP and can be reached via floating IP * VM1 can ping VM2 * VM2 can't ssh VM2 Useful additional information you may have gathered already: * Does the ssh client issue any error message, and which? * Is an sshd running on VM2? * If yes, any

Re: [Openstack] private network issue ( kola-ansible pike/stable deployment )

2018-04-06 Thread Brian Haley
On 04/06/2018 01:28 PM, s serge wrote: Hello, I'm evaluating an installation and everything from networking side was looking good until I tried to reach a VM host via private network from another VM via ssh. In short: 1. Spawn a VM 2. Associate a floating IP 3. Logon to VM via ssh on public

Re: [Openstack] private network issue ( kola-ansible pike/stable deployment )

2018-04-06 Thread s serge
I'm sorry, some corrections, p.5 and p.6 should be: 5. From 1st VM try to reach the second VM(p.4) via ssh private network IP - FAIL. 6. ICMP from 1st VM to second(p.4) IP via private network works well. 06.04.2018, 20:42, "s serge" : > Hello, > > I'm evaluating an

[Openstack] private network issue ( kola-ansible pike/stable deployment )

2018-04-06 Thread s serge
Hello, I'm evaluating an installation and everything from networking side was looking good until I tried to reach a VM host via private network from another VM via ssh. In short: 1. Spawn a VM 2. Associate a floating IP 3. Logon to VM via ssh on public network 4. Spawn another VM 5. Try to