I updated my bosh (using bosh-init) with enabling ignore_server_availability_zone. but it still failed when I deployed my cf. Anything suggestion? openstack: &openstack auth_url:

Dan, We announce the PWS's CF version on status.run.pivotal.io: About This Site If you encounter any issues please contact support(a)run.pivotal.io. Pivotal Web Services is the latest public

I was testing an app on Diego today and part of the test was for the app to fail. I simulated this by putting some garbage into the `-c` argument of `cf push`. This had the right effect and my app

We recently experienced a similar issue. Not sure if it is the same. But it was caused when we moved the nfs_mounter job template to the first item in the list of templates for the CC job. We moved

We have environments on stemcell 2977 that are running well. We have an environment using NFS that ran into that same issue and we have this bug open. [1] Specifying the nfs_mounter job last should

We recently experienced a similar issue. Not sure if it is the same. But it was caused when we moved the nfs_mounter job template to the first item in the list of templates for the CC job. We moved

Hi, Corentin, Diego, like the DEAs, supports evacuation of LRP instances during controlled shutdown of a cell VM (the analog of a single DEA in Diego's architecture). If you're using BOSH to deploy

The script that is executing at the time is: https://github.com/cloudfoundry/cf-release/blob/master/packages/uaa/pre_packaging#L36 So what my suggestion is to test if this works is that you can

Some other questions: - is there a consolidation mechanism? From what I can see from the videos, Diego is only doing load balancing when allocating an application to a DEA. What is more important to

I need some help here. I have been working on this for a week now and have researched the entire web but I couldn¹t find any relevant resource to this. 1. Lib/warden/container/linux.rb ­ I am

Hi, I'm experiencing a weird situation where api and api_worker jobs fail to update through bosh and end up being reported as "not running". However, manually running "monit start

I have a small environment with old version as 183 It only has one DEA, having couple apps running on that, it suddenly stop working when deploying apps (staging) without any obvious error and

Try telling BOSH to ignore what AZ the server is in when provisioning disks: https://github.com/cloudfoundry/bosh/blob/master/release/jobs/director/spec#L395 It will default to cinders default AZ

Hi, I am trying to deploy cf into Openstack with multiple computing nodes. Computer node 1: has all openstack services running, including cinder service (az1) Computer node 2: has computing

The cf-release v210 was released on May 23rd, 2015 Runtime - Addressed USN-2617-1 <http://www.ubuntu.com/usn/usn-2617-1/> CVE-2015-3202

Thanks Ivan! That is exactly what I was looking for.

For all the loggregator processes, you will be able to find their configuration properties in their respective spec and ERB files in

Hi all, I've been trying to figure out an issue here while upgrading to 210 from 208. It seems that a requirement has been added to the deployment manifests for a "metron_agent.deployment" property

This Java native memory leak debugging war story from a Twitter engineer is very interesting: http://www.evanjones.ca/java-native-leak-bug.html Tweet is

Hello all, As a follow on to the original notice [1], I wanted to clarify that we plan to remove the lucid64 stack from cf-release with the next final cf-release that we hope to make available in the