Hi Dr. Nic,

The API call to say "yes I want a TCP route, but I don't care what
host:port it is?" was implemented in this story [1]
and looks like:
POST /v2/routes?generate_port=true
{
"domain_guid": "1234",
"space_guid": "1234"
}

The proposed cf CLI UX is specified in this story [2] and looks like:

$ cf create-route myspace example.com --random-port
Creating route for org scoen / space test as scoen(a)pivotal.io...
OK
Route example.com:5678 has been created

-Dieu
CF CAPI PM


[1] https://www.pivotaltracker.com/story/show/101460700
[2] https://www.pivotaltracker.com/story/show/101461184

On Tue, Feb 23, 2016 at 12:40 AM, Dr Nic Williams <drnic(a)starkandwayne.com>
wrote:

I understand that host:port is used for routing TCP requests.

What is the use case for some rare users of PWS or BlueMix or other large
CF deployments to expect that they can declare what port they should be
allowed to route?

Is this use case so common or important that we should allow it to leak
into CF?

Will we support the 95-99% case (afaict sorry), where users just want any
port (and to be able to look up what host:port they got - remembering that
there will be multiple tcp LBs due to port limitations)? It wasn't in the
demo - so its a question - what's the API call to say "yes I want a TCP
route, but I don't care what host:port it is?"