What is the definition of these next_dea values and are the officially documented somewhere? staging_disk_limit_mb: 6144 staging_memory_limit_mb: 1024 disk_mb: 2048 memory_mb: 1024

Hi Mike, We have just been made aware of a potential problem with the database migration to encrypt an app’s specified buildpack at rest. It was known that it would cause API failures, but we also

Just hasn't been scheduled yet. No known issues at this time. Best Amit

We're about to begin the process of testing and rolling out 241 to our environments and I noticed that PWS still hasn't been upgraded to 241 [0]. Is there a particular issue with 241 causing the delay

Hi, Renaming the app while keeping the route is what the autopilot plugin does: https://github.com/contraband/autopilot James

Hi, I am trying to write a blue green deployment script, during which I'll be renaming my blue app to some other name without doing any change in blue route. Can this cause my application to be

Hi All, The AWS account used by the deprecated Lattice project will be deactivated on October 1, 2016. If you still use AMIs that are hosted by that AWS account, please copy them to your own AWS

At approximately 10:45am PST there was a hardware issue at the Linux Foundation's Oregon data center. This issue resulted in downtime across all Linux Foundation web properties and DNS services which

We believe that services have been restored now. wrote:

All, Impact: cloudfoundry.org does not resolve, vendors pointing to buildpacks.cloudfoundry.org are seeing failed `cf pushes` The Linux Foundation DNS nameservers are down. They are working on a

https://github.com/dingotiles/dingo-postgresql-release/releases/tag/v0.10.0 Dingo PostgreSQL is a "batteries included" service broker for Cloud Foundry that provisions dedicated highly available

Hi Rania, I found a Makefile in the spiff repo and learned that it's a go application: https://github.com/cloudfoundry-incubator/spiff/blob/master/Makefile So, you could build for windows env with

Hi Tomoe, We have moved along from this step and now stuck on step 4 while installing spiff in the below page: http://docs.cloudfoundry.org/deploying/boshlite/create_a_manifest.html we couldn't

Hi Rania, bin folder is in the bosh-lite repo[1] which you must have cloned to the host, not on the VM. [1]: https://github.com/cloudfoundry/bosh-lite/tree/master/bin Best, Tomoe

Answered in the github issue where this was copied from: https://github.com/cloudfoundry/cloud_controller_ng/issues/669#issuecomment-242437165 Nicholas Calugar Product Manager - Cloud Foundry

I think the problem was indeed related to issue 633. When I used another method to generate the rsa key pair for jwt (sadly the docs do not specify how this should be done) and deployed a new release

Example: api.example.com - [30/Aug/2016:19:39:20 +0000] "GET /v2/organizations?order-by=name HTTP/1.1" 500 195 "-" "go-cli 6.21.1+6fd3c9f / linux" 10.120.8.132, 10.120.7.14, 10.120.7.16

Yes, I see related requests in nginx_cc/nginx.access.log.

yes, I see related access requests in nginx_cc/nginx.access.log.

There has been no recreation of any VMs during this testing. The time span of the log file is within my tests. There is no 500 error and no matching ID. There is this issue that is