CN112114939A - Distributed system deployment equipment and method - Google Patents
Distributed system deployment equipment and method Download PDFInfo
- Publication number
- CN112114939A CN112114939A CN202010921043.9A CN202010921043A CN112114939A CN 112114939 A CN112114939 A CN 112114939A CN 202010921043 A CN202010921043 A CN 202010921043A CN 112114939 A CN112114939 A CN 112114939A
- Authority
- CN
- China
- Prior art keywords
- task
- deployment
- information
- distributed system
- target
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 29
- 238000004891 communication Methods 0.000 claims abstract description 48
- 230000004044 response Effects 0.000 claims abstract description 27
- 238000010586 diagram Methods 0.000 description 15
- 230000006870 function Effects 0.000 description 15
- 238000004590 computer program Methods 0.000 description 7
- 238000012545 processing Methods 0.000 description 5
- 238000013515 script Methods 0.000 description 4
- 238000011161 development Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000000694 effects Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000006835 compression Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/465—Distributed object oriented systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
Abstract
The application provides a distributed system deployment device and a distributed system deployment method, and relates to the technical field of distributed systems. The equipment deployed by the distributed system can receive configuration information and configuration files uploaded by the terminal through the communication component; responding to a task creating instruction received by the communication component, and creating a deployment task for deploying the target distributed system to a target node according to the configuration information and the configuration file; and in response to an execution command for the deployment task received through the communication component, deploying the configuration file in the deployment task to the target node. The distributed system deployment equipment firstly deploys the distributed system into tasks in a task customization mode, and then the tasks are called through the system, so that the distributed system is simply and efficiently deployed, and time and labor cost are saved.
Description
Technical Field
The present application relates to the field of distributed system technologies, and in particular, to a distributed system deployment apparatus and method.
Background
With the wide application of server clusters and the rapid development of the internet, more and more B/S systems in recent years adopt a scheme of distributed or micro-service deployment to publish systems. With the increasing functionality of B/S systems, the number of modules and servers that a system needs to deploy is also increasing, and how to more efficiently and simply deploy the status of the system in project development is also becoming more important.
At present, a manual deployment mode is mostly adopted in the deployment of the distributed B/S system, and a worker needs to deploy a configuration file on each node of the distributed B/S system respectively. The mode has slow labor efficiency and long time consumption, and can not meet the time requirement of deployment gradually, so that the problem restricts the further popularization of the distributed system.
How to provide a method for deploying a distributed system more effectively and concisely is a problem which needs to be solved urgently.
Disclosure of Invention
The embodiment of the application provides distributed system deployment equipment and method, the distributed system can be deployed and manufactured into tasks in a task customization mode, then the tasks are called through the system, the distributed system is deployed simply and efficiently, and time and labor cost are saved.
In a first aspect, an embodiment of the present application provides a distributed system deployed device, including a processor, a memory, and a communication component:
the memory is used for storing data used by the distributed system deployment;
the processor is used for receiving configuration information and configuration files uploaded by the terminal through the communication assembly; the configuration information is set according to the deployment requirement of the target distributed system; the configuration information comprises information of candidate target nodes of the target distributed system to be deployed; responding to a task creating instruction received by the communication component, and creating a deployment task for deploying the target distributed system to a target node according to the configuration information and the configuration file; the target nodes are part or all of the candidate target nodes; and in response to an execution command for the deployment task received through the communication component, deploying the configuration file in the deployment task to the target node.
The distributed system deployment equipment provided by the embodiment of the application can receive configuration information and configuration files uploaded by a terminal through the communication component; responding to a task creating instruction received by the communication component, and creating a deployment task for deploying the target distributed system to a target node according to the configuration information and the configuration file; and in response to an execution command for the deployment task received through the communication component, deploying the configuration file in the deployment task to the target node. The distributed system deployment equipment firstly deploys the distributed system into tasks in a task customization mode, and then the tasks are called through the system, so that the distributed system is simply and efficiently deployed, and time and labor cost are saved.
In one possible implementation, the processor is specifically configured to:
receiving configuration information uploaded by the terminal; receiving a configuration file uploaded by the terminal; and establishing and storing the association relationship between the configuration file and the configuration information.
The distributed system deployed device provided in this embodiment receives the configuration information uploaded by the terminal, then receives the configuration file uploaded by the terminal, establishes an association relationship between the configuration file and the configuration information, and stores the association relationship in the memory. The equipment can enable the configuration file and the configuration information to establish an incidence relation in advance and store the incidence relation, the distributed system is deployed and manufactured into a task through a task customizing mode on the basis, then the task is called through the system, the distributed system is deployed simply and efficiently, and time and labor cost are saved.
In a possible implementation manner, the configuration information further includes version information of the target distributed system and service information of a configuration file corresponding to the target distributed system; the processor is specifically configured to:
and establishing and storing the association relationship between the version information and the configuration file according to the version information and the service information.
In the device deployed in the distributed system, the configuration information further includes version information of the target distributed system and service information of a configuration file corresponding to the target distributed system, and the processor establishes and stores an association relationship between the version information and the configuration file according to the version information and the service information. The device introduces the version information, so that the memory of the device deployed by the distributed system can simultaneously store a plurality of versions and the service information corresponding to each version, and the deployed distributed system can be efficiently managed according to the versions.
In one possible implementation, the processor is specifically configured to:
receiving a task creating instruction; responding to the task creating instruction, and providing information to be selected of task parameters to the terminal equipment according to the configuration information and the configuration file; receiving the task parameters and the task identification information uploaded by the terminal equipment; the task parameters comprise part or all of the following: target node information, deployment version information, deployment service information and a start sequence of deployment service; and if the task parameters are checked to be free of conflict, the task parameters and the task identification information are stored in a correlation mode, and the deployment task for deploying the target distributed system in the target node is obtained.
The device for distributed system deployment provided in this embodiment receives a task creation instruction, sets task parameters according to the configuration information and the configuration file, and stores the task parameters if it is checked that the task parameters are not in conflict, to obtain a deployment task of the target distributed system. The equipment sets the task parameters according to the task creating instruction to obtain the deployment task of the target distributed system, so that the deployment of the distributed system can be completed through the system calling task, the distributed system can be deployed simply and efficiently, and time and labor cost are saved.
In one possible implementation, the processor is specifically configured to:
receiving an execution command of the deployment task; adding the target node to a target node list according to the target node information; adding services according to the deployment service information to obtain a service list of the deployment task; and running the deployment task according to the target node list, the starting sequence of the deployment service and the service list, and deploying the configuration file to the target node.
The distributed system deployment device provided by the embodiment receives an execution command of a deployment task; adding a target node into a target node list according to the target node information; adding services according to the deployment service information to obtain a service list of deployment tasks; and running a deployment task according to the target node list, the starting sequence of the deployment service and the service list, and deploying the configuration file to the target node. The equipment executes the deployment task after receiving the execution command of the deployment task, deploys the configuration file to the target node, realizes the concise and efficient deployment of the distributed system, and saves time and labor cost.
In a second aspect, an embodiment of the present application provides a deployment method of a distributed system, including:
receiving configuration information and configuration files uploaded by a terminal; the configuration information is set according to the deployment requirement of the target distributed system; the configuration information comprises information of candidate target nodes of the target distributed system to be deployed;
responding to a received task creating instruction, and creating a deployment task for deploying the target distributed system to a target node according to the configuration information and the configuration file; the target nodes are part or all of the candidate target nodes;
and in response to the received execution command for the deployment task, deploying the configuration file in the deployment task to the target node.
In a possible implementation manner, the receiving the configuration information and the configuration file uploaded by the terminal includes:
receiving configuration information set according to the deployment requirement of the target distributed system;
receiving a configuration file uploaded according to the deployment requirement of the target distributed system;
and establishing and storing the association relationship between the configuration file and the configuration information.
In a possible implementation manner, the configuration information further includes version information of the target distributed system and service information of a configuration file corresponding to the target distributed system;
the establishing and storing the association relationship between the configuration file and the configuration information includes:
and establishing and storing the association relationship between the version information and the configuration file according to the version information and the service information.
In a possible implementation manner, the creating, in response to the received task creating instruction, a deployment task for deploying the target distributed system to the target node according to the configuration information and the configuration file includes:
receiving a task creating instruction;
responding to the task creating instruction, and providing information to be selected of task parameters to the terminal equipment according to the configuration information and the configuration file;
receiving the task parameters and the task identification information uploaded by the terminal equipment; the task parameters comprise part or all of the following: target node information, deployment version information, deployment service information and a start sequence of deployment service;
and if the task parameters are checked to be free of conflict, the task parameters and the task identification information are stored in a correlation mode, and a deployment task of the target distributed system is obtained.
In one possible implementation, the deploying the configuration file to the target node in response to the received execution command of the deployment task includes:
receiving an execution command of the deployment task;
adding the target node to a target node list according to the target node information;
adding services according to the deployment service information to obtain a service list of the deployment task;
and running the deployment task according to the target node list, the starting sequence of the deployment service and the service list, and deploying the configuration file to the target node.
The technical effect brought by any implementation manner of the second aspect may be referred to the technical effect brought by the implementation manner of the first aspect, and is not described herein again.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.
Fig. 1 is a schematic view of an application scenario according to an embodiment of the present application;
fig. 2 is a block diagram of a hardware configuration of a distributed system deployment device according to an embodiment of the present application;
fig. 3 is a schematic diagram of a server management function of a distributed system deployment device according to an embodiment of the present application;
fig. 4 is a schematic view of a version management function of a distributed system deployment device according to an embodiment of the present application;
fig. 5 is a schematic diagram of a service management function of a distributed system deployment device according to an embodiment of the present application;
fig. 6 is a schematic diagram of task management functions of a distributed system deployment device according to an embodiment of the present application;
fig. 7 is a schematic flowchart of a method for deploying a distributed system according to an embodiment of the present application;
fig. 8 is an interaction diagram of another distributed system deployment method according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application clearer, the present application will be described in further detail with reference to the accompanying drawings, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all 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 application.
Some terms in the embodiments of the present application are explained below to facilitate understanding by those skilled in the art.
(1) The terminal equipment: the term "terminal device" in this embodiment of the present application refers to a device that can install various types of application programs, including an application carried by the terminal device and a third-party application, and can display an object provided in the installed application program, where the terminal device may be mobile or fixed. For example, a mobile phone, a tablet computer, a Personal Digital Assistant (PDA), or other terminal equipment capable of implementing the above functions.
(2) Distributed system: a distributed system is a software system built on top of a network. It is the nature of software that the distributed system is highly cohesive and transparent. The distinction between a network and a distributed system is not hardware, but rather is high-level software, particularly the operating system. In a distributed system, a set of independent computers appear to the user as a unified whole, as if it were a system. The system has various general physical and logical resources, can dynamically allocate tasks, and realizes information exchange by the dispersed physical and logical resources through a computer network. There is a distributed operating system in the system that manages computer resources in a global manner. Typically, a distributed system has only one model or paradigm for a user. Above the operating system there is a layer of software middleware (middleware) responsible for implementing this model. A well-known example of a distributed system is the World Wide Web (World Wide Web) where everything looks like a document (Web page).
(3) Micro-service: is an architectural approach for building applications. The micro-service architecture is different from the traditional monolithic scheme, and can split the application into a plurality of core functions. Each function is called a service and can be built and deployed individually, meaning that services do not affect each other when working or failing.
(4) B/S system (Browser/Server, Browser/Server mode): the B/S system is a network structure mode after WEB is started, and a WEB browser is the most main application software of a client. The mode unifies the client, centralizes the core part of the system function realization to the server, and simplifies the development, maintenance and use of the system. B/S systems generally expand the functionality of the system by adding web pages, with somewhat less stability, zero maintenance: and updating the page, namely updating facing all users.
In the deployment of the distributed B/S system, the number of modules and the number of servers to be deployed are continuously increased, and in the existing deployment process of the distributed B/S system, a manual deployment mode is mostly adopted, and the mode can not meet the time requirement of deployment gradually due to slow manual efficiency and long time consumption, so that the further popularization of the distributed system is restricted by the problems. Based on this, the embodiments of the present application provide a distributed system deployment apparatus and method, which may first deploy a distributed system as a task in a task customization manner, and then deploy the distributed system simply and efficiently by invoking the task through the system, thereby saving time and labor cost.
The distributed system deployment device in the embodiment of the present application refers to a terminal device in which a distributed system deployment application program is installed. The terminal device may be mobile or stationary. For example, a mobile phone, a tablet computer, a Personal Digital Assistant (PDA), a desktop computer, or other terminal devices capable of implementing the above functions.
In order to make the objects, technical solutions and advantages of the embodiments of the present application more apparent, the present application will be further described in detail with reference to the accompanying drawings, and it is to be understood that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments of the present application. 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 application.
The following embodiments of the present application are provided to more clearly illustrate the technical solutions of the embodiments of the present application, and do not limit the technical solutions provided in the embodiments of the present application, and it is obvious to a person skilled in the art that the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems with the occurrence of new application scenarios.
Fig. 1 shows an application scenario of the embodiment of the present application, and referring to fig. 1, the application scenario includes a terminal device 100, a distributed system deployment device 200, and a plurality of target servers 300 to be installed with a target distributed system. The terminal device 100, the distributed system deployment device 200 and the plurality of target servers 300 are in the same local area network, and the local area network can be a wired network or a wireless network.
The user can install the target distributed system to the plurality of target servers 300 on which the target distributed system is to be installed through the distributed system deploying apparatus 200 by operating on the terminal apparatus 100. The terminal device 100 can communicate with the distributed system deployment device 200. A user may set configuration information used for deploying a target distributed system through the terminal device 100, or may upload at least one configuration file used for deploying the target distributed system through the terminal device 100, and send the configuration information and the configuration file to the distributed system deployment device 200 through the terminal device 100. The distributed system deployment device 200 receives the configuration information and the configuration file uploaded by the terminal device 100 through the communication component 206, and stores the acquired configuration information and configuration file. The user can also set task parameters for deploying the target distributed system through the terminal device 100 and send the task parameters to the distributed system deployment device 200. The distributed system deployment device 200 forms an executable task of deploying the target distributed system by combining the task parameters, the configuration information and the configuration file in response to the task creation instruction received through the communication component. The distributed system deployment device 200 may respond to an execution command for a task of the deployment target distributed system, invoke the task of the deployment target distributed system, and deploy the target distributed system to the plurality of target servers 300 according to the configuration information and the configuration file corresponding to the target distributed system.
The distributed system deployment apparatus 200 and the target server 300 may be portable devices (e.g., tablet, notebook, etc.) or Personal Computers (PCs).
According to implementation needs, the application scenario in the embodiment of the present application may have any number of terminal devices, distributed system deployment devices, local area networks, and target servers. For example, the distributed system deployment apparatus 200 may be a server group composed of a plurality of distributed system deployment apparatuses.
A hardware configuration block diagram of a distributed system deployment apparatus 200 in an embodiment is illustrated in fig. 2. As shown in fig. 2, the distributed system deployment apparatus 200 is in the form of a general purpose computing apparatus. The components of distributed system deployment device 200 may include, but are not limited to: at least one processor 201, at least one memory 202, a bus 203 connecting different system components (including the memory 202 and the processor 201), a communication component 206.
Bus 203 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, a processor, or a local bus using any of a variety of bus architectures.
The memory 202, which is used for storing data or program code used when the distributed system deployment apparatus operates, may include readable media in the form of volatile memory, such as Random Access Memory (RAM)2021 and/or cache memory 2022, and may further include Read Only Memory (ROM) 2023.
A processor 201 for: receiving configuration information and configuration files uploaded by the terminal through the communication component 206; the configuration information is set according to the deployment requirement of the target distributed system; the configuration information comprises candidate target node information, and the candidate target node information is information of candidate target nodes of the target distributed system to be deployed; in response to the task creation instruction received through the communication component 206, a deployment task for deploying the target distributed system to the target node is created according to the configuration information and the configuration file; the target nodes are part or all of the candidate target nodes; the configuration file in the deployment task is deployed to the target node in response to an execution command for the deployment task received through the communication component 206.
In the embodiments of the present application, all the target nodes are taken as all the candidate target nodes for illustration.
In some embodiments, the target distributed system may be a microservice system. The target node may be a target server, the target server being a server on which the target distributed system is to be installed.
Illustratively, the target distributed system to be deployed is a micro service system a, the candidate target nodes to be deployed for the micro service system a are (target server host 1, target server host2, target server host3, …, target server host n), and the configuration file is a package set corresponding to a certain version a001 of the micro service system a, where the package set may be a package or a group of packages (a001, a002, a003, …, a00m) belonging to the version a001 of the micro service system a. The distributed system deployment device 200 receives configuration information and a configuration file uploaded by a user through the terminal device 100 through the communication component 206, wherein the configuration information is set according to a deployment requirement of a target distributed system, the configuration information includes information of candidate target nodes of the target distributed system to be deployed, and the information of the candidate target nodes is used for indicating candidate target nodes of the micro service system a to be deployed. The target nodes may be all nodes selected from the candidate target nodes.
In an embodiment of the present application, the information of the candidate target node is information of a candidate target node of a target distributed system to be deployed, and includes the following part or all of: server name, server address, SSH port, system type, username, password.
Illustratively, the information of the candidate target node may be an identification of the target server, for example, the information of the candidate target node is: target server host 1, target server host2, target servers host3, …, target server host n. The target servers host 1 to host n are identifiers of the target servers, such as server names or server addresses. The information of the candidate target nodes indicates that the candidate target nodes to be deployed with the micro service system A comprise: target server host 1, target server host2, target servers host3, …, target server host n.
The processor 201 of the distributed system deployment device 200 responds to a task creation instruction received through the communication component 206 and sent by the user through the terminal device 100, and creates a deployment task for deploying the target distributed system to the target node according to the configuration information and the configuration file; the target nodes are part or all of the candidate target nodes; the processor 201 of the distributed system deployment apparatus 200, in response to an execution command of a deployment task for the version a001 of the micro service system a received through the communication component 206, deploys a package set corresponding to the version a001 of the micro service system a to a target node, which may be (target server host 1, target server host2, target server host3, …, target server host n), which is all exemplified in the present embodiment that the target node is a candidate target node. By setting the information of the candidate target nodes in the configuration information, a user can define the candidate target nodes to which the target distributed system is to be deployed. The candidate target node may be a server that needs to be guaranteed to establish an information connection with the distributed system deployment apparatus 200.
In some embodiments, after receiving the configuration information and the configuration file uploaded by the terminal device 100 through the communication component 206, the processor 201 establishes an association relationship between the configuration file and the configuration information and stores the association relationship. The configuration file is set according to the deployment requirement of the target distributed system, and the configuration information is uploaded according to the deployment requirement of the target distributed system. A user may log in a user interface of the distributed system deployment device 200 through the terminal device 100, set configuration information including candidate target node information, version information, and service information according to a candidate target node to be deployed with the micro service system a, a version of the micro service system a to be deployed, and a package of a package set corresponding to the version of the micro service system a to be deployed, and may select a configuration file to upload according to the package of the package set corresponding to the version of the micro service system a to be deployed. In the service information, the configuration file and the configuration file are associated and stored in the memory 202. By establishing the association relationship, the configuration file and the version information can be associated, which is beneficial for the distributed system deployment device 200 to accurately call the program package corresponding to the installation version.
In some embodiments, the configuration information may include information of a candidate target node of the target distributed system to be deployed, for example, information including "the candidate target node of the micro service system a to be deployed is (server host 1, server host2, server host3, …, server host n)", and the configuration information may also include version information of the target distributed system to be deployed, for example, a version number is one version a001 of the micro service system a. The version information includes version number, version name, version log, version configuration, and the like. In some embodiments, the configuration information may further include service information of a package set corresponding to a target version of the distributed system to be deployed, for example, service information of a package set corresponding to one version a001 of the microservice system a. The micro-service system can be divided into a plurality of core functions, each core function is a service and can be independently constructed and deployed, and the services cannot be mutually influenced when working or having faults. In an embodiment of the application, each service of the microservice corresponds to one package in a package set corresponding to a target version of the microservice to be deployed. The service information is related information of a package set corresponding to a target version of the distributed system to be deployed, and includes a service name, a service description, a service type (front-end rar, back-end jar package, docker image file …), a service body file (rar/jar/tar, etc.), a service configuration file, a server boot script, a service version number, and the like.
In addition to the configuration information, the processor 201 of the distributed system deployment apparatus 200 also receives the configuration file uploaded by the user through the terminal apparatus 100 through the communication component 206, establishes an association relationship between the configuration file and the configuration information, and stores the association relationship. The configuration file comprises a program package of a program package set corresponding to a target version of the distributed system to be deployed. After receiving the configuration file through the communication component 206, the processor 201 of the distributed system deployment apparatus 200 establishes an association relationship between the configuration file and the configuration information and stores the association relationship in the memory 202.
In some embodiments, the configuration information further includes version information of the target distributed system and service information of a configuration file corresponding to the target distributed system; the processor 201 may establish and store an association relationship between the version information and the configuration file according to the version information and the service information.
The configuration file may be a package of a package set corresponding to a target version of the distributed system to be deployed. Illustratively, the distributed system may be a microservice. Each package may correspond to a service of the microservice. The program package can be a rar compression package or a jar package, a tar package or a docker image file, a docker file or other third-party components and the like. While uploading the program package, the user needs to fill in relevant information of the program package set corresponding to the target version of the distributed system to be deployed, including a service name, a service description, a service type (front end rar, back end jar package, docker image file …), a service subject file (rar/jar/tar, etc.), a service configuration file, a server start script, a service version number, etc.
In some embodiments of the present application, the candidate target node information, version information, service information, and configuration file in the foregoing embodiments may also be adjusted or viewed through the distributed system deployment apparatus 200.
In certain embodiments, the processor 201 is further configured to: modifying or deleting the candidate target node information in response to the candidate target node information adjustment command received via the communication component 206; modifying or deleting version information in response to a version information adjustment command received via the communication component 206; the service information and configuration files are modified or deleted in response to service adjustment commands received through the communication component 206.
In certain embodiments, the processor 201 is further configured to: in response to a candidate target node information viewing command received via the communication component 206, returning and displaying candidate target node information; in response to the version information viewing command received via the communication component 206, returning and displaying the version information; service information and configuration files are returned and displayed in response to service viewing commands received through the messaging component 206.
In some embodiments, the candidate target node is a target server.
As shown in fig. 3, in some embodiments, the distributed system deployment apparatus 200 may perform server management on a target server to be deployed with the microservice system a, including: adding a server, checking the server, editing the server and deleting the server. When a server is newly added, the distributed system deployment apparatus 200 receives attributes such as a name, an address, and the like of the server configured by the user through the communication component 206. When viewing the servers, the distributed system deployment device 200 lists all the servers, and the user can further select the server to be viewed from the list through the terminal device 100, and view the specific attributes of the individual servers. The distributed system deployment device 200 may also edit or delete the viewed servers. When deleting a server, the distributed system deployment device 200 selects a server to be deleted first, then determines whether the selected server is in use, and if a task is using the server, deletes the task first until no task is using the server, and then deletes the selected server to be deleted.
As shown in fig. 4, in some embodiments, the distributed system deployment apparatus 200 may perform version management on a version of the micro service system a to be deployed, including: adding a new version, checking the version, editing the version and deleting the version. When a new version is added, the distributed system deployment device 200 receives attributes such as a version name, a version number, and a version log configured by a user through the communication component 206. When viewing versions, the distributed system deployment device 200 lists all versions to view, and the user may further select a version to be viewed from the list through the terminal device 100 to view specific parameters of a single version. The distributed system deployment device 200 may also edit or delete the viewed version. When deleting the version, the distributed system deployment device 200 selects the version to be deleted first, then judges whether the selected version is used, if any task uses the version, deletes the task first until no task uses the version, and then deletes the selected version to be deleted.
As shown in fig. 5, in some embodiments, the distributed system deployment apparatus 200 may perform service management on a service to be deployed with the microservice system a, including: adding a service, checking the service, modifying the service and deleting the service. When a new service is added, the distributed system deployment device 200 may first receive the service type of the new service set by the user through the communication component 206, then receive the service version number of the new service set by the user through the communication component 206, and then receive the service attributes, such as name, description, and the like, of the new service set by the user; after the setting information is received, the distributed system deployment device 200 receives service-related files uploaded by the user according to the service types, including configuration files, start scripts and the like, through the communication component 206; next, the distributed system deployment device 200 acquires a port according to the configuration file, performs port conflict check, and saves service if the check result is no conflict. When modifying a service, the distributed system deployment apparatus 200 may modify the service version number, the service attribute, the configuration file, and the start script in sequence, corresponding to the newly added service. When viewing the services, the distributed system deploys the device list to view all the services, and the user can further select the service to be viewed from the list through the terminal device 100 to view the specific parameters of a single service. The distributed system deployment apparatus 200 may also delete the service. When deleting a service, the distributed system deployment device 200 selects a service to be deleted, then determines whether the selected service is in use, and if a task is using the service, deletes the task first until no task is using the service, and then deletes the selected service to be deleted.
In some embodiments, the processor 201 is specifically configured to: receiving a task creation instruction via the communication component 206; responding to the task creating instruction, and providing information to be selected of task parameters for the terminal equipment according to the configuration information and the configuration file; receiving task parameters and task identification information uploaded by terminal equipment; the task parameters include some or all of the following: target node information, deployment version information, deployment service information and a start sequence of deployment service; and if the task parameters are checked to be free of conflict, the task parameters and the task identification information are stored in an associated mode, and a deployment task for deploying the target distributed system on the target node is obtained.
As shown in FIG. 6, in some embodiments, the distributed system deployment apparatus 200 may perform task management on tasks to be deployed with the microservice system A, including: the method comprises the steps of task adding, task checking, task modifying, task deleting, service checking and task starting. The task addition is performed after the configuration information and the configuration file are uploaded. Illustratively, when a task is newly added, the processor receives a task creation instruction for the micro service system a to be deployed through the communication component 206; in response to a task creation instruction of the deployed micro service system A received through the communication component 206, providing candidate information of task parameters to the terminal device according to the configuration information and the configuration file; receiving task parameters and task identification information uploaded by terminal equipment; the task parameters include some or all of the following: target node information, deployment version information, deployment service information and a start sequence of deployment service; and if the task parameters are checked to be free of conflict, the task parameters and the task identification information are stored in the memory 202 in a correlation mode, and a deployment task for deploying the target distributed system in the target node is obtained.
For example, when the task parameters are checked, the port information of the candidate target nodes (server host 1, server host2, server host3, …, server host n) of the micro service system a to be deployed may be obtained, and the port conflict check may be performed. Or checking the service information of the packages of the package set corresponding to the version A001 of the micro service system A to be deployed one by one, acquiring the ports of the target nodes corresponding to the packages of the version A001, and checking whether a port conflict exists. And if the conflict exists in the task parameters, the received task parameters and the task identification information cannot be stored in an associated manner. In some embodiments, when it is checked that there is a conflict to the task parameter, the distributed system deployment apparatus 200 sends a notification that the task creation is wrong to the terminal apparatus. For example, the user may be informed of "there is a conflict in task parameters, please reset task parameters" by a prompt message.
In some embodiments, the processor 201 is specifically configured to: receiving an execution command of a deployment task; adding a target node into a target node list according to the target node information; adding services according to the deployment service information to obtain a service list of deployment tasks; and running a deployment task according to the target node list, the starting sequence of the deployment service and the service list, and deploying the configuration file to the target node.
Illustratively, the distributed system deployment apparatus 200 receives an execution command of a deployment task through the communication component 206; adding target nodes (server host 1, server host2, server host3, …, server host n) to a target node list according to the target node information; adding services according to the deployment service information to obtain a service list of deployment tasks; and running a deployment task according to the target node list, the starting sequence of the deployment service and the service list, and deploying the configuration file to the target node (the server host 1, the server host2, the server host3, … and the server host n), so that the task starting shown in FIG. 6 is completed.
The distributed system deployment apparatus 200 may also communicate with one or more external devices 204 (e.g., keyboard, pointing device, etc.), with one or more devices that enable a user to interact with the distributed system deployment apparatus 200, and/or with any devices (e.g., router, modem, etc.) that enable the distributed system deployment apparatus 200 to communicate with one or more other computing devices. Such communication may be through an input/output (I/O) interface 205. Also, distributed system deployment apparatus 200 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the internet) via communications component 206. As shown, the communication component 206 communicates with other modules for the distributed system deployment apparatus 200 over the bus 203. It should be understood that although not shown in the figures, other hardware and/or software modules may be used in conjunction with the distributed system deployment apparatus 200, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.
The distributed system deployment device provided by the embodiment is based on the same inventive concept, and the embodiment of the application also provides a distributed system deployment method. Fig. 7 shows a flowchart of a distributed system deployment method provided in an embodiment of the present application. The present invention is applicable to a distributed system deployment apparatus applicable to the hardware structure shown in fig. 2.
The distributed system deployment method may be executed by a distributed system deployment device, see fig. 7, and may include the following steps:
and step S701, receiving configuration information and configuration files uploaded by the terminal.
The configuration information is set according to the deployment requirement of the target distributed system; the configuration information includes information of a target node of the target distributed system to be deployed.
Step S702, in response to the received task creating instruction, creating a deployment task for deploying the target distributed system to the target node according to the configuration information and the configuration file.
Step S703, in response to the received execution command for the deployment task, deploying the configuration file in the deployment task to the target node.
In the method, the configuration information and the configuration file uploaded from the terminal device 100 are received through the communication component 206; responding to a task creating instruction received through the communication component, and creating a deployment task of the target distributed system according to the configuration information and the configuration file; and in response to an execution command for the deployment task received through the communication component, deploying the configuration file in the deployment task to the target node. According to the method, the distributed system is deployed and manufactured into the tasks in a task customization mode, and then the tasks are called through the system, so that the distributed system is deployed simply and efficiently, and time and labor cost are saved.
In some embodiments, in step S701, the receiving of the configuration information and the configuration file uploaded by the terminal includes:
step S7011, receiving configuration information set according to the deployment requirement of the target distributed system.
Step S7012, receiving the configuration file uploaded according to the deployment requirement of the target distributed system.
Step S7013, the association relationship between the configuration file and the configuration information is established and stored.
In some embodiments, the configuration information further includes version information of the target distributed system and service information of a configuration file corresponding to the target distributed system; step S7013, establishing and storing an association relationship between the configuration file and the configuration information, including:
step S70131, according to the version information and the service information, an association relationship between the version information and the configuration file is established and stored.
Fig. 8 shows an interaction diagram of another distributed system deployment method provided by the embodiment of the present application. The distributed system deployment method may be interactively executed by the distributed system deployment device and the terminal device, referring to fig. 8, and may include the following steps:
step S801, the terminal device sends configuration information and a configuration file to the distributed system deployment device.
Step S803, the distributed system deployment apparatus stores the configuration information and the configuration file.
The configuration information is set according to the deployment requirement of the target distributed system; the configuration information includes information of a target node of the target distributed system to be deployed.
Illustratively, the distributed system to be deployed is microservice system a. The target servers of the micro service system a to be deployed are (server host 1, server host2, server host3, …, server host n), and the version information is version a 001. The configuration file is a package in a package set (a 1, a 2, …, a t, …, a m) corresponding to version A001 of the micro service system A.
In step S803, the terminal device receives a task creation instruction input by the user.
The distributed system deployment apparatus 200 receives a task creation instruction issued by the user at the terminal apparatus 100 through the communication component 206.
Step S804, the terminal device sends a task creation instruction to the distributed system deployment device.
Step S805, in response to the received task creating instruction, generates a task parameter setting interface including information to be selected of task parameters according to the configuration information and the configuration file.
The task parameters include some or all of the following: target node information, deployment version information, deployment service information, and a start order of the deployment service.
Illustratively, the distributed system deployment device 200 receives the task creation instruction through the communication component 206, and generates a task parameter setting interface containing information to be selected of task parameters according to the configuration information and the configuration file. For example, the distributed system deployment device 200 generates a task parameter setting interface including information to be selected of task parameters according to the configuration information and the configuration file, and when a user sets target node information in the task parameters through the terminal device 100, the user may select a part of servers or all servers in (server host 1, server host2, server host3, …, server host n) from the information to be selected of the task parameters included in the task parameter setting interface as target nodes for deploying the micro service system a. For another example, when the user sets the deployment version information in the task parameter through the terminal device 100, the user may select the version a001 of the micro service system a from the candidate information of the task parameter included in the task parameter setting interface as the value of the deployment version information in the task parameter for creating the task. When a version of a distributed system to be deployed includes a plurality of services, it is necessary to set a starting sequence of deploying the services in task parameters when creating a task. The distributed system deployment equipment 200 determines the starting sequence of the plurality of services included in the version of the distributed system to be deployed according to the starting sequence of the deployment services.
Step S806, the distributed system deployment device sends the task parameter setting interface link to the terminal device.
In step S807, the terminal device displays a task parameter setting interface.
Step S808, the distributed system deployment device sends instruction information prompting the user to set task parameters and task identifier information to the terminal device.
In some embodiments, the distributed system deployment device 200 sends prompt information to the terminal device 100, prompting the user to set task parameters and task identification information.
Step S809, the terminal device displays indication information for prompting the user to set task parameters and task identification information.
Step S810, the terminal device receives the task parameter and the task identification information input by the user.
The user inputs the task parameter and the task identification information through the terminal device 100.
Step S811, the terminal device sends the task parameters and the task identification information to the distributed system deployment device.
Step S812, the distributed system deployment device receives the task parameter and the task identifier information and caches and stores the task parameter and the task identifier information.
In some embodiments, the distributed system deployment apparatus 200 receives and stores the task parameters and the task identification information to a pre-specified cache area.
In step S813, the distributed system deployment apparatus checks whether there is a conflict in the task parameters.
For example, when the distributed system deployment device 200 checks the task parameters, the port information of the target server (server host 1, server host2, server host3, …, server host n) of the micro service system a to be deployed may be obtained, and the port collision check may be performed. Or checking the service information of the packages of the package set corresponding to the version A001 of the micro service system A to be deployed one by one, acquiring the ports of the target nodes corresponding to the packages of the version A001, and checking whether a port conflict exists.
Step S814, if there is no conflict, the distributed system deployment device performs associated storage on the task parameter and the task identifier information to obtain a deployment task of the target distributed system.
Step S815, if there is a conflict, the distributed system deployment device sends instruction information prompting the user to set task parameters and task identifier information to the terminal device.
For example, if it is checked that there is a conflict with the task parameter, the received task parameter and the task identification information cannot be stored in association with each other and saved in the memory 202. In some embodiments, when it is checked that there is a conflict to the task parameter, the distributed system deployment apparatus 200 transmits a task creation failure prompt message to the terminal apparatus. For example, the user may be informed that "there is a conflict in task parameters, please reset task parameters".
In step S816, the terminal device receives the deployment task execution command information input by the user.
In some embodiments, the deployment task execution command information includes a deployment task execution instruction and a deployment task execution time.
Step S817, the terminal device sends deployment task execution command information to the distributed system deployment device.
In step S818, the distributed system deployment device receives the deployment task execution command information.
Step S819, the distributed system deployment device deploys the configuration file in the deployment task to the target node in response to the received deployment task execution command.
In some embodiments, step S819, the distributed system deploying device deploys the configuration file in the deployment task to the target node in response to the received deployment task execution command, including:
step 1, the distributed system deployment equipment receives an execution command of a deployment task.
And 2, adding the target node into a target node list by the distributed system deployment equipment according to the target node information.
And 3, adding services according to the deployment service information to obtain a service list of the deployment task.
And 4, running a deployment task according to the target node list, the starting sequence of the deployment service and the service list, and deploying the configuration file to the target node.
In some embodiments, the above method further comprises:
and 1.1, responding to the received candidate target node information adjusting command, and modifying or deleting the candidate target node information.
And 1.2, responding to the received version information adjusting command, and modifying or deleting the version information.
And step 1.3, responding to the received service adjusting command, and modifying or deleting the service information and the configuration file.
In some embodiments, the above method further comprises:
and 2.1, responding to the received candidate target node information viewing command, and returning and displaying the candidate target node information.
And 2.2, responding to the received version information viewing command, and returning and displaying the version information.
And 2.3, responding to the received service viewing command, and returning and displaying the service information and the configuration file.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.
Claims (10)
1. An apparatus deployed by a distributed system, comprising a processor, a memory, and a communications component:
the memory is used for storing data used by the distributed system deployment;
the processor is used for receiving configuration information and configuration files uploaded by the terminal through the communication assembly; the configuration information is set according to the deployment requirement of the target distributed system; the configuration information comprises information of candidate target nodes of the target distributed system to be deployed; responding to a task creating instruction received by the communication component, and creating a deployment task for deploying the target distributed system to a target node according to the configuration information and the configuration file; the target nodes are part or all of the candidate target nodes; and in response to an execution command for the deployment task received through the communication component, deploying the configuration file in the deployment task to the target node.
2. The device of claim 1, wherein the processor is specifically configured to:
receiving configuration information uploaded by the terminal; receiving a configuration file uploaded by the terminal; and establishing and storing the association relationship between the configuration file and the configuration information.
3. The apparatus of claim 2, wherein the configuration information further includes version information of the target distributed system and service information of a configuration file corresponding to the target distributed system; the processor is specifically configured to:
and establishing and storing the association relationship between the version information and the configuration file according to the version information and the service information.
4. The device of claim 3, wherein the processor is specifically configured to:
receiving a task creating instruction; responding to the task creating instruction, and providing information to be selected of task parameters to the terminal equipment according to the configuration information and the configuration file; receiving the task parameters and the task identification information uploaded by the terminal equipment; the task parameters comprise part or all of the following: target node information, deployment version information, deployment service information and a start sequence of deployment service; and if the task parameters are checked to be free of conflict, the task parameters and the task identification information are stored in a correlation mode, and the deployment task for deploying the target distributed system in the target node is obtained.
5. The device of claim 4, wherein the processor is specifically configured to:
receiving an execution command of the deployment task; adding the target node to a target node list according to the target node information; adding services according to the deployment service information to obtain a service list of the deployment task; and running the deployment task according to the target node list, the starting sequence of the deployment service and the service list, and deploying the configuration file to the target node.
6. A deployment method of a distributed system, comprising:
receiving configuration information and configuration files uploaded by a terminal; the configuration information is set according to the deployment requirement of the target distributed system; the configuration information comprises information of candidate target nodes of the target distributed system to be deployed;
responding to a received task creating instruction, and creating a deployment task for deploying the target distributed system to a target node according to the configuration information and the configuration file; the target nodes are part or all of the candidate target nodes;
and in response to the received execution command for the deployment task, deploying the configuration file in the deployment task to the target node.
7. The method according to claim 6, wherein the receiving the configuration information and the configuration file uploaded by the terminal comprises:
receiving configuration information set according to the deployment requirement of the target distributed system;
receiving a configuration file uploaded according to the deployment requirement of the target distributed system;
and establishing and storing the association relationship between the configuration file and the configuration information.
8. The method of claim 7, wherein the configuration information further includes version information of the target distributed system and service information of a configuration file corresponding to the target distributed system;
the establishing and storing the association relationship between the configuration file and the configuration information includes:
and establishing and storing the association relationship between the version information and the configuration file according to the version information and the service information.
9. The method of claim 8, wherein the creating a deployment task for deploying the target distributed system to a target node according to the configuration information and the configuration file in response to the received task creation instruction comprises:
receiving a task creating instruction;
responding to the task creating instruction, and providing information to be selected of task parameters to the terminal equipment according to the configuration information and the configuration file;
receiving the task parameters and the task identification information uploaded by the terminal equipment; the task parameters comprise part or all of the following: target node information, deployment version information, deployment service information and a start sequence of deployment service;
and if the task parameters are checked to be free of conflict, the task parameters and the task identification information are stored in a correlation mode, and the deployment task for deploying the target distributed system in the target node is obtained.
10. The method of claim 9, wherein deploying the configuration file to the target node in response to receiving the command to execute the deployment task comprises:
receiving an execution command of the deployment task;
adding the target node to a target node list according to the target node information;
adding services according to the deployment service information to obtain a service list of the deployment task;
and running the deployment task according to the target node list, the starting sequence of the deployment service and the service list, and deploying the configuration file to the target node.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010921043.9A CN112114939A (en) | 2020-09-04 | 2020-09-04 | Distributed system deployment equipment and method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010921043.9A CN112114939A (en) | 2020-09-04 | 2020-09-04 | Distributed system deployment equipment and method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112114939A true CN112114939A (en) | 2020-12-22 |
Family
ID=73802771
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010921043.9A Pending CN112114939A (en) | 2020-09-04 | 2020-09-04 | Distributed system deployment equipment and method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112114939A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112783514A (en) * | 2020-12-31 | 2021-05-11 | 罗普特科技集团股份有限公司 | Method and system for deployment management of web front-end project |
| CN114363332A (en) * | 2021-12-27 | 2022-04-15 | 徐工汉云技术股份有限公司 | Distributed-based gateway remote automatic operation and maintenance method |
| CN115514666A (en) * | 2022-09-26 | 2022-12-23 | 郑州小鸟信息科技有限公司 | Visual deployment method and system |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101809563A (en) * | 2007-09-26 | 2010-08-18 | 微软公司 | The establishment and the deployment of distributed, extensible application |
| CN102394939A (en) * | 2011-11-21 | 2012-03-28 | 苏州阔地网络科技有限公司 | Deployment method and systems of distributed system |
| CN106610836A (en) * | 2016-12-23 | 2017-05-03 | 国网信息通信产业集团有限公司 | Micro-service operation management tool |
| CN108322490A (en) * | 2017-01-17 | 2018-07-24 | 阿里巴巴集团控股有限公司 | The method, apparatus and server of virtual machine configuration and the distributed cloud service system of deployment |
| CN108804121A (en) * | 2018-05-28 | 2018-11-13 | 泰康保险集团股份有限公司 | Method for edition management, device, medium in distributed system and electronic equipment |
| CN110224869A (en) * | 2019-06-13 | 2019-09-10 | 北京航空航天大学 | A kind of Automation arranging method of micro services website |
| CN110597520A (en) * | 2019-08-27 | 2019-12-20 | 深圳证券交易所 | Server, deployment method thereof and computer-readable storage medium |
-
2020
- 2020-09-04 CN CN202010921043.9A patent/CN112114939A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101809563A (en) * | 2007-09-26 | 2010-08-18 | 微软公司 | The establishment and the deployment of distributed, extensible application |
| CN102394939A (en) * | 2011-11-21 | 2012-03-28 | 苏州阔地网络科技有限公司 | Deployment method and systems of distributed system |
| CN106610836A (en) * | 2016-12-23 | 2017-05-03 | 国网信息通信产业集团有限公司 | Micro-service operation management tool |
| CN108322490A (en) * | 2017-01-17 | 2018-07-24 | 阿里巴巴集团控股有限公司 | The method, apparatus and server of virtual machine configuration and the distributed cloud service system of deployment |
| CN108804121A (en) * | 2018-05-28 | 2018-11-13 | 泰康保险集团股份有限公司 | Method for edition management, device, medium in distributed system and electronic equipment |
| CN110224869A (en) * | 2019-06-13 | 2019-09-10 | 北京航空航天大学 | A kind of Automation arranging method of micro services website |
| CN110597520A (en) * | 2019-08-27 | 2019-12-20 | 深圳证券交易所 | Server, deployment method thereof and computer-readable storage medium |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112783514A (en) * | 2020-12-31 | 2021-05-11 | 罗普特科技集团股份有限公司 | Method and system for deployment management of web front-end project |
| CN112783514B (en) * | 2020-12-31 | 2022-06-14 | 罗普特科技集团股份有限公司 | Method and system for deployment management of web front-end project |
| CN114363332A (en) * | 2021-12-27 | 2022-04-15 | 徐工汉云技术股份有限公司 | Distributed-based gateway remote automatic operation and maintenance method |
| CN114363332B (en) * | 2021-12-27 | 2024-01-23 | 徐工汉云技术股份有限公司 | Remote automatic operation and maintenance method based on distributed gateway |
| CN115514666A (en) * | 2022-09-26 | 2022-12-23 | 郑州小鸟信息科技有限公司 | Visual deployment method and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110389900B (en) | Distributed database cluster testing method and device and storage medium | |
| US11586461B2 (en) | Service creation and management | |
| CN108809722B (en) | Method, device and storage medium for deploying Kubernetes cluster | |
| CN112114939A (en) | Distributed system deployment equipment and method | |
| US20170161059A1 (en) | Management of multiple application programming interface versions for development environments | |
| CN108737168B (en) | Container-based micro-service architecture application automatic construction method | |
| CN102355500B (en) | Service push method and device | |
| US20210075683A1 (en) | Policy management method and system, and apparatus | |
| CN111614490B (en) | Management system and method for managed container cluster based on top-level container cluster | |
| US20170337077A1 (en) | End-to-End Validation of Virtual Machines | |
| CN111930521A (en) | Method and device for deploying application, electronic equipment and readable storage medium | |
| CN107741852B (en) | Service deployment method based on cluster software | |
| CN102427481A (en) | System for managing cloud computing service and cloud computing management method | |
| US10817267B2 (en) | State machine representation of a development environment deployment process | |
| CN112867988A (en) | Implementing compliance settings by a mobile device to follow a configuration scenario | |
| US8438573B2 (en) | Dependency on a resource type | |
| JP7161560B2 (en) | Artificial intelligence development platform management method, device, medium | |
| WO2024077885A1 (en) | Management method, apparatus and device for container cluster, and non-volatile readable storage medium | |
| US20230342183A1 (en) | Management method and apparatus for container cluster | |
| CN111796838A (en) | MPP database automatic deployment method and device | |
| US10120707B2 (en) | Deployment of development environments | |
| CN114185734A (en) | Cluster monitoring method and device and electronic equipment | |
| CN112306640A (en) | Container dispensing method, apparatus, device and medium therefor | |
| CN106550002B (en) | paas cloud hosting system and method | |
| CN112564979B (en) | Execution method and device of construction task, computer 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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20201222 |
|
| RJ01 | Rejection of invention patent application after publication |