those urls do not look right. but they are dependent on what url you
deployed the uaa under. ( ie / or /uaa )

what's returned by uaac info is dependent on your uaa config.

I'd have to get back to you in CC config. not my area of expertise. but
yes I believe the CC will have an oauth client registered with the UAA

Filip

On Friday, September 4, 2015, kyle havlovitz <kylehav(a)gmail.com> wrote:

I realize it's a pain, but I'm setting these up without bosh. I'm just
unfamiliar with how the config between the CC and the UAA needs to be set.

The http://localhost:8080/login and http://localhost:8080/uaa seem to be
the correct URLs (they're whats returned by 'uaac info')
Likewise, the CLI seems to be pointed at the right places, it's just
getting this invalid token error, as if the CC can't correctly talk to the
uaa or something.

what should the uaa.resource_id and uaa.symmetric_secret fields in the CC
config be set to if I'm using the default config/clients? Are there any
other values in the CC config that might be the issue here?

On Fri, Sep 4, 2015 at 6:26 PM, Filip Hanik <fhanik(a)pivotal.io> wrote:

ok, is that the correct URL?

you're attempting to configure a very large eco system by hand. That can
be a bit difficult. If you want a local cloud foundry, I would suggest
bosh-lite

basically, clone cloudfoundry/cf-release and cloudfoundry/bosh-lite

cd bosh-lite
vagrant up (this launches a VM with bosh director on it)
bin/add-route (sets up network routing)
bin/provision-cf (builds and publishing cloud foundry to the VM

cf api api.10.244.0.34.xip.io
cf login







On Fri, Sep 4, 2015 at 4:18 PM, kyle havlovitz <kylehav(a)gmail.com>
wrote:

The cloud controller logs have "Invalid bearer token:
#<CF::UAA::InvalidSignature: Signature verification failed>" and the 401
invalid auth message.

On Fri, Sep 4, 2015 at 6:14 PM, kyle havlovitz <kylehav(a)gmail.com>
wrote:

Ok, I set those 2 properties to http://localhost:8080 and it looks
identical; same error, same endpoints requested.
Could something be wrong with the cloud controller config?

On Fri, Sep 4, 2015 at 5:58 PM, Filip Hanik <fhanik(a)pivotal.io> wrote:

yes, this is the URL misconfiguration I was talking about.

In your uaa.yml you should have two properties

login.url: http://localhost:8080
uaa.url: http://localhost:8080

set those two, and let's see that trace again



On Fri, Sep 4, 2015 at 2:58 PM, kyle havlovitz <kylehav(a)gmail.com>
wrote:

The CLI seems to be able to get a token now though, it's failing for
a different reason:

cf login

API endpoint: http://localhost:8181
REQUEST: [2015-09-04T20:46:51Z]
GET /v2/info HTTP/1.1
Host: localhost:8181
Accept: application/json
Content-Type: application/json
User-Agent: go-cli 6.12.3-c0c9a03 / linux


RESPONSE: [2015-09-04T20:46:51Z]
HTTP/1.1 200 OK
Content-Length: 406
Connection: keep-alive
Content-Type: application/json;charset=utf-8
Server: thin
X-Content-Type-Options: nosniff
X-Vcap-Request-Id: d44503ef-3b2c-4340-9958-ad91daf3706c
{"name":"vcap","build":"2222","support":"
http://support.local.example.com","version":2,"description":"CF v2
test environment","authorization_endpoint":"http://localhost:8080
","token_endpoint":"http://localhost:8080/uaa
","min_cli_version":null,"min_recommended_cli_version":null,"api_version":"2.34.0","app_ssh_endpoint":null,"app_ssh_host_key_fingerprint":null,"logging_endpoint":"ws://
127.0.0.1:9090"}
Warning: Insecure http API endpoint detected: secure https API
endpoints are recommended

REQUEST: [2015-09-04T20:46:51Z]
GET /login HTTP/1.1
Host: localhost:8080
Accept: application/json
Content-Type: application/json
User-Agent: go-cli 6.12.3-c0c9a03 / linux


RESPONSE: [2015-09-04T20:46:51Z]
HTTP/1.1 200 OK
Transfer-Encoding: chunked
Access-Control-Allow-Origin: *
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Cache-Control: no-cache, no-store, max-age=0
Content-Language: en-US
Content-Type: application/json;charset=UTF-8
Date: Fri, 04 Sep 2015 20:46:51 GMT
Expires: 0
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Pragma: no-cache
Pragma: no-cache
Server: Apache-Coyote/1.1
Strict-Transport-Security: max-age=31536000
X-Content-Type-Options: nosniff
X-Frame-Options: DENY
X-Xss-Protection: 1; mode=block
1fd

{"timestamp":"2015-08-05T00:00:41+0000","app":{"version":"2.5.1"},"idpDefinitions":[],"fieldUsernameShow":true,"zone_name":"uaa","commit_id":"eae6724","prompts":{"username":["text","Email"],"password":["password","Password"]},"forgotPasswordLink":"/forgot_password","createAccountLink":"/create_account","links":{"register":"/create_account","passwd":"/forgot_password","login":"
http://localhost:8080/login","uaa":"http://localhost:8080/uaa
"},"entityID":"cloudfoundry-saml-login","linkCreateAccountShow":true}
0


Email> admin
Password>
Authenticating...
REQUEST: [2015-09-04T20:46:58Z]
POST /oauth/token HTTP/1.1
Host: localhost:8080
Accept: application/json
Authorization: [PRIVATE DATA HIDDEN]
Content-Type: application/x-www-form-urlencoded
User-Agent: go-cli 6.12.3-c0c9a03 / linux
grant_type=password&password=[PRIVATE DATA
HIDDEN]&scope=&username=admin
RESPONSE: [2015-09-04T20:46:58Z]
HTTP/1.1 200 OK
Transfer-Encoding: chunked
Access-Control-Allow-Origin: *
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Cache-Control: no-store
Content-Type: application/json;charset=UTF-8
Date: Fri, 04 Sep 2015 20:46:58 GMT
Expires: 0
Pragma: no-cache
Pragma: no-cache
Server: Apache-Coyote/1.1
X-Content-Type-Options: nosniff
X-Frame-Options: DENY
X-Xss-Protection: 1; mode=block
738
{"access_token":"[PRIVATE DATA
HIDDEN]","token_type":"bearer","refresh_token":"[PRIVATE DATA
HIDDEN]","expires_in":43199,"scope":"scim.read scim.userids
cloud_controller.admin scim.write cloud_controller.write password.write
openid cloud_controller.read","jti":"cbda4e10-cf04-4696-a560-2e1f4d2c610c"}
0

OK

REQUEST: [2015-09-04T20:46:58Z]
GET /v2/organizations HTTP/1.1
Host: localhost:8181
Accept: application/json
Authorization: [PRIVATE DATA HIDDEN]
Content-Type: application/json
User-Agent: go-cli 6.12.3-c0c9a03 / linux


RESPONSE: [2015-09-04T20:46:58Z]
HTTP/1.1 401 Unauthorized
Content-Length: 97
Connection: keep-alive
Content-Type: application/json;charset=utf-8
Server: thin
X-Content-Type-Options: nosniff
X-Vcap-Request-Id: b7658709-8145-4e31-a7ed-12a7831e99da
{
"code": 1000,
"description": "Invalid Auth Token",
"error_code": "CF-InvalidAuthToken"
}

REQUEST: [2015-09-04T20:46:58Z]
POST /oauth/token HTTP/1.1
Host: localhost:8080
Accept: application/json
Authorization: [PRIVATE DATA HIDDEN]
Content-Type: application/x-www-form-urlencoded
User-Agent: go-cli 6.12.3-c0c9a03 / linux

grant_type=refresh_token&refresh_token=eyJhbGciOiJIUzI1NiJ9.eyJqdGkiOiJlNzFmOTNmZS0yMmEyLTQ3ZjgtODgwNC0xN2ZmNmU1YzM1NmMiLCJzdWIiOiIzMDBkZTc1YS1mN2RhLTRjMWQtYjA0Yi02YWZhZjI1ZmE5MjgiLCJzY29wZSI6WyJzY2ltLnJlYWQiLCJzY2ltLnVzZXJpZHMiLCJjbG91ZF9jb250cm9sbGVyLmFkbWluIiwic2NpbS53cml0ZSIsImNsb3VkX2NvbnRyb2xsZXIud3JpdGUiLCJwYXNzd29yZC53cml0ZSIsIm9wZW5pZCIsImNsb3VkX2NvbnRyb2xsZXIucmVhZCJdLCJpYXQiOjE0NDEzOTk2MTgsImV4cCI6MTQ0Mzk5MTYxOCwiY2lkIjoiY2YiLCJjbGllbnRfaWQiOiJjZiIsImlzcyI6Imh0dHA6Ly9sb2NhbGhvc3Q6ODA4MC91YWEvb2F1dGgvdG9rZW4iLCJ6aWQiOiJ1YWEiLCJncmFudF90eXBlIjoicGFzc3dvcmQiLCJ1c2VyX25hbWUiOiJhZG1pbiIsInVzZXJfaWQiOiIzMDBkZTc1YS1mN2RhLTRjMWQtYjA0Yi02YWZhZjI1ZmE5MjgiLCJyZXZfc2lnIjoiOTAyODliNjgiLCJhdWQiOlsiY2YiLCJzY2ltIiwiY2xvdWRfY29udHJvbGxlciIsInBhc3N3b3JkIiwib3BlbmlkIl19.-eGB2RWZfYVZkTSvT7c4lUzsY5QZMWgXFHMGGx4HEN8&scope=
RESPONSE: [2015-09-04T20:46:58Z]
HTTP/1.1 200 OK
Transfer-Encoding: chunked
Access-Control-Allow-Origin: *
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Cache-Control: no-store
Content-Type: application/json;charset=UTF-8
Date: Fri, 04 Sep 2015 20:46:58 GMT
Expires: 0
Pragma: no-cache
Pragma: no-cache
Server: Apache-Coyote/1.1
X-Content-Type-Options: nosniff
X-Frame-Options: DENY
X-Xss-Protection: 1; mode=block
738
{"access_token":"[PRIVATE DATA
HIDDEN]","token_type":"bearer","refresh_token":"[PRIVATE DATA
HIDDEN]","expires_in":43199,"scope":"scim.userids scim.read
cloud_controller.admin password.write scim.write openid
cloud_controller.write
cloud_controller.read","jti":"e62d3265-9ab7-441e-b2b2-69ca92d81d7c"}
0


REQUEST: [2015-09-04T20:46:58Z]
GET /v2/organizations HTTP/1.1
Host: localhost:8181
Accept: application/json
Authorization: [PRIVATE DATA HIDDEN]
Content-Type: application/json
User-Agent: go-cli 6.12.3-c0c9a03 / linux


RESPONSE: [2015-09-04T20:46:58Z]
HTTP/1.1 401 Unauthorized
Content-Length: 97
Connection: keep-alive
Content-Type: application/json;charset=utf-8
Server: thin
X-Content-Type-Options: nosniff
X-Vcap-Request-Id: 7b07e39c-60f0-4db4-9274-6a59e23b8f29
{
"code": 1000,
"description": "Invalid Auth Token",
"error_code": "CF-InvalidAuthToken"
}
FAILED
Error finding available orgs
Invalid auth token: Invalid Auth Token
FAILED
Error finding available orgs
Invalid auth token: Invalid Auth Token

API endpoint: http://localhost:8181 (API version: 2.34.0)
User: admin
No org or space targeted, use 'cf target -o ORG -s SPACE'


On Fri, Sep 4, 2015 at 4:49 PM, kyle havlovitz <kylehav(a)gmail.com>
wrote:

Ok, thanks for the helpful links.
I replaced my config with the uaa.yml and login.yml from there and
now the uaac commands from above work and I can run 'uaac token
owner get'. I still can't login to cf with the cli though.

On Fri, Sep 4, 2015 at 4:15 PM, Filip Hanik <fhanik(a)pivotal.io>
wrote:

Minimalist defaults are in the UAA repo (uaa.yml and login.yml)

https://github.com/cloudfoundry/uaa/tree/master/uaa/src/main/resources

Yaml is very sensitive to indentation. So hand crafting it may
become a bit difficult.

If you want the UAA to provide all default values (including
admin/adminsecret client and cf/<blank password> client, then don't add any
uaa.yml config file at all. Just start up UAA with it's defaults.
It will suck in client defaults from

https://github.com/cloudfoundry/uaa/blob/feature/invitations_flow_by_email_domain/uaa/src/main/webapp/WEB-INF/spring/oauth-clients.xml#L47-L172

Filip


On Fri, Sep 4, 2015 at 2:05 PM, kyle havlovitz <kylehav(a)gmail.com>
wrote:

is there an example somewhere of a minimalist working config for
them? I'm going through at the moment and trying to make mine resemble the
config here:
https://github.com/cloudfoundry/cf-release/blob/master/jobs/uaa/templates/uaa.yml.erb

I'm also defining a test admin user in the scim users section

On Fri, Sep 4, 2015 at 4:00 PM, Filip Hanik <fhanik(a)pivotal.io>
wrote:

ok, that tells me that your configuration of the UAA clients is
incorrect



On Fri, Sep 4, 2015 at 1:44 PM, kyle havlovitz <
kylehav(a)gmail.com> wrote:

ok so the 'uaac token client get' fails, and the error is 'Bad
credentials'

On Fri, Sep 4, 2015 at 3:33 PM, Filip Hanik <fhanik(a)pivotal.io>
wrote:

ok, so we can validate that

uaac target http://localhost:8080
uaac token client get admin -s <your admin client secret>
uaac clients

Should show your 'cf' client in the list

then we can do

uaac token owner get cf <username> -s "" -p <user password>

and if that works, we can take it to the next step



On Fri, Sep 4, 2015 at 1:26 PM, kyle havlovitz <
kylehav(a)gmail.com> wrote:

I started the uaa by building from the tagged version in
cf-release v215 and running it via tomcat with a custom config file, but I
didn't specify a database. I have both a cf and admin section in the uaa
clients config:

cf:

id: cf
override: true
authorized-grant-types: password,implicit,refresh_token
authorities: uaa.none
scope:
cloud_controller.read,cloud_controller.write,openid,password.write,cloud_controller.admin,scim.read,scim.write
secret: 'xxxxxxxxxx'

admin:

id: admin
authorized-grant-types: client_credentials
authorities:
clients.read,clients.write,clients.secret,password.write,scim.read,uaa.admin
scope: read,write,password
resource-ids: clients
secret: 'xxxxxxxxxx'


On Fri, Sep 4, 2015 at 3:09 PM, Filip Hanik <
fhanik(a)pivotal.io> wrote:

ok, so the URL you have is /oauth/token, that's fine. your
trace returns

"authorization_endpoint":"http://localhost:8080
","token_endpoint":"http://localhost:8080/uaa"

indicating that there is a misconfiguration somewhere, but
we can fix that later.

How did you start the UAA? Are you sure that your UAA has a
client named 'cf' in its database?



On Fri, Sep 4, 2015 at 1:05 PM, kyle havlovitz <
kylehav(a)gmail.com> wrote:

Running that command against /uaa/oauth/token gives just a
redirect to /login. Doing it with /oauth/token gives a 401 unauthorized,
same as the cf cli.

What do you mean by deploy it as root "/"? As in, a
override the url it hosts the endpoints at?

Hello again,

I'm sorry for having to revive this topic, but I'm still unaware about the
deletion process.

[... ] i believe with standard removal tools.

Could you please specify the term "standard removal tool". What's the
standard? Is standard just the deletion of the pointer pointing on files /
segments, or is secure deletion state of the art?
I'd be thankful for any reference on documentation regarding this topic.

Thanks in advance.

Cheers Chris

Here are some of the examples:

* Sensitive property management as part of manifest generation (encrypted
or acquired from an outside source)

* We have our own internal bosh releases and config that we'll need to
merge in with the things cf-deployment is doing. For example, if
cf-deployment tags v250 as including Diego 3333 and etcd 34 with given
templates perhaps we'd like to augment this with our own release jobs and
config that we know to work with cf-deployment 250's and perhaps tag it as
v250.lds and that becomes what we use to generate our manifests and upload
releases.

* Occasionally we may wish to use some config from a stock release not
currently exposed in a cf-deployment template. I'd like to be sure there
is a way we can add that config, in a not hacky way, without waiting for a
PR to be accepted and subsequent release.

* If for some reason we are forced to fork a stock release we'd like to be
able to use that forked release we are building instead of the publicly
available one for manifest generation and release uploads, etc.

Does that help?

Mike



On Tue, Sep 15, 2015 at 9:50 PM, Amit Gupta <agupta(a)pivotal.io> wrote:

Thanks for the feedback Mike!

Can you tell us more specifically what sort of extensions you need? It
would be great if cf-deployment provided an interface that could serve the
needs of essentially all operators of CF.

Thanks,
Amit

On Tue, Sep 15, 2015 at 4:02 PM, Mike Youngstrom <youngm(a)gmail.com>
wrote:

This is great stuff! My organization currently maintains our own custom
ways to generate manifests, include secure properties, and manage release
versions.

We would love to base the next generation of our solution on
cf-deployment. Have you put any thought into how others might customize or
extend cf-deployment? Our needs are very similar to yours just sometimes a
little different.

Perhaps a private fork periodically merged with a known good release
combination (tag) might be appropriate? Or some way to include the same
tools into a wholly private repo?

Mike


On Tue, Sep 8, 2015 at 1:22 PM, Amit Gupta <agupta(a)pivotal.io> wrote:

Hi all,

The CF OSS Release Integration team (casually referred to as the "MEGA
team") is trying to solve a lot of tightly interrelated problems, and make
many of said problems less interrelated. It is difficult to address just
one issue without touching the others, so the following proposal addresses
several issues, but the most important ones are:

* decompose cf-release into many independently manageable,
independently testable, independently usable releases
* separate manifest generation strategies from the release source,
paving the way for Diego to be part of the standard deployment

This proposal will outline a picture of how manifest generation will
work in a unified manner in development, test, and integration
environments. It will also outline a picture of what each release’s test
pipelines will look like, how they will feed into a common integration
environment, and how feedback from the integration environment will feed
back into the test environments. Finally, it will propose a picture for
what the integration environment will look like, and how we get from the
current integration environment to where we want to be.

For further details, please feel free to view and comment here:


https://docs.google.com/document/d/1Viga_TzUB2nLxN_ILqksmUiILM1hGhq7MBXxgLaUOkY

Thanks,
Amit, CF OSS Release Integration team

Hello Stevo,

Thank you for your suggestion of support for wildcards in route paths. I
have noted the request and will keep an ear out for the same request from
others in order to help me prioritize.

Best,

Shannon Coen
Product Manager, Cloud Foundry
Pivotal, Inc.

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

Thanks for heads up and fast reply!

Will read spec routing services/API specs in more detail. For the moment,
for use cases I mentioned, one can use/deploy something like Netflix Zuul
(Spring Boot) CF app, as a routing service. Covers a lot of use cases, but
I expected support in CF itself.

Thanks once more!

Kind regards,
Stevo Slavic.

On Mon, Sep 14, 2015 at 4:47 PM, Dieu Cao <dcao(a)pivotal.io> wrote:

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>
.

Thanks for heads up and fast reply!

Will read spec routing services/API specs in more detail. For the moment,
for use cases I mentioned, one can use/deploy something like Netflix Zuul
(Spring Boot) CF app, as a routing service. Covers a lot of use cases, but
I expected support in CF itself.

Thanks once more!

Kind regards,
Stevo Slavic.

On Mon, Sep 14, 2015 at 4:47 PM, Dieu Cao <dcao(a)pivotal.io> wrote:

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>
.

It's just the staticfile buildpack from
https://github.com/cloudfoundry/staticfile-buildpack.git, I can try git
cloning it from inside the warden container though

On Wed, Sep 16, 2015 at 9:30 AM, Mike Dalessio <mdalessio(a)pivotal.io>
wrote:

Worth noting that the git repo also needs to allow anonymous access. If
it's a private repo, then the 'git clone' is going to fail.

Can you verify that you can download the buildpack from your repo without
authenticating?

On Tue, Sep 15, 2015 at 7:43 PM, CF Runtime <cfruntime(a)gmail.com> wrote:

It's not something we've ever seen before.

In theory, the warden container needs the git binary, which I think it
gets from the cflinuxfs2 stack; and internet access to wherever the git
repo lives.

If the warden container has both of those things, I can't think of any
reason why it wouldn't work.

Joseph
OSS Release Integration Team

On Tue, Sep 15, 2015 at 2:06 PM, kyle havlovitz <kylehav(a)gmail.com>
wrote:

I tried deploying via uploading a buildpack to the CC (had to set up
nginx first, I didnt have it running/configured before) and that worked! So
that's awesome, but I'm not sure what the problem with using a remote
buildpack is. Even with nginx, I still get the exact same error as before
when pushing using a remote buildpack from git.

On Tue, Sep 15, 2015 at 6:57 AM, CF Runtime <cfruntime(a)gmail.com>
wrote:

Looking at the logs, we can see it finishing downloading the app
package. The next step should be to download and run the buildpack. Since
you mention there is no output after this, I'm guessing it doesn't get that
far.

It might be having trouble downloading the buildpack from the remote
git url. Could you try uploading the buildpack to Cloud Controller and then
having it use that buildpack to see if that makes a difference?


http://apidocs.cloudfoundry.org/217/buildpacks/creates_an_admin_buildpack.html

http://apidocs.cloudfoundry.org/217/buildpacks/upload_the_bits_for_an_admin_buildpack.html

Joseph
OSS Release Integration Team

On Mon, Sep 14, 2015 at 5:37 PM, kyle havlovitz <kylehav(a)gmail.com>
wrote:

Here's the full dea_ng and warden debug logs:
https://gist.github.com/MrEnzyme/6dcc74174482ac62c1cf

Are there any other places I should look for logs?

On Mon, Sep 14, 2015 at 8:14 PM, CF Runtime <cfruntime(a)gmail.com>
wrote:

That's not an error we normally get. It's not clear if the
staging_info.yml error is the source of the problem or an artifact of it.
Having more logs would allow us to speculate more.

Joseph & Dan
OSS Release Integration Team

On Mon, Sep 14, 2015 at 2:24 PM, kyle havlovitz <kylehav(a)gmail.com>
wrote:

I have the cloudfoundry components built, configured and running on
one VM (not in BOSH), and when I push an app I'm getting a generic 'FAILED
StagingError' message after '-----> Downloaded app package (460K)'.

There's nothing in the logs for the dea/warden that seems suspect
other than these 2 things:

{

"timestamp": 1441985105.8883495,

"message": "Exited with status 1 (35.120s):

[[\"/opt/cloudfoundry/warden/warden/src/closefds/closefds\",
\"/opt/cloudfoundry/warden/warden/src/closefds/closefds\"],
\"/var/warden/containers/18vf956il5v/bin/iomux-link\", \"-w\",
\"/var/warden/containers/18vf956il5v/jobs/8/cursors\",
\"/var/warden/containers/18vf956il5v/jobs/8\"]",

"log_level": "warn",

"source": "Warden::Container::Linux",

"data": {

"handle": "18vf956il5v",

"stdout": "",

"stderr": ""

},

"thread_id": 69890836968240,

"fiber_id": 69890849112480,

"process_id": 17063,

"file":

"/opt/cloudfoundry/warden/warden/lib/warden/container/spawn.rb",

"lineno": 135,

"method": "set_deferred_success"

}

{

"timestamp": 1441985105.94083,

"message": "Exited with status 23 (0.023s):

[[\"/opt/cloudfoundry/warden/warden/src/closefds/closefds\",
\"/opt/cloudfoundry/warden/warden/src/closefds/closefds\"], \"rsync\",
\"-e\", \"/var/warden/containers/18vf956il5v/bin/wsh --socket
/var/warden/containers/18vf956il5v/run/wshd.sock --rsh\", \"-r\", \"-p\",
\"--links\", \"vcap(a)container:/tmp/staged/staging_info.yml\",
\"/tmp/dea_ng/staging/d20150911-17093-1amg6y8\"]",

"log_level": "warn",

"source": "Warden::Container::Linux",

"data": {

"handle": "18vf956il5v",

"stdout": "",

"stderr": "rsync: link_stat

\"/tmp/staged/staging_info.yml\" failed: No such file or directory
(2)\nrsync error: some files/attrs were not transferred (see previous
errors) (code 23) at main.c(1655) [Receiver=3.1.0]\nrsync: [Receiver] write
error: Broken pipe (32)\n"

},

"thread_id": 69890836968240,

"fiber_id": 69890849112480,

"process_id": 17063,

"file":

"/opt/cloudfoundry/warden/warden/lib/warden/container/spawn.rb",

"lineno": 135,

"method": "set_deferred_success"

}


And I think the second error is just during cleanup, only failing
because the staging process didn't get far enough in to create the
'staging_info.yml'. The one about iomux-link exiting with status 1 is
pretty mysterious though and I have no idea what caused it. Does anyone
know why this might be happening?

Thanks for the feedback Mike!

Can you tell us more specifically what sort of extensions you need? It
would be great if cf-deployment provided an interface that could serve the
needs of essentially all operators of CF.

Thanks,
Amit

On Tue, Sep 15, 2015 at 4:02 PM, Mike Youngstrom <youngm(a)gmail.com> wrote:

This is great stuff! My organization currently maintains our own custom
ways to generate manifests, include secure properties, and manage release
versions.

We would love to base the next generation of our solution on
cf-deployment. Have you put any thought into how others might customize or
extend cf-deployment? Our needs are very similar to yours just sometimes a
little different.

Perhaps a private fork periodically merged with a known good release
combination (tag) might be appropriate? Or some way to include the same
tools into a wholly private repo?

Mike


On Tue, Sep 8, 2015 at 1:22 PM, Amit Gupta <agupta(a)pivotal.io> wrote:

Hi all,

The CF OSS Release Integration team (casually referred to as the "MEGA
team") is trying to solve a lot of tightly interrelated problems, and make
many of said problems less interrelated. It is difficult to address just
one issue without touching the others, so the following proposal addresses
several issues, but the most important ones are:

* decompose cf-release into many independently manageable, independently
testable, independently usable releases
* separate manifest generation strategies from the release source,
paving the way for Diego to be part of the standard deployment

This proposal will outline a picture of how manifest generation will
work in a unified manner in development, test, and integration
environments. It will also outline a picture of what each release’s test
pipelines will look like, how they will feed into a common integration
environment, and how feedback from the integration environment will feed
back into the test environments. Finally, it will propose a picture for
what the integration environment will look like, and how we get from the
current integration environment to where we want to be.

For further details, please feel free to view and comment here:


https://docs.google.com/document/d/1Viga_TzUB2nLxN_ILqksmUiILM1hGhq7MBXxgLaUOkY

Thanks,
Amit, CF OSS Release Integration team

+1 We'd love a metadata service as well when the dust settles.

Mike

On Wed, Sep 16, 2015 at 1:17 PM, Christopher B Ferris <chrisfer(a)us.ibm.com

wrote:

Onsi,

I can tell you that we (IBM) would welcome a secure metadata service for
retrieving credentials, etc. I'm sure we'd help make that happen.

Cheers,

Christopher Ferris
IBM Distinguished Engineer, CTO Open Technology
IBM Cloud, Open Technologies
email: chrisfer(a)us.ibm.com
twitter: @christo4ferris
blog: http://thoughtsoncloud.com/index.php/author/cferris/
phone: +1 508 667 0402



----- Original message -----
From: Onsi Fakhouri <ofakhouri(a)pivotal.io>
To: "Discussions about Cloud Foundry projects and the system overall." <
cf-dev(a)lists.cloudfoundry.org>
Cc:
Subject: [cf-dev] Re: Environment variable names (was RE: Environment
variable changes in DIEGO)
Date: Wed, Sep 16, 2015 11:40 AM


Would if we could! Environment variables are part of the surface area
that constitutes the contract between the platform and the application.
While we could have duplicates with CF_* and eventually deprecate VCAP_*
the new runtime needs to support droplets staged by the legacy runtime
seamlessly.

Once the dust settles I'd sooner see us step back and reconsider this
particular abstraction. For example, instead of env vars an authenticated
metadata service a la AWS's http://169.254.169.254/ would give us more
flexibility, allow us to dynamically control metadata made available to
apps, and even version metadata sanely.

Onsi

Sent from my iPad

On Sep 16, 2015, at 8:30 AM, john mcteague <john.mcteague(a)gmail.com>
wrote:


On a related, but slightly off, topic, while renaming the VCAP_* vars
would have a big impact, is it not time we thought about renaming these to
CF_* ?

John.
On 16 Sep 2015 16:09, "Matthew Sykes" <matthew.sykes(a)gmail.com> wrote:

The changes, in general, were intentional. The `application_uris` data
was always broken as it didn't reflect route changes. I can't speak
directly to the time stamp data.

The host is present still so I don't know why you don't see it.

We also have a migration guide [1]. If you think additional information
is needed there, pull requests would be welcome.

[1]:
https://github.com/cloudfoundry-incubator/diego-design-notes/blob/master/migrating-to-diego.md

On Wed, Sep 16, 2015 at 10:19 AM, Jack Cai <greensight(a)gmail.com> wrote:

I notice the below changes in the environment variables of DIEGO:
1. VCAP_APP_HOST & VCAP_APP_PORT are removed.
2. These fields are removed from VCAP_APPLICATION value:
application_uris, started_at, start, started_at_timestamp, host,
state_timestamp

I suppose #1 is intentional. How about #2?

Jack




--
Matthew Sykes
matthew.sykes(a)gmail.com

Thanks Dmitriy,

Just for clarity, are you saying multiple instances of a VM cannot share a
single shared filesystem?

On Wed, Sep 16, 2015 at 6:59 PM, Dmitriy Kalinin <dkalinin(a)pivotal.io>
wrote:

BOSH allocates a persistent disk per instance. It never shares persistent
disks between multiple instances at the same time.

If you need a shared file system, you will have to use some kind of a
release for it. It's not any different from what people do with nfs
server/client.

On Wed, Sep 16, 2015 at 7:09 AM, Amit Gupta <agupta(a)pivotal.io> wrote:

The shared file system aspect is an interesting wrinkle to the problem.
Unless you use some network layer to how you write to the shared file
system, e.g. SSHFS, I think apps will not work because they get isolated to
run in a container, they're given a chroot "jail" for their file system,
and it gets blown away whenever the app is stopped or restarted (which will
commonly happen, e.g. during a rolling deploy of the container-runner VMs).

Do you have something that currently works? How do your VMs currently
access this shared FS? I'm not sure BOSH has the abstractions for choosing
a shared, already-existing "persistent disk" to be attached to multiple
VMs. I also don't know what happens when you scale your VMs down, because
BOSH would generally destroy the associated persistent disk, but you don't
want to destroy the shared data.

Dmitriy, any idea how BOSH can work with a shared filesystem (e.g. HDFS)?

Amit

On Wed, Sep 16, 2015 at 6:54 AM, Kayode Odeyemi <dreyemi(a)gmail.com>
wrote:

On Wed, Sep 16, 2015 at 3:44 PM, Amit Gupta <agupta(a)pivotal.io> wrote:

Are the spark jobs tasks that you expect to end, or apps that you
expect to run forever?

They are tasks that run forever. The jobs are subscribers to RabbitMQ
queues that process
messages in batches.

Do your jobs need to write to the file system, or do they access a
shared/distributed file system somehow?

The jobs write to shared filesystem.

Do you need things like a static IP allocated to your jobs?

No.

Are your spark jobs serving any web traffic?

No.

----- Original message -----
From: Onsi Fakhouri <ofakhouri@...>
To: "Discussions about Cloud Foundry projects and the system overall." <cf-dev@...>
Cc:
Subject: [cf-dev] Re: Environment variable names (was RE: Environment variable changes in DIEGO)
Date: Wed, Sep 16, 2015 11:40 AM
 

 

Would if we could!  Environment variables are part of the surface area that constitutes the contract between the platform and the application.  While we could have duplicates with CF_* and eventually deprecate VCAP_* the new runtime needs to support droplets staged by the legacy runtime seamlessly.

 

Once the dust settles I'd sooner see us step back and reconsider this particular abstraction.  For example, instead of env vars an authenticated metadata service a la AWS's http://169.254.169.254/ would give us more flexibility, allow us to dynamically control metadata made available to apps, and even version metadata sanely.

 

Onsi

Sent from my iPad

On Sep 16, 2015, at 8:30 AM, john mcteague <john.mcteague@...> wrote:
 

On a related, but slightly off, topic, while renaming the VCAP_* vars would have a big impact, is it not time we thought about renaming these to CF_*  ?

John.

On 16 Sep 2015 16:09, "Matthew Sykes" <matthew.sykes@...> wrote:

The changes, in general, were intentional. The `application_uris` data was always broken as it didn't reflect route changes. I can't speak directly to the time stamp data.

 

The host is present still so I don't know why you don't see it.

 

We also have a migration guide [1]. If you think additional information is needed there, pull requests would be welcome.

 

[1]: https://github.com/cloudfoundry-incubator/diego-design-notes/blob/master/migrating-to-diego.md

 

On Wed, Sep 16, 2015 at 10:19 AM, Jack Cai <greensight@...> wrote:

I notice the below changes in the environment variables of DIEGO:
1. VCAP_APP_HOST & VCAP_APP_PORT are removed.
2. These fields are removed from VCAP_APPLICATION value: application_uris, started_at, start, started_at_timestamp, host, state_timestamp
 

I suppose #1 is intentional. How about #2?
 

Jack
 

 

 

--

Matthew Sykes
matthew.sykes@...

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.