System architecture generation methods, devices, equipment, and storage media
By generating a system architecture diagram, the relationship between node instances and resource instances is clarified, which solves the problem of unclear system architecture management in existing technologies, enables accurate acquisition and management of system instance operation status, and improves the reliability and operability of the system.
Patent Information
- Application Number
- CN202311219897.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2023-09-20
- Publication Date
- 2026-11-17
- Estimated Expiration
- 2043-09-20
AI Technical Summary
Existing technologies cannot accurately reflect the status of all instances in the system architecture, making it impossible for administrators to obtain the operational status of each instance in the entire system. This is especially true in the rapidly developing cloud-based and distributed rolling iteration process of the communications industry, where the scale and complexity of the system are increasing, and there is a lack of a standard system for clear and effective management.
By obtaining the identification information of multiple node instances and their associated resource instances in the target system, and arranging them according to the calling relationships between node instances, a system architecture diagram is generated, clarifying the relationship between node instances and resource instances, and constructing a clear system architecture diagram.
It enables clear management of the system architecture, allowing administrators to quickly and accurately obtain the operational status of each instance, simplifying system management and maintenance, and improving system reliability and operability.
Smart Images

Figure CN118797733B_ABST
Abstract
Description
Technical Field
[0001] This application belongs to the field of data security technology, and in particular relates to a system architecture generation method, apparatus, device, and storage medium. Background Technology
[0002] Against the backdrop of rapid development in the telecommunications industry, the transformation of operator business support systems towards full cloudification and distributed rolling iteration is an inevitable trend. However, as the scale and complexity of the systems increase, the system architecture becomes increasingly complex.
[0003] Existing system architecture management methods cannot accurately reflect the status of all instances within the system architecture. Consequently, administrators are unable to accurately obtain the operational status of each instance throughout the entire system. Summary of the Invention
[0004] This application provides a system architecture diagram generation method, apparatus, device, and storage medium that can improve the security of privacy data.
[0005] In a first aspect, embodiments of this application provide a method for generating a system architecture diagram, the method comprising:
[0006] Obtain multiple node instances in the target system. The node instances are instantiated objects of nodes in the system architecture. The node instances include attribute information, including the identification information of resource instances associated with the node instances. The resource instances are instantiated objects of resources available for use in the system.
[0007] Based on the calling relationships between the node instances, the node instances are arranged to generate the system architecture diagram of the target system.
[0008] Secondly, embodiments of this application provide a system architecture diagram generation method apparatus, the apparatus comprising:
[0009] The first acquisition module is used to acquire multiple node instances in the target system. The node instance is an instantiated object of a node in the system architecture. The node instance includes attribute information, including the identification information of the resource instance associated with the node instance. The resource instance is an instantiated object of a resource available in the system.
[0010] The orchestration module is used to orchestrate the node instances according to the calling relationships between them, and generate the architecture diagram of the target system.
[0011] Thirdly, embodiments of this application provide a system architecture diagram generation method apparatus, the apparatus including: a processor and a memory storing computer program instructions;
[0012] The above system architecture diagram generation method is implemented when the processor executes computer program instructions.
[0013] Fourthly, embodiments of this application provide a computer storage medium storing computer program instructions, which, when executed by a processor, implement the above-described system architecture diagram generation method.
[0014] Fifthly, embodiments of this application provide a computer program product, the computer program product including computer program instructions, which, when executed by a processor, implement the above-described system architecture diagram generation method.
[0015] The system architecture generation method provided in this application can obtain multiple node instances in a target system. Each node instance includes attribute information, including identifiers of resource instances associated with it. Resource instances are instantiated objects of resources available in the system. Based on the calling relationships between node instances, the methods orchestrate these instances to obtain the system architecture diagram. This divides system instances into node instances and resource instances. Each node instance, acting as a node in the system architecture, has its associated resource instance identifiers added to its attribute information, thus linking resource instances to node instances. Then, based on the calling relationships between node instances, a system architecture diagram is constructed, resulting in a clearer diagram that allows administrators to quickly and accurately obtain the operational status of each instance within the entire system. Attached Figure Description
[0016] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the embodiments of this application will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0017] Figure 1 This is a schematic diagram of a system architecture diagram generation method provided in an embodiment of this application;
[0018] Figure 2 This is a schematic diagram of a system architecture diagram generation method provided in another embodiment of this application;
[0019] Figure 3 This is a schematic diagram of the system architecture management device provided in an embodiment of this application;
[0020] Figure 4 This is a schematic diagram of the system architecture diagram generation device provided in an embodiment of this application;
[0021] Figure 5This is a schematic diagram of the system architecture diagram generation device provided in one embodiment of this application. Detailed Implementation
[0022] The features and exemplary embodiments of various aspects of this application will be described in detail below. To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain this application and not to limit it. For those skilled in the art, this application can be implemented without some of these specific details. The following description of the embodiments is merely to provide a better understanding of this application by illustrating examples of this application.
[0023] It should be noted that, in this document, relational terms such as "objective" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising..." does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes the element.
[0024] It should be noted that, unless otherwise specified, the embodiments and features described in this application can be combined with each other.
[0025] With the rapid development of the telecommunications industry, operator business support systems are iterating towards full cloudification and distributed architecture. As systems grow larger, their coupling and complexity increase, leading to higher system operation and maintenance costs. The lack of comprehensive and accurate control over system construction and operation has become a major challenge for current operations and maintenance work, necessitating effective management of the system at the architectural level.
[0026] Current traditional architecture management methods only cover specific domains and lack a standardized system. This makes it difficult to clearly and effectively control the system's constituent instances and resource deployments, and also makes it difficult to fully and accurately represent the calling relationships between different levels of the system.
[0027] To address the problems of the prior art, embodiments of this application provide a system architecture diagram generation method, apparatus, device, storage medium, and program product. The system architecture diagram generation method provided in this application embodiment will be described first below.
[0028] Figure 1A flowchart illustrating a system architecture diagram generation method according to an embodiment of this application is shown. The method includes the following steps S101 to S102:
[0029] S101, Obtain multiple node instances in the target system.
[0030] Among them, a node instance is an instantiated object of a node in the system architecture. A node instance includes attribute information, including the identification information of the resource instance associated with the node instance. A resource instance is an instantiated object of a resource that is available for use in the system.
[0031] For example, a node instance can be an independent node or entity in a distributed system. In a system architecture, a node instance can represent a physical server, a virtual machine, or a container instance. Each node instance typically has its own unique identifier and possesses certain computing and storage capabilities. They can communicate with each other, exchange data, and collaborate to complete the system's tasks and functions. By properly planning and managing node instances, functions such as system elastic scaling, load balancing, and fault recovery can be achieved. In a distributed database system, a node instance can refer to each database node, with each node responsible for processing a portion of the data and query requests. In a containerized microservice architecture, a node instance can refer to a container instance running a specific microservice, with each instance running independently and handling its corresponding requests. Effective management of node instances can improve system reliability, performance, and operability, thereby better meeting business needs.
[0032] For example, in a cloud computing environment, resource instances are infrastructure provided by cloud service providers, and users can use and manage these instances on demand. For instance, a cloud server instance is a virtual machine instance allocated to a user, who can choose appropriate specifications (such as CPU, memory, and disk space) and create, start, stop, or destroy these instances as needed.
[0033] In one example, IaaS instances are categorized as resource instances; PaaS or SaaS instances are categorized as node instances.
[0034] Resource instances provide the infrastructure and are managed by the user, while node instances host specific applications or services and are managed by the provider.
[0035] S102, based on the calling relationships between node instances, orchestrate the node instances to generate the system architecture diagram of the target system.
[0036] Specifically, since the attribute information of each node instance includes the identification information of the resource instances associated with the node instance, the system architecture diagram can be generated simply by arranging the node instances, and the system architecture diagram can be made clearer, making it easier to manage the system architecture.
[0037] The system architecture diagram generation method provided in this application can obtain multiple node instances in a target system. Each node instance includes attribute information, including identifiers of resource instances associated with it. Resource instances are instantiated objects of resources available in the system. Based on the calling relationships between node instances, the methods orchestrate these instances to obtain the system architecture diagram. This divides system instances into node instances and resource instances. Each node instance, acting as a node in the system architecture, has its associated resource instance identifiers added to its attribute information, thus linking resource instances to node instances. Then, based on the calling relationships between node instances, a system architecture diagram is constructed, resulting in a clearer diagram that allows administrators to quickly and accurately obtain the operational status of each instance within the entire system.
[0038] In some embodiments, prior to S101 above, the following may also be included:
[0039] Obtain multiple system instances, including node instances and resource instances;
[0040] Based on the association between each node instance and each resource instance, add the identification information of the resource instance associated with the node instance to the attribute information of each node instance;
[0041] Store node instances in the instance information repository;
[0042] The above S101 may include:
[0043] Retrieve multiple node instances from the target system from the instance information repository.
[0044] Specifically, firstly, node instances can be pre-stored in the instance information database. For each node instance, based on its association with resource instances, the identification information of the resource instance associated with that node instance is added to the node instance's attribute information. The identification information can be a unique identifier of the resource instance, such as the resource instance's ID or name, or it can be the resource instance's IP address.
[0045] Storing node instances in an instance repository can be done by creating an instance repository and storing the node instances and their attribute information within it. The instance repository is essentially a database used to store node instances; this database can be a relational database, a NoSQL database, etc. Therefore, during the generation of a system architecture diagram, multiple node instances from the target system can be retrieved from the instance repository.
[0046] Here, the attribute information of node instances is generated based on unified definition rules. This ensures that the same node instances in the architecture diagrams of different systems remain consistent, thus improving the applicability of the architecture diagrams.
[0047] In some embodiments, before obtaining multiple node instances in the target system from the instance information database, the following may also be included:
[0048] If the target node instance does not exist in the instance information database, receive the first input to the instance information database;
[0049] In response to the first input, add the target node instance to the instance information repository.
[0050] Specifically, pre-storing multiple node instances in the instance information repository facilitates the subsequent orchestration of node instances to generate a system architecture diagram. However, since there are multiple types of node instances in the system, and node instances in different systems are not the same, it is impossible to pre-store node instances from all systems in the instance information repository. Therefore, if a certain node instance (i.e., the target node instance) in the target system does not exist in the instance information repository, the node instance, including its attribute information, can be added to the instance information repository beforehand.
[0051] In one example, assuming the target system includes node instance A, and node instance A does not exist in the instance information database, the attribute information of node instance A (such as associated resource instances) is first determined according to the unified definition rules, and then node instance A and its corresponding attribute information are added to the instance information database.
[0052] In some embodiments, the attribute information of the node instance may also include the type information of the node instance.
[0053] The above S102 may include:
[0054] A cluster component is generated based on the first node instance among multiple node instances, where the first node instance includes instances of the same type among the multiple node instances.
[0055] Based on the calling relationships between the second node instances and cluster components, the second node instances and cluster components are orchestrated to obtain the architecture diagram of the target system. The second node instance can be any node instance among multiple node instances.
[0056] The cluster component consists of multiple node instances of the same type. In practical applications, system architectures often include multiple node instances of the same type. For resource balancing and disaster recovery considerations, node instances of the same type are usually centrally allocated and managed. The cluster component can evenly distribute requests or tasks to the node instances within the cluster to achieve efficient resource utilization and load balancing. By dynamically adjusting the load distribution among node instances, it can prevent some nodes from becoming overloaded and causing performance degradation, while ensuring that other nodes have sufficient resources to handle requests. Furthermore, the multiple node instances in the cluster component can achieve redundancy and backup. When a node instance fails or becomes unavailable, other node instances can take over its work, ensuring the normal operation of the system. This improves the system's disaster recovery and availability, and reduces the risk of single points of failure.
[0057] In this embodiment, node instances of the same type can be grouped into cluster components. Representing multiple node instances of the same type as cluster components in the system architecture diagram allows administrators to more conveniently configure, deploy, and monitor node instances in a unified manner through the architecture diagram. In other words, administrators can perform batch operations on the entire cluster through cluster components, simplifying management and maintenance. Furthermore, centralized management of node instances also facilitates system monitoring, performance optimization, and troubleshooting.
[0058] In some embodiments, S102 may include:
[0059] The scene components are obtained by orchestrating the third-node instances based on the calling relationships between them. Each third-node instance can be any node instance from a set of multiple node instances.
[0060] Based on the calling relationship between the fourth node instance and the scene components, the fourth node instance and the scene components are arranged to generate the architecture diagram of the target system. The fourth node instance can be any node instance among multiple node instances.
[0061] Scenario components can be created by dividing the system into different scenario components based on requirements and functions. A scenario component is a relatively independent functional unit, which can consist of one or more node instances and is responsible for handling specific business logic or functional modules. Each scenario component should have clear responsibilities and interface definitions.
[0062] Specifically, when generating the system architecture, multiple node instances can be first grouped into scene components, and then the overall system architecture can be built using these scene components. This allows for better management and organization of the various node instances in the system, achieving high cohesion and low coupling among the node instances.
[0063] In some embodiments, node instances and cluster components can be orchestrated to obtain scene components.
[0064] In some embodiments, S102 may include:
[0065] Receive edit input for node instances.
[0066] In response to edit input, connect the fifth node instance and the sixth node instance. There is a calling relationship between the fifth node instance and the sixth node instance. The fifth node instance and the sixth node instance can be any two node instances from a plurality of node instances.
[0067] Specifically, after obtaining multiple node instances in the target system, any two node instances can be connected according to the calling relationship between them, thereby accurately constructing the system architecture of the target system.
[0068] In one example, multiple node instances of the target system can first be obtained from the instance information database. These node instances can be displayed in the display interface. Users can drag and drop the node instances that need to be connected into the architecture diagram drawing interface. Then, in the architecture diagram drawing interface, two node instances with a calling relationship are connected to draw the system architecture diagram.
[0069] Alternatively, cluster components can be created first based on node instances of the same type in the target system, or scenario components can be created for multiple different node instances based on different scenarios; then, a system architecture diagram can be generated based on node instances, cluster components, and scenario components.
[0070] In some embodiments, after S101 above, the following may also be included:
[0071] Get the newly added node instance;
[0072] The architecture diagram of the target system is updated based on the calling relationships between the newly added node instance and multiple node instances.
[0073] Specifically, after generating the system architecture diagram, if new node instances are added to the target system, the original system architecture diagram can be updated. If the newly added node instance does not exist in the instance information repository, it can be added to the instance information repository first, and then the system architecture diagram can be updated.
[0074] To facilitate understanding, the above system architecture diagram generation method will be explained below with specific scenarios. For example... Figure 2 As shown:
[0075] Steps 201-202: For IT systems that require architecture management, classify the system instances they contain. One category is PaaS or SaaS instances that run business operations, such as hardware load balancers, software load balancers, middleware, application processes, etc. (equivalent to node instances); the other category is IaaS instances that provide underlying resources, including virtual machines, physical machines, containers, etc. (equivalent to resource instances).
[0076] Step 203: When processing IaaS class instances, leaf nodes (i.e., node instances) are not constructed separately, but are added to the resource information database as basic resources. They are associated with leaf nodes through IP address and resource ID, and their resource ID is added to the selectable value range of the leaf node attribute field.
[0077] Steps 204-206: When processing PaaS or SaaS instances, first determine if the category is already defined in the instance baseline library. If it is defined, reuse it directly and enter it as a leaf node into the instance information library. Each leaf node defines the following attributes: node number, node type, resource ID, instance ID, version, IP, and group number. If it is not defined, proceed to the instance configuration module, add the instance category, and then continue to use the instance category to enter it into the instance information library.
[0078] Step 207: Based on the data in the instance information database, the instance is drawn as a leaf node in the topology drawing module. Multiple leaf nodes of the same type form a cluster component. The leaf nodes and cluster components are connected by lines to identify the calling relationship, further forming scene components. Components support reuse and orchestration, thus supporting the display of complex systems.
[0079] Step 208: Convert the completed architecture diagram into a standard format and enter it into the result storage module.
[0080] Using this method, we can categorize and classify various system instances and display them through the interface under a unified standard. Subsequent additions of instances or resources can also be described according to this standard.
[0081] In summary, system instances are categorized by characteristics and managed separately according to different categories. A topology map is drawn on the interface based on the entered information, and running instances are associated with resources through attribute fields, clearly displaying the internal calling relationships and resource deployment status of the system.
[0082] In one instance, this application also provides a system architecture management device such as Figure 3 As shown, the device mainly includes an instance management unit, a topology management unit, and a resource management unit. The instance management unit includes an instance baseline library, an instance information library, and an instance configuration module; the topology management unit includes a topology drawing module and a result storage module; and the resource management unit includes a resource information library.
[0083] The specific explanation is as follows:
[0084] 1. Instance benchmark library
[0085] Define different types of system running instances, and define their vector graphics, attribute fields, and other standards.
[0086] (Equivalent to the definition rules mentioned above)
[0087] 2. Instance Information Database
[0088] It stores information about each instance running in the storage system, recording attribute values such as instance ID, instance type, associated resource ID, and group ID.
[0089] 3. Instance Configuration Module
[0090] It supports adding, modifying, and deleting instance types.
[0091] 4. Topology drawing module
[0092] Resource attributes are associated with resource IDs, and connections are used to represent the call relationships between instances. Multiple leaf nodes of the same type are drawn to form cluster components to represent cloud-based clusters; leaf nodes and cluster components can be connected to identify call relationships, further forming scenario components; through further reuse and orchestration of nodes and components, more complex system architectures can be displayed, thereby building the architecture topology diagram of the IT system layer by layer.
[0093] The topology drawing module provides drawing operation functions, allowing users to draw leaf nodes directly by dragging and dropping a single instance using predefined instance information.
[0094] Based on the system architecture diagram generation method provided in the above embodiments, this application also provides specific implementations of the system architecture diagram generation apparatus. Please refer to the following embodiments.
[0095] First see Figure 4 The system architecture diagram generation device 400 provided in this application embodiment includes the following modules:
[0096] The first acquisition module 401 is used to acquire multiple node instances in the target system. The node instance is an instantiated object of a node in the system architecture. The node instance includes attribute information, including the identification information of the resource instance associated with the node instance. The resource instance is an instantiated object of a resource available in the system.
[0097] The orchestration module 402 is used to orchestrate the node instances according to the calling relationships between them, generating the architecture diagram of the target system.
[0098] The system architecture diagram generation device provided in this embodiment can acquire multiple node instances in a target system. Each node instance includes attribute information, including identifiers of resource instances associated with it. Resource instances are instantiated objects of resources available in the system. Based on the calling relationships between node instances, the device arranges these instances to obtain the architecture diagram of the target system. Thus, system instances are divided into node instances and resource instances. Each node instance, as a node in the system architecture, has its associated resource instance identifiers added to its attribute information, thereby associating resource instances with node instances. Then, based on the calling relationships between node instances, a system architecture diagram is constructed, resulting in a clearer diagram that allows administrators to quickly and accurately obtain the operational status of each instance in the entire system.
[0099] In some embodiments, the above-described apparatus further includes:
[0100] The second acquisition module is used to acquire multiple system instances, including node instances and resource instances;
[0101] The first addition module is used to add the identification information of the resource instance associated with the node instance to the attribute information of each node instance based on the association relationship between each node instance and each resource instance.
[0102] The storage module is used to store node instances in the instance information repository;
[0103] The aforementioned first acquisition module includes:
[0104] The acquisition unit is used to acquire multiple node instances from the instance information database in the target system.
[0105] In some embodiments, the above-described apparatus further includes:
[0106] The first receiving module is used to receive the first input to the instance information database when the target node instance does not exist in the instance information database;
[0107] The second add module is used to add the target node instance to the instance information database in response to the first input.
[0108] In some embodiments, the attribute information of the node instance may also include the type information of the node instance.
[0109] The above-mentioned orchestration module 402 includes:
[0110] The first generation unit is used to generate cluster components based on the first node instance among multiple node instances. The first node instance includes instances of the same type among the multiple node instances.
[0111] The first orchestration unit is used to orchestrate each second node instance and cluster component according to the calling relationship between the second node instance and the cluster component to obtain the architecture diagram of the target system. The second node instance can be any node instance among multiple node instances.
[0112] In some embodiments, the above-described orchestration module 402 includes:
[0113] The first receiving unit is used to receive edit input for node instances.
[0114] The drawing unit is used to connect the fifth node instance and the sixth node instance in response to the editing input, and generate the system architecture diagram of the target system. There is a calling relationship between the fifth node instance and the sixth node instance, and the fifth node instance and the sixth node instance can be any two node instances from multiple node instances.
[0115] In some embodiments, the above-described apparatus further includes:
[0116] The third acquisition module is used to acquire newly added node instances;
[0117] The update module is used to update the architecture diagram of the target system based on the calling relationships between newly added node instances and multiple node instances.
[0118] Figure 5 A schematic diagram of the hardware structure of the system architecture diagram generation method device provided in this application embodiment is shown.
[0119] The system architecture diagram generation method device may include a processor 501 and a memory 502 storing computer program instructions.
[0120] Specifically, the processor 501 may include a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of this application.
[0121] Memory 502 may include mass storage for data or instructions. For example, and not limitingly, memory 502 may include a hard disk drive (HDD), floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or Universal Serial Bus (USB) drive, or a combination of two or more of these. Where appropriate, memory 502 may include removable or non-removable (or fixed) media. Where appropriate, memory 502 may be internal or external to the integrated gateway disaster recovery device. In a particular embodiment, memory 502 is non-volatile solid-state memory.
[0122] Memory may include read-only memory (ROM), random access memory (RAM), disk storage media devices, optical storage media devices, flash memory devices, and electrical, optical, or other physical / tangible memory storage devices. Therefore, typically, memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the methods according to one aspect of this disclosure.
[0123] The processor 501 reads and executes computer program instructions stored in the memory 502 to implement any of the system architecture diagram generation methods in the above embodiments.
[0124] In one example, the system architecture diagram generation method device may further include a communication interface 503 and a bus 510. Wherein, as Figure 5 As shown, the processor 501, memory 502, and communication interface 503 are connected through bus 510 and complete communication with each other.
[0125] The communication interface 503 is mainly used to realize communication between various modules, devices, units and / or equipment in the embodiments of this application.
[0126] Bus 510 includes hardware, software, or both, that couples components of the system architecture diagram generation method device together. For example, and not limitingly, the bus may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), HyperTransport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Low Pin Count (LPC) bus, a memory bus, a Microchannel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local (VLB) bus, or other suitable buses, or combinations of two or more of these. Where appropriate, bus 510 may include one or more buses. Although specific buses are described and illustrated in embodiments of this application, this application contemplates any suitable bus or interconnect.
[0127] The system architecture diagram generation method and device can be based on the above embodiments to achieve the combination. Figures 1 to 4 The system architecture diagram generation method and apparatus are described.
[0128] Furthermore, in conjunction with the system architecture diagram generation method in the above embodiments, this application embodiment can provide a computer storage medium for implementation. This computer storage medium stores computer program instructions; when these computer program instructions are executed by a processor, they implement any of the system architecture diagram generation methods in the above embodiments and achieve the same technical effect. To avoid repetition, further details are omitted here. The aforementioned computer-readable storage medium may include non-transitory computer-readable storage media, such as read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks, etc., and is not limited thereto.
[0129] In addition, this application also provides a computer program product, including computer program instructions, which, when executed by a processor, can implement the steps and corresponding content of the aforementioned method embodiments.
[0130] It should be clarified that this application is not limited to the specific configurations and processes described above and shown in the figures. For the sake of brevity, detailed descriptions of known methods are omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of this application is not limited to the specific steps described and shown. Those skilled in the art can make various changes, modifications, and additions, or change the order of steps, after understanding the spirit of this application.
[0131] The functional blocks shown in the above block diagram can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application-specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of this application are programs or code segments used to perform the required tasks. Programs or code segments can be stored on a machine-readable medium or transmitted over a transmission medium or communication link via data signals carried on a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio frequency (RF) links, etc. Code segments can be downloaded via computer networks such as the Internet, intranets, etc.
[0132] It should also be noted that the exemplary embodiments mentioned in this application describe methods or systems based on a series of steps or apparatus. However, this application is not limited to the order of the above steps; that is, the steps can be performed in the order mentioned in the embodiments, or in a different order, or several steps can be performed simultaneously.
[0133] The aspects of this disclosure have been described above with reference to flowchart illustrations and / or block diagrams of methods, apparatuses, and computer program products according to embodiments of this disclosure. It should be understood that each block in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable system architecture generation method apparatus to produce a machine such that these instructions, executable via the processor of the computer or other programmable system architecture generation method apparatus, enable the implementation of functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It is also understood that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can also be implemented by special-purpose hardware performing the specified functions or actions, or can be implemented by a combination of special-purpose hardware and computer instructions.
[0134] The above are merely specific embodiments of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, modules, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. It should be understood that the protection scope of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the protection scope of this application.
Claims
1. A method for generating a system architecture diagram, characterized in that, The method includes: The system acquires multiple node instances in the target system. Each node instance is an instantiated object of a node in the IT system's system architecture. Each node instance includes attribute information, including identifier information of resource instances associated with it. This attribute information is generated based on unified definition rules. Each resource instance is an instantiated object of a usable resource in the IT system. The target system is a fully cloud-based, distributed, and iteratively iterative carrier business support IT system. The node instances include PaaS instances and SaaS instances, and the resource instances include IaaS instances. Based on the calling relationships between the node instances, the node instances are arranged to generate the system architecture diagram of the target system; The attribute information of the node instance also includes the type information of the node instance. The step of arranging the node instances according to the calling relationships between them to obtain the architecture diagram of the target system includes: A cluster component is generated based on a first node instance among the plurality of node instances, wherein the first node instance includes instances of the same type among the plurality of node instances. Based on the calling relationship between the second node instance and the cluster component, each second node instance and the cluster component are orchestrated to obtain the architecture diagram of the target system, wherein the second node instance is any node instance among the multiple node instances; The third node instances are arranged based on the calling relationships between them to obtain scene components. Each third node instance can be any one of the multiple node instances. Based on the calling relationship between the fourth node instance and the scene component, each fourth node instance and the scene component are arranged to generate the architecture diagram of the target system. The fourth node instance is any node instance among the multiple node instances. If the newly added node instance does not exist in the instance information database of the target system, the newly added node instance is added to the instance information database, and the architecture diagram is updated based on the newly added node instance and the calling relationship between the newly added node instance and the node instance.
2. The method according to claim 1, characterized in that, Before obtaining multiple node instances in the target system, the process also includes: Obtain multiple system instances, including node instances and resource instances; Based on the association between each node instance and each resource instance, add the identification information of the resource instance associated with the node instance to the attribute information of each node instance; Store the node instance in the instance information database; The acquisition of node instances in the target system includes: Obtain multiple node instances from the target system from the instance information database.
3. The method according to claim 2, characterized in that, Before obtaining multiple node instances from the target system from the instance information database, the method further includes: If no target node instance exists in the instance information database, receive the first input to the instance information database; In response to the first input, the target node instance is added to the instance information database.
4. The method according to claim 1, characterized in that, The step of arranging the node instances according to the calling relationships between them to obtain the architecture diagram of the target system includes: Receive edit input for the node instance. In response to the edit input, the fifth node instance and the sixth node instance are connected to generate the architecture diagram of the target system. There is a calling relationship between the fifth node instance and the sixth node instance, and the fifth node instance and the sixth node instance are any two node instances among the plurality of node instances.
5. The method according to claim 1, characterized in that, Based on the calling relationships between the node instances, the node instances are orchestrated to obtain the architecture diagram of the target system. This then includes: Get the newly added node instance; The architecture diagram of the target system is updated based on the calling relationship between the newly added node instance and the multiple node instances.
6. A system architecture diagram generation device, characterized in that, The device includes: The first acquisition module is used to acquire multiple node instances in the target system. The node instances are instantiated objects of nodes in the system architecture of the IT system. The node instances include attribute information, including identification information of resource instances associated with the node instances. The attribute information is generated based on unified definition rules. The resource instances are instantiated objects of resources available for use in the IT system. The target system is a fully cloud-based, distributed, and iteratively updated operator business support IT system. The node instances include PaaS instances and SaaS instances, and the resource instances include IaaS instances. The orchestration module is used to orchestrate the node instances according to the calling relationships between them, and generate the architecture diagram of the target system. The attribute information of the node instance also includes the type information of the node instance. The step of arranging the node instances according to the calling relationships between them to obtain the architecture diagram of the target system includes: A cluster component is generated based on a first node instance among the plurality of node instances, wherein the first node instance includes instances of the same type among the plurality of node instances. Based on the calling relationship between the second node instance and the cluster component, each second node instance and the cluster component are orchestrated to obtain the architecture diagram of the target system, wherein the second node instance is any node instance among the multiple node instances; The third node instances are arranged based on the calling relationships between them to obtain scene components. Each third node instance can be any one of the multiple node instances. Based on the calling relationship between the fourth node instance and the scene component, each fourth node instance and the scene component are arranged to generate the architecture diagram of the target system. The fourth node instance is any node instance among the multiple node instances. If the newly added node instance does not exist in the instance information database of the target system, the newly added node instance is added to the instance information database, and the architecture diagram is updated based on the newly added node instance and the calling relationship between the newly added node instance and the node instance.
7. An electronic device, characterized in that, The device includes: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, it implements the steps of the method as described in any one of claims 1-5.
8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer program instructions that, when executed by a processor, implement the steps of the method as described in any one of claims 1-5.
Citation Information
Patent Citations
Method and device for generating example service topology
CN109586938A
Network simulation method and device, equipment and storage medium
CN113037545A
Edge distributed management and control system, method and equipment and storage medium
CN114301909A
Container cluster scheduling method and device, equipment and storage medium
CN115408100A
