CN117407008A - System component cluster deployment method and device for microminiature data center - Google Patents
System component cluster deployment method and device for microminiature data center Download PDFInfo
- Publication number
- CN117407008A CN117407008A CN202311722141.XA CN202311722141A CN117407008A CN 117407008 A CN117407008 A CN 117407008A CN 202311722141 A CN202311722141 A CN 202311722141A CN 117407008 A CN117407008 A CN 117407008A
- Authority
- CN
- China
- Prior art keywords
- deployment
- installation
- system component
- workflow
- component
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 34
- 239000000463 material Substances 0.000 claims abstract description 251
- 238000009434 installation Methods 0.000 claims abstract description 181
- 238000013515 script Methods 0.000 claims abstract description 49
- 238000010276 construction Methods 0.000 claims abstract description 18
- 238000012545 processing Methods 0.000 claims abstract description 17
- 238000011900 installation process Methods 0.000 claims description 10
- 241000380131 Ammophila arenaria Species 0.000 claims description 5
- 230000007246 mechanism Effects 0.000 claims description 5
- 238000004806 packaging method and process Methods 0.000 claims description 5
- 238000009877 rendering Methods 0.000 claims description 5
- 230000005540 biological transmission Effects 0.000 claims description 3
- 230000006837 decompression Effects 0.000 claims description 3
- 230000001502 supplementing effect Effects 0.000 claims description 3
- 239000004566 building material Substances 0.000 claims 1
- 238000004590 computer program Methods 0.000 description 15
- 238000010586 diagram Methods 0.000 description 8
- 230000000694 effects Effects 0.000 description 6
- 230000001419 dependent effect Effects 0.000 description 5
- 230000010354 integration Effects 0.000 description 5
- 230000006870 function Effects 0.000 description 4
- 230000008859 change Effects 0.000 description 3
- 238000007781 pre-processing Methods 0.000 description 3
- 238000002360 preparation method Methods 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 230000009471 action Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000008520 organization Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- OKTJSMMVPCPJKN-UHFFFAOYSA-N Carbon Chemical compound [C] OKTJSMMVPCPJKN-UHFFFAOYSA-N 0.000 description 1
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000005856 abnormality Effects 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000006835 compression Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 229910021389 graphene Inorganic materials 0.000 description 1
- 238000003384 imaging method Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/211—Schema design and management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- Stored Programmes (AREA)
Abstract
The application provides a system component cluster deployment method and device for a microminiature data center, comprising the steps of acquiring materials of corresponding system components and deploying the materials based on preset material deployment specifications; customizing and cutting the deployed materials to obtain a system component deployment material delivery package; and processing the material delivery package deployed by the system component to obtain a workflow load file which is depended by the workflow engine, editing the workflow load file, and controlling the workflow engine to execute the edited workflow load file to complete the installation of the system component. The deployment material construction specification of the microminiature data center system component is provided, so that the system component supports rapid overall deployment, and each functional component of the system is composed of a deployment script and a configuration list. By means of the component deployment workflow engine, the component installation and execution sequence is arranged, batch configuration of the multi-component deployment parameters is carried out, and the component deployment is customized, so that the deployment flow is more flexible, and the components can be cut and customized.
Description
Technical Field
The present invention relates to the field of database installation, and in particular, to a system component cluster deployment method and apparatus for a microminiature data center.
Background
Compared with the traditional data center, the microminiature data center is easier to build and move, so that the microminiature data center is popular with small and medium enterprises. Different microminiature data centers often need to support different complex service scenarios, which leads to heterogeneous deployment of system components each time, and various deployment flows, which also leads to more complex deployment schemes for microminiature data centers. In order to solve the problem of installation and deployment of system components, on one hand, certain specifications of organization forms of component materials are required to be ensured. On the other hand, on the basis of standardized storage of component materials, a workflow engine based on specifications is also required to be constructed, so that automatic execution and installation steps are conveniently realized.
At present, a single component in a microminiature data center has a management format of software packages such as RPM (Red Hat Package Manager) and Deb (Debian) and various installation modes, but lacks a fixed standard organization form, so that the execution sequence of material installation is difficult to arrange, and standardized integration and installation of installed software cannot be achieved.
Disclosure of Invention
Based on the foregoing, it is necessary to provide a deployment method and device for a system component cluster facing to a microminiature data center, which can provide an execution mechanism related to material integration for system component deployment.
In a first aspect, the present application provides a deployment method of a system component cluster facing a micro-miniature data center, where the deployment method of the system component cluster facing the micro-miniature data center includes:
acquiring materials corresponding to the system components, and performing material deployment based on preset material deployment specifications;
customizing and cutting the deployed materials to obtain a system component deployment material delivery package;
and processing the material delivery package deployed by the system component to obtain a workflow load file which is depended by a workflow engine, editing the workflow load file, and controlling the workflow engine to execute the edited workflow load file to complete the installation of the system component.
In one embodiment, the obtaining the material corresponding to the system component, performing material deployment based on a preset material deployment specification, includes:
preparing corresponding materials according to the requirements of system components;
And constructing a material deployment specification, creating a material catalog according to the material deployment specification, and classifying and placing the materials based on the material catalog to complete material deployment.
In one embodiment, the build material deployment specification comprises:
defining specific components of a system deployment material, including a configuration file, an installation script, a helm mechanism package, a mirror image, an rpm package and a deb package;
defining the assembly to organize the current service installation and uninstallation command by using the compiled file;
the configurable parameters defining the components are placed in a single configuration file.
In one embodiment, the custom cutting the deployed material to obtain a system component deployment material delivery package includes:
cutting or supplementing the materials according to the field requirements of the microminiature data center to obtain processed materials;
and packaging the processed materials to obtain a system component deployment material delivery package.
In one embodiment, the processing the material delivery package for system component deployment to obtain a workflow load file relied by a workflow engine, editing the workflow load file, controlling the workflow engine to execute the edited workflow load file to complete system component installation, and the method includes:
Decompressing the system component deployment material delivery package, and combining a pre-constructed deployment workflow engine to combine decompression results according to an execution flow to obtain a workflow load file which is relied by the workflow engine and contains a single installation execution stage and an execution result;
editing the workflow load file based on deployment logic, including expansion and cutting, to obtain an edited workflow load file;
editing a unified configuration file of a system component to be installed, and carrying out batch configuration on the component to be installed;
and controlling the workflow engine to execute the edited workflow load file to complete the installation of the system component.
In one embodiment, the workflow load file includes:
a phase field for indicating the execution result of the current installation;
a stages array for representing installation information of all system components to be installed;
wherein each element in the stages array defines the installation details of a single component.
In one embodiment, the decompressing the system component deployment material delivery package combines the decompressed results according to the execution flow by combining with a pre-built deployment workflow engine to obtain a workflow load file including a single installation execution stage and an execution result, which is relied on by the workflow engine, and the method includes:
Extracting installation dependency information in a manifest. Yaml file of each component, generating a directed acyclic graph of the dependency relationship of the system component installation, performing topological ordering on execution steps in the directed acyclic graph, and determining the execution sequence of the system component installation;
and rendering the execution sequence record information of the system component installation to obtain a workflow load file containing a single installation execution stage and an execution result.
In one embodiment, the editing a unified configuration file of a system component to be installed, and performing batch configuration on the component to be installed includes:
extracting first data for realizing custom data key value pairs of component developers and second data for storing common configuration items on which a plurality of component materials depend from the unified configuration file;
maintaining the first data to finish the value transmission and the value taking of materials of different components;
and editing the second data, and overwriting the values.yaml files under all directory levels.
In one embodiment, the controlling the workflow engine to execute the edited workflow load file completes system component installation, including:
judging whether the workflow load file exists or not, and if so, entering the next step; if not, stopping the installation process;
Loading the workflow load file, analyzing the stages array, and decomposing the specific installation stage information to be executed;
circularly and sequentially executing the installation flow of the single service material;
and judging whether the subsequently executed stage array exists, if so, continuing to execute the loop to sequentially execute the installation flow of the single service material, and if not, recording the current installation state and exiting the installation process.
In a second aspect, the present application further provides a system component cluster deployment apparatus for a micro-miniature data center, where the apparatus includes:
the material deployment module is used for acquiring materials corresponding to the system components and deploying the materials based on a preset material deployment specification;
the delivery package construction module is used for carrying out customized cutting on the deployed materials to obtain a system component deployment material delivery package;
and the system component installation module is used for processing the system component deployment material delivery package to obtain a workflow load file which is depended by a workflow engine, editing the workflow load file, and controlling the workflow engine to execute the edited workflow load file to complete system component installation.
In a third aspect, the present application also provides a computer device. The computer device comprises a memory storing a computer program and a processor which when executing the computer program performs the steps of:
acquiring materials corresponding to the system components, and performing material deployment based on preset material deployment specifications;
customizing and cutting the deployed materials to obtain a system component deployment material delivery package;
and processing the material delivery package deployed by the system component to obtain a workflow load file which is depended by a workflow engine, editing the workflow load file, and controlling the workflow engine to execute the edited workflow load file to complete the installation of the system component.
In a fourth aspect, the present application also provides a computer-readable storage medium. The computer readable storage medium having stored thereon a computer program which when executed by a processor performs the steps of:
acquiring materials corresponding to the system components, and performing material deployment based on preset material deployment specifications;
customizing and cutting the deployed materials to obtain a system component deployment material delivery package;
And processing the material delivery package deployed by the system component to obtain a workflow load file which is depended by a workflow engine, editing the workflow load file, and controlling the workflow engine to execute the edited workflow load file to complete the installation of the system component.
In a fifth aspect, the present application also provides a computer program product. The computer program product comprises a computer program which, when executed by a processor, implements the steps of:
acquiring materials corresponding to the system components, and performing material deployment based on preset material deployment specifications;
customizing and cutting the deployed materials to obtain a system component deployment material delivery package;
and processing the material delivery package deployed by the system component to obtain a workflow load file which is depended by a workflow engine, editing the workflow load file, and controlling the workflow engine to execute the edited workflow load file to complete the installation of the system component.
And the system component deployment material delivery package of different system component combinations is realized through customized packaging, so that customized deployment is performed. The components are installed more flexibly by adjusting the configuration of single component materials such as configuration files, installation scripts and the like. By configuring the public configuration items in the public configuration, unified replacement of public configuration fields of all materials is realized. And through a cutting configuration switch of the material directory, in the construction stage of the workflow load file, adding and deleting the steps of executing the pages in the workflow load file, and achieving the function of customizing cutting deployment software in field deployment.
Drawings
FIG. 1 is a flow chart of a system component cluster deployment method for a micro-miniature data center in one embodiment;
FIG. 2 is a diagram of a system component deployment engineering catalog architecture diagram in one embodiment;
FIG. 3 is a material preparation flow diagram of a component developer's reference system component build specification in one embodiment;
FIG. 4 is a flow diagram of the installation of a workflow engine with reference to a workflow load file in one embodiment;
FIG. 5 is a block diagram of a deployment device for a system component cluster for a micro-miniature data center in one embodiment;
fig. 6 is an internal structural diagram of a computer device in one embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be further described in detail with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the present application.
In one embodiment, a system component cluster deployment method for a micro-miniature data center is provided, and custom integration, cutting and installation of application components can be realized in a custom deployment scene of the micro-miniature data center, so that rapid adaptation of deployment software to a complex cloud deployment environment is realized. The embodiment is illustrated by the method applied to the terminal, and it is understood that the method can also be applied to the server, and can also be applied to a system comprising the terminal and the server, and implemented through interaction between the terminal and the server.
For easy understanding, the technical terms related to the present technical solution are explained first:
the system component deployment refers to the collaborative deployment of a series of software combinations that are capable of implementing business functions in a complete industrial scenario. In the combination of the system components, the components may have a dependency relationship, and may be combined into a complete set of service software through different interaction modes, or a certain service function may be independently implemented by a certain software.
The system component deployment material refers to all resource information which is depended on by installing certain system software, and comprises a binary package which is depended on by installing current service software: rpm package, deb package, and mirror package, as well as executable script files and configuration files required to install these software packages.
Component developers mainly refer to the developer of a certain component in a system component combination to be deployed and are mainly responsible for organizing material resources required by the current component deployment.
Deployment personnel mainly refer to deployment personnel of system software.
The system component deployment project mainly refers to a deployment project maintained by different component developers, and the project accords with the material construction specification.
The system component deployment material delivery package mainly refers to a compression package required by system component deployment carried by deployment personnel on a deployment site, and the deployment personnel make customized cutting according to self deployment requirements in system component deployment engineering, so as to form the system component deployment material delivery package.
The workflow engine is a software material installation program for adapting to material construction specifications, and the program uses a material delivery package deployed by a system component as an input source to realize the installation of system software.
Based on the foregoing technical term explanation, as shown in fig. 1, the system component cluster deployment method for the micro-miniature data center provided in this embodiment includes the following steps:
step S20, acquiring materials corresponding to the system components, and carrying out material deployment based on a preset material deployment specification.
The material deployment specification mentioned herein specifically refers to organizing own component installation scripts, configuration files and installation package files in a system component deployment material delivery package.
And S40, performing customized cutting on the deployed materials to obtain a system component deployment material delivery package.
The system component deployment material delivery package is tailored or newly added by deployment personnel according to actual requirements of a deployment site, and the components in the system component deployment engineering are packaged into the system component deployment material delivery package, so that the effect of system software custom deployment is achieved.
And step S60, processing the material delivery package for deploying the system component to obtain a workflow load file which is depended by a workflow engine, editing the workflow load file, and controlling the workflow engine to execute the edited workflow load file to complete the installation of the system component.
The workflow load file generated here contains the execution stage and the execution result of single installation, wherein each execution stage contains all information of single component installation dependence, including the absolute path of the execution entry Makefile of the execution component installation, the information of the incoming parameters and the like.
The embodiment of the application provides a deployment material construction specification of a microminiature data center system component, so that the system component supports rapid overall deployment, and each functional component of the system is maintained by a developer with respective deployment script and configuration list. The deployment personnel can arrange the assembly installation execution sequence, carry out batch configuration of the multi-assembly deployment parameters and custom-cut assembly deployment by means of the assembly deployment workflow engine, so that the deployment flow is more flexible, tailorable and customizable.
In one embodiment, step S20 includes:
Preparing corresponding materials according to the requirements of system components;
and constructing a material deployment specification, creating a material catalog according to the material deployment specification, and classifying and placing the materials based on the material catalog to complete material deployment.
In practice, to complete the modular installation of the system components, the materials required to build the system components first need to be sorted, where the sorting criteria is a catalog of materials created based on the material deployment specifications. In order to meet the subsequent selection requirement of materials, a system component deployment engineering catalog structure diagram shown in fig. 2 is provided, and the specific contents in fig. 2 are as follows:
/archive: delivering a top level directory hierarchy of deployment packages;
installer: delivering the directory hierarchy in which script files of all components in the deployment package are located;
demo1: an exemplary package catalog of components;
config: placing a configuration file on which a current service software script file depends in execution;
xxx.config: an exemplary component profile;
values. Yaml: a special profile that can be overridden by the profile of the same key in global. Yaml;
scripts: placing a script file on which current service software is installed;
xxx.sh: an example component installation dependent script file;
makefile: the system component is exposed to an installation and uninstallation portal of the workflow engine, and comprises two subcommands of install and uninstall;
manift. Yaml: including upper layer application information on which the system components are installed;
/charts: a palm part package path on which the component materials are installed;
demo2: an exemplary package catalog of components;
global. Yaml: unifying configuration files;
material: delivering an installation package of all service materials in the deployment package and a directory level where the mirror image is located;
rpm: component mounting dependent rpm packet path;
/deb: component installation dependent deb packet paths;
imaging: a mirror packet path on which the component is installed;
osInsitaler: an executable binary of the workflow engine.
Considering that in a specific material access specification, installation package installation of native support of linux such as rpm/deb and a help installation of service applications in kubenates cluster are included, it is necessary to pay attention to an integration specification of system software materials, and organize material resources on which development software depends in a system component deployment project by referring to the integration specification, and specifically execute the following steps:
step 1: and determining an installation mode, and preparing material resources required by basic software installation. In the case of the Helm installation mode, a Helm Chart package and a mirror tar package need to be prepared, and in the case of the installation of a binary file, an RPM package or a DEB package needs to be prepared.
Step 2: and placing component materials under the catalog of the responsible components according to the engineering structure of the system component deployment engineering. The script file and the configuration file of the component installation dependency are placed in the script and/or config of the delivery package.
Step 3: and writing a Makefile which needs to contain subcommands of install and uninstall, so that a workflow engine can conveniently install and uninstall all materials based on the Makefile.
Step 4: a manifest. Yaml file is written that contains two parts, one part being the switch whether the software was cut for installation and the other part being the pre-installation system component name on which the component installation depends.
Step 5: if the installation script of the component in deployment depends on the input of parameters, a key value pair of the parameter needs to be set in a unified configuration file global. Yaml, and the deployment personnel is given to fill in the designated parameter before deployment.
Based on the component construction specification, single component installation can be closed-loop under own directory level, and an entry file for installation operation is provided in the material directory level, so that a workflow engine is convenient to arrange a material installation and unloading flow. The installation of different components is mutually decoupled, so that the method is suitable for multi-team collaborative deployment, and each team only needs to pay attention to the context dependency relationship and the installation script of the installation of the component, and does not need to pay attention to the specific installation steps and logic of the other components.
According to the system component cluster deployment method facing the microminiature data center, the deployment engineering and the deployment delivery package are separated, so that components in the component deployment package can be conveniently and freely combined. In addition, by means of unified component construction specifications, the deployment of the newly-added system software only needs a developer to change the directory structure of the system component deployment project. The independent deployment of the deployment component is realized, or the tailoring, combining and customizing deployment are carried out by means of a workflow engine, so that the execution sequence of arranging the material installation is conveniently realized, and the standardized integrated installation of the installation software is realized.
In one embodiment, the specific content of the material deployment specification in the foregoing step includes:
defining specific components of a system deployment material, including a configuration file, an installation script, a helm mechanism package, a mirror image, an rpm package and a deb package;
defining the assembly to organize the current service installation and uninstallation command by using the compiled file;
the configurable parameters defining the components are placed in a single configuration file.
In an implementation, the specific content of the material deployment specification includes:
1) The component deployment materials are divided into: configuration files, installation scripts, helm mechanism packages, mirror images, rpm packages, deb packages. The component materials are placed in different directory levels.
2) The assembly uses a compiling file (usually a Makefile) to organize the installation and unloading commands of the current service, so that an external working engine can conveniently and uniformly arrange the deployment and unloading sequence among the services.
3) The configurable parameters of the components are uniformly placed in a single configuration file, so that deployment personnel can uniformly configure the components conveniently.
4) The deployment material of each system component is provided with independent folders of the delivery package, and the folders for placing the materials of different components are under the same directory level.
5) A component profile (yaml) is placed in a single component inventory. The file contains information on both sides, on the one hand, pre-component information that is relied upon to record the current component installation and on the other hand, whether the current material is configured to be ignored by the workflow engine for installation.
6) A module installation entry Makefile is placed in a single module material catalog, the file is an execution entry file of module installation, a workflow engine can automatically identify the file and execute a module installation or uninstallation instruction of the file.
7) The three folder specifications in a single component inventory are as follows: scripts-component materials installation dependent script file, config-materials installation dependent configuration file, and parts-placement component installation required palm part package.
A material preparation flow chart of the component developer's reference system component material construction specification as shown in fig. 3, the component developer should prepare corresponding installation materials according to installation requirements and place them in a delivered material package archive if he needs to deploy his own development application.
Specifically, after the start, a package of components is prepared, and then it is determined whether a custom installation step is required. If yes, adding a custom installation script file under the/scripts catalog, judging whether the configuration file needs to be added, and if not, directly judging whether the configuration file needs to be added. If the judgment of adding the configuration file is needed, adding the custom adding component configuration file under the/config directory, judging whether the configuration file is modified by the deployment personnel or not, and if not, directly judging whether the configuration file is modified by the deployment personnel or not. If the judgment of the configuration file is needed to be modified by the deployment personnel, a configuration field is newly added in global. Yaml, the operation of preparing other materials is executed, and if not, the operation of preparing other materials is directly executed.
After the operation of preparing other materials is completed, the corresponding processing is required according to different installation modes. If the current software is installed by using a binary file, executing rpm/deb installation, and then preparing a binary installation file; i.e. package the binary package into rpm package, deb package and place it in the corresponding directory in the/material folder. If the current software is installed by using the palm, the palm needs to be prepared to install the charts package and the mirror image file used by the current service, and the programs are placed under the appointed mesh of delivery projects such as the/charts catalogue of the material file, so that the process is finished. If the installation mode is different from the two installation modes, the service developer needs to write script files required by installation under the/scripts catalogue of the service material, and call the script in the Makefile file to realize the installation and the uninstallation of the service.
In the service material access specification, all installation and unloading of service materials can be independently realized in the Makefile, the current service material can be accessed to the workflow installation engine for automatic installation, and deployment personnel can independently execute the Makefile to complete the installation and unloading of the current software. Data transfer between service materials is mainly achieved through global.yaml files. The following list two scenarios of component installation and specific actions by deployment personnel:
scene 1: installation scripts for material services require deployment personnel to configure the parameters. The component developer should read and parse the values of the corresponding configuration items in global. Yaml from the script. The deployment personnel need to manually fill in the configuration item values in global. Yaml when actually deployed.
Scene 2: the material deployment script is used for entering the data generated after the installation of a certain material as the script. The component developer should output relevant data that may be relied on by other service materials after the service is deployed in global. Yaml.
The deployment personnel carries the system deployment delivery package to reach the deployment site, so that the network communication between the machine storing the archive package and the machine to be deployed is ensured to be normal. The deployment personnel will take the following steps when actually deploying:
Step 1: the deployment personnel execute the osInstaller's workload build command and the current work engine will generate a workflow load file of workbench. Yaml under the archive directory.
Step 2: the deployment personnel fills in the configuration item parameters in global. Yaml.
Step 3: the deployment personnel can modify the configuration files in the config files under each material according to the real deployment environment of the site.
Step 4: the deployment personnel execute the installation instruction of the osInstaller, and the service software materials are installed one by one according to the execution sequence in the workflow load file of workload.yaml.
In one embodiment, step S40 includes:
cutting or supplementing the materials according to the field requirements of the microminiature data center to obtain processed materials;
and packaging the processed materials to obtain a system component deployment material delivery package.
In the implementation, the system software deployment engineering is subjected to customized cutting and a system component deployment material delivery package is produced, and the steps are mainly that deployment personnel cut or newly add components in the system component deployment engineering according to the actual requirements of a deployment site, and package the components into the system component deployment material delivery package, so that the effect of customized deployment of the system software is achieved.
In one embodiment, step S60 includes:
step S62, decompressing the system component deployment material delivery package, and combining the decompression result according to the execution flow by combining a pre-constructed deployment workflow engine to obtain a workflow load file which is relied by the workflow engine and contains a single installation execution stage and an execution result.
And step S64, editing the workflow load file based on deployment logic, including expansion and cutting, to obtain an edited workflow load file.
And S66, editing a unified configuration file of the system components to be installed, and configuring the components to be installed in batches.
And step S68, controlling the workflow engine to execute the edited workflow load file to complete the installation of the system components.
In practice, this step is essentially the preparation for the workflow engine, and the workflow engine installation phase.
Execution of the workflow engine involves two phases: a pre-processing stage and a workflow engine installation stage. The preprocessing stage is mainly used for generating workflow load files of workflow load.yaml which are depended on by the operation of a workflow engine.
Specifically, the workflow load file workload. Yaml contains a phase field for representing the execution result of the current installation, and a stages array for representing installation information of all system components to be installed,
Each element in the stages array defines the installation details of a single component, and specifically includes:
script represents the absolute path of the entry script file of the software installation and the input parameters of script execution;
the rollback represents the absolute path of the service offload entry script file and script input parameters;
the render represents a configuration rendering field containing the source file to be configured for replacement and the absolute path of the target file to be configured for replacement;
skip indicates whether the current install stage phase is skipped.
And the deployment personnel adds and deletes the directory structure in the system component deployment material delivery package which accords with the component construction specification and re-executes the pre-processing flow of the workflow engine, so that a new workflow load file can be rendered.
In one embodiment, step S62 is used to construct a workflow load file, including:
extracting installation dependency information in a manifest. Yaml file of each component, generating a directed acyclic graph of the dependency relationship of the system component installation, performing topological ordering on execution steps in the directed acyclic graph, and determining the execution sequence of the system component installation;
and rendering the execution sequence record information of the system component installation to obtain a workflow load file containing a single installation execution stage and an execution result.
In one embodiment, step S66 includes:
extracting first data for realizing custom data key value pairs of component developers and second data for storing common configuration items on which a plurality of component materials depend from the unified configuration file;
maintaining the first data to finish the value transmission and the value taking of materials of different components;
and editing the second data, and overwriting the values.yaml files under all directory levels.
In implementation, batch configuration is performed on the components to be installed by editing the unified configuration file, and in particular, the batch configuration is realized by rendering values in the unified configuration file into configuration items of different components.
In order to implement unified configuration of system components, two types of configuration parameters are defined in a unified configuration file global. Yaml, first data are configuration item parameters of a single component, the configuration item parameters are data key value pairs customized by component developers, the component developers maintain the data by themselves, and the partial data are mainly used for transmitting values and taking values of materials of different components. No deployment personnel are required to fill in. For such configuration parameters, the value/assignment logic for the configuration is written by the component developer within the respective component materials.
The second data is a configuration item which belongs to the common dependence of a plurality of components, after the configuration is filled in by deployment personnel, before the workflow engine executes an installation step, key values with the same keys in the files of/char/values.yaml and/config/values.yaml under the directory level of all the components are covered by using global.yaml, so that the aim of unified configuration replacement is achieved.
In one embodiment, step S68 includes:
judging whether the workflow load file exists or not, and if so, entering the next step; if not, stopping the installation process;
loading the workflow load file, analyzing the stages array, and decomposing the specific installation stage information to be executed;
circularly and sequentially executing the installation flow of the single service material;
and judging whether the subsequently executed stage array exists, if so, continuing to execute the loop to sequentially execute the installation flow of the single service material, and if not, recording the current installation state and exiting the installation process.
In implementation, after batch configuration of the components to be installed is completed, the workflow engine installation operation in step S68 needs to be executed, and mainly, the workflow engine performs a specific installation step for the description information of the workflow load file. As shown in fig. 4, the specific steps are:
Step 1: and (3) judging whether a workflow load file workload.yaml file exists or not, if so, entering the next step, if not, throwing out an abnormality, and stopping the installation process.
Step 2: the workflow load file is loaded into workbench.yaml, the execute stages field is parsed, and the information of the specific installation stage to be executed next is decomposed.
Step 3: the execution steps defined in the single stages, i.e. the installation flow of the service material, are circularly executed.
Step 4: and judging whether the action of the stages pointer to the next stage element can be executed, namely whether the next element exists, if so, continuing to execute the step 3, and if not, recording the successful installation state of the execution and exiting the installation process.
The step 3 specifically includes:
step 3.1: and judging whether the skip field value in the stage is true, if so, skipping the current stage, executing the step 4, and if not, continuing to execute the current installation step.
Step 3.2: and acquiring a user-defined configuration file and a configuration file path to be replaced described in a render configuration field in the stage, wherein the field is an unnecessary field, if the render configuration field exists, performing configuration item coverage to realize value replacement of the configuration item, then continuing to execute the subsequent step 3.3, and if the field does not exist, directly executing the subsequent step 3.3.
Step 3.3: judging the execution state of the current installation stage, if the execution state is failed, indicating that the last installation result of the current stage is a failure state, and continuing to execute the step 3.3.1. If the current stage is the pending stage, the step 3.3.2 is continued. If the execution state is success, the current stage is successfully installed in the previous installation process, and the step 4 is continuously executed.
Step 3.4: and (3) checking the execution result, if the checking is successful, continuing to execute the step (4), if the checking is failed, updating the workflow execution state to failed, recording the abnormal error reporting information in a result field of the current stage, judging that the execution is failed, and exiting the current installation process.
Wherein, step 3.3 specifically includes:
step 3.3.1: and acquiring an absolute path (Makefile absolute path of service software) of a service software material unloading entry script file in a roller ack field in the stage, transmitting a parameter uninstallion to the script file, executing the script file to unload the current service material, executing a rollback script in the roller ack field, and continuing to execute the step 3.3.2 after finishing.
Step 3.3.2: the absolute path of the system software material installation entry script file (namely, the Makefile absolute path of the service software) in the script field in the stage is obtained, the entry script defined in the script is executed, and then the subsequent installation step 3.4 is executed.
Based on the technical scheme, in a complex deployment environment, deployment personnel realize the system component deployment material delivery package of different system component combinations through customized packaging, so that customized deployment is performed. And the components can be installed more flexibly by adjusting the configuration of single component materials such as configuration files, installation scripts and the like. Deployment personnel can also realize unified replacement of common configuration fields of all materials by configuring common configuration items in common configuration global. Yaml. Through the clipping configuration switch in the manifest. Yaml in the material catalog, deployment personnel can add and delete the steps of executing the stages in the workflow load file in the construction stage of the workflow load file, thereby achieving the function of customizing clipping deployment software in field deployment.
It should be understood that, although the steps in the flowcharts related to the embodiments described above are sequentially shown as indicated by arrows, these steps are not necessarily sequentially performed in the order indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps in the flowcharts described in the above embodiments may include a plurality of steps or a plurality of stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of the steps or stages is not necessarily performed sequentially, but may be performed alternately or alternately with at least some of the other steps or stages.
Based on the same inventive concept, the embodiment of the application also provides a system component cluster deployment device facing the microminiature data center for realizing the system component cluster deployment method facing the microminiature data center. The implementation scheme of the solution provided by the device is similar to the implementation scheme described in the above method, so the specific limitation in the embodiments of one or more system component cluster deployment devices for a micro-miniature data center provided below may be referred to the limitation of the system component cluster deployment method for a micro-miniature data center described above, which is not repeated herein.
In one embodiment, as shown in fig. 5, there is provided a system component cluster deployment apparatus 80 for a micro-miniature data center, including:
the material deployment module 82 is configured to acquire materials corresponding to the system components, and deploy the materials based on a preset material deployment specification;
a delivery package construction module 84, configured to perform customized cutting on the deployed material, so as to obtain a system component deployment material delivery package;
and the system component installation module 86 is configured to process the system component deployment material delivery package to obtain a workflow load file on which the generated workflow engine depends, edit the workflow load file, and control the workflow engine to execute the edited workflow load file to complete system component installation.
The material deployment module 82 is configured to acquire materials corresponding to the system components, and deploy the materials based on a preset material deployment specification;
the material deployment specification mentioned herein specifically refers to organizing own component installation scripts, configuration files and installation package files in a system component deployment material delivery package.
A delivery package construction module 84, configured to perform customized cutting on the deployed material, so as to obtain a system component deployment material delivery package;
the system component deployment material delivery package is tailored or newly added by deployment personnel according to actual requirements of a deployment site, and the components in the system component deployment engineering are packaged into the system component deployment material delivery package, so that the effect of system software custom deployment is achieved.
And the system component installation module 86 is configured to process the system component deployment material delivery package to obtain a workflow load file on which the generated workflow engine depends, edit the workflow load file, and control the workflow engine to execute the edited workflow load file to complete system component installation.
The workflow load file generated here contains the execution stage and the execution result of single installation, wherein each execution stage contains all information of single component installation dependence, including the absolute path of the execution entry Makefile of the execution component installation, the information of the incoming parameters and the like.
The embodiment of the application provides a deployment material construction specification of a microminiature data center system component, so that the system component supports rapid overall deployment, and each functional component of the system is maintained by a developer with respective deployment script and configuration list. The deployment personnel can arrange the assembly installation execution sequence, carry out batch configuration of the multi-assembly deployment parameters and custom-cut assembly deployment by means of the assembly deployment workflow engine, so that the deployment flow is more flexible, tailorable and customizable.
The modules in the system component cluster deployment device facing the microminiature data center can be fully or partially realized by software, hardware and a combination thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.
In one embodiment, a computer device is provided, which may be a server, the internal structure of which may be as shown in fig. 6. The computer device includes a processor, a memory, and a network interface connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database of the computer equipment is used for storing system component cluster deployment data facing the microminiature data center. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program, when executed by a processor, implements a system component cluster deployment method for a microminiature data center.
It will be appreciated by those skilled in the art that the structure shown in fig. 6 is merely a block diagram of some of the structures associated with the present application and is not limiting of the computer device to which the present application may be applied, and that a particular computer device may include more or fewer components than shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided comprising a memory and a processor, the memory having stored therein a computer program, the processor when executing the computer program performing the steps of:
step S20, acquiring materials corresponding to the system components, and carrying out material deployment based on a preset material deployment specification.
The material deployment specification mentioned herein specifically refers to organizing own component installation scripts, configuration files and installation package files in a system component deployment material delivery package.
And S40, performing customized cutting on the deployed materials to obtain a system component deployment material delivery package.
The system component deployment material delivery package is tailored or newly added by deployment personnel according to actual requirements of a deployment site, and the components in the system component deployment engineering are packaged into the system component deployment material delivery package, so that the effect of system software custom deployment is achieved.
And step S60, processing the material delivery package for deploying the system component to obtain a workflow load file which is depended by a workflow engine, editing the workflow load file, and controlling the workflow engine to execute the edited workflow load file to complete the installation of the system component.
The workflow load file generated here contains the execution stage and the execution result of single installation, wherein each execution stage contains all information of single component installation dependence, including the absolute path of the execution entry Makefile of the execution component installation, the information of the incoming parameters and the like.
The embodiment of the application provides a deployment material construction specification of a microminiature data center system component, so that the system component supports rapid overall deployment, and each functional component of the system is maintained by a developer with respective deployment script and configuration list. The deployment personnel can arrange the assembly installation execution sequence, carry out batch configuration of the multi-assembly deployment parameters and custom-cut assembly deployment by means of the assembly deployment workflow engine, so that the deployment flow is more flexible, tailorable and customizable.
In one embodiment, a computer readable storage medium is provided having a computer program stored thereon, which when executed by a processor, performs the steps of:
Step S20, acquiring materials corresponding to the system components, and carrying out material deployment based on a preset material deployment specification.
The material deployment specification mentioned herein specifically refers to organizing own component installation scripts, configuration files and installation package files in a system component deployment material delivery package.
And S40, performing customized cutting on the deployed materials to obtain a system component deployment material delivery package.
The system component deployment material delivery package is tailored or newly added by deployment personnel according to actual requirements of a deployment site, and the components in the system component deployment engineering are packaged into the system component deployment material delivery package, so that the effect of system software custom deployment is achieved.
And step S60, processing the material delivery package for deploying the system component to obtain a workflow load file which is depended by a workflow engine, editing the workflow load file, and controlling the workflow engine to execute the edited workflow load file to complete the installation of the system component.
The workflow load file generated here contains the execution stage and the execution result of single installation, wherein each execution stage contains all information of single component installation dependence, including the absolute path of the execution entry Makefile of the execution component installation, the information of the incoming parameters and the like.
The embodiment of the application provides a deployment material construction specification of a microminiature data center system component, so that the system component supports rapid overall deployment, and each functional component of the system is maintained by a developer with respective deployment script and configuration list. The deployment personnel can arrange the assembly installation execution sequence, carry out batch configuration of the multi-assembly deployment parameters and custom-cut assembly deployment by means of the assembly deployment workflow engine, so that the deployment flow is more flexible, tailorable and customizable.
In one embodiment, a computer program product is provided comprising a computer program which, when executed by a processor, performs the steps of:
step S20, acquiring materials corresponding to the system components, and carrying out material deployment based on a preset material deployment specification.
The material deployment specification mentioned herein specifically refers to organizing own component installation scripts, configuration files and installation package files in a system component deployment material delivery package.
And S40, performing customized cutting on the deployed materials to obtain a system component deployment material delivery package.
The system component deployment material delivery package is tailored or newly added by deployment personnel according to actual requirements of a deployment site, and the components in the system component deployment engineering are packaged into the system component deployment material delivery package, so that the effect of system software custom deployment is achieved.
And step S60, processing the material delivery package for deploying the system component to obtain a workflow load file which is depended by a workflow engine, editing the workflow load file, and controlling the workflow engine to execute the edited workflow load file to complete the installation of the system component.
The workflow load file generated here contains the execution stage and the execution result of single installation, wherein each execution stage contains all information of single component installation dependence, including the absolute path of the execution entry Makefile of the execution component installation, the information of the incoming parameters and the like.
The embodiment of the application provides a deployment material construction specification of a microminiature data center system component, so that the system component supports rapid overall deployment, and each functional component of the system is maintained by a developer with respective deployment script and configuration list. The deployment personnel can arrange the assembly installation execution sequence, carry out batch configuration of the multi-assembly deployment parameters and custom-cut assembly deployment by means of the assembly deployment workflow engine, so that the deployment flow is more flexible, tailorable and customizable.
Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, database, or other medium used in the various embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, high density embedded nonvolatile Memory, resistive random access Memory (ReRAM), magnetic random access Memory (Magnetoresistive Random Access Memory, MRAM), ferroelectric Memory (Ferroelectric Random Access Memory, FRAM), phase change Memory (Phase Change Memory, PCM), graphene Memory, and the like. Volatile memory can include random access memory (Random Access Memory, RAM) or external cache memory, and the like. By way of illustration, and not limitation, RAM can be in the form of a variety of forms, such as static random access memory (Static Random Access Memory, SRAM) or dynamic random access memory (Dynamic Random Access Memory, DRAM), and the like. The databases referred to in the various embodiments provided herein may include at least one of relational databases and non-relational databases. The non-relational database may include, but is not limited to, a blockchain-based distributed database, and the like. The processors referred to in the embodiments provided herein may be general purpose processors, central processing units, graphics processors, digital signal processors, programmable logic units, quantum computing-based data processing logic units, etc., without being limited thereto.
The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.
The above examples only represent a few embodiments of the present application, which are described in more detail and are not to be construed as limiting the scope of the present application. It should be noted that it would be apparent to those skilled in the art that various modifications and improvements could be made without departing from the spirit of the present application, which would be within the scope of the present application. Accordingly, the scope of protection of the present application shall be subject to the appended claims.
Claims (10)
1. The system component cluster deployment method for the microminiature data center is characterized by comprising the following steps of:
acquiring materials corresponding to the system components, and performing material deployment based on preset material deployment specifications;
customizing and cutting the deployed materials to obtain a system component deployment material delivery package;
And processing the material delivery package deployed by the system component to obtain a workflow load file which is depended by a workflow engine, editing the workflow load file, and controlling the workflow engine to execute the edited workflow load file to complete the installation of the system component.
2. The deployment method of the system component cluster for the microminiature data center according to claim 1, wherein the acquiring the material of the corresponding system component and deploying the material based on a preset material deployment specification comprises:
preparing corresponding materials according to the requirements of system components;
and constructing a material deployment specification, creating a material catalog according to the material deployment specification, and classifying and placing the materials based on the material catalog to complete material deployment.
3. The deployment method of the system component cluster for the microminiature data center according to claim 2, wherein the building material deployment specification comprises:
defining specific components of a system deployment material, including a configuration file, an installation script, a helm mechanism package, a mirror image, an rpm package and a deb package;
defining the assembly to organize the current service installation and uninstallation command by using the compiled file;
The configurable parameters defining the components are placed in a single configuration file.
4. The deployment method of the system component cluster for the microminiature data center according to claim 1, wherein the custom cutting of the deployed materials to obtain a system component deployment material delivery package comprises:
cutting or supplementing the materials according to the field requirements of the microminiature data center to obtain processed materials;
and packaging the processed materials to obtain a system component deployment material delivery package.
5. The deployment method of the system component cluster for the microminiature data center according to claim 1, wherein the processing the system component deployment material delivery package to obtain a workflow load file relied on by a workflow engine, editing the workflow load file, controlling the workflow engine to execute the edited workflow load file to complete system component installation comprises:
decompressing the system component deployment material delivery package, and combining a pre-constructed deployment workflow engine to combine decompression results according to an execution flow to obtain a workflow load file which is relied by the workflow engine and contains a single installation execution stage and an execution result;
Editing the workflow load file based on deployment logic, including expansion and cutting, to obtain an edited workflow load file;
editing a unified configuration file of a system component to be installed, and carrying out batch configuration on the component to be installed;
and controlling the workflow engine to execute the edited workflow load file to complete the installation of the system component.
6. The deployment method of system component clusters for a microminiature data center of claim 5, wherein the workflow load file comprises:
a phase field for indicating the execution result of the current installation;
a stages array for representing installation information of all system components to be installed;
wherein each element in the stages array defines the installation details of a single component.
7. The deployment method of the system component cluster for the microminiature data center according to claim 5, wherein the decompressing the system component deployment material delivery package and combining the decompressed results according to the execution flow by combining a pre-built deployment workflow engine to obtain a workflow load file including a single installation execution stage and an execution result, which is relied on by the workflow engine, comprises:
Extracting installation dependency information in a manifest. Yaml file of each component, generating a directed acyclic graph of the dependency relationship of the system component installation, performing topological ordering on execution steps in the directed acyclic graph, and determining the execution sequence of the system component installation;
and rendering the execution sequence record information of the system component installation to obtain a workflow load file containing a single installation execution stage and an execution result.
8. The deployment method of the system component cluster for the microminiature data center according to claim 5, wherein editing the unified configuration file of the system components to be installed, and performing batch configuration on the components to be installed comprises:
extracting first data for realizing custom data key value pairs of component developers and second data for storing common configuration items on which a plurality of component materials depend from the unified configuration file;
maintaining the first data to finish the value transmission and the value taking of materials of different components;
and editing the second data, and overwriting the values.yaml files under all directory levels.
9. The deployment method of system component clusters for a micro-miniature data center of claim 6, wherein the controlling the workflow engine to execute the edited workflow load file to complete system component installation comprises:
Judging whether the workflow load file exists or not, and if so, entering the next step; if not, stopping the installation process;
loading the workflow load file, analyzing the stages array, and decomposing the specific installation stage information to be executed;
circularly and sequentially executing the installation flow of the single service material;
and judging whether the subsequently executed stage array exists, if so, continuing to execute the loop to sequentially execute the installation flow of the single service material, and if not, recording the current installation state and exiting the installation process.
10. A system component cluster deployment device for a microminiature data center, the device comprising:
the material deployment module is used for acquiring materials corresponding to the system components and deploying the materials based on a preset material deployment specification;
the delivery package construction module is used for carrying out customized cutting on the deployed materials to obtain a system component deployment material delivery package;
and the system component installation module is used for processing the system component deployment material delivery package to obtain a workflow load file which is depended by a workflow engine, editing the workflow load file, and controlling the workflow engine to execute the edited workflow load file to complete system component installation.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311722141.XA CN117407008B (en) | 2023-12-14 | 2023-12-14 | System component cluster deployment method and device for microminiature data center |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311722141.XA CN117407008B (en) | 2023-12-14 | 2023-12-14 | System component cluster deployment method and device for microminiature data center |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN117407008A true CN117407008A (en) | 2024-01-16 |
| CN117407008B CN117407008B (en) | 2024-04-19 |
Family
ID=89494763
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311722141.XA Active CN117407008B (en) | 2023-12-14 | 2023-12-14 | System component cluster deployment method and device for microminiature data center |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117407008B (en) |
Citations (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109389299A (en) * | 2018-09-26 | 2019-02-26 | 中国平安人寿保险股份有限公司 | Work process flow dispositions method, device, computer equipment and storage medium |
| CN111221541A (en) * | 2019-12-26 | 2020-06-02 | 曙光信息产业(北京)有限公司 | Cluster parallel program deployment method and device |
| CN111338657A (en) * | 2020-02-26 | 2020-06-26 | 山东汇贸电子口岸有限公司 | Template-based palm parameter batch configuration method |
| CN112214227A (en) * | 2020-10-20 | 2021-01-12 | 随锐科技集团股份有限公司 | Edge server mirror image customization and deployment system and method |
| CN112860277A (en) * | 2021-02-04 | 2021-05-28 | 江苏云从曦和人工智能有限公司 | Software deployment method, device and computer readable storage medium |
| CN113869841A (en) * | 2020-06-30 | 2021-12-31 | 北京字节跳动网络技术有限公司 | Workflow control method, system and storage medium |
| CN115202674A (en) * | 2022-06-28 | 2022-10-18 | 浪潮云信息技术股份公司 | Helm-based automatic deployment method for local volumes in kubernets cluster |
| CN115220874A (en) * | 2022-09-05 | 2022-10-21 | 税友信息技术有限公司 | Kubernetes cluster deployment method, device, equipment and storage medium |
| CN115237436A (en) * | 2022-08-29 | 2022-10-25 | 北京百度网讯科技有限公司 | Application deployment method and device, electronic equipment and readable storage medium |
| CN115495111A (en) * | 2022-10-31 | 2022-12-20 | 浪潮通用软件有限公司 | Application deployment method, system, equipment and storage medium |
| US20230059339A1 (en) * | 2021-08-19 | 2023-02-23 | International Business Machines Corporation | Microservice hardware and software deployment |
| CN116185432A (en) * | 2022-09-28 | 2023-05-30 | 成都信息工程大学 | Off-line automatic deployment method for Kubeedge computing framework |
| CN116755716A (en) * | 2023-05-16 | 2023-09-15 | 浪潮通信信息系统有限公司 | Software package deployment method, device and equipment of big data cluster and storage medium |
| CN116775048A (en) * | 2023-08-24 | 2023-09-19 | 浪潮通用软件有限公司 | Rapid deployment method, device and medium based on software delivery |
| CN116893822A (en) * | 2023-07-27 | 2023-10-17 | 中银金融科技有限公司 | Workflow engine multi-environment deployment method and system, electronic device and storage medium |
| US20230359450A1 (en) * | 2022-05-09 | 2023-11-09 | Nanjing Xiyin Ecommerce Co., Ltd. | Cloud application engine deployment method for shielding web framework from users and apparatus, device and storage medium thereof |
| CN117112122A (en) * | 2022-05-17 | 2023-11-24 | 北京京东振世信息技术有限公司 | Cluster deployment method and device |
| CN117193800A (en) * | 2022-05-30 | 2023-12-08 | 奇安信科技集团股份有限公司 | Software installation method and device, electronic equipment and storage medium |
-
2023
- 2023-12-14 CN CN202311722141.XA patent/CN117407008B/en active Active
Patent Citations (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109389299A (en) * | 2018-09-26 | 2019-02-26 | 中国平安人寿保险股份有限公司 | Work process flow dispositions method, device, computer equipment and storage medium |
| CN111221541A (en) * | 2019-12-26 | 2020-06-02 | 曙光信息产业(北京)有限公司 | Cluster parallel program deployment method and device |
| CN111338657A (en) * | 2020-02-26 | 2020-06-26 | 山东汇贸电子口岸有限公司 | Template-based palm parameter batch configuration method |
| CN113869841A (en) * | 2020-06-30 | 2021-12-31 | 北京字节跳动网络技术有限公司 | Workflow control method, system and storage medium |
| CN112214227A (en) * | 2020-10-20 | 2021-01-12 | 随锐科技集团股份有限公司 | Edge server mirror image customization and deployment system and method |
| CN112860277A (en) * | 2021-02-04 | 2021-05-28 | 江苏云从曦和人工智能有限公司 | Software deployment method, device and computer readable storage medium |
| US20230059339A1 (en) * | 2021-08-19 | 2023-02-23 | International Business Machines Corporation | Microservice hardware and software deployment |
| US20230359450A1 (en) * | 2022-05-09 | 2023-11-09 | Nanjing Xiyin Ecommerce Co., Ltd. | Cloud application engine deployment method for shielding web framework from users and apparatus, device and storage medium thereof |
| CN117112122A (en) * | 2022-05-17 | 2023-11-24 | 北京京东振世信息技术有限公司 | Cluster deployment method and device |
| CN117193800A (en) * | 2022-05-30 | 2023-12-08 | 奇安信科技集团股份有限公司 | Software installation method and device, electronic equipment and storage medium |
| CN115202674A (en) * | 2022-06-28 | 2022-10-18 | 浪潮云信息技术股份公司 | Helm-based automatic deployment method for local volumes in kubernets cluster |
| CN115237436A (en) * | 2022-08-29 | 2022-10-25 | 北京百度网讯科技有限公司 | Application deployment method and device, electronic equipment and readable storage medium |
| CN115220874A (en) * | 2022-09-05 | 2022-10-21 | 税友信息技术有限公司 | Kubernetes cluster deployment method, device, equipment and storage medium |
| CN116185432A (en) * | 2022-09-28 | 2023-05-30 | 成都信息工程大学 | Off-line automatic deployment method for Kubeedge computing framework |
| CN115495111A (en) * | 2022-10-31 | 2022-12-20 | 浪潮通用软件有限公司 | Application deployment method, system, equipment and storage medium |
| CN116755716A (en) * | 2023-05-16 | 2023-09-15 | 浪潮通信信息系统有限公司 | Software package deployment method, device and equipment of big data cluster and storage medium |
| CN116893822A (en) * | 2023-07-27 | 2023-10-17 | 中银金融科技有限公司 | Workflow engine multi-environment deployment method and system, electronic device and storage medium |
| CN116775048A (en) * | 2023-08-24 | 2023-09-19 | 浪潮通用软件有限公司 | Rapid deployment method, device and medium based on software delivery |
Non-Patent Citations (2)
| Title |
|---|
| MCCORMICK, R ET AL.: "Development of Miniature Robotic Manipulators to Enable SmallSat Clusters", 《IEEE AEROSPACE CONFERENCE》, 31 December 2017 (2017-12-31) * |
| 相铮;石春鹏;韩立新;: "Docker容器技术在MES系统部署中的应用", 制造业自动化, no. 04, 25 April 2020 (2020-04-25) * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN117407008B (en) | 2024-04-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112286779B (en) | Test task processing method and device, storage medium and computer equipment | |
| CN112650475B (en) | Software low-code development system and development method combined with middle platform architecture theory | |
| US20040088397A1 (en) | System and method for management of software applications | |
| KR20200115020A (en) | Hyperledger fabric network creation method, controller and storage medium | |
| US10585785B2 (en) | Preservation of modifications after overlay removal from a container | |
| US9542173B2 (en) | Dependency handling for software extensions | |
| KR102397494B1 (en) | Low code web development and operating system, and service method using of it | |
| US11150919B2 (en) | Logging of scripts executed in an information technology workflow orchestration system | |
| CN111651219A (en) | Method and equipment for managing multi-module project configuration file | |
| CN114911471A (en) | Software engineering construction method, system and storage medium | |
| CN114115838A (en) | Data interaction method and system based on distributed components and cloud platform | |
| CN112564979B (en) | Execution method and device of construction task, computer equipment and storage medium | |
| CN113835705A (en) | Big data service product development method, device and system | |
| CN112596746B (en) | Application installation package generation method and device, computer equipment and storage medium | |
| CN117407008B (en) | System component cluster deployment method and device for microminiature data center | |
| EP3712733A1 (en) | Method and system of preparing engineering data for industrial control systems | |
| CN114676418B (en) | Operation request processing method, device, equipment, storage medium and program product | |
| CN115129360A (en) | Code file management method and device, electronic equipment and storage medium | |
| CN114201174A (en) | Construction method and device of hybrid mobile application, electronic equipment and storage medium | |
| CN117093207B (en) | Entity processing method, device and system of multi-service data model | |
| US20240143487A1 (en) | Secure testing of attachment functionality of objects | |
| CN118092950A (en) | Heterogeneous supercomputing-oriented application software packaging method and system | |
| CN117193928A (en) | K8 s-based application integration deployment method, equipment and medium | |
| CN116302055A (en) | Method and device for integrating small programs and electronic equipment | |
| CN114138324A (en) | Task control method and device based on cloud service 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |