We recently upgrades from 222 to 228 and saw a change we'd like to know the reason for. Looking at the generated uaa.yml for the job's config, in the newest version, oauth.client.autoapprove only

HI Ponraj, Yes, for that specific API call the CC will internally be sending a request to the UAA for user information. That extra request is probably what you are seeing. - Chris

Hi Shashank, We're all pretty eager to start messing about with data services via containers vs. relying on BOSH-provisioned VMs. There's a lot we could do to move forward, but the real sticking

Hello Daniel, Thank you for your response. Thanks, Sam

The cell VMs are where your actual applications run, so redundancy and capacity are two scenarios that come to mind where you'd have multiple cells. Dan

I believe that this is the diego database. See here. https://github.com/cloudfoundry-incubator/diego-design-notes#components-on-the-database-vms (2) In generated manifest xml diego.xml, I saw

Hi, We found that /v2/organizations/4df92169-5b8d-489b-ba0f-7114168aa476/users takes more response time compared to other org retrievals

Yes. More precisely the Goclient. Thanks

Ok, hidden too deeply ;-) And this call is using inline-relation-depth=2 for this purpose? Current release used is logsearch-for-cloudfoundry v7 Sent: Donnerstag, 21. Januar 2016 09:43 To:

It helped, thanks a lot!

They use firehose-to-syslog as ingestor

Yes – we use logsearch and logsearch-for-cloudfoundry bosh releases Sent: Donnerstag, 21. Januar 2016 09:25 To: Discussions about Cloud Foundry projects and the system overall.

Are you using logsearch ?? or just normal ELK stack ? wrote:

Hi Gwenn, We use ELK connected through firehose ingestors for app logs and syslog ingestors for cf logs. No firehose-to-syslog however. Thanks Sent: Donnerstag, 21. Januar 2016 01:37 To: Discussions

Client IP would be helpful, if there is a way to actually get the "real" IP. Nginx.access.log shows the origin of the http request - in our case unfortunately the nat translated IP of the (hardware)

inline-relations-depth are already deprecated. You need to work on supporting multiple call.

I have another question, in diego.xml, I saw cell has two jobs "cell_z1" and "cell_z2", what is the difference between them? in which scenario I need use cell_z2? - instances: 1 name: cell_z1

I have another question, in diego.xml, I saw cell has "cell_z1" and "cell_z2", the difference I saw is that network and resources are different, what is the cell_z2 for? - instances: 1 name:

Hi, I am making REST API call to list spaces "/v2/organizations/orgGuid/spaces?inline-relations-depth=1". Response will list all the space relations such as array of

Hello, I read document http://docs.cloudfoundry.org/concepts/high-availability.html today, there are several questions as below, please help to review and answer these questions: (1) In "Scalable