CN114741092A - Multi-tenant deployment method, device, equipment and storage medium for traditional application - Google Patents
Multi-tenant deployment method, device, equipment and storage medium for traditional application Download PDFInfo
- Publication number
- CN114741092A CN114741092A CN202210421881.9A CN202210421881A CN114741092A CN 114741092 A CN114741092 A CN 114741092A CN 202210421881 A CN202210421881 A CN 202210421881A CN 114741092 A CN114741092 A CN 114741092A
- Authority
- CN
- China
- Prior art keywords
- tenant
- deployment
- deployment package
- micro
- application
- 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 50
- 238000012545 processing Methods 0.000 claims abstract description 12
- 230000015654 memory Effects 0.000 claims description 23
- 230000005540 biological transmission Effects 0.000 claims description 6
- 238000004590 computer program Methods 0.000 claims description 6
- 238000005516 engineering process Methods 0.000 abstract description 14
- 238000012423 maintenance Methods 0.000 abstract description 10
- 238000011161 development Methods 0.000 abstract description 4
- 238000007726 management method Methods 0.000 description 34
- 238000002955 isolation Methods 0.000 description 11
- 230000004048 modification Effects 0.000 description 9
- 238000012986 modification Methods 0.000 description 9
- 230000006870 function Effects 0.000 description 8
- 241000380131 Ammophila arenaria Species 0.000 description 6
- 230000008569 process Effects 0.000 description 6
- 238000013473 artificial intelligence Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 238000004891 communication Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 239000004973 liquid crystal related substance Substances 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000009466 transformation Effects 0.000 description 2
- 101001072091 Homo sapiens ProSAAS Proteins 0.000 description 1
- 102100036366 ProSAAS Human genes 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000013135 deep learning Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000010801 machine learning Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000003058 natural language processing Methods 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000013515 script Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
- G06F8/63—Image based installation; Cloning; Build to order
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The invention relates to a data processing technology, and discloses a multi-tenant deployment method for traditional application, which comprises the following steps: registering relevant information of the application to a preset micro-service deployment package template to obtain an application micro-service deployment package template; the method comprises the steps that a tenant unique identification is loaded to an application micro-service deployment package template, a tenant deployment package and an object information table are generated, the tenant deployment package is stored in a preset deployment package management warehouse, and the object information table is stored in a preset object storage library; acquiring a user deployment space corresponding to the tenant unique identifier as a space to be deployed according to the tenant unique identifier in the tenant deployment package; and deploying the mirror image deployment parameters to the space to be deployed through the tenant deployment package. The invention also relates to a block chain technology, and the preset micro-service deployment package template is stored in the block chain. The invention can solve the problems that the operation and maintenance cost is high, the data of each tenant are not intercommunicated, the operation statistics needs to assemble the data of each system, the extra development workload is large and the like in the prior art.
Description
Technical Field
The present invention relates to the field of data processing, and in particular, to a method, an apparatus, a device, and a storage medium for multi-tenant deployment of a legacy application.
Background
Under the great trend of cloud SAAS application, how to convert a traditional application system into multi-tenant application with low cost and high efficiency to realize resource isolation and data isolation is a main problem for traditional application transformation. For multi-tenant deployment of traditional applications, there are two main current solutions:
the first is logically implemented multi-tenancy. Mainly through adding the tenant ID field on all tables of the application database, in the business of adding, deleting, modifying and checking, through adding the tenant ID field to filter, realize the data isolation of different tenants; by changing the stateful application into the stateless application, the application has the distributed transverse expansion capability, and the resource isolation is realized to a certain degree. The logically realized multi-tenant solution has the advantages that the system after modification is simple in deployment structure, basically the same as that before modification, and data are stored in the same database table, so that operation statistics is facilitated; the system has the defects that the workload of system transformation is large, all functions of the system are involved, a single database has performance bottleneck under the condition that more and more tenants exist, the database can be optimized only in a table and database dividing mode, and the complexity of the system is increased.
The second is to achieve complete physical isolation using container technology. Deployment is accomplished through kubernets scripts on kubernets clusters by modifying the application into a docker mirror. The solution for realizing complete physical isolation by using the container technology has the advantages that only a deployment architecture needs to be modified, the application function does not need to be modified, and the development cost is low; the method has the disadvantages that under the condition that more and more tenants are needed, more and more systems needing operation and maintenance are needed, the operation and maintenance cost is high, data of each tenant are not intercommunicated due to complete physical isolation, operation statistics needs to gather data of each system, and extra development workload exists.
Disclosure of Invention
The invention provides a multi-tenant deployment method, a device, equipment and a storage medium for traditional application, and mainly aims to solve the problems that in the prior art, complete physical isolation is realized by using a container technology, under the condition that more and more tenants are provided, more and more systems needing operation and maintenance are provided, the operation and maintenance cost is high, due to the complete physical isolation, the data of each tenant are not intercommunicated, the operation statistics needs to be gathered on the data of each system, the extra development workload is large, and the like.
In a first aspect, to achieve the above object, the present invention provides a method for multi-tenant deployment of legacy applications, where the method includes:
according to the acquired tenant deployment instruction, registering relevant information of the application to a corresponding preset micro-service deployment package template, and establishing a corresponding relation between the application and the micro-service to obtain an application micro-service deployment package template;
correspondingly loading the unique tenant identification in the acquired tenant micro-service request information to the application micro-service deployment package template, generating a tenant deployment package and an object information table corresponding to the tenant deployment package, storing the tenant deployment package to a preset deployment package management warehouse and storing the object information table to a preset object repository; the object information table comprises a tenant unique identifier and relevant information of a tenant deployment package corresponding to the tenant unique identifier; the tenant deployment package comprises a tenant unique identifier, an application name field and a micro-service name field;
acquiring a user deployment space corresponding to the tenant unique identifier from a preset deployment container cluster as a space to be deployed according to the tenant unique identifier in the tenant deployment package;
and acquiring mirror image deployment parameters matched with the tenant deployment package in advance from a preset program data mirror image warehouse, and deploying the mirror image deployment parameters to the space to be deployed through the tenant deployment package.
In a second aspect, to solve the above problem, the present invention further provides a multi-tenant deployment apparatus for legacy applications, including:
the registration module is used for registering relevant information of the application to a corresponding preset micro-service deployment package template according to the acquired tenant deployment instruction, and establishing a corresponding relation between the application and the micro-service to obtain an application micro-service deployment package template;
the loading module is used for correspondingly loading the unique tenant identification in the acquired tenant micro-service request information to the application micro-service deployment package template, generating a tenant deployment package and an object information table corresponding to the tenant deployment package, storing the tenant deployment package to a preset deployment package management warehouse and storing the object information table to a preset object storage library; the object information table comprises a tenant unique identifier and relevant information of a tenant deployment package corresponding to the tenant unique identifier; the tenant deployment package comprises a tenant unique identifier, an application name field and a micro-service name field;
the acquisition module is used for acquiring a user deployment space corresponding to the unique tenant identification from a preset deployment container cluster as a space to be deployed according to the unique tenant identification in the tenant deployment package;
and the deployment module is used for acquiring mirror deployment parameters matched with the tenant deployment package in advance from a preset program data mirror warehouse and deploying the mirror deployment parameters to the space to be deployed through the tenant deployment package.
In a third aspect, to solve the above problem, the present invention further provides an electronic apparatus, including:
at least one processor; and (c) a second step of,
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the steps of the multi-tenant deployment method of legacy applications as described above.
In a fourth aspect, to solve the above problem, the present invention further provides a computer-readable storage medium storing a computer program, which when executed by a processor implements the multi-tenant deployment method of the legacy application as described above.
According to the multi-tenant deployment method, the device, the equipment and the storage medium of the traditional application, the micro-service deployment package template is preset, the corresponding relation between the application and the micro-service is established to obtain the application micro-service deployment package template, and the tenant unique identification in the tenant micro-service request information is correspondingly loaded to the application micro-service deployment package template, so that the tenant deployment package is automatically generated; the subsequent operation and maintenance of the tenant deployment package do not need manual maintenance, and the method is suitable for a multi-tenant scene; the object information table generated according to the tenant deployment package is stored in the preset object repository, so that the association relationship between the tenant and the application and the micro service is stored, and the searching and the subsequent maintenance are facilitated; the tenant deployment package change only needs to update the deployment package template once, the deployment package of each tenant does not need to be updated once, the system automatically updates the deployment package, and labor cost is reduced.
Drawings
Fig. 1 is a flowchart illustrating a multi-tenant deployment method for a legacy application according to an embodiment of the present invention;
fig. 2 is a block diagram of a multi-tenant deployment apparatus for a legacy application according to an embodiment of the present invention;
fig. 3 is a schematic internal structural diagram of an electronic device implementing a multi-tenant deployment method for a legacy application according to an embodiment of 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.
The embodiment of the application can acquire and process related data based on an artificial intelligence technology. Among them, Artificial Intelligence (AI) is a theory, method, technique and application system that simulates, extends and expands human Intelligence using a digital computer or a machine controlled by a digital computer, senses the environment, acquires knowledge and uses the knowledge to obtain the best result.
The artificial intelligence infrastructure generally includes technologies such as sensors, dedicated artificial intelligence chips, cloud computing, distributed storage, big data processing technologies, operation/interaction systems, mechatronics, and the like. The artificial intelligence software technology mainly comprises a computer vision technology, a robot technology, a biological recognition technology, a voice processing technology, a natural language processing technology, machine learning/deep learning and the like.
The invention provides a multi-tenant deployment method of traditional application. Fig. 1 is a schematic flowchart of a multi-tenant deployment method for a legacy application according to an embodiment of the present invention. The method may be performed by an apparatus, which may be implemented by software and/or hardware.
In this embodiment, the multi-tenant deployment method for the legacy application includes:
step S110, according to the acquired tenant deployment instruction, registering relevant information of the application to a corresponding preset micro-service deployment package template, and establishing a corresponding relation between the application and the micro-service to obtain an application micro-service deployment package template.
Specifically, the application may be composed of one or more micro services according to an actual situation, and the micro services are made into mirror image deployment parameters and stored in a preset program data mirror image warehouse. In the existing multi-tenant deployment method, a programmer writes a deployment package for each tenant according to a tenant request, and then deploys mirror deployment parameters of micro services of the application requested by the tenant into a corresponding tenant deployment space. Because the user deployment package is written for each tenant, corresponding modification is also needed for subsequent modification of the application microservices, and the workload is large.
For example, the main idea of implementing multi-tenants in kubernets (container orchestration engine) is to customize independent hell chart deployment packages for each tenant, which rely on the same docker image, and differ only in configuration, including: the number of CPU cores, the number of memories, port ports, service names servicename, name space name and the like which are distributed by mirror image operation.
In order to solve the problem of large modification amount, the invention presets a micro-service deployment package template, and the preset micro-service deployment package template can comprise a port, a service name servicename, a user deployment space name namespace and the like of micro-service deployment mirror image operation distribution. Because the same host is assigned in the actual deployment process, the port, the service name (internal domain name), and the user deployment space name must be different, otherwise one of the services fails to be deployed due to conflict.
When the tenant deployment instruction is obtained, the processor obtains a corresponding preset micro-service deployment package template according to the micro-service name provided by each application, registers the relevant information of the application to the corresponding preset micro-service deployment package template, and establishes a corresponding relation between the application and the micro-service to obtain the application micro-service deployment package template. For example, the application 1 may provide three micro services, i.e., a micro service 1, a micro service 2, and a service 3, and then may obtain a preset micro service deployment package template of the micro service 1, a preset micro service deployment package template of the micro service 2, and a preset micro service deployment package template of the micro service 3. And loading relevant information of the application, such as an application name field, into three preset micro-service deployment package templates to obtain the application micro-service deployment package template.
As an optional embodiment of the present invention, before the storing a preset micro-service deployment package template in a block chain, registering relevant information of an application to a corresponding preset micro-service deployment package template according to an obtained tenant deployment instruction, and establishing a corresponding relationship between the application and a micro-service to obtain an application micro-service deployment package template, the method further includes:
creating an initial definition table directory according to a preset directory rule;
and carrying out format variable replacement processing on the initial definition table catalog based on the variables of the micro-services to obtain a preset micro-service deployment package template.
Specifically, a directory rule is preset, and an initial definition table directory is created. For example, the specification content is organized according to charts (charts), an initial definition table directory is created, and format variables are replaced in the initial definition table directory, so that preset micro-service deployment package templates of different micro-services are obtained. And carrying out format variable replacement processing on the initial definition table catalog according to the counted micro service types of all the applications to obtain a preset micro service deployment package template.
As an optional embodiment of the present invention, registering relevant information of an application to a corresponding preset microservice deployment package template according to an obtained tenant deployment instruction, and establishing a corresponding relationship between the application and a microservice to obtain an application microservice deployment package template includes:
acquiring a preset micro-service deployment package template corresponding to each application as a target micro-service deployment package template according to the name of the micro-service provided by each application;
and loading the relevant information of the application to a target micro-service deployment package template, so that a corresponding relation is established between the application and the micro-service provided by the application, and the application micro-service deployment package template is obtained.
Specifically, the name of the micro-service provided by each application is collected, and then a corresponding preset micro-service deployment package template is obtained according to the name of the micro-service corresponding to each application and is used as a target micro-service deployment package template. And then, loading relevant information of the application, such as an application name field and the like, to the target micro-service deployment package template, so that a corresponding relation is established between the application and the micro-service provided by the application, and the application micro-service deployment package template is obtained.
Step S120, correspondingly loading the tenant unique identifier in the acquired tenant micro service request information to an application micro service deployment package template, generating a tenant deployment package and an object information table corresponding to the tenant deployment package, storing the tenant deployment package to a preset deployment package management warehouse and storing the object information table to a preset object repository; the object information table comprises a tenant unique identifier and relevant information of a tenant deployment package corresponding to the tenant unique identifier; the tenant deployment package comprises a tenant unique identifier, an application name field and a micro-service name field.
Specifically, when each tenant needs to use a micro service of an application, tenant micro service request information needs to be sent to the processor, and the tenant micro service request information is collected through the tenant information management system, where the tenant micro service request information at least includes a unique identifier of the tenant (such as a tenant ID), an application name field (such as the name of application 1) for requesting renting, and a name field of a specific micro service (such as micro service 2). And correspondingly loading the unique tenant identification to the corresponding application micro-service deployment package template so as to generate a tenant deployment package, and generating a corresponding object information table according to the tenant deployment package. The tenant deployment package at least comprises a tenant unique identifier, an application name field and a micro-service name field; the object information table at least comprises the unique tenant identification and relevant information of the tenant deployment package corresponding to the unique tenant identification. Respectively storing the tenant deployment packages to a preset deployment package management warehouse to facilitate the deployment and use of subsequent deployment packages; and storing the object information table into a preset object storage library, so that subsequent information query and operation and maintenance are facilitated.
As an optional embodiment of the present invention, correspondingly loading the tenant unique identifier in the obtained tenant microservice request information to the application microservice deployment package template, generating a tenant deployment package and an object information table corresponding to the tenant deployment package, and storing the tenant deployment package in a preset deployment package management repository and storing the object information table in a preset object repository includes:
acquiring an application name field and a micro-service name field appointed in tenant micro-service request information; the tenant microservice request information comprises the following information: a tenant unique identifier, an application name field and a micro-service name field;
acquiring an application micro-service deployment package template corresponding to tenant micro-service request information according to the application name field and the micro-service name field, and taking the application micro-service deployment package template as a selected deployment package template; the application microservice deployment package template comprises an application name field and a microservice name field;
loading the unique tenant identification to the selected deployment package template to generate a tenant deployment package, and loading the unique tenant identification and relevant information of the tenant deployment package to a preset information table to generate an object information table;
storing the tenant deployment package to a preset deployment package management warehouse and storing the object information table to a preset object storage library.
Specifically, an application name field and a micro-service name field are obtained from tenant micro-service request information, an application micro-service deployment package template with the same application name field and the same micro-service name field is selected from the application micro-service deployment package template to serve as a selected deployment package template, then a tenant unique identifier is loaded to the selected deployment package template to generate a tenant deployment package, and the tenant unique identifier and relevant information of the tenant deployment package are loaded to a preset information table to generate an object information table. When a user deployment container is constructed by kubernets, the preset deployment package management warehouse can adopt a helm warehouse, some metadata about a Chart package (tenant deployment package) is contained in an index file of the helm warehouse, a group of K8S resources can be packaged and uniformly managed, and the management method is an optimal mode for searching, sharing and using software constructed for kubernets.
Step S130, according to the unique tenant identification in the tenant deployment package, obtaining a user deployment space corresponding to the unique tenant identification from a preset deployment container cluster as a space to be deployed.
Specifically, the tenant deployment package is stored in a preset deployment package management warehouse, in the preset deployment package management warehouse, each tenant has a plurality of tenant deployment packages according to different micro services requested to be used, for example, the tenant deployment package corresponding to tenant1 may be represented as tenant 1-release, a user of the tenant requests to use two micro services, namely, a service a and a service B, and a sequence number of a corresponding tenant deployment space is 1, which may be represented as that the tenant 1-release includes, below, Chart-a-tenant1 and Chart-B-tenant1, where tenant1 corresponds to a user deployment space in a preset deployment container cluster. The building of the corresponding relation between the tenant deployment package and the tenant deployment space can be realized through the helm warehouse and the Kubernets cluster. And acquiring a user deployment space corresponding to the unique tenant identification from a preset deployment container cluster as a space to be deployed.
As an optional embodiment of the present invention, before acquiring, according to a tenant unique identifier in a tenant deployment package, a user deployment space corresponding to the tenant unique identifier from a preset deployment container cluster as a space to be deployed, the method further includes:
creating a user deployment space for each tenant according to the tenant micro-service request information;
and storing the user deployment space into a preset container through a container arrangement engine to obtain a preset deployment container cluster.
Specifically, according to the acquired tenant microservice request information, a user deployment space is created for each tenant in advance, and the user deployment space can be stored into a preset container by adopting a kubernets container arrangement engine to obtain a preset deployment container cluster. And facilitating subsequent application microservices for the tenants.
Step S140, mirror image deployment parameters which are matched with the tenant deployment package in advance are obtained from a preset program data mirror image warehouse, and the mirror image deployment parameters are deployed to the space to be deployed through the tenant deployment package.
Specifically, for each micro service provided by each application, a corresponding mirror deployment parameter is generated in advance, and the corresponding mirror deployment parameter is deployed to the space to be deployed through the tenant deployment package.
As an optional embodiment of the present invention, acquiring a mirror deployment parameter that is pre-matched with a tenant deployment package from a preset program data mirror repository, and deploying the mirror deployment parameter to the space to be deployed by using the tenant deployment package includes:
acquiring mirror image deployment parameters corresponding to the tenant deployment package from a preset program data mirror image warehouse according to an application name field and a micro-service name field in the tenant deployment package; the preset program data mirror image warehouse stores mirror image deployment parameters of the micro-services provided by the application;
a tenant deployment package in the deployment package management warehouse establishes data transmission with a space to be deployed through a data interface; and deploying the mirror image deployment parameters to the space to be deployed.
Specifically, the mirror image deployment parameters in the preset program data mirror image warehouse correspond to corresponding application name fields and micro-service name fields, so that the mirror image deployment parameters corresponding to the tenant deployment package can be acquired according to the application name fields and the micro-service name fields in the tenant deployment package, and the tenant deployment package in the deployment package management warehouse establishes data transmission with the space to be deployed through a data interface (such as an API interface); and deploying the mirror image deployment parameters to the space to be deployed. The application of each tenant is deployed into the deployment space of the corresponding tenant, and the data isolation effect is achieved.
As an optional embodiment of the present invention, after acquiring a mirror image deployment parameter pre-matched with a tenant deployment package from a preset program data mirror image warehouse, and deploying the mirror image deployment parameter to a space to be deployed by the tenant deployment package, the method further includes:
according to the acquired data updating information of the micro service, positioning an updating identifier of the micro service;
updating the variables of the micro-services in the tenant deployment package corresponding to the micro-services according to the update identification of the micro-services and the name fields of the micro-services to obtain an updated tenant deployment package, and updating the object information table corresponding to the updated tenant deployment package according to the update content of the updated tenant deployment package to obtain a new object information table;
uploading the updated tenant deployment package to a preset deployment package management warehouse, and replacing the updated tenant deployment package with the corresponding previous tenant deployment package; and uploading the new object information table to a preset object repository, and overlaying the previous object information table with the new object information table.
Specifically, when the microservice program is updated or the data is updated, data update information of the microservice is generated, the updated content is located, and the update identifier is generated. Finding the updated microservice according to the name field of the microservice with data update indicated in the data update information of the microservice, and positioning the updated data of the microservice; updating the variables of the micro-service in the tenant deployment package corresponding to the micro-service to obtain an updated tenant deployment package, and updating the object information table corresponding to the updated tenant deployment package according to the updating content of the updated tenant deployment package to obtain a new object information table; uploading the updated tenant deployment package to a preset deployment package management warehouse, and replacing the updated tenant deployment package with the corresponding previous tenant deployment package; and uploading the new object information table to a preset object repository, and overlaying the previous object information table with the new object information table. In the updating process, if the tenant information changes, the relevant information (for example, the unique tenant identification) of the tenant in the tenant deployment package can be updated by the same method, and then the object information table is updated according to the updated deployment package.
Fig. 2 is a functional block diagram of a multi-tenant deployment apparatus of a conventional application according to an embodiment of the present invention.
The multi-tenant deployment apparatus 200 of the conventional application of the present invention can be installed in an electronic device. According to the implemented functions, the multi-tenant deployment apparatus of the legacy application may include a registration module 210, a loading module 220, an obtaining module 230, and a deployment module 240. A module according to the present invention, which may also be referred to as a unit, refers to a series of computer program segments that can be executed by a processor of an electronic device and that can perform a fixed function, and that are stored in a memory of the electronic device.
In the present embodiment, the functions regarding the respective modules/units are as follows:
the registering module 210 is configured to register, according to the obtained tenant deployment instruction, related information of the application to a corresponding preset microservice deployment package template, and establish a corresponding relationship between the application and the microservice to obtain an application microservice deployment package template.
Specifically, the application may be composed of one or more micro services according to an actual situation, and the micro services are made into mirror image deployment parameters and stored in a preset program data mirror image warehouse. In the existing multi-tenant deployment method, a programmer writes a deployment package for each tenant according to a tenant request, and then deploys mirror deployment parameters of micro services of the application requested by the tenant into a corresponding tenant deployment space. Because the user deployment package is written for each tenant, corresponding modification is also needed for subsequent modification of the application microservices, and the workload is large.
For example, the main idea of implementing multi-tenants in kubernets (container orchestration engine) is to customize independent hell chart deployment packages for each tenant, which rely on the same docker image, and differ only in configuration, including: the number of CPU cores, the number of memories, port ports, service names servicename, name space name and the like which are distributed by mirror image operation.
In order to solve the problem of large modification amount, the invention presets a micro-service deployment package template, and the preset micro-service deployment package template can comprise a port, a service name servicename, a user deployment space name namespace and the like of micro-service deployment mirror image operation distribution. Because the ports, service names (internal domain names) and user deployment space names are distributed to the same host in the actual deployment process, otherwise, one of the services fails to be deployed due to conflict.
When the tenant deployment instruction is obtained, the processor obtains a corresponding preset micro-service deployment package template according to the micro-service name provided by each application through the registration module 210, registers the relevant information of the application to the corresponding preset micro-service deployment package template, and establishes a corresponding relationship between the application and the micro-service to obtain the application micro-service deployment package template. For example, the application 1 may provide three micro services, i.e., a micro service 1, a micro service 2, and a service 3, and then may obtain a preset micro service deployment package template of the micro service 1, a preset micro service deployment package template of the micro service 2, and a preset micro service deployment package template of the micro service 3. And loading relevant information of the application, such as an application name field, into three preset micro-service deployment package templates to obtain the application micro-service deployment package template.
As an optional embodiment of the present invention, the multi-tenant deployment apparatus 200 for legacy application further includes: a catalog creation module and a format variable replacement module (not shown in the figure). Wherein,
the catalog creating module is used for creating an initial definition list catalog according to a preset catalog rule;
and the format variable replacing module is used for carrying out format variable replacing processing on the initial definition table catalog based on the variables of the micro-service to obtain a preset micro-service deployment package template.
Specifically, the initial definition table directory is created through the directory creation module according to the preset directory rule. For example, the specification content is organized according to charts (charts), an initial definition table directory is created, and format variables are replaced in the initial definition table directory through a format variable replacement module, so that preset micro-service deployment package templates of different micro-services are obtained. And carrying out format variable replacement processing on the initial definition table catalog according to the counted micro service types of all the applications to obtain a preset micro service deployment package template.
As an alternative embodiment of the present invention, the registration module 210 further includes a target microservice deployment package template obtaining unit and an information registration unit (not shown in the figure). Wherein,
the target micro-service deployment package template acquisition unit is used for acquiring a preset micro-service deployment package template corresponding to each application as a target micro-service deployment package template according to the name of the micro-service provided by each application;
and the information registration unit is used for loading the relevant information of the application to the target micro-service deployment package template so as to establish a corresponding relation between the application and the micro-service provided by the application and obtain the application micro-service deployment package template.
Specifically, the name of the micro-service provided by each application is collected, and then the corresponding preset micro-service deployment package template is obtained by the target micro-service deployment package template obtaining unit according to the name of the micro-service corresponding to each application and is used as the target micro-service deployment package template. And loading relevant information of the application, such as an application name field and the like, to the target micro-service deployment package template through the information registration unit, so that a corresponding relation is established between the application and the micro-service provided by the application, and the application micro-service deployment package template is obtained.
The loading module 220 is configured to correspondingly load the tenant unique identifier in the acquired tenant microservice request information to the application microservice deployment package template, generate a tenant deployment package and an object information table corresponding to the tenant deployment package, store the tenant deployment package in a preset deployment package management warehouse, and store the object information table in a preset object repository; the object information table comprises a tenant unique identifier and relevant information of a tenant deployment package corresponding to the tenant unique identifier; the tenant deployment package comprises a tenant unique identifier, an application name field and a micro-service name field.
Specifically, when each tenant needs to use a certain micro service of a certain application, tenant micro service request information needs to be sent to the processor, and the tenant micro service request information is collected by the tenant information management system, and at least a unique identifier of the tenant (such as a tenant ID), an application name field requesting lease (such as the name of application 1), and a name field of a specific micro service (such as micro service 2) should be included in the tenant micro service request information. The tenant unique identifier is correspondingly loaded to the corresponding application microservice deployment package template through the loading module 220, so that a tenant deployment package is generated, and a corresponding object information table is generated according to the tenant deployment package. The tenant deployment package at least comprises a tenant unique identifier, an application name field and a micro-service name field; the object information table at least comprises the unique tenant identification and relevant information of the tenant deployment package corresponding to the unique tenant identification. Respectively storing the tenant deployment packages to a preset deployment package management warehouse to facilitate the deployment and use of subsequent deployment packages; and storing the object information table into a preset object storage library, so that subsequent information query and operation and maintenance are facilitated.
As an alternative embodiment of the present invention, the loading module 220 further includes a field obtaining unit, a template selecting unit, an identifier loading unit and a storing unit (not shown in the figure). Wherein,
the field acquisition unit is used for acquiring an application name field and a micro-service name field specified in tenant micro-service request information; the tenant microservice request information comprises the following information: a tenant unique identifier, an application name field and a micro-service name field;
the template selection unit is used for acquiring an application micro-service deployment package template corresponding to tenant micro-service request information according to the application name field and the micro-service name field and taking the application micro-service deployment package template as a selected deployment package template; the application microservice deployment package template comprises an application name field and a microservice name field;
the identification loading unit is used for loading the unique tenant identification to the selected deployment package template to generate a tenant deployment package, and loading the unique tenant identification and relevant information of the tenant deployment package into a preset information table to generate an object information table;
and the storage unit is used for storing the tenant deployment package to a preset deployment package management warehouse and storing the object information table to a preset object storage library.
Specifically, an application name field and a micro-service name field are acquired from tenant micro-service request information through a field acquisition unit, an application micro-service deployment package template with the same application name field and micro-service name field is selected from the application micro-service deployment package template through a template selection unit to serve as a selected deployment package template, a tenant unique identifier is loaded to the selected deployment package template through an identifier loading unit to generate a tenant deployment package, and related information of the tenant unique identifier and the tenant deployment package is loaded to a preset information table to generate an object information table. And storing the tenant deployment package to a preset deployment package management warehouse and storing the object information table to a preset object storage library through a storage unit.
When a user deployment container is constructed by kubernets, the preset deployment package management warehouse can adopt a helm warehouse, some metadata about a Chart package (tenant deployment package) is contained in an index file of the helm warehouse, a group of K8S resources can be packaged and uniformly managed, and the management method is an optimal mode for searching, sharing and using software constructed for kubernets.
The obtaining module 230 is configured to obtain, according to the unique tenant identifier in the tenant deployment package, a user deployment space corresponding to the unique tenant identifier from a preset deployment container cluster as a space to be deployed.
Specifically, the tenant deployment package is stored in a preset deployment package management warehouse, in the preset deployment package management warehouse, each tenant has a plurality of tenant deployment packages according to different micro services requested to be used, for example, the tenant deployment package corresponding to tenant1 may be represented as tenant 1-release, a user of the tenant requests to use two micro services, namely, a service a and a service B, and a sequence number of a corresponding tenant deployment space is 1, which may be represented as that the tenant 1-release includes, below, Chart-a-tenant1 and Chart-B-tenant1, where tenant1 corresponds to a user deployment space in a preset deployment container cluster. The building of the corresponding relation between the tenant deployment package and the tenant deployment space can be realized through the helm warehouse and the Kubernets cluster. And acquiring a user deployment space corresponding to the unique tenant identification from a preset deployment container cluster as a space to be deployed.
As an optional embodiment of the present invention, the multi-tenant deployment apparatus 200 of the legacy application further includes a deployment space creation module and a space storage module (not shown in the figure). Wherein,
the deployment space creation module is used for creating a user deployment space for each tenant according to the tenant micro-service request information;
and the space storage module is used for storing the user deployment space into a preset container through the container arrangement engine to obtain a preset deployment container cluster.
Specifically, a user deployment space is created for each tenant in advance through a deployment space creation module according to the acquired tenant microservice request information, and the user deployment space can be stored into a preset container through a space storage module by adopting a Kubernets container arrangement engine, so that a preset deployment container cluster is obtained. And the subsequent deployment of the application micro service program for the tenant is facilitated.
And the deployment module 240 is configured to obtain the mirror deployment parameters that are pre-matched with the tenant deployment package from the preset program data mirror repository, and deploy the mirror deployment parameters to the space to be deployed through the tenant deployment package.
Specifically, for each micro service provided by each application, a corresponding mirror deployment parameter is generated in advance, and the corresponding mirror deployment parameter is deployed to the space to be deployed through the tenant deployment package.
As an alternative embodiment of the present invention, the deployment module 240 further comprises: a parameter acquisition unit and a deployment unit (not shown in the figure). Wherein,
the parameter acquisition unit is used for acquiring mirror image deployment parameters corresponding to the tenant deployment package from a preset program data mirror image warehouse according to the application name field and the micro-service name field in the tenant deployment package; the preset program data mirror image warehouse stores mirror image deployment parameters of the micro-services provided by the application;
the deployment unit is used for establishing data transmission between the tenant deployment package in the deployment package management warehouse and the space to be deployed through a data interface; and deploying the mirror image deployment parameters to the space to be deployed.
Specifically, the mirror image deployment parameters in the preset program data mirror image warehouse correspond to corresponding application name fields and micro-service name fields, so that the mirror image deployment parameters corresponding to the tenant deployment package can be acquired through the parameter acquisition unit according to the application name fields and the micro-service name fields in the tenant deployment package, and the tenant deployment package in the deployment package management warehouse establishes data transmission with a space to be deployed through a data interface (such as an API interface) by adopting the deployment unit; and deploying the mirror image deployment parameters to the space to be deployed. The application of each tenant is deployed into the deployment space of the corresponding tenant, and the data isolation effect is achieved.
As an alternative embodiment of the present invention, the multi-tenant deployment apparatus 200 of the legacy application further includes an update location module, an update module, and a replacement module (not shown in the figure). Wherein,
the updating and positioning module is used for positioning the updating identification of the micro service according to the acquired data updating information of the micro service;
the updating module is used for updating the variables of the micro services in the tenant deployment package corresponding to the micro services according to the updating identification of the micro services and the name fields of the micro services to obtain an updated tenant deployment package, and updating the object information table corresponding to the updated tenant deployment package according to the updating content of the updated tenant deployment package to obtain a new object information table;
the replacement module is used for uploading the updated tenant deployment package to a preset deployment package management warehouse and replacing the updated tenant deployment package with the corresponding previous tenant deployment package; and uploading the new object information table to a preset object storage library, and covering the previous object information table with the new object information table.
Specifically, when the microservice program is updated or the data is updated, data updating information of the microservice is generated, and the updating content is positioned by the updating positioning module to generate an updating identifier. Finding the updated microservice and positioning the updated data of the microservice by the updating module according to the name field of the microservice with the data updating pointed out in the data updating information of the microservice; updating the variables of the micro-service in the tenant deployment package corresponding to the micro-service to obtain an updated tenant deployment package, and updating the object information table corresponding to the updated tenant deployment package according to the updating content of the updated tenant deployment package to obtain a new object information table; uploading the updated tenant deployment package to a preset deployment package management warehouse through a replacement module, and replacing the updated tenant deployment package with a corresponding previous tenant deployment package; and uploading the new object information table to a preset object repository, and overlaying the previous object information table with the new object information table. In the updating process, if the tenant information changes, the relevant information (for example, the tenant unique identifier) of the tenant in the tenant deployment package can be updated by the same method, and then the object information table is updated according to the updated deployment package.
Fig. 3 is a schematic structural diagram of an electronic device implementing a multi-tenant deployment method for legacy applications according to an embodiment of the present invention.
The electronic device 1 may include a processor 10, a memory 11, and a bus, and may further include a computer program stored in the memory 11 and executable on the processor 10, such as a multi-tenant deployment program 12 of a legacy application.
The memory 11 includes at least one type of readable storage medium, which includes flash memory, removable hard disk, multimedia card, card-type memory (e.g., SD or DX memory, etc.), magnetic memory, magnetic disk, optical disk, etc. The memory 11 may in some embodiments be an internal storage unit of the electronic device 1, such as a removable hard disk of the electronic device 1. The memory 11 may also be an external storage device of the electronic device 1 in other embodiments, such as a plug-in mobile hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like, which are provided on the electronic device 1. Further, the memory 11 may also include both an internal storage unit and an external storage device of the electronic device 1. The memory 11 may be used to store not only application software installed in the electronic device 1 and various types of data, such as codes of multi-tenant deployment programs of legacy applications, but also temporarily store data that has been output or is to be output.
The processor 10 may be composed of an integrated circuit in some embodiments, for example, a single packaged integrated circuit, or may be composed of a plurality of integrated circuits packaged with the same or different functions, and includes one or more Central Processing Units (CPUs), microprocessors, digital Processing chips, graphics processors, and combinations of various control chips. The processor 10 is a Control Unit (Control Unit) of the electronic device, connects various components of the whole electronic device by using various interfaces and lines, and executes various functions and processes data of the electronic device 1 by running or executing programs or modules (e.g., multi-tenant deployment programs of legacy applications, etc.) stored in the memory 11 and calling data stored in the memory 11.
The bus may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. The bus is arranged to enable connection communication between the memory 11 and at least one processor 10 or the like.
Fig. 3 shows only an electronic device with components, and it will be understood by those skilled in the art that the structure shown in fig. 3 does not constitute a limitation of the electronic device 1, and may comprise fewer or more components than those shown, or some components may be combined, or a different arrangement of components.
For example, although not shown, the electronic device 1 may further include a power supply (such as a battery) for supplying power to each component, and preferably, the power supply may be logically connected to the at least one processor 10 through a power management device, so as to implement functions of charge management, discharge management, power consumption management, and the like through the power management device. The power supply may also include any component of one or more dc or ac power sources, recharging devices, power failure detection circuitry, power converters or inverters, power status indicators, and the like. The electronic device 1 may further include various sensors, a bluetooth module, a Wi-Fi module, and the like, which are not described herein again.
Further, the electronic device 1 may further include a network interface, and optionally, the network interface may include a wired interface and/or a wireless interface (such as a WI-FI interface, a bluetooth interface, etc.), which are generally used for establishing a communication connection between the electronic device 1 and other electronic devices.
Optionally, the electronic device 1 may further comprise a user interface, which may be a Display (Display), an input unit (such as a Keyboard), and optionally a standard wired interface, a wireless interface. Alternatively, in some embodiments, the display may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, an OLED (Organic Light-Emitting Diode) touch device, or the like. The display, which may also be referred to as a display screen or display unit, is suitable for displaying information processed in the electronic device 1 and for displaying a visualized user interface, among other things.
It is to be understood that the described embodiments are for purposes of illustration only and that the scope of the appended claims is not limited to such structures.
The multi-tenant deployment program 12 of the legacy application stored in the memory 11 of the electronic device 1 is a combination of a plurality of instructions that, when executed in the processor 10, can implement:
according to the acquired tenant deployment instruction, registering relevant information of the application to a corresponding preset micro-service deployment package template, and establishing a corresponding relation between the application and the micro-service to obtain an application micro-service deployment package template;
correspondingly loading the tenant unique identifier in the acquired tenant micro service request information to an application micro service deployment package template, generating a tenant deployment package and an object information table corresponding to the tenant deployment package, storing the tenant deployment package to a preset deployment package management warehouse and storing the object information table to a preset object repository; the object information table comprises a tenant unique identifier and relevant information of a tenant deployment package corresponding to the tenant unique identifier; the tenant deployment package comprises a tenant unique identifier, an application name field and a micro-service name field;
acquiring a user deployment space corresponding to the tenant unique identifier from a preset deployment container cluster as a space to be deployed according to the tenant unique identifier in the tenant deployment package;
acquiring mirror image deployment parameters matched with the tenant deployment package in advance from a preset program data mirror image warehouse, and deploying the mirror image deployment parameters to a space to be deployed through the tenant deployment package.
Specifically, the specific implementation method of the processor 10 for the instruction may refer to the description of the relevant steps in the embodiment corresponding to fig. 1, which is not described herein again. It should be emphasized that, in order to further ensure the privacy and security of the preset microservice deployment package template, the preset microservice deployment package template may also be stored in a node of a block chain.
Further, the integrated modules/units of the electronic device 1, if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium. The computer-readable medium may include: any entity or device capable of carrying said computer program code, a recording medium, a usb-disk, a removable hard disk, a magnetic diskette, an optical disk, a computer Memory, a Read-Only Memory (ROM).
In the embodiments provided in the present invention, it should be understood that the disclosed apparatus, device and method can be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the modules is only one logical functional division, and other divisions may be realized in practice.
The modules described as separate parts may or may not be physically separate, and parts displayed as modules may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, functional modules in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional module.
It will be evident to those skilled in the art that the invention is not limited to the details of the foregoing illustrative embodiments, and that the present invention may be embodied in other specific forms without departing from the spirit or essential attributes thereof.
The present embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the invention being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Any reference signs in the claims shall not be construed as limiting the claim concerned.
The block chain is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, a consensus mechanism, an encryption algorithm and the like. A block chain (Blockchain), which is essentially a decentralized database, is a series of data blocks associated by using a cryptographic method, and each data block contains information of a batch of network transactions, so as to verify the validity (anti-counterfeiting) of the information and generate a next block. The blockchain may include a blockchain underlying platform, a platform product service layer, an application service layer, and the like.
Furthermore, it is obvious that the word "comprising" does not exclude other elements or steps, and the singular does not exclude the plural. A plurality of units or means recited in the system claims may also be implemented by one unit or means in software or hardware. The terms second, etc. are used to denote names, but not any particular order.
Finally, it should be noted that the above embodiments are only for illustrating the technical solutions of the present invention and not for limiting, and although the present invention is described in detail with reference to the preferred embodiments, it should be understood by those skilled in the art that modifications or equivalent substitutions may be made on the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention.
Claims (10)
1. A multi-tenant deployment method of a legacy application, applied to an electronic device, is characterized by comprising:
according to the acquired tenant deployment instruction, registering relevant information of the application to a corresponding preset micro-service deployment package template, and establishing a corresponding relation between the application and the micro-service to obtain an application micro-service deployment package template;
correspondingly loading the unique tenant identification in the acquired tenant micro-service request information to the application micro-service deployment package template, generating a tenant deployment package and an object information table corresponding to the tenant deployment package, storing the tenant deployment package to a preset deployment package management warehouse and storing the object information table to a preset object repository; the object information table comprises a tenant unique identifier and relevant information of a tenant deployment package corresponding to the tenant unique identifier; the tenant deployment package comprises a tenant unique identifier, an application name field and a micro-service name field;
according to the unique tenant identification in the tenant deployment package, acquiring a user deployment space corresponding to the unique tenant identification from a preset deployment container cluster as a space to be deployed;
and acquiring mirror image deployment parameters matched with the tenant deployment package in advance from a preset program data mirror image warehouse, and deploying the mirror image deployment parameters to the space to be deployed through the tenant deployment package.
2. The method according to claim 1, wherein the preset microservice deployment package template is stored in a block chain, and before the registering of the relevant information of the application to the corresponding preset microservice deployment package template according to the obtained tenant deployment instruction, establishing the correspondence between the application and the microservice, and obtaining the application microservice deployment package template, the method further comprises:
creating an initial definition table directory according to a preset directory rule;
and carrying out format variable replacement processing on the initial definition table directory based on the variables of the micro-services to obtain a preset micro-service deployment package template.
3. The multi-tenant deployment method of traditional applications according to claim 1, wherein the registering relevant information of an application to a corresponding preset micro-service deployment package template according to the obtained tenant deployment instruction, and establishing a corresponding relationship between the application and a micro-service to obtain an application micro-service deployment package template includes:
acquiring a preset micro-service deployment package template corresponding to each application as a target micro-service deployment package template according to the name of the micro-service provided by each application;
and loading the relevant information of the application to the target micro-service deployment package template, so that a corresponding relation is established between the application and the micro-service provided by the application, and the application micro-service deployment package template is obtained.
4. The method of claim 1, wherein the correspondingly loading the tenant unique identifier in the obtained tenant microservice request information to the application microservice deployment package template, generating a tenant deployment package and an object information table corresponding to the tenant deployment package, and storing the tenant deployment package to a preset deployment package management repository and the object information table to a preset object repository comprises:
acquiring an application name field and a micro-service name field appointed in the tenant micro-service request information; wherein the tenant microservice request information comprises: the tenant unique identification, the application name field and the micro-service name field;
acquiring an application micro-service deployment package template corresponding to the tenant micro-service request information according to the application name field and the micro-service name field, and taking the application micro-service deployment package template as a selected deployment package template; the application microservice deployment package template comprises an application name field and a microservice name field;
loading the unique tenant identification to the selected deployment package template to generate a tenant deployment package, and loading the unique tenant identification and the relevant information of the tenant deployment package to a preset information table to generate an object information table;
storing the tenant deployment package to a preset deployment package management warehouse and storing the object information table to a preset object storage library.
5. The multi-tenant deployment method of the legacy application according to claim 1, wherein before the obtaining, according to the tenant unique identifier in the tenant deployment package, the user deployment space corresponding to the tenant unique identifier from a preset deployment container cluster as the space to be deployed, the method further comprises:
creating a user deployment space for each tenant according to the tenant micro service request information;
and storing the user deployment space into a preset container through a container arrangement engine to obtain a preset deployment container cluster.
6. The multi-tenant deployment method of traditional applications according to claim 1, wherein the obtaining of the mirror deployment parameters pre-matched with the tenant deployment package from a preset program data mirror repository and the deploying of the mirror deployment parameters to the space to be deployed by the tenant deployment package comprises:
acquiring mirror image deployment parameters corresponding to the tenant deployment package from a preset program data mirror image warehouse according to an application name field and a micro-service name field in the tenant deployment package; the preset program data mirror image warehouse stores mirror image deployment parameters of the micro-service provided by the application;
a tenant deployment package in the deployment package management warehouse establishes data transmission with the space to be deployed through a data interface; and deploying the mirror image deployment parameters to the space to be deployed.
7. The method according to claim 1, wherein after the obtaining of the mirror deployment parameters pre-matched to the tenant deployment package from the preset program data mirror repository and the deployment of the mirror deployment parameters to the space to be deployed by the tenant deployment package, the method further comprises:
positioning an updating identifier of the micro service according to the acquired data updating information of the micro service;
updating the variables of the micro-services in the tenant deployment package corresponding to the micro-services according to the update identification of the micro-services and the name fields of the micro-services to obtain an updated tenant deployment package, and updating the object information table corresponding to the updated tenant deployment package according to the update content of the updated tenant deployment package to obtain a new object information table;
uploading the updated tenant deployment package to the preset deployment package management warehouse, and replacing the updated tenant deployment package with a corresponding previous tenant deployment package; and uploading the new object information table to the preset object repository, and overlaying the previous object information table with the new object information table.
8. An apparatus for multi-tenant deployment of legacy applications, the apparatus comprising:
the registration module is used for registering relevant information of the application to a corresponding preset micro-service deployment package template according to the acquired tenant deployment instruction, and establishing a corresponding relation between the application and the micro-service to obtain an application micro-service deployment package template;
the loading module is used for correspondingly loading the unique tenant identification in the acquired tenant microservice request information to the application microservice deployment package template, generating a tenant deployment package and an object information table corresponding to the tenant deployment package, storing the tenant deployment package to a preset deployment package management warehouse and storing the object information table to a preset object repository; the object information table comprises a tenant unique identifier and relevant information of a tenant deployment package corresponding to the tenant unique identifier; the tenant deployment package comprises a tenant unique identifier, an application name field and a micro-service name field;
the acquisition module is used for acquiring a user deployment space corresponding to the tenant unique identifier from a preset deployment container cluster as a space to be deployed according to the tenant unique identifier in the tenant deployment package;
and the deployment module is used for acquiring mirror deployment parameters matched with the tenant deployment package in advance from a preset program data mirror warehouse and deploying the mirror deployment parameters to the space to be deployed through the tenant deployment package.
9. An electronic device, characterized in that the electronic device comprises:
at least one processor; and the number of the first and second groups,
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the steps of the multi-tenant deployment method of legacy applications as claimed in any one of claims 1 to 7.
10. A computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the multi-tenant deployment method of a legacy application as claimed in any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210421881.9A CN114741092B (en) | 2022-04-21 | 2022-04-21 | Multi-tenant deployment method, device, equipment and storage medium for traditional application |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210421881.9A CN114741092B (en) | 2022-04-21 | 2022-04-21 | Multi-tenant deployment method, device, equipment and storage medium for traditional application |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114741092A true CN114741092A (en) | 2022-07-12 |
| CN114741092B CN114741092B (en) | 2024-08-09 |
Family
ID=82284707
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210421881.9A Active CN114741092B (en) | 2022-04-21 | 2022-04-21 | Multi-tenant deployment method, device, equipment and storage medium for traditional application |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114741092B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109274731A (en) * | 2018-09-04 | 2019-01-25 | 北京京东金融科技控股有限公司 | Deployment, call method and the device of web services based on multi-tenant technology |
| CN113741909A (en) * | 2021-08-31 | 2021-12-03 | 平安国际智慧城市科技股份有限公司 | Micro-service deployment method, device, electronic equipment and storage medium |
| CN114003360A (en) * | 2021-10-28 | 2022-02-01 | 芜湖雄狮汽车科技有限公司 | Multi-tenant task management method and device, electronic equipment and storage medium |
-
2022
- 2022-04-21 CN CN202210421881.9A patent/CN114741092B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109274731A (en) * | 2018-09-04 | 2019-01-25 | 北京京东金融科技控股有限公司 | Deployment, call method and the device of web services based on multi-tenant technology |
| CN113741909A (en) * | 2021-08-31 | 2021-12-03 | 平安国际智慧城市科技股份有限公司 | Micro-service deployment method, device, electronic equipment and storage medium |
| CN114003360A (en) * | 2021-10-28 | 2022-02-01 | 芜湖雄狮汽车科技有限公司 | Multi-tenant task management method and device, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114741092B (en) | 2024-08-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110795219B (en) | Resource scheduling method and system suitable for multiple computing frameworks | |
| CN109885316B (en) | Hdfs-hbase deployment method and device based on kubernetes | |
| CN112085217A (en) | Method, device, equipment and computer medium for deploying artificial intelligence service | |
| CN113741909B (en) | Micro-service deployment method and device, electronic equipment and storage medium | |
| CN114691050B (en) | Cloud native storage method, device, equipment and medium based on kubernets | |
| CN112948427A (en) | Data query method, device, equipment and storage medium | |
| CN111538573A (en) | Asynchronous task processing method and device and computer readable storage medium | |
| CN113704665A (en) | Dynamic service publishing method, device, electronic equipment and storage medium | |
| CN114398194A (en) | Data collection method and device, electronic equipment and readable storage medium | |
| CN112580079A (en) | Authority configuration method and device, electronic equipment and readable storage medium | |
| CN111651426A (en) | Data migration method and device and computer readable storage medium | |
| CN113254446A (en) | Data fusion method and device, electronic equipment and medium | |
| CN112328656A (en) | Service query method, device, equipment and storage medium based on middle platform architecture | |
| CN114860314B (en) | Deployment upgrading method, device, equipment and medium based on database compatibility | |
| CN114741092B (en) | Multi-tenant deployment method, device, equipment and storage medium for traditional application | |
| CN114860349B (en) | Data loading method, device, equipment and medium | |
| CN115794400A (en) | Memory management method, device and equipment of deep learning model and storage medium | |
| CN116954815A (en) | Resource scheduling method and device, computer equipment and computer readable storage medium | |
| CN115757121A (en) | Test method, device, equipment and storage medium built based on test environment | |
| CN114895942A (en) | Application skin changing method, device, equipment and storage medium | |
| CN115437749A (en) | Cloud host rescue method, device, equipment and storage medium based on OpenStack cluster | |
| CN114185522A (en) | Page theme customizing method and device, electronic equipment and storage medium | |
| CN113918305A (en) | Node scheduling method and device, electronic equipment and readable storage medium | |
| CN114564207A (en) | Software product processing method and device, computer equipment and storage medium | |
| CN114116673A (en) | Data migration method based on artificial intelligence and related 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 |