What's even weirder is the GET request to /login seems to do the right thing, but POST to /oauth/token gets translated to a request for uaa.cisco.com. The error is coming back from the gorouter, so

Hi, Can you please share your deployment manifest. There is something strange going on because for some reason UAA requests are being routed to *uaa.cisco.com <http://uaa.cisco.com/> instead of

The main concerns I have is: * Maintaining Compatibility: If a buildpack were to make a breaking change it may be complex to know that a vendor must upgrade its integration before the user can

Hi Ricky, Fair enough, that sounds like an alright plan for now. If you decide to reenable SSL in the future and run into these problems again, please don't hesitate to let us know and we can try to

Dear CF Community, The following proposal describes an import-path service for Cloud Foundry's Golang code repositories, and is submitted for your questions and feedback. This service would provide a

Hi Mike, You make a great point, and the question of "where should the responsibility live" is something we debated quite a bit, and even experimented with on a few different occasions. You're right

Thanks, Omar.

Hi Michal (sorry for late response.. I caught you on Slack as well, but responding to dev list) Yes we have recently added a stage in our continuous delivery pipeline to catch performance

Thanks! That helps a lot. Looks like (from slack chat and pivotal tracker) that the routingteam already has a job set-up which runs perf. tests each hour and posts results to datadog, which is

Hi Ranga, Apparently this is related to the following issue: https://github.com/cloudfoundry/cloud_controller_ng/issues/570 I hope this gets fixed in the new release. Regards, Omar

I've tried with version 3215 stemcells - still same issue. | bosh-vsphere-esxi-ubuntu-trusty-go_agent | ubuntu-trusty | 3215*

Is a goal of this work to run pure data services like PostgreSQL or Redis inside "application instances"?

Hi I am using cf-231 . After deploying, I can set cf endpoint. But I could not login While logging, it gives me the following 404 Not Found: Requested route ('uaa.cisco.com<http://uaa.cisco.com>')

This proposal describes the changes necessary to the Service Broker API to utilize the new Volume Management features of the Diego runtime. It contains examples of how services can provide a variety

Logs from /var/vcap/data/sys/log/nginx_ctl.err.log: [2016-04-05 21:40:34+0000] ------------ STARTING nginx_ctl at Tue Apr 5 21:40:34 UTC 2016 -------------- [2016-04-05 21:41:30+0000]

Hi, I just deployed v233 in a vSphere environment. Both api_z1 and api_z2 are failing. Any help would be appreciated. Stemcell version: | bosh-vsphere-esxi-ubuntu-trusty-go_agent |

Sounds like a new issue. Can you start a new mailing list thread? Thanks, Amit TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

An interesting idea. I see the licensing of agent binaries and upgrading of agent binaries as a real problem that needs to be solved. I like the idea of the brokers providing binary agent downloads

Hi John, The point of seeding is so that there aren't two decisions (code paths) for requests to create a route. Seeding the database requires no changes to route creation logic. Would anyone else

Hi there, This feature narrative [1] looks to propose a new method for delivering service-agents. This new and exciting feature would enable an ecosystem of third-party developers to more easily