Announcing support for TCP Routing


Shannon Coen
 

On behalf of the CF Routing team I invite you to bring your non-http
workloads to Cloud Foundry.

By deploying the Routing Release [1] alongside Cloud Foundry and the Diego
runtime backend, operators can enable developers to create TCP routes based
on reservable ports.

The developer UX for pushing an app and mapping a TCP route is as simple as
this:

cf p myapp -d tcp.bosh-lite.com --random-route

The response includes a port associated with the TCP route. Client requests
to these ports will be routed to applications running on CF through a
layer-4 protocol-agnostic routing tier.

The Routing Release is still very much a work in progress. We are focusing
on mitigating stale routing information in the event of network partition
with system components, and on streamlining the deployment workflow.

Please review our README for deployment instructions, give it a go. We are
looking forward to your feedback.

Thank you!

[1] https://github.com/cloudfoundry-incubator/cf-routing-release

Note:
- UDP protocols are not supported.
- Both HTTP and TCP routes will be directed to the same application port,
identified by environment variable $PORT. Support for multiple application
ports is coming soon.


Shannon Coen
Product Manager, Cloud Foundry
Pivotal, Inc.


Chris Sterling
 

Wow, this is great news! Congratulations, team!

Chris Sterling
chris.sterling(a)gmail.com
twitter: @csterwa
linkedin: http://www.linkedin.com/in/chrissterling

On Tue, May 10, 2016 at 6:28 PM, Shannon Coen <scoen(a)pivotal.io> wrote:

On behalf of the CF Routing team I invite you to bring your non-http
workloads to Cloud Foundry.

By deploying the Routing Release [1] alongside Cloud Foundry and the Diego
runtime backend, operators can enable developers to create TCP routes based
on reservable ports.

The developer UX for pushing an app and mapping a TCP route is as simple
as this:

cf p myapp -d tcp.bosh-lite.com --random-route

The response includes a port associated with the TCP route. Client
requests to these ports will be routed to applications running on CF
through a layer-4 protocol-agnostic routing tier.

The Routing Release is still very much a work in progress. We are focusing
on mitigating stale routing information in the event of network partition
with system components, and on streamlining the deployment workflow.

Please review our README for deployment instructions, give it a go. We are
looking forward to your feedback.

Thank you!

[1] https://github.com/cloudfoundry-incubator/cf-routing-release

Note:
- UDP protocols are not supported.
- Both HTTP and TCP routes will be directed to the same application port,
identified by environment variable $PORT. Support for multiple application
ports is coming soon.


Shannon Coen
Product Manager, Cloud Foundry
Pivotal, Inc.


Dr Nic Williams <drnicwilliams@...>
 

Great work finishing the end to end integration with the CLI etc!!

On Tue, May 10, 2016 at 6:54 PM -0700, "Chris Sterling" <chris.sterling(a)gmail.com> wrote:










Wow, this is great news! Congratulations, team!
Chris Sterling
chris.sterling(a)gmail.com
twitter: @csterwa
linkedin: http://www.linkedin.com/in/chrissterling

On Tue, May 10, 2016 at 6:28 PM, Shannon Coen <scoen(a)pivotal.io> wrote:
On behalf of the CF Routing team I invite you to bring your non-http workloads to Cloud Foundry.
By deploying the Routing Release [1] alongside Cloud Foundry and the Diego runtime backend, operators can enable developers to create TCP routes based on reservable ports. 
The developer UX for pushing an app and mapping a TCP route is as simple as this:
cf p myapp -d tcp.bosh-lite.com --random-route

The response includes a port associated with the TCP route. Client requests to these ports will be routed to applications running on CF through a layer-4 protocol-agnostic routing tier. 
The Routing Release is still very much a work in progress. We are focusing on mitigating stale routing information in the event of network partition with system components, and on streamlining the deployment workflow.
Please review our README for deployment instructions, give it a go. We are looking forward to your feedback. 
Thank you!
[1] https://github.com/cloudfoundry-incubator/cf-routing-release
Note: - UDP protocols are not supported. - Both HTTP and TCP routes will be directed to the same application port, identified by environment variable $PORT. Support for multiple application ports is coming soon.

Shannon CoenProduct Manager, Cloud FoundryPivotal, Inc.


Benjamin Black
 

Great work, everyone!

On May 10, 2016 18:29, "Shannon Coen" <scoen(a)pivotal.io> wrote:

On behalf of the CF Routing team I invite you to bring your non-http
workloads to Cloud Foundry.

By deploying the Routing Release [1] alongside Cloud Foundry and the Diego
runtime backend, operators can enable developers to create TCP routes based
on reservable ports.

The developer UX for pushing an app and mapping a TCP route is as simple
as this:

cf p myapp -d tcp.bosh-lite.com --random-route

The response includes a port associated with the TCP route. Client
requests to these ports will be routed to applications running on CF
through a layer-4 protocol-agnostic routing tier.

The Routing Release is still very much a work in progress. We are focusing
on mitigating stale routing information in the event of network partition
with system components, and on streamlining the deployment workflow.

Please review our README for deployment instructions, give it a go. We are
looking forward to your feedback.

Thank you!

[1] https://github.com/cloudfoundry-incubator/cf-routing-release

Note:
- UDP protocols are not supported.
- Both HTTP and TCP routes will be directed to the same application port,
identified by environment variable $PORT. Support for multiple application
ports is coming soon.


Shannon Coen
Product Manager, Cloud Foundry
Pivotal, Inc.


Onsi Fakhouri <ofakhouri@...>
 

Well done y'all! Huge milestone for CF and the routing team!

Onsi

On Tue, May 10, 2016 at 7:53 PM, Benjamin Black <bblack(a)pivotal.io> wrote:

Great work, everyone!
On May 10, 2016 18:29, "Shannon Coen" <scoen(a)pivotal.io> wrote:

On behalf of the CF Routing team I invite you to bring your non-http
workloads to Cloud Foundry.

By deploying the Routing Release [1] alongside Cloud Foundry and the
Diego runtime backend, operators can enable developers to create TCP routes
based on reservable ports.

The developer UX for pushing an app and mapping a TCP route is as simple
as this:

cf p myapp -d tcp.bosh-lite.com --random-route

The response includes a port associated with the TCP route. Client
requests to these ports will be routed to applications running on CF
through a layer-4 protocol-agnostic routing tier.

The Routing Release is still very much a work in progress. We are
focusing on mitigating stale routing information in the event of network
partition with system components, and on streamlining the deployment
workflow.

Please review our README for deployment instructions, give it a go. We
are looking forward to your feedback.

Thank you!

[1] https://github.com/cloudfoundry-incubator/cf-routing-release

Note:
- UDP protocols are not supported.
- Both HTTP and TCP routes will be directed to the same application port,
identified by environment variable $PORT. Support for multiple application
ports is coming soon.


Shannon Coen
Product Manager, Cloud Foundry
Pivotal, Inc.


Sam Ramji
 

And the crowd goes wild. Great news.

Looking forward to UDP support in the future for more IoT protocols.


*Sam* Ramji | sramji(a)cloudfoundry.org | +1-510-913-6495

On Tue, May 10, 2016 at 6:28 PM, Shannon Coen <scoen(a)pivotal.io> wrote:

On behalf of the CF Routing team I invite you to bring your non-http
workloads to Cloud Foundry.

By deploying the Routing Release [1] alongside Cloud Foundry and the Diego
runtime backend, operators can enable developers to create TCP routes based
on reservable ports.

The developer UX for pushing an app and mapping a TCP route is as simple
as this:

cf p myapp -d tcp.bosh-lite.com --random-route

The response includes a port associated with the TCP route. Client
requests to these ports will be routed to applications running on CF
through a layer-4 protocol-agnostic routing tier.

The Routing Release is still very much a work in progress. We are focusing
on mitigating stale routing information in the event of network partition
with system components, and on streamlining the deployment workflow.

Please review our README for deployment instructions, give it a go. We are
looking forward to your feedback.

Thank you!

[1] https://github.com/cloudfoundry-incubator/cf-routing-release

Note:
- UDP protocols are not supported.
- Both HTTP and TCP routes will be directed to the same application port,
identified by environment variable $PORT. Support for multiple application
ports is coming soon.


Shannon Coen
Product Manager, Cloud Foundry
Pivotal, Inc.


Ruben Koster (VMware)
 

Really nice!! When will we be able to play with this functionality on PWS?


Shannon Coen
 

Hello Ruben,

We're currently adding support for quota management of route ports, as they
can be a limited resource in some environments. This is particularly bad on
AWS, where an ELB can be configured to listen on a maximum of 100 ports.

We're nearly done with quota support for route ports, and the CLI team is
adding support for the new quota attribute. Once the API and CLI are
delivered, we'll look at offering TCP routing on PWS to a limited audience.

Best,

Shannon Coen
Product Manager, Cloud Foundry
Pivotal, Inc.

On Wed, May 11, 2016 at 2:54 AM, Ruben Koster <superruup(a)gmail.com> wrote:

Really nice!! When will we be able to play with this functionality on PWS?