Date
1 - 3 of 3
consolidated routing api
Shannon Coen
We currently have two routing APIs in CF.
1. HTTP Routing API in cf-release:
https://github.com/cloudfoundry-incubator/routing-api
2. TCP Routing API in cf-routing-release:
https://github.com/cloudfoundry-incubator/cf-routing-release
The TCP Routing API is quite basic and we want to extend it for high
availability, authentication, etc. However, instead of enhancing the
existing TCP Routing API, we plan to add support for TCP route registration
to the Routing API in cf-release, as it already supports many of the
desired features. We'll get rid of the current API in cf-routing-release
and submodule in the Routing API from cf-release. Eventually we'll move the
Routing API (along with GoRouter and HAProxy) from cf-release into
cf-routing-release and submodule them into cf-release.
This consolidation, along with our not having any API consumer besides
GoRouter yet, gives us the opportunity to consider a common behavior for
routing API endpoints. We welcome your comments in our design doc:
https://docs.google.com/document/d/1v941oy3Y7RRI80gmLfhPZlaahElK_Q0C3pCQewK8Z3g/edit?usp=sharing
Thank you,
Shannon Coen
Product Manager, Cloud Foundry
Pivotal, Inc.
1. HTTP Routing API in cf-release:
https://github.com/cloudfoundry-incubator/routing-api
2. TCP Routing API in cf-routing-release:
https://github.com/cloudfoundry-incubator/cf-routing-release
The TCP Routing API is quite basic and we want to extend it for high
availability, authentication, etc. However, instead of enhancing the
existing TCP Routing API, we plan to add support for TCP route registration
to the Routing API in cf-release, as it already supports many of the
desired features. We'll get rid of the current API in cf-routing-release
and submodule in the Routing API from cf-release. Eventually we'll move the
Routing API (along with GoRouter and HAProxy) from cf-release into
cf-routing-release and submodule them into cf-release.
This consolidation, along with our not having any API consumer besides
GoRouter yet, gives us the opportunity to consider a common behavior for
routing API endpoints. We welcome your comments in our design doc:
https://docs.google.com/document/d/1v941oy3Y7RRI80gmLfhPZlaahElK_Q0C3pCQewK8Z3g/edit?usp=sharing
Thank you,
Shannon Coen
Product Manager, Cloud Foundry
Pivotal, Inc.
Shannon Coen
Some of the proposed changes to the Routing API are backward incompatible.
We don't believe anyone is using it yet, as adoption has generally be
blocked on securing connections to Consul, but we'd like to confirm.
Please raise your hand if you're using the routing API.
Thank you!
Shannon Coen
Product Manager, Cloud Foundry
Pivotal, Inc.
toggle quoted message
Show quoted text
We don't believe anyone is using it yet, as adoption has generally be
blocked on securing connections to Consul, but we'd like to confirm.
Please raise your hand if you're using the routing API.
Thank you!
Shannon Coen
Product Manager, Cloud Foundry
Pivotal, Inc.
On Wed, Sep 9, 2015 at 12:10 PM, Shannon Coen <scoen(a)pivotal.io> wrote:
We currently have two routing APIs in CF.
1. HTTP Routing API in cf-release:
https://github.com/cloudfoundry-incubator/routing-api
2. TCP Routing API in cf-routing-release:
https://github.com/cloudfoundry-incubator/cf-routing-release
The TCP Routing API is quite basic and we want to extend it for high
availability, authentication, etc. However, instead of enhancing the
existing TCP Routing API, we plan to add support for TCP route registration
to the Routing API in cf-release, as it already supports many of the
desired features. We'll get rid of the current API in cf-routing-release
and submodule in the Routing API from cf-release. Eventually we'll move the
Routing API (along with GoRouter and HAProxy) from cf-release into
cf-routing-release and submodule them into cf-release.
This consolidation, along with our not having any API consumer besides
GoRouter yet, gives us the opportunity to consider a common behavior for
routing API endpoints. We welcome your comments in our design doc:
https://docs.google.com/document/d/1v941oy3Y7RRI80gmLfhPZlaahElK_Q0C3pCQewK8Z3g/edit?usp=sharing
Thank you,
Shannon Coen
Product Manager, Cloud Foundry
Pivotal, Inc.
Shannon Coen
Checking once more that no one is using the Routing API yet, so we can
proceed with backward incompatible API changes. I believe we still have
this opportunity as we have not yet announced the component is ready for
use.
Our current plan is that the first consumers of the Routing API will be:
- CC (to register it's own route: api.system-domain)
- TCP Route Emitter (to register routes for Diego LRPs with TCP Routes)
- TCP Router (to fetch routing table of TCP routes)
Thank you,
Shannon Coen
Product Manager, Cloud Foundry
Pivotal, Inc.
toggle quoted message
Show quoted text
proceed with backward incompatible API changes. I believe we still have
this opportunity as we have not yet announced the component is ready for
use.
Our current plan is that the first consumers of the Routing API will be:
- CC (to register it's own route: api.system-domain)
- TCP Route Emitter (to register routes for Diego LRPs with TCP Routes)
- TCP Router (to fetch routing table of TCP routes)
Thank you,
Shannon Coen
Product Manager, Cloud Foundry
Pivotal, Inc.
On Wed, Sep 9, 2015 at 6:05 PM, Shannon Coen <scoen(a)pivotal.io> wrote:
Some of the proposed changes to the Routing API are backward incompatible.
We don't believe anyone is using it yet, as adoption has generally be
blocked on securing connections to Consul, but we'd like to confirm.
Please raise your hand if you're using the routing API.
Thank you!
Shannon Coen
Product Manager, Cloud Foundry
Pivotal, Inc.
On Wed, Sep 9, 2015 at 12:10 PM, Shannon Coen <scoen(a)pivotal.io> wrote:We currently have two routing APIs in CF.
1. HTTP Routing API in cf-release:
https://github.com/cloudfoundry-incubator/routing-api
2. TCP Routing API in cf-routing-release:
https://github.com/cloudfoundry-incubator/cf-routing-release
The TCP Routing API is quite basic and we want to extend it for high
availability, authentication, etc. However, instead of enhancing the
existing TCP Routing API, we plan to add support for TCP route registration
to the Routing API in cf-release, as it already supports many of the
desired features. We'll get rid of the current API in cf-routing-release
and submodule in the Routing API from cf-release. Eventually we'll move the
Routing API (along with GoRouter and HAProxy) from cf-release into
cf-routing-release and submodule them into cf-release.
This consolidation, along with our not having any API consumer besides
GoRouter yet, gives us the opportunity to consider a common behavior for
routing API endpoints. We welcome your comments in our design doc:
https://docs.google.com/document/d/1v941oy3Y7RRI80gmLfhPZlaahElK_Q0C3pCQewK8Z3g/edit?usp=sharing
Thank you,
Shannon Coen
Product Manager, Cloud Foundry
Pivotal, Inc.