Need ability to cancel subscription in HCM without invoking any lifecycle action

[sandeep_]

Some may want to use HCM/ CSA to automate the deployment of Cloud servers, but may not want to manage subscriptions - modify or any other actions, including the automation of undeployment only for certain subscriptions. Hence a feature that would provide the ability to cancel subscription an active subscription that does not trigger any OO flows during cancelling would be helpful. This would help with managing the licenses more effectively and use the complete Cloud server lifecycle management only for those who require.

[Spiff]

I think this would be a great idea - provides the customer with much needed flexibility.

[Alex Savio]

Can you please explain how does the license get managed effectively by not allowing the customer to de-provision the instance which will give back that license unit? IMO, this will make the customer keep the license consumed always, right? By the way, we have a road map item to customize the service lifecycle management which may allow this kind of capability.  However please provide your inputs as requested

[Spiff]

I have 2 use cases:

4 years ago, in order to bump up the CSA numbers, our company paid HPE to migrate around 500 servers into the CSA solution - in effect, taking 500 servers that were not spun up by CSA, and allowing the servers to be managed by CSA.  The decision was made about 6 months ago not to use these servers as "cloud servers" - in effect, reversing the decision from 4 years ago.  We now have thousands of cloud servers - these 500 were never treated the same as a cloud server (and when subscription migration to Propel occurred 2 years ago, they were not brought over - technology challenges).  Bottom line: we have 500 servers that are not in Propel, are not managed by CSA/HCM today - but are still consuming a license.

We have an internal customer who wants to deploy servers via HCM, but wants to manage the subscriptions outside of any automated solution.  They would like to use a license to spin up the server, then have that license available to spin up another server in the future.  They do not wish to use the added benefits of HCM outside of spinning up the server.