An application resource integration implementation scheme based on an architectural diagram

Abstract

This invention discloses an integrated application resource implementation scheme based on architecture diagrams, belonging to the field of computer technology. The system includes an architecture diagram design module, a resource association module, a work order generation module, and multiple collaboration modules. The architecture diagram design module provides a graphical interface for drawing architecture diagrams containing application nodes and connections; the resource association module associates resource information with application nodes; the work order generation module generates resource request work orders based on newly added application nodes and communication access control work orders based on the communication requirements corresponding to the connections; the multiple collaboration modules share the architecture diagram, resource information, resource request work orders, and communication access control work orders with multiple collaboration groups, and receive update feedback on work order status from multiple collaboration groups to dynamically adjust resource configuration. This invention achieves integrated management of architecture, applications, and resources, reduces cross-group collaboration costs, and improves resource configuration efficiency and system management efficiency.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and more specifically to an integrated application resource implementation scheme based on an architecture diagram. Background Technology

[0002] Current system development trends show a focus on diversified business operations, microservice-based applications, and cloud-native resources. In the full lifecycle management of "architecture-application-resources," existing technologies often employ separate management systems for maintenance. For example, infrastructure resources are managed through resource management systems, application configurations through configuration management systems, and operations and maintenance are managed through monitoring tools. However, this separate management approach suffers from the following problems: First, there is a fragmentation in management. Application architecture, infrastructure resources, and security operations are maintained by different management systems, resulting in a lack of effective data communication and integration between these systems. This leads to high costs for change coordination and low management efficiency. Secondly, resource allocation is unreasonable. In complex projects, due to insufficient judgment of peak business hours and daily traffic, business application resources are often misallocated, resulting in resource waste and affecting resource allocation for new projects; Furthermore, fault handling efficiency is low. When multiple fault points occur simultaneously, existing technologies struggle to quickly determine the extent of the fault's impact, leading to inefficient decision-making. Finally, architectural iteration is difficult. Traditional configuration management databases mainly record static configuration relationships, which are not updated and maintained in a timely manner. They are difficult to adapt to the needs of dynamic architectures such as microservices and containerization, and cannot accurately reflect the dynamic changes in the architecture, resulting in a lack of reliable data support when adjusting the architecture or allocating resources.

[0003] To address the aforementioned issues, there is an urgent need for an integrated application resource implementation solution based on architecture diagrams, which can solve problems such as fragmented management dimensions, unreasonable resource allocation, low fault handling efficiency, and difficulty in architecture iteration that exist in traditional separate management methods. Summary of the Invention

[0004] The purpose of this invention is to provide an integrated application resource implementation scheme based on an architecture diagram, so as to solve the problems of fragmented management dimensions, unreasonable resource allocation, low fault handling efficiency and difficulty in architecture iteration that exist in the traditional separate management method.

[0005] To achieve the above objectives, the technical solution adopted by the present invention is as follows: An application resource integration management system based on an architecture diagram includes: The architecture diagram design module provides a graphical interface for drawing architecture diagrams that include application nodes and connecting lines. The resource association module is used to associate resource information with the application node; The work order generation module is used to generate resource request work orders based on newly added application nodes, and to generate wall opening work orders based on the communication requirements corresponding to the connection lines. Multiple collaborative modules are used to share the architecture diagram, resource information, resource application work orders, and wall-breaking work orders to multiple collaborative groups, and to receive update feedback on the work order status from the multiple collaborative groups in order to dynamically adjust resource configuration.

[0006] In one specific implementation, the architecture diagram design module is also used to add functional descriptions to the application nodes, label the communication protocols for the connection lines, and set the communication protocol type for the connection lines.

[0007] In one specific implementation scheme, the resource association module includes: The resource mapping unit is used to configure resource requirements for the application node based on user input. The verification unit is used to display the actual resource information corresponding to the application nodes that have been allocated resources.

[0008] In one specific implementation, the resource association module is also used to display the corresponding machine IP, central processing unit information and memory information after the application node has been allocated resources.

[0009] In one specific implementation scheme, the work order generation module includes: The new node identification unit is used to analyze the resource requirements of the newly added application node and generate the resource request work order when the new application node is detected. The communication requirements analysis unit is used to analyze the network communication requirements between the application nodes connected by the connection line, and generate the wall opening work order when cross-network communication is detected.

[0010] In a specific implementation scheme, the resource application work order generated by the work order generation module includes node information, resource type and application status, and the firewall access work order includes source node, target node, protocol and port.

[0011] In one specific implementation scheme, the multiple sets of collaborative modules include: An information sharing unit is used to synchronize the architecture diagram, the resource information, and the work order status among the multiple collaboration groups; The dynamic adjustment unit is used to adjust resource allocation or network configuration based on the update feedback of the work order status, and to trigger the work order generation module to regenerate the work order if the requirements are not met after the adjustment.

[0012] In one specific implementation, the multiple collaborative groups shared by the multiple collaborative modules include a development group, a resource management group, and a network management group.

[0013] In one specific implementation scheme, the integrated application resource management system based on architecture diagrams further includes: The progress management module is used to view the processing progress of each work order in real time; The deployment module is used to generate and execute the project deployment plan based on the architecture diagram, resource allocation results, and work order processing results.

[0014] In summary, the present invention has the following beneficial technical effects: This invention organically integrates an architecture diagram design module, a resource association module, a work order generation module, and multiple sets of collaborative modules to construct an integrated management platform for architecture, applications, and resources. This breaks down the information barriers between traditional separate management systems, realizes a unified view and real-time synchronization of multi-dimensional management data, effectively reduces change linkage costs, and improves overall management efficiency.

[0015] This invention enables users to intuitively draw application nodes and their connections through a graphical architecture diagram design module. Combined with a resource association module, it accurately configures resource requirements for each application node. Furthermore, it utilizes a work order generation module to automatically identify the resource requirements of newly added nodes, analyze the cross-network communication requirements of connection lines, and generate corresponding resource application work orders and wall opening work orders. This achieves accurate analysis and automated management of resource configuration, effectively reducing resource mismatch and avoiding resource waste.

[0016] This invention uses multiple collaborative modules to share architecture diagrams, resource information, and work order status in real time with multiple collaborative groups, and receives updates on work order status from each group. It dynamically adjusts resource allocation and network configuration, enabling the rapid determination of the scope of fault impact based on an integrated architecture view when multiple fault points occur. This provides reliable data support for decision-making and effectively improves fault handling efficiency.

[0017] This invention uses a dynamically editable architecture diagram as its core carrier to record and reflect the dynamic changes of application nodes, connection relationships, and resource configurations in real time. It overcomes the limitations of traditional configuration management databases that only record static configuration relationships, accurately reflects the dynamic evolution of the architecture, and provides accurate and timely data support when adjusting the architecture or allocating resources, effectively solving the problem of difficult architecture iteration. Attached Figure Description

[0018] Figure 1 An architecture diagram and review process diagram of an application resource integration management system based on an architecture diagram are provided for embodiments of the present invention. Figure 2 This is a schematic diagram of the work order generation and collaborative execution process of the application resource integrated management system based on the architecture diagram provided in this embodiment of the invention. Detailed Implementation

[0019] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the invention. Furthermore, the technical features involved in the various embodiments of this invention described below can be combined with each other as long as they do not conflict with each other.

[0020] This invention provides an integrated application resource management system based on an architecture diagram, such as... Figure 1 As shown, the system includes an architecture diagram design module, a resource association module, a work order generation module, a multi-group collaboration module, a progress management module, and a deployment module.

[0021] The architecture diagram design module provides a graphical interface for drawing architecture diagrams containing application nodes and connections. Specifically, this module is implemented using a web graphics library (such as AntV X6, Draw.io, or a self-developed graphics engine), allowing users to create application nodes on a canvas by dragging and dropping components. Each node corresponds to a unique identifier (UUID) in the underlying data model and stores attributes such as node name, node type, network zone (e.g., "production zone," "office zone," "DMZ zone"), and resource specifications. Users can draw connections between two nodes using the connection tool. The connection records the source node ID and target node ID in the data model and supports storing extended attributes such as protocol and port.

[0022] The architecture diagram design module also supports annotation functionality: users can right-click on an application node and enter a functional description text in the pop-up attribute editing window (for example, adding "Maintain transaction information with customers" to the "Order Service" node). This description is stored as a node attribute and displayed as part of the application description when a work order is generated later. After clicking on a connection line, users can annotate the communication protocol (such as TCP / IP, HTTP) for the connection line in the attribute panel on the right and set the communication protocol type (such as TCP, UDP). It also supports modifying the set communication protocol type.

[0023] The architecture diagram data is stored in the backend database in JSON format, containing a list of nodes, a list of connections, and their respective extended attributes. Each time a user saves the architecture diagram, the system generates a version snapshot for subsequent modules to detect changes.

[0024] The resource association module is used to associate resource information with application nodes. This module includes a resource mapping unit and a verification unit.

[0025] The resource mapping unit is used to configure resource requirements for application nodes based on user input. Users specify resource requirements through a form in the node properties panel, including: number of instances (e.g., 2), number of CPU cores (e.g., 2 cores), memory size (e.g., 4GB), disk capacity (e.g., 500GB), and operating system type (e.g., CentOS 7.9). The resource mapping unit stores these requirements in a structured manner in the node's "resource_spec" field.

[0026] The verification unit displays the actual resource information corresponding to the application nodes for which resources have been allocated. After the application node completes resource allocation, the resource association module calls the query interface of the cloud management platform (such as OpenStack, VMware vSphere, Alibaba Cloud ECS API), inputs the node identifier or resource instance ID, and obtains the actual allocated resource details, including the machine IP address (IPv4 / IPv6), CPU model and number of cores, and memory size. This information is displayed in the "Actual Resources" area of ​​the node details page for users to verify whether the resource configuration matches the application. If there is a discrepancy between the actual resources and the applied resources, the system can prompt the user through the interface to confirm or reapply.

[0027] The work order generation module is used to generate resource request work orders based on newly added application nodes, and to generate wall opening work orders based on the communication requirements corresponding to the connection lines. This module includes a new node identification unit and a communication requirement analysis unit.

[0028] When a user saves the architecture diagram, the new node identification unit compares the currently saved node list with the node list of the previous version. If a node ID is found to be absent in the previous version, it is identified as a newly added node. Subsequently, the new node identification unit reads the "resource_spec" field from the node's attributes, extracts resource requirements (number of instances, CPU, memory, disk, etc.), and calls the API of the ticketing system (such as Jira or a self-developed ticketing engine) to generate a resource request ticket. This ticket includes: node name, required number of CPU cores, memory size, disk capacity, function description, and application status (initially "pending approval"), and is automatically associated with the resource management group.

[0029] Each time the architecture diagram is saved, the communication requirements analysis unit iterates through all current connections. For each connection, it retrieves the "Network Region" field stored by the source and target nodes. If the network regions of the two nodes are different, it determines that there is a cross-network communication requirement. The communication requirements analysis unit further extracts the preset "Protocol" and "Port" fields (such as TCP, 8080) on the connection and calls the work order system API to generate a network access control work order. This work order includes: source node name and IP, target node name and IP, protocol type, port number, and is associated with the network management group.

[0030] The multi-group collaboration module is used to share architecture diagrams, resource information, resource application work orders, and wall-breaking work orders to multiple collaboration groups, and to receive update feedback on the work order status from the multiple collaboration groups in order to dynamically adjust resource configuration. The multi-group collaboration module includes an information sharing unit and a dynamic adjustment unit.

[0031] The information sharing unit pushes architecture diagram data, resource information, and work order status changes to the front-end interface of all collaboration groups in real time via WebSocket or message queues (such as Kafka, Redis Pub / Sub). The system pre-configures three roles: development group, resource management group, and network management group. Resource application work orders are only visible and can be approved by the resource management group; access control work orders are only visible and can be approved by the network management group. The development group can view the status of all work orders but does not have approval permissions, thus achieving permission isolation and information synchronization.

[0032] The dynamic adjustment unit monitors the approval result callback of the work order system: When the status of a resource application work order changes to "approved", the dynamic adjustment unit calls the resource allocation interface of the resource management platform, completes the creation of virtual machines or containers according to the resource specifications in the work order, and writes the allocation results (IP, CPU, memory) back to the verification unit of the resource association module; when the status of a firewall access work order changes to "approved", the dynamic adjustment unit calls the policy distribution interface of the network firewall management platform, creates access control policies (such as iptables rules, security group rules) according to the source IP, destination IP, protocol and port in the work order; if the work order status is "rejected", the dynamic adjustment unit parses the rejection reason. If the rejection reason is "insufficient resources" or "port conflict", it automatically adjusts the resource specification parameters (such as adjusting a 4-core CPU to a 2-core CPU, or changing the conflicting port to another available port) and then triggers the work order generation module to regenerate the work order.

[0033] The progress management module is used to view the processing progress of each work order in real time. This module provides a work order list view, which displays the current status (such as "Pending Approval", "Approved", "Approval Rejected", "Resource Delivered"), operation timeline (submission time, approval time, completion time), and approval comments of resource application work orders and wall opening work orders by calling the query interface of the work order system. It supports filtering by node name, work order type, and status.

[0034] The deployment module generates and executes a project deployment plan based on the architecture diagram, resource allocation results, and work order processing results. When all resource application work orders and network access control work orders related to the current architecture diagram are in the "approved" state, the deployment module performs the following operations: reads the deployment order of nodes in the architecture diagram (if not specified by the user, it is automatically sorted according to topology dependencies); reads the list of allocated resource IPs and enabled network policies; automatically generates an Ansible Playbook or Shell deployment script; and provides two methods: "one-click execution" and "export deployment package". During execution, it calls the Agent on the target server or completes the application installation and configuration via SSH connection, ultimately completing the system deployment.

[0035] In one specific embodiment, such as Figure 2 As shown, the user drew an architecture diagram containing three application nodes: Node A (network area: production area), Node B (network area: office area), and Node C (new, network area: production area). A connection exists between Node A and Node B, and the user has labeled the protocol as TCP and port as 8080. The user adds Node C to the architecture diagram and configures its resource requirements: two virtual machines, each with 2 CPU cores, 4GB of memory, and a 500GB hard drive. After the user saves the architecture diagram: the new node identification unit identifies Node C as a new node through version comparison, reads its resource_spec field, generates a resource request work order, and submits it to the resource management group; the communication requirements analysis unit detects that the network areas at both ends of the connection between Node A and Node B are inconsistent (production area vs. office area), and that the connection line has been labeled with the protocol as TCP and port as 8080, generates a network access request work order, and submits it to the network management group. The development team can view the work order status in real time through multiple collaborative modules. After the resource management group approves the resource request, the dynamic adjustment unit automatically calls the cloud platform to create two virtual machines and populates their IP addresses into the resource information of node C. After the network management group approves the firewall permission request, the dynamic adjustment unit automatically issues a firewall policy allowing TCP port 8080 access from the production area to the office area. Once all requests are completed, the deployment module reads the IP information of node C and the network policy between node A and node B, generates a deployment script, and completes the application deployment. In practical applications, this solution can improve cross-group collaboration efficiency by approximately 40%.

[0036] Contents not described in detail in this specification are prior art known to those skilled in the art. It is hereby indicated that the above description is intended to help those skilled in the art understand this invention, but does not limit the scope of protection of this invention. Any equivalent substitutions, modifications, improvements, or simplifications of the above descriptions that do not depart from the essential content of this invention fall within the scope of protection of this invention.

Claims

1. An integrated application resource management system based on an architecture diagram, characterized in that, include: The architecture diagram design module provides a graphical interface for drawing architecture diagrams that include application nodes and connecting lines. The resource association module is used to associate resource information with the application node; The work order generation module is used to generate resource request work orders based on newly added application nodes, and to generate wall opening work orders based on the communication requirements corresponding to the connection lines. Multiple collaborative modules are used to share the architecture diagram, resource information, resource application work orders, and wall-breaking work orders to multiple collaborative groups, and to receive update feedback on the work order status from the multiple collaborative groups in order to dynamically adjust resource configuration.

2. The application resource integration management system based on architecture diagram according to claim 1, characterized in that, The architecture diagram design module is also used to add functional descriptions to the application nodes, label the communication protocols for the connection lines, and set the communication protocol type for the connection lines.

3. The application resource integration management system based on architecture diagram according to claim 1, characterized in that, The resource association module includes: The resource mapping unit is used to configure resource requirements for the application node based on user input. The verification unit is used to display the actual resource information corresponding to the application nodes that have been allocated resources.

4. The application resource integration management system based on architecture diagram according to claim 1, characterized in that, The resource association module is also used to display the corresponding machine IP, CPU information and memory information after the application node has been allocated resources.

5. The application resource integration management system based on architecture diagram according to claim 1, characterized in that, The work order generation module includes: The new node identification unit is used to analyze the resource requirements of the newly added application node and generate the resource request work order when the new application node is detected. The communication requirements analysis unit is used to analyze the network communication requirements between the application nodes connected by the connection line, and generate the wall opening work order when cross-network communication is detected.

6. The application resource integration management system based on architecture diagram according to claim 1, characterized in that, The work order generated by the work order generation module includes node information, resource type and application status, and the wall-breaking work order includes source node, target node, protocol and port.

7. The application resource integration management system based on architecture diagram according to claim 1, characterized in that, The multiple sets of collaborative modules include: An information sharing unit is used to synchronize the architecture diagram, the resource information, and the work order status among the multiple collaboration groups; The dynamic adjustment unit is used to adjust resource allocation or network configuration based on the update feedback of the work order status, and to trigger the work order generation module to regenerate the work order if the requirements are not met after the adjustment.

8. The application resource integration management system based on architecture diagram according to claim 1, characterized in that, The multiple collaborative groups shared by the multiple collaborative modules include a development group, a resource management group, and a network management group.

9. The application resource integration management system based on architecture diagram according to claim 1, characterized in that, Also includes: The progress management module is used to view the processing progress of each work order in real time; The deployment module is used to generate and execute the project deployment plan based on the architecture diagram, resource allocation results, and work order processing results.

Images