In a previous post I began discussing the internal software architecture of private cloud implementations. Individual private cloud components (such as UCS blade servers, networks, and storage) need to consider the use cases and workflow needs of the IT organization. The IT workflow software is the critical user interface for seamless orchestration of private cloud components.
When designing the software architecture for a private cloud implementation, one architectural component becomes central: the CMDB, or configuration management database. For example, if a storage device wants to be an effective member of a private cloud, it needs to somehow register itself with the CMDB and keep its' system state up to date. All IT operations mapped onto the storage device should begin at the CMDB and flow down to the device itself.
The CMDB that EMC is deploying as the key piece in the private cloud software architecture is the Infra CMDB. The EMC acquisition of Infra nearly 18 months ago has resulted in the Infra CMDB becoming the "center of the cloud" when it comes to private cloud implementation. All private cloud planning, discovery, control, monitoring, and audit flows through the Infra CMDB, which is characterized by four major entities:
- Services: the private cloud services provided by IT to customers (e.g. email, app support). These entries become the service catalogue of the private cloud.
- Configuration Items (CIs): the components that need to be managed to deliver a set of services from the private cloud.
- Structures: abstract entities that serve as "containers" for a group of CIs (e.g. a department or a server room).
- Baselines: The overall and complete configuration of a private cloud at a given point in time.
These four structures are all common and familiar to those well-versed in the ITIL standard. What's unique about the Infra CMDB is the remaining architectural elements that surround it:
- Dynamic application discovery (based on SMARTS technology) . This architectural piece discovers new applications and inserts them into the CMDB.
- Automated application mapping . This architectural piece maps applications to their underlying CIs in the private cloud.
- Fault monitoring (also based on SMARTS). Alert storms between private cloud components are analyzed and resolved to the offending CI or event; the CMDB is updated appropriately.
- Blueprint display: a graphical tool to display the private cloud blueprint and enable capacity planning activities.
- Change configuration: the software responsible for moving a private cloud away from a baseline configuration and onto an upgraded configuration.
What's basically occurring here is that the Infra CMDB is serving as the central convergence point for a set of applications/acquisitions in EMC's technology portfolio: Infra workflows, Voyence, ECC, SMARTS, nLayers, Application Discovery Manager (ADM) etc., will communicate with and through the CMDB using RESTful interfaces. The sum total of this converged architecture is known as Ionix.
The individual components of Ionix still function as standalone products. When working together for private cloud, Infra is known as Ionix Service Management , SMARTS is known as Ionix IT Operations Intelligence, ECC and Voyence are known as Ionix Data Center Automation and Compliance, and ADM is known as Ionix Service Discovery and Mapping.
These tools, when converged on a common CMDB and common protocols, lay the groundwork for a much more seamless and automated management of a private cloud. There are more tools and products that fall into these four Ionix categories (more to come in future posts).
Today's Ionix Data Center Insight (DCI) press release clearly mentions private cloud. A careful reading reveals many of the same themes that I mention above: auto-population of the CMDB, integration of the CMDB with other Ionix assets (e.g. Ionix ADM and ECC), and improved mappings of VMs to their underlying resources. The new-and-improved CMDB also moves customers closer to the vision of a much more highly federated and distributed CMDB.
Looking for a starting point for discussions about private cloud software architecture and implementations? Start with the CMDB.
Steve
http://stevetodd.typepad.com
Twitter: @Steve Todd
EMC Intraprenenur
Comments