Only the ConPaaS Director (instead of the Service Managers) is allowed to manage cloud resources (create/delete instances/volumes). Fix the context generation. Make sure that deleting an application will free all the cloud resources, irrespective of the state of the Application Manager or service managers. Make sure that the Director remains stateless by keeping all the necessary information in the Director database, so restarting the Director (apache2) does not break the applications running in ConPaaS.
This might require some polishing in terms of message format and error handling, but it is working.
I am closing this and I will eventually open another enhancement issue related to this.
Only the ConPaaS Director (instead of the Service Managers) is allowed to manage cloud resources (create/delete instances/volumes). Fix the context generation. Make sure that deleting an application will free all the cloud resources, irrespective of the state of the Application Manager or service managers. Make sure that the Director remains stateless by keeping all the necessary information in the Director database, so restarting the Director (apache2) does not break the applications running in ConPaaS.