Cleanup

claw exposes two different cleanup mechanisms. One mechanism is used to undeploy all deployments on a Cloudify manager, the other mechanism is used to remove all IaaS resources in an environment.

Deployment Cleanup

To undeploy all deployments on a claw based Cloudify manager environment, run:

$ claw cleanup-deployments CONFIGURATION_NAME

This command will iterate all deployments on the Cloudify manager and for each deployment the uninstall workflow will be executed, the deployment will be deleted and its blueprint will be deleted.

To cancel currently running executions of deployments before the undeployment process, pass the --cancel-executions to the claw cleanup-deployments command.

Caution

Internally, claw cleanup-deployments will pass --ignore-live-nodes to the underlying cfy deployments delete commands. You should be aware of this when using this command.

IaaS Cleanup

To remove all IaaS resources on the IaaS used by a certain configuration, run:

$ claw cleanup CONFIGURATION_NAME

Caution

This command removes all IaaS resources it finds (with a few exceptions).

Don’t run it on a shared tenant/account.

Note

At the moment, the claw cleanup command is only implemented for openstack based environments.

Note

On openstack, claw cleanup will not delete key pairs by default. To make the claw cleanup command delete key pairs, add delete_keypairs: true to the relevant handler configuration. For example:

handler_configurations:
  some_openstack_env:
    ...
    delete_keypairs: true

Note

If a certain configuration is passed to claw cleanup and it doesn’t exist, it will be generated temporarily for cleanup purposes. As such you can use the --inputs-override and --manager-blueprint-override flags as described in Bootstrap and Teardown.