On Sun, Mar 29, 2015 at 6:45 AM, Kevin Benton <blak...@gmail.com> wrote:
> Does the decision about the floating IP have to be based on the use of the > private IP in the original destination, or could you get by with rules on > the L3 agent to avoid NAT just based on the destination being in a > configured set of CIDRs? > > If you could get by with the latter it would be a much simpler problem to > solve. However, I suspect you will want the former to be able to connect to > floating IPs internally as well. > That's one issue. Having systems like monitoring accessing both addresses. The other, like many other large organizations, is that we have a fairly large number of disjoint address spaces between all the groups accessing our cloud. So trying to create and maintain that sort of list, short of a routing protocol feed, is not easy. -Steve Wormley
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
