Auto-migration does happen, but at some point we end support for certain versions. Upgrading to 211 will automigrate your Postgres to 9.4.2. Upgrading to 230 will automigrate that to 9.4.6.

Hi Maggie, First off, please be sure to backup your data in case anything goes wrong during an upgrade. Also, do note that while private vendors of Cloud Foundry may support upgrades between several d

Hi Stefan, Mike, For real applications, would you want a common 503 page for all applications on the platform, or would your different applications have different custom domains, with custom 503 pages

Hi William, Yes, this looks like a mixup between domain and system_domain. Both should be the same value, system.domain.com. The two separate properties exist for historical reasons, we plan to reduce

Hi Yitao, I would recommend either using manual networks, or following the GitHub issue Ben R created above to see if the BOSH team can figure out the root cause of this issue with dynamic networks. B

That other thread Rob and Alvaro just mentioned currently leaves open the question of why metron_agent worked when deployed from Micro BOSH on stemcell 3160 but started giving this error message on 31

This will not work with dynamic networks. Many jobs in cf-release rely on data from BOSH to determine their IP so that configuration files can be rendered up-front by the director rather than at runti

Orchestrating a raft cluster in a way that requires no manual intervention is incredibly difficult. We write the PID file late for a specific reason: https://www.pivotaltracker.com/story/show/11201806

All buildpacks except the binary buildpack perform build at push time. Both "buildpacks" and "12-factor" came out of Heroku. That said, whether to use the Go buildpack vs binary buildpack is an intere

The UAA needs to know the router IPs to know which IPs to accept inbound requests from. If you don't care about this, you can try configuring UAA to allow requests from many IPs, and remove the static

Hi all, Sorry for the confusion, I originally added some extraneous docs to the Required Reading list that people have been trying and failing to access. Those links have been removed, the most up-to-

Hi there, Since you've also asked this question on the cf-bosh mailing list: https://lists.cloudfoundry.org/archives/list/cf-bosh(a)lists.cloudfoundry.org/thread/KPJNZSVAAOQEFLME4BERHL26DDBTDNXJ/ and

Hi all, If you are familiar with the proposed Elastic Clusters feature narrative (or even if you're not), I welcome you to take a look at the below proposal for Consul-based service discovery for comp

What's even weirder is the GET request to /login seems to do the right thing, but POST to /oauth/token gets translated to a request for uaa.cisco.com. The error is coming back from the gorouter, so it

Sounds like a new issue. Can you start a new mailing list thread? Thanks, Amit TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

Ok, I would use veritas to look at the Diego BBS, and confirm that it still thinks the app is there. You can also go onto the router and query its HTTP endpoint to confirm that the route you're seeing

Hi Raymond, Yes, you can deploy Cloud Foundry without using the Ops Manager appliance. However "Elastic Runtime", "Ops Manager", etc. are Pivotal products built on top of the open source Cloud Foundry

You can also use the "veritas" tool to inspect more of what's going on with the Diego BBS, in particular you could see if the cf apps domain is fresh. https://github.com/pivotal-cf-experimental/verita

Tom, So you're saying that none of the org/spaces shows the app or the route, but the app continues to run and be routeable? I could imagine this happen if some CC Bridge components are not able to ta

Hi all, Several releases, including cf-release and diego-release, use an AWS account belonging to the Cloud Foundry Foundation to store final release blobs. This account was accidentally closed, causi