Hello everyone,
I would like to know if Nutanix NCM Self-Service supports a feature that allows setting a VM expiration option during the VM or blueprint creation request, enabling the VM to expire after a specified time interval automatically. Or if it does not support, can we schedule it on Day-2 Operation features? Thank you!
Hey,
I haven’t heard of such an option.
I would say to use the built in day-2 ‘delete’ action programmatically, via API, but I just checked it and unfortunately the App-Action-Run API method won’t let you use ‘action_delete’ nor ‘action_soft_delete’. This API call will fail with code 422 when trying to use one of them.
The only solution I can think of, is to create a runbook that queries all the applications via API, and get the “created_time” attribute. (it’s a unix time format).
Then, find the ones that passed the expiration time and send a report by mail.
Using this report you can go to the applications and use the day-2 ‘delete’ action on them.
Hi
NCM Self-Service does not currently support native VM expiration options during VM or blueprint creation requests. There’s no out-of-the-box setting to automatically expire or delete a VM after a defined period.
However, a workaround is possible:
You can create a runbook to regularly check the VM or application created_time via API.
Based on this, you can generate a report to identify expired VMs.
From there, you’d need to manually apply a Day-2 'delete' action in the Self-Service UI, since the App-Action-Run API does not support automated delete calls (returns a 422 error).
This is a limitation today, and automating cleanup will require scripting and oversight outside of NCM’s built-in policy controls.
Always confirm with Nutanix support before making changes in production
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.