New application instance with same EBS mySQL DB

[werner5471]

I'd like to deploy a second application instance which uses the same mySQL DB as an existing one (to allow for an application update without downtime). The DB is located on an EBS volume, so I chose "existing EBS volume" for the deployment.

However the deployment fails with the log messages below. I guess even using an existing EBS volume means that still a new DB is tried to be created.

Is there a way I can configure the deployment to use the existing DB on the existing EBS volume?


---------------- START --------------
Executing command: Mon Oct 11 04:38:43 EDT 2010 : ssh on ###############.eu-west-1.compute.amazonaws.com: dos2unix|bash
Executing command: Mon Oct 11 04:38:44 EDT 2010 : ssh on ###############.eu-west-1.compute.amazonaws.com: dos2unix|bash
installing ...
Thank you for using SpringSource tc Server!
Executing command: Mon Oct 11 04:38:48 EDT 2010 : ssh on ###############.eu-west-1.compute.amazonaws.com: dos2unix|bash
Executing command: Mon Oct 11 04:38:50 EDT 2010 : ssh on ###############.eu-west-1.compute.amazonaws.com: /sbin/service mysqld stop
Stopping MySQL: [FAILED]

----------------- END ---------------

[werner5471]

Thinking it over, I guess that multiple connections to the same DB are not possible using EBS but rather using Amazon Relational Database Service (RDS).

Is it possible (or planned) to use RDS via CloudFoundry? Or would I just choose "local" and configure the RDS connection data in my application?