CN114827275A - Management platform of federated tenants and resource management method of federated tenants - Google Patents
Management platform of federated tenants and resource management method of federated tenants Download PDFInfo
- Publication number
- CN114827275A CN114827275A CN202210399719.1A CN202210399719A CN114827275A CN 114827275 A CN114827275 A CN 114827275A CN 202210399719 A CN202210399719 A CN 202210399719A CN 114827275 A CN114827275 A CN 114827275A
- Authority
- CN
- China
- Prior art keywords
- tenant
- federal
- resource
- federated
- console
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000007726 management method Methods 0.000 title claims abstract description 136
- 238000010276 construction Methods 0.000 claims abstract description 5
- 238000000034 method Methods 0.000 claims description 19
- 230000004048 modification Effects 0.000 claims description 9
- 238000012986 modification Methods 0.000 claims description 9
- 238000012217 deletion Methods 0.000 claims description 7
- 230000037430 deletion Effects 0.000 claims description 7
- 238000012795 verification Methods 0.000 claims description 3
- 238000010586 diagram Methods 0.000 description 11
- 238000004590 computer program Methods 0.000 description 7
- 230000008859 change Effects 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 5
- 230000006978 adaptation Effects 0.000 description 4
- 238000004891 communication Methods 0.000 description 4
- 238000013519 translation Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 230000002776 aggregation Effects 0.000 description 1
- 238000004220 aggregation Methods 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000001953 sensory effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a management platform of a federated tenant and a resource management method of the federated tenant. The management platform of the federal tenant comprises a federal tenant construction module and a tenant resource management module; the federated tenant management module is used for constructing federated tenants, the federated tenants comprise at least one member tenant, and each member tenant comprises a main tenant; and the tenant resource management module is used for managing tenant resources through a federal console and/or a tenant console. The invention can provide the user with the resource unified display and unified management of cross-region and cross-cluster, thereby greatly improving the resource management efficiency of the Federal cloud.
Description
Technical Field
The invention relates to the technical field of network resource management, in particular to a management platform of a federated tenant and a resource management method of the federated tenant.
Background
Tenants are one way to share resources in a computer system. In a relatively large computer cluster, a plurality of users may share cluster resources, and when a plurality of users share resources, some users may occupy too many resources and some users may not obtain the resources. In order to embody the fairness principle and avoid unreasonable resource preemption of users when sharing resources, a tenant technology is introduced. The tenant sets some restrictions for the user when using the resources, for example, an upper limit may be set for the amount of resources such as a GPU and a memory used by a certain user, and the GPU resources may be prohibited or released from being used.
In a global context, enterprises usually conduct business in different countries and different cities. Businesses of an enterprise in different regions are usually deployed on different clusters, and the different clusters may be deployed on regions of multiple public clouds or on private clouds in different regions. The same user may have tenant resources on different clusters. These tenants scattered in different regions bring about a certain difficulty for the user to manage their resources. Existing tenant mechanisms, such as the Namespace + resourcequta technology provided by kubernets cluster, can only take effect in a single cluster; the federated Namespace technology provides cross-cluster resource management, but the resources are still independent under the same name Namespace on each cluster; on public clouds, the same VPC cannot be created across regions (data center clusters).
Disclosure of Invention
The invention provides a management platform of a federated tenant and a resource management method of the federated tenant, so as to realize unified tenant resource management.
According to one aspect of the invention, a management platform of federated tenants is provided, and the platform comprises a federated tenant construction module and a tenant resource management module;
the federated tenant management module is used for constructing federated tenants, the federated tenants comprise at least one member tenant, and each member tenant comprises a main tenant;
and the tenant resource management module is used for managing tenant resources through a federal console and/or a tenant console.
Optionally, the platform further includes a user identity management module;
the user identity management module is used for carrying out user identity verification when a user logs in, when the user logs in through the federal console, the user obtains the authority of a federal administrator, and when the user logs in through the tenant console, the user obtains the authority of member tenants.
Optionally, the tenant resource management module includes a main tenant management unit and a member tenant management unit;
the main tenant management unit is used for managing upper resources of each member tenant through the federal console;
and the member tenant management unit is used for managing the tenant resources of each member tenant through the tenant console.
Optionally, the platform further includes a tenant snapshot management module;
the tenant snapshot management module is used for managing the federal tenant snapshot of the federal tenant, and the federal tenant snapshot is formed by the main tenant according to the upper-layer resource information of each member tenant.
Optionally, the federal tenant management module is further configured to:
and receiving a quit request of the member tenant, and removing the member tenant from the federated tenant according to the quit request.
According to another aspect of the present invention, a resource management method for federated tenants is provided, which is applied to a main tenant of the federated tenants, and the method includes:
receiving a resource management request through a federal console;
and determining target tenants and target upper-layer resources in member tenants according to the resource management request, and managing the target upper-layer resources under the target tenants through the federal console.
Optionally, the resource management request includes a resource deployment request, a resource query request, a resource modification request, and/or a resource deletion request.
Optionally, the method further includes:
and receiving upper-layer resource information sent by the member tenant, forming a federal tenant snapshot of the federal tenant according to the upper-layer resource information, and displaying the federal tenant snapshot through the federal console.
Optionally, the managing, by the federal console, target upper layer resources under the target tenant includes:
when the resource management request is the resource deployment request;
and acquiring the federal tenant snapshot, adding resource information of the target upper-layer resource in the federal tenant snapshot according to the resource deployment request, and deploying the target upper-layer resource under the target tenant through the federal console.
Optionally, the managing, by the federal console, target upper layer resources under the target tenant includes:
when the resource management request is the resource query request, the resource modification request or the resource deletion request;
and determining a target resource management mode according to the resource management request, managing the target upper-layer resources in the target resource management mode under the target tenant through the federal console, and updating the snapshot of the federal tenant.
According to the technical scheme of the embodiment of the invention, a management platform of the federal tenant is built, and the management platform comprises a federal tenant construction module and a tenant resource management module; the system comprises a federal tenant management module, a member tenant management module and a member tenant management module, wherein the federal tenant management module is used for constructing a federal tenant, the federal tenant comprises at least one member tenant, and each member tenant comprises a main tenant; and the tenant resource management module is used for managing tenant resources through the federal console and/or the tenant console. Unified tenant resource management can be achieved, cross-region and cross-cluster resource unified display is provided for users, and the resource management efficiency of the Federal cloud is greatly improved.
It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present invention, nor do they necessarily limit the scope of the invention. Other features of the present invention will become apparent from the following description.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, 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 structural diagram of a management platform of a federated tenant provided in an embodiment of the present invention;
fig. 2 is a schematic diagram of a federal tenant constructed by a management platform of a federated tenant provided in an embodiment of the present invention;
fig. 3 is a schematic diagram of a first application of a management platform of a federated tenant according to an embodiment of the present invention;
fig. 4 is a schematic diagram of a second application of a management platform of a federated tenant provided in an embodiment of the present invention;
fig. 5 is a schematic diagram illustrating a principle of forming a snapshot of a federal tenant in a management platform of a federated tenant according to an embodiment of the present invention;
fig. 6 is a flowchart of a resource management method for federated tenants according to a second embodiment of the present invention.
Detailed Description
In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
It should be noted that the terms "main", "upper", "first", "second", and the like in the description and the claims of the present invention and the drawings described above are used for distinguishing similar objects, and are not necessarily used for describing a specific order or sequence. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
Example one
Fig. 1 is a schematic structural diagram of a management platform of a federated tenant provided in an embodiment of the present invention. As shown in fig. 1, the management platform of a federal tenant may include a federal tenant build module 10 and a tenant resource management module 20.
The federal tenant management module 10 may be configured to construct a federal tenant, where the federal tenant includes at least one member tenant, and each member tenant includes one main tenant.
In practical application, the federal tenant is a core technology of the federal cloud, users can create different federal tenants through the federal tenant management module 10 according to the overall requirements of services, and tenants with the same requirements located in different regions and different clusters can be added into one federal tenant to cooperate to complete a common target. The federated tenant can realize centralized and unified management on tenant resources and data of cross clusters.
Specifically, a user can create a federal tenant on a federal cloud master control cluster, and the federal cloud deploys a set of federal consoles for the federal tenant, so as to centrally manage member tenants under the federal tenant.
Fig. 2 is a schematic diagram of a federated tenant constructed by a management platform of a federated tenant provided in an embodiment of the present invention. As shown in fig. 2, a user may apply for adding his/her Tenant into the federal Tenant, or may apply for adding tenants located in different regions and different clusters into the federal cloud cluster, so as to form a federal Tenant Federation Tenant.
The tenant resource management module 20 may be configured to manage tenant resources through a federal console and/or a tenant console.
In this embodiment, the federated tenant has external permissions that are visible to the user by the member tenants, such as application lifecycle management and resource quota management in the member tenants. But the member tenants still have some independent and autonomous rights, such as the users under the tenants can be managed.
Optionally, the management platform of the federal tenant provided in this embodiment may further include a user identity management module.
The user identity management module can be used for carrying out user identity verification when a user logs in, when the user logs in through the federal console, the user obtains the authority of the federal administrator, and when the user logs in through the tenant console, the user obtains the authority of member tenants.
Specifically, users in the federated tenant can achieve unified identity authentication in multiple clusters. A user who logs on to the federal console has the user identity of the primary tenant throughout the federal tenant, and the user has equal rights in the original tenant in the federal tenant.
Optionally, the tenant resource management module 20 may include a main tenant management unit and a member tenant management unit.
And the main tenant management unit can be used for managing the upper-layer resources of each member tenant through the federal console.
In particular, the federal tenant has a unified console, referred to as the federal console. The main tenant can uniformly manage member tenants of the federal tenant and upper-layer resources of the member tenants on the cross-region multi-cluster through the federal console. In addition, a federated tenant may manage different versions of tenants.
The management of computing resources to member tenants can include deployment, synchronization, deletion, modification, querying, data access, and the like of applications in the tenants.
1) Inquiring, modifying and deleting resources: the federal console supports request routing towards certain resources. When a request containing a global unique resource identifier is given, the federal console can find an access entry of the API of the member tenant of the resource and send the access entry to the corresponding member tenant. With this capability, the primary tenant can implement query, modify, and delete operations for a given resource.
2) Deployment of resources: the federal console supports request routing towards a certain member tenant. When a request containing cluster and member tenant information is given, the federal console discovers an API access entry of the member tenant and issues the request, thereby supporting the capability of creating resources in the given tenant.
3) Data access: the federal tenant console allows a primary tenant user to access member tenant's data with authorization, including but not limited to: and checking an access address of data, such as JDBC connection strings, directly accessing front-end interface browsing data of a big data product, checking a calculation task and the like.
The federal console can complete the admission of tenants of different versions by means of a tenant API adaptation layer. The federal console supports adaptation of different versions of each resource, and the adaptation mode can include: translation of the request target address, translation of the requesting entity, translation of the responding entity, etc. The federal console also supports the adaptation of requests by intercepting the request and proxying it to a local controller.
Exemplarily, fig. 3 is a schematic diagram of a first application of a management platform of a federated tenant provided according to an embodiment of the present invention. As shown in fig. 3, each tenant has its corresponding version of the tenant console and tenant API. The federal console is also the console of the main tenant in the federal tenant. The federal console inherits all functions of the main tenant console and has the capability of managing resources of other tenants in the federal tenant.
And the member tenant management unit can be used for managing the tenant resources of each member tenant through the tenant console.
In this embodiment, each member tenant in the federation has a separate console, which is called a tenant console. The member tenants can independently manage the tenant resources of the tenant through the tenant console. And the change of the upper-layer resources through the tenant console is visible to the Federal tenant console in real time.
Fig. 4 is a schematic diagram of a second application of a management platform for federated tenants according to an embodiment of the present invention. As shown in fig. 4, each tenant has its corresponding version of the tenant console and tenant API. And the user in the tenant performs identity authentication on the tenant console through single sign-on in the cluster and has the identity associated authority. And the tenant console communicates with system programs in the tenants and system services on the cloud platform through a uniform tenant API.
Optionally, the management platform of the federal tenant provided in this embodiment may further include a tenant snapshot management module.
And the tenant snapshot management module can be used for managing the federal tenant snapshot of the federal tenant, and the federal tenant snapshot is formed by the main tenant according to the upper-layer resource information of each member tenant.
In this embodiment, due to the characteristics of the federated tenant across clusters, across tenants, and across regions, the federated cloud introduces a concept of tenant snapshots for improving resource access efficiency and assisting in routing of resource requests. In the federal tenant, the top level resources of the member tenant are stored in the main tenant in the form of a snapshot. The federal console displays the federal leased resources for synchronization and aggregation on the upper federal console of each member tenant, and gives a globally unique resource identifier to the upper federal console. And by resource synchronization, the indoor upper-layer resource has the capability of unifying the views.
The federated tenant snapshot may have the following characteristics: only including the upper resources of the member tenants, and the sub-resources below the upper resources are still only stored in the original member tenants; each record in the snapshot contains information of a cluster and a tenant; when a user accesses a certain upper-layer resource or a sub-resource under the upper-layer resource, the federal console can locate a target resource through a snapshot and then route a request to a corresponding member tenant; the snapshot is read only for users, and users of the federal tenants can quickly acquire the overview of resources in member tenants through the snapshot, but the users cannot directly modify the content of the snapshot.
In addition, a Write-Through policy may be employed in creating the resource: when a user creates resources in a certain member tenant, the federal console generates a unique UUID in the federal tenant for the user, records the UUID, and submits the change to a target member tenant. If the change fails, the record is removed from the snapshot.
The Write-Around policy may be employed when updating resources: when a user updates a resource in a member tenant, the changes are directly committed to the target member tenant. The state is modified in place in the snapshot by the federal console through a synchronization mechanism.
Fig. 5 is a schematic diagram illustrating a principle of forming a snapshot of a federated tenant in a management platform of the federated tenant according to an embodiment of the present invention. As shown in fig. 5, C may represent a cluster, T may represent a tenant, R may represent an upper resource, and SR may represent a child resource of the tenant. For example, c1.t1.r1 represents resource 1 of tenant 1 in cluster 1.
The tenant snapshot technology synchronizes the states of member tenants distributed on multiple regions, clouds and clusters to a federal tenant in a snapshot mode, and performs unified view display in the federal tenant, so that a main tenant can conveniently manage multiple tenants. A snapshot list of the federal tenants in the federal tenants is read-only, when a main tenant initiates a state change operation on a certain member tenant in the federal tenants, a snapshot COW action is triggered, the tenant snapshot automatically routes the state change operation to an actual member tenant, and after the state change operation is completed, a new snapshot of the federal tenants is generated and synchronized to the main tenant.
Optionally, the federal tenant management module 10 may be further configured to:
and receiving a quit request of the member tenant, and removing the member tenant from the federal tenant according to the quit request.
Specifically, when the business is adjusted, the member tenant can freely join or leave the federate.
According to the technical scheme of the embodiment of the invention, a management platform of the federal tenant is built, and the management platform comprises a federal tenant construction module and a tenant resource management module; the system comprises a federal tenant management module, a member tenant management module and a member tenant management module, wherein the federal tenant management module is used for constructing a federal tenant, the federal tenant comprises at least one member tenant, and each member tenant comprises a main tenant; and the tenant resource management module is used for managing tenant resources through the federal console and/or the tenant console. Unified tenant resource management can be achieved, cross-region and cross-cluster resource unified display is provided for users, and the resource management efficiency of the Federal cloud is greatly improved.
Example two
Fig. 6 is a flowchart of a resource management method for federated tenants according to a second embodiment of the present invention. The embodiment is applicable to the same situation of managing tenant resources, and the method can be executed by a main tenant in the federated tenants. As shown in fig. 6, the method includes:
and S210, receiving a resource management request through a federal console.
Optionally, the resource management request may include a resource deployment request, a resource query request, a resource modification request, and/or a resource deletion request.
S220, determining target tenants and target upper-layer resources in member tenants according to the resource management requests, and managing the target upper-layer resources under the target tenants through a federal console.
Optionally, the resource management method for the federal tenant provided in this embodiment may further include:
and receiving upper-layer resource information sent by the member tenants, forming a federal tenant snapshot of the federal tenants according to the upper-layer resource information, and displaying the federal tenant snapshot through the federal console.
Optionally, the federal console is used to manage target upper layer resources of a target tenant, and the method can be implemented as follows:
1) when the resource management request is a resource deployment request; and acquiring a federal tenant snapshot, adding resource information of the target upper-layer resource in the federal tenant snapshot according to the resource deployment request, and deploying the target upper-layer resource under the target tenant through a federal console.
2) When the resource management request is a resource query request, a resource modification request or a resource deletion request; and determining a target resource management mode according to the resource management request, managing target upper-layer resources in the target resource management mode under the target tenant through a federal console, and updating the federal tenant snapshot of the target tenant.
Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), system on a chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.
A computer program for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the computer programs, when executed by the processor, cause the functions/acts specified in the flowchart and/or block diagram block or blocks to be performed. A computer program can execute entirely on a machine, partly on a machine, as a stand-alone software package partly on a machine and partly on a remote machine or entirely on a remote machine or server.
In the context of the present invention, a computer-readable storage medium may be a tangible medium that can contain, or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. A computer readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, the computer readable storage medium may be a machine readable signal medium. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, 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.
To provide for interaction with a user, the systems and techniques described here can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the electronic device. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), Wide Area Networks (WANs), blockchain networks, and the internet.
The computing system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical host and VPS service are overcome.
It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present invention may be executed in parallel, sequentially, or in different orders, and are not limited herein as long as the desired results of the technical solution of the present invention can be achieved.
The above-described embodiments should not be construed as limiting the scope of the invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (10)
1. A management platform of a federated tenant is characterized by comprising a federated tenant construction module and a tenant resource management module;
the federated tenant management module is used for constructing federated tenants, the federated tenants comprise at least one member tenant, and each member tenant comprises a main tenant;
and the tenant resource management module is used for managing tenant resources through a federal console and/or a tenant console.
2. The federated tenant management platform of claim 1, wherein the platform further comprises a user identity management module;
the user identity management module is used for carrying out user identity verification when a user logs in, when the user logs in through the federal console, the user obtains the authority of a federal administrator, and when the user logs in through the tenant console, the user obtains the authority of member tenants.
3. The management platform of a federated tenant of claim 1, wherein the tenant resource management module comprises a master tenant management unit and a member tenant management unit;
the main tenant management unit is used for managing upper-layer resources of each member tenant through the federal console;
and the member tenant management unit is used for managing the tenant resources of each member tenant through the tenant console.
4. The federated tenant management platform of claim 1, further comprising a tenant snapshot management module;
the tenant snapshot management module is used for managing the federal tenant snapshot of the federal tenant, and the federal tenant snapshot is formed by the main tenant according to the upper-layer resource information of each member tenant.
5. The federal tenant management platform of claim 1, wherein the federal tenant management module is further configured to:
and receiving a quit request of the member tenant, and removing the member tenant from the federated tenant according to the quit request.
6. A resource management method of a federated tenant is applied to a main tenant in the federated tenant, and is characterized by comprising the following steps:
receiving a resource management request through a federal console;
and determining target tenants and target upper-layer resources in member tenants according to the resource management request, and managing the target upper-layer resources under the target tenants through the federal console.
7. The method for resource management of a federated tenant according to claim 6,
the resource management request comprises a resource deployment request, a resource query request, a resource modification request and/or a resource deletion request.
8. The method for resource management by a federated tenant of claim 7, wherein the method further comprises:
and receiving upper-layer resource information sent by the member tenant, forming a federal tenant snapshot of the federal tenant according to the upper-layer resource information, and displaying the federal tenant snapshot through the federal console.
9. The method for resource management of a federal tenant according to claim 8, wherein the managing target upper resources of the target tenant via the federal console comprises:
when the resource management request is the resource deployment request;
and acquiring the federal tenant snapshot, adding resource information of the target upper-layer resource in the federal tenant snapshot according to the resource deployment request, and deploying the target upper-layer resource under the target tenant through the federal console.
10. The method for resource management of a federal tenant according to claim 8, wherein the managing target upper resources of the target tenant via the federal console comprises:
when the resource management request is the resource query request, the resource modification request or the resource deletion request;
and determining a target resource management mode according to the resource management request, managing the target upper-layer resources in the target resource management mode under the target tenant through the federal console, and updating the snapshot of the federal tenant.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210399719.1A CN114827275B (en) | 2022-04-15 | 2022-04-15 | Management platform of federal tenant and resource management method of federal tenant |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210399719.1A CN114827275B (en) | 2022-04-15 | 2022-04-15 | Management platform of federal tenant and resource management method of federal tenant |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114827275A true CN114827275A (en) | 2022-07-29 |
| CN114827275B CN114827275B (en) | 2024-03-22 |
Family
ID=82537147
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210399719.1A Active CN114827275B (en) | 2022-04-15 | 2022-04-15 | Management platform of federal tenant and resource management method of federal tenant |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114827275B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100211548A1 (en) * | 2009-02-17 | 2010-08-19 | Microsoft Corporation | Tenant management of a hosted multi-tenant application |
| CN109117650A (en) * | 2018-07-25 | 2019-01-01 | 华为技术有限公司 | A kind of creation method of enterprise's cloud and management platform |
| CN109784090A (en) * | 2018-12-27 | 2019-05-21 | 浪潮软件股份有限公司 | A kind of method and system for realizing multi-tenant control based on cloud messaging service |
| CN109889595A (en) * | 2019-02-26 | 2019-06-14 | 中电科软件信息服务有限公司 | High Availabitity cloud infrastructure management system based on multi-tenant |
| CN111404757A (en) * | 2020-03-26 | 2020-07-10 | 成都云巢智联科技有限公司 | Cloud-based cross-network application integration system |
| CN112925647A (en) * | 2021-03-24 | 2021-06-08 | 北京金山云网络技术有限公司 | Cloud edge coordination system, and control method and device of cluster resources |
-
2022
- 2022-04-15 CN CN202210399719.1A patent/CN114827275B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100211548A1 (en) * | 2009-02-17 | 2010-08-19 | Microsoft Corporation | Tenant management of a hosted multi-tenant application |
| CN109117650A (en) * | 2018-07-25 | 2019-01-01 | 华为技术有限公司 | A kind of creation method of enterprise's cloud and management platform |
| CN109784090A (en) * | 2018-12-27 | 2019-05-21 | 浪潮软件股份有限公司 | A kind of method and system for realizing multi-tenant control based on cloud messaging service |
| CN109889595A (en) * | 2019-02-26 | 2019-06-14 | 中电科软件信息服务有限公司 | High Availabitity cloud infrastructure management system based on multi-tenant |
| CN111404757A (en) * | 2020-03-26 | 2020-07-10 | 成都云巢智联科技有限公司 | Cloud-based cross-network application integration system |
| CN112925647A (en) * | 2021-03-24 | 2021-06-08 | 北京金山云网络技术有限公司 | Cloud edge coordination system, and control method and device of cluster resources |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114827275B (en) | 2024-03-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11140176B2 (en) | Distributed topology enabler for identity manager | |
| TWI473029B (en) | Extensible and programmable multi-tenant service architecture | |
| US10810316B2 (en) | Updating monitoring systems using merged data policies | |
| US9244951B2 (en) | Managing tenant-specific data sets in a multi-tenant environment | |
| US20210328864A1 (en) | Generating configuration files for configuring an information technology infrastructure | |
| US10656972B2 (en) | Managing idempotent operations while interacting with a system of record | |
| US20140108639A1 (en) | Transparently enforcing policies in hadoop-style processing infrastructures | |
| CN108132775B (en) | Tenant management system and method | |
| US20180165299A1 (en) | Data transformation for object storage | |
| CN109408523B (en) | Data sharing method and device, data sharing platform and electronic equipment | |
| US20120304262A1 (en) | Automating cloud service reconnections | |
| US11165660B2 (en) | Dynamically grouping monitored resources in a cloud environment to collections representing a composite application | |
| US10558373B1 (en) | Scalable index store | |
| CN112015696A (en) | Data access method, data relationship setting method, data access device, data relationship setting device and storage medium | |
| US11093477B1 (en) | Multiple source database system consolidation | |
| US11176013B2 (en) | Method to efficiently and reliably process ordered user account events in a cluster | |
| US20230306026A1 (en) | Database query performance improvement | |
| CN114827275B (en) | Management platform of federal tenant and resource management method of federal tenant | |
| US11853286B2 (en) | Dynamic deployment of multiple database systems with data reduction | |
| US11157454B2 (en) | Event-based synchronization in a file sharing environment | |
| US10884621B2 (en) | Block volume mount synchronization to prevent data corruption | |
| CN115485677A (en) | Secure data replication in a distributed data storage environment | |
| Hu et al. | A cloud oriented account service mechanism for SME SaaS ecosystem | |
| Darcy et al. | BUILDING A CLOUD FILESYSTEM | |
| US11599432B2 (en) | Distributed application orchestration management in a heterogeneous distributed computing environment |
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 |