CN112698839A - Data center node deployment method, device and system and computer storage medium - Google Patents

Data center node deployment method, device and system and computer storage medium Download PDF

Info

Publication number
CN112698839A
CN112698839A CN202011644284.XA CN202011644284A CN112698839A CN 112698839 A CN112698839 A CN 112698839A CN 202011644284 A CN202011644284 A CN 202011644284A CN 112698839 A CN112698839 A CN 112698839A
Authority
CN
China
Prior art keywords
target
configuration information
idc
data center
parameters
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
Application number
CN202011644284.XA
Other languages
Chinese (zh)
Other versions
CN112698839B (en
Inventor
魏艳梅
侯向辉
李斌
江旻
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
WeBank Co Ltd
Original Assignee
WeBank Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by WeBank Co Ltd filed Critical WeBank Co Ltd
Priority to CN202011644284.XA priority Critical patent/CN112698839B/en
Publication of CN112698839A publication Critical patent/CN112698839A/en
Application granted granted Critical
Publication of CN112698839B publication Critical patent/CN112698839B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • 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
    • 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
    • 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/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
    • G06F9/44526—Plug-ins; Add-ons
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/03—Credit; Loans; Processing thereof
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/02—Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Databases & Information Systems (AREA)
  • Economics (AREA)
  • General Business, Economics & Management (AREA)
  • Technology Law (AREA)
  • Strategic Management (AREA)
  • Marketing (AREA)
  • Development Economics (AREA)
  • Data Mining & Analysis (AREA)
  • Computer Security & Cryptography (AREA)
  • Stored Programmes (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The invention relates to the technical field of financial science and technology, and discloses a data center node deployment method, device and system and a computer storage medium. The data center node deployment method is applied to a packaging system and comprises the following steps: the packaging system acquires a subsystem identifier of a DCN (data center node) to be deployed and a target Internet Data Center (IDC), and acquires target configuration information according to the subsystem identifier and the target IDC; pulling a target SOP component from a standard operation program SOP adapter according to the subsystem identifier, and packaging the target SOP component into a JAR packet; and when the application is started, sending the target configuration information and the JAR packet to an application system, so that the application system loads the parameters of the SOP component corresponding to the JAR packet and the target configuration information to deploy the parameters to the target IDC. The invention can reduce the deployment time and cost of the DCN and improve the deployment efficiency of the DCN.

Description

Data center node deployment method, device and system and computer storage medium
Technical Field
The invention relates to the technical field of financial technology (Fintech), in particular to a data center node deployment method, device and system and a computer storage medium.
Background
With the development of computer technology, more and more technologies are applied in the financial field, and the traditional financial industry is gradually changing to financial technology (Fintech), but higher requirements are also put forward on the technologies due to the requirements of the financial industry on safety and real-time performance.
In the multi-product line deployment process, in the prior art, applications in different DCN (Data Center Node) areas are generally deployed for different product lines, and subsystems, configurations, DBs (Data base) and GIT (Georgia Institute of Technology) engineering of the used system are independent, specifically, the system configuration is as shown in fig. 1 (for example, the subsystems are CPS, Credit process system, and loan core customer account processing system).
With the continuous expansion of services, product lines need to be expanded continuously to support the demands of products in different fields. In existing product line systems, lateral expansion is usually performed, and accordingly, subsystems, configuration, DB, and system GIT engineering all need to be re-developed and tested, resulting in higher DCN deployment time and cost. Therefore, how to reduce the deployment time and cost of the DCN and improve the deployment efficiency of the DCN is a problem to be solved urgently at present.
Disclosure of Invention
The invention mainly aims to provide a data center node deployment method, a data center node deployment device, a data center node deployment system and a computer storage medium, and aims to reduce the deployment time and cost of a DCN and improve the deployment efficiency of the DCN.
In order to achieve the above object, the present invention provides a data center node deployment method, which is applied to a packaging system, and the data center node deployment method includes:
the packaging system acquires a subsystem identifier of a DCN (data center node) to be deployed and a target Internet Data Center (IDC), and acquires target configuration information according to the subsystem identifier and the target IDC;
pulling a target SOP component from a standard operation program SOP adapter according to the subsystem identifier, and packaging the target SOP component into a JAR packet;
and when the application is started, sending the target configuration information and the JAR packet to an application system, so that the application system loads the parameters of the SOP component corresponding to the JAR packet and the target configuration information to deploy the parameters to the target IDC.
Optionally, the packaging system obtains a subsystem identifier and a target IDC of a DCN to be deployed, and the step of obtaining target configuration information according to the subsystem identifier and the target IDC includes:
the packaging system acquires a subsystem identifier and a target IDC of a DCN to be deployed, and acquires initial configuration information according to the subsystem identifier;
acquiring a subsystem variable according to the subsystem identification, and determining to obtain system configuration information according to the subsystem identification, the subsystem variable and the initial configuration information;
acquiring IDC variables according to the target IDC, and determining IDC configuration information according to the target IDC, the IDC variables and the initial configuration information; wherein the target configuration information comprises the system configuration information and the IDC configuration information.
Optionally, the step of sending the target configuration information and the JAR packet to an application system when the application is started, so that the application system loads the parameters of the SOP component corresponding to the JAR packet and the target configuration information, and deploys the parameters and the target configuration information to the target IDC includes:
when the application is started, acquiring a version address corresponding to the JAR packet from a preset attribute label of a preset file of the JAR packet;
and sending the target configuration information and the version address corresponding to the JAR packet to an application system, so that the application system loads the parameters of the corresponding SOP component based on the version address corresponding to the JAR packet, and loads the target configuration information to deploy the target configuration information to the target IDC.
Optionally, the target configuration information includes engineering code, system parameters, scripts, and environment variables.
In addition, to achieve the above object, the present invention further provides a data center node deployment method, which is applied to a data center node deployment system, where the data center node deployment system includes a packaging system and an application system, and the data center node deployment method includes:
the packaging system acquires a subsystem identifier and a target IDC of a DCN to be deployed, and acquires target configuration information according to the subsystem identifier and the target IDC;
the packaging system pulls a target SOP component from the SOP adapter according to the subsystem identifier and packages the target SOP component into a JAR packet;
when the application is started, the application system receives target configuration information and JAR packets which are sent by the packaging system based on the subsystem identifier of the DCN to be deployed and the target IDC;
and the application system loads the parameters of the SOP component corresponding to the JAR packet and the target configuration information so as to deploy the parameters into the target IDC.
Optionally, the step of loading, by the application system, the parameters of the SOP component corresponding to the JAR packet and the target configuration information to deploy to the target IDC includes:
the application system receives an external system identifier and an operation category sent by an external system;
the application system obtains a strategy constructor through a strategy adapter according to the external system identification and the operation type adaptation;
and the application system loads the parameters of the SOP component corresponding to the JAR packet and the target configuration information based on the policy constructor so as to deploy the parameters and the target configuration information to the target IDC corresponding to the external system identifier.
Optionally, the step of loading, by the application system, the parameters of the SOP component corresponding to the JAR packet and the target configuration information to deploy to the target IDC includes:
the application system acquires the current operation type;
the application system obtains a strategy constructor through a strategy adapter according to the subsystem identification and the current operation type adaptation;
and the application system loads parameters of SOP components corresponding to the JAR packet and the target configuration information based on the policy constructor so as to deploy the parameters and the target configuration information to a target IDC to which a target external docking system corresponding to the subsystem identification and the current operation type belongs.
In addition, to achieve the above object, the present invention further provides a data center node deployment apparatus, where the data center node deployment apparatus includes:
the system comprises an acquisition module, a configuration module and a configuration module, wherein the acquisition module is used for acquiring a subsystem identifier and a target IDC of the DCN to be deployed and acquiring target configuration information according to the subsystem identifier and the target IDC;
the packaging module is used for pulling a target SOP component from the SOP adapter according to the subsystem identifier and packaging the target SOP component into a JAR packet;
and the sending module is used for sending the target configuration information and the JAR packet to an application system when the application is started so that the application system can load the parameters of the SOP component corresponding to the JAR packet and the target configuration information to deploy the parameters into the target IDC.
In addition, to achieve the above object, the present invention further provides a data center node deployment system, which is characterized in that the data center node deployment system includes: packaging system and application system still include: a memory, a processor, and a DCN deployment program stored on the memory and executable on the processor, the DCN deployment program when executed by the processor implementing the steps of the second data center node deployment method as described above. .
In addition, to achieve the above object, the present invention further provides a computer-readable storage medium, where a DCN deployment program is stored, and when executed by a processor, the DCN deployment program implements the steps of the first or second data center node deployment method described above.
The invention provides a data center node deployment method, a device, a system and a computer storage medium, wherein the data center node deployment method is applied to a packaging system, the packaging system firstly acquires a subsystem identifier and a target IDC of a DCN to be deployed, and acquires target configuration information according to the subsystem identifier and the target IDC; then, pulling a target SOP component from the SOP adapter according to the subsystem identifier, and packaging the target SOP component into a JAR packet; and when the application is started, sending the target configuration information and the JAR packet to an application system so as to load the parameters and the target configuration information of the SOP component corresponding to the JAR packet by the application system and deploy the parameters and the target configuration information to the target IDC. By the mode, when different subsystems in different DCN areas are deployed on a multi-product line, multiple deployments of one set of codes can be realized without repeated development by directly acquiring target configuration information (including some configuration parameters, GIT engineering codes and the like). In addition, different SOP components are expanded through SOP packaging, and then the target SOP component can be directly pulled during deployment, so that self-adaptation of the SOP component is realized, and repeated construction of a product function module is avoided. Through the self-adaption strategy, a set of code multi-deployment scheme under a distributed architecture multi-DCN system can be realized, so that the deployment time and cost of the DCN can be reduced, and the deployment efficiency of the DCN is improved.
Drawings
Fig. 1 is a schematic diagram of a system for product line deployment in the prior art related to the data center node deployment method of the present invention;
fig. 2 is a schematic diagram of a terminal structure of a hardware operating environment according to an embodiment of the present invention;
FIG. 3 is a schematic flow chart of a first embodiment of a data center node deployment method applied to a packaging system according to the present invention;
fig. 4 is a schematic flow chart of a first embodiment of a data center node deployment method applied to a data center node deployment system according to the present invention.
The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
Referring to fig. 2, fig. 2 is a schematic diagram of a terminal structure of a hardware operating environment according to an embodiment of the present invention.
The terminal according to the embodiment of the present invention may be a server, or may be a terminal device such as a PC (Personal Computer), a tablet Computer, or a mobile Computer, and the terminal is a terminal equipped with a packaging system.
As shown in fig. 2, the terminal may include: a processor 1001, such as a CPU, a communication bus 1002, a network interface 1003, and a memory 1004. Wherein a communication bus 1002 is used to enable connective communication between these components. The network interface 1003 may optionally include a standard wired interface, a wireless interface (e.g., a Wi-Fi interface). The memory 1004 may be a high-speed RAM memory or a non-volatile memory (e.g., a disk memory). The memory 1004 may alternatively be a storage device separate from the processor 1001.
Those skilled in the art will appreciate that the terminal structure shown in fig. 1 is not intended to be limiting and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.
As shown in fig. 2, the memory 1004, which is a kind of computer storage medium, may include therein an operating system, a network communication module, and a DCN deployment program.
In the terminal shown in fig. 2, the network interface 1003 is mainly used for connecting a terminal corresponding to a terminal having an application system installed therein and performing data communication with the terminal corresponding to the application system installed therein; and the processor 1001 may be configured to call the DCN deployment program stored in the memory 1004 and perform the following operations:
acquiring a subsystem identifier of a DCN (data center node) to be deployed and a target Internet Data Center (IDC), and acquiring target configuration information according to the subsystem identifier and the target IDC;
pulling a target SOP component from a standard operation program SOP adapter according to the subsystem identifier, and packaging the target SOP component into a JAR packet;
and when the application is started, sending the target configuration information and the JAR packet to an application system, so that the application system loads the parameters of the SOP component corresponding to the JAR packet and the target configuration information to deploy the parameters to the target IDC.
Further, the processor 1001 may call the DCN deployment program stored in the memory 1004, and further perform the following operations:
the packaging system acquires a subsystem identifier and a target IDC of a DCN to be deployed, and acquires initial configuration information according to the subsystem identifier;
acquiring a subsystem variable according to the subsystem identification, and determining to obtain system configuration information according to the subsystem identification, the subsystem variable and the initial configuration information;
acquiring IDC variables according to the target IDC, and determining IDC configuration information according to the target IDC, the IDC variables and the initial configuration information; wherein the target configuration information comprises the system configuration information and the IDC configuration information.
Further, the processor 1001 may call the DCN deployment program stored in the memory 1004, and further perform the following operations:
when the application is started, acquiring a version address corresponding to the JAR packet from a preset attribute label of a preset file of the JAR packet;
and sending the target configuration information and the version address corresponding to the JAR packet to an application system, so that the application system loads the parameters of the corresponding SOP component based on the version address corresponding to the JAR packet, and loads the target configuration information to deploy the target configuration information to the target IDC.
Further, the target configuration information includes engineering code, system parameters, scripts, and environment variables.
Based on the hardware structure, the embodiments of the data center node deployment method are provided.
The invention provides a data center node deployment method.
Referring to fig. 3, fig. 3 is a schematic flow chart of a first embodiment of a data center node deployment method applied to a packaging system according to the present invention.
In this embodiment, the data center node deployment method is applied to a packaging system, and includes:
step S10, the packaging system acquires a subsystem identifier of a DCN (data center node) to be deployed and a target Internet Data Center (IDC), and acquires target configuration information according to the subsystem identifier and the target IDC;
the data center node deployment method of the embodiment is implemented by a terminal equipped with a packaging system (PACE +). In this embodiment, when receiving a deployment request of a product line, the packaging system may first obtain a subsystem identifier (system id) and a target IDC (Internet Data Center) of a DCN (Data Center Node) to be deployed according to the deployment request, and then obtain target configuration information according to the subsystem identifier and the target IDC.
Specifically, a CMDB (Configuration Management Database) may be constructed in advance, where a mapping relationship between a subsystem identifier and Configuration information is stored in the CMDB, where the Configuration information includes an engineering code (program), a system parameter (param), a script (shell), and an environment variable (Env), the engineering code is a java code corresponding to the GIT project, the system parameter is some parameter Configuration data of the system, the script is personalized setting under a product, such as data cleaning, and the environment variable is some parameters used in the operating system to specify an operating environment of the operating system. When the target configuration information is obtained, the initial configuration information can be obtained according to the subsystem identification; then, acquiring a subsystem variable according to the subsystem identifier, and determining to obtain system configuration information according to the subsystem identifier, the subsystem variable and the initial configuration information; meanwhile, obtaining IDC variables according to the target IDC, and determining to obtain IDC configuration information according to the target IDC, the IDC variables and the initial configuration information; wherein the target configuration information comprises system configuration information and IDC configuration information. Specific implementation can be referred to the second embodiment described below.
Step S20, pulling a target SOP component from a standard operation program SOP adapter according to the subsystem identifier, and packaging the target SOP component into a JAR package;
then, a target SOP component is pulled from an SOP (Standard Operating Procedure) adapter according to the subsystem identification, and the target SOP component is packaged into a JAR package. The SOP adapter comprises SOP components corresponding to different subsystem identifications, and the packaging aims to facilitate subsequent deployment.
Specifically, the SOP components are based on differences in product functionality, by extracting system parameters highly, abstracting commonalities into components, and the functions of differences are obtained by component expansion. Through the extension external member with different products mapping different types, ensure the customization code level of different products and keep apart, and then can realize: 1) SOP granularity, functional cohesion, reusability and expandability of the component; 2) different products can be customized and combined with different service components; 3) the components are independent, so that unit testing is facilitated to guarantee quality; 4) by expanding the suite, multi-product customized service flow support can be realized.
Step S30, when the application is started, the target configuration information and the JAR packet are sent to an application system, so that the application system can load the parameters of the SOP component corresponding to the JAR packet and the target configuration information to deploy the parameters to the target IDC.
And when the application is started, sending the target configuration information and the JAR packet to an application system so as to load the parameters and the target configuration information of the SOP component corresponding to the JAR packet by the application system and deploy the parameters and the target configuration information to the target IDC.
Specifically, step S30 includes:
step a31, when an application is started, acquiring a version address corresponding to the JAR package from a preset attribute label of a preset file of the JAR package;
step a32, sending the target configuration information and the version address corresponding to the JAR packet to an application system, so that the application system loads the parameters of the corresponding SOP component based on the version address corresponding to the JAR packet, and loads the target configuration information to deploy to the target IDC.
In this embodiment, when the application is started, the version address corresponding to the JAR package is obtained from a preset attribute tag of a preset file of the JAR package, where the preset file is optionally a pop file, and the preset attribute tag is a sop, version _ replacement _ version-snap in properties attribute tag. And then, sending the target configuration information and the version address corresponding to the JAR packet to an application system, so that the application system loads the parameters of the corresponding SOP component based on the version address corresponding to the JAR packet, and loads the target configuration information to deploy the target configuration information to a target IDC.
Correspondingly, after receiving the target configuration information and the version address corresponding to the JAR packet, the application system can automatically load the parameters of the corresponding SOP component based on the version address corresponding to the JAR packet to realize the automatic adaptation of the SOP, and simultaneously load the target configuration information to deploy the target configuration information to the target IDC.
The embodiment of the invention provides a data center node deployment method, which is applied to a packaging system, wherein the packaging system firstly acquires a subsystem identifier and a target IDC of a DCN to be deployed, and acquires target configuration information according to the subsystem identifier and the target IDC; then, pulling a target SOP component from the SOP adapter according to the subsystem identifier, and packaging the target SOP component into a JAR packet; and when the application is started, sending the target configuration information and the JAR packet to an application system so as to load the parameters and the target configuration information of the SOP component corresponding to the JAR packet by the application system and deploy the parameters and the target configuration information to the target IDC. By the mode, when different subsystems in different DCN areas are deployed on a multi-product line, multiple deployments of one set of codes can be realized without repeated development by directly acquiring target configuration information (including some configuration parameters, GIT engineering codes and the like). In addition, different SOP components are expanded through SOP packaging, and then the target SOP component can be directly pulled during deployment, so that self-adaptation of the SOP component is realized, and repeated construction of a product function module is avoided. Through the self-adaption strategy, a set of code multi-deployment scheme under a distributed architecture multi-DCN system can be realized, so that the deployment time and cost of the DCN can be reduced, and the deployment efficiency of the DCN is improved.
Further, based on the first embodiment, a second embodiment of the data center node deployment method applied to the packaging system is provided.
In the present embodiment, step S10 includes:
a11, the packaging system acquires a subsystem identifier and a target IDC of a DCN to be deployed, and acquires initial configuration information according to the subsystem identifier;
in this embodiment, the packaging system obtains a subsystem identifier and a target IDC of a DCN to be deployed, and obtains initial configuration information according to the subsystem identifier, specifically, initial configuration information corresponding to the subsystem identifier can be obtained from a CMDB storing a mapping relationship between the subsystem identifier and the configuration information; the initial configuration information comprises engineering codes, system parameters, scripts and environment variables, wherein the engineering codes are java codes corresponding to GIT projects, the system parameters are some parameter configuration data of the system, the scripts are personalized settings under products, such as data cleaning and the like, and the environment variables are some parameters used for specifying the operating environment of the operating system in the operating system.
A12, acquiring subsystem variables according to the subsystem identifications, and determining system configuration information according to the subsystem identifications, the subsystem variables and the initial configuration information;
then, the subsystem variable is obtained according to the subsystem identifier, and the system configuration information is determined and obtained according to the subsystem identifier, the subsystem variable and the initial configuration information, namely, the subsystem variable is used as a key value in the key-value, and the automatic replacement of the relevant variable value of the system is carried out.
A13, acquiring IDC variables according to the target IDC, and determining IDC configuration information according to the target IDC, the IDC variables and the initial configuration information; wherein the target configuration information comprises the system configuration information and the IDC configuration information.
When the system configuration information is determined, the IDC variables can be obtained according to the target IDC, and the IDC configuration information is determined and obtained according to the target IDC, the IDC variables and the initial configuration information, namely, the IDC variables are used as key values in the key-value to automatically replace the IDC related variable values. Wherein the IDC variable is optionally an environment variable, such as E environment, G environment, etc.
Finally, the target configuration information includes system configuration information and IDC configuration information. Correspondingly, the target configuration information includes 4 types of information, namely engineering code, system parameters, scripts and environment variables.
In this embodiment, after the initial configuration information is acquired according to the subsystem identifier, the corresponding system related variable value (i.e., system configuration information) and IDC related variable value (i.e., IDC configuration information) are respectively determined according to the subsystem variable and the IDC variable, so that automatic replacement of the system related variable value and the IDC related variable value is realized, and subsequent deployment can be further facilitated.
Further, referring to fig. 4, fig. 4 is a schematic flowchart of a first embodiment of a data center node deployment method applied to an application system according to the present invention.
In this embodiment, the data center node deployment method is applied to a data center node deployment system, where the data center node deployment system includes a packaging system and an application system, and the data center node deployment method further includes:
step S100, the packaging system acquires a subsystem identifier and a target IDC of a DCN to be deployed, and acquires target configuration information according to the subsystem identifier and the target IDC;
the data center node deployment method of the embodiment is applied to a data center node deployment system, and the data center node deployment system comprises a packaging system and an application system. In this embodiment, when receiving a deployment request of a product line, the packaging system may first obtain a subsystem identifier (system id) and a target IDC (Internet Data Center) of a DCN (Data Center Node) to be deployed according to the deployment request, and then obtain target configuration information according to the subsystem identifier and the target IDC.
Specifically, a CMDB (Configuration Management Database) may be constructed in advance, where a mapping relationship between a subsystem identifier and Configuration information is stored in the CMDB, where the Configuration information includes an engineering code (program), a system parameter (param), a script (shell), and an environment variable (Env), the engineering code is a java code corresponding to the GIT project, the system parameter is some parameter Configuration data of the system, the script is personalized setting under a product, such as data cleaning, and the environment variable is some parameters used in the operating system to specify an operating environment of the operating system. When the target configuration information is obtained, the initial configuration information can be obtained according to the subsystem identification; then, acquiring a subsystem variable according to the subsystem identifier, and determining to obtain system configuration information according to the subsystem identifier, the subsystem variable and the initial configuration information; meanwhile, obtaining IDC variables according to the target IDC, and determining to obtain IDC configuration information according to the target IDC, the IDC variables and the initial configuration information; wherein the target configuration information comprises system configuration information and IDC configuration information. The specific implementation process may refer to the second embodiment of the data center node deployment method applied to the packaging system.
Step S200, the packaging system pulls a target SOP component from the SOP adapter according to the subsystem identifier and packages the target SOP component into a JAR package;
then, the packaging system pulls a target SOP component from an SOP (Standard Operating Procedure) adapter according to the subsystem identifier, and packages the target SOP component into a JAR package. The SOP adapter comprises SOP components corresponding to different subsystem identifications, and the packaging aims to facilitate subsequent deployment.
Specifically, the SOP components are based on differences in product functionality, by extracting system parameters highly, abstracting commonalities into components, and the functions of differences are obtained by component expansion. Through the extension external member with different products mapping different types, ensure the customization code level of different products and keep apart, and then can realize: 1) SOP granularity, functional cohesion, reusability and expandability of the component; 2) different products can be customized and combined with different service components; 3) the components are independent, so that unit testing is facilitated to guarantee quality; 4) by expanding the suite, multi-product customized service flow support can be realized.
Step S300, when the application is started, the application system receives the subsystem identification of the packaging system based on the DCN to be deployed and target configuration information and JAR packets sent by a target IDC;
when the application is started, the application system receives target configuration information and a JAR packet which are sent by the packaging system based on the subsystem identifier of the DCN to be deployed and the target IDC, wherein the target configuration information includes system configuration information and IDC configuration information, specifically including 4 types of engineering codes, system parameters, scripts and environment variables, and the process of acquiring the target configuration information and the JAR packet may refer to the first embodiment of the data center node deployment method applied to the packaging system, which is not described herein again.
Step S400, the application system loads parameters of the SOP component corresponding to the JAR packet and the target configuration information so as to deploy the parameters and the target configuration information to the target IDC.
After receiving the target configuration information and the JAR packet, the application system loads the parameters of the SOP component corresponding to the JAR packet and the target configuration information so as to deploy the parameters and the target configuration information to the target IDC.
Further, in specific implementation, after obtaining the JAR package packed by the SOP component, the packing system may first obtain a version address corresponding to the JAR package from a preset attribute tag of a preset file of the JAR package, where the preset file may optionally be a pop file, and the preset attribute tag is a SOP, version, page _ relocation, version-SNAPSHOT-snap in properties attribute tag. And then, sending the target configuration information and the version address corresponding to the JAR packet to an application system, wherein at the moment, after receiving the target configuration information and the version address corresponding to the JAR packet, the application system can automatically load parameters of a corresponding SOP component based on the version address corresponding to the JAR packet so as to realize the automatic adaptation of the SOP, and simultaneously loads the target configuration information so as to deploy the target configuration information to the target IDC.
As an embodiment, step S200 may include:
step a211, the application system receives an external system identifier and a job category sent by an external system;
step a212, the application system obtains a policy constructor through a policy adapter according to the external system identification and the operation type adaptation;
step a213, the application system loads the parameters of the SOP component corresponding to the JAR packet and the target configuration information based on the policy constructor, so as to deploy the parameters to the target IDC corresponding to the external system identifier.
In this embodiment, when the external system transmits its own system identifier (system id, denoted as external system identifier) and job type (bizType), the deployment process specifically includes:
the application system receives an external system identifier and a job type sent by an external system, then a Policy Builder (Policy Builder) is obtained through a Policy adapter (Policy adapter) according to the external system identifier and the job type adaptation, and finally parameters and target configuration information of SOP components corresponding to JAR packets are loaded based on the Policy Builder so as to be deployed to target IDCs corresponding to the external system identifier. By the mode, self-adaption processing of the receiving function of the external system can be realized.
As another embodiment, step S200 may include:
step a221, the application system acquires the current job type;
step a222, the application system obtains a policy constructor through a policy adapter according to the subsystem identification and the current operation type adaptation;
step a223, the application system loads parameters of the SOP component corresponding to the JAR packet and the target configuration information based on the policy constructor, so as to deploy the parameters and the target configuration information to a target IDC to which a target external docking system corresponding to the subsystem identifier and the current job category belongs.
In this embodiment, when the external system does not transfer its own system identifier and job category, the deployment process specifically includes:
the application system obtains a current job type, wherein the current job type can be determined based on a current execution job of the system flow, for example, the system flow is self-locking → data synchronization → short message, the current execution job is determined according to the above sequence, self-adaptation processing of an external system sending function of the job type of self-locking is performed first, self-adaptation processing of the external system sending function of the job type of data synchronization is performed, and finally self-adaptation processing of the external system sending function of the job type of short message is performed. Then, a strategy constructor is obtained through the strategy adapter according to the subsystem identification and the current operation type adaptation; and finally, a strategy constructor is obtained according to the strategy generator in an adaptive mode, and parameters and target configuration information of the SOP component corresponding to the JAR packet are loaded on the basis of the strategy constructor so as to be deployed into a target IDC to which a target external docking system corresponding to the subsystem identifier and the current operation type belongs. By the mode, self-adaption processing of the sending function of the external system can be realized.
In the embodiment, the packaging system firstly acquires the subsystem identifier and the target IDC of the DCN to be deployed, and acquires target configuration information according to the subsystem identifier and the target IDC; then, pulling a target SOP component from the SOP adapter according to the subsystem identifier, and packaging the target SOP component into a JAR packet; when the application is started, the application system receives a subsystem identifier of a DCN to be deployed and target configuration information and a JAR packet which are sent by a target IDC of a packaging system; and then loading parameters and target configuration information of the SOP component corresponding to the JAR packet so as to deploy the parameters and the target configuration information to the target IDC. By the mode, when different subsystems in different DCN areas are deployed on a multi-product line, multiple deployments of one set of codes can be realized without repeated development by directly acquiring target configuration information (including some configuration parameters, GIT engineering codes and the like). Meanwhile, different SOP components are expanded through SOP packaging, and then the target SOP component can be directly pulled during deployment, so that self-adaptation of the SOP component is realized, and repeated construction of a product function module is avoided. In addition, the strategy constructor is used for realizing the automatic adaptation of the docking functions of different docking systems so as to deploy the docking functions to the corresponding target IDC, thereby further reducing the deployment time and cost of the DCN and improving the deployment efficiency of the DCN. Through the self-adaption strategy, a set of code multi-deployment scheme under a distributed architecture multi-DCN system can be realized, so that the deployment time and cost of the DCN can be reduced, and the deployment efficiency of the DCN is improved.
The invention also provides a DCN system.
The data center node deployment system comprises: packaging system and application system still include: a memory, a processor, and a DCN deployment program stored on the memory and executable on the processor, the DCN deployment program when executed by the processor implementing the steps of the data center node deployment method as described above. The specific implementation process is basically the same as that of each embodiment of the data center node deployment method, and is not described herein again.
The invention also provides a data center node deployment device.
In this embodiment, the data center node deployment apparatus includes:
the system comprises an acquisition module, a configuration module and a configuration module, wherein the acquisition module is used for acquiring a subsystem identifier and a target IDC of the DCN to be deployed and acquiring target configuration information according to the subsystem identifier and the target IDC;
the packaging module is used for pulling a target SOP component from the SOP adapter according to the subsystem identifier and packaging the target SOP component into a JAR packet;
and the sending module is used for sending the target configuration information and the JAR packet to an application system when the application is started so that the application system can load the parameters of the SOP component corresponding to the JAR packet and the target configuration information to deploy the parameters into the target IDC.
Further, the obtaining module comprises:
the first obtaining unit is used for obtaining a subsystem identifier and a target IDC of the DCN to be deployed and obtaining initial configuration information according to the subsystem identifier;
the first determining unit is used for acquiring a subsystem variable according to the subsystem identifier and determining system configuration information according to the subsystem identifier, the subsystem variable and the initial configuration information;
the second determining unit is used for acquiring IDC variables according to the target IDC and determining IDC configuration information according to the target IDC, the IDC variables and the initial configuration information; wherein the target configuration information comprises the system configuration information and the IDC configuration information.
Further, the sending module includes:
the second obtaining unit is used for obtaining a corresponding version address of the JAR packet from a preset attribute label of a preset file of the JAR packet when the application is started;
and the sending unit is used for sending the target configuration information and the version address corresponding to the JAR packet to an application system so that the application system can load the parameters of the corresponding SOP component based on the version address corresponding to the JAR packet and load the target configuration information so as to deploy the target configuration information to the target IDC.
Further, the target configuration information includes engineering code, system parameters, scripts, and environment variables.
The function implementation of each module in the data center node deployment apparatus corresponds to each step in the first data center node deployment method embodiment, and the function and implementation process thereof are not described in detail here.
The present invention also provides a computer-readable storage medium, on which a DCN deployment program is stored, which, when executed by a processor, implements the steps of the first data center node deployment method according to any one of the above embodiments.
The specific embodiment of the computer-readable storage medium of the present invention is basically the same as the embodiments of the first data center node deployment method described above, and details are not described herein.
The present invention further provides a computer-readable storage medium, having a DCN deployment program stored thereon, where the DCN deployment program, when executed by a processor, implements the steps of the second data center node deployment method according to any one of the above embodiments.
The specific embodiment of the computer-readable storage medium of the present invention is substantially the same as the embodiments of the second data center node deployment method, and is not described herein again.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or system. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or system that comprises the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) as described above and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.

Claims (10)

1. A data center node deployment method is applied to a packaging system, and comprises the following steps:
the packaging system acquires a subsystem identifier of a DCN (data center node) to be deployed and a target Internet Data Center (IDC), and acquires target configuration information according to the subsystem identifier and the target IDC;
pulling a target SOP component from a standard operation program SOP adapter according to the subsystem identifier, and packaging the target SOP component into a JAR packet;
and when the application is started, sending the target configuration information and the JAR packet to an application system, so that the application system loads the parameters of the SOP component corresponding to the JAR packet and the target configuration information to deploy the parameters to the target IDC.
2. The data center node deployment method of claim 1, wherein the packaging system obtains a subsystem identifier and a target IDC of a DCN to be deployed, and the step of obtaining target configuration information according to the subsystem identifier and the target IDC comprises:
the packaging system acquires a subsystem identifier and a target IDC of a DCN to be deployed, and acquires initial configuration information according to the subsystem identifier;
acquiring a subsystem variable according to the subsystem identification, and determining to obtain system configuration information according to the subsystem identification, the subsystem variable and the initial configuration information;
acquiring IDC variables according to the target IDC, and determining IDC configuration information according to the target IDC, the IDC variables and the initial configuration information; wherein the target configuration information comprises the system configuration information and the IDC configuration information.
3. The data center node deployment method of claim 1, wherein the step of sending the target configuration information and the JAR packet to an application system when an application is started, so that the application system loads parameters of SOP components corresponding to the JAR packet and the target configuration information, and deploys the parameters and the target configuration information to the target IDC, comprises:
when the application is started, acquiring a version address corresponding to the JAR packet from a preset attribute label of a preset file of the JAR packet;
and sending the target configuration information and the version address corresponding to the JAR packet to an application system, so that the application system loads the parameters of the corresponding SOP component based on the version address corresponding to the JAR packet, and loads the target configuration information to deploy the target configuration information to the target IDC.
4. The data center node deployment method of any one of claims 1 to 3, wherein the target configuration information comprises engineering code, system parameters, scripts, and environmental variables.
5. A data center node deployment method is applied to a data center node deployment system, the data center node deployment system comprises a packaging system and an application system, and the data center node deployment method comprises the following steps:
the packaging system acquires a subsystem identifier and a target IDC of a DCN to be deployed, and acquires target configuration information according to the subsystem identifier and the target IDC;
the packaging system pulls a target SOP component from the SOP adapter according to the subsystem identifier and packages the target SOP component into a JAR packet;
when the application is started, the application system receives target configuration information and JAR packets which are sent by the packaging system based on the subsystem identifier of the DCN to be deployed and the target IDC;
and the application system loads the parameters of the SOP component corresponding to the JAR packet and the target configuration information so as to deploy the parameters into the target IDC.
6. The data center node deployment method of claim 5, wherein the step of the application system loading the parameters of the SOP component corresponding to the JAR packet and the target configuration information to deploy into the target IDC comprises:
the application system receives an external system identifier and an operation category sent by an external system;
the application system obtains a strategy constructor through a strategy adapter according to the external system identification and the operation type adaptation;
and the application system loads the parameters of the SOP component corresponding to the JAR packet and the target configuration information based on the policy constructor so as to deploy the parameters and the target configuration information to the target IDC corresponding to the external system identifier.
7. The data center node deployment method of claim 5, wherein the step of the application system loading the parameters of the SOP component corresponding to the JAR packet and the target configuration information to deploy into the target IDC comprises:
the application system acquires the current operation type;
the application system obtains a strategy constructor through a strategy adapter according to the subsystem identification and the current operation type adaptation;
and the application system loads parameters of SOP components corresponding to the JAR packet and the target configuration information based on the policy constructor so as to deploy the parameters and the target configuration information to a target IDC to which a target external docking system corresponding to the subsystem identification and the current operation type belongs.
8. A data center node deployment device is characterized in that the data center node deployment device comprises:
the system comprises an acquisition module, a configuration module and a configuration module, wherein the acquisition module is used for acquiring a subsystem identifier and a target IDC of the DCN to be deployed and acquiring target configuration information according to the subsystem identifier and the target IDC;
the packaging module is used for pulling a target SOP component from the SOP adapter according to the subsystem identifier and packaging the target SOP component into a JAR packet;
and the sending module is used for sending the target configuration information and the JAR packet to an application system when the application is started so that the application system can load the parameters of the SOP component corresponding to the JAR packet and the target configuration information to deploy the parameters into the target IDC.
9. A data center node deployment system, the data center node deployment system comprising: packaging system and application system still include: memory, a processor and a DCN deployment program stored on the memory and executable on the processor, the DCN deployment program when executed by the processor implementing the steps of the data center node deployment method of any of claims 5 to 7.
10. A computer-readable storage medium, having stored thereon a DCN deployment program that, when executed by a processor, performs the steps of the data center node deployment method of any one of claims 1 to 4 or 5 to 7.
CN202011644284.XA 2020-12-30 2020-12-30 Data center node deployment method, device and system and computer storage medium Active CN112698839B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011644284.XA CN112698839B (en) 2020-12-30 2020-12-30 Data center node deployment method, device and system and computer storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011644284.XA CN112698839B (en) 2020-12-30 2020-12-30 Data center node deployment method, device and system and computer storage medium

Publications (2)

Publication Number Publication Date
CN112698839A true CN112698839A (en) 2021-04-23
CN112698839B CN112698839B (en) 2024-04-12

Family

ID=75514304

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011644284.XA Active CN112698839B (en) 2020-12-30 2020-12-30 Data center node deployment method, device and system and computer storage medium

Country Status (1)

Country Link
CN (1) CN112698839B (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114281428A (en) * 2021-12-28 2022-04-05 挂号网（杭州）科技有限公司 Configuration method of service dictionary, electronic equipment and storage medium
CN114579193A (en) * 2022-03-08 2022-06-03 国泰新点软件股份有限公司 Multi-system loading method, device, equipment and storage medium
CN114860349A (en) * 2022-07-06 2022-08-05 深圳华锐分布式技术股份有限公司 Data loading method, device, equipment and medium

Citations (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU2004322201A1 (en) * 2004-08-12 2006-02-16 Fujitsu Limited Java applet, jar file creating method, jar file creating program, and jar file creating device
CN106201481A (en) * 2016-06-30 2016-12-07 传线网络科技（上海）有限公司 Assembly management method and apparatus in application development system
CN106990960A (en) * 2017-03-28 2017-07-28 阿里巴巴集团控股有限公司 Code dispositions method and device
US20180121182A1 (en) * 2016-10-31 2018-05-03 Servicenow, Inc. System and Method for Creating and Deploying A Release Package
CN109086051A (en) * 2018-06-29 2018-12-25 平安科技（深圳）有限公司 Application component dispositions method, device and computer storage medium
CN109542462A (en) * 2018-10-17 2019-03-29 平安科技（深圳）有限公司 A kind of system environments dispositions method, storage medium and server
CN109597655A (en) * 2017-09-28 2019-04-09 华为技术有限公司 Configure the method and device of application program
CN109871208A (en) * 2019-01-04 2019-06-11 平安科技（深圳）有限公司 Software systems generation method, device, computer readable storage medium and server
CN110109680A (en) * 2019-05-14 2019-08-09 重庆商勤科技有限公司 Using dispositions method, device and apply dissemination method, server, storage medium
CN110225138A (en) * 2019-06-25 2019-09-10 深圳前海微众银行股份有限公司 A kind of distributed structure/architecture
CN110572436A (en) * 2019-08-12 2019-12-13 浙江讯盟科技有限公司 Multi-place cross-cluster server deployment method and system
CN111078200A (en) * 2019-11-29 2020-04-28 深圳前海微众银行股份有限公司 Task construction method, device, equipment, medium and system
CN111666099A (en) * 2020-06-12 2020-09-15 江苏云柜网络技术有限公司 Application service publishing system
CN111767092A (en) * 2020-06-30 2020-10-13 深圳前海微众银行股份有限公司 Job execution method, device, system and computer readable storage medium

Patent Citations (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU2004322201A1 (en) * 2004-08-12 2006-02-16 Fujitsu Limited Java applet, jar file creating method, jar file creating program, and jar file creating device
CN106201481A (en) * 2016-06-30 2016-12-07 传线网络科技（上海）有限公司 Assembly management method and apparatus in application development system
US20180121182A1 (en) * 2016-10-31 2018-05-03 Servicenow, Inc. System and Method for Creating and Deploying A Release Package
CN106990960A (en) * 2017-03-28 2017-07-28 阿里巴巴集团控股有限公司 Code dispositions method and device
CN109597655A (en) * 2017-09-28 2019-04-09 华为技术有限公司 Configure the method and device of application program
CN109086051A (en) * 2018-06-29 2018-12-25 平安科技（深圳）有限公司 Application component dispositions method, device and computer storage medium
CN109542462A (en) * 2018-10-17 2019-03-29 平安科技（深圳）有限公司 A kind of system environments dispositions method, storage medium and server
CN109871208A (en) * 2019-01-04 2019-06-11 平安科技（深圳）有限公司 Software systems generation method, device, computer readable storage medium and server
CN110109680A (en) * 2019-05-14 2019-08-09 重庆商勤科技有限公司 Using dispositions method, device and apply dissemination method, server, storage medium
CN110225138A (en) * 2019-06-25 2019-09-10 深圳前海微众银行股份有限公司 A kind of distributed structure/architecture
CN110572436A (en) * 2019-08-12 2019-12-13 浙江讯盟科技有限公司 Multi-place cross-cluster server deployment method and system
CN111078200A (en) * 2019-11-29 2020-04-28 深圳前海微众银行股份有限公司 Task construction method, device, equipment, medium and system
CN111666099A (en) * 2020-06-12 2020-09-15 江苏云柜网络技术有限公司 Application service publishing system
CN111767092A (en) * 2020-06-30 2020-10-13 深圳前海微众银行股份有限公司 Job execution method, device, system and computer readable storage medium

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HAN QI: "Data center network architecture in cloud computing：review，taxonomy，and open research issues", 《JOURNAL OF ZHEJIANG UNIVERSITY SCIENCE C》 *
腾讯云数据库: "亿级客户和PB级数据规模的金融级数据库实战历程", Retrieved from the Internet <URL:《https://www.yisu.com/zixun/267941.html》> *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114281428A (en) * 2021-12-28 2022-04-05 挂号网（杭州）科技有限公司 Configuration method of service dictionary, electronic equipment and storage medium
CN114281428B (en) * 2021-12-28 2024-06-04 挂号网（杭州）科技有限公司 Service dictionary configuration method, electronic equipment and storage medium
CN114579193A (en) * 2022-03-08 2022-06-03 国泰新点软件股份有限公司 Multi-system loading method, device, equipment and storage medium
CN114579193B (en) * 2022-03-08 2024-01-12 国泰新点软件股份有限公司 Multi-system loading method, device, equipment and storage medium
CN114860349A (en) * 2022-07-06 2022-08-05 深圳华锐分布式技术股份有限公司 Data loading method, device, equipment and medium
CN114860349B (en) * 2022-07-06 2022-11-08 深圳华锐分布式技术股份有限公司 Data loading method, device, equipment and medium

Also Published As

Publication number Publication date
CN112698839B (en) 2024-04-12

Similar Documents

Publication Publication Date Title
CN112698839A (en) Data center node deployment method, device and system and computer storage medium
EP2608585B1 (en) Method, device and system for triggering terminal operation
CN112202920B (en) Vehicle-mounted system upgrading method and device
CN109213533B (en) Advertisement SDK dynamic loading method, device and terminal
CN111651169B (en) Block chain intelligent contract operation method and system based on web container
CN111399860B (en) Light application deployment method, light application deployment device, computer equipment and storage medium
CN109039730B (en) Server cluster and server cluster configuration information management method
CN111078553B (en) Data development task testing method and device, computer equipment and storage medium
CN113722048B (en) IAST agent automatic deployment method and system in k8s
CN109766123B (en) Application program packaging method and device
CN113138768B (en) Application package generation method and device, electronic equipment and readable storage medium
WO2017045345A1 (en) Resource management method and apparatus, and multi-mode soft base station unified network management
CN111158689A (en) Cross-system UI application generation method, device and computer-readable storage medium
CN112685102B (en) Gateway plug-in hot loading method, device, equipment and medium
CN114466070A (en) Middleware system, service request processing method, electronic device, and storage medium
CN110399161B (en) Mapping relation generation method, calling method and device
CN113268272A (en) Application delivery method, device and system based on private cloud
CN111857791A (en) Embedded product maintenance method and device, electronic equipment and storage medium
CN111198721A (en) Application program running method and device
CN113703827B (en) Dependency package management method, system, equipment and computer readable storage medium
US20220278895A1 (en) Network resource access intermediary system based on resource plug-ins and processing method therefor
CN113312063B (en) Kubernetes-based software system rapid deployment and upgrade method
CN114116051A (en) Processing method, device, equipment and storage medium based on neural network model
CN113596958B (en) Terminal equipment data interaction method, system, equipment and storage medium
CN115390862A (en) Application deployment method and device

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