sorry, my university webmail is making fun of me, here it

Sorry, but I don't see any logs attached. ------------------------ Alex Lomov *Altoros* — Cloud Foundry deployment, training and integration *Twitter:* @code1n <https://twitter.com/code1n>

Hello, the log is into the api_* folder in my previous email,  I attach it here too! Thank you! Michael

I am wondering about "Installing runtime (python-2.7.6)" I think only 2.7.9 and 2.7.10 are supported on the cf2linux stack. Do you specify the python version on your application ? Can you try the

Hi, there I upgraded CloudFoundry to verion 210 from 205 last week, today when I push a "hello world" python project (works before) to CF using command below: cf push python11 -p python-sample.zip

Hi, Mohamed, Thanks for reporting the problems you've encountered. As Gwenn pointed out, this has already been reported on GitHub in https://github.com/cloudfoundry-incubator/diego-release/issues/60,

What log do you have into the dir /var/vcap/sys/log/cloudcontroller_ng/ thanks? michael.grifalconi(a)studenti.unimi.it> wrote:

Missing of documentation really ? There is a lot of documentation about Diego https://github.com/cloudfoundry-incubator/diego-release

Hi, We are trying to deploy Diego on Openstack (using microbosh), since there is no clear documentation on doing that we are having several problems. The manifest that we are using is attached. The

Hi All, cf-release 213 was committed to the master branch, but has some issues during deploy and should be avoided. There is a backwards incompatible ccdb migration that will cause cloud controller's

i have not used the terraform installer, so take that with a grain of salt. because apps.54.2.3.4.xip.io will always resolve to 54.2.3.4, all calls using that domain will go out through the aws

Hello,  I attached the logs I got from 'bosh logs VM_JOB INSTANCE_N' and they looks the same as the ones I can see by manually ssh into the VM. What is the difference? I'd point you to this logs

Hi, This log are not so usefull, can you login into the VM using bosh ssh and go to /var/vcap/sys/log/ and you will see some folder and you will have some log

Hello all, I'm trying to deploy CF on top of a little OpenStack cluster but I get api and uaa VMs constantly on starting/failing status. After each 'bosh deploy' with some changes on the

Thanks Mike for the detailed notes. It seems the toolsmiths-tracker url is wrong and pointing to the buildpacks tracker, and the IF-tracker has not yet been configured for being public (I get an "You

According to their travis.yml and this commit ( https://github.com/cloudfoundry/cli/commit/cde3852c1059f3600a41400c9d1f39839005a190), 1.2.2.

Nice Thanks !

I recently used this terraform project to create a AWS cf install: https://github.com/cloudfoundry-community/terraform-aws-cf-install I uses the floating ipaddress of the public proxy as its default

Thanks again! I have deployed the same app in my Bluemix environment and seeing a delay in the response till buffer is getting full. CF version as I mentioned earlier is CF210.2 and express package

What version of Go is the CLI built with currently? Mike