Cloud Deployment Nodes Kinship-Based Autonomous Component Distribution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Cloud platform application deployment systems heavily rely on a central server, leading to reduced flexibility and efficiency in application component deployment, as deployment nodes are dependent on the server and cannot deploy components independently.
Innovation Solution
The method involves deployment nodes determining their kinship relationships, such as parent-child or brother nodes, to independently deploy application components based on pre-defined hierarchical relationships, reducing dependence on the central server by sending deployment instructions to parent or sibling nodes only after they have completed their tasks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a cloud platform application deployment server centrally controls the entire application deployment process using a configuration management tool, then the deployment process is centralized and controllable, but the deployment nodes heavily depend on the server, reducing flexibility and efficiency
Solution Approach 1:
The patent segments the centralized deployment control into distributed control among multiple deployment nodes. Each node is divided into a deployment execution unit and a status reporting unit, allowing independent execution while maintaining coordination through status reporting to the server. This segmentation resolves the contradiction by distributing control (improving flexibility) while preserving monitoring capability (maintaining reliability).
Solution Approach 2:
The deployment nodes are equipped with self-service capabilities through the deployment execution unit that can independently determine deployment sequences and execute deployments without continuous server intervention. The nodes automatically report status and receive instructions only when needed, enabling self-directed deployment operations that improve flexibility while maintaining server oversight for reliability.
2Reliability
If deployment nodes heavily depend on the central server for deployment instructions, then centralized control is maintained, but deployment efficiency and concurrency are reduced
Solution Approach 1:
The server performs preliminary action by sending initial deployment instructions and deployment sequences to the nodes before actual deployment execution. The deployment execution unit then uses this pre-provided information to autonomously execute deployments and coordinate with other nodes, eliminating the need for continuous server intervention and improving deployment efficiency while maintaining centralized control through the initial instruction distribution.
Solution Approach 2:
The patent implements a feedback mechanism where the deployment execution unit reports deployment status to the server, and the server provides follow-up instructions based on this feedback. This closed-loop feedback system maintains centralized control and reliability while allowing nodes to operate autonomously between feedback cycles, thereby improving deployment efficiency and concurrency.
3Reliability
If the central deployment server becomes faulty, then the entire application deployment process fails, but increasing server redundancy complicates the system architecture
Solution Approach 1:
The patent extracts the deployment execution capability from the central server and embeds it directly into the deployment nodes. The server retains only the functions of sending initial instructions and receiving status reports, while the nodes independently execute deployments and coordinate with each other. This extraction eliminates the single point of failure at the server, improving reliability without adding server redundancy, and actually simplifies the architecture by reducing the server's operational burden.
4Reliability
If deployment nodes cannot independently deploy components, then centralized control is maintained, but deployment concurrency and flexibility are limited
Solution Approach 1:
The patent introduces dynamics by enabling deployment nodes to adaptively determine their own deployment sequences based on status information from other nodes. The deployment execution unit dynamically adjusts execution timing and coordination based on real-time deployment status, allowing concurrent deployments when conditions permit while maintaining centralized oversight. This dynamic behavior increases deployment concurrency while preserving centralized control through the status reporting mechanism.
Data Source
AI summary
Embodiment of this application disclose an application component deployment method and a deployment node. In the method, a target deployment node receives a first deployment instruction sent by a management server, and determines a kinship node of the target deployment node according to the first deployment instruction, and a second application component that is in the multiple application components and that corresponds to the parent node, where the kinship node includes a parent node. Then, when detecting that the parent node has deployed the second application component, the target deployment node sends a second deployment instruction to the parent node. The target deployment node deploys a first application component according to the first deployment instruction.