SAP LaMa deprovisioning workflow - system destroy
The following figure highlights the main steps executed with the system destroy workflow.
To decommission a cloned system, it must be stopped and prepared in advance. Afterwards the system destroy workflow can be started.
In this example, we run the system destroy workflow for the system created before. We select the system in the System View screen and start the system destroy workflow under Destroy Processes.
All the mount points maintained during the provisioning phase are shown here and are deleted during the system destroy workflow process.
No virtual hostnames are deleted because they are maintained through DNS and have been assigned automatically.
The operation is started by clicking the execute button.
SAP LaMa now performs the deletion of the volume clones and deletes the configuration of the cloned system.
You can monitor the progress of the clone workflow under the Monitoring menu.
By selecting the Delete NetAppClone task, the detailed log for that step is displayed. The execution of the Ansible Playbook is shown here. As you can see, the Ansible playbook
netapp_lama_ServiceConfigRemoval.ymlis executed for each HANA database volume, data, log, and shared.