Cloud network resource management method and device, nonvolatile storage medium and electronic equipment

Abstract

The invention discloses a cloud network resource management method and device, a nonvolatile storage medium and electronic equipment. The method comprises the steps that cloud network resource data are acquired, a first topological graph is generated according to the cloud network resource data, the first topological graph is displayed on canvas, nodes in the first topological graph are used for representing the cloud network resource data, and edges between the nodes are used for representing the incidence relation between the cloud network resource data; in response to an operation instruction for the first topological graph detected by the visual editor, adjusting the first topological graph to obtain a second topological graph; in response to the logic entity binding instruction, binding a logic entity indicated by the logic entity binding instruction in the canvas with elements in the canvas; and in response to an event binding instruction for the element in the canvas, binding an event indicated by the event binding instruction with the element in the canvas. The technical problem of high management difficulty caused by static presentation of data in a topological form in existing resource management is solved.

Description

Technical Field

[0001] The present application relates to the field of cloud services, and more specifically, to a cloud network resource management method, device, non-volatile storage medium, and electronic device. Background Art

[0002] Most cloud service providers provide a graphical user interface (GUI) to manage resources within the cloud. Users can use the console to intuitively view and manage resources such as subnets, virtual machines, virtual firewalls, and the relationships between them. In addition to the console, these resources can also be managed through command line interfaces, APIs, automation tools (such as Terraform, Ansible, Puppet, and other automation tools), and cloud resource orchestration services from some vendors. However, these tools focus on resource lifecycle management (creation, modification, or deletion), as well as static resource presentation based on limited hierarchical mapping relationships from various perspectives. There are compatibility issues, and because the data is presented statically, the management interface has low operability and high management difficulty.

[0003] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0004] The embodiments of the present application provide a cloud network resource management method, device, non-volatile storage medium and electronic device to at least solve the technical problem of high management difficulty caused by the static presentation of data in topological form in existing resource management.

[0005] According to one aspect of an embodiment of the present application, a cloud network resource management method is provided, including: obtaining cloud network resource data, generating a first topology map based on the cloud network resource data and displaying the first topology map on a canvas, wherein the nodes in the first topology map are used to represent the cloud network resource data, and the edges between the nodes are used to represent the association relationship between the cloud network resource data; in response to an operation instruction for the first topology map detected in a visual editor, adjusting the first topology map to obtain a second topology map; in response to a logical entity binding instruction, binding the logical entity indicated by the logical entity binding instruction in the canvas to an element in the canvas, wherein the element includes: a node in the second topology map, an edge in the second topology map, and a visual component in the canvas other than the second topology map; in response to an event binding instruction for an element in the canvas, binding the event indicated by the event binding instruction to the element in the canvas.

[0006] Optionally, the operation instruction includes a drag instruction; in response to the operation instruction for the first topology diagram detected in the visual editor, adjusting the first topology diagram to obtain the second topology diagram includes: responding to the drag instruction, adding an edge corresponding to the drag instruction to the first topology diagram to obtain the second topology diagram, wherein the edge corresponding to the drag instruction is at least used to reflect the physical link from the user business end to the entrance to the cloud to the virtual core firewall.

[0007] Optionally, in response to an operation instruction for the first topology map detected in the visual editor, after adjusting the first topology map to obtain the second topology map, the method also includes: saving the execution result of the operation instruction as json record data, and storing the json record data in a database.

[0008] Optionally, in response to a logical entity binding instruction, binding the logical entity indicated by the logical entity binding instruction in the canvas and the element in the canvas includes: determining the logical entity indicated by the logical entity binding instruction based on the device type and device IP address carried in the logical entity binding instruction; binding the unique identifier of the logical entity to the element in the canvas; saving the binding result as json record data, and storing the json record data in a database.

[0009] Optionally, in response to the logical entity binding instruction, binding the logical entity indicated by the logical entity binding instruction in the canvas and the element in the canvas includes: determining the device state corresponding to the unique identifier through the unique identifier; and updating the element attribute of the element bound to the unique identifier according to the device state.

[0010] Optionally, the event binding instruction includes an event binding script; responding to the event binding instruction for an element in the canvas, binding the event indicated by the event binding instruction and the element in the canvas includes: determining the target element indicated by the event binding instruction based on the event binding script; determining the event type of the event and the trigger action performed after the event is triggered based on the event binding script; configuring the target element based on the event type and the trigger action, thereby binding the event to the target element; saving the binding result as json record data, and storing the json record data in a database.

[0011] Optionally, the method also includes: executing the action indicated by the triggered event through a callback function, wherein the callback function includes a first field, a second field and a third field, the first field is used to identify the event type of the event, the second field is used to identify the element object of the element associated with the event, the element object includes attribute information and association information of the element, and the third field is used to pass associated data of the event.

[0012] According to another aspect of an embodiment of the present application, a cloud network resource management device is also provided, including: a first processing module, used to obtain cloud network resource data, and generate a first topology map based on the cloud network resource data and display the first topology map on a canvas, wherein the nodes in the first topology map are used to represent the cloud network resource data, and the edges between the nodes are used to represent the association relationship between the cloud network resource data; a second processing module, used to adjust the first topology map to obtain a second topology map in response to an operation instruction for the first topology map detected in a visual editor; a third processing module, used to respond to a logical entity binding instruction, and bind the logical entity indicated by the logical entity binding instruction in the canvas to the element in the canvas, wherein the element includes: nodes in the second topology map, edges in the second topology map, and visual components in the canvas except the second topology map; a fourth processing module, used to respond to an event binding instruction for the element in the canvas, and bind the event indicated by the event binding instruction to the element in the canvas.

[0013] According to another aspect of an embodiment of the present application, a non-volatile storage medium is further provided, in which a program is stored, wherein when the program is running, a device where the non-volatile storage medium is located is controlled to execute a cloud network resource management method.

[0014] According to another aspect of an embodiment of the present application, there is also provided an electronic device, including: a memory and a processor, the processor being used to run a program stored in the memory, wherein the cloud network resource management method is executed when the program is running.

[0015] According to another aspect of an embodiment of the present application, a computer program product is also provided, including a computer program, which implements a cloud network resource management method when the computer program is executed by a processor.

[0016] In an embodiment of the present application, cloud network resource data is obtained, and a first topology map is generated based on the cloud network resource data and displayed on a canvas, wherein the nodes in the first topology map are used to represent the cloud network resource data, and the edges between the nodes are used to represent the association relationship between the cloud network resource data; in response to an operation instruction for the first topology map detected in a visual editor, the first topology map is adjusted to obtain a second topology map; in response to a logical entity binding instruction, the logical entity indicated by the logical entity binding instruction in the canvas is bound to an element in the canvas, wherein the element includes: a node in the second topology map, an edge in the second topology map, and a visual component in the canvas other than the second topology map; in response to an event binding instruction for an element in the canvas, an event indicated by the event binding instruction is bound to an element in the canvas, and the purpose of real-time updating and dynamic interaction of resources is achieved through semi-automatic resource relationship establishment and dynamic binding, thereby achieving the technical effect of flexibly displaying and efficiently managing cloud network resource relationships, thereby solving the technical problem of high management difficulty caused by the static display of data in the form of topology in existing resource management. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0018] Figure 1 is a structural schematic diagram of a computer terminal provided according to an embodiment of the present application;

[0019] Figure 2 It is a flowchart of a cloud network resource management method provided according to an embodiment of the present application;

[0020] Figure 3 It is a schematic diagram of a system framework provided according to an embodiment of the present application;

[0021] Figure 4 is a schematic diagram of a first topological diagram provided according to an embodiment of the present application;

[0022] Figure 5 It is a schematic diagram of a data collection and analysis process provided according to an embodiment of the present application;

[0023] Figure 6 It is a schematic diagram of a data collection and analysis process provided according to an embodiment of the present application;

[0024] Figure 7 It is a schematic diagram of a data collection and analysis process provided according to an embodiment of the present application;

[0025] Figure 8It is a schematic diagram of a cloud network resource management process provided according to an embodiment of the present application;

[0026] Fig. 9 is a schematic diagram of a fault detection function provided according to an embodiment of the present application;

[0027] Fig.10 It is a structural diagram of a cloud network resource management device provided according to an embodiment of the present invention. DETAILED DESCRIPTION

[0028] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0029] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0030] The products of various manufacturers are basically based on OpenStack, and are modified and packaged on it: various resources and the relationship between resources are recorded in the database, each resource corresponds to a table, and the mapping between various resources is saved by the view. In actual use, there are the following problems:

[0031] 1. Compatibility: Before a device can be managed, it must first meet compatibility requirements. Products that are not on the compatibility list cannot be managed, and lifecycle management and resource relationship display are out of the question.

[0032] 2. Lack of canvas function: Common products lack canvas function and can only display 2-3 level resources and relationships based on the relationship between resources. Incompatible devices, multi-level relationships, and business resources that are not within the scope of IT or a certain profession cannot be depicted, resulting in the display of only a certain perspective, rather than a comprehensive or scenario-based perspective.

[0033] 3. Static data: Resource relationships are often presented in the form of topology, and topology basically presents static properties rather than dynamic or real-time data. Operation and maintenance personnel hope to obtain more data and further operation execution capabilities based on static topology, as well as the ability for topology to change as data changes.

[0034] In order to solve the above problems, relevant solutions are provided in the embodiments of the present application, which are described in detail below.

[0035] According to an embodiment of the present application, a method embodiment of a cloud network resource management method is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0036] The method embodiments provided in the embodiments of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Figure 1 The hardware structure block diagram of a computer terminal (or mobile device) for implementing a cloud network resource management method is shown. Figure 1 As shown, the computer terminal 10 (or mobile device 10) may include one or more (102a, 102b, ..., 102n are used to illustrate) processors 102 (the processor 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 104 for storing data, and a transmission device 106 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the BUS bus), a network interface, a power supply and / or a camera. It can be understood by those skilled in the art that Figure 1 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 1 More or fewer components as shown, or with Figure 1 Different configurations are shown.

[0037] It should be noted that the one or more processors 102 and / or other data processing circuits described above may generally be referred to herein as "data processing circuits". The data processing circuits may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. In addition, the data processing circuit may be a single independent processing module, or may be incorporated in whole or in part into any of the other components in the computer terminal 10 (or mobile device). As described in the embodiments of the present application, the data processing circuit acts as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

[0038] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the cloud network resource management method in the embodiment of the present application. The processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, the above-mentioned cloud network resource management method is realized. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include a memory remotely arranged relative to the processor 102, and these remote memories may be connected to the computer terminal 10 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0039] The transmission device 106 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the computer terminal 10. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0040] The display may be, for example, a touch screen liquid crystal display (LCD) that enables a user to interact with a user interface of the computer terminal 10 (or mobile device).

[0041] In the above operating environment, the present application embodiment provides a cloud network resource management method, such as Figure 2 As shown, the method comprises the following steps:

[0042] Step S202, obtain cloud network resource data, generate a first topology map based on the cloud network resource data and display the first topology map on the canvas, wherein the nodes in the first topology map are used to represent the cloud network resource data, and the edges between the nodes are used to represent the association relationship between the cloud network resource data.

[0043] Optionally, obtaining cloud network resource data includes:

[0044] (1) Obtain CI (Configuration Item) resources through the resource interface in the API in the cloud stack. CI resources include virtual machines, hosts, VPCs, networks, subnets, and security group lists. CI resources are stored in the classified resource tables of the MySQL database, including the tb_vms, tb_hosts, tb_vpcs, tb_networks, tb_subnets, and tb_sgs tables. The return result of the virtual machine resource includes the ID of the host, VPC (Virtual Private Cloud), and security group. The return result of the VPC resource includes the ID of the associated network. The return result of the network resource includes the ID of the associated subnet. Finally, a mapping relationship between the VM and the subnet is established through the VM (virtual machine). The IP, project information, and host information of the VM are obtained through the restful API interface of the business system in use. And the VM list under the project is obtained through the project information. Then the host, VPC, security group, and subnet information corresponding to each VM are obtained through a loop structure. The above part completes the logical part of the relationship between the subnet, security group, VM, and host in the VPC on the cloud. Through the association relationship, the JSON structure required by the topology is automatically generated.

[0045] According to the established unified API interface specifications, ensure that different versions of API and system internal interfaces can communicate according to the same standards. Perform compatibility processing on the interface part and provide a unified calling entry and parameter format.

[0046] Optionally, Figure 3 A first topological diagram is shown, such as Figure 3 As shown, the nodes in the first topological graph are used to represent cloud network resource data, and the edges between the nodes are used to represent the association relationship between the cloud network resource data.

[0047] Step S204: in response to an operation instruction for the first topology map detected in the visual editor, adjusting the first topology map to obtain a second topology map.

[0048] In the technical solution provided in step S204, the operation instruction includes a drag instruction; in response to the operation instruction for the first topology diagram detected in the visual editor, adjusting the first topology diagram to obtain the second topology diagram includes: responding to the drag instruction, adding an edge corresponding to the drag instruction to the first topology diagram to obtain the second topology diagram, wherein the edge corresponding to the drag instruction is at least used to reflect the physical link from the user business end to the entrance to the cloud to the virtual core firewall.

[0049] In the technical solution provided in step S204, in response to an operation instruction for the first topology map detected in the visual editor, after adjusting the first topology map to obtain the second topology map, the method also includes: saving the execution result of the operation instruction as json record data, and storing the json record data in a database.

[0050] Optionally, a visual web topology editor is implemented based on vue+ts+svg, and the needs of manually drawing physical resource pool topology, business resources outside the resource pool, application layer or more complex types of resources with unrelated information are met by configuring elements, attributes and events. By responding to the drag and drop operation detected in the visual editor for the first topology diagram, the physical link (represented by edges) from the user's business end to the cloud entrance to the virtual core firewall and the drawing of the logical topology and the cloud topology with missing associated information are completed. The drawing result is saved as a json record in the mysql database. By automatically inserting attributes, events and other data into the json record, the automatic update of the topology and the generation of a new topology are completed, and the second topology diagram is obtained, and the repeated design of dragging and dropping the interface is no longer required. By recording data in JSON, there is no need to drag and draw again when reopening the topology diagram file, and the second topology diagram can be generated directly according to the JSON record.

[0051] Step S206, in response to the logical entity binding instruction, bind the logical entity indicated by the logical entity binding instruction in the canvas and the elements in the canvas, wherein the elements include: nodes in the second topology graph, edges in the second topology graph, and visual components in the canvas except the second topology graph.

[0052] In the technical solution provided in step S206, in response to the logical entity binding instruction, the logical entity indicated by the logical entity binding instruction in the canvas and the element in the canvas are bound, including: determining the logical entity indicated by the logical entity binding instruction based on the device type and device IP address carried in the logical entity binding instruction; binding the unique identifier of the logical entity to the element in the canvas; saving the binding result as json record data, and storing the json record data in a database.

[0053] Optionally, by recording data in JSON, there is no need to bind again when reopening the topology map file, and the logical entity indicated by the logical entity binding instruction in the canvas can be directly bound to the element in the canvas according to the JSON record.

[0054] In the technical solution provided in step S206, in response to the logical entity binding instruction, the logical entity indicated by the logical entity binding instruction in the canvas and the element in the canvas are bound, including: determining the device state corresponding to the unique identifier through the unique identifier; and updating the element attributes of the element bound to the unique identifier according to the device state.

[0055] Optionally, in the system, according to the device type and device IP address, the user can select the corresponding logical entity and bind it to the drawn elements on the page, thereby establishing a mapping relationship between the device and the page elements. The specific functions and implementation methods are as follows:

[0056] (1) Component call and business logic binding: The platform provides the deviceBind component, which is responsible for calling business services and binding the unique identifier of the logical entity selected by the user to the graphical element in the canvas one-to-one. Through this operation, the system can achieve accurate correspondence between the device logical entity and the page visualization element.

[0057] (2) Dynamic resource status acquisition and real-time update: When the topology map is drawn, the system can obtain the corresponding real resource status in real time through the bound logical entity unique identifier. By calling the setItemAttrs method of the component, the attributes of the corresponding graphic element in the canvas can be dynamically updated. This real-time update mechanism ensures that the displayed content on the page always reflects the latest status of the device, thereby achieving real-time dynamic display effects.

[0058] (3) Event binding: In addition to real-time status updates, the unique identifier of the logical entity can also provide convenient support in subsequent event binding functions.

[0059] (4) Persistence of binding relationships: To ensure data consistency, all binding relationships are synchronously saved in a JSON object maintained by the system. This persistence operation ensures that the binding relationship remains intact after the system is restarted or data is transferred, laying a reliable foundation for subsequent operations.

[0060] Step S208 , responding to the event binding instruction for the element in the canvas, binding the event indicated by the event binding instruction with the element in the canvas.

[0061] In the technical solution provided in step S208, the event binding instruction includes an event binding script; responding to the event binding instruction for the element in the canvas, binding the event indicated by the event binding instruction and the element in the canvas includes: determining the target element indicated by the event binding instruction according to the event binding script; determining the event type of the event and the trigger action executed after the event is triggered according to the event binding script; configuring the target element according to the event type and the trigger action, thereby binding the event to the target element; saving the binding result as json record data, and storing the json record data in a database.

[0062] Optionally, the system supports users to perform event binding operations on icons drawn on the page by selecting the icon and choosing the desired event from the event drop-down options, and then entering the corresponding event response script to complete the script binding.

[0063] Specific implementation method:

[0064] (1) Event binding operation: After the user selects an element on the canvas (such as a cloud host, host machine, physical machine, etc., various types of devices, network components, etc., so that the user can select the appropriate element to draw as needed), select the event to be bound from the event drop-down option (such as single click, double click, mouse in, mouse out, etc.). Then, enter the corresponding event response script in the system custom code input box to complete the binding of the event and the element. In this way, the system realizes the direct association between the element and the user-defined interactive behavior.

[0065] (2) Persistence of event binding relationships: To ensure the persistence and consistency of event binding, all bound event relationships are synchronously stored in a JSON object maintained by the system. This persistence mechanism ensures that events remain valid and can be correctly parsed and responded to during system restarts, data transfers, or other situations.

[0066] Optionally, the method also includes: executing the action indicated by the triggered event through a callback function, wherein the callback function includes a first field, a second field and a third field, the first field is used to identify the event type of the event, the second field is used to identify the element object of the element associated with the event, the element object includes attribute information and association information of the element, and the third field is used to pass associated data of the event.

[0067] Optionally, executing the action indicated by the triggered event through the callback function includes: registering a callback function onEventCallBack in the canvas page to receive and process events actively triggered by the element, and when the event occurs, the onEventCallBack function will call the corresponding interface or execute the corresponding logic according to the type of event. "Element active" means that the element (such as the device node in the topology diagram) triggers a predefined event under the user's interaction (such as single click, double click, mouse movement, etc.). These events are caused by the user's behavior, and the system captures and processes these events through the callback function onEventCallBack to perform corresponding operations.

[0068] Optionally, the parameters of onEventCallBack are defined as (type: string, node: object, ... args: any[]). The parameter design of this function is very flexible:

[0069] Type field: used to identify the type of event. The system predefines some common event types, such as single click, double click, mouse in, mouse out, etc. Single click will call the device indicator interface to obtain the current device status in real time; double click will call the device alarm interface to obtain the latest alarm status of the device; mouse in will call the device details interface to obtain detailed device information; mouse out event will restore the original topology status.

[0070] Node field: passes the element object that currently triggers the event, which contains various attributes of the element and the associated information bound to it. Through the node parameter, the user can obtain the detailed status of the icon and the unique identifier of the device binding in the callback function, and execute the corresponding logic accordingly.

[0071] args field: represents variable parameters, which can pass other data related to the event. Since any number and type of parameters can be passed, this design greatly enhances the scalability of the component and enables it to adapt to a variety of complex scenario requirements.

[0072] Optionally, in addition to the common event types built into the system, the system also supports users to define and bind custom events by extending the onEventCallBack function. This flexibility enables the system to adapt to the needs of different business scenarios, supports users to write custom event response logic based on actual needs, and achieves personalized interaction effects.

[0073] Optionally, according to an embodiment of the present application, a system embodiment of a cloud network resource management method is provided. Figure 4 The system framework diagram is shown in FIG. Figure 4As shown in the figure, the system architecture adopts a layered structure, including four levels: display layer, interaction layer, platform layer and data layer. The data layer is used to store various resource data, resource relationship data, business data and graph database data, and cache the performance indicator data of bound devices. The platform layer is responsible for business logic, responsible for obtaining basic data through various interfaces and storing them in the database, responsible for generating resource relationship graphs for various types of stored data, and responsible for providing various event access interfaces. The display layer and interaction layer are responsible for UI display and front-end logic, receiving user page input and calling platform layer services, and generating page display results based on platform layer feedback.

[0074] Optionally, Figure 5 , Figure 6 and Figure 7 The flow chart of data collection and analysis is shown in FIG. Figure 5 , Figure 6 and Figure 7 As shown, the data flow of the patent is as follows:

[0075] Resource relationship display: First, the underlying data source must contain necessary resource data and resource relationship data. The cloud management platform provides business information, including work orders, commissions, projects and other data; various merchant platforms provide resource data and resource relationship data, and provide the above data through the merchant's RESTful API interface. Second, the data collection layer processes the data obtained from the data source into the database. Since this patent focuses on cloud resources, corresponding tables are established in the MySQL database for various types of cloud resources, and are synchronized with the data source regularly. Resource relationship data is processed in the same way. Third, as a data consumption layer, the data collection layer below is data input, and the data presentation layer above is business demand input. Modeling is done in the data consumption layer, and the underlying input is generated according to the business logic association based on the user application. Finally, the resource relationship is presented in the data presentation layer.

[0076] Manual modification and dynamic binding of resource relationships: First, complete the drag and drop and binding operations of the page in the data presentation layer. Second, the front-end page model records the json script generated by manual operations. Third, the generated json script is saved to the mysql database with the business submission.

[0077] Data information storage instructions:

[0078] The database of the patent includes at least a resource table, a resource relationship table, a topology and json mapping table, and a json data storage table. The resource table and the resource relationship table store information such as synchronization time, resource ID, resource attribute, and mapping relationship. The json data storage table stores the creator, modification time, and json information. The topology and json mapping table stores project information, json data ID, etc.

[0079] Optionally, Figure 8A cloud network resource management process is shown, such as Figure 8 As shown, the specific steps of resource management include:

[0080] (1) Semi-automatic generation of resources and relationships: The system first automatically generates a preliminary topological diagram of the relationships between cloud network resources based on the association relationships of the cloud management platform. The generated resources and relationships are only basic information, representing the resource configuration status initially identified by the system.

[0081] (2) Enhancement and manual completion of canvas function: The present invention provides an interactive canvas function, where users can drag and drop on the canvas to supplement or modify the deficiencies of the system's automatic generation, and ultimately achieve accurate actual topology.

[0082] (3) Binding of display elements and logical entities: The resource elements and relationship lines drawn by the user on the canvas can be bound to specific cloud resources. Through this binding operation, the system can establish a mapping relationship between the icon and the actual resource, so that the display content on the canvas is consistent with the resource status of the background.

[0083] (4) Binding of display elements with custom events: The present invention supports users to bind custom events to display elements on the canvas. Users can select system-predefined event types (such as single click, double click, mouse in, mouse out, etc.), or enter custom response scripts. Through these event bindings, users can interact with backend services, making the display of resource topology no longer just static, but can interact dynamically based on real-time data.

[0084] (5) Dynamic display and real-time update: By binding custom events to backend services, users can trigger specific operations, such as obtaining the latest resource status, indicator information, alarm information, etc. Fig. 9 As shown in Figure 1, the system can dynamically update the displayed content on the canvas based on the feedback from the backend service. This dynamic display mechanism enables the resource topology map to not only reflect the current status, but also respond to changes in cloud resources in real time.

[0085] Through the above steps, cloud network resource management that supports dynamic binding can be realized, and a preliminary framework of resources and their relationships can be generated by a semi-automatic mechanism, which significantly reduces the workload of manual input by users. At the same time, the powerful canvas function is integrated, allowing users to easily complete or adjust the information of resources and their complex relationships through intuitive drag-and-drop operations, and realize dynamic construction and flexible adjustment of resource relationships. Users can not only tightly bind display elements with the logical entities of the backend to ensure real-time synchronization between the interface and the data source, but also directly associate display elements with front-end events to achieve instant feedback of user operations. This feature enables the resource relationship diagram to dynamically respond to data changes or user operations, such as updating resource status, adding, deleting and modifying relationships, which can be reflected in real time on the front-end interface, greatly improving the timeliness and accuracy of information display. By integrating the front-end event trigger mechanism, the system can seamlessly integrate and call back-end services. This means that users can not only intuitively view resource status and relationships on the resource relationship diagram, but also directly trigger back-end service requests such as resource configuration, performance monitoring, troubleshooting, etc. through simple operations such as clicking and dragging, realizing a leap from static display to dynamic operation, and from passive query to active service. This change greatly simplifies the operation process, improves operation and maintenance efficiency and user experience. Specifically, this application has the following advantages:

[0086] 1. Semi-automatic topology generation:

[0087] Through the method of the embodiment of the present application, the system can not only automatically generate a preliminary topological structure based on the dependencies and associations between resources, thereby greatly reducing manual operations, but also synchronously manage non-Cloud Namguan devices (in the manual completion step, through manual editing: based on the underlying topological data, by adding and editing topological nodes, the final business topology is formed), thereby achieving comprehensive resource complementarity and consistency maintenance. In the manual completion step, through manual editing: based on the underlying topological data, by adding and editing topological nodes, the final business topology is formed. In a cloud environment, resources are complexly distributed. The embodiment of the present application can help operation and maintenance personnel quickly generate and manage resource relationships between cloud platforms, and monitor resource status in real time.

[0088] 2. Dynamic binding and logical entity mapping:

[0089] Through the method of the embodiment of the present application, the topology elements can be bound to the actual cloud resources. By assigning a unique identifier to each element in the topology diagram and performing logical entity mapping with the actual cloud resources, the system can obtain and display the latest status information of the resources in real time. In daily operation and maintenance activities, a more intuitive visual monitoring method for the cloud environment can be provided.

[0090] 3. Custom events and dynamic interactions:

[0091] The embodiments of the present application support the binding of topology elements and custom events, allowing users to interact with backend services through event response mechanisms. These custom events can directly trigger the call of backend services to achieve dynamic management and control of resources. This feature makes the topological display of cloud resources no longer static, but can be updated and respond to user operations in real time, thereby achieving a dynamic interactive effect. When a fault occurs, operation and maintenance personnel can directly obtain detailed resource status, indicator information, and alarm information through dynamic topology components, and can directly determine the scope of the fault impact, helping to quickly locate the problem and take measures.

[0092] The core of the embodiment of the present application lies in the dynamic binding technology, which realizes the instant binding of various devices and scripts, so that the resource relationship diagram is not only a static display, but also a real-time operable platform. Compared with the limitation of traditional topology diagrams that only display limited resources and static information, the embodiment of the present application adopts a semi-automatic generation method to comprehensively and intuitively display the resources on the cloud on the canvas. By dragging and dropping the page, users can easily complete the resource relationship diagram, which can not only display network topology information, but also fully display business processes and the relationships between components within various subsystems. The binding of various devices and scripts is realized through dynamic binding, so as to realize real-time control and management of various resources on a relationship diagram.

[0093] Traditional consoles can often only manage their own subsystems, resulting in fragmented and inefficient operation and maintenance work. However, the embodiments of the present application break down the barriers between systems through a unified resource relationship diagram, and realize resource integration and unified management across manufacturers and subsystems. It not only reduces the cumbersome steps of logging into multiple systems, but also avoids association errors and management blind spots caused by the lack of data intercommunication between systems. When a fault or alarm occurs, the embodiments of the present application can quickly locate the source of the fault through a real-time dynamic resource relationship diagram, and provide an intuitive operation interface for rapid response. This method controls all resources on a resource relationship diagram, which can greatly improve the efficiency and reliability of cloud-network integrated operation and maintenance management, reduce operating costs, and not only shorten the fault recovery time, but also improve the stability and reliability of the entire cloud-network system. It has important practical significance and broad application prospects.

[0094] The present application embodiment provides a cloud network resource management device, Fig.10 is a schematic diagram of the structure of the device, such as Fig.10As shown, the device includes: a first processing module 100, which is used to obtain cloud network resource data, and generate a first topology map based on the cloud network resource data and display the first topology map on a canvas, wherein the nodes in the first topology map are used to represent the cloud network resource data, and the edges between the nodes are used to represent the association relationship between the cloud network resource data; a second processing module 102, which is used to adjust the first topology map to obtain a second topology map in response to an operation instruction for the first topology map detected in a visual editor; a third processing module 104, which is used to respond to a logical entity binding instruction, and bind the logical entity indicated by the logical entity binding instruction in the canvas to the element in the canvas, wherein the element includes: a node in the second topology map, an edge in the second topology map, and a visual component in the canvas other than the second topology map; a fourth processing module 106, which is used to respond to an event binding instruction for the element in the canvas, and bind the event indicated by the event binding instruction to the element in the canvas.

[0095] In some embodiments of the present application, the operation instruction includes a drag instruction; in response to the operation instruction for the first topology diagram detected in the visual editor, adjusting the first topology diagram to obtain the second topology diagram includes: responding to the drag instruction, adding an edge corresponding to the drag instruction in the first topology diagram to obtain the second topology diagram, wherein the edge corresponding to the drag instruction is at least used to reflect the physical link from the user business end to the entrance to the cloud to the virtual core firewall.

[0096] In some embodiments of the present application, in response to an operation instruction for a first topology map detected in a visual editor, after adjusting the first topology map to obtain a second topology map, the method also includes: saving the execution result of the operation instruction as json record data, and storing the json record data in a database.

[0097] In some embodiments of the present application, the second processing module 102 responds to the logical entity binding instruction to bind the logical entity indicated by the logical entity binding instruction in the canvas and the element in the canvas, including: determining the logical entity indicated by the logical entity binding instruction based on the device type and device IP address carried in the logical entity binding instruction; binding the unique identifier of the logical entity to the element in the canvas; saving the binding result as json record data, and storing the json record data in a database.

[0098] In some embodiments of the present application, the third processing module 104 responds to the logical entity binding instruction to bind the logical entity indicated by the logical entity binding instruction in the canvas and the element in the canvas, including: determining the device state corresponding to the unique identifier through the unique identifier; and updating the element attributes of the element bound to the unique identifier according to the device state.

[0099] In some embodiments of the present application, an event binding instruction includes an event binding script; in response to an event binding instruction for an element in a canvas, binding the event indicated by the event binding instruction and the element in the canvas includes: determining, based on the event binding script, a target element indicated by the event binding instruction; determining, based on the event binding script, an event type of the event and a trigger action to be performed after the event is triggered; configuring the target element based on the event type and the trigger action, thereby binding the event to the target element; saving the binding result as json record data, and storing the json record data in a database.

[0100] In some embodiments of the present application, the method also includes: executing the action indicated by the triggered event through a callback function, wherein the callback function includes a first field, a second field and a third field, the first field is used to identify the event type of the event, the second field is used to identify the element object of the element associated with the event, the element object includes attribute information and association information of the element, and the third field is used to pass associated data of the event.

[0101] It should be noted that the various modules in the above-mentioned cloud network resource management device can be program modules (for example, a set of program instructions that implement a certain specific function) or hardware modules. For the latter, it can be expressed in the following forms, but is not limited to this: the expression form of each of the above-mentioned modules is a processor, or the functions of each of the above-mentioned modules are implemented by a processor.

[0102] An embodiment of the present application provides a non-volatile storage medium, in which a program is stored, wherein when the program is running, the device where the non-volatile storage medium is located is controlled to execute the following cloud network resource management method: obtaining cloud network resource data, and generating a first topology map based on the cloud network resource data and displaying the first topology map on a canvas, wherein the nodes in the first topology map are used to represent the cloud network resource data, and the edges between the nodes are used to represent the association relationship between the cloud network resource data; in response to an operation instruction for the first topology map detected in a visual editor, adjusting the first topology map to obtain a second topology map; in response to a logical entity binding instruction, binding the logical entity indicated by the logical entity binding instruction in the canvas to the element in the canvas, wherein the element includes: the node in the second topology map, the edge in the second topology map and the visual component in the canvas except the second topology map; in response to an event binding instruction for the element in the canvas, binding the event indicated by the event binding instruction to the element in the canvas.

[0103] An embodiment of the present application provides an electronic device, including: a memory and a processor, the processor being used to run a program stored in the memory, wherein the program executes the following cloud network resource management method when it is run: obtaining cloud network resource data, and generating a first topology map based on the cloud network resource data and displaying the first topology map on a canvas, wherein the nodes in the first topology map are used to represent the cloud network resource data, and the edges between the nodes are used to represent the association relationship between the cloud network resource data; in response to an operation instruction for the first topology map detected in a visual editor, adjusting the first topology map to obtain a second topology map; in response to a logical entity binding instruction, binding the logical entity indicated by the logical entity binding instruction in the canvas to the element in the canvas, wherein the element includes: the node in the second topology map, the edge in the second topology map and the visual component in the canvas other than the second topology map; in response to an event binding instruction for the element in the canvas, binding the event indicated by the event binding instruction to the element in the canvas.

[0104] An embodiment of the present application provides a computer program product, including a computer program, which implements the following cloud network resource management method when executed by a processor: obtaining cloud network resource data, generating a first topology map based on the cloud network resource data and displaying the first topology map on a canvas, wherein the nodes in the first topology map are used to represent the cloud network resource data, and the edges between the nodes are used to represent the association relationship between the cloud network resource data; in response to an operation instruction for the first topology map detected in a visual editor, adjusting the first topology map to obtain a second topology map; in response to a logical entity binding instruction, binding the logical entity indicated by the logical entity binding instruction in the canvas to the element in the canvas, wherein the element includes: the node in the second topology map, the edge in the second topology map and the visual component in the canvas other than the second topology map; in response to an event binding instruction for the element in the canvas, binding the event indicated by the event binding instruction to the element in the canvas.

[0105] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0106] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0107] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0108] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0109] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the relevant technology or all or part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk, etc. Various media that can store program codes.

[0110] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A cloud network resource management method, characterized in that: include: Acquire cloud network resource data, generate a first topology graph based on the cloud network resource data, and display the first topology graph on a canvas, wherein the nodes in the first topology graph are used to represent the cloud network resource data, and the edges between the nodes are used to represent the association relationship between the cloud network resource data; In response to an operation instruction for the first topology map detected in the visual editor, adjusting the first topology map to obtain a second topology map; In response to a logical entity binding instruction, binding the logical entity indicated by the logical entity binding instruction in the canvas with an element in the canvas, wherein the element includes: a node in the second topological graph, an edge in the second topological graph, and a visual component in the canvas other than the second topological graph; In response to an event binding instruction for an element in the canvas, an event indicated by the event binding instruction is bound to the element in the canvas.

2. The cloud network resource management method according to claim 1, characterized in that: The operation instruction includes a drag instruction; In response to an operation instruction for the first topology map detected in the visual editor, adjusting the first topology map to obtain a second topology map includes: In response to the drag instruction, an edge corresponding to the drag instruction is added to the first topology map to obtain the second topology map, wherein the edge corresponding to the drag instruction is at least used to reflect the physical link from the user business end to the cloud entrance to the virtual core firewall.

3. The cloud network resource management method according to claim 1, characterized in that: In response to an operation instruction for the first topology map detected in the visual editor, after adjusting the first topology map to obtain a second topology map, the method further includes: The execution result of the operation instruction is saved as JSON record data, and the JSON record data is stored in a database.

4. The cloud network resource management method according to claim 1, characterized in that: In response to the logical entity binding instruction, binding the logical entity indicated by the logical entity binding instruction in the canvas with the element in the canvas includes: Determine the logical entity indicated by the logical entity binding instruction according to the device type and device IP address carried in the logical entity binding instruction; Binding a unique identifier of the logical entity to an element in the canvas; The binding result is saved as json record data, and the json record data is stored in the database.

5. The cloud network resource management method according to claim 4, characterized in that: In response to the logical entity binding instruction, binding the logical entity indicated by the logical entity binding instruction in the canvas with the element in the canvas includes: Determine, by means of the unique identifier, a device status corresponding to the unique identifier; An element attribute of an element bound to the unique identifier is updated according to the device state.

6. The cloud network resource management method according to claim 1, characterized in that: The event binding instruction includes an event binding script; in response to the event binding instruction for the element in the canvas, binding the event indicated by the event binding instruction with the element in the canvas includes: Determine the target element indicated by the event binding instruction according to the event binding script; Determine the event type of the event and the trigger action to be executed after the event is triggered according to the event binding script; Configuring the target element according to the event type and the trigger action, thereby binding the event to the target element; The binding result is saved as json record data, and the json record data is stored in the database.

7. The cloud network resource management method according to claim 1, characterized in that: The method further comprises: The action indicated by the triggered event is executed through a callback function, wherein the callback function includes a first field, a second field and a third field, the first field is used to identify the event type of the event, the second field is used to identify the element object of the element associated with the event, the element object includes attribute information and associated information of the element, and the third field is used to pass associated data of the event.

8. A cloud network resource management device, characterized in that: include: A first processing module, used to obtain cloud network resource data, generate a first topology graph based on the cloud network resource data, and display the first topology graph on a canvas, wherein the nodes in the first topology graph are used to represent the cloud network resource data, and the edges between the nodes are used to represent the association relationship between the cloud network resource data; A second processing module, configured to adjust the first topology map to obtain a second topology map in response to an operation instruction for the first topology map detected in the visual editor; a third processing module, configured to bind the logical entity indicated by the logical entity binding instruction in the canvas to the elements in the canvas in response to the logical entity binding instruction, wherein the elements include: nodes in the second topological graph, edges in the second topological graph, and visual components in the canvas other than the second topological graph; The fourth processing module is used to respond to the event binding instruction for the element in the canvas, and bind the event indicated by the event binding instruction with the element in the canvas.

9. A non-volatile storage medium, characterized in that: The non-volatile storage medium stores a program, wherein when the program is running, the device where the non-volatile storage medium is located is controlled to execute the cloud network resource management method described in any one of claims 1 to 7.

10. An electronic device, characterized in that: include: A memory and a processor, wherein the processor is used to run a program stored in the memory, wherein the program, when running, executes the cloud network resource management method described in any one of claims 1 to 7.

11. A computer program product, characterized in that It includes a computer program, which, when executed by a processor, implements the cloud network resource management method according to any one of claims 1 to 7.

Images