Cloud Automation Extensibility for Custom Day-2 Operations
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current cloud automation platforms lack extensibility mechanisms to support custom day-2 operations on cloud resources, limiting users' ability to define and implement non-standard resource actions for complex use cases, particularly in software-defined data centers.
Innovation Solution
The implementation of Action Based Extensibility (ABX) actions, such as AWS lambdas and Azure Functions, managed by cloud automation platforms like vRealize Automation, allows users to configure custom day-2 operations by integrating serverless development models, enabling users to create and manage custom resource actions through a unified interface.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If cloud automation platforms use predefined operations only, then system stability is maintained, but adaptability to custom day-2 operations is limited
Solution Approach 1:
The platform is segmented into modular components: a core automation engine that handles predefined operations, and extensible plugin interfaces that enable custom day-2 operations. This segmentation allows the system to maintain stability from the core while adding adaptability through separate, optional extensions without increasing overall system complexity.
Solution Approach 2:
The automation platform is designed with universal interfaces and standardized APIs that can handle both predefined cloud operations and custom day-2 operations through a unified framework. This multi-functionality allows the same platform infrastructure to support diverse operations without requiring separate systems, thus improving adaptability without proportionally increasing complexity.
2Adaptability or versatility
If cloud automation platforms support only standard operations, then ease of operation is maintained, but ability to handle complex use cases is limited
Solution Approach 1:
An intermediary abstraction layer is introduced between the user and the underlying complex operations. This layer provides simplified, standardized interfaces for common tasks while allowing complex custom operations to be defined through configurable templates and workflows. Users interact with simple abstractions while the intermediary handles the complexity of custom day-2 operations, thus maintaining ease of operation while enabling adaptability.
3Adaptability or versatility
If cloud automation platforms allow extensive customization, then versatility for complex use cases is improved, but system complexity increases
Solution Approach 1:
The system implements a nested architecture where simple predefined operations are contained within the core platform, while custom day-2 operations are nested as extensible modules that build upon the core functionality. This nested structure allows the system to provide basic operations with minimal complexity while enabling progressive customization by nesting additional layers of complexity only when and where needed, rather than requiring the entire system to be complex.
Data Source
AI summary
The present disclosure is related to devices, systems, and methods for extensibility for custom day-2 operations on cloud resources. One example includes receiving an indication of a resource type of a software-defined datacenter via an interface of a cloud automation platform, receiving an indication of an ABX action via the interface, associating the resource type with the ABX action to create a resource action responsive to an input via the interface, and deploying a blueprint containing a resource of the resource type, wherein the resource action is executable to modify an internal state of the resource.