CN117348966A - Topology management method, electronic equipment and storage media based on open application model - Google Patents
Topology management method, electronic equipment and storage media based on open application model Download PDFInfo
- Publication number
- CN117348966A CN117348966A CN202210736846.6A CN202210736846A CN117348966A CN 117348966 A CN117348966 A CN 117348966A CN 202210736846 A CN202210736846 A CN 202210736846A CN 117348966 A CN117348966 A CN 117348966A
- Authority
- CN
- China
- Prior art keywords
- model
- information
- application
- resource
- component
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/4557—Distribution of virtual machine instances; Migration and load balancing
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the invention discloses a topology management method, electronic equipment and a storage medium based on an open application model, wherein the method comprises the following steps: adding model labels to model objects and model resources in an open application model to obtain label information, wherein the model objects comprise: an application component, a deployment component, and an operation and maintenance feature; reading blueprint information and state information of an application component, wherein the blueprint information comprises reference relations among model objects, and the state information comprises model resources associated with the application component; establishing a topological relation between model objects according to the blueprint information and the state information; model resources are attributed to deployment components and operational characteristics associated with the application components based on the tag information. The scheme of the embodiment of the application can globally and intuitively reflect the topological hierarchy relation of all model objects in the system, reduce the operation and maintenance difficulty and cost and improve the use experience of users.
Description
Technical Field
The present invention relates to the field of topology management technologies, and in particular, to a topology management method based on an open application model, an electronic device, and a storage medium.
Background
With the widespread use of Cloud computing, the concept of Cloud Native (Cloud Native) has grown, with microservices and containerization as their core technologies, and the application of containers on various types of public Cloud platforms has shown dramatic growth. Among them, kubernetes (K8S) is currently the most powerful container orchestration engine. However, the container management platform mainly comprising K8S is oriented to and encapsulates the underlying infrastructure, so that the upper layer service personnel need to rapidly deploy and apply the complex infrastructure concept and management in K8S, and a great learning cost is required. Accordingly, the combination of ali cloud and microsoft pushes out an open application model (Open Application Model, OAM) that provides a user with a standard, highly consistent model that is focused on application management through uniform, standard application-centric application programming interface (Application Programming Interface, API) resources.
At present, an open Application model encapsulates bottom resources, and although the convenience of shielding a bottom infrastructure is brought to a user, a plurality of inconveniences are brought to a platform developer, namely, as the topological hierarchical relationship of all Application resources in a system cannot be intuitively reflected from the whole, the monitoring of the Application creation resource state can only depend on the state output of an Application component (Application) in the model, and the problems of simple state information and poor real-time state feedback exist; in addition, the abstract function of the application component shields the actually created resource for the user, and when the state of the application component deviates from the state of the actually deployed resource, the user can hardly find out the problem, and the operation and maintenance difficulty and the cost are increased.
Disclosure of Invention
The embodiment of the application provides a topology management method, a device, electronic equipment and a storage medium based on an open application model, which can globally and intuitively reflect the topology hierarchical relation of all model objects in a system, ensure that the topology relation can accurately and rapidly reflect the state of an application component, and reduce the operation and maintenance difficulty and cost.
In a first aspect, an embodiment of the present application provides a topology management method based on an open application model, where the method includes: adding model labels to model objects and model resources in an open application model to obtain label information, wherein the model objects comprise: an application component, a deployment component, and an operation and maintenance feature; reading blueprint information and state information of the application component, wherein the blueprint information comprises reference relations among the model objects; the state information includes the model resource associated with the application component; establishing a topological relation between the model objects according to the blueprint information and the state information; attributing the model resource to the deployment component and the operational feature associated with the application component according to the tag information.
In a second aspect, an embodiment of the present application provides a topology management apparatus based on an open application model, including: the adding module is used for adding model labels to model objects and model resources in the open application model to obtain label information, wherein the model objects comprise: an application component, a deployment component, and an operation and maintenance feature; the reading module is used for reading blueprint information and state information of the application component, wherein the blueprint information comprises reference relations among the model objects; the state information includes model resources associated with the application component; the establishing module is used for establishing a topological relation between the model objects according to the blueprint information and the state information; and the association module is used for attributing the model resource to the deployment component and the operation and maintenance feature associated with the application component according to the label information.
In a third aspect, an embodiment of the present application provides an electronic device, including: the topology management method based on the open application model provided by the embodiment of the application is realized when the processor executes the computer program.
In a fourth aspect, embodiments of the present application provide a computer readable storage medium storing a computer program, where when executed by a computer program processor, implements the topology management method based on the open application model provided in the embodiments of the present application.
According to the embodiment of the application, the label information is obtained by adding the model labels to the model objects and the model resources in the open application model; reading blueprint information and state information of the application component; establishing a topological relation between the model objects according to the blueprint information and the state information; attributing the model resource to the deployment component and the operational feature associated with the application component according to the tag information. The scheme of the embodiment of the application can globally and intuitively reflect the topological hierarchy relation of all model objects in the system, ensure that the topological relation can accurately and rapidly reflect the state of the application component, reduce the operation and maintenance difficulty and cost and improve the use experience of users.
Drawings
Fig. 1 is a schematic flow chart of a topology management method based on an open application model according to an embodiment of the present application;
FIG. 2 is a schematic diagram illustrating a specific implementation procedure of another embodiment of step S1000 in FIG. 1;
FIG. 3 is a schematic diagram illustrating a specific implementation procedure of another embodiment of step S3000 in FIG. 2;
FIG. 4 is a schematic diagram illustrating a specific implementation procedure of another embodiment of step S4000 in FIG. 1;
FIG. 5 is a schematic diagram illustrating a specific implementation procedure of another embodiment of step S4300 in FIG. 1;
FIG. 6 is a block diagram of a topology management device based on an open application model according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be further described in detail with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the present application.
It should be appreciated that in the description of the embodiments of the present application, if any, the descriptions of "first," "second," etc. are used for the purpose of distinguishing between technical features only, and are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated or implicitly indicating the precedence of the technical features indicated. "at least one" means one or more, and "a plurality" means two or more. "and/or", describes an association relation of association objects, and indicates that there may be three kinds of relations, for example, a and/or B, and may indicate that a alone exists, a and B together, and B alone exists. Wherein A, B may be singular or plural. The character "/" generally indicates that the context-dependent object is an "or" relationship. "at least one of the following" and the like means any combination of these items, including any combination of single or plural items. For example, at least one of a, b and c may represent: a, b, c, a and b, a and c, b and c or a and b and c, wherein a, b and c can be single or multiple.
In addition, technical features described below in the various embodiments of the present application may be combined with each other as long as they do not conflict with each other.
The topology management method based on the open application model is based on the open application model to establish and manage the topology relationship, and the state of the application component is accurately and rapidly reflected by establishing the topology relationship among model objects so as to improve the observability of the application component and facilitate the operation and maintenance of platform personnel.
In order to ensure observability of application components in an open application model, the existing topology management method based on the open application model is as follows: by inquiring information of the application components through the API, a user and a platform developer can inquire application deployment states through an API interface, or by expanding the API interface, resource information can be inquired in a self-defined mode, observability of the application components is improved, and response can be timely made when problems occur to the application. However, the resource information obtained in this way is limited, and an application component can only query the state of its corresponding deployed container, but cannot query the type of Workload (Workload) and associated resources it uses, by way of example; in addition, if the user has the inquiry requirement of other resources, secondary development and expansion are needed, and the operation and maintenance cost is increased; moreover, since the topological hierarchical relationship of all model objects in the open application model is not globally and intuitively reflected, efficient and accurate development and maintenance cannot be realized in the application scene of the open application model.
Based on the above, the embodiments of the present application provide a topology management method, apparatus, electronic device and computer readable storage medium based on an open application model, where tag information is obtained by adding a model tag to a model object in the open application model; reading state information of an application component; establishing a topological relation between model objects according to the label information and the state information; according to the topological relation, model resources are attributed to deployment components and operation and maintenance features associated with application components, so that the purpose of globally and intuitively reflecting the topological hierarchical relation of all model objects in the system is achieved, the topological relation can be ensured to accurately and rapidly reflect the state of the application components, the operation and maintenance difficulty and cost are reduced, and the use experience of users is improved.
Referring to fig. 1, fig. 1 shows a flow of a topology management method based on an open application model according to an embodiment of the present application. As shown in fig. 1, the topology management method based on the open application model according to the embodiment of the present application includes the following steps:
s1000, adding model labels to model objects and model resources in an open application model to obtain label information, wherein the model objects comprise: an application component, a deployment component, and an operation and maintenance feature.
It will be appreciated that the core model objects of the open application model mainly include application components, deployment components (components) and operational dimension features (tracks). The deployment components are in one-to-one correspondence with the workload of the model bottom layer; the operation and maintenance features are mounted on specific deployment components; and the application component is composed of a plurality of deployment components and operation and maintenance feature superposition. Thus, the open application model provides a user with a standard, highly consistent model that is focused on application management through uniform, standard application component-centric API resources. In addition, the open application model shields the upper layer users from the underlying complex infrastructure management, allowing application developers to focus more on what the application components themselves exhibit, rather than the specific deployment process of the application components.
It will be appreciated that the interfaces of the application component, deployment component and the operation and maintenance feature all have fields of the original data tag, such as metadata, labels, according to the interface definition specification of the model object by the open application model. Thus, these fields can be utilized to establish associations between application components, deployment components, and operational characteristics. In order to improve the accuracy and uniformity of model labels, the links between model objects can be quickly and accurately established, and unified model labels can be added to each model object and model resources packaged by each model object in the running process of an open application model. The situation that the relation between model objects is incomplete is effectively avoided, and the referenceability of the model labels is improved.
Exemplary model tags include, but are not limited to, application name (app_name), resource type (resource_type), deployment object type (component_type), deployment object name (component_name), operation and maintenance feature type (track_type), operation and maintenance feature name (track_name), cluster name (cluster_name), and tenant Namespace (name_name).
It can be understood that by adding the model labels to the model objects and the model resources in the open application model, label information for accurately describing data association, causal relation and the like between the model objects is formed in the application component, the deployment component and the operation and maintenance feature, so that the interactive relation between the model objects and the model resources can be conveniently and accurately reflected, and the situation that the model labels are not uniform and cannot be matched is avoided.
Referring to fig. 2, fig. 2 is a schematic diagram illustrating a specific implementation procedure of another embodiment of the step S1000. As shown in fig. 2, step S1000 includes at least the following steps:
s1100, in the case that the model object directly encapsulates the model resource, a model label is added to the model object and the model resource.
It can be appreciated that in the case where the application component directly encapsulates the model resource, the API query interface of the open application model runtime reads the blueprint information and the state information of the application component. Then, a unified model tag is identified for each model object and the encapsulated model resources. In the method, the adding operation is automatically performed through the application component by the open application model, so that the process of adding the model label belongs to the non-perception operation for an upper application user, and the operation process of the model label does not cause constraint on the user.
S1200, when the model object indirectly encapsulates the model resource, adding a corresponding model label when instantiating the model object.
It may be appreciated that in the case where the model object encapsulates the model resource indirectly, that is, the model object does not encapsulate the model resource directly, and when the model object encapsulates the model resource of the third party component, the open application model runtime parses the model object, and then cannot identify the corresponding model resource, such as the Helm application package, and after the key words of the resource tag need to be constrained, the user adds the corresponding tag when instantiating the model object. Thus, the operation process thereof has a forced constraint on the user.
It will be appreciated that the process of instantiating a model object is the process of creating a model object from existing model object templates. In the process of creating the model object, a designated model label, such as a Cluster name (Cluster_name) and a tenant name space (Namespace_name), is added, so that the relevance between the model object and the model resource can be effectively ensured.
S2000, reading blueprint information and state information of the application component, wherein the blueprint information comprises reference relations among model objects; the state information includes model resources associated with the application component.
It is to be appreciated that an application component is composed of a superposition of multiple deployment components and operational characteristics, and thus, the application component is associated with multiple different deployment components, operational characteristics, and model resources. Because the data relevance between the model objects cannot be completely embodied in the mode of matching the model labels in the steps, after blueprint information and state information of the application components are acquired, the application components, the deployment components and the operation and maintenance features can be further related through model resources, and the comprehensiveness and the accuracy of the connection between the model objects are guaranteed.
It is to be appreciated that the blueprint information includes reference relationships between model objects and the state information includes model resources associated with the application components. The blueprint information and the state information of the application component are read, so that the reference relation between model objects and between the model objects and model resources can be conveniently and rapidly acquired accurately, and a user can conveniently and comprehensively grasp the data transmission and digital interaction process between the model objects and the model resources.
It will be appreciated that blueprint information and state information of an application component can be read through an API query interface to obtain reference relationships between model objects, as well as model resources associated with the application component. The API is used as a contract for connecting different components in the software system, and the blueprint information and the state information of the application component can be rapidly and accurately read through the API query interface. In an actual application environment, blueprint information meeting specified conditions can be returned through a calling instruction. For example, using zero or more filter parameters (space-id, space-name, and stored-state) and only one search parameter (name or tag) to represent a condition, only blueprint information within the scope of the user's rights will be returned.
It can be understood that the reading process does not need to access the source code of the open application model, and does not need to understand the details of the internal working mechanism of the open application model, so that the efficiency and the accuracy of reading the blueprint information and the state information of the application component are ensured. As to how the API query interface obtains the blueprint information and the state information of the application component through the program and the protocol, the description thereof is omitted.
S3000, establishing a topological relation between model objects according to the blueprint information and the state information.
It can be understood that, by acquiring the blueprint information of the application component, the deployment component and the operation and maintenance feature and the state information of the application component, the affiliation and the data association between the model objects can be accurately acquired, and the topological relationship between the model objects can be established. Illustratively, the open application model resolves blueprints of application components according to keywords of metadata/name, spec/components and spec/components/tracks by normalizing interface definitions of the application components, and establishes topological relations among the application components, deployment components and operation and maintenance features.
Referring to fig. 3, fig. 3 is a schematic diagram illustrating a specific implementation procedure of another embodiment of the step S3000. As shown in fig. 3, step S3000 includes at least the following steps:
s3100, acquiring keywords in the tag information.
It can be appreciated that, in order to improve the timeliness and accuracy of the topology establishment, keywords in the blueprint information need to be defined according to the operation and maintenance requirements. And by defining and analyzing keywords in the blueprint information, model resources commonly referenced by the model objects can be quickly found out. Illustratively, by looking up keywords such as an application name (app_name), a Resource type (resource_type), a deployment object type (component_type), a deployment object name (component_name), an operation and maintenance feature type (track_type), an operation and maintenance feature name (track_name), etc., a reference relationship between model objects can be determined, and thus, a dependency relationship and a data relevance between an application Component, a deployment Component and operation and maintenance features can be determined.
S3200, analyzing blueprint information and state information according to the keywords to obtain the connection relation between model objects.
It can be appreciated that the blueprint information includes reference relationships between model objects, the state information includes model resources associated with the application components, and the blueprint information and the state information are parsed according to the keywords, so that the reference relationships between the application components and the model resources can be efficiently obtained, and the connection relationships between the application components, the deployment components and the operation and maintenance features can be more comprehensively displayed.
S3300, establishing topological relations of the application components, the deployment components and the operation and maintenance features according to the connection relations.
It can be understood that, after the connection relationship between the model objects is obtained, in order to more intuitively and comprehensively display the correlation between the model objects, each application component, each deployment component and each operation and maintenance feature in the open application model need to be displayed, and the connection relationship between each model resource is marked.
It will be appreciated that the topology can visually describe the arrangement and configuration of the open application model, including interrelationships between various model resources. The topological relation is irrelevant to the specific configuration of the model objects, only the connection relation among the model objects is shown, and the relation among the model objects is shown in a chart mode and the like.
S4000, attributing the model resource to the deployment component and the operation and maintenance feature associated with the application component according to the label information.
It can be understood that after the topological relation among the model objects is obtained, in order to facilitate management of the connection relation between the model objects and the model resources related to the model objects, the model resources need to be attributed to the corresponding deployment components and operation and maintenance features according to the label information so as to improve the comprehensiveness of the topological relation. By way of example, under the condition that output data of the application component deviate, model resources, deployment components and operation and maintenance features corresponding to the application component can be quickly checked through topological relations, so that quick troubleshooting and accurate fault point positioning are realized, and operation and maintenance efficiency is improved.
Referring to fig. 4, fig. 4 is a schematic diagram illustrating a specific implementation procedure of another embodiment of the step S4000. As shown in fig. 4, step S4000 includes at least the following steps:
s4100, obtaining model resources deployed in the open application model in the state information, and generating a resource list.
It will be appreciated that the state information includes model resources associated with the application components, so that by reading the state information, model resources associated with the model objects, i.e., model resources deployed into the open application model, can be quickly and comprehensively obtained. Illustratively, model resources actually deployed into the open application model are obtained by parsing keywords of status/appiiedresources in the application component interface.
It can be understood that, in order to ensure that the model resources deployed in the open application model can be managed more intuitively and completely, the related model resources need to be integrated and arranged in sequence to form a resource list convenient to read, so that when the state information is changed, the resource list can be updated timely and accurately.
S4200, traversing the resource list, obtaining a container cluster and a deployment namespace of the model resource, and obtaining cluster access information.
It will be appreciated that the nature of K8S is a group of server clusters, with specific application objects running on each node of the cluster to manage containers in the node. And a namespace (namespace) is an organization mechanism provided by the K8S for classifying, filtering, and managing any set of model objects in the cluster. Therefore, classification management and filtering treatment can be carried out on the model resources through obtaining the container clusters and the deployment namespaces of the model resources, and the treatment efficiency of the model resources is improved. By way of example, according to cluster: { cluster_name } and nalmespace: { nalmespace_name } information in the resource list, a container cluster and a deployment namespace to which the model resource belongs can be rapidly determined, and cluster access information of the model resource is formed, so that rapid classified management of the model resource is facilitated.
S4300, filtering and processing cluster access information, and attributing model resources to deployment components and operation and maintenance features corresponding to the model resources.
It can be appreciated that, because the cluster access information includes container clusters and deployment namespaces of model resources, model resources of different types of labels can be classified through operations such as screening, filtering and the like, so that the model resources can be accurately attributed to deployment components and operation and maintenance features corresponding to the model resources.
Referring to fig. 5, fig. 5 is a schematic diagram illustrating a specific implementation procedure of another embodiment of the step S4300. As shown in fig. 5, step S4300 includes at least the steps of:
s4310, a type tag of the cluster access information is acquired.
It can be understood that the cluster access information is classified according to the resource types of the model resources, and the type labels are formed, so that the processing efficiency of the cluster access information can be effectively improved. The model resources are classified by the Resource types and the Resource names of the model resources, namely, the type labels of cluster access information are formed by taking the type { resource_kind } and the name { resource_name } as keywords, and the model resources are filtered according to the type labels of the 'resource_type'.
S4320, in the case that the type label of the cluster access information is a workload, the model resource is attributed to the corresponding deployment component.
It is understood that a Workload (Workload) is an application component that runs on K8S, whether the Workload is a single model object or is made up of multiple model objects working together, where the Workload can be run in a container that is running on a set of clusters in K8S. In the case that the type tag of the cluster access information is a workload, the workload is attributed to a specific deployment Component according to "component_name" and "component_type" in the type tag.
S4330, obtaining the container load of the model resource according to the cluster access information.
It is understood that K8S is used to manage containerized applications on multiple hosts in a cloud platform, and K8S is also an open source platform for automated container operations including a range of functions such as container orchestration, resource scheduling, elastic scaling, balanced disaster recovery, deployment management, and service discovery. Wherein the container load is used as the bottom resource in the open application model, and the model resource surrounds and serves the container load. Through the container clusters and the deployment namespaces in the cluster access information, the container loads corresponding to the model resources can be accurately acquired.
S4340, attributing the container load to the workload.
It can be understood that the container load is attributed to the workload, the connection between the model object and the bottom layer resource in the open application model is established, the integrity of the topological relation is further ensured, and the failure reason of the application component can not be rapidly and accurately positioned under the condition that the container load is unavailable is avoided. Therefore, after obtaining the container load of the model resource, the container load is attributed to the workload, and then the topological relation between the container load and the model object is established. Illustratively, the open application model can attribute the container load to the corresponding workload in accordance with the label "component_name".
S4350, when the type label of the cluster access information is the operation and maintenance feature, the model resource is attributed to the corresponding operation and maintenance feature.
It can be understood that, under the condition that the type label of the cluster access information is an operation and maintenance feature, the model resource is attributed to the operation and maintenance feature corresponding to the cluster access information, so that the model resource can be further integrated, the relevance between the model resource and the operation and maintenance feature is enhanced, and the integrity of the topological relation is improved. Illustratively, model resources are attributed under specific operation and maintenance features according to the labels "component_name", "track_type", and "track_name".
Referring to fig. 6, fig. 6 is a schematic structural diagram of an open application model-based topology management apparatus 500 provided in an embodiment of the present application, where the following modules in the open application model-based topology management apparatus 500 are involved in the whole flow of the open application model-based topology management method provided in the embodiment of the present application: an adding module 510, a reading module 520, a creating module 530, and an associating module 540.
The adding module 510 is configured to add a model tag to a model object and a model resource in the open application model to obtain tag information, where the model object includes: an application component, a deployment component, and an operation and maintenance feature;
a reading module 520, configured to read blueprint information and state information of an application component, where the blueprint information includes a reference relationship between model objects; the state information includes model resources associated with the application component;
the establishing module 530 is configured to establish a topological relation between model objects according to the blueprint information and the state information;
and an association module 540, configured to assign the model resource to the deployment component and the operation and maintenance feature associated with the application component according to the tag information.
It should be noted that, because the content of information interaction and execution process between modules of the above apparatus is based on the same concept as the method embodiment of the present application, specific functions and technical effects thereof may be referred to in the method embodiment section, and details are not repeated herein.
It can be appreciated that the topology management device 500 based on the open application model is further connected with a presentation module for performance data collection, log collection and data tracking. The display module can be used for inquiring the performance index in the topological relation in real time, and carrying out relevant filtering and aggregation operations, retrieval of relevant logs and the like. The topology relation established by the topology management device based on the open application model is intuitively reflected through the display module, belongs to the prior art, and is not repeated here.
Fig. 7 shows an electronic device 600 provided by an embodiment of the present application. The electronic device 600 includes, but is not limited to:
a memory 601 for storing a program;
a processor 602 for executing the program stored in the memory 601, and when the processor 602 executes the program stored in the memory 601, the processor 602 is configured to execute the topology management method based on the open application model as described above.
The processor 602 and the memory 601 may be connected by a bus or other means.
The memory 601, as a non-transitory computer readable storage medium, may be used to store non-transitory software programs and non-transitory computer executable programs, such as the open application model-based topology management methods described in any of the embodiments of the present application. The processor 602 implements the topology management method based on the open application model described above by running non-transitory software programs and instructions stored in the memory 601.
The memory 601 may include a storage program area that may store an operating system, at least one application program required for functions, and a storage data area; the storage data area may store topology management methods based on the open application model described above. In addition, the memory 601 may include high-speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid state storage device. In some implementations, the memory 601 may optionally include memory located remotely from the processor 602, the remote memory being connectable to the processor 602 through a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The non-transitory software programs and instructions required to implement the open application model-based topology management method described above are stored in the memory 601, which when executed by the one or more processors 602, perform the open application model-based topology management method provided by any embodiment of the present application.
The embodiment of the application also provides a storage medium, which stores computer executable instructions for executing the topology management method based on the open application model.
In an embodiment, the storage medium stores computer executable instructions that are executed by one or more control processors 602, for example, by one of the processors 602 in the electronic device 600, so that the one or more processors 602 perform the topology management method based on the open application model provided in any embodiment of the present application.
The embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, i.e. may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
Those of ordinary skill in the art will appreciate that all or some of the steps, systems, and methods disclosed above may be implemented as software, firmware, hardware, and suitable combinations thereof. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). The term computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, as known to those skilled in the art. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer. Furthermore, as is well known to those of ordinary skill in the art, communication media typically include computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and may include any information delivery media.
Claims (10)
1. A topology management method based on an open application model, the method comprising:
adding model labels to model objects and model resources in an open application model to obtain label information, wherein the model objects comprise: an application component, a deployment component, and an operation and maintenance feature;
reading blueprint information and state information of the application component, wherein the blueprint information comprises reference relations among the model objects; the state information includes the model resource associated with the application component;
establishing a topological relation between the model objects according to the blueprint information and the state information;
attributing the model resource to the deployment component and the operational feature associated with the application component according to the tag information.
2. The method according to claim 1, wherein adding model labels to model objects and model resources in the open application model to obtain label information comprises:
and adding the model label to the model object and the model resource under the condition that the model object directly encapsulates the model resource.
3. The method according to claim 2, wherein adding model labels to model objects in the open application model to obtain label information further comprises:
in the case where the model object encapsulates the model resource indirectly, the corresponding model tag is added when instantiating the model object.
4. The method of claim 1, wherein establishing a topological relationship between the model objects based on the blueprint information and the state information comprises:
acquiring keywords in the tag information;
analyzing the blueprint information and the state information according to the keywords to obtain a connection relation between the model objects;
and establishing topological relations among the application component, the deployment component and the operation and maintenance features according to the connection relation.
5. A method according to claim 3, wherein said attributing the model resource to the deployment component and the operational dimension feature associated with the application component in accordance with the tag information comprises:
acquiring the model resources deployed in the open application model in the state information, and generating a resource list;
traversing the resource list, and obtaining a container cluster and a deployment name space of the model resource to obtain cluster access information;
and filtering and processing the cluster access information, and attributing the model resource to the deployment component and the operation and maintenance feature corresponding to the model resource.
6. The method of claim 5, wherein the filtering the cluster access information to attribute the model resource to the deployment component and the operation and maintenance feature corresponding thereto comprises:
under the condition that the type label of the cluster access information is a workload, attributing the model resource to the deployment component corresponding to the model resource;
obtaining the container load of the model resource according to the cluster access information;
attributing the container load to the workload.
7. The method of claim 5, wherein the filtering processes the cluster access information to attribute the model resource to the deployment component and the operation and maintenance feature corresponding thereto, further comprising:
and under the condition that the type label of the cluster access information is the operation and maintenance feature, attributing the model resource to the operation and maintenance feature corresponding to the model resource.
8. A topology management apparatus based on an open application model, comprising:
the adding module is used for adding model labels to model objects and model resources in the open application model to obtain label information, wherein the model objects comprise: an application component, a deployment component, and an operation and maintenance feature;
the reading module is used for reading blueprint information and state information of the application component, wherein the blueprint information comprises connection relations among the model objects; the state information includes model resources associated with the application component;
the establishing module is used for establishing a topological relation between the model objects according to the blueprint information and the state information;
and the association module is used for attributing the model resource to the deployment component and the operation and maintenance feature associated with the application component according to the label information.
9. An electronic device, comprising: memory, a processor and a computer program stored on the memory and executable on the processor, which processor, when executing the computer program, implements the open application model based topology management method according to any of claims 1 to 7.
10. A computer readable storage medium, characterized in that a computer program is stored, which, when being executed by a processor, implements the topology management method based on an open application model according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210736846.6A CN117348966A (en) | 2022-06-27 | 2022-06-27 | Topology management method, electronic equipment and storage media based on open application model |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210736846.6A CN117348966A (en) | 2022-06-27 | 2022-06-27 | Topology management method, electronic equipment and storage media based on open application model |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117348966A true CN117348966A (en) | 2024-01-05 |
Family
ID=89361830
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210736846.6A Pending CN117348966A (en) | 2022-06-27 | 2022-06-27 | Topology management method, electronic equipment and storage media based on open application model |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117348966A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN119536791A (en) * | 2024-10-30 | 2025-02-28 | 同济大学 | A rapid packaging method for industrial intelligent models based on open architecture |
-
2022
- 2022-06-27 CN CN202210736846.6A patent/CN117348966A/en active Pending
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN119536791A (en) * | 2024-10-30 | 2025-02-28 | 同济大学 | A rapid packaging method for industrial intelligent models based on open architecture |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9256413B2 (en) | Automatic identification of services | |
| US11303539B2 (en) | Network component placement architecture | |
| US11171835B2 (en) | Automated generation of an information technology asset ontology | |
| US7945613B2 (en) | Method for non-disruptively associating applications and middleware components with information technology infrastructure | |
| CN113037891B (en) | Access method and device for stateful application in edge computing system and electronic equipment | |
| CN106559438A (en) | A kind of program method for uploading and device based on objective network platform | |
| Di Martino et al. | Towards a unified owl ontology of cloud vendors' appliances and services at paas and saas level | |
| US20150286505A1 (en) | Computing system resource provisioning | |
| US12355797B2 (en) | System for collecting computer network entity information employing abstract models | |
| US20130191357A1 (en) | Managing multiple versions of enterprise meta-models using semantic based indexing | |
| KR100910336B1 (en) | A system and method for managing the business process model which mapped the logical process and the physical process model | |
| US20160092604A1 (en) | Method for metamodeling unification | |
| CN120822538A (en) | A multi-agent platform collaboration system, method, device and medium | |
| US11184251B2 (en) | Data center cartography bootstrapping from process table data | |
| CN117348966A (en) | Topology management method, electronic equipment and storage media based on open application model | |
| US20070266139A1 (en) | Methods, systems and computer program products for invariant representation of computer network information technology (it) managed resources | |
| US7937711B2 (en) | Method and apparatus for providing a consolidated namespace to client applications in multi-tenant common information model (CIM) environments | |
| CN111858355B (en) | Test case processing method and device, computer equipment and readable storage medium | |
| CN113535220B (en) | Code packet management method and device | |
| CN118069213A (en) | Template deployment system based on cloud primordia | |
| Leida et al. | Facing big data variety in a model driven approach | |
| TW202123001A (en) | Decoupling method and system for decomposing services | |
| CN115658424B (en) | Monitoring methods, devices, equipment, media and program products based on knowledge graphs | |
| CN118656539A (en) | Information recommendation data processing method, device, electronic device and storage medium | |
| US20210306370A1 (en) | Interface security in business applications |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |