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.

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.

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.

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.

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.

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?