Community

What is the difference between stopping-and-deleting an orchestration and force-deleting it?

orivej@gmx.fr
What is the difference between stopping-and-deleting an orchestration and force-deleting it?

An orchestration which is not in stopped state can't be deleted.

Orchestration is a specification of how you want objects (compute, network, storage, cloudservices, etc..) to be orchestrated across your private an public clouds. You can specify dependencies, sites -private/public clouds, policies etc ...

Adding an Orchestration:
You save the orchestration specification in Nimbula Director

Starting an Orchestration:
This creates objects specified in the orchestration. instances, storage , cloudservices etc ...

Stopping an Orchestration:
This cleans up all the objects as specified in the orchestration.

Deleting an Orchestration:
You can only delete an orchestration when it is in stopped state. When you stop an orchestration, it deletes all the objects in the orchestration.

Force-Deleting an Orchestration:
When you force delete an orchestration, you do not wait for all the objects in an orchestration to be deleted. You may have to manually delete the objects in an orchestration.
The recommended way is to stop an orchestration and then delete it.

Thank you, this cleared my understanding. You perceive an orchestration as a simple specification object protected from deletion until the effects of executing it are undone, rather than a complex object encompassing all the objects it governs which cleans them in order to be deleted itself.

orivej@gmx.fr
Thank you, this cleared my understanding. You perceive an orchestration as a simple specification object protected from deletion until the effects of executing it are undone, rather than a complex object encompassing all the objects it governs which cleans them in order to be deleted itself.

Actually, an orchestration is also what you mention. It can encompass a large number of complex objects, and do all the creation and clean-up of those objects upon receiving the "start" and "stop" commands. If you have any objects in your orchestration, those will be created when the orchestration is started, and deleted when the orchestration is stopped. You can even specify relationships so that some objects are made sure to be present before other objects are created. See around p47 of our User Guide for more information.