Re: vcap.component.discover in 233


Matthew Sykes <matthew.sykes@...>
 

For the DEA's, I think it was removed here [1] with the removal of
`vcap/component`. For health manager, I believe it was removed here [2]
when the `cfcomponent` dependency was removed.

In both cases, it was part of a move away from /varz to the collector and a
change from using nats for discovery to consul.

[1]:
https://github.com/cloudfoundry/dea_ng/commit/57581eef6532d87f736145ae4005880e009cf956
[2]:
https://github.com/cloudfoundry/hm9000/commit/7c343033a598b891193ee12278d92b786a35697f

On Tue, Apr 12, 2016 at 3:44 PM, Matt Cholick <cholick(a)gmail.com> wrote:

We recently upgrade from 228 to 233. Since then, one thing I'm seeing is
that neither DEA nor HM9000 is responding to a vcap.component.discover on
nats. Is this expected? I've dug a bit and haven't found a commit yet.
Wondering if the bug is in our environment/config or our expectations.

CloudController and etc are examples of some things that still respond to
this request.

-Matt Cholick

--
Matthew Sykes
matthew.sykes(a)gmail.com

Join cf-dev@lists.cloudfoundry.org to automatically receive all group messages.