Re: Proposal (v2) for Service Discovery within Elastic Clusters

Amit Kumar Gupta

Hey Nic,

No, this is service discovery between system components. There would be a
CC in the management tier and a Diego BBS in an elastic cluster. Currently
these things talk to each other over Consul DNS because their Consul agents
all talk to the same Consul clusters. In the EC model, they will be
separate deployments with separate Consul clusters, possibly in separate
datacenters. But somehow they still need to discover each other. That's
what this proposal is about.

Not about app/container-to-container discovery.


On Wed, Jun 15, 2016 at 4:48 AM, Dr Nic Williams <drnicwilliams(a)>

I am sorry if I've misread or am missing some previous context - who/what
is the target audience for the proposal?

Is this something for apps running on CF - a service discovery experience
that is exposed thru to apps instead of/in leui of $VCAP_SERVICES? And then
my service brokers can dynamically update credentials or host:port
information to bound apps?


On Wed, Jun 15, 2016 at 3:04 PM +1000, "Amit Gupta" <agupta(a)>

Sorry about that, here's the link:

On Tue, Jun 14, 2016 at 9:41 PM, Gwenn Etourneau <getourneau(a)>

I think for forget the link ??

On Wed, Jun 15, 2016 at 1:09 PM, Amit Gupta <agupta(a)> wrote:

Hi all,

A while back, the Infrastructure team sent out a proposal for how to
implement service discovery between elastic clusters, as part of the
elastic clusters feature narrative. We have a second revision to the
proposal [0], which includes contextual links to previous work (the
original elastic clusters feature narrative, the previous service discovery
proposal, etc.).

This proposal is open for comment to anyone. Feedback is eagerly
solicited from anyone in the Cloud Foundry community, especially users of
and contributors to components that may be affected by this proposal.

Amit, CF Infrastructure PM

Join to automatically receive all group messages.