The cloud has changed everything. The way we build, deliver, and manage services looks nothing like it did when ITIL first emerged.  Traditional frameworks were designed for centralized, relatively static infrastructures. Today, most organizations live in the dynamic, distributed reality of cloud computing - where scalability, automation, and speed rule the day. ITIL 4 bridges that gap beautifully. Its Service Value System (SVS) connects governance, Agile, Lean , DevOps , Site Reliability Engineering (SRE) , and continual improvement into one integrated approach. I often describe ITIL 4 as moving from rigid processes to flexible, value-driven practices . Nowhere is that shift more evident than in the cloud. New Realities in Cloud Environments Cloud computing gives us extraordinary power: elastic scalability, self-service provisioning, and global reach. But it also introduces new challenges. Resources appear and disappear in seconds. Ownership lines blur between custome...

The question about how to manage virtualization and configuration items pertaining to the Cloud continues to challenge service management practitioners and managers who are trying to strategize and architect a working solution to provision business services.  Some would say the idea of the CMDB (Configuration Management Database) is dead because we use the infamous “Cloud”. Let’s start with a refresher about the structure and purpose of a CMDB and system and then move into how that relates to the management of virtual Configuration Items or Cloud services. Configuration Management System The key to a CMDB, or the sets of data that comprise your broader Configuration Management System (CMS), is “Relationships”.  When provisioning a service, the service provider must be able to manage and control all of the items necessary to produce “Value” to the consumer.  All elements in the end to end service that need to be managed and controlled are referred to as a Conf...

As business organizations opt for support from the cloud to provision Software, Platform, or Infrastructure services the need for warranty through the service value chain becomes paramount. Service warranty is gained by achieving specified levels of availability, capacity, continuity, and security.  The dynamic, nature of the business and varied demand from multiple customers and user profiles must be considered when defining and investing in cloud architectures.  Each customer will expect that only their application or service will be delivered to users when in fact multiple customer and user communities could be leverage from the scalability and shared resources in the cloud. Availability/Capacity and the Cloud Service providers must gain assurance that multiple instances of the same application are delivered in a scalable manner.  In order to ensure availability and leverage capacity on demand additional tools and technologies such as load balancing, server ...