Re: [vcap-dev] Re: Proposal for Context Path Routing


Dieu Cao <dcao@...>
 

Shannon, the Product Manager for the Routing team, has this story [1] in
the CF Routing tracker project for doing a PR to the CLI to add support for
context path routes.

Yes, that's correct that the context path route support does not currently
support the particular example you've specified with wildcards or routing
based on HTTP methods.
If I recall correctly, we wanted to add some basic support for context path
routes without adding too much overhead in what gorouter needed to reason
about, as any logic added could impact every request to the gorouter.

There's a currently in progress tracks of work to support Route Services
[2] [3].
That would allow you to insert you're own proxy to support all sorts of use
cases and could be used to support what you've described.

Shannon is currently on vacation, but should be returning later this week.
I'll forward this request to him for consideration. You might also
consider opening up an issue against the gorouter with these enhancement
requests.

[1] https://www.pivotaltracker.com/story/show/93368928
[2] https://www.pivotaltracker.com/epic/show/2031344
[3] https://www.pivotaltracker.com/epic/show/1884060

On Mon, Sep 14, 2015 at 6:44 AM, Stevo Slavić <sslavic(a)gmail.com> wrote:

In this proposal and current Routes API docs
<http://apidocs.cloudfoundry.org/217/routes/creating_a_route.html> I
don't see support for wildcards when defining context path based route. Am
I missing something?
E.g. for resources like

/foos/bar/1/doSomeAction
/foos/baz/2/doSomeAction

and

/foos/bar/1/doSomeOtherAction
/foos/baz/2/doSomeOtherAction

I'd like all /foos/*/*/doSomeAction to be routed to one CF app, and all
/foos/*/*/doSomeOtherAction to be routed to a different CF app.

Did you consider supporting HTTP methods to be used for routing as well?
E.g. similar to previous example, I'd like some HTTP methods on particular
resources to be handled by separate app then the rest of the requests on
same resources.

DELETE /foos -> route to one cf app
* /foos -> route to another cf app, where * means any HTTP method, most
specific rule wins strategy

Ideally one would be able to combine both wildcards in HTTP methods and in
path segments to define a routing rule.


Also I do not see context path routing support in CF CLI (v6.12.3) or a
ticket in CF CLI issues to add the support. Did I miss something there? If
not should I create new ticket?

Kind regards,
Stevo Slavic.

On Tue, May 19, 2015 at 4:41 PM, sabith ks <sabithksme(a)gmail.com> wrote:

Thanks

On Tue, May 19, 2015 at 7:16 AM James Bayer <jbayer(a)pivotal.io> wrote:

context path based routing is currently experimental and mostly complete:
http://apidocs.cloudfoundry.org/208/routes/creating_a_route.html

see this epic: https://www.pivotaltracker.com/epic/show/1808212

On Tue, May 19, 2015 at 5:55 AM, sabith ks <sabithksme(a)gmail.com> wrote:

Hi all,

Was there any follow ups on this proposal

-- Thanks
Sabith

On Fri, Apr 24, 2015 at 08:35 Mike Youngstrom <youngm(a)gmail.com> wrote:

+1 couldn't have designed the feature better myself. :)

Mike

On Fri, Apr 24, 2015 at 3:52 AM, Dieu Cao <dcao(a)pivotal.io> wrote:

Ooops!

The link to the proposal is here:

[1]
https://docs.google.com/document/d/1H_adSiY7wGR85av9YfxxPRylSO8Q8U0ANJJTg6wpYRQ/edit?usp=sharing

On Friday, April 24, 2015 at 1:11:15 AM UTC-7, Johannes Hiemer wrote:

Hi Dieu,
link missing? :-/


On Friday, April 24, 2015 at 10:04:39 AM UTC+2, Dieu Cao wrote:

Hi All,

We've put together a proposal for Context Path Routing [1].

The goal of this feature is to enhance the gorouter, the cloud
controller, the routing api, and the cf cli to support the ability for a
space developer to create and map a route with a path to app1 and a route
with a different path to app2.

We'd like to be able to iterate on this document quickly, so please
keep your input and feedback in the comments of the document.

Thanks!
-Dieu
CF Runtime PM

--
You received this message because you are subscribed to the Google
Groups "Cloud Foundry Developers" group.
To view this discussion on the web visit
https://groups.google.com/a/cloudfoundry.org/d/msgid/vcap-dev/6f24eea9-7d1c-4547-8ed8-4a4643f1329b%40cloudfoundry.org
<https://groups.google.com/a/cloudfoundry.org/d/msgid/vcap-dev/6f24eea9-7d1c-4547-8ed8-4a4643f1329b%40cloudfoundry.org?utm_medium=email&utm_source=footer>
.

To unsubscribe from this group and stop receiving emails from it,
send an email to vcap-dev+unsubscribe(a)cloudfoundry.org.
--
You received this message because you are subscribed to the Google
Groups "Cloud Foundry Developers" group.
To view this discussion on the web visit
https://groups.google.com/a/cloudfoundry.org/d/msgid/vcap-dev/CAEoPEDpqCbFDS3Ogn%2B%3D_Q7FzX6Nr9OnO5_T0o1eYkBOmpEpUxQ%40mail.gmail.com
<https://groups.google.com/a/cloudfoundry.org/d/msgid/vcap-dev/CAEoPEDpqCbFDS3Ogn%2B%3D_Q7FzX6Nr9OnO5_T0o1eYkBOmpEpUxQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
.

To unsubscribe from this group and stop receiving emails from it, send
an email to vcap-dev+unsubscribe(a)cloudfoundry.org.
--
This mailing list is for closed, and is available for archival purposes
only. For active discussion, please visit
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev or email
cf-dev(a)lists.cloudfoundry.org
---
You received this message because you are subscribed to the Google
Groups "Cloud Foundry Developers" group.
To view this discussion on the web visit
https://groups.google.com/a/cloudfoundry.org/d/msgid/vcap-dev/CAHCF%3DJd%2BmiWb5apYUKjS3rVF7sr8vpedKFLQJS5XT5N25HCAcA%40mail.gmail.com
<https://groups.google.com/a/cloudfoundry.org/d/msgid/vcap-dev/CAHCF%3DJd%2BmiWb5apYUKjS3rVF7sr8vpedKFLQJS5XT5N25HCAcA%40mail.gmail.com?utm_medium=email&utm_source=footer>
.


--
Thank you,

James Bayer

--
This mailing list is for closed, and is available for archival purposes
only. For active discussion, please visit
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev or email
cf-dev(a)lists.cloudfoundry.org
---
You received this message because you are subscribed to the Google
Groups "Cloud Foundry Developers" group.
To view this discussion on the web visit
https://groups.google.com/a/cloudfoundry.org/d/msgid/vcap-dev/CAB%3Dt-sWEN8jaxrfRa3zRBbt-AyjaULBnTPHb0%2BpoboqhYp06jQ%40mail.gmail.com
<https://groups.google.com/a/cloudfoundry.org/d/msgid/vcap-dev/CAB%3Dt-sWEN8jaxrfRa3zRBbt-AyjaULBnTPHb0%2BpoboqhYp06jQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
.
--
This mailing list is for closed, and is available for archival purposes
only. For active discussion, please visit
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev or email
cf-dev(a)lists.cloudfoundry.org
---
You received this message because you are subscribed to the Google Groups
"Cloud Foundry Developers" group.
To view this discussion on the web visit
https://groups.google.com/a/cloudfoundry.org/d/msgid/vcap-dev/CAHCF%3DJdyN5BtFJbH0e8sMqgWJ4Z89tx%3D8Ou1kBju%2BWQ3AGAfVw%40mail.gmail.com
<https://groups.google.com/a/cloudfoundry.org/d/msgid/vcap-dev/CAHCF%3DJdyN5BtFJbH0e8sMqgWJ4Z89tx%3D8Ou1kBju%2BWQ3AGAfVw%40mail.gmail.com?utm_medium=email&utm_source=footer>
.

Join cf-dev@lists.cloudfoundry.org to automatically receive all group messages.