Automated Cloud Resource Suspension and Redeployment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Enterprises face increased costs due to unused containerized applications and infrastructure in off-premises cloud environments, as existing automated shutdown procedures lead to manual reprovisioning requirements when users attempt to access inactive applications.
Innovation Solution
The implementation of automated suspension and redeployment methods that monitor network traffic, suspend inactive containerized applications, and automatically reprovision them upon request without human intervention, using processor circuitry and transient containers to manage resource allocation and request forwarding.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of energy
If automated shutdown procedures are implemented to reduce costs from unused applications, then computational resource usage is reduced, but manual reprovisioning is required when users attempt to access inactive applications
Solution Approach 1:
The system automatically detects user access requests to suspended applications and reprovisions the applications without manual intervention. The automated suspension and redeployment mechanism serves itself by monitoring network traffic, detecting access requests, and automatically restarting suspended applications, eliminating the need for user manual reprovisioning operations.
Solution Approach 2:
The system continuously monitors network traffic to detect access requests to suspended applications. When access requests are detected, the feedback loop triggers automatic reprovisioning of the application. This closed-loop feedback mechanism ensures that applications are automatically restored when needed, resolving the contradiction between resource savings and access availability.
2Loss of energy
If cloud resources are suspended to reduce operational costs, then infrastructure costs are reduced, but system complexity increases due to manual intervention requirements
Solution Approach 1:
The automated suspension and redeployment system eliminates manual intervention by automatically detecting when applications need to be restarted and executing the redeployment process autonomously. This self-service capability reduces operational complexity despite maintaining cost-saving suspension functionality.
Solution Approach 2:
A transient container acts as an intermediary between the suspended application and the user access request. When users attempt to access a suspended application, the transient container receives the request, triggers the reprovisioning process, and manages the transition back to the active application state, simplifying the overall system architecture.
3Device complexity
If manual reprovisioning is required for inactive applications, then system simplicity is maintained, but user access time increases and productivity decreases
Solution Approach 1:
The system maintains applications in a suspended but ready state, preserving their configuration and state information. When access requests are detected, the application can be rapidly reprovisioned from the suspended state rather than requiring complete recreation, significantly reducing access time while maintaining system simplicity.
Solution Approach 2:
Real-time monitoring of network traffic provides immediate feedback when users attempt to access applications. This triggers instant reprovisioning actions, eliminating delays associated with manual reprovisioning and significantly improving user access speed without complicating the system architecture.
Data Source
AI summary
Methods, apparatus, systems, and articles of manufacture are disclosed to automate suspension and redeployment of cloud resources. The example apparatus is to, based on network traffic associated with a compute cluster hosting a containerized application, determine whether to suspend the containerized application. Additionally, the example apparatus is to determine a port of a transient container that is available to be mapped to the containerized application and cause a request to access the containerized application to be forwarded to the port of the transient container instead of the containerized application. The example apparatus is also to deprovision one or more resources associated with the containerized application.