Recently included with UIMp is the Service Adoption Utility.
The Service Adoption Utility was originally a standalone tool to assist customers who wanted to import environments into UIMp that had not been provisioned with UIMp.
The problem with older versions of UIMp was that there was no Service Adoption Utility and therefore all provisioning needed to be made through UIMp. This caused a whole host of issues…
If you for example added a datastore natively in Unisphere and masked it to all your ESXi hosts, it would not be visible in UIMp as part of the existing service offering. If that service offering was ever expanded, by adding a blade to the service offering, that datastore that you had manually masked to your ESXi hosts would not be automatically masked to the new ESXi host that you had just added to the service offering. This inflexibility was infuriating and was not just an issue with datastores, but across all UIMp managed components. Want to add a new VLAN to your service offering in UCS Manager? Bad idea for the same reason and until recently you could not add new VLANs to existing service offerings. This put organisations into a real catch 22 – Because UIMp was incapable of detecting or importing changes made outside of UIMp, you could no longer use the native management tools but UIMp until recently didn’t have any elasticity functionality. I spent the whole Christmas week in 2011 rebuilding our entire service offering with VCE because we wanted to add some new storage grades to our existing service offering. There was no elasticity or Service Adoption Utility at that time so we spent 5 days re-provisioning the cluster and getting it back into a production state.
Now with the Service Adoption Utility all those troubles are a distant past. You can now run a mixed environment. You can make changes outside UIMp with the knowledge that these changes can be imported back into your existing service offerings, if required.
Not only that but if you ever have any issues provisioning new datastores or VLANS, you can finish the configuration manually in Unisphere or UCS manager and run the SAU to import the changes. Not only will the SAU import the new config, but it will delete the partially provisioned objects from with UIMp. Frikkin awesome!
Before you run the service adoption utility you need to ensure the following:
- You’ve added your vBlock and all the credentials and the discovery must first be successful without any failures.
- You’ve run ‘Validate Setup’. Setup Validation must return a status of Warning or Ready. If status shows “Failed” then you will need to click this link and review the Compliance Rules that came back with a Compliance Status of “Error”.
- Ensure you have installed UIMp correctly, i.e. you’ve imported the certificate from UCS Manager, configured all your Identity Pools, Blade and Storage Grades, and added vCenter. (This is not a complete list!)
Once these are successful, you can then proceed with the Service Adoption Utility to import your existing hosts, LUNs, etc.
Note: This is best done with EMC (at least the first time), just to be on the safe side.
Connect to the UIMp SAU:
UIMp is accessed through the URL: https://uimserver/slm/sau
Select your vBlock and continue:
The tool will do a discovery of your infrastructure to determine which components are not currently included in an existing service offering.
Select Services for Adoption:
UIMp will spit out a list of Blades, VLANS and datastores for you to import. You have to assign the grades for the blades (you can see the warning ‘grade not set’ below as this has not been done yet. Datastores will automatically be imported depending on the storage pool.
Once you hit OK the adoption will commence…
And finally you should hopefully see a nice ‘Adoption Succeeded’ status as per the screenshot below. Job done!
Confirm imported Service Offerings in Administration:
Logging into UIMp you should now see the new service offering available under the Administration->Service Offering tab as per the screenshot below.
The service adoption utility has revolutionised UIMp. It single handedly takes away its major weakness – its inflexibility to co-exist with existing environments, and environments that change outside of UIMp.
Good job IONIX UIMp team!