, 2014 3:50 PM
*To:* OpenStack Development Mailing List
*Subject:* [openstack-dev] [Neutron] About ports backing floating IPs
TL;DR;
I have been looking back at the API and found out that it's a bit weird
how floating IPs are mapped to ports. This might or might not be an issue,
and several
Logically, the port is really an alias for the external port of the router,
rather than being just detached. I'm not sure this adds much to the
discussion, but clearly that's where its traffic goes and is terminated.
From past experience (don't ask) weird things happen if you start creating
your
I am also perplexed about the ports backing floating ips. when plugin is
selected OVS or LB, the ip address belonging to a port backing that floating
ip is really set on VIF of 'qg-' , what is the port real action?
At 2014-01-15 07:50:36,Salvatore Orlando sorla...@nicira.com wrote:
TL;DR;
I have been looking back at the API and found out that it's a bit weird how
floating IPs are mapped to ports. This might or might not be an issue, and
several things can be done about it.
The rest of this post is a boring description of the problem and a possibly
even more boring list of
for all ports:
user can change the device_id and device owner easily, it will cause mess
in particularly for system ports, such as router interface and gateway
ports, dhcp ports etc.
dhcp port:
there is not point of updating its security groups, and I don't know the
effect when we update its Ip
...@nicira.com]
Sent: Tuesday, January 14, 2014 3:50 PM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [Neutron] About ports backing floating IPs
TL;DR;
I have been looking back at the API and found out that it's a bit weird how
floating IPs are mapped to ports. This might or might
