Update exisiting Cloud Foundry Deployment to a newer version (cf-release + cf-services-release)

[Julian Weber]

Hey,

maybe anyone can bring light into our update questions.

We are running a Cloud Foundry release from the old cf-release repository (commit: ea61ec6f8fee73b9aeb5724ca5cdff10f0fe5320; Release: appcloud-131, IaaS Layer: vSpere) with the included services. We have some users running all kinds of applications including service instances (MySQL, PostgreSQL, MongoDB, RabbitMQ, Redis). 

We would like to update our installation to a recent release where Cloud Foundry's core components and the service releases (cf-services-release, cf-services-contrib-release) are separated from each other. Right now our fear is to loose user data when deploying a new release as an update.

Could anyone give us some advice on how to update our running installation without loosing important data, or should there be no problems when combining the new releases in a deployment file listing all already running jobs from the new separated releases (cf-release, cf-services-release, cf-services-contrib-release)?

We already know how to bring the different jobs and packages from different releases together, but we would like to hear some thoughts about this before updating our installation.

Regards,

Julian Weber

--

anynines.com