CN111008023A - Instance deployment method and system - Google Patents
Instance deployment method and system Download PDFInfo
- Publication number
- CN111008023A CN111008023A CN201911243110.XA CN201911243110A CN111008023A CN 111008023 A CN111008023 A CN 111008023A CN 201911243110 A CN201911243110 A CN 201911243110A CN 111008023 A CN111008023 A CN 111008023A
- Authority
- CN
- China
- Prior art keywords
- cluster
- deployment
- proxy
- tiller
- platform
- 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
- 238000000034 method Methods 0.000 title claims abstract description 40
- 238000004891 communication Methods 0.000 claims abstract description 11
- 239000002699 waste material Substances 0.000 abstract description 6
- 230000008569 process Effects 0.000 description 8
- 230000009471 action Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 230000008878 coupling Effects 0.000 description 2
- 238000010168 coupling process Methods 0.000 description 2
- 238000005859 coupling reaction Methods 0.000 description 2
- 238000009434 installation Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
-
- 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
Abstract
The embodiment of the invention provides an example deployment method and an example deployment system, wherein the method is applied to a cluster management system, the cluster management system comprises a cluster information database, a platform tiller-proxy and a plurality of clusters, and when the platform tiller-proxy in the embodiment of the invention receives an example deployment instruction, a target cluster is determined in the cluster information database according to a target cluster ID in the example deployment instruction; and then sending the instance deployment instruction to a deployment component of the target cluster so that the deployment component deploys the instance according to the instance deployment instruction. In the embodiment of the invention, the cluster information database and the platform tiller-proxy are arranged, so that one platform tiller-proxy can realize communication with a plurality of clusters, thereby completing the deployment of the examples in the target cluster and avoiding resource waste.
Description
Technical Field
The invention relates to the field of cloud computing, in particular to an instance deployment method and an instance deployment system.
Background
Kubernetes, K8s for short, is an open source, is used for managing a containerized distributed system platform on a plurality of hosts in a cloud platform, and can realize the management of a cluster.
In order to facilitate the management of the cluster, kubernets official community provides Kubeapps, and referring to fig. 1, fig. 1 is a schematic structural diagram of kubernets adopted in the prior art, and Kubeapps includes three components, namely a front end, chartsvc and tiller-proxy. The chartsvc component is used for managing and configuring a chart application packaging file chart package in a chart warehouse, and the tiller-proxy component is used for realizing the deployment of the chart package in the cluster.
The tiller-proxy component needs to interact with a deployment component tiller and a Kubernetes APIServer of the cluster to achieve deployment of the application corresponding to the chat packet.
In the prior art, tiller-proxy components are deployed in clusters, and correspond to deployment components of the clusters one to one, if a user deploys a plurality of clusters, the tiller-proxy components are deployed in each cluster, which causes resource waste, and a close coupling relationship exists between the tiller-proxy components and the clusters.
Disclosure of Invention
In view of this, the present invention provides an example deployment method and system, so that when an example is deployed, deployment can be completed in a one-to-many manner, thereby avoiding resource waste and decoupling a tiller-proxy from a cluster.
In order to achieve the above object, the following solutions are proposed:
an example deployment method is applied to a cluster management system, wherein the cluster management system comprises a cluster information database, a platform tiller-proxy and a plurality of clusters, and the method comprises the following steps:
when the platform tiller-proxy receives an example deployment instruction, determining a target cluster in the cluster information database according to a target cluster ID in the example deployment instruction;
sending the instance deployment instruction to a deployment component of the target cluster, so that the deployment component deploys the instance according to the instance deployment instruction.
Preferably, the method further comprises the following steps:
when it is monitored that new cluster information is input into the cluster information database by creating a new cluster, a client component having a corresponding relation with the deployment component of the new cluster is created, so that communication with the deployment component of the new cluster is realized through the client component.
Preferably, the creating a client component having a corresponding relationship with the deployment component of the new cluster specifically includes:
adding the cluster ID of the new cluster in a first field corresponding to a Hash object established in the platform tiller-proxy, and adding a proxy object corresponding to the new cluster in a second field;
creating a first sub-client and a second sub-client in the proxy object;
the first sub-client is used for communicating with a tiller in the new cluster deployment component, and the second sub-client is used for communicating with a Kubeapps API Server in the new cluster deployment component.
Preferably, the method further comprises the following steps:
and when it is monitored that cluster information corresponding to the old cluster is deleted from the cluster information database by deleting the old cluster, deleting the client side component corresponding to the old cluster.
Preferably, the platform tiller-proxy is deployed outside of all clusters.
Preferably, the platform tiller-proxy is deployed in any one cluster.
In another aspect, the present invention further provides an instance deployment system, including:
the system comprises a cluster information database, a platform tiller-proxy and a plurality of clusters;
the platform tiller-proxy is used for determining a target cluster in the cluster information database according to a target cluster ID in an example deployment instruction when the example deployment instruction is received;
sending the instance deployment instruction to a deployment component of the target cluster, so that the deployment component deploys the instance according to the instance deployment instruction.
Preferably, the platform tiller-proxy is deployed outside of all clusters.
Preferably, the platform tiller-proxy is deployed in any one cluster.
The embodiment of the invention provides an example deployment method and an example deployment system, wherein the method is applied to a cluster management system, the cluster management system comprises a cluster information database, a platform tiller-proxy and a plurality of clusters, and when the platform tiller-proxy in the embodiment of the invention receives an example deployment instruction, a target cluster is determined in the cluster information database according to a target cluster ID in the example deployment instruction; and then sending the instance deployment instruction to a deployment component of the target cluster so that the deployment component deploys the instance according to the instance deployment instruction. In the embodiment of the invention, the cluster information database and the platform tiller-proxy are arranged, so that one platform tiller-proxy can realize communication with a plurality of clusters, thereby completing the deployment of the examples in the target cluster, avoiding resource waste and decoupling the tiller-proxy and the clusters.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
FIG. 1 is a schematic structural diagram of a K8s deployment example in the prior art;
fig. 2 is a flowchart illustrating an example deployment method according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The embodiment of the invention provides an instance deployment method and an instance deployment system, which are used for realizing deployment of a chart application. In the prior art, referring to fig. 1, fig. 1 is a schematic structural diagram of a deployment instance of K8s in the prior art, and in K8s, the deployment of one chart instance may be performed through the following processes:
1, calling chartsvc by the front end of kubaaps to list all chart packets;
2, the front end requests chartsvc to list all configuration information of the chart packet needing to be installed.
And 3, the front end sends the request for creating the instance to a tiller-proxy, so that the front end downloads the requested chart packet in a chart warehouse, namely chartmueum in the graph, sends related information to a tiller in the deployment component for analysis, sends the analyzed content to a Kubernets API Server in the deployment component, when the tiller-proxy is verified to have corresponding authority, the tiller-proxy sends the chart packet to the tiller, and the tiller calls Kubernets API Server to execute installation and stores application instance information into a database of the tiller-proxy to finish the deployment of the application in the cluster.
However, deployment components are in a one-to-one correspondence with tiller-proxy, thus resulting in wasted resources. In view of this, the present invention provides an example deployment method to avoid data redundancy and decouple the tiller-proxy from the cluster. The following describes embodiments of the present invention in detail.
Referring to fig. 2, fig. 2 is a flowchart illustrating an example deployment method according to an embodiment of the present invention.
The example deployment method provided by the invention is applied to a cluster management system, and the cluster management system comprises a cluster information database, a platform tiller-proxy and a plurality of clusters.
In the embodiment of the present invention, a cluster information database is provided, and cluster information of each cluster, such as a cluster ID, token, access address, and the like, is stored in the cluster information database.
In the embodiment of the invention, a platform tiller-proxy is also set, and the process of establishing the platform tiller-proxy can comprise the following steps: installing a tiller-proxy software package, modifying a corresponding configuration file and starting the configured service.
It is understood that the basic functions of the platform tiller-proxy are cross-referenced to the functions of tiller-proxy in the cluster.
In the embodiment of the invention, the platform tiller-proxy can be deployed in a certain cluster or can be deployed outside all clusters.
If the cluster is deployed outside all the clusters, other clusters do not need to deploy corresponding components, so that all the clusters are more simplified. If the cluster is deployed in a certain cluster, the cluster is required to have communication connection with other clusters, the requirement on the configuration of a single cluster is high, and the coupling is strong.
It will be appreciated that it may also be deployed in other devices with which communication with all clusters may be implemented. As long as the corresponding functions can be realized, the platform tiller-proxy in the embodiment of the invention can be deployed according to actual needs. This is not particularly limited.
In the embodiment of the invention, the method comprises the following steps:
s201, when the platform tiller-proxy receives an example deployment instruction, determining a target cluster in the cluster information database according to a target cluster ID in the example deployment instruction;
s202, sending the instance deployment instruction to a deployment component of the target cluster, so that the deployment component deploys the instance according to the instance deployment instruction.
Based on the above framework adopted by the present invention, in the embodiment of the present invention, the platform tiller-proxy receives an instance deployment instruction. The example deployment instruction may be sent by a user through a UI interface that operates and manages the platform tiller-proxy, or may be sent by another device.
It can be understood that the example deployment instruction includes a cluster ID of the target cluster, and in the embodiment of the present invention, the platform tiller-proxy may implement communication with multiple clusters, so that the cluster ID of the target cluster needs to be determined, so as to facilitate communication with the cluster where the example needs to be deployed.
In the embodiment of the invention, a deployment component is deployed in the target cluster, and the deployment component can be a tiller and a Kubernets API Server.
It should be noted that, the following example deployment process of tiller and kubernets API Server may refer to the prior art, and the process is not described in detail in the present invention.
In the embodiment of the invention, the method is applied to a cluster management system, the cluster management system comprises a cluster information database, a platform tiller-proxy and a plurality of clusters, and when the platform tiller-proxy in the embodiment of the invention receives an example deployment instruction, a target cluster is determined in the cluster information database according to a target cluster ID in the example deployment instruction; and then sending the instance deployment instruction to a deployment component of the target cluster so that the deployment component deploys the instance according to the instance deployment instruction. In the embodiment of the invention, the cluster information database and the platform tiller-proxy are arranged, so that one platform tiller-proxy can realize communication with a plurality of clusters, thereby completing the deployment of the examples in the target cluster and avoiding resource waste.
In the embodiment of the present invention, since a one-to-many relationship is established, if a new cluster is established, corresponding operations need to be performed on the new cluster.
On the basis of the above embodiment, the embodiment of the present invention further includes:
when it is monitored that new cluster information is input into the cluster information database by creating a new cluster, a client component having a corresponding relation with the deployment component of the new cluster is created, so that communication with the deployment component of the new cluster is realized through the client component.
In the embodiment of the invention, the data change when a new cluster is built can be realized by creating a database management component database manager object.
In the embodiment of the invention, the data change of the information database is monitored by the database management component, and if new cluster information is input into the cluster information database, the process of creating the client component corresponding to the deployment component of the new cluster is triggered. The same platform tiller-proxy is communicated with a plurality of clusters, and a plurality of cluster example deployments are realized.
In the embodiment of the invention, Proxy objects in a tiller-Proxy platform are changed into Hash objects, each item in the Hash objects corresponds to a cluster, wherein key is a cluster ID, and value is a Proxy object corresponding to the cluster.
In this embodiment of the present invention, the creating a client component having a corresponding relationship with the deployment component of the new cluster specifically includes:
adding the cluster ID of the new cluster in a first field corresponding to a Hash object established in the platform tiller-proxy, and adding a proxy object corresponding to the new cluster in a second field;
creating a first sub-client and a second sub-client in the proxy object;
the first sub-client is used for communicating with a tiller in the new cluster deployment component, and the second sub-client is used for communicating with a Kubeapps API Server in the new cluster deployment component.
In the embodiment of the invention, when the establishment of a new cluster is monitored, the cluster ID of the new cluster is added in a first field, namely a key, of a Hash object established in a platform tiller-Proxy, and a Proxy object corresponding to the cluster is added in a second field, namely a value field.
The first sub-client is a helmClient inside the Proxy object and is used for communicating with a tiller of the cluster, and the second sub-client is a kubbeclient inside the Proxy object and is used for communicating with a kubernets api server of the cluster. To collectively complete the deployment of the instances.
In the embodiment of the present invention, the method may further include:
and when it is monitored that cluster information corresponding to the old cluster is deleted from the cluster information database by deleting the old cluster, deleting the client side component corresponding to the old cluster.
In the embodiment of the invention, the new cluster is added, and the corresponding content corresponding to the old cluster can be deleted as the old cluster is deleted, so that the resource is saved to the maximum extent.
Therefore, in the embodiment of the present invention, when the old cluster is deleted, the corresponding content of the old cluster in the Hash object, such as the first sub-client and the second sub-client, is correspondingly deleted.
Therefore, the embodiment of the invention can save resources to the maximum extent and decouple the tiller-proxy and the cluster.
And (4) optional. The platform tiller-proxy is deployed outside of all clusters.
And (4) optional. The platform tiller-proxy is deployed in any one cluster.
Corresponding to the embodiment of the method, the invention also discloses an example deployment system.
The invention discloses an example deployment system, which comprises:
the system comprises a cluster information database, a platform tiller-proxy and a plurality of clusters;
the platform tiller-proxy is used for determining a target cluster in the cluster information database according to a target cluster ID in an example deployment instruction when the example deployment instruction is received;
sending the instance deployment instruction to a deployment component of the target cluster, so that the deployment component deploys the instance according to the instance deployment instruction.
And (4) optional. The platform tiller-proxy is deployed outside of all clusters.
And (4) optional. The platform tiller-proxy is deployed in any one cluster.
For the function implementation of the system, reference may be made to an example deployment method in the foregoing embodiment, and the adopted architecture and functions are not described herein again.
In the embodiment of the invention, the cluster information database and the platform tiller-proxy are arranged, so that one platform tiller-proxy can realize communication with a plurality of clusters, thereby completing the deployment of the examples in the target cluster, avoiding resource waste and decoupling the tiller-proxy and the clusters.
Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The embodiments in the present description are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (9)
1. An example deployment method is applied to a cluster management system, wherein the cluster management system comprises a cluster information database, a platform tiller-proxy and a plurality of clusters, and the method comprises the following steps:
when the platform tiller-proxy receives an example deployment instruction, determining a target cluster in the cluster information database according to a target cluster ID in the example deployment instruction;
sending the instance deployment instruction to a deployment component of the target cluster, so that the deployment component deploys the instance according to the instance deployment instruction.
2. The method of claim 1, further comprising:
when it is monitored that new cluster information is input into the cluster information database by creating a new cluster, a client component having a corresponding relation with the deployment component of the new cluster is created, so that communication with the deployment component of the new cluster is realized through the client component.
3. The method according to claim 2, wherein the creating a client component having a correspondence with the deployment component of the new cluster specifically comprises:
adding the cluster ID of the new cluster in a first field corresponding to a Hash object established in the platform tiller-proxy, and adding a proxy object corresponding to the new cluster in a second field;
creating a first sub-client and a second sub-client in the proxy object;
the first sub-client is used for communicating with a tiller in the new cluster deployment component, and the second sub-client is used for communicating with a Kubeapps API Server in the new cluster deployment component.
4. The method of claim 3, further comprising:
and when it is monitored that cluster information corresponding to the old cluster is deleted from the cluster information database by deleting the old cluster, deleting the client side component corresponding to the old cluster.
5. The method of claim 1, wherein the platform tiller-proxy is deployed outside of all clusters.
6. The method of claim 1, wherein the platform tiller-proxy is deployed in any one cluster.
7. An instance deployment system, comprising:
the system comprises a cluster information database, a platform tiller-proxy and a plurality of clusters;
the platform tiller-proxy is used for determining a target cluster in the cluster information database according to a target cluster ID in an example deployment instruction when the example deployment instruction is received;
sending the instance deployment instruction to a deployment component of the target cluster, so that the deployment component deploys the instance according to the instance deployment instruction.
8. The system of claim 7, wherein the platform tiller-proxy is deployed outside of all clusters.
9. The system of claim 7, wherein the platform tiller-proxy is deployed in any one of the clusters.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911243110.XA CN111008023B (en) | 2019-12-06 | 2019-12-06 | Instance deployment method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911243110.XA CN111008023B (en) | 2019-12-06 | 2019-12-06 | Instance deployment method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111008023A true CN111008023A (en) | 2020-04-14 |
| CN111008023B CN111008023B (en) | 2024-01-09 |
Family
ID=70115071
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911243110.XA Active CN111008023B (en) | 2019-12-06 | 2019-12-06 | Instance deployment method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111008023B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114500268A (en) * | 2022-01-17 | 2022-05-13 | 远景智能国际私人投资有限公司 | Deployment method, device, server and storage medium of chart resource |
| CN116192853A (en) * | 2023-04-25 | 2023-05-30 | 安元科技股份有限公司 | Multi-cluster management method |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106713458A (en) * | 2016-12-23 | 2017-05-24 | 智者四海（北京）技术有限公司 | Zookeeper cluster deployment method, Zookeeper cluster deployment device, Zookeeper instance deployment method, Zookeeper instance deployment device, and Zookeeper cluster management platform |
| CN106815318A (en) * | 2016-12-24 | 2017-06-09 | 上海七牛信息技术有限公司 | A kind of clustering method and system of time series database |
| US20170300352A1 (en) * | 2014-12-29 | 2017-10-19 | Huawei Technologies Co., Ltd. | Method and Apparatus for Deploying Virtual Machine Instance, and Device |
| CN108737468A (en) * | 2017-04-19 | 2018-11-02 | 中兴通讯股份有限公司 | Cloud platform service cluster, construction method and device |
| CN108804618A (en) * | 2018-05-31 | 2018-11-13 | 康键信息技术（深圳）有限公司 | Configuration method for database, device, computer equipment and storage medium |
-
2019
- 2019-12-06 CN CN201911243110.XA patent/CN111008023B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170300352A1 (en) * | 2014-12-29 | 2017-10-19 | Huawei Technologies Co., Ltd. | Method and Apparatus for Deploying Virtual Machine Instance, and Device |
| CN106713458A (en) * | 2016-12-23 | 2017-05-24 | 智者四海（北京）技术有限公司 | Zookeeper cluster deployment method, Zookeeper cluster deployment device, Zookeeper instance deployment method, Zookeeper instance deployment device, and Zookeeper cluster management platform |
| CN106815318A (en) * | 2016-12-24 | 2017-06-09 | 上海七牛信息技术有限公司 | A kind of clustering method and system of time series database |
| CN108737468A (en) * | 2017-04-19 | 2018-11-02 | 中兴通讯股份有限公司 | Cloud platform service cluster, construction method and device |
| CN108804618A (en) * | 2018-05-31 | 2018-11-13 | 康键信息技术（深圳）有限公司 | Configuration method for database, device, computer equipment and storage medium |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114500268A (en) * | 2022-01-17 | 2022-05-13 | 远景智能国际私人投资有限公司 | Deployment method, device, server and storage medium of chart resource |
| CN114500268B (en) * | 2022-01-17 | 2023-07-21 | 远景智能国际私人投资有限公司 | Method and device for deploying char resources, server and storage medium |
| CN116192853A (en) * | 2023-04-25 | 2023-05-30 | 安元科技股份有限公司 | Multi-cluster management method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111008023B (en) | 2024-01-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11750456B2 (en) | Secure configuration of cloud computing nodes | |
| CN110311983B (en) | Service request processing method, device and system, electronic equipment and storage medium | |
| US20070294376A1 (en) | Method, apparatus and program product for software provisioning | |
| CN111258723B (en) | Transaction processing method, device, system, medium and equipment of distributed system | |
| US11546287B2 (en) | Multi-device workspace notifications | |
| US10404568B2 (en) | Agent manager for distributed transaction monitoring system | |
| US20160352843A1 (en) | Data Processing Method, Device, and ESB System | |
| WO2016115896A1 (en) | Method and device for management of virtual network function (vnf) | |
| EP3826266B1 (en) | Method for sending a certificate, method for receiving a certificate, cloud and terminal device | |
| CN111345008A (en) | Mobile edge host service notification method and device | |
| CN111008023A (en) | Instance deployment method and system | |
| CN112751847A (en) | Interface call request processing method and device, electronic equipment and storage medium | |
| CN112187903B (en) | Message pushing method and device and message service system | |
| CN111090495A (en) | Node management method, device, equipment, storage medium and system | |
| CN110990025A (en) | Instance deployment method and system | |
| CN108073426B (en) | Software management method, device and system based on cloud computing | |
| US8560732B2 (en) | Peer-to-peer object distribution | |
| CN113783914A (en) | Data processing method, device and equipment | |
| CN104573489A (en) | Method and device for forbidding application to establish desktop icon | |
| CN109218259B (en) | License management method and device, APPLM functional entity and computer readable storage medium | |
| US7350065B2 (en) | Method, apparatus and program storage device for providing a remote power reset at a remote server through a network connection | |
| CN111831402A (en) | Method, apparatus and computer program product for managing software functions | |
| CN112685102B (en) | Gateway plug-in hot loading method, device, equipment and medium | |
| CN105827567B (en) | Service management and control method and capability opening platform | |
| CN110650033B (en) | Distributed application configuration management method and distributed computing system |
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 |