CN110333889B - Method and system for upgrading container service user cluster - Google Patents
Method and system for upgrading container service user cluster Download PDFInfo
- Publication number
- CN110333889B CN110333889B CN201910654171.9A CN201910654171A CN110333889B CN 110333889 B CN110333889 B CN 110333889B CN 201910654171 A CN201910654171 A CN 201910654171A CN 110333889 B CN110333889 B CN 110333889B
- Authority
- CN
- China
- Prior art keywords
- version
- upgrade
- cluster
- installation package
- script
- 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.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- 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)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a method and a system for upgrading a container service user cluster, which belong to container service upgrading, and solve the technical problem of how to realize quick upgrading of user cluster versions and components; the method comprises the following steps: classifying the components in the cluster to obtain a plurality of components; writing a corresponding upgrade script aiming at the upgrade update condition of each component, and uploading a new version image used by the upgrade script to an image warehouse; constructing a version management system, wherein the version management system stores an installation package of each historical version, and stores an influenceable historical version of an upgrade script in the installation package of each version, and the upgrade script in the installation package comprises upgrade scripts of each component; and for the current version of the cluster, invoking an upgrade script affecting the current version in the installation package to upgrade the cluster. The system comprises a component classification module, a script writing module, a version management system configuration module and an upgrade configuration module.
Description
Technical Field
The invention relates to the field of container service upgrading, in particular to a method and a system for upgrading a container service user cluster.
Background
In recent years, with development of cloud computing and cloud services, container technology is widely applied, kubernetes is also becoming more and more important as an advanced container arrangement system, kubernetes version and each component in a cluster are continuously updated, and upgrading of version in the container service becomes an important problem.
Kubernetes is an advanced container arrangement system, and the container service has the cluster management functions of creating and deleting Kubernetes clusters, and for cluster upgrade, the following core concepts are provided:
cluster upgrade: the k8s version upgrade comprises the upgrade of the k8s core component and the upgrade of the dependent component thereof, and the upgrading process should ensure that the pod is available;
cluster installation package: the method consists of an onsible script, comprises a plurality of roles, and can rapidly and simultaneously deploy k8s clusters on a plurality of nodes;
cluster upgrade script: upgrading the cluster into an allowable script with a specified version, wherein the upgrade script is positioned in a cluster installation package.
How to realize the rapid upgrade of the user cluster version and the components is a technical problem to be solved.
Disclosure of Invention
The technical task of the invention is to provide an upgrading method and system of a container service user cluster aiming at the defects, so as to solve the problem of how to realize the rapid upgrading of the user cluster version and components.
In a first aspect, the present invention provides a method for upgrading a customer cluster of a container service, including the steps of:
classifying the components in the cluster to obtain a plurality of components;
writing a corresponding upgrade script aiming at the upgrade update condition of each component, and uploading a new version image used by the upgrade script to an image warehouse;
constructing a version management system, wherein the version management system stores an installation package of each historical version, and stores an influenceable historical version of an upgrade script in the installation package of each version, and the upgrade script in the installation package comprises upgrade scripts of each component;
and for the current version of the cluster, invoking an upgrade script affecting the current version in the installation package to upgrade the cluster.
In the above embodiment, the built version management system stores the installation packages of each historical version, and the upgrade script in the installation package of each version can realize the upgrade of the historical version which can be affected by the installation package, and the historical version which can be affected is understood as follows: for the current version, all low-level versions of the upgrade can be realized through the installation package of the current version; the upgrade script in the installation package includes upgrade scripts for each component. When the current version of the cluster is upgraded, an installation package corresponding to the target version can be selected according to the target version to be upgraded, and a corresponding upgrading script in the installation package is called to upgrade the cluster, so that the cluster and all components in the cluster are upgraded.
Preferably, the components inside the cluster are classified, and the obtained components include:
a Kubelet component comprising a kuberet core component, and a static pod pulled by the Kubelet core component;
an Etcd component to provide storage for a cluster;
a Docker component for providing a container engine for a cluster;
and the Calico component is used for providing a network for the cluster.
Preferably, the upgrade update case for each component is written with a generic upgrade script or one specific to a certain version through an existing.
Preferably, the version management system is constructed, comprising the following steps:
manufacturing an installation package according to the upgrading conditions of all the components, naming the installation package according to naming rules, wherein an upgrading script in the installation package comprises the upgrading script of all the components;
uploading an installation package, recording an installation package version, dividing a directory of the installation package according to the installation package version, and recording and storing the installation package of all historical versions;
the upgrade script in the record installation package can influence the historical version, and is used for facilitating the cluster to find the upgradeable version according to the current version.
Preferably, in the process of calling the upgrade script affecting the current version in the installation package to upgrade the cluster, if a new image is needed, calling the image warehouse to pull the new image.
Preferably, for the current version of the cluster, invoking an upgrade script affecting the current version in the installation package to upgrade the cluster, including the following steps:
acquiring an upgradeable version and displaying upgrade characteristics of the upgradeable version, wherein the upgradeable version is the highest version in all versions affecting the current version;
selecting a target version to be upgraded into a current version, and calling an installation package according to the target version;
invoking an upgrade script affecting the current version in the installation package to upgrade the cluster, and invoking a mirror image warehouse to pull a new mirror image if the new mirror image is needed;
judging whether the upgrade is successful or not according to the upgrade script execution result, and feeding back the execution result.
Preferably, the method further comprises the steps of constructing a cluster upgrading interface, wherein the cluster upgrading interface performs data interaction with the version management system through a cluster upgrading API;
the cluster upgrading interface is interacted with a user, an upgradeable version is obtained through the cluster upgrading interface, a target version is selected, and an execution result is displayed through the cluster upgrading interface.
In a second aspect, the present invention provides an upgrade system for a container service user cluster, comprising:
the component classification module is used for classifying the components in the cluster to obtain a plurality of components;
the script writing module is used for writing a corresponding upgrade script according to upgrade and update conditions of each component and uploading a new version image used by the upgrade script to the image warehouse;
the version management system configuration module is used for constructing a version management system, wherein the constructed version management system stores installation packages of various historical versions, and stores influenceable historical versions of upgrade scripts in the installation packages of each version, and the upgrade scripts in the installation packages comprise upgrade scripts of various components;
and the upgrade configuration module is used for calling an upgrade script affecting the current version in the installation package for cluster upgrade for the current version of the cluster.
Preferably, the version management system configuration module is configured to construct the version management system by:
manufacturing an installation package according to the upgrading conditions of all the components, naming the installation package according to naming rules, wherein an upgrading script in the installation package comprises the upgrading script of all the components;
uploading an installation package, recording an installation package version, dividing a directory of the installation package according to the installation package version, and recording and storing the installation package of all historical versions;
the record installation package upgrade script can influence the historical version for facilitating the cluster to find the upgradeable version according to the current version.
Preferably, the upgrade configuration module upgrades to the current version of the cluster by:
acquiring an upgradeable version and displaying upgrade characteristics of the upgradeable version, wherein the upgradeable version is the highest version in all versions affecting the current version;
selecting a target version to be upgraded into a current version, and calling an installation package according to the target version;
invoking an upgrade script affecting the current version in the installation package to upgrade the cluster, and invoking a mirror image warehouse to pull a new mirror image if the new mirror image is needed;
judging whether the upgrade is successful or not according to the upgrade script execution result, and feeding back the execution result;
the upgrade configuration module is provided with a cluster upgrade interface, and the cluster upgrade interface performs data interaction with the version management system through a cluster upgrade API; the cluster upgrading interface is interacted with a user, an upgradeable version is obtained through the cluster upgrading interface, a target version is selected, and an execution result is displayed through the cluster upgrading interface.
The method and the system for upgrading the container service user cluster have the following advantages: the user cluster upgrading efficiency is effectively improved, the upgradeable components can be timely upgraded, and the cluster version is more convenient to manage.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings that are needed in the description of the embodiments will be briefly described below, it will be apparent that the drawings in the following description are only some embodiments of the present invention, and other drawings can be obtained according to these drawings without inventive effort for a person skilled in the art.
The invention is further described below with reference to the accompanying drawings.
Fig. 1 is a flow chart of a method for upgrading a container service subscriber cluster according to embodiment 1.
Detailed Description
The invention will be further described with reference to the accompanying drawings and specific examples, so that those skilled in the art can better understand the invention and implement it, but the examples are not meant to limit the invention, and the technical features of the embodiments of the invention and the examples can be combined with each other without conflict.
The embodiment of the invention provides a method and a system for upgrading a container service user cluster, which are used for solving the technical problem of how to realize quick upgrading of user cluster versions and components.
Example 1:
the invention relates to a method for upgrading a container service user cluster, which comprises the following steps:
s100, classifying the components in the cluster to obtain a plurality of components;
s200, writing a corresponding upgrade script according to upgrade and update conditions of each component, and uploading a new version image used by the upgrade script to an image warehouse;
s300, constructing a version management system, wherein the version management system stores installation packages of various historical versions, and stores influenceable historical versions of upgrade scripts in the installation packages of each version, and the upgrade scripts in the installation packages comprise upgrade scripts of various components;
s400, for the current version of the cluster, invoking an upgrade script affecting the current version in the installation package to upgrade the cluster.
In step S100, the components inside the cluster are classified, and the obtained multiple components include a Kubelet component, an Etcd component, a Docker component and a Calico component, where the Kubelet component includes a kubernetes core component and a static pod pulled up by the Kubelet core component, the Etcd component is used to provide storage for the cluster, the Docker component is used to provide a container engine for the cluster, and the Calico component is used to provide a network for the cluster.
In step S200, a general upgrade script or an upgrade script specific to a certain version is written through an allowable for each component upgrade update case.
In step S300, a version management system is constructed, comprising the following steps:
s310, manufacturing an installation package according to the upgrading conditions of all the components, naming the installation package according to naming rules, wherein an upgrading script in the installation package comprises the upgrading script of all the components;
s320, uploading the installation package and recording the version of the installation package, dividing the directory of the installation package according to the version of the installation package, and recording and storing the installation package of all historical versions;
s330, recording the update script of the installation package can influence the historical version, and is used for facilitating the cluster to find the upgradeable version according to the current version.
In step S400, in the process of calling the upgrade script affecting the current version in the installation package to upgrade the cluster, if a new image is needed, the image warehouse is called to pull the new image.
Step S400 includes the following sub-steps:
s410, acquiring an upgradeable version and displaying upgrade characteristics of the upgradeable version, wherein the upgradeable version is the highest version in all versions affecting the current version;
s420, selecting a target version to be upgraded into a current version, and calling an installation package according to the target version;
s430, invoking an upgrade script affecting the current version in the installation package, upgrading the cluster, and invoking an image warehouse to pull a new image if the new image is needed;
s440, judging whether the upgrade is successful according to the upgrade script execution result, and feeding back the execution result.
In this embodiment, besides the version upgrade management system, a cluster upgrade interface is also constructed, and the cluster upgrade interface performs data interaction with the version management system through a cluster upgrade API. The cluster upgrading interface is interacted with a user, an upgradeable version is obtained through the cluster upgrading interface, a current version of a cluster is selected, and an upgrading execution result is displayed through the cluster upgrading interface.
The cluster upgrading interface can display the installation packages of all versions, an upgrading button is configured in the cluster upgrading interface, and the versions are selected through the upgrading button so as to call the corresponding installation packages and execute upgrading of the current version.
The upgrading method of the container service user cluster can effectively improve the upgrading efficiency of the user cluster, upgrade the upgradeable component timely, and manage the cluster version more conveniently.
Example 2:
the invention relates to an upgrade system of a container service user cluster, which comprises a component classification module, a script writing module, a version management system configuration module and an upgrade configuration module. The component classification module is used for classifying the components in the cluster to obtain a plurality of components; the script writing module is used for writing a corresponding upgrading script aiming at the upgrading and updating conditions of each component and uploading a new version image used by the upgrading script to the image warehouse; the version management system configuration module is used for constructing a version management system, wherein the constructed version management system stores installation packages of various historical versions, and stores influenceable historical versions of upgrade scripts in the installation packages of each version, and the upgrade scripts in the installation packages comprise upgrade scripts of various components; and the upgrade configuration module is used for calling an upgrade script affecting the current version in the installation package for cluster upgrade for the current version.
In this embodiment, the internal components of the cluster are classified, and the obtained multiple components include a Kubelet component, an Etcd component, a Docker component and a Calico component, where the Kubelet component includes a kubernetes core component and a static pod pulled up by the Kubelet core component, the Etcd component is used to provide storage for the cluster, the Docker component is used to provide a container engine for the cluster, and the Calico component is used to provide a network for the cluster.
The script writing module writes a general upgrade script or a special upgrade script for a certain version through an allowable for upgrade update conditions of each component.
The version management system configuration module is used for constructing a version management system through the following steps:
(1) Manufacturing an installation package according to the upgrading conditions of all the components, naming the installation package according to naming rules, wherein an upgrading script in the installation package comprises the upgrading script of all the components;
(2) Uploading the installation package and recording the version of the installation package, dividing the directory of the installation package according to the version of the installation package, and recording and storing the installation package of all historical versions;
(3) The record installation package upgrade script can influence the historical version, and is used for facilitating the cluster to find the upgradeable version according to the current version.
The upgrade script in the installation package of each version can realize the upgrade of the influential historical version, and the influential historical version is understood as follows: for the current version, all lower-level versions of the upgrade may be implemented by the installation package of the current version.
The upgrade configuration module also has the following functions: and if the new mirror image is needed in the upgrading process, calling a mirror image warehouse to pull the new mirror image.
In this embodiment, the upgrade configuration module upgrades the current version of the cluster by:
(1) Acquiring an upgradeable version and displaying upgrade characteristics of the upgradeable version, wherein the upgradeable version is the highest version in all versions affecting the current version;
(2) Selecting a target version to be upgraded into a current version, and calling an installation package according to the target version;
(3) Calling an upgrade script affecting the current version in the installation package to upgrade the cluster, and calling a mirror image warehouse to pull a new mirror image if the new mirror image is needed;
(4) Judging whether the upgrade is successful or not according to the upgrade script execution result, and feeding back the execution result.
The upgrade configuration module is provided with a cluster upgrade interface, and the cluster upgrade interface performs data interaction with the version management system through a cluster upgrade API; the cluster upgrading interface is interacted with a user, an upgradeable version is obtained through the cluster upgrading interface, a target version is selected, and an execution result is displayed through the cluster upgrading interface.
The upgrade system of the container service user cluster of the present invention may execute the upgrade method of the container service user cluster disclosed in embodiment 1.
The above-described embodiments are merely preferred embodiments for fully explaining the present invention, and the scope of the present invention is not limited thereto. Equivalent substitutions and modifications will occur to those skilled in the art based on the present invention, and are intended to be within the scope of the present invention. The protection scope of the invention is subject to the claims.
Claims (3)
1. The method for upgrading the container service user cluster is characterized by comprising the following steps:
classifying the components in the cluster to obtain a plurality of components;
aiming at the upgrade update condition of each component, writing a general upgrade script or a special upgrade script for a certain version through an allowable, and uploading a new version image used by the upgrade script to an image warehouse;
constructing a version management system, wherein the version management system stores an installation package of each historical version, and stores an influenceable historical version of an upgrade script in the installation package of each version, and the upgrade script in the installation package comprises upgrade scripts of each component;
for the current version of the cluster, calling an upgrade script affecting the current version in the installation package to upgrade the cluster, and calling a mirror image warehouse to pull a new mirror image if the new mirror image is needed;
the method also comprises the following steps: constructing a cluster upgrading interface, wherein the cluster upgrading interface performs data interaction with a version management system through a cluster upgrading API; the cluster upgrading interface is interacted with a user, an upgradeable version is obtained through the cluster upgrading interface, a target version is selected, and an execution result is displayed through the cluster upgrading interface;
the version management system is constructed, which comprises the following steps:
manufacturing an installation package according to the upgrading conditions of all the components, naming the installation package according to naming rules, wherein an upgrading script in the installation package comprises the upgrading script of all the components;
uploading an installation package, recording an installation package version, dividing a directory of the installation package according to the installation package version, and recording and storing the installation package of all historical versions;
recording an upgrade script in the installation package, which can influence the historical version, for facilitating the cluster to find an upgradeable version according to the current version;
for the current version of the cluster, invoking an upgrade script affecting the current version in the installation package to upgrade the cluster, and comprising the following steps:
acquiring an upgradeable version and displaying upgrade characteristics of the upgradeable version, wherein the upgradeable version is the highest version in all versions affecting the current version;
selecting a target version to be upgraded into a current version, and calling an installation package according to the target version;
invoking an upgrade script affecting the current version in the installation package to upgrade the cluster, and invoking a mirror image warehouse to pull a new mirror image if the new mirror image is needed;
judging whether the upgrade is successful or not according to the upgrade script execution result, and feeding back the execution result.
2. The method for upgrading a customer cluster for container service according to claim 1, wherein the classifying the components in the cluster to obtain a plurality of components comprises:
a Kubelet component comprising a kubernetes core component, and a static pod pulled by the Kubelet component;
an Etcd component to provide storage for a cluster;
a Docker component for providing a container engine for a cluster;
and the Calico component is used for providing a network for the cluster.
3. An upgrade system for a container service user cluster, comprising:
the component classification module is used for classifying the components in the cluster to obtain a plurality of components;
the script writing module is used for writing a corresponding upgrade script according to upgrade and update conditions of each component and uploading a new version image used by the upgrade script to the image warehouse;
the version management system configuration module is used for constructing a version management system, wherein the constructed version management system stores installation packages of various historical versions, and stores influenceable historical versions of upgrade scripts in the installation packages of each version, and the upgrade scripts in the installation packages comprise upgrade scripts of various components;
the upgrading configuration module is used for calling an upgrading script affecting the current version in the installation package for cluster upgrading for the current version of clusters;
the version management system configuration module is used for constructing a version management system through the following steps:
manufacturing an installation package according to the upgrading conditions of all the components, naming the installation package according to naming rules, wherein an upgrading script in the installation package comprises the upgrading script of all the components;
uploading an installation package, recording an installation package version, dividing a directory of the installation package according to the installation package version, and recording and storing the installation package of all historical versions;
recording the update script of the installation package can influence the historical version, and is used for facilitating the cluster to find the upgradeable version according to the current version;
the upgrade configuration module upgrades the current version of the cluster by:
acquiring an upgradeable version and displaying upgrade characteristics of the upgradeable version, wherein the upgradeable version is the highest version in all versions affecting the current version;
selecting a target version to be upgraded into a current version, and calling an installation package according to the target version;
invoking an upgrade script affecting the current version in the installation package to upgrade the cluster, and invoking a mirror image warehouse to pull a new mirror image if the new mirror image is needed;
judging whether the upgrade is successful or not according to the upgrade script execution result, and feeding back the execution result;
the upgrade configuration module is provided with a cluster upgrade interface, and the cluster upgrade interface performs data interaction with the version management system through a cluster upgrade API; the cluster upgrading interface is interacted with a user, an upgradeable version is obtained through the cluster upgrading interface, a target version is selected, and an execution result is displayed through the cluster upgrading interface.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910654171.9A CN110333889B (en) | 2019-07-19 | 2019-07-19 | Method and system for upgrading container service user cluster |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910654171.9A CN110333889B (en) | 2019-07-19 | 2019-07-19 | Method and system for upgrading container service user cluster |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110333889A CN110333889A (en) | 2019-10-15 |
| CN110333889B true CN110333889B (en) | 2023-09-15 |
Family
ID=68145940
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910654171.9A Active CN110333889B (en) | 2019-07-19 | 2019-07-19 | Method and system for upgrading container service user cluster |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110333889B (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110806881B (en) * | 2019-11-05 | 2023-07-04 | 浪潮云信息技术股份公司 | Method for deploying different CPU architectures by kubernetes |
| CN111752581A (en) * | 2020-05-22 | 2020-10-09 | 中国邮政储蓄银行股份有限公司 | Distributed system upgrading method and device and computer system |
| CN111708608B (en) * | 2020-06-19 | 2023-04-25 | 浪潮云信息技术股份公司 | Container large cluster rapid deployment method and system based on stable |
| CN112306626B (en) * | 2020-09-01 | 2024-04-05 | 北京京东尚科信息技术有限公司 | Method and device for updating cloud platform |
| CN112379903B (en) * | 2020-11-09 | 2023-04-18 | 杭州安恒信息技术股份有限公司 | Version updating method, device, system, electronic device and storage medium |
| CN112860282B (en) * | 2021-03-31 | 2024-02-09 | 中国工商银行股份有限公司 | Cluster plug-in upgrading method, device and server |
| US11816469B2 (en) * | 2021-09-22 | 2023-11-14 | International Business Machines Corporation | Resolving the version mismatch problem when implementing a rolling update in an open-source platform for container orchestration |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105867955A (en) * | 2015-09-18 | 2016-08-17 | 乐视云计算有限公司 | Deployment system and deployment method of application program |
| CN106888254B (en) * | 2017-01-20 | 2020-08-18 | 华南理工大学 | Kubernetes-based container cloud architecture and interaction method among modules thereof |
| CN106850621A (en) * | 2017-02-07 | 2017-06-13 | 南京云创大数据科技股份有限公司 | A kind of method based on container cloud fast construction Hadoop clusters |
| CN106933600A (en) * | 2017-03-28 | 2017-07-07 | 联想(北京)有限公司 | A kind of method for upgrading system and device |
| CN109445825A (en) * | 2018-11-09 | 2019-03-08 | 郑州云海信息技术有限公司 | The method and apparatus that a kind of server cluster system updates upgrading |
-
2019
- 2019-07-19 CN CN201910654171.9A patent/CN110333889B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN110333889A (en) | 2019-10-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110333889B (en) | Method and system for upgrading container service user cluster | |
| CN109697153A (en) | Monitoring method, monitoring system and computer readable storage medium | |
| US20050135338A1 (en) | Method for creating and deploying system changes in a voice application system | |
| US10304222B2 (en) | System and method for graphically displaying recommended mappings in an integration cloud service design time | |
| US8627284B2 (en) | Managed system extensibility | |
| CN101552976B (en) | Multi-service form file processing system and method | |
| CN104679532B (en) | kernel module loading method and device | |
| US9654343B2 (en) | System and method for managing service characteristics | |
| CN112165507B (en) | Method, device, equipment and medium for supporting multi-service architecture by single Web project | |
| CN110780897A (en) | Code changing method and device | |
| CN103946794A (en) | Cross-reference and priority claim to related applications | |
| US7739660B2 (en) | Code management in a distributed software development environment | |
| CN111008047A (en) | Page element conflict processing method and device and electronic equipment | |
| CN111158743B (en) | Big data operation and maintenance management platform | |
| US7187380B2 (en) | Telecommunications graphical service program | |
| CN109032685A (en) | A kind of method and terminal accelerating Android system starting | |
| CN107977243A (en) | A kind of third party's interface call method and device | |
| CN116048609A (en) | Configuration file updating method, device, computer equipment and storage medium | |
| CN113568603B (en) | Component object creating and interface method calling method, terminal and storage device | |
| CN109840078A (en) | A kind of method and device of collaborative editing Layered-Metadata | |
| CN110221952B (en) | Service data processing method and device and service data processing system | |
| CN114880073A (en) | Cloud application engine deployment method, device, equipment and storage medium for shielding Web framework for user | |
| US6523074B1 (en) | Apparatus and method to manage the invocation of feature service | |
| CN112862399A (en) | Method, device and equipment for changing material list table and storage medium | |
| CN110876067B (en) | Interface element display method, device, equipment and storage medium |
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 | ||
| CB02 | Change of applicant information |
Address after: 250100 No. 1036 Tidal Road, Jinan High-tech Zone, Shandong Province, S01 Building, Tidal Science Park Applicant after: Inspur cloud Information Technology Co.,Ltd. Address before: 250100 No. 1036 Tidal Road, Jinan High-tech Zone, Shandong Province, S01 Building, Tidal Science Park Applicant before: Tidal Cloud Information Technology Co.,Ltd. |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |