Following up on my previously posted config, I found the following message in /var/vcap/sys/log/cloud_controller_ng/cloud_controller_ng.log (The error log was empty... ): Problem is that I don't

Hello Ronak, I have used XIP. It does not seem to have helped. I got much the same result. API node does not complete the job. looking at the vcap logs looks similar to above: cloud_controller_ng_ctl

Ignore me, I can't read... looks like this is using that already. Nice!

Have we abandoned plans for the import path service Eric proposed back in April? If not, aren't we just going to have to update all our imports again once that rolls out?

Need more info. What's the command(s) you're running? What's the full output from the command(s)? What is the output of `cf target`? Is Diego supported / available on that target? Dan

I tried enabling the diego for the php app and I am not able to start the app after enabling. I get the below errors: Server error, status code: 500, error code: 10001, message: An unknown error

I got past the api_z1 failure by adding: - name: consul_agent release: cf to the api_z1 section. I'm now confused by having to remove the other lines. I will need to test this out. Tom

you can tell when you're on DEAs by comparing the notes that dan referred to here [1]. for example, if you have the env variable VCAP_APP_PORT then you're likely on a DEA

I've found when doing this the easiest thing to do is to use sed to remove existing imports followed by goimports -w on the same files. KH

Congrats on making it official! I assume you folks are going to build some scripts or some "go fmt -r" to find/change all import paths that need updating. If you find anything useful that other

Excellent!!!. Good luck.

Installed the sample app and tried it on Bluemix and I don't see CF_INSTANCE_GUID or INSTANCE_GUID in Environment section. How do I know if its Diego or DEA ?. Thanks, Vinod

You can use xip.io for temporary domain, try generating manifest again and deploy.

That was the problem. I removed the MySQL profile and it worked. Thanks!

That stuff has always technically been foundation code and should have moved out of pivotal-golang into cloudfoundry-incubator long ago. Back when we made the org the rules about how orgs are

As I was not planning on sigining exposing this deployment to the outside, I was planning on using HAPROXY through it's floating IP. I did not set a domain, because I have not yet interfaced with my

Hello Eyal, Can you paste the domain properties from your final manifest ( system domain & app domain part). Thanks Ronak

I know there are some changes to the env variables between DEAs and Diego. I don't know exactly and don't have a DEA to

Hi all, We are currently in the process of moving all of the Diego repositories from `cloudfoundry-incubator` to the `cloudfoundry` organization. Specifically we are moving the following

Hello Amit, I have removed the lines that you have marked. Now I am getting a different error... Process 'consul_agent' running Process 'cloud_controller_ng' Connection