CN110365547B - Method, device and equipment for creating tenant node of multi-level tenant system and computer readable storage medium - Google Patents
Method, device and equipment for creating tenant node of multi-level tenant system and computer readable storage medium Download PDFInfo
- Publication number
- CN110365547B CN110365547B CN201910845826.0A CN201910845826A CN110365547B CN 110365547 B CN110365547 B CN 110365547B CN 201910845826 A CN201910845826 A CN 201910845826A CN 110365547 B CN110365547 B CN 110365547B
- Authority
- CN
- China
- Prior art keywords
- tenant
- node
- level
- type
- hierarchy
- 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.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0645—Rental transactions; Leasing transactions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0893—Assignment of logical groups to network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
Abstract
The invention relates to a method, a device, equipment and a medium for creating a tenant node based on a multi-level tenant system structure, which are used for acquiring a tenant node creating request initiated by a current tenant node, determining a tenant level corresponding to a target tenant node in the multi-level tenant system structure according to the tenant type of the target tenant node carried by the creating request, wherein the multi-level tenant system structure comprises a plurality of tenant levels respectively corresponding to different tenant types, and then creating the target tenant node in the tenant level. According to the scheme, the corresponding tenant level can be searched according to the tenant type to which the target tenant node to be created belongs, a new tenant node is created on the tenant level, the new tenant level cannot be increased in the creation process of the tenant node, and therefore the number of the tenant levels of the whole tenant system cannot be increased along with the increase of the tenant node, the number of the levels of a multi-level tenant system structure can be kept constant, and the time complexity of logic implementation of the tenant system is reduced.
Description
Technical Field
The present invention relates to the field of internet technologies, and in particular, to a method and an apparatus for creating tenant nodes based on a multi-level tenant architecture, a computer device, and a computer-readable storage medium.
Background
Multi-tier tenant architectures are commonly applied in cloud service platforms (e.g., IaaS, PaaS, and SaaS). For example, in the design of a tenant of a cloud computing service platform, relatively independent resource management capabilities are provided for different tenants in a resource isolation manner. The tenant is a common resource isolation mode in a cloud computing service platform, for example, an IaaS cloud service platform needs to provide cloud resources (such as resources of computing capacity, network, storage and the like) to an enterprise a and an enterprise B, in the architectural design of the IaaS cloud service platform, the cloud resources purchased by different enterprises need to be distinguished, and it is ensured that a user of the enterprise a accesses and uses the cloud resources purchased by the enterprise a instead of the cloud resources of the enterprise B.
When a new tenant node is created in a multi-level tenant system, the conventional technology generally configures attributes of multiple tenant types for a current tenant node, and creates the new tenant node directly under the current tenant node based on the attributes, thereby increasing the level of the multi-level tenant system. However, this approach will make the multi-hierarchy tenant architecture an infinite hierarchy tree structure, and as the hierarchy increases, the time complexity of implementing logic by the tenant architecture will also be higher.
Disclosure of Invention
Based on this, it is necessary to provide a tenant node creation method based on a multi-level tenant architecture, a tenant node creation apparatus based on the multi-level tenant architecture, a computer device, and a computer readable storage medium, for solving the technical problem that the time complexity of implementing logic of a tenant architecture is higher and higher as the hierarchy of the conventional technology increases.
A tenant node creating method based on a multi-level tenant architecture comprises the following steps:
acquiring a tenant node creation request; the tenant node creation request is initiated by the current tenant node; the tenant node creating request carries the tenant type of the target tenant node to be created;
determining a tenant hierarchy corresponding to the tenant type in a multi-hierarchy tenant architecture according to the tenant type; the multi-hierarchy tenant architecture comprises a plurality of tenant hierarchies, and each tenant hierarchy corresponds to different tenant types;
creating the target tenant node in the tenant hierarchy.
A tenant node creation apparatus based on a multi-hierarchy tenant architecture, comprising:
the request acquisition module is used for acquiring a tenant node creation request; the tenant node creation request is initiated by the current tenant node; the tenant node creating request carries the tenant type of the target tenant node to be created;
the hierarchy determining module is used for determining a tenant hierarchy corresponding to the tenant type in a multi-level tenant architecture according to the tenant type; the multi-hierarchy tenant architecture comprises a plurality of tenant hierarchies, and each tenant hierarchy corresponds to different tenant types;
a node creation module to create the target tenant node in the tenant hierarchy.
A computer device comprising a processor and a memory, the memory storing a computer program that when executed by the processor performs the steps of:
acquiring a tenant node creation request; the tenant node creation request is initiated by the current tenant node; the tenant node creating request carries the tenant type of the target tenant node to be created; determining a tenant hierarchy corresponding to the tenant type in a multi-hierarchy tenant architecture according to the tenant type; the multi-hierarchy tenant architecture comprises a plurality of tenant hierarchies, and each tenant hierarchy corresponds to different tenant types; creating the target tenant node in the tenant hierarchy.
A computer-readable storage medium, on which a computer program is stored which, when executed by a processor, carries out the steps of:
acquiring a tenant node creation request; the tenant node creation request is initiated by the current tenant node; the tenant node creating request carries the tenant type of the target tenant node to be created; determining a tenant hierarchy corresponding to the tenant type in a multi-hierarchy tenant architecture according to the tenant type; the multi-hierarchy tenant architecture comprises a plurality of tenant hierarchies, and each tenant hierarchy corresponds to different tenant types; creating the target tenant node in the tenant hierarchy.
According to the method, the device, the computer equipment and the storage medium for creating the tenant node based on the multi-level tenant system structure, the tenant node creating request initiated by the current tenant node is firstly obtained, then the tenant hierarchy corresponding to the tenant type is determined in the multi-level tenant system structure according to the tenant type to which the target tenant node belongs, wherein the multi-level tenant system structure comprises a plurality of tenant hierarchies, each tenant hierarchy respectively corresponds to different tenant types, and then the target tenant node is created in the tenant hierarchy. According to the scheme, the corresponding tenant hierarchy can be searched according to the tenant type to which the target tenant node to be created belongs, a new tenant node is created on the tenant hierarchy, and the new tenant hierarchy cannot be added in the creation process of the tenant node, so that the number of the tenant hierarchies of the whole tenant system cannot be increased along with the increase of the tenant node, the number of the hierarchies of a multi-level tenant system structure can be kept constant, and the time complexity of logic implementation of the multi-level tenant system is reduced.
Drawings
Fig. 1 is a flowchart illustrating a tenant node creation method based on a multi-level tenant architecture in an embodiment.
Fig. 2 is a schematic diagram of a principle of creating tenant nodes in a multi-level tenant architecture.
Figure 3 is a schematic diagram of creating tenant nodes in a multi-tier tenant architecture in one embodiment.
Fig. 4 is a block diagram of a tenant node creation apparatus based on a multi-level tenant architecture in one embodiment.
FIG. 5 is a diagram illustrating an internal structure of a computer device according to an embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
In an embodiment, a method for creating a tenant node based on a multi-level tenant architecture is provided, and referring to fig. 1, fig. 1 is a schematic flow diagram of a method for creating a tenant node based on a multi-level tenant architecture in an embodiment, where the method may be implemented based on a server of a cloud server platform, and the method for creating a tenant node based on a multi-level tenant architecture may include the following steps:
step S101, a tenant node creation request is obtained.
In this step, the tenant node creation request is initiated by the current tenant node, and the tenant node creation request is mainly used for creating a new tenant node for the current tenant node. Wherein, the tenant node creation request carries the tenant type of the target tenant node to be created.
Specifically, the implementation logic of the tenant system is to associate an organization with tenants, one organization can simultaneously have multiple tenant types, the step can distinguish tenants of different tenant types by using the tenant type as an attribute of the tenant, for a multi-level tenant system, each tenant level can be provided with multiple tenant nodes, and the tenant can acquire, distribute and manage resources through corresponding tenant nodes in the tenant system.
In this step, the current tenant node may be one or more of tenant nodes preset in the multi-level tenant architecture, for example, if the multi-level tenant architecture is preset with a tenant node a, a tenant node B, and a tenant node C, the current tenant node may be one or more of the tenant node a, the tenant node B, and the tenant node C. When a current tenant node needs to create a new tenant node in the multi-level tenant architecture, the new tenant node to be created may be set as a target tenant node, a tenant type of the target tenant node is determined, and the tenant type is loaded into a tenant node creation request as attribute information of the target tenant node, so that the tenant node creation request initiated by the current tenant node carries a tenant type to which the target tenant node belongs.
Step S102, according to the tenant type, determining a tenant level corresponding to the tenant type in a multi-level tenant architecture.
In this step, the multi-level tenant architecture may include a plurality of tenant levels, and each tenant level corresponds to a different tenant type. In this step, the tenant type is associated with a tenant hierarchy, that is, different tenant hierarchies of a multi-hierarchy tenant architecture correspond to different tenant types. Specifically, if the tenant type includes a tenant type a, a tenant type B, and a tenant type C, the multi-level tenant architecture is a tenant architecture composed of three tenant levels, and may include a top layer, a middle layer, and a bottom layer, which respectively correspond to the tenant type a, the tenant type B, and the tenant type C. Therefore, when a tenant node creation request initiated by the current tenant node is acquired, the tenant type to which the target tenant node to be created belongs can be extracted, and the tenant level corresponding to the tenant type is determined according to the tenant type.
In one embodiment, the multi-level tenant architecture may be pre-built by:
determining a plurality of tenant types; configuring a plurality of tenant levels; wherein the plurality of tenant hierarchies correspond to a plurality of tenant types, respectively; on a tenant level, a tenant node matched with the tenant type of the tenant level is created, and a multi-level tenant architecture is constructed.
In this embodiment, the total number of tenant types required by the multi-hierarchy tenant architecture may be determined first, if three tenant types, four tenant types, and the like are required, then, tenant hierarchies are configured for the tenant types, three tenant hierarchies are configured for the three tenant types, four tenant hierarchies are configured for the four tenant types, and each tenant hierarchy corresponds to a different tenant type, that is, the tenant hierarchies correspond to the tenant types one to one. Then, a plurality of tenant nodes can be created on each tenant level, and the tenant types of the tenant nodes on the same tenant level are the same and are the same as the tenant type corresponding to the tenant level, so that the construction of a multi-level tenant architecture is completed.
And step S103, creating a target tenant node in the tenant hierarchy.
The steps are mainly that after a tenant hierarchy corresponding to the tenant type of the target tenant node is determined, a new tenant node is directly established in the tenant hierarchy as the target tenant node, wherein the target tenant node and the current tenant node initiating the tenant node establishing request can be subjected to resource management and configuration by the same tenant, and because the new tenant node is not directly established in the current tenant node but established in the existing tenant hierarchy, the tenant hierarchy is not increased due to the increase of the number of the established tenant nodes in the tenant node establishing process, so that the number of the hierarchy of the multi-level tenant architecture can be kept unchanged, the time complexity of the implementation logic of the multi-level tenant architecture is low, for example, for the multi-level tenant architecture with the tenant level 3, the time complexity of its implementation logic is O (1).
The method for creating the tenant node based on the multi-level tenant system structure comprises the steps of firstly obtaining a tenant node creating request initiated by a current tenant node, then determining a tenant level corresponding to a target tenant node in the multi-level tenant system structure according to the tenant type of the target tenant node carried in the tenant node creating request, wherein the multi-level tenant system structure comprises a plurality of tenant levels, each tenant level corresponds to different tenant types, and then creating the target tenant node in the tenant level. According to the scheme, the corresponding tenant hierarchy can be searched according to the tenant type to which the target tenant node to be created belongs, a new tenant node is created on the tenant hierarchy, and the new tenant hierarchy cannot be added in the creation process of the tenant node, so that the number of the tenant hierarchies of the whole tenant system cannot be increased along with the increase of the tenant node, the number of the hierarchies of a multi-level tenant system structure can be kept constant, and the time complexity of logic implementation of the multi-level tenant system is reduced.
In an embodiment, a sub-tenant node may be further configured for a newly created target tenant node, so that the target tenant node can perform resource allocation, management, and other operations for its sub-tenant node, and after step S103, the following steps may be further included:
determining a sub-tenant level subordinate to a target tenant level based on a multi-level tenant system structure; creating a child tenant node of the target tenant node in the child tenant hierarchy.
In this embodiment, the target tenant level refers to a tenant level corresponding to a tenant type to which the target tenant node belongs. Taking a three-level tenant architecture as an example, a tenant type to which a target tenant node belongs is set as a tenant type B, the tenant level B corresponds to an intermediate layer in the three-level tenant architecture, and the target tenant level refers to the intermediate layer.
In the multi-level tenant system structure, a certain hierarchy relationship is formed among tenant levels, a tenant node with a higher tenant level can perform resource allocation and management on a sub-tenant node under the tenant node, the step can be based on the multi-level tenant system structure, a newly created sub-tenant level under a target tenant level is determined, the target tenant level is set as a middle layer by taking a three-level tenant system structure as an example, and the sub-tenant level under the target tenant level can be determined as a bottom layer according to the three-level tenant system structure. A child tenant node of the target tenant node may then be created in the child tenant hierarchy. According to the scheme for creating the child nodes for the target tenant node, on the premise that the number of tenant levels of the multi-level tenant architecture is not increased, the effect of creating the child tenant nodes for the target tenant node is achieved, and the target tenant node can be created and managed conveniently.
In one embodiment, a multi-level tenant architecture includes three tenant levels; the tenant types include a top tenant, a middle tenant, and a bottom tenant.
The embodiment mainly adopts a three-level structure as the multi-level tenant architecture. In this embodiment, the multi-level tenant architecture includes a total of three tenant levels, and correspondingly, the tenant types also include three types, which correspond to the three tenant levels respectively. The tenant type can include a top tenant, a middle tenant and a bottom tenant, the top tenant corresponds to a top level of the three tenant levels, the middle tenant corresponds to a middle level of the three tenant levels, and the bottom tenant corresponds to a bottom level of the three tenant levels. The tenant levels have a certain hierarchical relationship, and the hierarchical relationship can be used for determining the logical relationship of resource allocation and management of different levels, wherein the bottom level is the lowest level in a three-level tenant architecture and is the subordinate level of the middle level, the middle level is the subordinate level of the top level, the top level is the highest level in the three-level tenant architecture, only one tenant node is usually arranged in the top level, the tenant node of the top level can define resources and allocate the resources to the tenant node of the middle level, and the tenant node of the middle level can obtain the resources from the tenant node of the top level and allocate the resources to the tenant node of the bottom level. The three-level structure of the embodiment is adopted as a tenant architecture, so that the requirements on resource allocation and management can be met, the tenant level set by the tenant architecture is constant 3, and the logic time complexity is O (1).
Furthermore, the multi-level tenant architecture can be used as a multi-level tenant architecture of a cloud service platform, and resources provided by the cloud service platform can be conveniently distributed and managed based on the multi-level tenant architecture. The multi-level tenant system structure can adopt a three-level tenant system structure, the top-level tenant is set as a platform owner, the middle-level tenant is set as a platform operator, and the bottom-level tenant is set as a common tenant.
In one embodiment, the tenant node creation request in step S101 may be initiated by a tenant node corresponding to a common tenant, that is, the tenant type to which the current tenant node belongs may be a common tenant, and the tenant type to which the target tenant node belongs may be a platform operator. That is, when an ordinary tenant wants to become a platform operator, a tenant node creation request may be initiated, a new tenant node is created at a tenant level where the platform operator is located, and since the tenant type of the new tenant node is the platform operator, the ordinary tenant that originally initiated the tenant node creation request can further create and manage a child tenant node of the new tenant node in the new tenant node, and perform operations such as resource allocation and management.
In one embodiment, the tenant node with the platform owner can be used for defining resources and allocating the resources to the tenant node with the platform operator, the tenant node with the platform operator is used for acquiring the resources from the tenant node with the platform owner and allocating the resources to the tenant node with the common tenant; the tenant node of which the type is common tenant is used for acquiring resources from the tenant node of which the type is a platform operator, and the common tenant cannot allocate the resources to other common tenants.
The scheme provided by the embodiment can meet the requirements of the fields such as the cloud service platform and the like on multi-level tenants, namely multi-level management on resource isolation and allocation, and meanwhile, the time complexity of realizing logic is not increased along with the increase of levels, and the resource isolation and pricing strategy is simpler to realize.
In order to more clearly clarify the technical solution provided by the present invention, a tenant node creation method based on a multi-level tenant architecture provided by an embodiment of the present invention is described with reference to fig. 2 and 3:
as shown in fig. 2, fig. 2 is a schematic diagram of a principle of creating a tenant node in a multi-level tenant architecture, where the principle is a principle of creating a tenant node adopted in the conventional technology: under the preset condition, the platform owner corresponds to the top layer, and the platform operator corresponds to the intermediate level, and tenant a corresponds to the bottom, and wherein, tenant a is platform operator's tenant originally, and tenant a needs to become platform operator now, directly grants platform operator's identity for tenant a this moment, also is that tenant a possess 2 identities simultaneously: the tenant and the platform operator then create two sub-tenant nodes at the tenant node corresponding to the tenant a, namely, the sub-tenant nodes corresponding to the tenant b1 and the tenant b2, and thus, the hierarchy number of the multi-level tenant architecture is increased by 1 level; on this basis, if a tenant b1 of tenant a (platform operator a) now wants to become a platform operator, then the operator identity is directly granted to tenant b1, that is, tenant b1 has 2 identities at the same time: the tenant and the platform operator then create two sub-tenant nodes, i.e., tenant c1 and tenant c2, at the tenant node corresponding to the tenant b1, so that the level of the multi-level tenant architecture is incremented. The tenant system is an infinite hierarchy tree structure from a logic design to an implementation mode, except leaf nodes, any intermediate node has double identities, namely a child tenant of an upper node and a parent tenant of a lower node, the design can cause the complexity of technical implementation to be increased, for example, n-level self-defined resource isolation strategies and pricing strategies need to be supported, one intermediate node firstly needs to purchase resources to the upper node in order to distribute the resources to the lower node, but if a resource pool of the upper node is not enough, the upper node needs to continuously apply for the resources to the upper node, and so on, the situation is more difficult to handle as the hierarchies are more, and for example, as the hierarchies are increased, the logic and the flow of generating bills are more and more complicated.
As shown in fig. 3, fig. 3 is a schematic diagram of a principle of creating a tenant node in a multi-hierarchy tenant architecture in an embodiment, where the principle is a principle of creating a tenant node adopted in each embodiment of the present invention, under a preset condition, a platform owner corresponds to a top layer, a platform operator corresponds to an intermediate layer, a tenant a corresponds to a bottom layer, the tenant a is originally a tenant of a platform operator, and if the tenant a needs to become a platform operator, an identity of a platform operator b is opened for the tenant a, and then a sub-tenant node can be created in the tenant node corresponding to the platform operator b, that is, the tenant node corresponding to the tenant b1 and the tenant b2, where at this time, the hierarchy number of the multi-hierarchy tenant architecture is still 3 and is not increased along with creation of the tenant node; on this basis, if a tenant b1 of a tenant a (platform operator b) wants to become a platform operator, the identity of a platform operator c is opened for the tenant b1, and then a sub-tenant node, that is, a tenant node corresponding to the tenant c1 and a tenant c2, can be created in the tenant node corresponding to the platform operator c, at this time, the level number of the multi-level tenant architecture is still not increased along with the creation of the tenant node, and is still 3.
For the two ways of creating tenant nodes in the multi-level tenant architecture, the time complexity in technical implementation can be analyzed as follows: for a certain input value n, if the execution time of the algorithm is a function f (n) of n, the time complexity of the algorithm is O (n), and if the execution time of the algorithm is a fixed constant, the time complexity of the algorithm is O (1). For the two multi-level tenant systems, the first method is an n-level structure with uncertain implementation logic, the execution time of the code increases according to the increase of the level n, so the time complexity is O (n), while the second method is a 3-level structure with fixed implementation logic no matter how many tenant nodes need to be created, the execution time of the code does not change with n, so the time complexity is O (1). Therefore, the method provided by the embodiment of the invention is adopted to create the tenant node, and the time complexity of the logic realization of the multi-level tenant system can be effectively reduced.
In an embodiment, a multi-level tenant architecture based tenant node creation apparatus is provided, and referring to fig. 4, fig. 4 is a block diagram of the multi-level tenant architecture based tenant node creation apparatus in an embodiment, and the multi-level tenant architecture based tenant node creation apparatus may include:
a request obtaining module 101, configured to obtain a tenant node creation request; the tenant node creation request is initiated by the current tenant node; the tenant node creation request carries the tenant type of a target tenant node to be created;
the hierarchy determining module 102 is configured to determine, according to a tenant type, a tenant hierarchy corresponding to the tenant type in a multi-level tenant architecture; the multi-level tenant system structure comprises a plurality of tenant levels, and each tenant level corresponds to different tenant types;
a node creation module 103 for creating a target tenant node in the tenant hierarchy.
In an embodiment, the tenant node creation apparatus based on a multi-level tenant architecture may further include:
the child tenant node creating module is used for determining a child tenant level subordinate to the target tenant level based on a multi-level tenant architecture; the target tenant level is a tenant level corresponding to the tenant type to which the target tenant node belongs; creating a child tenant node of the target tenant node in the child tenant hierarchy.
In one embodiment, a multi-level tenant architecture includes three tenant levels; the tenant type comprises a top-level tenant, a middle-level tenant and a bottom-level tenant; the top-level tenant corresponds to the top level of the three tenant levels, the middle-level tenant corresponds to the middle level of the three tenant levels, and the bottom-level tenant corresponds to the bottom level of the three tenant levels; the bottom layer is the subordinate level of the middle layer, and the middle layer is the subordinate level of the top layer.
In one embodiment, the multi-level tenant architecture is a multi-level tenant architecture of a cloud service platform; the top tenant is a platform owner, the middle tenant is a platform operator, and the bottom tenant is a common tenant. In one embodiment, the tenant node of which the type is a platform owner is used for defining resources and allocating the resources to the tenant node of which the type is a platform operator; the tenant node with the type of the tenant as a platform operator is used for acquiring resources from the tenant node with the type of the tenant as a platform owner and distributing the resources to the tenant node with the type of the tenant as a common tenant; and the tenant node of which the type is common tenant is used for acquiring resources from the tenant node of which the type is a platform operator.
In one embodiment, the tenant type to which the current tenant node belongs is the common tenant; and the type of the tenant of the target tenant node is the platform operator.
In an embodiment, the tenant node creation apparatus based on a multi-level tenant architecture may further include:
an architecture creation module to determine a plurality of tenant types; configuring a plurality of tenant levels; the plurality of tenant hierarchies correspond to a plurality of tenant types, respectively; on a tenant level, a tenant node matched with the tenant type of the tenant level is created, and a multi-level tenant architecture is constructed.
The tenant node creating device based on the multi-level tenant architecture corresponds to the tenant node creating method based on the multi-level tenant architecture one to one, specific limitations on the tenant node creating device based on the multi-level tenant architecture can be referred to the above limitations on the tenant node creating method based on the multi-level tenant architecture, and technical features and beneficial effects described in the embodiment of the tenant node creating method based on the multi-level tenant architecture are both applicable to the embodiment of the tenant node creating device based on the multi-level tenant architecture, and are not described herein again. The modules in the tenant node creation apparatus based on the multi-level tenant architecture can be wholly or partially implemented by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, the computer device may be a server, the internal structure of which may be as shown in fig. 5, and fig. 5 is an internal structure of the computer device in one embodiment. The computer device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The database of the computer device may be used to store data such as tenant node creation requests, tenant types, multi-level tenant architectures, and the like. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a tenant node creation method based on a multi-level tenant architecture.
Those skilled in the art will appreciate that the configuration shown in fig. 5 is a block diagram of only a portion of the configuration associated with aspects of the present invention and is not intended to limit the computing devices to which aspects of the present invention may be applied, and that a particular computing device may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided, which includes a processor and a memory, the memory storing a computer program, the processor implementing the tenant node creation method based on a multi-level tenant architecture as described in any one of the above embodiments when executing the computer program.
In one embodiment, there is provided a computer device comprising a processor and a memory, the memory storing a computer program which when executed by the processor performs the steps of:
acquiring a tenant node creation request; the tenant node creation request is initiated by the current tenant node; the tenant node creation request carries the tenant type of a target tenant node to be created; determining a tenant level corresponding to the tenant type in a multi-level tenant architecture according to the tenant type; the multi-level tenant system structure comprises a plurality of tenant levels, and each tenant level corresponds to different tenant types; creating the target tenant node in a tenant hierarchy.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
determining a sub-tenant level subordinate to a target tenant level based on a multi-level tenant system structure; the target tenant level is a tenant level corresponding to the tenant type to which the target tenant node belongs; creating a child tenant node of the target tenant node in the child tenant hierarchy.
In one embodiment, a multi-level tenant architecture includes three tenant levels; the tenant type comprises a top-level tenant, a middle-level tenant and a bottom-level tenant; the top-level tenant corresponds to the top level of the three tenant levels, the middle-level tenant corresponds to the middle level of the three tenant levels, and the bottom-level tenant corresponds to the bottom level of the three tenant levels; the bottom layer is the subordinate level of the middle layer, and the middle layer is the subordinate level of the top layer.
In one embodiment, the multi-level tenant architecture is a multi-level tenant architecture of a cloud service platform; the top tenant is a platform owner, the middle tenant is a platform operator, and the bottom tenant is a common tenant.
In one embodiment, the tenant node of which the type is a platform owner is used for defining resources and allocating the resources to the tenant node of which the type is a platform operator; the tenant node with the type of the tenant as a platform operator is used for acquiring resources from the tenant node with the type of the tenant as a platform owner and distributing the resources to the tenant node with the type of the tenant as a common tenant; and the tenant node of which the type is common tenant is used for acquiring resources from the tenant node of which the type is a platform operator.
In one embodiment, the type of the tenant to which the current tenant node belongs is a common tenant; and the type of the tenant to which the target tenant node belongs is a platform operator.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
determining a plurality of tenant types; configuring a plurality of tenant levels; the plurality of tenant hierarchies correspond to a plurality of tenant types, respectively; on a tenant level, a tenant node matched with the tenant type of the tenant level is created, and a multi-level tenant architecture is constructed.
According to the computer equipment, through the computer program running on the processor, the corresponding tenant level can be found according to the tenant type to which the target tenant node to be created belongs, a new tenant node is created on the tenant level, and the new tenant level cannot be increased in the creation process of the tenant node, so that the number of the tenant levels of the whole tenant system cannot be increased along with the increase of the tenant nodes, the number of the levels of the multi-level tenant system structure can be kept constant, and the time complexity of logic implementation of the multi-level tenant system is reduced.
One of ordinary skill in the art will appreciate that all or part of the processes in the method for creating a tenant node based on a multi-level tenant architecture according to any of the above embodiments may be implemented by a computer program, which may be stored in a non-volatile computer-readable storage medium, for instructing related hardware to implement the processes of the embodiments of the methods. Any reference to memory, storage, databases, or other media used in embodiments provided herein may include non-volatile and/or volatile memory. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
Accordingly, a computer-readable storage medium is also provided in an embodiment, and a computer program is stored thereon, wherein the program when executed by a processor implements the tenant node creation method based on a multi-level tenant architecture as described in any one of the above embodiments.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of:
acquiring a tenant node creation request; the tenant node creation request is initiated by the current tenant node; the tenant node creation request carries the tenant type of a target tenant node to be created; determining a tenant level corresponding to the tenant type in a multi-level tenant architecture according to the tenant type; the multi-level tenant system structure comprises a plurality of tenant levels, and each tenant level corresponds to different tenant types; creating the target tenant node in a tenant hierarchy.
In one embodiment, the computer program when executed by the processor further performs the steps of:
determining a sub-tenant level subordinate to a target tenant level based on a multi-level tenant system structure; the target tenant level is a tenant level corresponding to the tenant type to which the target tenant node belongs; creating a child tenant node of the target tenant node in the child tenant hierarchy.
In one embodiment, a multi-level tenant architecture includes three tenant levels; the tenant type comprises a top-level tenant, a middle-level tenant and a bottom-level tenant; the top-level tenant corresponds to the top level of the three tenant levels, the middle-level tenant corresponds to the middle level of the three tenant levels, and the bottom-level tenant corresponds to the bottom level of the three tenant levels; the bottom layer is the subordinate level of the middle layer, and the middle layer is the subordinate level of the top layer.
In one embodiment, the multi-level tenant architecture is a multi-level tenant architecture of a cloud service platform; the top tenant is a platform owner, the middle tenant is a platform operator, and the bottom tenant is a common tenant.
In one embodiment, the tenant node of which the type is a platform owner is used for defining resources and allocating the resources to the tenant node of which the type is a platform operator; the tenant node with the type of the tenant as a platform operator is used for acquiring resources from the tenant node with the type of the tenant as a platform owner and distributing the resources to the tenant node with the type of the tenant as a common tenant; and the tenant node of which the type is common tenant is used for acquiring resources from the tenant node of which the type is a platform operator.
In one embodiment, the type of the tenant to which the current tenant node belongs is a common tenant; and the type of the tenant to which the target tenant node belongs is a platform operator.
In one embodiment, the computer program when executed by the processor further performs the steps of:
determining a plurality of tenant types; configuring a plurality of tenant levels; the plurality of tenant hierarchies correspond to a plurality of tenant types, respectively; on a tenant level, a tenant node matched with the tenant type of the tenant level is created, and a multi-level tenant architecture is constructed.
According to the computer readable storage medium, through the stored computer program, the corresponding tenant hierarchy can be found according to the tenant type to which the target tenant node to be created belongs, a new tenant node is created on the tenant hierarchy, and the new tenant hierarchy is not added in the creation process of the tenant node, so that the number of the tenant hierarchies of the whole tenant system is not increased along with the increase of the tenant nodes, the number of the hierarchies of the multi-hierarchy tenant system structure can be kept constant, and the time complexity of logic implementation of the multi-hierarchy tenant system is reduced.
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present invention, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the inventive concept, which falls within the scope of the present invention. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. A tenant node creating method based on a multi-level tenant architecture is characterized by comprising the following steps:
acquiring a tenant node creation request; the tenant node creation request is initiated by the current tenant node; the tenant node creating request carries the tenant type of the target tenant node to be created;
determining a tenant hierarchy corresponding to the tenant type in a multi-hierarchy tenant architecture according to the tenant type; the multi-hierarchy tenant architecture comprises a plurality of tenant hierarchies, and each tenant hierarchy corresponds to different tenant types;
creating the target tenant node in the tenant hierarchy.
2. The method of claim 1, further comprising, after the step of creating the target tenant node in the tenant hierarchy,:
determining a sub-tenant level subordinate to a target tenant level based on the multi-level tenant architecture; the target tenant level is a tenant level corresponding to the tenant type to which the target tenant node belongs;
creating a child tenant node of the target tenant node in the child tenant hierarchy.
3. The method of claim 1, wherein the multi-tier tenant architecture comprises three tenant tiers; the tenant types comprise a top-level tenant, a middle-level tenant and a bottom-level tenant; wherein the content of the first and second substances,
the top tenant corresponds to a top level of the three tenant levels, the middle level tenant corresponds to a middle level of the three tenant levels, and the bottom level tenant corresponds to a bottom level of the three tenant levels; the bottom layer is a subordinate level of the middle layer, and the middle layer is a subordinate level of the top layer.
4. The method of claim 3, wherein the multi-level tenant architecture is a multi-level tenant architecture of a cloud service platform; the top-level tenant is a platform owner, the middle-level tenant is a platform operator, and the bottom-level tenant is a common tenant.
5. The method of claim 4,
the tenant node with the type of the tenant as a platform owner is used for defining resources and distributing the resources to the tenant node with the type of the tenant as a platform operator;
the tenant node with the type of the tenant as a platform operator is used for acquiring resources from the tenant node with the type of the tenant as a platform owner and distributing the resources to the tenant node with the type of the tenant as a common tenant;
and the tenant node of which the type is common tenant is used for acquiring resources from the tenant node of which the type is a platform operator.
6. The method according to claim 4, wherein the tenant type to which the current tenant node belongs is the common tenant; the tenant type of the target tenant node is the platform operator.
7. The method of claim 1, further comprising the step of:
determining a plurality of tenant types;
configuring a plurality of tenant levels; the plurality of tenant hierarchies correspond to the plurality of tenant types, respectively;
and on the tenant level, creating a tenant node matched with the tenant type of the tenant level, and constructing the multi-level tenant architecture.
8. A tenant node creation apparatus based on a multi-hierarchy tenant architecture, comprising:
the request acquisition module is used for acquiring a tenant node creation request; the tenant node creation request is initiated by the current tenant node; the tenant node creating request carries the tenant type of the target tenant node to be created;
the hierarchy determining module is used for determining a tenant hierarchy corresponding to the tenant type in a multi-level tenant architecture according to the tenant type; the multi-hierarchy tenant architecture comprises a plurality of tenant hierarchies, and each tenant hierarchy corresponds to different tenant types;
a node creation module to create the target tenant node in the tenant hierarchy.
9. A computer device comprising a processor and a memory, said memory storing a computer program, characterized in that said processor, when executing said computer program, implements the steps of the method according to any one of claims 1 to 7.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910845826.0A CN110365547B (en) | 2019-09-09 | 2019-09-09 | Method, device and equipment for creating tenant node of multi-level tenant system and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910845826.0A CN110365547B (en) | 2019-09-09 | 2019-09-09 | Method, device and equipment for creating tenant node of multi-level tenant system and computer readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110365547A CN110365547A (en) | 2019-10-22 |
| CN110365547B true CN110365547B (en) | 2019-12-24 |
Family
ID=68225505
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910845826.0A Active CN110365547B (en) | 2019-09-09 | 2019-09-09 | Method, device and equipment for creating tenant node of multi-level tenant system and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110365547B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110730106B (en) * | 2019-12-18 | 2020-04-17 | 数字广东网络建设有限公司 | Electronic official document exchange method and device based on tree structure and computer equipment |
| CN111865943B (en) * | 2020-07-02 | 2023-04-07 | 北京同创永益科技发展有限公司 | Multi-level tenant authentication method and device based on micro-service |
| CN112532632B (en) * | 2020-11-30 | 2022-10-28 | 数字广东网络建设有限公司 | Resource allocation method and device for multi-level cloud platform and computer equipment |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104123616A (en) * | 2014-07-25 | 2014-10-29 | 南京邮电大学 | Cloud computing system towards multiple tenants |
| CN104144143A (en) * | 2013-05-08 | 2014-11-12 | 华为技术有限公司 | Network establishment method and control device |
| CN105917309A (en) * | 2014-01-20 | 2016-08-31 | 惠普发展公司，有限责任合伙企业 | Determining a permission of a first tenant with respect to a second tenant |
| CN108092806A (en) * | 2017-12-11 | 2018-05-29 | 国云科技股份有限公司 | A kind of administration of multiple roles method based on cloudy platform |
| CN108551399A (en) * | 2018-03-29 | 2018-09-18 | 深信服科技股份有限公司 | Dispositions method, system and the relevant apparatus serviced under a kind of cloud environment |
| CN109040276A (en) * | 2018-08-20 | 2018-12-18 | 郑州云海信息技术有限公司 | A kind of method, apparatus, computer storage medium and terminal constructing cloud platform |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10592293B2 (en) * | 2017-08-31 | 2020-03-17 | Cisco Technology, Inc. | Tenant-specific policy generation and enforcement within containers |
-
2019
- 2019-09-09 CN CN201910845826.0A patent/CN110365547B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104144143A (en) * | 2013-05-08 | 2014-11-12 | 华为技术有限公司 | Network establishment method and control device |
| CN105917309A (en) * | 2014-01-20 | 2016-08-31 | 惠普发展公司，有限责任合伙企业 | Determining a permission of a first tenant with respect to a second tenant |
| CN104123616A (en) * | 2014-07-25 | 2014-10-29 | 南京邮电大学 | Cloud computing system towards multiple tenants |
| CN108092806A (en) * | 2017-12-11 | 2018-05-29 | 国云科技股份有限公司 | A kind of administration of multiple roles method based on cloudy platform |
| CN108551399A (en) * | 2018-03-29 | 2018-09-18 | 深信服科技股份有限公司 | Dispositions method, system and the relevant apparatus serviced under a kind of cloud environment |
| CN109040276A (en) * | 2018-08-20 | 2018-12-18 | 郑州云海信息技术有限公司 | A kind of method, apparatus, computer storage medium and terminal constructing cloud platform |
Non-Patent Citations (1)
| Title |
|---|
| Warden多租户网络隔离设计与实现;赖春彬;《中国优秀硕士学位论文全文数据库 信息科技辑》;20160715;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110365547A (en) | 2019-10-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110365547B (en) | Method, device and equipment for creating tenant node of multi-level tenant system and computer readable storage medium | |
| US11316742B2 (en) | Stateless resource management | |
| US20190222633A1 (en) | Distributed partitioned map reduce using a data fabric | |
| US20160094626A1 (en) | System and method for classloading in a multitenant application server environment | |
| WO2020177548A1 (en) | Blockchain authority control method and device | |
| KR102230901B1 (en) | Quality of service support method and apparatus for cloud resource management | |
| US20100125893A1 (en) | Techniques for enforcing access rights during directory access | |
| US20180067848A1 (en) | Memory access control method and system | |
| US20240104059A1 (en) | Method for Service Processing and System, Device, and Medium | |
| CN109033365B (en) | Data processing method and related equipment | |
| US11948005B2 (en) | Managed integration of constituent services of multi-service applications | |
| US10740332B2 (en) | Memory-aware plan negotiation in query concurrency control | |
| CN110673787A (en) | Volume configuration method and device | |
| CN110941681B (en) | Multi-tenant data processing system, method and device of power system | |
| CN112181599A (en) | Model training method, device and storage medium | |
| US10956363B2 (en) | Automated data management via machine-readable data definition files | |
| US9009731B2 (en) | Conversion of lightweight object to a heavyweight object | |
| US20150052109A1 (en) | Network-backed file system | |
| CN110532533B (en) | Form precision collocation method, device, computer equipment and storage medium | |
| CN114328650A (en) | Database resource management method and device, computer equipment and storage medium | |
| WO2022110786A1 (en) | Resource scheduling method, apparatus, and system | |
| Setaouti et al. | Fault tolerance model based on service delivery quality levels in cloud computing | |
| US9531713B2 (en) | Method and system for enabling and disabling execution of computer instructions | |
| CN110045930B (en) | Method, device, equipment and medium for virtual platform to manage storage equipment volume | |
| US11855908B2 (en) | Resource allocation in cloud computing systems |
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 | ||
| CP02 | Change in the address of a patent holder |
Address after: 7, 9-12 / F, Zhujiang Yide building, 362 Dongfeng Middle Road, Yuexiu District, Guangzhou, Guangdong 510000 Patentee after: DIGITAL GUANGDONG NETWORK CONSTRUCTION Co.,Ltd. Address before: 510300 room 230, building 14, No. 788, Guangzhou Avenue South, Haizhu District, Guangzhou City, Guangdong Province Patentee before: DIGITAL GUANGDONG NETWORK CONSTRUCTION Co.,Ltd. |
|
| CP02 | Change in the address of a patent holder |