CN111638939A - Management system and method for application life cycle of Kubernetes container platform - Google Patents
Management system and method for application life cycle of Kubernetes container platform Download PDFInfo
- Publication number
- CN111638939A CN111638939A CN202010404131.1A CN202010404131A CN111638939A CN 111638939 A CN111638939 A CN 111638939A CN 202010404131 A CN202010404131 A CN 202010404131A CN 111638939 A CN111638939 A CN 111638939A
- Authority
- CN
- China
- Prior art keywords
- application
- resource
- sub
- request
- data
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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; CALCULATING OR 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/45575—Starting, stopping, suspending or resuming virtual machine instances
Abstract
The invention discloses a management system for an application life cycle of a Kubernetes container platform facing a Shenwei platform, which comprises an application management component, an application API gateway module and a Kubernetes cluster agent module, wherein the application management component is a component which is deployed on a physical or virtual host and is used for realizing application life cycle management, the application API gateway module and the application management component are deployed in the same intranet to provide a gateway function of an application API, and the Kubernetes cluster agent module is a component which is deployed in the same intranet with the application management component to provide a function of multiple Kubernetes cluster agents. The invention simplifies the flow of application life cycle management, greatly improves the application life cycle management efficiency and has good practicability.
Description
Technical Field
The invention relates to a management system and a management method for a Kubernetes container platform application life cycle, belonging to the field of management of application life cycles.
Background
With the development of containerization technology and its large-scale application, the container platform kubernets is also increasingly used in production environments for programming container applications. Application is a Kubernetes CRD resource that defines metadata information for an Application, as well as Group and kidd information for each Kubernetes resource that the Application contains. When the application is created based on the CRD, the resource objects contained in the application are respectively created, and then the application resource objects are created according to the created resource metadata. Although the Application provides one package of the Application and the related resources thereof, the Application data does not contain all data information of the resources, and when the resource creation and resource update are involved, a user needs to manually associate the resources with the Application and create or update the resources one by one to complete the lifecycle management of the Application.
Disclosure of Invention
The management system and the method for the application life cycle of the Kubernets container platform simplify the flow of application life cycle management, greatly improve the application life cycle management efficiency and have good practicability.
In order to achieve the purpose, the invention adopts the technical scheme that: there is provided a management system for a kubernets container platform application lifecycle, comprising: the system comprises an application API gateway module, an application management component and a Kubernetes cluster agent module;
the application API gateway module is used for exposing an application life cycle management interface of the application management component, providing the capability of a user to access the application management interface through the REST API, and performing authentication, safety, log and flow control on the API;
the application management component is used for realizing management of an application life cycle, and specifically comprises:
receiving an application creation or update request, and checking the validity of the application creation or update request load;
grouping and classifying the applied sub-resource data to obtain resource groups and categories contained in the sub-resource data, removing repeated categories to obtain non-repeated resource groups and categories of sub-resource data, and updating the non-repeated resource groups and categories to spec.componentKinds fields in Application object data;
temporarily storing the applied sub-resource data into a request context, setting a spec.
Submitting a request for creating or updating the Application resource to a Kubernets system according to the assembled Application object, namely the sub-resource data, the resource grouping and the category information of the Application;
receiving a successful response of the Kubernetes system or returning an error response to the user;
acquiring the temporarily stored sub-resource data of the application from the request context, and sequentially performing data cleaning operation, data injection operation, owner association and application creation or updating operation on each sub-resource;
for the application creation request, submitting the creation request of each resource data to a Kubernetes system, and storing the sub-resource data in the Kubernetes system;
for the application update request, performing a difference calculation operation of the child resource;
returning the content to the client Application object as the content of the response;
and the Kubernetes cluster agent module is used for realizing the multi-cluster agent access function.
The invention also provides a management method of the management system based on the application life cycle of the Kubernets container platform, which is oriented to the Shenwei platform and comprises the following steps:
step 1: assembling an Application creation or update request, wherein the load of the creation or update request comprises Application resource data, and the spec.componenttemplates field of the resource data comprises sub-resource data of an Application, wherein the sub-resource data of the Application refers to resource data subordinate to the Application;
step 2: submitting an application creation or update request to an application management component, receiving the creation or update request by the application management component, checking the legality of the load of the application creation or update request, if the request is legal, executing a step 3, if the request is illegal, returning an error response, and terminating the step;
and step 3: the Application management component carries out grouping classification on the sub-resource data of the Application to obtain resource groups and categories contained in the sub-resource data, removes repeated categories to obtain non-repeated resource groups and categories of the sub-resource data, and updates the non-repeated resource groups and categories to spec.
And 4, step 4: the application management component temporarily stores the sub-resource data of the application obtained after the processing of the step 3 into the request context, sets the spec.
And 5: the Application management component submits an Application resource creating or updating request to a Kubernets system according to the Application object assembled in the previous step, wherein the Application object comprises the sub-resource data, the resource grouping and the category information of the Application;
step 6: the application management component continues the next step when receiving the successful response of the Kubernetes system, and otherwise, returns an error response to the user;
and 7: the application management component acquires the sub-resource data of the application temporarily stored in the step 4 from the request context, and for each sub-resource, the application management component executes data cleaning operation, wherein the data cleaning operation refers to the removal of data automatically generated by the Kubernetes and the application management component in the sub-resource data, so that errors in creating or updating the resource data are avoided;
and 8: for each sub-resource, after performing a data washing operation, the application management component performs a data injection operation, where the data injection operation refers to injecting a selector label of an application into a metadata.
And step 9: after the data injection operation is completed, the Application management component executes owner association, and sets an ownerReference to the Application object for each sub-resource object, so that after the Application object is deleted, the sub-resources to which the Application management component belongs can be automatically subjected to garbage collection by a Kubernetes system;
step 10: after the owner association is completed, the preparation of the sub-resource data of the application is finished, and the application management component starts to execute the application creation or update operation:
for the application creation request, the application management component concurrently submits the creation request of each resource data to the Kubernets system, and stores the sub-resource data in the Kubernets system;
for the application updating request, the application management component executes the difference calculation operation of the sub-resources, wherein the difference calculation operation refers to the comparison of the sub-resource data of the existing application in the current Kubernets system and the resource data in the application updating request to obtain 3 resource data sets to be created, updated and deleted;
for the resources to be created, concurrently submitting a resource creating request to a Kubernets system, for the resources to be updated, concurrently submitting a resource updating request to the Kubernets system, and for the resources to be deleted, concurrently submitting a resource deleting request to the Kubernets system;
step 11: if all the resource requests submitted to the Kubernets system in the step 10 are successful, the spec.assembyphase field of the Application object is updated to be set as Success;
if the resource request submitted to the Kubernets system in the step 10 has failure, updating spec.assembelyphase field of the Application object to Failed;
step 12: the Application management component submits the update request of the modified Application object to a Kubernetes system;
step 13: the Application management component returns the client Application object as the content of the response.
Due to the application of the technical scheme, compared with the prior art, the invention has the following advantages:
the invention relates to a management method and a management system for an Application life cycle of a Kubernetes container platform facing a Shenwei platform, which are characterized in that an Application resource field is added in an Application CRD, an Application management component is added between a client and the Kubernetes system, an Application life cycle management function is packaged in the Application resource field, and an interface for Application life cycle management is exposed to the client, so that the problem that the Application life cycle management efficiency is low due to the fact that the original Application life cycle management is complex and the life cycle management needs to be carried out independently on resources under each Application is solved, the problem that the efficiency is low and the steps are complicated due to the fact that the life cycle management is carried out based on the Application CRD is solved, the flow of the Application life cycle management is simplified, the Application life cycle management efficiency is greatly improved, and the management method and the.
Drawings
FIG. 1 is a schematic flow diagram of the present invention;
FIG. 2 is a sequence diagram of the application management component system interaction of the present invention;
fig. 3 is a system configuration diagram of the present invention.
Detailed Description
Example (b): the invention provides a management system of a Kubernetes container platform application life cycle, as shown in figure 3, the Kubernetes system comprises a plurality of server nodes and a main node for controlling the management nodes, the management system of the application life cycle comprises an application management component, an application API gateway module and a Kubernetes cluster agent module, the application management component is deployed on a physical or virtual host and is used for realizing application life cycle management, the application API gateway module and the application management component are deployed in the same intranet and provide gateway functions of application APIs, the Kubernetes cluster agent module and the application management component are deployed in the same intranet and provide functions of multiple Kubernetes cluster agents;
an application life cycle management interface provided by the application management component is exposed through the application API gateway module, authentication, safety, log and flow control functions are provided for the application management interface, and the safety, service performance and availability of the application management component are ensured;
the management of the application life cycle is realized through the application management component, and the management specifically comprises the following steps:
receiving an application creation or update request, and checking the validity of the application creation or update request load;
grouping and classifying the applied sub-resource data to obtain resource groups and categories contained in the sub-resource data, removing repeated categories to obtain non-repeated resource groups and categories of sub-resource data, and updating the non-repeated resource groups and categories to spec.componentKinds fields in Application object data;
temporarily storing the applied sub-resource data into a request context, setting a spec.
Submitting a request for creating or updating the Application resource to a Kubernets system according to the assembled Application object, namely the sub-resource data, the resource grouping and the category information of the Application;
receiving a successful response of the Kubernetes system or returning an error response to the user;
acquiring the temporarily stored sub-resource data of the application from the request context, and sequentially performing data cleaning operation, data injection operation, owner association and application creation or updating operation on each sub-resource;
for the application creation request, submitting the creation request of each resource data to a Kubernetes system, and storing the sub-resource data in the Kubernetes system;
for the application update request, performing a difference calculation operation of the child resource;
returning the content to the client Application object as the content of the response;
the kubernets multi-cluster management module allows application lifecycle management by directly accessing various kubernets clusters through the application management component without concern for authentication and address configuration information of the different clusters.
The invention provides a management method of a Kubernetes container platform application life cycle, as shown in figure 1, comprising the following steps:
step 1: assembling an Application creation or update request, wherein the load of the creation or update request comprises Application resource data, and the spec.componenttemplates field of the resource data comprises sub-resource data of an Application, wherein the sub-resource data of the Application refers to resource data subordinate to the Application;
step 2: submitting an application creation or update request to an application management component, receiving the creation or update request by the application management component, checking the legality of the load of the application creation or update request, if the request is legal, executing a step 3, if the request is illegal, returning an error response, and terminating the step;
and step 3: the Application management component carries out grouping classification on the sub-resource data of the Application to obtain resource groups and categories contained in the sub-resource data, removes repeated categories to obtain non-repeated resource groups and categories of the sub-resource data, and updates the non-repeated resource groups and categories to spec.
And 4, step 4: the application management component temporarily stores the sub-resource data of the application obtained after the processing of the step 3 into the request context, sets the spec.
And 5: the Application management component submits an Application resource creating or updating request to a Kubernets system according to the Application object assembled in the previous step, wherein the Application object comprises the sub-resource data, the resource grouping and the category information of the Application;
step 6: the application management component continues the next step when receiving the successful response of the Kubernetes system, and otherwise, returns an error response to the user;
and 7: the application management component acquires the sub-resource data of the application temporarily stored in the step 4 from the request context, and for each sub-resource, the application management component executes data cleaning operation, wherein the data cleaning operation refers to the removal of data automatically generated by the Kubernetes and the application management component in the sub-resource data, so that errors in creating or updating the resource data are avoided;
and 8: for each child resource, after performing the data cleansing operation, the application management component performs a data injection operation, which refers to injecting a selector label of an application into the metadata.labels field of each resource object, enabling the application to be associated with the label of the child resource, and for the injection of the selector label, particularly for the Deployment, stateful set, and DaemonSet resource types, the spec.selector.matchedlabels and spec.template.labels fields injected into the resource object are also needed;
and step 9: after the data injection operation is completed, the Application management component executes owner association, and sets an ownerReference to the Application object for each sub-resource object, so that after the Application object is deleted, the sub-resources to which the Application management component belongs can be automatically subjected to garbage collection by a Kubernetes system;
step 10: after the owner association is completed, the preparation of the sub-resource data of the application is finished, and the application management component starts to execute the application creation or update operation:
for the application creation request, the application management component concurrently submits the creation request of each resource data to the Kubernets system, and stores the sub-resource data in the Kubernets system;
for the application updating request, the application management component executes the difference calculation operation of the sub-resources, wherein the difference calculation operation refers to the comparison of the sub-resource data of the existing application in the current Kubernets system and the resource data in the application updating request to obtain 3 resource data sets to be created, updated and deleted;
for the resources to be created, concurrently submitting a resource creating request to a Kubernets system, for the resources to be updated, concurrently submitting a resource updating request to the Kubernets system, and for the resources to be deleted, concurrently submitting a resource deleting request to the Kubernets system;
step 11: if all the resource requests submitted to the Kubernets system in the step 10 are successful, the spec.assembyphase field of the Application object is updated to be set as Success;
if the resource request submitted to the Kubernets system in the step 10 has failure, updating spec.assembelyphase field of the Application object to Failed;
step 12: the Application management component submits the update request of the modified Application object to a Kubernetes system;
step 13: the Application management component returns the client Application object as the content of the response.
When the Application lifecycle management method and system for the Kubernetes container platform facing the Shenwei platform are adopted, the Application resource field is added in the Application CRD, the Application management component is added between the client and the Kubernetes system, the Application lifecycle management function is packaged in the Application resource field, and an interface for Application lifecycle management is exposed to the client, so that the problem that the Application lifecycle management efficiency is low due to the fact that the original Application lifecycle management is complex and the lifecycle management needs to be independently carried out on resources under each Application is solved, the problem that the Application lifecycle management efficiency is low due to the fact that the lifecycle management is carried out based on the Application CRD is solved, the steps are complex, the flow of the Application lifecycle management is simplified, the Application lifecycle management efficiency is greatly improved, and the Application lifecycle management method and system have good practicability.
The above embodiments are merely illustrative of the technical ideas and features of the present invention, and the purpose thereof is to enable those skilled in the art to understand the contents of the present invention and implement the present invention, and not to limit the protection scope of the present invention. All equivalent changes and modifications made according to the spirit of the present invention should be covered within the protection scope of the present invention.
Claims (2)
1. A management system for a kubernets container platform application lifecycle, comprising: the system comprises an application API gateway module, an application management component and a Kubernetes cluster agent module;
the application API gateway module is used for exposing an application life cycle management interface of the application management component, providing the capability of a user to access the application management interface through the REST API, and performing authentication, safety, log and flow control on the API;
the application management component is used for realizing management of an application life cycle, and specifically comprises:
receiving an application creation or update request, and checking the validity of the application creation or update request load;
grouping and classifying the applied sub-resource data to obtain resource groups and categories contained in the sub-resource data, removing repeated categories to obtain non-repeated resource groups and categories of sub-resource data, and updating the non-repeated resource groups and categories to spec.componentKinds fields in Application object data;
temporarily storing the applied sub-resource data into a request context, setting a spec.
Submitting a request for creating or updating the Application resource to a Kubernets system according to the assembled Application object, namely the sub-resource data, the resource grouping and the category information of the Application;
receiving a successful response of the Kubernetes system or returning an error response to the user;
acquiring the temporarily stored sub-resource data of the application from the request context, and sequentially performing data cleaning operation, data injection operation, owner association and application creation or updating operation on each sub-resource;
for the application creation request, submitting the creation request of each resource data to a Kubernetes system, and storing the sub-resource data in the Kubernetes system;
for the application update request, performing a difference calculation operation of the child resource;
returning the content to the client Application object as the content of the response;
and the Kubernetes cluster agent module is used for realizing the multi-cluster agent access function.
2. A management method of a management system based on the application life cycle of the Kubernetes container platform is characterized in that the management method facing to the Shenwei platform comprises the following steps:
step 1: assembling an Application creation or update request, wherein the load of the creation or update request comprises Application resource data, and the spec.componenttemplates field of the resource data comprises sub-resource data of an Application, wherein the sub-resource data of the Application refers to resource data subordinate to the Application;
step 2: submitting an application creation or update request to an application management component, receiving the creation or update request by the application management component, checking the legality of the load of the application creation or update request, if the request is legal, executing a step 3, if the request is illegal, returning an error response, and terminating the step;
and step 3: the Application management component carries out grouping classification on the sub-resource data of the Application to obtain resource groups and categories contained in the sub-resource data, removes repeated categories to obtain non-repeated resource groups and categories of the sub-resource data, and updates the non-repeated resource groups and categories to spec.
And 4, step 4: the application management component temporarily stores the sub-resource data of the application obtained after the processing of the step 3 into the request context, sets the spec.
And 5: the Application management component submits an Application resource creating or updating request to a Kubernets system according to the Application object assembled in the previous step, wherein the Application object comprises the sub-resource data, the resource grouping and the category information of the Application;
step 6: the application management component continues the next step when receiving the successful response of the Kubernetes system, and otherwise, returns an error response to the user;
and 7: the application management component acquires the sub-resource data of the application temporarily stored in the step 4 from the request context, and for each sub-resource, the application management component executes data cleaning operation, wherein the data cleaning operation refers to the removal of data automatically generated by the Kubernetes and the application management component in the sub-resource data, so that errors in creating or updating the resource data are avoided;
and 8: for each sub-resource, after performing a data washing operation, the application management component performs a data injection operation, where the data injection operation refers to injecting a selector label of an application into a metadata.
And step 9: after the data injection operation is completed, the Application management component executes owner association, and sets an ownerReference to the Application object for each sub-resource object, so that after the Application object is deleted, the sub-resources to which the Application management component belongs can be automatically subjected to garbage collection by a Kubernetes system;
step 10: after the owner association is completed, the preparation of the sub-resource data of the application is finished, and the application management component starts to execute the application creation or update operation:
for the application creation request, the application management component concurrently submits the creation request of each resource data to the Kubernets system, and stores the sub-resource data in the Kubernets system;
for the application updating request, the application management component executes the difference calculation operation of the sub-resources, wherein the difference calculation operation refers to the comparison of the sub-resource data of the existing application in the current Kubernets system and the resource data in the application updating request to obtain 3 resource data sets to be created, updated and deleted;
for the resources to be created, concurrently submitting a resource creating request to a Kubernets system, for the resources to be updated, concurrently submitting a resource updating request to the Kubernets system, and for the resources to be deleted, concurrently submitting a resource deleting request to the Kubernets system;
step 11: if all the resource requests submitted to the Kubernets system in the step 10 are successful, the spec.assembyphase field of the Application object is updated to be set as Success;
if the resource request submitted to the Kubernets system in the step 10 has failure, updating spec.assembelyphase field of the Application object to Failed;
step 12: the Application management component submits the update request of the modified Application object to a Kubernetes system;
step 13: the Application management component returns the client Application object as the content of the response.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010404131.1A CN111638939B (en) | 2020-05-13 | 2020-05-13 | Management system and method for Kubernets container platform application life cycle |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010404131.1A CN111638939B (en) | 2020-05-13 | 2020-05-13 | Management system and method for Kubernets container platform application life cycle |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111638939A true CN111638939A (en) | 2020-09-08 |
| CN111638939B CN111638939B (en) | 2022-11-15 |
Family
ID=72332747
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010404131.1A Active CN111638939B (en) | 2020-05-13 | 2020-05-13 | Management system and method for Kubernets container platform application life cycle |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111638939B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112269640A (en) * | 2020-11-02 | 2021-01-26 | 浪潮云信息技术股份公司 | Method for realizing life cycle management of container cloud component |
| CN113760448A (en) * | 2021-04-30 | 2021-12-07 | 中科天玑数据科技股份有限公司 | Big data management platform based on kubernets |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109962940A (en) * | 2017-12-14 | 2019-07-02 | 北京云基数技术有限公司 | A kind of virtualization example scheduling system and dispatching method based on cloud platform |
| US20190281112A1 (en) * | 2018-03-08 | 2019-09-12 | Nutanix, Inc. | System and method for orchestrating cloud platform operations |
-
2020
- 2020-05-13 CN CN202010404131.1A patent/CN111638939B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109962940A (en) * | 2017-12-14 | 2019-07-02 | 北京云基数技术有限公司 | A kind of virtualization example scheduling system and dispatching method based on cloud platform |
| US20190281112A1 (en) * | 2018-03-08 | 2019-09-12 | Nutanix, Inc. | System and method for orchestrating cloud platform operations |
Non-Patent Citations (2)
| Title |
|---|
| MERLIJN SEBRECHTS 等: "《Beyond Generic Lifecycles: Reusable Modeling of Custom-Fit Management Workflows for Cloud Applications》", 《2018 IEEE 11TH INTERNATIONAL CONFERENCE ON CLOUD COMPUTING (CLOUD)》 * |
| 翁湦元 等: "《基于Kubernetes的容器云平台设计与实践》", 《计算机应用》 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112269640A (en) * | 2020-11-02 | 2021-01-26 | 浪潮云信息技术股份公司 | Method for realizing life cycle management of container cloud component |
| CN113760448A (en) * | 2021-04-30 | 2021-12-07 | 中科天玑数据科技股份有限公司 | Big data management platform based on kubernets |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111638939B (en) | 2022-11-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9703890B2 (en) | Method and system that determine whether or not two graph-like representations of two systems describe equivalent systems | |
| CN110532074B (en) | Task scheduling method and system for multi-tenant mode SaaS service cluster environment | |
| CN111324610A (en) | Data synchronization method and device | |
| CN111638939B (en) | Management system and method for Kubernets container platform application life cycle | |
| CN109325016A (en) | Data migration method, device, medium and electronic equipment | |
| US11321394B2 (en) | Graph processing system | |
| CN111752945B (en) | Time sequence database data interaction method and system based on container and hierarchical model | |
| CN109561165A (en) | Domain name system configuration method and relevant apparatus | |
| US20200371902A1 (en) | Systems and methods for software regression detection | |
| CN109753302B (en) | Service method without service function based on hybrid cloud computing platform | |
| CN101968747B (en) | Cluster application management system and application management method thereof | |
| CN110096543B (en) | Data operation method, device, server and medium of application program | |
| CN111813836A (en) | Method for improving Ethereum block chain system expansibility | |
| CN113612818B (en) | Industrial app release system of low-code platform | |
| CN115878860A (en) | Menu generation method, device, server equipment and medium | |
| CN115686497A (en) | Business development data management method, development engine, electronic device, and storage medium | |
| CN114547206A (en) | Data synchronization method and data synchronization system | |
| CN114866416A (en) | Multi-cluster unified management system and deployment method | |
| CN112083914A (en) | Method and system for realizing soft bus of object model embedded operating system | |
| CN110377298B (en) | Distributed cluster upgrading method and distributed cluster | |
| US7849164B2 (en) | Configuring a device in a network via steps | |
| WO2003003244A1 (en) | Method of rapidly eliminating different information in databases | |
| CN110309365A (en) | A kind of openstack data query method and apparatus realized based on Mybatis | |
| TWI765447B (en) | Decoupling method and system for decomposing services | |
| CN114866609B (en) | Data interconnection and intercommunication method and device based on unified information model |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |