OneView 7.1 Migration Feature - license check makes migration very complicating

[Vampire25]

I am migrating all of our servers from oneview 6.6 to 7.1 with usage of migration feature to get a clean setup of license usage and server integration. So during setup of 7.1 I added all license keys to oneview 7.1.

Now when I migrate the servers on some servers migrations stops because of license key already presented in oneview 7.1 during migration BUT the license key is NOT used (available capacity 1 from 1).

So I have to manually find out the used license key in 6.6 via rest api (very very complicated) and then have to find out the rest number of license key in 7.1 and delete there the license key via rest api.

So what the hell is this so complicated ?!? Would be very easy to check during migration if license key is still "free" and "overwrite" the key during migration so that it is then used. Maybe a feature for next minor release ??

[support_s]

System recommended content:

1. HPE OneView 7.1 Release Notes

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[ChrisLynch]

So I have to manually find out the used license key in 6.6 via rest api (very very complicated) and then have to find out the rest number of license key in 7.1 and delete there the license key via rest api.

In the OneView 6.60 release, we added a new license view.  When you are in the Licenses panel, there is a report in the Actions menu.  You can then find the servers associated with specific license keys, and show the entire license key.  You copy it from there and can then add it to the target appliance.

New View License Details option in the Actions menu, introduced in HPE OneView 6.60.

Sample output of license details, including full license string and assigned server resources, introduced in HPE OneView 6.60.

We spent a long time discussing how this experience should behave. While we cannot cover all use cases, it is a complex process.  Especially when AKA or Flex licenses are used.  We do not want to add undo burden to customers where we inadvertantly add more license capacity then customers were entitled to (the total license capacity).  Appliances do not share license pools, nor were they intended to.  So ensuring keys and consumed quantity is "migrated" correctly was top of mind.

Would be very easy to check during migration if license key is still "free" and "overwrite" the key during migration so that it is then used. Maybe a feature for next minor release ??

We do that already.  We validate if the key was migrated previously.  We don't necessarily "overwrite" the key, rather the migrated quantity.  You can override that migration check by manually copying the license key using the process I outlined above.  Just know that we won't keep track of "migrated" quantity.  It is up to you to manage that.