Re: Documents about multiple app ports


Mike Youngstrom
 

I'm not a member of the teams. But from what I recall, around the time
this issue was getting finished up and support in the CLI was being
considered, some usability problems in the API became apparent when looking
at it from the CLI's perspective. At the same time the container
networking project started to pick up steam and I think given the overlap
between container networking regarding container listening ports coupled
with the API problems discovered as part of the CLI work the decision was
made to put the work on hold until container networking matured more and
revisit the feature and APIs then.

You might be able to piece together some info from the CLI proposal
document [0]. Hope that helps.

Mike

[0]
https://docs.google.com/document/d/1SfwaQ1hnngfopXC_Q24cT6lbo0yFwvbAbPcCPEHeNPY/edit#

On Fri, Mar 24, 2017 at 6:23 AM, Noburou TANIGUCHI <dev(a)nota.m001.jp> wrote:

Thank you very much for the response, Zach,

I would love to hear about how and why you wish to use multiple ports to
help inform how we replace this.
I've heard it multiple times from our users who wanted to migrate their
existing application(s) onto Cloud Foundry that they need to use multiple
ports with an app for easier migration.

Now I know it's experimental. But it seems working completely well as far
as
I have tested. So my next question is "why will you cease to support this
(well-working) feature? Is there any issue / problem with it?"


Zach Robinson wrote
Hey Noburou,

The multiple app ports were introduced as an experimental feature. I
believe we do not intend to continue supporting them in their current
incarnation, and to not currently have a concrete replacement.

I would love to hear about how and why you wish to use multiple ports to
help inform how we replace this.

Thanks,
Zach Robinson
CAPI PM




-----
I'm not a ...
Noburou TANIGUCHI
--
View this message in context: http://cf-dev.70369.x6.nabble.
com/Documents-about-multiple-app-ports-tp6610p6638.html
Sent from the CF Dev mailing list archive at Nabble.com.

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