Products for Cloud Ops vs. Traditional Ops

0 Comment

Don’t know how I missed this one. Highly recommended. I completely agree that there are new winners and losers because of cloud. For example, self-service and the catalog come to the forefront. Lifecycle and subscription management also become important.

On the other hand the traditional CMDB? Not so relevant since so many services become abstract; what elements do you need to track?

As for assets? They become subscriptions, which are financial liabilities.

Anyway here’s the rest… I recommend it.

I see roughly five dimensions for how ITSM product use might shift within a cloud model:

• Overall increase in use, due to IT Operational needs created by the automation and dynamics within a cloud infrastructure. With more dynamic/unpredictable resource requirements, some ITSM tools may become more valuable than ever. For example, take Billing/Chargeback. Clearly any provider of a public (or internal) cloud will need this to provide the pay-as-you-go economic model, particularly as individual resource needs shift over time. Same clearly goes for tools such as Dynamic Workload Brokering, etc.

• Overall decrease/obviation of need, due to the the automation/virtualization within a cloud infrastructure. As automation begins to manage resources within the cloud, certain closely-monitored and managed services may simply be obviated. Take for example application-specific Capacity Planning; no longer will this matter to the degree it used to – now that we have “elastic” cloud capacity. Similarly, things like event correlation _might_ no longer be needed — at least by the end-user — because automation shields them from need to know about infrastructure-related issues.

Tags: , ,