Lifecycle Manager for Custom Cloud Resources
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current cloud management systems are limited in managing custom resources, as they do not provide mechanisms for modeling and managing resources such as users, security groups, firewalls, or load balancers, and require manual-intensive software programming for lifecycle management.
Innovation Solution
The implementation of a virtual appliance with an extensibility service that allows customers to register custom resources for lifecycle management, using a state machine and event-based messaging system, enabling declarative definitions in human-readable formats like YAML or JSON, and providing a catalog for resource management without service downtime.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If manual user input and configuration are used to install, configure, and deploy cloud components, then flexibility and customization are improved, but labor intensity and time consumption increase
Solution Approach 1:
The patent uses templates to define custom resources and their lifecycle states. These templates serve as reusable copies that can be instantiated multiple times without manual reconfiguration, reducing configuration time while maintaining customization through template parameters and variables.
Solution Approach 2:
The system allows dynamic parameter changes within defined templates. Users can modify resource parameters, lifecycle state definitions, and transition rules without recreating entire configurations, enabling flexible customization while maintaining automated processing efficiency.
2Device complexity
If manual configuration methods are used for cloud resource management, then system simplicity is maintained, but automation capability deteriorates
Solution Approach 1:
The system implements self-service automation where the lifecycle manager automatically monitors custom resources, detects state changes, and executes transitions based on defined templates. This automation handles routine lifecycle management tasks without requiring manual intervention, while the template-based approach keeps the system structure simple and manageable.
Solution Approach 2:
The lifecycle manager acts as an intermediary between users and cloud resources. It receives high-level template definitions from users and automatically handles the complex lifecycle management operations, shielding users from complexity while providing advanced automation capabilities.
3Productivity
If existing cloud management systems are used, then infrastructure resource management is improved, but custom resource management capability deteriorates
Solution Approach 1:
The lifecycle manager is designed with universal functionality to manage both standard cloud infrastructure resources and custom resources through a unified template-based approach. The same lifecycle management mechanisms handle diverse resource types, providing both broad applicability and customizability without requiring separate management systems.
Solution Approach 2:
The system segments resource management into standardized lifecycle states and transitions that can be applied universally. Custom resources are broken down into discrete state components that can be managed independently through template definitions, allowing flexible customization while maintaining efficient standardized processing for each state transition.
Data Source
AI summary
Example virtual appliances disclosed herein include processor circuitry to accept a resource definition of a custom resource to be executed in a cloud computing environment. Disclosed example virtual appliances also include a lifecycle manager to manage a lifecycle of the custom resource based on a state machine. Disclosed example virtual appliances further include a database to: (i) query the lifecycle manager for a set of operations available to execute in a current lifecycle state of the custom resource; (ii) update a catalog item for the custom resource to present the set of operations available to execute in the current lifecycle state of the custom resource, the catalog item created based on the resource definition of the custom resource; and (iii) in response to selection of a first operation in the set of operations, send a message to cause the processor circuitry to execute the first operation.