They might be not perfect but from my little experience they are able to
forward traffic and do SNAT/DNAT without too many issues.
If your deployment is failing to properly configure routing, you should be
getting errors in the l3 agent logs - sharing them might help.
Trying to ping the internal
Hello Pedro,
Neutron has some (limited) capabilities for injecting static routes into
instances.
You can try whether the subnet's host_routes attribute [1] can satisfy your
requirement.
Routes can however be specified only in the form destination CIDR/next hop.
Note: the host_routes option
Good morning Sam,
As you say, your requirement cannot be satisfied today. The option you
mention provided a nice workaround but did not fully solve your problem.
I think in order to satisfy it Neutron could either:
1) Specify this on a per-network setting in Neutron
2) Enable VIF usage tracking
The comment from Kris is correct.
In the official openstack guide I believe it is stated to remove any
address from the interface attached to br-ex (sudo ip addr del dev
), not to assign it 0.0.0.0
If the guide says otherwise please open a bug against the relevant doc
project.
Salvatore
On
Senior Linux Systems Engineer
GoDaddy, LLC.
From: Salvatore Orlando salv.orla...@gmail.com
Date: Tuesday, August 25, 2015 at 4:33 PM
To: Assaf Muller amul...@redhat.com
Cc: openstack-operators@lists.openstack.org
openstack-operators@lists.openstack.org
Subject: Re: [Openstack-operators
As the specification linked by Assaf has without doubt value for operators,
I think the drivers team might consider it for inclusion in the Liberty
release.
Unfortunately the specification and the patch have not received many
reviews, but can still be sorted, especially considering that the
.
I am able to ssh to the same machine with the floating IP outside
Openstack but internally it doesn’t seem to work. My goal here is to ssh
within an instance using the floating IP.
Thank you,
Aishwarya
*From:* Salvatore Orlando [mailto:salv.orla...@gmail.com]
*Sent:* Friday, July
Why are you focusing on authentication issues when it seems you have either
a sshd config issue or a connectivity problem?
Indeed your ssh handshake is stopping quite early - see below:
debug1: Connecting to 192.168.1.250 [192.168.1.250] port 22.
debug1: Connection established.
debug1: Enabling
hope I got your question right!
Regards
2015-07-23 16:58 GMT+02:00 Salvatore Orlando salv.orla...@gmail.com:
When you manually setup IP addressing on the VMs, are they able to ping
each other?
The issue you are describing is compatible with a scenario where both the
dhcp agent and the l3
