[Openstack-operators] Anyone using Project Calico for tenant networking?

Ned Rhudy (BLOOMBERG/ 731 LEX) erhudy at bloomberg.net
Sat Feb 6 14:40:47 UTC 2016

Thanks. Having read the documentation, I have one question about the network design. Basically, our use case specifies that instances be able to have a stable IP across terminations; effectively what we'd like to do is have a setup where both the fixed and floating IPs are routable outside the cluster. Any given instance should get a routable IP when it launches, but additionally be able to take a floating IP that would act as a stable endpoint for other things to reference. 

The Calico docs specify that you can create public/private IPv4 networks in Neutron, both with DHCP enabled. Is it possible to accomplish what I'm talking about by creating what are two public IPv4 subnets, one with DHCP enabled and one with DHCP disabled that would be used as the float pool? Or is this not possible?

----- Original Message -----
From: Neil Jerram <Neil.Jerram at metaswitch.com>
To: EDMUND RHUDY, openstack-operators at lists.openstack.org
At: 05-Feb-2016 14:11:34

On 05/02/16 19:03, Ned Rhudy (BLOOMBERG/ 731 LEX) wrote:
> I meant in a general sense of the networking technology that you're
> using for instance networking, not in the sense of per-tenant networks,
> though my wording was ambiguous. Part of our larger question centers
> around the viability of tying instances directly to a provider network.
> Being that we only operate a private cloud for internal consumption,
> doing so would have some attractive upsides; tenants clamor for the IP
> inside their instance to be the same as the floating IP that the outside
> world sees, but nobody's ever asked us about the ability to roll their
> own network topology, so we think we could probably do without that.

Cool, IMO that's a good match for what Calico provides.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160206/c2584849/attachment.html>

More information about the OpenStack-operators mailing list