On May 23, 2017 3:18 PM, "Mike Youngstrom" <youngm(a)gmail.com> wrote:

It was fun digging this thread out of the archives.

Thanks for keeping these features in the CC for so long. Now that we're
fully transitioned to Diego you can safely remove debug and console from
the CC along with all the other DEA stuff.

Thanks,
Mike

On Thu, Aug 29, 2013 at 1:12 AM, James Bayer <jbayer(a)gopivotal.com> wrote:

Mike,

Even though you proactively posted in mid-July, the runtime team was not
aware of any customer use of the console/debug ports because the post was
not remember when recent work was being done in that area. Mark Kropf, who
sets the priorities for the runtime team, will be looking into this
particular situation. The expectation is that teams should double-check on
the mailing lists before assuming it's OK to remove a feature and I'm sorry
that wasn't done in this case.

Engineering wanted to remove these features because we are preparing work
on a Task feature that enables custom commands like database migrations and
interactive shells to be used with an application droplet. The way it will
work is to provide users with a new Warden container with your droplet and
shell access. However, the task containers are not routable, so if you are
using the console/debug feature to using JMX / Debug on live routed
instances [1], then the task feature will not help you. Your other thread
completely explains why you want this capability, so thank you for the
proactive post in July. It was not disregarded intentionally.

[1] https://groups.google.com/a/cloudfoundry.org/forum/?fromgrou
ps#!searchin/vcap-dev/debug$20and$20console/vcap-dev/
R58HtrTb4fQ/2sIeXrVc-i0J

Thanks,

James

On Wed, Aug 28, 2013 at 8:19 PM, Mike Youngstrom <youngm(a)gmail.com> wrote:

After looking closer at the commits I think that we will be ok in our use
of console and debug ports. I think we can replicate the functionality in
our dea fork until there is a suitable replacement. However, if you were
to remove these features from the cloud controller that would be
devastating. Is the plan currently to remove this functionality from CC
and CF also? Would it possible we can keep the debug and console port code
in CC and cf long enough for a replacement to be ready to go?

Mike


On Wed, Aug 28, 2013 at 7:40 PM, Mike Youngstrom <youngm(a)gmail.com>
wrote:

Sorry about the last message. I was upset.

I would really appreciate hearing from someone on the DEA team to
explain what is going on with these DEA network changes and what the plan
going forward is to replace functionality like what the debug and console
ports provided.

Mike
On Aug 28, 2013 6:57 PM, "Mike Youngstrom" <youngm(a)gmail.com> wrote:

I knew you guys were going to do this!

https://github.com/cloudfoundry/dea_ng/commit/983bd6f9ee0ce9
91b853569f2f2cb27bb5c5f000

https://github.com/cloudfoundry/dea_ng/commit/a548ea0ff1c72c
a22f2daba32bfe014419e4493e

We were quite dependent upon these ports being available to apps. I
tried to make our use of these ports known: https://groups.google.c
om/a/cloudfoundry.org/forum/?fromgroups#!searchin/vcap-dev/d
ebug$20and$20console/vcap-dev/R58HtrTb4fQ/2sIeXrVc-i0J

Do we have an ETA of a replacement? Is there any hope of getting these
commits reverted until there is at least a solid plan/timetable to replace
them?

Mike

To unsubscribe from this group and stop receiving emails from it, send an
email to vcap-dev+unsubscribe(a)cloudfoundry.org.

--
Thank you,

James Bayer

To unsubscribe from this group and stop receiving emails from it, send an
email to vcap-dev+unsubscribe(a)cloudfoundry.org.