CN114489954A

CN114489954A - Tenant creation method based on virtualization platform, tenant access method and equipment

Info

Publication number: CN114489954A
Application number: CN202210128589.8A
Authority: CN
Inventors: 董方旭; 王亚明; 王秋菊; 陈维强; 孙永良; 李建伟
Original assignee: Hisense TransTech Co Ltd
Current assignee: Hisense TransTech Co Ltd
Priority date: 2022-02-11
Filing date: 2022-02-11
Publication date: 2022-05-13

Abstract

The application relates to the technical field of containerization, and discloses a tenant creating method based on a virtualization platform, a tenant access method and equipment.

Description

Tenant creation method based on virtualization platform, tenant access method and device

Technical Field

The application relates to the technical field of containerization, in particular to a tenant creating method, a tenant access method and equipment based on a virtualization platform.

Background

In the prior art, after a container cluster of a virtualization platform receives a creation request of a new tenant, a project space is allocated to the new tenant, a network isolation policy is configured for the new tenant so that the project space of the new tenant is isolated from the project spaces of other tenants in the container cluster except the new tenant, and then a resource configuration is performed on the project space of the new tenant to complete a creation process of the new tenant. However, for a plurality of different tenants, the method for creating a tenant needs to perform repeated service deployment for a plurality of times, so that the operation is complicated and the workload is large, each tenant can only access the service of the corresponding tenant through the corresponding entry, and when the service of one tenant has a problem, the use of the service of other tenants is affected.

Disclosure of Invention

The embodiment of the application provides a tenant creating method, a tenant access method and equipment based on a virtualization platform, so that the problems of service isolation and repeated service deployment among multiple tenants can be solved.

In a first aspect, an embodiment of the present application provides a tenant creating method based on a virtualization platform, including:

after receiving a creation request of a tenant, creating a tenant item corresponding to the tenant, wherein the tenant item comprises a service;

determining a configuration file of a tenant project and a service configuration of the tenant project based on a configuration file of a source project corresponding to the tenant project and the service configuration of the source project;

and starting the service in the tenant project to finish the creation of the tenant by using the configuration file of the tenant project and the service configuration of the tenant project.

Compared with the prior art that multiple tenants are designed to a logic resource layer, namely only resources of a container are managed, when a tenant is created, the tenant item corresponding to the tenant is taken as the latitude to perform extended deployment on services in the tenant item, firstly, the tenant item is ensured to contain the services when the tenant item corresponding to the tenant is created, then, based on the configuration file of the source item corresponding to the tenant item and the service configuration of the source item, the configuration file of the tenant item and the service configuration of the tenant item are determined, and finally, the creation of the tenant is completed by starting the services in the group item, so that the problems of service isolation among the multiple tenants and repeated deployment of the services are solved.

Optionally, after creating the tenant item corresponding to the tenant, the method further includes:

and creating an item space corresponding to the tenant item, so that the service in the tenant item is started in the item space.

According to the method and the device, the application program is further controlled, the project space corresponding to the tenant project is created, and the service in the tenant project is started in the project space, so that the problems of service isolation and repeated service deployment among multiple tenants can be better solved.

Optionally, the determining the configuration file of the tenant item and the service configuration of the tenant item based on the configuration file of the source item corresponding to the tenant item and the service configuration of the source item includes:

and extracting data in the configuration file of the source project and data in the service configuration of the source project by adopting a cyclic algorithm to obtain the configuration file of the tenant project and the service configuration of the tenant project.

According to the method and the device, the data in the tenant project are obtained by extracting the data in the source project, so that the determined configuration file of the tenant project and the service configuration of the tenant project are more accurate.

Optionally, after the determining the configuration file of the tenant item and the service configuration of the tenant item, before the initiating the service in the tenant item, the method further includes:

receiving a modification request for the configuration file of the tenant project, and modifying the configuration file of the tenant project based on the modification request.

The configuration file of the tenant item is modified by utilizing the modification request, so that the finally determined configuration file of the tenant item and the service configuration of the tenant item are more accurate.

Optionally, after the completing the creation of the tenant, the method further includes:

and constructing an incidence relation between the identification information of the tenant and the project space, and storing the incidence relation to a gateway between the tenant and a user so that the user can determine the project space by using the identification information of the tenant through the gateway.

By storing the incidence relation between the identification information of the tenants and the project space in the gateway, the multiple tenants can access the application program corresponding to each tenant through the same entrance, so that the resource utilization rate is improved, and the complexity of the process of repeatedly constructing tenant access is reduced.

In a second aspect, an embodiment of the present application provides a tenant access method based on a virtualization platform, where the method includes:

receiving an access request of a user, and acquiring identification information of a tenant to be accessed based on the access request;

determining an item space corresponding to the tenant to be accessed according to the pre-stored association relationship between the identification information of the tenant and the item space;

and starting the service in the project space corresponding to the tenant to be accessed.

In a third aspect, an embodiment of the present application provides a tenant creating device based on a virtualization platform, including: a processor and a display;

the display is used for displaying a user operation interface;

the processor configured to perform:

Optionally, after the processor is configured to create the tenant item corresponding to the tenant, the processor is further configured to perform:

Optionally, the processor is configured to execute determining a configuration file of the tenant item and a service configuration of the tenant item based on a configuration file of a source item corresponding to the tenant item and a service configuration of the source item, and is specifically configured to execute:

Optionally, the processor is configured to perform, after determining the configuration file of the tenant item and the service configuration of the tenant item, and before the launching of the service in the tenant item, further configured to perform:

Optionally, the processor is configured to perform, after the completing the creation of the tenant, further configured to perform:

In a fourth aspect, an embodiment of the present application provides a tenant access device based on a virtualization platform, including: a processor and a display;

the display is used for displaying a user operation interface;

the processor configured to perform:

In a fifth aspect, an embodiment of the present application provides a tenant creating apparatus based on a virtualization platform, including:

the system comprises a creation module, a service module and a service module, wherein the creation module is used for creating a tenant item corresponding to a tenant after receiving a creation request of the tenant;

the determining module is used for determining the configuration file of the tenant project and the service configuration of the tenant project based on the configuration file of the source project corresponding to the tenant project and the service configuration of the source project;

and the starting module is used for starting the service in the tenant project to finish the creation of the tenant by utilizing the configuration file of the tenant project and the service configuration of the tenant project.

Optionally, after the tenant item corresponding to the tenant is created in the creation module, the creation module is further configured to:

Optionally, the determining module is specifically configured to:

Optionally, after determining the configuration file of the tenant item and the service configuration of the tenant item, and before the starting of the service in the tenant item, the starting module is further configured to:

Optionally, after completing the creation of the tenant, the starting module is further configured to:

In a sixth aspect, an embodiment of the present application provides a tenant access apparatus based on a virtualization platform, including:

the receiving module is used for receiving an access request of a user and acquiring identification information of a tenant to be accessed based on the access request;

the first determining module is used for determining the project space corresponding to the tenant to be accessed according to the pre-stored association relationship between the identification information of the tenant and the project space;

and the first starting module is used for starting the service in the project space corresponding to the tenant to be accessed.

In a seventh aspect, an embodiment of the present application further provides a computer-readable storage medium, where when instructions of the computer-readable storage medium are executed by a processor of any one of a tenant creation device or a tenant access device based on a virtualization platform, the tenant creation device or the tenant access device based on the virtualization platform is enabled to execute any one of the methods provided in the first aspect or the second aspect of the present application.

In an eighth aspect, an embodiment of the present application provides a computer program product comprising computer programs/instructions which, when executed by a processor, implement any of the methods as provided in the first or second aspects of the present application.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the embodiments of the present application will be briefly described below, and it is obvious that the drawings described below are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 is a schematic flowchart of a tenant creating method based on a virtualization platform according to an embodiment of the present application;

FIG. 2 is a schematic diagram of an interface for creating a tenant according to an embodiment of the present application;

FIG. 3 is a schematic diagram of an interface for creating tenant items according to an embodiment of the present application;

FIG. 4 is a schematic diagram of an interface for creating a project space according to an embodiment of the present application;

FIG. 5 is a schematic diagram of an interface for editing a configuration file according to an embodiment of the present application;

FIG. 6 is a schematic interface diagram of an editing service provided in an embodiment of the present application;

FIG. 7 is a flowchart illustrating a process for a user to access a project space according to an embodiment of the present application;

fig. 8 is a flowchart illustrating a tenant access method based on a virtualization platform according to an embodiment of the present application;

fig. 9 is a schematic flowchart of a tenant creating device based on a virtualization platform or a tenant accessing device based on a virtualization platform according to an embodiment of the present application.

Detailed Description

In order to make the technical solutions of the present application better understood by those of ordinary skill in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings.

Hereinafter, some terms in the embodiments of the present application are explained to facilitate understanding by those skilled in the art.

(1) In the embodiments of the present application, the term "plurality" means two or more, and other terms are similar thereto.

(2) "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.

(3) Multi-tenant, meaning that a single instance can serve multiple organizations. The multi-tenant technology is how to provide services, which are the same as or even customizable to a plurality of clients, in a single system architecture and service in a shared data center, and can still guarantee data isolation of customers.

Therefore, when a tenant is created, the tenant item corresponding to the tenant is taken as the latitude to perform extended deployment on services in the tenant item, firstly, the fact that the tenant item comprises the services is ensured when the tenant item corresponding to the tenant is created, then, based on the configuration file of the source item corresponding to the tenant item and the service configuration of the source item, the configuration file of the tenant item and the service configuration of the tenant item are determined, and finally, the creation of the tenant is completed by starting the services in the group item, so that the problems of service isolation and repeated service deployment among a plurality of tenants are solved. According to the method and the system, a set of base frame for resource unified management and maintenance is determined through the service creation process, so that the capabilities of resource unified monitoring, resource elastic expansion as required, high service availability management and the like can be realized, and the efficiency is improved.

To further illustrate the technical solutions provided by the embodiments of the present application, the following detailed description is made with reference to the accompanying drawings and the detailed description. Although the embodiments of the present application provide the method operation steps as shown in the following embodiments or figures, more or less operation steps may be included in the method based on the conventional or non-inventive labor. In steps where no necessary causal relationship exists logically, the order of execution of these steps is not limited to the order of execution provided by the embodiments of the present application.

Fig. 1 illustrates a tenant creating method based on a virtualization platform according to an embodiment of the present application, including the following steps:

s101, after receiving a creation request of a tenant, creating a tenant item corresponding to the tenant, wherein the tenant item comprises a service.

For example, as shown in fig. 2, the building of the service isolation environment is achieved through page operations. Illustratively, the user can present the interface shown in FIG. 2 by clicking on the multi-tenant management in the cluster details. Wherein the interface shown in FIG. 2 further shows the create multi-tenant step: step 1, creating a new multi-tenant, step 2, modifying the configuration file, step 3, modifying the service, and step 4, starting the service.

The user sends the tenant's create request by triggering the "add" button in the interface of figure 2. After the user triggers the add button, as shown in fig. 3, by inputting "cloud brain tenant" in the "tenant name", inputting "hibernain" tenant code ", selecting" basic cloud brain "in the" source project ", selecting" default project "or creating project in the" tenant project ", clicking the confirm button, that is, completing the creation of the tenant project corresponding to the tenant.

By further controlling the application program, after the tenant project corresponding to the tenant is created, the project space corresponding to the tenant project can be created, so that the service in the tenant project is started in the project space. One tenant item is bound with one corresponding item space, and isolation of services of each tenant item in an independent logic item space is guaranteed. Here, the tenant item and the corresponding item space are created after the tenant item is determined to contain the service. When the tenant item does not contain the service, the tenant item and the corresponding item space are not created, and only the tenant item information is saved.

As shown in fig. 4, assuming that a source project space exists in the container cluster, and the source project space includes service 1, service 2, and service n (n is a positive integer), after creation of the tenant project is completed, an project space corresponding to the tenant project is created based on tenant identification information user1, that is, a user1 project space, and a user1 project space also includes service 1, service 2, and service n (n is a positive integer). Here, service 1, service 2, service n are logically isolated, exist independently and do not interact with each other, in the source project space and user1 project space.

After the creation of the tenant item corresponding to the tenant is completed, the step S102 may be continuously performed to determine a configuration file of the tenant item and a service configuration of the tenant item based on the configuration file of the source item corresponding to the tenant item and the service configuration of the source item.

Optionally, in order that the service in the tenant item can be started smoothly, the configuration file and the service configuration of the source item are first obtained from the database, and then the data in the configuration file of the source item and the data in the service configuration of the source item are extracted by using a loop algorithm, so that the configuration file of the tenant item and the service configuration of the tenant item are obtained.

In an embodiment of the application, after determining the configuration file of the tenant item and the service configuration of the tenant item, and before starting a service in the tenant item, if a modification request for the configuration file of the tenant item is received, the configuration file of the tenant item is modified based on the modification request. For example, if the user clicks the corresponding edit configuration file in the configuration management of the cluster details in the interface in fig. 2, the interface is shown in fig. 5, and the user may modify the configuration file of the tenant item in the interface shown in fig. 5. Such as modifying the database configuration, message queue configuration, etc. in the configuration file.

Fig. 6 shows a service editing interface of a tenant item, for example, a service name is menhu, a home item is a base cloud, a selected mirror image is registry.kubbeoperant.io: 8083/menhu: v4.0, the number of start instances is 1, a service type is nodoport, a container port number is 80, and a node port number is 30090, a profile group is menhu, a file group name is menhu, a file name is nginx.conf, a configuration path is/etc/nginx/conf.d/default.conf, and a computing resource is CPU: 100-1000 m, 100-1000 MB of memory, no health examination.

After determining the configuration file of the tenant item and the service configuration of the tenant item, step S103 may be continuously performed, and a service in the tenant item is started to complete creation of the tenant by using the configuration file of the tenant item and the service configuration of the tenant item.

For example, by calling Kubernets (K8s, an open source software for automatically deploying, extending and managing containerized applications) to start the service in the project of the tenant, the creation of the tenant is completed, and the application realizes that a plurality of services are started in the project space of another tenant through page operation.

In an embodiment of the application, after the creation of the tenant is completed, the association relationship between the identification information of the tenant and the project space is built, and the association relationship is stored in a gateway between the tenant and a user, so that the user can determine the project space through the gateway by using the identification information of the tenant.

Illustratively, a layer of gateway is added between the user and the tenant service for routing, and the routing table is updated in real time. For example, the routing table includes: tenant user 1-project space Namespace1, tenant user 2-project space Namespace2 and tenant user 3-project space Namespace3, when detecting a newly-built tenant user4 and project space Namespace4, updating a routing table, wherein the updated routing table comprises: tenant user 1-project space Namespace1, tenant user 2-project space Namespace2, tenant user 3-project space Namespace3, and tenant user 4-project space Namespace 4. When an access request of a tenant user1 is received, determining that the project space needing to be accessed is a project space Namespace1 through a routing table. Here, the routing table may be stored in Redis, and a gateway between the user and the tenant service may directly acquire the routing table from the Redis. And the gateway between the user and the tenant service is not used for authentication of the user authority, and can sink to the lower layer gateway.

According to the method and the system, different tenants can access services in corresponding tenant projects through the same entrance by adding the dynamic routing gateway. As shown in fig. 7, after the identification information of the tenant to be accessed by the user is determined, the entry space to be accessed is determined through the routing table in the gateway. FIG. 7 shows project space Namespace1 of tenant user1, project space Namespace2 of tenant user2, and project space with the tenant name in a blank state. From the above description, the services in the project space Namespace1 of tenant user1, the project space Namespace2 of tenant user2 and the project space with the tenant name in the blank state are the same, and include: the auth-OAuth2 authentication service in the open source project nacos, gateway-interface gateway to proxy all micro services, share-share, access-a database type, assets-resources, etc.

Fig. 8 illustrates a tenant access method based on a virtualization platform according to an embodiment of the present application, including the following steps:

s801, receiving an access request of a user, and acquiring identification information of a tenant to be accessed based on the access request.

For example, after receiving an access request from a user, a request line in the access request includes: a request method, a blank space, a URL (Uniform Resource Locator), a protocol version, a carriage return symbol, and a line feed symbol, where parameters in an access request include: the tenant name and the token, the access request further includes: carriage returns, linefeeds, and request data. The identification information of the tenant to be accessed, which is acquired based on the access request, may be one or more of a tenant name and a token.

S802, determining the project space corresponding to the tenant to be accessed according to the pre-stored association relationship between the identification information of the tenant and the project space.

For example, as known from the tenant creating method, a routing table is obtained from Redis, and an association relationship between the identification information of the tenant and the project space is stored in the routing table, where the association relationship is, for example: tenant user 1-project space Namespace1, tenant user 2-project space Namespace2, tenant user 3-project space Namespace3, and tenant user 4-project space Namespace 4. After an access request of a tenant user1 to be accessed is received, determining that an item space needing to be accessed is an item space Namespace1 through a routing table.

Here, if the project space corresponding to the tenant to be accessed is not found according to the pre-stored association relationship between the identification information of the tenant and the project space, the project space with the tenant name in a blank state is determined as the project space corresponding to the tenant to be accessed.

After determining the project space corresponding to the tenant to be accessed, the step S803 may be continuously executed to start the service in the project space corresponding to the tenant to be accessed.

After introducing the tenant creating method based on the virtualization platform and the tenant accessing method based on the virtualization platform according to the exemplary embodiment of the present application, next, a tenant creating device based on the virtualization platform and a tenant accessing device based on the virtualization platform according to another exemplary embodiment of the present application are introduced.

As will be appreciated by one skilled in the art, aspects of the present application may be embodied as a system, method or program product. Accordingly, various aspects of the present application may be embodied in the form of: an entirely hardware embodiment, an entirely software embodiment (including firmware, microcode, etc.) or an embodiment combining hardware and software aspects that may all generally be referred to herein as a "circuit," module "or" system.

In some possible embodiments, a virtualization platform based tenant creation device or a virtualization platform based tenant access device according to the present application may include at least one processor, and at least one memory. The memory stores program code, and the program code, when executed by the processor, causes the processor to perform the steps of the virtualization platform based tenant creation method or the virtualization platform based tenant access method according to various exemplary embodiments of the present application described above in this specification. For example, the processor may perform steps as in a virtualization platform based tenant creation method or a virtualization platform based tenant access method.

A virtualization platform based tenant creation device or a virtualization platform based tenant access device 120 according to this embodiment of the present application is described below with reference to fig. 9. The virtual platform-based tenant creation device or the virtual platform-based tenant access device 120 shown in fig. 9 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present application.

As shown in fig. 9, the virtualization platform based tenant creation device or virtualization platform based tenant access device 120 is represented in the form of a general virtualization platform based tenant creation device or virtualization platform based tenant access device. The components of the virtualization platform based tenant creation device or virtualization platform based tenant access device 120 may include, but are not limited to: the at least one processor 121, the at least one memory 122, and a bus 123 connecting the various system components (including the memory 122 and the processor 121).

Bus 123 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, a processor, or a local bus using any of a variety of bus architectures.

The memory 122 may include readable media in the form of volatile memory, such as Random Access Memory (RAM)1221 and/or cache memory 1222, and may further include Read Only Memory (ROM) 1223.

Memory 122 may also include a program/utility 1225 having a set (at least one) of program modules 1224, such program modules 1224 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which, or some combination thereof, may comprise an implementation of a network environment.

The virtualization platform based tenant creation device or virtualization platform based tenant access device 120 may also communicate with one or more external devices 124 (e.g., keyboard, pointing device, etc.), one or more devices that enable a user to interact with the virtualization platform based tenant creation device or virtualization platform based tenant access device 120, and/or any device (e.g., router, modem, etc.) that enables the virtualization platform based tenant creation device or virtualization platform based tenant access device 120 to communicate with one or more other virtualization platform based tenant creation devices or virtualization platform based tenant access devices. Such communication may be through input/output (I/O) interfaces 125. Also, the virtualized platform based tenant create device or virtualized platform based tenant access device 120 may also communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the internet) through a network adapter 126. As shown, the network adapter 126 communicates with other modules for the virtualized platform based tenant create device or the virtualized platform based tenant access device 120 over a bus 123. It should be understood that although not shown in the figures, other hardware and/or software modules may be used in conjunction with the virtualization platform based tenant creation device or virtualization platform based tenant access device 120, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.

In an exemplary embodiment, a computer-readable storage medium comprising instructions, such as the memory 122 comprising instructions, executable by the processor 121 to perform the above-described method is also provided. Alternatively, the computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.

In an exemplary embodiment, there is also provided a computer program product comprising computer programs/instructions which, when executed by the processor 121, implement either the virtualization platform based tenant creation method or the virtualization platform based tenant access method as provided herein.

In an exemplary embodiment, various aspects of a virtualization platform based tenant creation method or a virtualization platform based tenant access method provided in the present application may also be implemented in the form of a program product including program code for causing a computer device to perform the steps of a virtualization platform based tenant creation method or a virtualization platform based tenant access method according to various exemplary embodiments of the present application described above in this specification when the program product is run on the computer device.

The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

The program product for virtualization platform based tenant creation or virtualization platform based tenant access of embodiments of the present application may employ a portable compact disk read only memory (CD-ROM) and include program code and may run on a virtualization platform based tenant creation device or a virtualization platform based tenant access device. However, the program product of the present application is not limited thereto, and in this document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

A readable signal medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Program code for carrying out operations of the present application may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user virtualization platform based tenant creation device or virtualization platform based tenant access device, partly on the user device, as a stand-alone software package, partly on the user virtualization platform based tenant creation device or virtualization platform based tenant access device, partly on the remote virtualization platform based tenant creation device or virtualization platform based tenant access device, or entirely on the remote virtualization platform based tenant creation device or virtualization platform based tenant access device or service. In the case of a remote virtualization platform based tenant creation device or virtualization platform based tenant access device, the remote virtualization platform based tenant creation device or virtualization platform based tenant access device may be connected to the user virtualization platform based tenant creation device or virtualization platform based tenant access device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external virtualization platform based tenant creation device or virtualization platform based tenant access device (e.g., through the internet using an internet service provider).

It should be noted that although several units or sub-units of the apparatus are mentioned in the above detailed description, such division is merely exemplary and not mandatory. Indeed, the features and functions of two or more units described above may be embodied in one unit, according to embodiments of the application. Conversely, the features and functions of one unit described above may be further divided into embodiments by a plurality of units.

Further, while the operations of the methods of the present application are depicted in the drawings in a particular order, this does not require or imply that these operations must be performed in this particular order, or that all of the illustrated operations must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable virtualization platform based tenant creation device or virtualization platform based tenant access device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable virtualization platform based tenant creation device or virtualization platform based tenant access device, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable virtualization platform-based tenant creation device or virtualization platform-based tenant access device to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable virtualization platform-based tenant creation device or a virtualization platform-based tenant access device to cause a series of operational steps to be performed on the computer or other programmable device to produce a computer implemented process such that the instructions which execute on the computer or other programmable device provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

While the preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all alterations and modifications as fall within the scope of the application.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. A tenant creating method based on a virtualization platform is characterized by comprising the following steps:

2. The method according to claim 1, wherein after the creating of the tenant item corresponding to the tenant, the method further comprises:

3. The method of claim 1, wherein the determining the configuration file of the tenant item and the service configuration of the tenant item based on the configuration file of the source item corresponding to the tenant item and the service configuration of the source item comprises:

4. The method of claim 1, wherein after the determining the configuration file of the tenant item and the service configuration of the tenant item, and before the initiating the service in the tenant item, the method further comprises:

5. The method according to claim 2, wherein after the completion of the creation of the tenant, the method further comprises:

6. A tenant access method based on a virtualization platform is characterized by comprising the following steps:

7. A tenant creation device based on a virtualization platform, comprising: a processor and a display;

the display is used for displaying a user operation interface;

the processor configured to perform:

8. The apparatus of claim 7, wherein the processor is configured to perform, after creating the tenant item corresponding to the tenant, further configured to perform:

9. The device of claim 7, wherein the processor is configured to perform determining the configuration file of the tenant item and the service configuration of the tenant item based on the configuration file of the source item and the service configuration of the source item corresponding to the tenant item, and is specifically configured to perform:

10. A tenant access device based on a virtualization platform, comprising: a processor and a display;

the display is used for displaying a user operation interface;

the processor configured to perform:

determining a project space corresponding to the tenant to be accessed according to a pre-stored incidence relation between the identification information of the tenant and the project space;