toggle quoted messageShow quoted text
It would be great to have a chance to talk more about this at summit.
In summary, I believe supporting your use case is a large effort, and yours
in the only evidence I've heard in support of it. This makes prioritization
a challenge. However, I believe our current plan for architectural changes
to routing will eventually satisfy your requirements as well.
Currently, CC sends route registration to Diego when an app is started.
Routes do not land in the router's routing table until the app is started,
as Diego doesn't know anything about stopped apps (LRPs are deleted when a
user requests stop). Since Diego will have no information about the LRP,
the router-emitter has no way of discovering that a route should be
Our plan is to move routing info out Diego. I believe it will fulfill your
use case, and the Diego team very much wants this also.
The plan looks like this:
1. Update Routing API endpoints for HTTP route registration to be
consistent with the TCP endpoints we've been focused on
2. Update the Route-Registrar job used by system components, service
brokers, etc. to register HTTP, to point at the Routing API, instead of
3. Update the route-emitter to register HTTP routes for apps on Diego
with the Routing API. *At this point, we believe we will have removed
the need for NATS in CF*
4. Update the Routing API to support route reservation, independent of
whether there are backends or not. *At this point, an independent client
could conceivably register a route with a route_service_url, and without
5. We may need to update Route-Registrar job to support reservation of a
route without backends, and association of backends with the route
6. Update CC to register app routes with Routing API, instead of sending
this data to Diego with createLRP, and update the route-emitter to
significantly change its behavior: instead of calculating the routing table
and sending it to Routing API, it will ask Diego for backends associated
with routes in the Routing API (linked by the process ID, most likely). *At
this point, a developer could conceivably use CLI to create a route, bind
it to a Route Service, and without mapping the route to an app, the router
would forward requests for the route to the Route Service.*
Product Manager, Cloud Foundry
On Fri, May 13, 2016 at 1:31 AM, Guillaume Berche <bercheg(a)gmail.com> wrote:
What are your current thoughts on "maintaining routes with no backends in
the routing table" ? I quickly scanned the routing backlog few days ago
without yet finding trace of it.
I wish we could have used the opportunity of the cf summit "project office
hours" routing session  to have interactive exchanges around these use
cases. Unfortunately, my autosleep session  is scheduled at the exact
If the cf foundation organizers were able to swap sessions that would be
great. I'll send a separate email to events(a)cloudfoundry.org, is there
are other community members suffering from the same conflict.
Thanks in advance,
On Sun, May 1, 2016 at 12:03 AM, Stefan Mayr <stefan(a)mayr-stefan.de>
Am 28.04.2016 um 23:08 schrieb Mike Youngstrom:
Here is another minor use case. My users are often confused that a+1 for that proposal. A 404 also causes issues when crawler remove pages
stopped app returns a 404 instead of a 503. So, we implement that
functionality for the user using an app mapped to wildcard routes that
constantly asks the CC for valid routes. This works for wildcard
domains but not one off domains.
It might be better if the router returned a 503. At least for routes
bound to apps. Not sure if this should extend to routes not bound to
from their index. A 503 has less side effects. I would also prefer a 503
service unavailable when a route is not bound - because there is no service
for this route. IMHO the meaning is much closer to what has happended.
On Thu, Apr 28, 2016 at 1:32 PM, Shannon Coen <scoen(a)pivotal.io
Thank you for sharing your thoughts on these use cases. I can see
a route service field requests for an app, whether the app is up on
could be useful.
However, enabling this would significantly change how routes are
for apps on Cloud Foundry, and how the router handles the route
Routes are not currently enabled in the routing tier unless they are
to an app, and only when the app is determined healthy.
You are proposing the router maintains routes which have no
instead of a failed lookup determining whether a 404 is returned,
should figure out whether a route has any backends or a route
I'll chew on your use case and keep my ear out for additional use
maintaining routes with no backends in the routing table.
View this message in context:
Sent from the CF Dev mailing list archive at Nabble.com.