About this time last year, I published a report on cloud service management (Enabling IT’s Transformation to Cloud Service Provider) where I outlined the software components needed to become a cloud service provider on-premises. Primary capabilities include orchestration and automation but also things like CMDB, federation, and chargeback. Like everything in this industry, there has been a lot of change in the past year, which I will cover in detail in the update to the CSM report later this quarter. In the meantime, I thought it would be useful to write about some of the trends I’m seeing in this space:
· Hybrid Isn’t Even Table Stakes – Last year I thought it was goodness when I saw a CSM company building functionality that supported an IT department being able to manage on-premises ‘private cloud’ and off-premises ‘public cloud.’ Over the past year that has evolved to requiring the ability to manage multiple cloud types in on- and off-premises. For example, a company may have an MS Azure cloud as well as a VMware cloud on-premises and public cloud off-premises with a VMware cloud and AWS resources on Amazon’s cloud. This means that the CSM software has to be able to manage all of these resources and be able to provide a unified dashboard, rationalize pricing methods, and potentially a way to move workloads seamlessly between clouds.