I need the cf logs output from the service broker app when you issue the bind request. -Sabha -- Sabha Parameswaran Platform Engineering, Cloud Foundry Pivotal, Inc. m: +1 (415) 244-5554

Hi Parameswaran, I have tried with the inputs provided. Still I am facing the same issue. The logs are attached for your review. Please suggest. Thanks. Regards, Kumaresh

Sure Parameswaran. I will update the ServiceBinding code. I will try in our PCF environment and let you know.

Hi Jason,Thank you for the feedback. Yes, I believe that's very true and would generally be the case with production deployments. Let me add a note to the slide to include this as well. I read up on

Hi Moiz, Looks good overall. My only minor clarification is that the HAProxy configuration that you've shown is only one way to set up CF, and not necessarily what people use in production. For

I suspect you are getting tripped by new additional parameters being sent in the json payload during the bind request. Add following to the ServiceBinding code: @JsonIgnoreProperties(ignoreUnknown =

Kumaresh, Continue to check the logs even as you issue the bind to app. Dont stop just with health check. Also, the logs get buffered for a bit before they show up in the cf logs. Retry the bind

Hi Sabha, I got healthcheck passed status for haash-service-broker-app. It doesn't show errors in logs. What may be the problem? Regards, Kumaresh

Kumaresh, Marco meant you to check the logs of your Haash service broker app running on CF or elsewhere. If running on CF, issue cf logs <haash-service-broker-app> and from another window try the

Congratulations Ben! Even though I haven't worked on the cf java client for months, I am still amazed by the attention to detail given by yourself and the team. I describe the client code to others as

Hi, During a CF install on Vsphere I get a problem with the uaa service. bosh deploy returns this error: tarted updating job uaa_z1 > uaa_z1/0 (49dfbb23-64ba-4eef-9872-2dfc8fb9a9e6)

No Marco. I got above exception when attempt to bind the service instance with an app.

I understand. I'm claiming that if consul-release supports just the first two, then you don't really need the third. Can you describe a case where you would want to do the third thing on that list

At first glance, it looks like your own broker server is returning 502 when CC attempts to issue the bind request. Do you see anything which corresponds to the request in your broker's

Actually you need to build your own STEMCELL which is vmdk type as the qcow2 mainly used for KVM hypervisor -- Regards, Yitao

We use vsphere esxi as our hypervisor environment, and this environment is managed by openstack,that is to say we use openstack to manage the lifecycle of virtual machines and images and so on. Now I

/etc/resolv.conf and (b) not listen on port 53, would probably never any recursing? Sorry I did not explain myself. I did not mean that I want to implement all scenarios at the same time. I meant

Hi all, I knocked up a tiny utility that Concourse users might find handy. It takes a YAML file of variables, and runs a command with those variables in the environment. Handy if you use

Hi, I created haash service broker in out PCF environment. I created service instance for haash service and named as 'my-hash'. I can't bind 'my-hash' service instance with an app. I am getting

And finally I did a mapping of uaa.yml property names to config keys in the API, and uaa is hitting my server. Problem solved. wrote: