Hi Jason,
Thank you for the feedback.

Yes, I believe that's very true and would generally be the case with
production deployments. Let me add a note to the slide to include this as
well.

I read up on the direct container networking initiative and it's quite
interesting to see overlays in action in this context. :-)

Thanks
Moiz

------------------------------
From: jsherron(a)pivotal.io
Date: Tue, 23 Aug 2016 18:31:58 +0000
To: cf-dev(a)lists.cloudfoundry.org
Subject: [cf-dev] Re: CF Routing Use Cases


Hi Moiz,

Looks good overall.

My only minor clarification is that the HAProxy configuration that you've
shown is only one way to set up CF, and not necessarily what people use in
production. For example, on slide 8, the outbound NAT function might be an
AWS NAT instance or service separate from HAProxy. [1] The flow you've
drawn is still correct, it just might traverse a discrete component. (And
more generally, load balancing is often delegated up to a hardware
component like an F5 appliance.)

Beyond GoRouter, we're working on an OSS project to enable direct
container networking. [2] Deepa Kalani from Plumgrid worked with on it for
a period, too.

1 - https://docs.cloudfoundry.org/concepts/security.html
2 -
https://www.cloudfoundry.org/vision-future-container-networking-cloud-foundry/


On Sun, Aug 21, 2016 at 9:25 PM Moiz Arif <moizarif2002(a)hotmail.com>
wrote:

Hi All,

I have put together a slide deck explaining a few routing use cases based
on my understanding of the traffic flows in Cloud Foundry.

Please feel free to point out any missing/erroneous flows in the deck. So,
that we can make this deck a good learning experience for users new to CF.
Your feedback will be greatly appreciated :-)

Thanks
Moiz Arif