Topology-Based Cloud Service Lifecycle Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing blueprint approach for designing, provisioning, deploying, and managing cloud services lacks the ability to describe physical topologies, making it difficult to associate metadata and policies, and is not intuitive for designers, leading to challenges in using blueprints as models for applications or infrastructure templates.
Innovation Solution
The introduction of architecture-descriptive topologies that define the physical architecture of a cloud service, allowing for the association of nodes with relationships, properties, actions, policies, and lifecycle management actions, and the use of a cloud service broker that supports both topologies and blueprints with a unified lifecycle management engine.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If a blueprint approach is used for designing and managing cloud services, then service provisioning can be automated, but the ability to describe physical topologies and associate metadata is lost
Solution Approach 1:
The patent merges the blueprint approach with architecture-descriptive topology modeling, combining service provisioning automation capabilities with physical topology description. The topology model integrates nodes, connections, and metadata association while maintaining automated provisioning workflows, thus eliminating the need to choose between automation and topology description.
Solution Approach 2:
The architecture-descriptive topology serves multiple functions simultaneously: it describes physical architecture, associates metadata with nodes and connections, enables policy attachment, and supports automated provisioning. This multi-functional model replaces the single-purpose blueprint approach, allowing the same structure to handle both automation and descriptive requirements.
2Loss of information
If architecture-descriptive topologies are introduced to define physical architecture, then physical topology description and metadata association improve, but system complexity increases
Solution Approach 1:
The topology model is segmented into distinct components: nodes representing infrastructure elements, connections representing relationships, metadata associated with each node and connection, and policies attached to specific topology elements. This segmentation allows complex physical architectures to be modeled through simple, reusable building blocks, reducing perceived complexity while improving descriptive capability.
Solution Approach 2:
The patent introduces a lifecycle management engine that acts as an intermediary between the topology model and the cloud service provisioning system. This engine handles the complexity of interpreting topology descriptions, associating metadata, enforcing policies, and coordinating provisioning actions, thereby shielding users from underlying system complexity while enabling rich topology modeling.
3Ease of operation
If nodes are associated with relationships, properties, actions, and policies in the topology model, then lifecycle management capability improves, but the complexity of managing these associations increases
Solution Approach 1:
The topology model employs dynamic node types and relationship categories that can be configured based on specific cloud service requirements. Nodes can represent different infrastructure elements (computing, storage, networking) with appropriate properties and allowed actions, allowing the model to adapt to various scenarios without requiring a completely different structure for each case.
Solution Approach 2:
The patent uses parameter-based node definitions where each node type has a set of configurable parameters (properties) that define its characteristics, allowed actions, and associated policies. By changing parameters rather than restructuring the entire model, the system can manage complex node associations while maintaining a consistent, manageable framework across different cloud service scenarios.
Data Source
AI summary
A method of managing the lifecycle of cloud service modeled as a topology includes, with a processor, generating a topology, the topology representing a cloud service, associating a number of lifecycle management actions (LCMAs) with a number of nodes within the topology, associating a number of policies with a number of nodes within the topology, the policies guiding the lifecycle management of the nodes, and with a lifecycle management engine, executing the topology.