CN110572276B - Deployment method, device, equipment and storage medium - Google Patents
Deployment method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN110572276B CN110572276B CN201910746474.3A CN201910746474A CN110572276B CN 110572276 B CN110572276 B CN 110572276B CN 201910746474 A CN201910746474 A CN 201910746474A CN 110572276 B CN110572276 B CN 110572276B
- Authority
- CN
- China
- Prior art keywords
- cloud
- framework
- identifier
- matched
- deployment
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0823—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Hardware Redundancy (AREA)
Abstract
The application provides a deployment method, a deployment device, deployment equipment and a storage medium, and belongs to the technical field of cloud. The deployment method comprises the following steps: acquiring a first cloud arrangement framework, wherein functional components in the first cloud arrangement framework are less than functional components in a second cloud arrangement framework; deploying the first cloud orchestration framework. According to the method and the device, the size of the acquired first cloud arrangement frame is smaller than that of the acquired second cloud arrangement frame, so that the occupation of the first cloud arrangement frame on system resources is reduced during deployment, and the first cloud arrangement frame is more flexible in deployment and dynamic expansion and contraction and is easier to use.
Description
Technical Field
The present application relates to the field of cloud technologies, and in particular, to a deployment method, an apparatus, a device, and a storage medium.
Background
With the rapid development of information technology, the complexity of software systems is higher and higher, and the architecture design mode of micro-service architecture is becoming more and more popular. Along with the increasing maturity of containerization technology, more and more software adopts containerization schemes for deployment and operation and maintenance management, so that the operation and maintenance are greatly facilitated, the operation and maintenance management cost is reduced, and meanwhile, some new requirements are provided for some existing software.
At present, Cloudify is used as an open-source mature cloud arrangement framework, and the design and the use of arrangement are greatly facilitated. The method has many advantages of pluggable plug-ins, Topology and business process specifications based on standard TOSCA (TOPOLOGY and organizational Specification for Cloud Applications), support for various Cloud environments, and the like.
However, when the Cloudify is deployed, the entire Cloudify is directly deployed on the node, resulting in a large storage space required for each deployment, and thus a large system resource is occupied.
Disclosure of Invention
An object of the embodiments of the present application is to provide a method, an apparatus, a device, and a storage medium for deploying system resources, which can reduce occupation of the system resources.
In a first aspect, an embodiment of the present application provides a method for deploying a mobile device, where the method includes: acquiring a first cloud arrangement framework, wherein functional components in the first cloud arrangement framework are less than functional components in a second cloud arrangement framework; deploying the first cloud orchestration framework.
In the implementation process, by obtaining the first cloud arrangement frame, functional components in the first cloud arrangement frame are less than functional components in the second cloud arrangement frame, so that when the first cloud arrangement frame is deployed, the size of the first cloud arrangement frame is smaller than that of the second cloud arrangement frame, and therefore the occupation of system resources by the first cloud arrangement frame is reduced, and the first cloud arrangement frame is more flexible in deployment and dynamic expansion and contraction and is easier to use.
With reference to the first aspect, an embodiment of the present application provides a first possible implementation manner of the first aspect, where the obtaining a first cloud orchestration framework includes: acquiring state identification of each component in the second cloud orchestration framework, wherein the state identification comprises a first identification used for representing that the component is in a state and a second identification used for representing that the component is not in a state; and splitting the component matched with the first identifier from the second cloud arrangement frame to obtain the first cloud arrangement frame matched with the second identifier.
In the implementation process, the state identifier of each component in the second cloud arrangement framework is obtained, so that the components with the states are quickly removed from the second cloud arrangement framework, and the first cloud arrangement framework is accurately and quickly obtained.
With reference to the first possible implementation manner of the first aspect, this application provides a second possible implementation manner of the first aspect, where splitting the component matching the first identifier from the second cloud arrangement framework to obtain the first cloud arrangement framework matching the second identifier includes: and splitting the message queue RabbitMQ and the data storage Postgres matched with the first identifier from the second cloud arrangement framework to obtain the first cloud arrangement framework matched with the second identifier.
In the implementation process, the message queue RabbitMQ and the data storage Postgres matched with the first identifier are separated from the second cloud arrangement framework, so that the size of the first cloud arrangement framework can be effectively reduced, and the first cloud arrangement framework can be conveniently fused into kubernets for use.
With reference to the second possible implementation manner of the first aspect, an embodiment of the present application provides a third possible implementation manner of the first aspect, where the RabbitMQ is deployed on each first node in the first cluster.
In the implementation process, the RabbitMQ is deployed on the first cluster, so that the first cloud orchestration framework can conveniently access the message queue for communication through the RabbitMQ cluster, and the reliability of the message queue is guaranteed.
With reference to the third possible implementation manner of the first aspect, an embodiment of the present application provides a fourth possible implementation manner of the first aspect, where the Postgres is deployed on each second node in the second cluster.
In the implementation process, a Postgres cluster is built, so that the redundancy and high availability of the data of the first cloud arrangement framework are ensured, and the reliability of the data is increased.
With reference to the third possible implementation manner of the first aspect, an embodiment of the present application provides a fourth possible implementation manner of the first aspect, and the method further includes: deploying a synchronization system on the at least one node, the synchronization system for synchronizing data stored in each node on which the first cloud orchestration framework is deployed.
In the implementation process, by deploying the synchronization system, when the files in the first cloud arrangement framework/under the resources directories are changed, the synchronization system can synchronize the changed data to other nodes, so that all the visible/resources directories in the first cloud arrangement framework are the same, and thus the normal work of each first cloud arrangement framework is ensured.
In a second aspect, an embodiment of the present application provides a deployment apparatus, including: the cloud editing system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring a first cloud editing frame, and functional components in the first cloud editing frame are less than functional components in a second cloud editing frame; a first deployment module to deploy the first cloud orchestration framework.
With reference to the second aspect, an embodiment of the present application provides a first possible implementation manner of the second aspect, where the obtaining module includes: a first sub-module, configured to obtain a state identifier of each component in the second cloud orchestration framework, where the state identifier includes a first identifier for representing that the component is in a state and a second identifier for representing that the component is not in a state; and the second submodule is used for splitting the component matched with the first identifier from the second cloud arrangement framework to obtain the first cloud arrangement framework matched with the second identifier.
With reference to the first possible implementation manner of the second aspect, an embodiment of the present application provides a second possible implementation manner of the second aspect, where the second sub-module is further configured to: and splitting the message queue RabbitMQ and the data storage Postgres matched with the first identifier from the second cloud arrangement framework to obtain the first cloud arrangement framework matched with the second identifier.
In combination with the first possible implementation manner of the second aspect, the present embodiment provides a third possible implementation manner of the second aspect, and the RabbitMQ is deployed on each first node in the first cluster.
With reference to the third possible implementation manner of the second aspect, this embodiment provides a fourth possible implementation manner of the second aspect, and the Postgres is deployed on each second node in the second cluster.
In combination with any implementation manner of the second aspect, this application provides a fifth possible implementation manner of the second aspect, and the apparatus further includes: a second deployment module configured to deploy a synchronization system on the at least one node, the synchronization system being configured to synchronize data stored in each node on which the first cloud orchestration framework is deployed.
In a third aspect, an embodiment of the present application provides a server, including: a memory, a processor and a computer program stored in the memory and executable on the processor, the processor implementing the steps of the deployment method according to any one of the first aspect when executing the computer program.
In a fourth aspect, a storage medium is provided in an embodiment of the present application, where the storage medium has instructions stored thereon, and when the instructions are executed on a computer, the instructions cause the computer to perform the deployment method according to any one of the first aspect.
In a fifth aspect, an embodiment of the present application provides a computer program product, which when run on a computer, causes the computer to execute the deployment method according to any one of the first aspect.
Additional features and advantages of the disclosure will be set forth in the description which follows, or in part may be learned by the practice of the above-described techniques of the disclosure, or may be learned by practice of the disclosure.
In order to make the aforementioned objects, features and advantages of the present application more comprehensible, preferred embodiments accompanied with figures are described in detail below.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments of the present application will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and that those skilled in the art can also obtain other related drawings based on the drawings without inventive efforts.
FIG. 1 is a flow chart of a method of deployment provided by an embodiment of the present application;
FIG. 2 is a schematic diagram of cluster deployment in one deployment method shown in FIG. 1;
fig. 3 is a schematic structural diagram of a deployment apparatus according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.
Referring to fig. 1, fig. 1 is a flowchart of a deployment method provided in the embodiment of the present application, it should be understood that the method may be executed by a deployment apparatus shown in fig. 3, which corresponds to the electronic device shown in fig. 4, which may be various devices capable of executing the method, such as a computer or a cloud server, and the embodiment of the present application is not limited thereto, and specifically includes the following steps:
step S101, a first cloud arrangement framework is obtained.
Optionally, the functional components in the first cloud orchestration framework are less than the functional components in the second cloud orchestration framework.
Optionally, the second cloud orchestration framework is prior art Cloudify.
Alternatively, the first cloud orchestration framework may exist in the form of an image file.
Optionally, the first cloud orchestration framework may be uploaded by a user or downloaded over a network. Here, the number of the carbon atoms is not particularly limited.
Optionally, the second cloud orchestration framework is composed of a plurality of components, and specifically, the second cloud orchestration framework includes two states of components, where each state corresponds to a plurality of components. While the functional components in the first cloud orchestration framework have only one state.
Alternatively, a component may also be referred to as a service, and may also be referred to as a functional module. Here, the number of the carbon atoms is not particularly limited.
Optionally, the two states include both stateful and stateless.
Alternatively, a stateful service refers to a service that returns results that are not the same when multiple users access the service. If the returned results are the same, it is stateless. For example, a user requests multiple times, and each time the result returned is the same, the service is stateless. On the contrary, if a user requests for a plurality of times, the returned result is different every time, the service is stateful.
As an embodiment, step S101 includes: acquiring state identification of each component in the second cloud orchestration framework, wherein the state identification comprises a first identification used for representing that the component is in a state and a second identification used for representing that the component is not in a state; and splitting the component matched with the first identifier from the second cloud arrangement frame to obtain the first cloud arrangement frame matched with the second identifier.
Optionally, the second cloud arrangement framework may be split manually, or the splitting of the second cloud arrangement framework may be automatically completed by the electronic device.
Alternatively, the state identification of each component in the second cloud orchestration framework may be obtained individually.
Of course, in actual use, to improve efficiency, the state identification of each component in the second cloud orchestration framework may be obtained concurrently. Namely, the state identifications of all the components are collected at one time at the same time in a multi-thread concurrent mode.
Alternatively, the status flag may be pre-marked by the developer, or may be measured by a mechanism of sending messages multiple times through the electronic device. For example, when the state of a certain component is measured to be a non-state, the component is marked with a second identifier, and when the state of a certain component is measured to be a state, the component is marked with a first identifier. Here, the number of the carbon atoms is not particularly limited.
In the implementation process, the state identifier of each component is acquired, so that the components with the states are quickly removed from the second cloud arrangement framework, and the first cloud arrangement framework is accurately and quickly obtained.
Optionally, the first cloud orchestration framework is made up of stateless components.
Optionally, the second cloud orchestration framework comprises components such as message queues RabbitMQ, data stores postgrids, cloud-restservices, cloud-mgmtworker, cloud-amqp-postgrids, cloud-stage, nginx, and resource.
Optionally, the message queue RabbitMQ and the data storage Postgres are stateful components.
Optionally, the components include Cloudify-restservice, Cloudify-mgmtworker, Cloudify-amqp-postgrams, Cloudify-stage, nginx, and resource.
Optionally, the splitting the component matching the first identifier out of the second cloud arrangement framework to obtain the first cloud arrangement framework matching the second identifier includes: and splitting the message queue RabbitMQ and the data storage Postgres matched with the first identifier from a second cloud arrangement frame to obtain the first cloud arrangement frame matched with the second identifier.
Alternatively, the first cloud orchestration framework may be referred to as Cloudify POD.
Optionally, the RabbitMQ is a message queue service in Cloudify, which is responsible for passing messages between the various components, reporting the progress of the workflow.
Optionally, the first cloud orchestration framework matched with the second identifier is formed by components of which the obtained first cloud orchestration framework is stateless.
Optionally, the RabbitMQ is deployed on each first node in the first cluster.
Optionally, the first cluster is a high availability cluster.
In the implementation process, the RabbitMQ is deployed on the high-availability cluster, so that the message queue can be conveniently accessed by the cloud POD through the Rabbitmq cluster for communication, and the reliability of the message queue is ensured.
Optionally, the Postgres is deployed on each second node in the second cluster.
Optionally, the second cluster is a high availability cluster.
Alternatively, the second node may be the same physical machine as the first node. That is, Postgres and RabbitMQ may be deployed on the same physical machine, but may constitute two different clusters.
In the implementation process, the data reliability is increased by building a Postgres cluster so as to ensure the redundancy and high availability of the data of the cloud POD.
Step S102, deploying the first cloud orchestration framework.
Alternatively, a physical machine or server may complete the deployment by running an image file of the first cloud orchestration framework.
Alternatively, the Cloudify POD may be deployed on one node, or may be deployed on multiple nodes, for example, 2 or 3, etc. Here, the number of the carbon atoms is not particularly limited.
Alternatively, the node deployed by the Cloudify POD may be on the same physical machine as that deployed by Postgres and RabbitMQ.
Of course, it is also possible to deploy Cloudify POD onto a different physical machine than that deployed by Postgres and RabbitMQ. Here, the number of the carbon atoms is not particularly limited.
Optionally, the nodes deployed with Cloudify PODs are in data communication with the first cluster and the second cluster, respectively, to form a new high availability cluster. For example, as shown in fig. 2, Cloudify POD can interact with Postgres clusters and RabbitMQ clusters for data to implement a highly available clustering scheme.
Alternatively, although the existing Cloudify can be deployed on multiple nodes, it can only exist independently, i.e., cannot form a cluster. Since in the conventional Cloudify, the RabbitMq is in the same Pod as other components of the Cloudify, and when the Pod is hung, the RabbitMq is also in a fault state, so that the whole node is unavailable.
In the implementation manner, because the existing open-source community version of Cloudify only provides a single-copy method based on docker images, which cannot be directly applied to the micro-service architecture with high availability requirement, the application forms a high-availability cluster by stripping stateful components in Cloudify, deploying a Postgres cluster and a RabbitMQ cluster, and deploying Cloudify POD on at least one node, so that the Cloudify POD communicates with the Postgres cluster and the RabbitMQ cluster, and thus the Cloudify can also be applied to the micro-service architecture with high requirement (i.e. applied to the high-availability cluster).
Optionally, the first cloud orchestration framework is deployed on at least one node on which kubernets are installed.
Alternatively, kubernets, abbreviated K8s, is an abbreviation for 8 instead of the 8 characters "ubernet". The Kubernetes is an open source and used for managing containerized applications on a plurality of hosts in a cloud platform, aims to make the application of the containerization simple and efficient to deploy (powerfull), and provides a mechanism for deploying, planning, updating and maintaining the applications.
In a possible embodiment, the method further comprises: deploying, on at least one node, a synchronization system for synchronizing data stored in each node on which the first cloud orchestration framework is deployed.
Optionally, at least one node may be any node installed with kubernets, or any node in the second node, or any node in the first node. It may also be any node that deploys the first cloud orchestration framework. Here, the number of the carbon atoms is not particularly limited.
Alternatively, the synchronization system may also be referred to as a file synchronization system.
Alternatively, the synchronization system may be configured to synchronize data in the Cloudify POD node for each deployment by a combination of an inotify tool and a rsync (remote synchronization) tool. For example, when a file in the cloud POD node/resources directory changes, the synchronization system synchronizes the changed data to other nodes, so that all the records in the cloud POD are the same, thereby ensuring the normal operation of each cloud POD.
For example, as shown in fig. 2, when the file synchronization system monitors that a file in a Cloudify POD/under a resources directory changes, a preinstalled inotify tool and a rsync tool are used to synchronize data of any Cloudify POD changing to other nodes, so that all the visible/resources directories in the Cloudify PODs are the same, thereby ensuring the normal operation of each Cloudify POD.
In the implementation process, by deploying the synchronization system, when the files in the first cloud arrangement framework/under the resources directories are changed, the synchronization system can synchronize the changed data to other nodes, so that all the visible/resources directories in the first cloud arrangement framework are the same, and thus the normal work of each first cloud arrangement framework is ensured.
According to the deployment method provided by the embodiment of the application, by obtaining the first cloud arrangement frame, the functional components in the first cloud arrangement frame are less than the functional components in the second cloud arrangement frame, so that when the first cloud arrangement frame is deployed, the size of the first cloud arrangement frame is smaller than that of the second cloud arrangement frame, and therefore the occupation of system resources by the first cloud arrangement frame is reduced, and the first cloud arrangement frame is more flexible in deployment and dynamic expansion and contraction and is easier to use.
Based on the same inventive concept, please refer to fig. 3, an embodiment of the present application further provides a deployment apparatus corresponding to the deployment method shown in fig. 1, it should be understood that the apparatus 300 corresponds to the method embodiment of fig. 1, and is capable of performing the steps related to the method embodiment, specific functions of the apparatus 300 may be referred to the description above, and detailed descriptions are appropriately omitted herein to avoid redundancy. The apparatus 300 includes at least one software functional module that can be stored in a memory in the form of software or firmware (firmware) or solidified in an Operating System (OS) of the electronic device. Specifically, the apparatus 300 includes:
an obtaining module 310 is configured to obtain a first cloud arrangement framework, where functional components in the first cloud arrangement framework are less than functional components in a second cloud arrangement framework.
A first deployment module 320 to deploy the first cloud orchestration framework.
Optionally, the obtaining module 310 includes: a first sub-module, configured to obtain a state identifier of each component in the second cloud orchestration framework, where the state identifier includes a first identifier for representing that the component is in a state and a second identifier for representing that the component is not in a state; and the second submodule is used for splitting the component matched with the first identifier from the second cloud arrangement framework to obtain the first cloud arrangement framework matched with the second identifier.
Optionally, the second sub-module is further configured to: and splitting the message queue RabbitMQ and the data storage Postgres matched with the first identifier from the second cloud arrangement framework to obtain the first cloud arrangement framework matched with the second identifier.
Optionally, the RabbitMQ is deployed on each first node in the first cluster.
Optionally, the Postgres is deployed on each second node in the second cluster.
In a possible embodiment, the apparatus 300 further comprises: a second deployment module configured to deploy a synchronization system on the at least one node, the synchronization system being configured to synchronize data stored in each node on which the first cloud orchestration framework is deployed.
Based on the same inventive concept, the present application further provides an electronic device, and fig. 4 is a block diagram of a structure of the electronic device 500 in the embodiment of the present application, as shown in fig. 4. Electronic device 500 may include a processor 510, a communication interface 520, a memory 530, and at least one communication bus 540. Wherein the communication bus 540 is used for realizing direct connection communication of these components. The communication interface 520 of the device in the embodiment of the present application is used for performing signaling or data communication with other node devices. Processor 510 may be an integrated circuit chip having signal processing capabilities.
The Processor 510 may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; but may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor 510 may be any conventional processor or the like.
The Memory 530 may be, but is not limited to, a Random Access Memory (RAM), a Read Only Memory (ROM), a Programmable Read-Only Memory (PROM), an Erasable Read-Only Memory (EPROM), an electrically Erasable Read-Only Memory (EEPROM), and the like. The memory 530 stores computer readable instructions that, when executed by the processor 510, enable the electronic device 500 to perform the steps associated with the method embodiment of fig. 1 described above.
Optionally, the electronic device 500 may also include a memory controller.
The memory 530, memory controller, and processor 510 are electrically connected to each other directly or indirectly to enable data transmission or interaction. For example, these elements may be electrically coupled to each other via one or more communication buses 540. The processor 510 is used to execute executable modules stored in the memory 530, such as software functional modules or computer programs included in the apparatus 300. Also, the apparatus 300 is configured to perform the following method: acquiring a first cloud arrangement frame; deploying the first cloud orchestration framework.
It is to be understood that the configuration shown in fig. 4 is merely exemplary, and that the electronic device 500 may include more or fewer components than shown in fig. 4, or have a different configuration than shown in fig. 4. The components shown in fig. 4 may be implemented in hardware, software, or a combination thereof.
The embodiment of the present application further provides a storage medium, where the storage medium stores instructions, and when the instructions are run on a computer, when the computer program is executed by a processor, the method in the method embodiment is implemented, and in order to avoid repetition, details are not repeated here.
The present application also provides a computer program product which, when run on a computer, causes the computer to perform the method of the method embodiments.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one logical division, and there may be other divisions when actually implemented, and for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of devices or units through some communication interfaces, and may be in an electrical, mechanical or other form.
In addition, units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
Furthermore, the functional modules in the embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
In this document, 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.
The above description is only an example of the present application and is not intended to limit the scope of the present application, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application.
Claims (6)
1. A method of deployment, the method comprising:
acquiring a first cloud arrangement framework, wherein functional components in the first cloud arrangement framework are less than functional components in a second cloud arrangement framework; wherein the second cloud orchestration framework is Cloudify;
deploying the first cloud orchestration framework;
wherein the obtaining a first cloud orchestration framework comprises:
acquiring state identification of each component in the second cloud orchestration framework, wherein the state identification comprises a first identification used for representing that the component is in a state and a second identification used for representing that the component is not in a state;
splitting the component matched with the first identifier from the second cloud arrangement framework to obtain the first cloud arrangement framework matched with the second identifier;
splitting the component matched with the first identifier from the second cloud arrangement framework to obtain the first cloud arrangement framework matched with the second identifier, wherein the splitting comprises: splitting a message queue RabbitMQ and a data storage Postgres which are matched with the first identifier from the second cloud arrangement framework to obtain the first cloud arrangement framework matched with the second identifier;
the method further comprises the following steps: deploying, on at least one node, a synchronization system for synchronizing data stored in each node on which the first cloud orchestration framework is deployed.
2. The method as in claim 1, wherein the RabbitMQ is deployed at each first node in the first cluster.
3. The method of claim 2, wherein the Postgres is deployed on each second node in a second cluster.
4. A deployment device, comprising:
the cloud editing system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring a first cloud editing frame, and functional components in the first cloud editing frame are less than functional components in a second cloud editing frame; wherein the second cloud orchestration framework is Cloudify;
a first deployment module to deploy the first cloud orchestration framework;
wherein, the obtaining module includes:
a first sub-module, configured to obtain a state identifier of each component in the second cloud orchestration framework, where the state identifier includes a first identifier for representing that the component is in a state and a second identifier for representing that the component is not in a state;
the second submodule is used for splitting the component matched with the first identifier from the second cloud arrangement framework to obtain the first cloud arrangement framework matched with the second identifier;
the second submodule is provided with a message queue RabbitMQ and a data storage Postgres which are matched with the first identifier, and is used for splitting the message queue RabbitMQ and the data storage Postgres from the second cloud arrangement frame to obtain the first cloud arrangement frame matched with the second identifier;
the device further comprises: a second deployment module configured to deploy a synchronization system on at least one node, the synchronization system configured to synchronize data stored in each node on which the first cloud orchestration framework is deployed.
5. An electronic device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, the processor implementing the steps of the deployment method according to any one of claims 1-3 when executing the computer program.
6. A storage medium having stored thereon a computer program which, when run on a computer, causes the computer to execute the deployment method of any one of claims 1-3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910746474.3A CN110572276B (en) | 2019-08-13 | 2019-08-13 | Deployment method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910746474.3A CN110572276B (en) | 2019-08-13 | 2019-08-13 | Deployment method, device, equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110572276A CN110572276A (en) | 2019-12-13 |
| CN110572276B true CN110572276B (en) | 2021-02-09 |
Family
ID=68775153
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910746474.3A Active CN110572276B (en) | 2019-08-13 | 2019-08-13 | Deployment method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110572276B (en) |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107948254A (en) * | 2017-11-10 | 2018-04-20 | 上海华讯网络***有限公司 | Mix the big data processing frame arranging system and method for cloud platform |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10680880B2 (en) * | 2014-01-31 | 2020-06-09 | Micro Focus Llc | Cloud implementation orchestration |
| US9621428B1 (en) * | 2014-04-09 | 2017-04-11 | Cisco Technology, Inc. | Multi-tiered cloud application topology modeling tool |
| CN106209402B (en) * | 2015-04-30 | 2019-10-22 | 华为技术有限公司 | A kind of telescopic method and equipment of virtual network function |
| CN109040152B (en) * | 2017-06-08 | 2022-05-31 | 创新先进技术有限公司 | Service request and providing method and device based on service arrangement and electronic equipment |
| CN109327490B (en) * | 2017-07-31 | 2021-01-15 | 华为技术有限公司 | Method and server for deploying cloud service component |
| CN108279926B (en) * | 2018-01-10 | 2021-06-08 | 浙江网新恒天软件有限公司 | Method for micro-service of single application |
-
2019
- 2019-08-13 CN CN201910746474.3A patent/CN110572276B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107948254A (en) * | 2017-11-10 | 2018-04-20 | 上海华讯网络***有限公司 | Mix the big data processing frame arranging system and method for cloud platform |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110572276A (en) | 2019-12-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108809722B (en) | Method, device and storage medium for deploying Kubernetes cluster | |
| CN106331098B (en) | Server cluster system | |
| CN107870845B (en) | Management method and system for micro-service architecture application | |
| EP3252607A1 (en) | Network function virtualization management and orchestration device, system, management method, and program | |
| CN113742031B (en) | Node state information acquisition method and device, electronic equipment and readable storage medium | |
| CN111163173B (en) | Cluster configuration method and device, server and readable storage medium | |
| CN109871384B (en) | Method, system, equipment and storage medium for container migration based on PaaS platform | |
| CN107666493B (en) | Database configuration method and equipment thereof | |
| CN109245908B (en) | Method and device for switching master cluster and slave cluster | |
| CN110932914B (en) | Deployment method, deployment device, hybrid cloud system architecture and computer storage medium | |
| CN112698992B (en) | Disaster recovery management method and related device for cloud cluster | |
| CN112417051A (en) | Container arrangement engine resource management method and device, readable medium and electronic equipment | |
| CN105306237A (en) | Distributed management method and device for network management | |
| CN107665141B (en) | Database configuration method and equipment thereof | |
| CN105530116B (en) | Method and corresponding device for backing up and recovering virtualized network | |
| CN110391940A (en) | Response method, device, system, equipment and the storage medium of address of service | |
| CN111641521A (en) | Ambari-based method for deploying big data clusters on cloud | |
| CN114565502A (en) | GPU resource management method, scheduling method, device, electronic equipment and storage medium | |
| CN111078238A (en) | Centralized processing method and device for application configuration in container environment | |
| CN112087516A (en) | Storage upgrading method and device based on Docker virtualization technology | |
| EP3883183A1 (en) | Virtualization management method and device | |
| CN110572276B (en) | Deployment method, device, equipment and storage medium | |
| CN113220432A (en) | Multi-cloud interconnection method, device, equipment, storage medium and product | |
| CN113726638B (en) | Method, device and equipment for managing multi-cloud multi-core container and storage medium | |
| CN110798358A (en) | Distributed service identification method and device, computer readable medium and electronic equipment |
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: No. 6 Science and Education Software Park, Binhu District, Wuxi City, Jiangsu Province Applicant after: Huayun data holding group Co., Ltd Address before: No. 6 Science and Education Software Park, Binhu District, Wuxi City, Jiangsu Province Applicant before: WUXI CHINAC DATA TECHNICAL SERVICE Co.,Ltd. |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |