CN117978802A

CN117978802A - Cloud resource management system and deployment method thereof

Info

Publication number: CN117978802A
Application number: CN202310402195.1A
Authority: CN
Inventors: 江涛; 温嘉佳
Original assignee: Huawei Cloud Computing Technologies Co Ltd
Current assignee: Huawei Cloud Computing Technologies Co Ltd
Priority date: 2022-10-24
Filing date: 2023-04-14
Publication date: 2024-05-03

Abstract

The application discloses a cloud resource management system and a deployment method thereof. The on-cloud resource management system comprises: the cloud resource management system comprises a cloud resource management node, a bottom management component and an external resource management component, wherein: the cloud resource management node is used for deploying a bottom layer management component, the bottom layer management component is used for managing an internal resource cluster, and an external resource management component is deployed based on the internal resource cluster; the external resource management component is used for managing the external resource cluster, the external resource management component comprises a basic management component, the basic management component is used for managing a basic resource group in the external resource cluster, a virtual instance is created based on the basic resource group, and services of tenants are deployed in the virtual instance. The basic management component only manages the basic resource groups in the external resource clusters, effectively controls the residual resource groups occupied by the basic management component, and is beneficial to reducing the construction cost of the resource management system on the cloud.

Description

Cloud resource management system and deployment method thereof

The present application claims priority from chinese patent application No. 202211300013.1 entitled "resource cluster management system deployment method" filed on 24 months 10, 2022, the entire contents of which are incorporated herein by reference.

Technical Field

The application relates to the technical field of resource management, in particular to a cloud resource management system and a deployment method thereof.

Background

In public clouds or enterprise private clouds, a resource pool is generally divided into two parts, a management area and a tenant area. The management area resource pool and the tenant area resource pool are completely independent from each other, cloud services deployed in any type of resource pool are fixedly deployed in the type of resource pool in the whole life cycle, and the situation that the cloud services are extended to the opposite side area to realize co-deployment or migration deployment does not exist. The virtual instance created in the management area resource pool is used for deploying a resource management system, a basic cloud service, an operation and maintenance service, a security service and the like of the management area resource pool.

At present, cloud services in a management area resource pool are in a virtual instance form and do not have the capability of elastic expansion. In order to cope with performance impact of service peak flow, a large-scale virtual machine is generally selected in a management area resource pool, and a large-scale service cluster is deployed.

However, the service peak flow is usually very short, which causes a great amount of resource waste in the resource pool of the management area, resulting in higher construction cost of the resource management system.

Disclosure of Invention

The application provides a cloud resource management system and a deployment method thereof. The basic management component only manages the basic resource group in the external resource cluster, effectively controls the resources occupied by the basic management component, and is beneficial to reducing the construction cost of the resource management system on the cloud. The technical scheme provided by the application is as follows:

In a first aspect, the present application provides a cloud resource management system, including: the cloud resource management system comprises a cloud resource management node, a bottom management component and an external resource management component, wherein: the cloud resource management node is used for deploying a bottom layer management component, the bottom layer management component is used for managing an internal resource cluster, and an external resource management component is deployed based on the internal resource cluster; the external resource management component is used for managing the external resource cluster, and comprises a basic management component, wherein the basic management component is used for managing a basic resource group in the external resource cluster, creating a virtual instance based on the basic resource group, and deploying the service of the tenant in the virtual instance.

In the on-cloud resource management system, the base management component only manages the base resource group in the external resource cluster, not all the resources of the external resource cluster. On the one hand, the method controls the resource quantity of the external resource cluster managed by the base management component, effectively controls the resources occupied by the base management component, reduces the probability that the scale of the base management component increases in a linkage way along with the increase of the scale of the external resource cluster, and is beneficial to reducing the construction cost of the resource management system on the cloud. On the other hand, the foundation management component is used for carrying out nano-tube on partial resources in the external resource cluster, and provides conditions for the foundation management component to expand the whole control surface of the on-cloud resource management system based on the external resource cluster, so that the on-cloud resource management system has the capability of controlling the resource pool of the ultra-large-scale infrastructure.

In one implementation, the external resource management component further comprises an extension management component. At this time, the basic management component is specifically configured to deploy the extension management component based on the basic resource group. The basic management component provides cloud services to tenants specifically through the extension management component. For example, the extension management component is configured to nanotube an extended resource group in an external resource cluster, create a virtual instance based on the extended resource group, and deploy a tenant's business in the virtual instance.

Optionally, the base management component is further configured to deploy an extension management component based on the base resource group, the extension management component being configured to nanotube the extension resource group in the external resource cluster. The base management component is specifically configured to create a virtual instance based on the remaining resource groups of the base resource groups that are not occupied by the extension management component, and deploy the tenant's business in the virtual instance.

The above process of deploying the extension management component may be regarded as a process of further deploying the external resource management component when there is an increase in traffic. Therefore, the basic management component is deployed based on the internal resource clusters, the expansion management component is deployed based on the external resource clusters, resources occupied by the basic management component can be effectively controlled, the scale of the minimum starting unit is limited, when the scale of the external resource clusters needs to be changed according to the traffic, the scale of the minimum starting unit does not need to be increased in a linkage manner along with the increase of the scale of the external resource clusters, the characteristics of stability and reliability are achieved, and the construction cost of the resource management system on the cloud is reduced.

In one implementation, the base management component is specifically configured to create a first virtual instance cluster based on the set of base resources, and deploy the extension management component in the first virtual instance cluster.

In another implementation, the base management component is specifically configured to create a first virtual instance cluster based on the base resource group; the underlying management component is further configured to deploy the extension management component in the first virtual instance cluster.

Optionally, the resources used by the deployment of the underlying management component are isolated from external resource clusters and/or isolated from internal resource clusters. When the resources used by the bottom management component are isolated from the external resource clusters and the internal resource clusters, the bottom management component is independent of the internal resource clusters and the external resource clusters, and can be regarded as a completely self-contained service of the resource management nodes on the cloud, the decoupling of the bottom management component from the internal resource clusters and the external resource clusters is realized, the physical isolation of the bottom management component from the internal resource clusters and the external resource clusters is realized, the fault isolation effect can be achieved, the fault diffusion is avoided, and the complete resource management system on the cloud can be rebuilt on the basis of the bottom management component after the fault occurs. In addition, the internal resource clusters and the external resource clusters may also be isolated from each other.

Optionally, in order to further ensure the security of the on-cloud resource management system, an underlying management component may be deployed on a plurality of on-cloud resource management nodes, so that the underlying management component has disaster recovery capability.

In one implementation, the underlying management component is specifically configured to create a second virtual instance cluster based on the internal resource cluster, and to deploy a base management component in the external resource management component in the second virtual instance cluster.

Optionally, the underlying management component may include at least one of an underlying public service and essential middleware. The public service is a service which can be shared by cloud services which can be provided by the cloud resource management system through the external resource cluster. For example, the public service may be a database service. The necessary middleware is middleware which is needed to be used by cloud services which can be provided by a cloud resource management system through an external resource cluster. For example, the necessary middleware may be a cache and a message queue.

Or the underlying management component may not include at least one of the underlying public service and the necessary middleware. In one implementation, the underlying management component is further configured to deploy at least one of the underlying public service and the required middleware based on the internal resource cluster. The implementation process comprises the following steps: the underlying management component creates a third virtual instance cluster based on the internal resource cluster, in which at least one of the underlying public service and the required middleware is deployed.

The second virtual instance cluster and the third virtual instance cluster may be one instance cluster created by the underlying management component based on all the internal resource clusters at one time, or may be an instance cluster created by the underlying management component multiple times and based on a part of the resources in the internal resource clusters each time, which is not particularly limited by the present application.

The subsystem comprising the underlying management component and the underlying management component may be considered the most underlying management subsystem in the on-cloud resource management system. The most basic management subsystem is in a form of maintaining the minimum scale of the normal running state of the resource management system on the cloud under the condition of minimum tenant traffic. Thus, this most basic management subsystem is also referred to as the minimum startup unit of the resource management system on the cloud. The minimum starting unit comprises a computing and storage root service which is completely self-contained at the bottom layer, an internal resource cluster managed by the root service, a basic public service and necessary middleware which are issued on the basis of the internal resource cluster, and a basic management component which is provided with a specific-scale external resource cluster. The minimum starting unit can be seen to exist independently relative to the external resource cluster, complete decoupling with the external resource cluster is achieved, and the effect of fault isolation with the external resource cluster is achieved. Moreover, the scale of the minimum starting unit is controlled, the minimum starting unit cannot synchronously increase along with the increase of the capacity of the external resource cluster, and the cost of the resource management system on the cloud is effectively controlled. The minimum starting unit is equivalent to a basic input/output system of a computer, is the firmest and reliable fort of the resource management system on the whole cloud, can finish the guidance and initialization of the resource management system on the whole cloud with minimum cost, can expand the complete resource management system on the cloud based on the minimum starting unit, and can gradually reconstruct the complete resource management system on the cloud based on the minimum starting unit after serious disaster occurs.

Alternatively, the external resource management component may include a plurality of extension management components, any two of which may be isolated from each other, and/or the base management component may be isolated from any one of the extension management components. For example, the external resource management component may adopt a gridding architecture, that is, the entire external management component adopts a multi-service grid form, and the basic management component and each expansion management component are each an independent service grid. When any two expansion management components are isolated from each other, fault propagation between the expansion management components can be avoided, and reliability of the expansion management components is guaranteed. Similarly, when the basic management component and the expansion management component are isolated from each other, fault propagation between the expansion management component and the basic management component can be avoided, and reliability of the expansion management component and the basic management component is ensured.

In one implementation, the virtual instance is a container or virtual machine.

In a second aspect, the present application provides a deployment method of an on-cloud resource management system, where the method is applied to the on-cloud resource management system, and the on-cloud resource management system includes an on-cloud resource management node, a bottom management component and an external resource management component, and the method includes: the cloud resource management node deploys a bottom management component; the bottom layer management component manages an internal resource cluster, and an external resource management component is deployed based on the internal resource cluster; the external resource management component manages the external resource cluster, wherein the external resource management component comprises a basic management component, the basic management component manages a basic resource group in the external resource cluster, a virtual instance is created based on the basic resource group, and services of tenants are deployed in the virtual instance.

Optionally, the external resource management component further comprises an extension management component, and the method further comprises: the basic management component deploys the expansion management component based on the basic resource group; the expansion management component manages an expansion resource group in the external resource cluster, creates a virtual instance based on the expansion resource group, and deploys services of the tenant in the virtual instance.

Optionally, the external resource management component further comprises an extension management component, and the method further comprises: the basic management component deploys an expansion management component based on the basic resource group, wherein the expansion management component is used for managing the expansion resource group in the external resource cluster; the base management component creates a virtual instance based on the remaining resource groups of the base resource groups that are not occupied by the extension management component, deploying tenant traffic in the virtual instance.

Optionally, the base management component deploys the extension management component based on the base resource group, including: the base management component creates a first virtual instance cluster based on the base resource group, and deploys the extension management component in the first virtual instance cluster.

Optionally, the base management component deploys the extension management component based on the base resource group, including: the base management component creates a first virtual instance cluster based on the base resource group; the underlying management component deploys the extension management component in the first virtual instance cluster.

Optionally, the resources used by the deployment of the underlying management component are isolated from external resource clusters and/or isolated from internal resource clusters.

Optionally, the underlying management component has disaster recovery capabilities.

Optionally, the underlying management component deploys a base management component of the external resource management component based on the internal resource cluster, including: the underlying management component creates a second virtual instance cluster based on the internal resource cluster, and deploys the external resource management component within the second virtual instance cluster.

Optionally, the underlying management component includes at least one of an underlying public service and essential middleware.

Optionally, the method further comprises: the underlying management component deploys at least one of the underlying public service and the required middleware based on the internal resource clusters.

Optionally, the underlying management component deploys at least one of the underlying public service and the middleware based on the internal resource cluster, including: the underlying management component creates a third virtual instance cluster based on the internal resource cluster, in which at least one of the underlying public service and the required middleware is deployed.

Optionally, the external resource management component includes a plurality of extension management components, any two of which are isolated from each other, and/or the base management component is isolated from any one of the extension management components.

Optionally, the virtual instance is a container or a virtual machine.

In a third aspect, the application provides a computing device comprising a memory storing program instructions and a processor executing the program instructions to perform the method provided in the second aspect of the application and any one of its possible implementations.

In a fourth aspect, the present application provides a cluster of computing devices comprising a plurality of processors and a plurality of memories, the plurality of memories having stored therein program instructions that are executable by the plurality of processors to cause the cluster of computing devices to perform the method provided in the second aspect of the present application and any of its possible implementations.

In a fifth aspect, the application provides a computer readable storage medium, the computer readable storage medium being a non-volatile computer readable storage medium comprising program instructions which, when run on a computing device, cause the computing device to perform the method provided in the second aspect of the application and any one of its possible implementations.

In a sixth aspect, the application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method provided in the second aspect of the application and any one of its possible implementations.

Drawings

Fig. 1 is a schematic structural diagram of an implementation environment related to a deployment method of an on-cloud resource management system according to an embodiment of the present application;

FIG. 2 is a schematic diagram of a deployment process of an on-cloud resource management system according to an embodiment of the present application;

FIG. 3 is a flowchart of a deployment method of an on-cloud resource management system according to an embodiment of the present application;

FIG. 4 is a schematic diagram of a deployment of an underlying management component provided by an embodiment of the present application;

FIG. 5 is a schematic diagram of an underlying management component nanotube internal resource cluster according to an embodiment of the present application;

FIG. 6 is a schematic diagram of a deployment of underlying management components, underlying public services, and essential middleware provided by an embodiment of the present application;

FIG. 7 is a schematic diagram of a basic management component nanotube basic resource set according to an embodiment of the present application;

FIG. 8 is a flowchart of another method for deploying a resource management system on a cloud provided by an embodiment of the present application;

FIG. 9 is a schematic diagram of an extended K8s cluster according to an embodiment of the present application;

FIG. 10 is a schematic diagram of an expansion management component nanotube expansion resource group according to an embodiment of the present application;

FIG. 11 is a flowchart of a deployment method of a resource management system on a cloud according to an embodiment of the present application;

fig. 12 is a schematic structural diagram of a computing device according to an embodiment of the present application.

Detailed Description

For the purpose of making the objects, technical solutions and advantages of the present application more apparent, the embodiments of the present application will be described in further detail with reference to the accompanying drawings.

For ease of understanding, the techniques and background referred to in the embodiments of the present application are explained first.

Virtualization (virtualization) is a resource management technology, which abstracts and converts various physical resources of a host, such as computing resources, network resources, and storage resources, and presents the resources, so as to break through the unclassifiable barrier between the physical structures of the host, and enable users to apply the resources in a better manner than the original configuration. The resources used by virtualization are called virtualized resources, and the virtualized resources are not limited by the erection mode, the setting region or the physical configuration of the existing entity resources.

Host (PHYSICAL MACHINE, PM): physical resources for carrying virtualization technology. The host is also called a physical machine. Typically, the host used to deploy the virtual instance is a physical server. The physical machine has a plurality of physical devices. For example, a physical server has physical devices such as a processor and memory. Multiple virtual instances can be deployed in one host, and multiple virtual instances deployed on the same host share physical resources of the host. According to different use cases, one host can only deploy virtual instances belonging to one user, and can also deploy virtual instances belonging to a plurality of users.

A resource pool is a collection of various hardware and software resources involved in a cloud computing data center. Generally, the resources in the resource pool can be divided into computing resources, storage resources, and network resources by the type of resource.

The virtual instance runs on an operating system of the host, the virtual instance is provided with the operating system, and the operating system of the virtual instance runs with an application program which is used for realizing the service of the user. The virtual instances may use the hardware resources of the host, with the different virtual instances being isolated from each other. In general, a virtual instance may be a virtual machine or container.

Virtual Machine (VM): refers to a complete computer system which is obtained through simulation by a virtualization technology and has complete hardware system functions and operates in a completely isolated environment. Some subset of the instructions of the virtual machine may be processed in a host (host) machine, and other portions of the instructions may be executed in an emulated manner. Virtual machines are also known as virtual servers.

A virtual machine may be considered a collection of several virtual devices that are complete computer systems with complete hardware system functionality and that operate in a completely isolated environment. The virtual device is obtained virtually on the basis of a physical device capable of being shared with a resource by a virtualization-based technique. For example, a virtual processor that is virtually derived on a processor basis is a virtual device based on virtualization technology. For another example, based on virtualization technology, a training card that is virtually obtained on the basis of a field-programmable gate array (FPGA) is also a virtual device.

The container provides a lightweight virtual execution environment. The container may be obtained by packaging all code, libraries, dependencies, etc. of the user's application into a mirror image. When the mirror image is executed, the mirror image runs in a virtual running environment. The container is now a mirrored runtime instance, similar to a lightweight sandbox, which can be started, stopped, and deleted. The mirror image does not share the memory, processor (such as central processing unit (central processing unit, CPU)) and disk of the host machine with other mirror images, so that the isolation of the container between the mirror image and the host machine and between the mirror image and other mirror images is realized, and the process in the container can not monitor any process or resource outside the container.

Container techniques include docker, kubernetes, coreos and other container techniques. The following will take kubernetes container technology as an example.

Kubernetes is a container orchestration engine of Google (Google) open source that supports automated deployment, large scale scalability, application containerization management. At kubernetes, multiple containers can be created, running one application instance within each container. When an application is deployed in a production environment, multiple application instances of the application can be deployed, and then managed, discovered and accessed through a built-in load balancing policy, without requiring complex manual configuration and processing by operation staff for implementation of these details. The component that manages containers using kubernetes container technology may be referred to as a kubernetes management component (K8S management component for short). The container implemented by kubernetes container technology may be referred to as kubernetes container (K8S container for short).

The embodiment of the application provides a cloud resource management system and a deployment method thereof. In the deployment method of the resource management system on the cloud, a bottom management component is deployed by a resource management node on the cloud of the resource management system on the cloud, then the bottom management component manages an internal resource cluster, an external resource management component is deployed based on the internal resource cluster, the external resource management component manages an external resource cluster, the external resource management component comprises a basic management component, the basic management component manages a basic resource group in the external resource cluster, and services of tenants are deployed based on the basic resource group.

In the on-cloud resource management system and the deployment method thereof, the basic management component only manages basic resource groups in the external resource cluster, but not all resources of the external resource cluster. On the one hand, the method controls the resource quantity of the external resource cluster managed by the base management component, effectively controls the resources occupied by the base management component, reduces the probability that the scale of the base management component increases in a linkage way along with the increase of the scale of the external resource cluster, and is beneficial to reducing the construction cost of the resource management system on the cloud. On the other hand, the foundation management component is used for carrying out nano-tube on partial resources in the external resource cluster, and provides conditions for the foundation management component to expand the whole control surface of the on-cloud resource management system based on the external resource cluster, so that the on-cloud resource management system has the capability of controlling the resource pool of the ultra-large-scale infrastructure.

Fig. 1 is a schematic structural diagram of an implementation environment related to a deployment method of a resource management system on a cloud according to an embodiment of the present application. As shown in fig. 1, the implementation environment includes: client 01, on-cloud resource management node 02, internal resource cluster 03, and external resource cluster 04. Communication connection can be established between the client 01 and the on-cloud resource management node 02, between the on-cloud resource management node 02 and the internal resource cluster 03, between the on-cloud resource management node 02 and the external resource cluster 04, and between the internal resource cluster 03 and the external resource cluster 04. For example, a communication connection may be established between the client 01 and the resource management node 02 on the cloud via a network. Alternatively, the network may be a local area network, or may be the internet, or may be another network, which is not limited by the embodiment of the present application.

In this implementation environment, an operator of the on-cloud resource management system may interact with the on-cloud resource management node 02 through the client 01. For example, the operator may send, through the client 01, an indication to the on-cloud resource management node 02 to deploy the on-cloud resource management system, so as to instruct the on-cloud resource management node 02 to deploy the on-cloud resource management system based on the resources of the on-cloud resource management node 02, the internal resource cluster 03, and the external resource cluster 04. The cloud resource management system is used for managing the resources of the external resource cluster 04 and providing cloud services for tenants based on the resources of the external resource cluster 04. As shown in fig. 2, after receiving the indication, the on-cloud resource management node 02 can execute the deployment method of the on-cloud resource management system provided by the embodiment of the present application based on the resources of the on-cloud resource management node 02, the internal resource cluster 03 and the external resource cluster 04. For example, the on-cloud resource management node 02 may deploy an underlying management component based on the resources of the on-cloud resource management node 02, and control the underlying management component to receive an internal resource cluster 03, create a container cluster management system (Kubernetes, abbreviated as K8 s) cluster based on the internal resource cluster 03, and deploy at least one of a basic public service and a necessary middleware in the K8s cluster, and deploy an external resource management component, then receive the external resource cluster 04 through the external management component, and provide cloud services for tenants based on the external resource cluster 04.

Optionally, the client 01 may be a computer, a personal computer, a laptop computer, a mobile phone, a smart phone, a tablet computer, a cloud host, a portable mobile terminal, a multimedia player, an electronic book reader, a wearable device, an intelligent home appliance, an artificial intelligent device, an intelligent wearable device, an intelligent vehicle-mounted device, or an internet of things device, etc. The resource management node 02 on the cloud can be a cloud server or a cloud physical machine, or a cloud server cluster or a physical machine cluster formed by a plurality of cloud servers, or a cloud computing service center. The internal resource cluster 03 and the external resource cluster 04 may be a server cluster composed of several servers, or a cloud computing service center. Among them, a large amount of basic resources owned by cloud service providers are deployed in a cloud computing service center. For example, a cloud computing service center is deployed with computing resources, storage resources, network resources, and the like. The cloud computing service center can realize the deployment method of the on-cloud resource management system provided by the embodiment of the application based on the large amount of basic resources. When the on-cloud resource management node 02, the internal resource cluster 03 and the external resource cluster 04 are implemented through the cloud computing service center, the deployment method for implementing the on-cloud resource management system provided by the embodiment of the application is to actually construct a resource management and control architecture of the cloud computing service center so as to provide cloud services for tenants based on the resource management and control architecture.

It should be noted that, the on-cloud resource management node 02, the internal resource cluster 03, and the external resource cluster 04 in the implementation environment may also be implemented by other resource platforms besides the cloud computing service center, which is not specifically limited by the embodiment of the present application.

It should be understood that the foregoing is an exemplary description of an application scenario of the deployment method of the on-cloud resource management system provided by the embodiment of the present application, and does not constitute a limitation on the application scenario of the deployment method of the on-cloud resource management system, and those skilled in the art can know that, as the service requirement changes, the application scenario can be adjusted according to the application requirement, which is not specifically recited in the embodiment of the present application.

The deployment method of the cloud resource management system provided by the embodiment of the application is described below. As shown in fig. 3, the deployment method of the resource management system on the cloud includes the following steps:

step 301, deploying a bottom management component by a resource management node on the cloud.

In the process of deploying the on-cloud resource management system, the on-cloud resource management node can deploy the bottom management component in the on-cloud resource management node. The bottom management component can be regarded as the basis of the resource management system on the whole cloud, and after the bottom management component is deployed, other components in the resource management system on the cloud can be continuously deployed based on the bottom management component. In one implementation, an implementation of deploying an underlying management component by a resource management node on a cloud includes: the cloud resource management node deploys the bottom layer management component based on the resources of the cloud resource management node. The resource management node on the cloud may be a physical machine or the like. At this time, the deployment of the bottom management component is actually based on storage resources and computing resources of the physical machine.

Wherein resources used by the deployment of the underlying management component may be isolated from external resource clusters and/or isolated from internal resource clusters. The internal resource cluster is used for being used by a management component of the resource management system on the cloud, and the external resource cluster is used for providing cloud services for tenants. The internal resource cluster and the external resource cluster can be a server cluster formed by a plurality of servers or a cloud computing service center. When the resources used by the bottom management component are isolated from the external resource clusters and the internal resource clusters, the bottom management component is independent of the internal resource clusters and the external resource clusters, and can be regarded as a completely self-contained service of the resource management nodes on the cloud, the decoupling of the bottom management component from the internal resource clusters and the external resource clusters is realized, the physical isolation of the bottom management component from the internal resource clusters and the external resource clusters is realized, the fault isolation effect can be achieved, the fault diffusion is avoided, and the complete resource management system on the cloud can be rebuilt on the basis of the bottom management component after the fault occurs. In addition, the internal resource clusters and the external resource clusters may also be isolated from each other.

Optionally, in order to further ensure the security of the on-cloud resource management system, an underlying management component may be deployed on a plurality of on-cloud resource management nodes, so that the underlying management component has disaster recovery capability. For example, the black boxes in FIG. 4 represent physical machines, and the unfilled boxes in FIG. 4 identify clusters of internal resources. As shown in fig. 4, fig. 4 shows 3 physical machines, and the 3 physical machines can deploy an underlying management component based on their own resources, so that the underlying management component has node-level local disaster recovery capability.

It can be seen from the deployment mode of the underlying management component: the deployment of the bottom management component is not dependent on the resources of the resource management nodes on the cloud except the resources of the resource management nodes on the cloud, the bottom management component can be regarded as the service born by the resource management nodes on the cloud, and the external resource management component and the like can be regarded as the higher-layer service deployed based on the bottom management component. Thus, this underlying management component is also referred to as a root service. Because the deployment of the bottom layer management component has no dependence on resources except the resource management nodes on the cloud, and the resource management nodes on the cloud do not belong to an external resource cluster, the root service can be regarded as the computing and storage root service which is completely self-contained at the bottom layer in the resource management system on the cloud. Therefore, when the scale of the external resource cluster needs to be changed according to the traffic, the bottom management component does not need to be increased in a linkage way along with the increase of the scale of the external resource cluster, the method has the characteristics of stability and reliability, and the construction cost of the resource management system on the cloud can be reduced.

Step 302, the bottom management component manages the internal resource clusters.

The bottom management component manages the internal resource clusters by installing an operating system for servers in the internal resource clusters, assigning internet protocol (internet protocol, IP) addresses, installing clients, and the like. After installing an operating system, distributing an IP address, installing a client and the like on a server in the internal resource cluster, the bottom management component can acquire the resource use condition of the server through the client and distribute the resources of the server, so that the nano-tube of the internal resource cluster can be realized. As shown in FIG. 5, the unfilled blocks in FIG. 5 represent servers in the internal resource cluster on which the underlying management component may install operating systems, assign IP addresses, install clients, etc., to implement nanotubes to those servers, i.e., to implement nanotubes to the internal resource cluster.

Step 303, the underlying management component deploys the basic management component of the external resource management component based on the internal resource cluster, or deploys at least one of the basic public service and the necessary middleware based on the internal resource cluster, and deploys the basic management component of the external resource management component.

The external resource management component is used for managing the external resource cluster. The external resource management component includes a base management component and an extension management component. The expansion management component is obtained based on resource deployment of the base management component nanotubes. The underlying management component may be considered as a basis for the outward expansion of the external resource management component, and thus the scope of management of the underlying management component at least needs to cover the resources required to deploy the extended management component. For example, when the external resource management component is composed of a base management component and a primary expansion management component, and the expansion management component is configured to manage all resources in the external resource cluster except for the resources used by the deployment of the expansion management component, the base management component is configured to manage the resources used by the deployment of the expansion management component. The foundation management component can be deployed across the ground, so that the foundation management component has the capability of disaster recovery in different places, and the reliability of the foundation management component is ensured.

Optionally, the underlying management component may include at least one of an underlying public service and essential middleware. Wherein the underlying public service is a service that must be used by the underlying management component to operate. For example, the underlying public service may be a database service. The necessary middleware is middleware that must be used by the underlying management component to operate. For example, the necessary middleware may be a cache and a message queue. At this point, this step 303 is actually that the underlying management component deploys the entire underlying management component based on the internal resource clusters. In one implementation, the implementation includes: the underlying management component creates a second virtual instance cluster based on the internal resource cluster, and deploys the entire underlying management component in the second virtual instance cluster. The virtual instance cluster includes a plurality of virtual instances. In an embodiment of the present application, the virtual instance may be a container or a virtual machine. For example, the second virtual instance cluster may be a K8s cluster, and the basic management component may be software with management functions implemented through a container modality.

Or the underlying management component may not include at least one of the underlying public service and the necessary middleware. At this point, this step 303 is actually that the underlying management component deploys at least one of the basic public service and the necessary middleware based on the internal resource cluster, and then deploys the basic management component on the basis of the at least one of the basic public service and the necessary middleware. The deployment of the underlying management component is implemented as described in the previous paragraph. The bottom management component deploys at least one of basic public service and necessary middleware based on the internal resource cluster, and the implementation process comprises the following steps: the underlying management component creates a third virtual instance cluster based on the internal resource cluster, in which at least one of the underlying public service and the required middleware is deployed. By way of example, the third virtual instance cluster may be a K8s cluster and the underlying public service and the necessary middleware may be software with related functionality implemented by means of container modalities. As shown in FIG. 6, the underlying management component may create a K8s cluster based on the internal resource cluster and deploy basic common services, necessary middleware, and basic management components, respectively, in the K8s cluster. The second virtual instance cluster and the third virtual instance cluster may be one instance cluster created by the underlying management component based on all the internal resource clusters at one time, or may be an instance cluster created by the underlying management component multiple times based on a part of the resources in the internal resource clusters each time, which is not specifically limited in the embodiment of the present application.

When the underlying management component does not include the underlying public service and the requisite middleware, the underlying management component is deployed by first deploying the underlying public service and the requisite middleware based on the internal resource cluster, and then on the basis of the underlying public service and the requisite middleware. Therefore, sharing of the public capacity of the cross-cloud service is realized to the maximum extent, the realization cost of the basic management component is reduced, and the deployment complexity of the basic management component is simplified. The deployment implementation embodies the principles of service-based development services (service on service). The principle of developing services based on services refers to that on the premise of layering, stabilizing and sustainable supplying the bottom cloud services, the upper layer services are deployed based on the bottom cloud services.

After step 303 is performed, deployment of the most basic management subsystem in the on-cloud resource management system is completed. The most basic management subsystem is in a form of maintaining the minimum scale of the normal running state of the resource management system on the cloud under the condition of minimum tenant traffic. Thus, this most basic management subsystem is also referred to as the minimum startup unit (minimum starting unit, MSU) of the resource management system on the cloud. The range of the minimum start-up unit is illustrated in fig. 6, for example. The minimum starting unit comprises a computing and storage root service which is completely self-contained at the bottom layer, an internal resource cluster managed by the root service, a basic public service and necessary middleware which are issued on the basis of the internal resource cluster, and a basic management component which is provided with a specific-scale external resource cluster. The minimum starting unit can be seen to exist independently relative to the external resource cluster, complete decoupling with the external resource cluster is achieved, and the effect of fault isolation with the external resource cluster is achieved. Moreover, the scale of the minimum starting unit is controlled, the minimum starting unit cannot synchronously increase along with the increase of the capacity of the external resource cluster, and the cost of the resource management system on the cloud is effectively controlled. The minimum starting unit is equivalent to a basic input output system (basic input output system, BIOS) of a computer, is the firmest and reliable fort of the resource management system on the whole cloud, can finish the guidance and initialization of the resource management system on the whole cloud with minimum cost, can expand the complete resource management system on the cloud based on the minimum starting unit, and can gradually reconstruct the complete resource management system on the cloud based on the minimum starting unit after serious disaster occurs.

Step 304, the basic management component manages the basic resource group in the external resource cluster.

The basic management component manages the basic resource group in the external resource cluster, and can be implemented by installing an operating system, distributing an IP address, installing a client and the like for a server providing the basic resource group. After the operating system is installed, the IP address is allocated, the client is installed and the like on the server for providing the basic resource group, the basic management component can acquire the resource use condition of the server through the client and allocate the resources of the server, so that the nano-tube of the basic resource group can be realized. As shown in fig. 7, the host unit 1 in fig. 7 provides a basic resource group in an external resource cluster, the host unit 1 includes a plurality of servers, and the basic management component may install an operating system, allocate an IP address, install a client, and the like on each server in the host unit 1 to implement a nanotube for the basic resource group.

Step 305, the basic management component provides cloud services to the tenant based on the basic resource group.

There are various implementations of the basic management component providing cloud services to tenants based on the basic resource groups. The implementation of this step 305 is described below taking an implementation in which the base management component directly and indirectly provides cloud services to tenants based on the base resource group as an example.

In a first implementation of step 305, the underlying management component indirectly provides cloud services to the tenant based on the underlying resource group. As shown in fig. 8, the implementation process includes:

step 305a1, the basic management component deploys an extension management component of the external resource management component based on the basic resource group.

As can be seen from the foregoing description, the basic management component of the external resource management component belongs to the minimum starting unit of the on-cloud resource management system, and the minimum starting unit is the form of the minimum scale of the on-cloud resource management system that maintains the normal running state. When the service volume of the tenant increases, the scale of the resources managed by the resource management system on the cloud needs to increase, for example, the scale of the external resource cluster is increased, and the scale of the resource management system on the cloud needs to correspondingly increase. At this time, the base management component may deploy the extension management component based on the base resource group, so as to manage the added resources based on the extension management component. The process of deploying an extension management component may be considered as a process of extending the scale of an external resource management component when there is an increase in traffic. Therefore, the basic management component is deployed based on the internal resource clusters, the expansion management component is deployed based on the external resource clusters, resources occupied by the basic management component can be effectively controlled, the scale of the minimum starting unit is limited, when the scale of the external resource clusters needs to be changed according to the traffic, the scale of the minimum starting unit does not need to be increased in a linkage manner along with the increase of the scale of the external resource clusters, the characteristics of stability and reliability are achieved, and the construction cost of the resource management system on the cloud is reduced.

Alternatively, the implementation of step 305a1 may be varied, and the following two implementations are taken as examples.

In a first implementation of deploying an extension management component, a base management component deploys the extension management component based on a base resource group, including: the base management component creates a first virtual instance cluster based on the base resource group, and deploys the extension management component in the first virtual instance cluster. For example, the first virtual instance cluster may be a container cluster management system K8s cluster, and the extension management component may be software with a management function implemented through a container form.

In a second implementation of deploying an extension management component, the base management component deploys the extension management component based on the base resource group, including: the base management component creates a first virtual instance cluster based on the base resource group, and the underlying management component deploys the extension management component in the first virtual instance cluster. In this implementation, the first virtual instance cluster may be a container cluster management system K8s cluster, and the extension management component may be software with a management function implemented through a container form.

In this second implementation, the base management component may be considered as providing the capability to virtual out a virtual instance cluster based on resources, and after the base management component creates a first virtual instance cluster, the first virtual instance cluster is scheduled by the underlying management component, and the extension management component is deployed based on the first virtual instance cluster. After the base management component creates the first virtual instance cluster, the base management component may provide relevant information of the first virtual instance cluster to the underlying management component, so that the underlying management component may schedule the first virtual instance cluster based on the relevant information. Before the underlying management component schedules the first virtual instance cluster, the underlying management component may merge the first virtual instance cluster with the second virtual instance cluster into one virtual instance cluster and then schedule the expanded virtual instance cluster. The process of merging the first virtual instance cluster with the second virtual instance cluster may be considered as adding the first virtual instance cluster based on the second virtual instance cluster, and expanding the second virtual instance cluster into a logically large cluster spanning the internal resource cluster and the external resource cluster. For example, as shown in FIG. 9, when both the first virtual instance cluster and the second virtual instance cluster are K8s clusters, the K8s clusters created based on the set of base resources may be merged with the K8s clusters created based on the internal resource clusters using Virtual Kublet techniques to extend the K8s clusters created based on the internal resource clusters into a logically large cluster spanning the internal resource clusters and the external resource clusters. When the second virtual instance cluster and the third virtual instance cluster are different clusters, the bottom management component merges the first virtual instance cluster, the second virtual instance cluster and the third virtual instance cluster, and the merged implementation process refers to the merged implementation process of the first virtual instance cluster and the second virtual instance cluster correspondingly. Further, to ensure isolation between the first virtual instance cluster and the second virtual instance cluster, the internal resource cluster and the external resource cluster may be isolated from each other, and a relatively independent resource cluster management technique may be used.

Alternatively, the external resource management component may include a plurality of extension management components, any two of which may be isolated from each other, and/or the base management component may be isolated from any one of the extension management components. For example, the external resource management component may adopt a grid (grid) architecture, that is, the entire external management component adopts a multi-service grid form, and the basic management component and each expansion management component are each an independent service grid. When any two expansion management components are isolated from each other, fault propagation between the expansion management components can be avoided, and reliability of the expansion management components is guaranteed. Similarly, when the basic management component and the expansion management component are isolated from each other, fault propagation between the expansion management component and the basic management component can be avoided, and reliability of the expansion management component and the basic management component is ensured.

Step 305a2, the expansion management component manages the expansion resource group in the external resource cluster, creates a virtual instance based on the expansion resource group, and deploys the service of the tenant in the virtual instance.

After the deployment of the expansion management component is completed, the expansion management component can perform nano-tube on the expansion resource group by installing an operating system, distributing an IP address, installing a client and the like for a server in the expansion resource group. For example, as shown in fig. 10, the host groups 2,3, 4, etc. in fig. 10 provide extended resource groups in an external resource cluster, where each host group includes a plurality of servers, and the extended management component may install an operating system, allocate an IP address, install a client, etc. on each of these host groups to implement a nanotube for the extended resource group. After the expansion management component manages the expansion resource group, when cloud service is required to be provided for the tenant, a virtual instance can be created based on the expansion resource group, and the service of the tenant can be deployed in the virtual instance so as to provide cloud service for the tenant.

In a second implementation of step 305, the underlying management component provides cloud services directly to the tenant based on the underlying resource group. The implementation process comprises the following steps: the base management component creates a virtual instance based on the base resource group, deploying tenant's business in the virtual instance. For example, after the base management component receives the base resource group, when cloud services need to be provided for the tenant, the base management component can create a virtual instance based on the base resource group and deploy the tenant's business in the virtual instance to provide cloud services to the tenant.

Optionally, in addition to deploying tenant traffic based on the base resource group, the base management component may deploy an extension management component based on the base resource group. The expansion management component is used for carrying out nano-tube on the expansion resource group in the external resource cluster, creating a virtual instance based on the expansion resource group and deploying the service of the tenant in the virtual instance. The implementation manner of deploying the expansion management component, the implementation manner of deploying the tenant service by the expansion management component, may refer to the related content correspondingly, which is not described herein.

In one implementation, since the extension management component is configured to nanotube an extension resource group in an external resource cluster and provide cloud services for tenants based thereon, to ensure that the extension resource group can be effectively utilized, the extension management component may have priority to use the base resource group over virtual instances for deploying tenants. That is, the extension management component can be deployed by preferentially using the base resource group in the base management component, and when the service of the tenant needs to be deployed, a virtual instance is created based on the remaining resource groups which are not occupied by the extension management component in the base resource group, and the service of the tenant is deployed in the virtual instance. For example, as shown in fig. 11, before the base management component creates a virtual instance based on the base resource group, and deploys the tenant's business in the virtual instance, the method further includes:

Step 305b1, the basic management component deploys the extension management component based on the basic resource group.

The implementation process of the step 305b1 is referred to as the implementation process of the step 305a1, and will not be described herein.

At this time, as shown in fig. 11, the basic management component creates a virtual instance based on the basic resource group, and deploys the tenant's service in the virtual instance, including: step 305b2, the basic management component creates a virtual instance based on the remaining resource groups in the basic resource groups that are not occupied by the extended management component, and deploys the tenant's service in the virtual instance.

From the above, it can be seen that the minimum startup unit is configured to provide a starting specification of various services (including a basic management component, a basic public service and a necessary middleware) deployed therein, so as to meet a resource requirement of a normal service load, and in a service peak period, an expansion management component needs to be deployed in an external resource cluster, so as to increase a service processing capability of the resource cluster. Therefore, after the traffic peak passes, the resources occupied by the traffic peak in the external resource pool can be released in time, including releasing the resources used for deploying the corresponding traffic and the resources occupied by the expansion management component, so that the elastic expansion and contraction of the resources are realized, and the cost occupation of the resource management system on the cloud is optimized.

In summary, in the deployment method of the on-cloud resource management system provided by the embodiment of the application, firstly, a bottom management component which is completely independent of the outside in the minimum starting unit is constructed, the bottom management component is utilized to receive the internal resource cluster, then, the basic management component, the basic public service and the necessary middleware of the external resource management component are deployed based on the internal resource cluster, then, the expansion management component of the external resource management component is constructed, and further, the management control surface of the on-cloud resource management system is expanded and deployed from the minimum starting unit to the external resource cluster. The method for constructing the resource management system on the cloud by means of bootstrapping and partial sequence dependence not only can ensure that the scale of an internal resource pool of a minimum starting unit is limited, but also is beneficial to improving the utilization rate of the whole resource, and effectively reduces the construction cost of the resource management system on the cloud. In addition, the method for realizing the deployment of the resource management system on the whole cloud on the basis of the minimum starting unit not only ensures that the resource management system on the cloud has the capacity of controlling the resource pool of the ultra-large-scale infrastructure, but also realizes the isolation of the minimum starting unit and the external resource cluster on the basis of controlling the cost of the resource management system on the cloud, and avoids the fault diffusion between the minimum starting unit and the external resource cluster. In addition, when the cloud resource management system issues virtual instances with the same resource form in the resource management and control process, the minimum starting unit can be ensured to be simple and stable enough, self-contained of the minimum starting unit can be easily realized, and the reliability of the cloud resource management system can be ensured. Meanwhile, deployment resources required by the management component are expanded, most of the deployment resources are expanded in an external resource pool, the resource pool is shared with the tenant, fragmentation of the hardware resource pool is avoided to a large extent, and cost optimization is facilitated.

It should be noted that, the sequence of the steps of the deployment method of the resource management system on the cloud provided by the embodiment of the application can be properly adjusted, and the steps can be correspondingly increased or decreased according to the situation. Any method that can be easily conceived by those skilled in the art within the technical scope of the present disclosure should be covered in the protection scope of the present application, and thus will not be repeated.

The deployment method of the cloud resource management system in the embodiment of the application is introduced, and the cloud resource management system is also provided in the embodiment of the application corresponding to the method. Fig. 7 and fig. 10 are schematic structural diagrams of an on-cloud resource management system according to an embodiment of the present application. It should be understood that the on-cloud resource management system may include additional components than those shown or omit some of the components shown therein, as embodiments of the application are not limited in this respect. Optionally, the on-cloud resource management system may be configured on a cloud platform. As shown in fig. 7, the on-cloud resource management system may include: the cloud resource management system comprises a cloud resource management node, a bottom management component and an external resource management component.

The bottom management component is used for managing the internal resource clusters, and the foundation management component of the external resource management component is deployed based on the internal resource clusters.

The external resource management component is used for managing the external resource cluster, wherein the external resource management component comprises a basic management component, the basic management component is used for managing a basic resource group in the external resource cluster, a virtual instance is created based on the basic resource group, and services of tenants are deployed in the virtual instance.

In one implementation, as shown in fig. 10, the system further includes: an extension management component of the external resource management component. At this time, the basic management component is specifically configured to deploy the extension management component based on the basic resource group. The basic management component provides cloud services to tenants specifically through the extension management component. For example, the extension management component is configured to nanotube an extended resource group in an external resource cluster, create a virtual instance based on the extended resource group, and deploy a tenant's business in the virtual instance.

Or the basic management component is specifically configured to create a virtual instance based on the basic resource group, and deploy services of the tenant in the virtual instance.

Optionally, in this implementation, the base management component is further configured to deploy the extension management component based on the base resource group. The base management component is specifically configured to create a virtual instance based on the remaining resource groups of the base resource groups that are not occupied by the extension management component, and deploy the tenant's business in the virtual instance.

The above process of deploying the extension management component may be regarded as a process of further deploying the external resource management component when there is an increase in traffic. In this way, the basic management component is deployed based on the internal resource clusters, the extension management component is deployed based on the external resource clusters, the residual resource groups occupied by the basic management component can be effectively controlled, the scale of the minimum starting unit is limited, when the scale of the external resource clusters needs to be changed according to the traffic, the scale of the minimum starting unit does not need to be increased in a linkage manner along with the increase of the scale of the external resource clusters, the characteristics of stability and reliability are achieved, and the construction cost of the resource management system on the cloud is reduced.

Optionally, the resources used by the deployment of the underlying management component are isolated from external resource clusters and/or isolated from internal resource clusters. In addition, the internal resource clusters and the external resource clusters may also be isolated from each other.

In one implementation, the underlying management component is specifically configured to create a second virtual instance cluster based on the internal resource cluster, and to deploy the underlying management component of the external resource management component within the second virtual instance cluster.

Or the underlying management component may not include at least one of the underlying public service and the necessary middleware. In one implementation, the underlying management component deploys at least one of the underlying public service and the required middleware based on the internal resource cluster, the implementation comprising: the underlying management component creates a third virtual instance cluster based on the internal resource cluster, in which at least one of the underlying public service and the required middleware is deployed.

Alternatively, the external resource management component may include a plurality of extension management components, any two of which may be isolated from each other, and/or the base management component may be isolated from any one of the extension management components. In one implementation, the virtual instance is a container or virtual machine.

In summary, the on-cloud resource management system provided by the embodiment of the application not only can ensure that the scale of the internal resource pool of the minimum starting unit is limited, but also is beneficial to improving the utilization rate of the whole resource, and effectively reduces the construction cost of the on-cloud resource management system. And the on-cloud resource management system is obtained by deployment on the basis of the minimum starting unit, so that the on-cloud resource management system has the capacity of managing and controlling the ultra-large-scale infrastructure resource pool, and on the basis of controlling the cost of the on-cloud resource management system, the isolation between the minimum starting unit and an external resource cluster is realized, and the fault diffusion between the minimum starting unit and the external resource cluster is avoided. In addition, when the cloud resource management system issues virtual instances with the same resource form in the resource management and control process, the minimum starting unit can be ensured to be simple and stable enough, self-contained of the minimum starting unit can be easily realized, and the reliability of the cloud resource management system can be ensured. Meanwhile, deployment resources required by the management component are expanded, most of the deployment resources are expanded in an external resource pool, the resource pool is shared with the tenant, fragmentation of the hardware resource pool is avoided to a large extent, and cost optimization is facilitated.

It may be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working process of the above-described on-cloud resource management system and each component may refer to the corresponding content in the foregoing method embodiment, which is not described herein again.

Embodiments of the present application provide a computing device. The computing device is used for realizing part or all of functions in the deployment method of the cloud resource management system provided by the embodiment of the application. Fig. 12 is a schematic structural diagram of a computing device according to an embodiment of the present application. As shown in fig. 12, the computing device 1200 includes a processor 1201, a memory 1202, a communication interface 1203, and a bus 1204. Wherein the processor 1201, the memory 1202 and the communication interface 1203 are communicatively coupled to each other via a bus 1204.

The processor 1201 may include a general purpose processor and/or a dedicated hardware chip. The general purpose processor may include: a central processing unit (central processing unit, CPU), a microprocessor, or a graphics processor (graphics processing unit, GPU). The CPU is, for example, a single-core processor (single-CPU), and is, for example, a multi-core processor (multi-CPU). The special-purpose hardware chip is a high-performance processing hardware module. The special purpose hardware chip includes at least one of a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or a network processor (network processer, NP). Processor 1201 may also be an integrated circuit chip with signal processing capabilities. In the implementation process, part or all of the functions of the deployment method of the on-cloud resource management system of the present application may be completed by an integrated logic circuit of hardware in the processor 1201 or an instruction in the form of software.

The memory 1202 is used to store a computer program that includes an operating system 1202a and executable code (i.e., program instructions) 1202b. Memory 1202 is, but is not limited to, a read-only memory or other type of static storage device that can store static information and instructions, a random access memory or other type of dynamic storage device that can store information and instructions, an electrically erasable programmable read-only memory, a read-only optical or other optical storage, an optical storage (including compact discs, laser discs, optical discs, digital versatile discs, blu-ray discs, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired executable code in the form of instructions or data structures and that can be accessed by a computer. Such as memory 1202 for storing port queues and the like. The memory 1202 is, for example, independent and is coupled to the processor 1201 by a bus 1204. Or the memory 1202 and the processor 1201 may be integrated. The memory 1202 may store executable code, and when the executable code stored in the memory 1202 is executed by the processor 1201, the processor 1201 is configured to perform part or all of the functions of the deployment method of the on-cloud resource management system provided by the embodiment of the present application. The implementation of the process performed by the processor 1201 is referred to correspondingly in the description of the previous embodiments. Memory 1202 may also include software modules and data for other operating systems and the like that are required for other processes to run.

The communication interface 1203 uses a transceiver module, such as, but not limited to, a transceiver, to enable communication with other devices or communication networks. For example, the communication interface 1203 may be any one or any combination of the following devices: network interfaces (e.g., ethernet interfaces), wireless network cards, and the like having network access functionality.

Bus 1204 is any type of communication bus used to interconnect the internal devices of a computing device (e.g., memory 1202, processor 1201, communication interface 1203). Such as a system bus. The embodiments of the present application are described with respect to the interconnection of the devices within the computing device via bus 1204, and alternatively, the devices within the computing device 1200 may be communicatively coupled to each other using other connections than bus 1204. For example, the aforementioned devices within computing device 1200 are interconnected by internal logic interfaces.

The plurality of devices may be provided on separate chips, or may be provided at least partially or entirely on the same chip. Whether the individual devices are independently disposed on different chips or integrally disposed on one or more chips is often dependent on the needs of the product design. The embodiment of the application does not limit the specific implementation form of the device. And the descriptions of the processes corresponding to the drawings are focused on, and the descriptions of other processes can be referred to for the parts of a certain process which are not described in detail.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product providing the program development platform includes one or more computer instructions that, when loaded and executed on a computing device, fully or partially implement the functionality of the method for deploying a resource management system on a cloud provided by an embodiment of the application.

Moreover, the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, optical fiber, digital subscriber line), or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer readable storage medium stores computer program instructions that provide a program development platform.

The embodiment of the application also provides a computing device cluster. The cluster of computing devices includes at least one computing device. The computing device may be a server, such as a central server, an edge server, or a local server in a local data center. In some embodiments, the computing device may also be a terminal device such as a desktop, notebook, or smart phone.

Alternatively, the structure of at least one computing device included in the computing device cluster may be referred to as computing device 1200 shown in fig. 12. The same instructions for performing the deployment method of the resource management system on the cloud may be stored in memory 1202 in one or more computing devices 1200 in the cluster of computing devices.

In some possible implementations, the memory 1202 of one or more computing devices 1200 in the computing device cluster may also each have stored therein a portion of instructions for performing a method of deploying a resource management system on the cloud. In other words, a combination of one or more computing devices 1200 may collectively execute instructions for performing a method of deploying a resource management system on a cloud.

It should be noted that, the memory 1202 in different computing devices 1200 in the computing device cluster may store different instructions for performing part of the functions of the resource management system on the cloud, respectively. That is, the instructions stored by the memory 1202 in the different computing devices 1200 may implement the functionality of one or more of the first, second, and third determination modules.

In some possible implementations, multiple computing devices in a cluster of computing devices may be connected through a network. Wherein the network may be a wide area network or a local area network, etc. Any two computing devices are connected by a network. Specifically, the connection to the network is made through a communication interface in each computing device. In one such possible implementation, each computing device includes a bus, a processor, a memory, and a communication interface.

The embodiment of the application also provides a computer readable storage medium which is a nonvolatile computer readable storage medium, and the computer readable storage medium comprises program instructions which, when run on a computing device, cause the computing device to realize the deployment method of the cloud resource management system provided by the embodiment of the application.

The embodiment of the application also provides a computer program product containing instructions, which when run on a computer, cause the computer to realize the deployment method of the cloud resource management system provided by the embodiment of the application.

It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program for instructing relevant hardware, where the program may be stored in a computer readable storage medium, and the storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.

It should be noted that, the information (including but not limited to user equipment information, user personal information, etc.), data (including but not limited to data for analysis, stored data, presented data, etc.), and signals related to the present application are all authorized by the user or are fully authorized by the parties, and the collection, use, and processing of the related data is required to comply with the relevant laws and regulations and standards of the relevant countries and regions. For example, the original data and the executable code and the like involved in the present application are all acquired with sufficient authorization.

In embodiments of the present application, the terms "first," "second," and "third" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. The term "at least one" means one or more, the term "plurality" means two or more, unless expressly defined otherwise.

The term "and/or" in the present application is merely an association relation describing the association object, and indicates that three kinds of relations may exist, for example, a and/or B may indicate: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

The foregoing description of the preferred embodiments of the present application is not intended to limit the application, but is intended to cover any modifications, equivalents, alternatives, and improvements within the spirit and principles of the application.

Claims

1. An on-cloud resource management system, comprising: the cloud resource management system comprises a cloud resource management node, a bottom management component and an external resource management component, wherein:

The resource management node on the cloud is used for deploying the bottom layer management component;

the bottom layer management component is used for managing an internal resource cluster in a nano-tube, and the external resource management component is deployed based on the internal resource cluster;

The external resource management component is used for managing the external resource cluster, wherein the external resource management component comprises a basic management component, the basic management component is used for managing a basic resource group in the external resource cluster, a virtual instance is created based on the basic resource group, and a tenant service is deployed in the virtual instance.

2. The system of claim 1, wherein the external resource management component further comprises an extension management component;

the basic management component is further used for deploying the expansion management component based on the basic resource group;

The expansion management component is used for managing an expansion resource group in the external resource cluster, creating a virtual instance based on the expansion resource group, and deploying the service of the tenant in the virtual instance.

3. The system of claim 1, wherein the external resource management component further comprises an extension management component;

The basic management component is further used for deploying the expansion management component based on the basic resource group, and the expansion management component is used for managing the expansion resource group in the external resource cluster;

The basic management component is further configured to create a virtual instance based on a remaining resource group of the basic resource group that is not occupied by the extension management component, and deploy the service of the tenant in the virtual instance.

4. A system according to claim 2 or 3, wherein,

The base management component is further configured to create a first virtual instance cluster based on the base resource group, and deploy the extension management component in the first virtual instance cluster.

5. A system according to claim 2 or 3, wherein,

The base management component is further configured to create a first virtual instance cluster based on the base resource group;

the underlying management component is further configured to deploy the extension management component in the first virtual instance cluster.

6. The system according to any one of claims 1 to 5, wherein,

The underlying management component is further configured to create a second virtual instance cluster based on the internal resource cluster, and deploy the external resource management component in the second virtual instance cluster.

7. The system of any of claims 1 to 6, wherein the underlying management component comprises at least one of the underlying public service and essential middleware.

8. The system according to any one of claims 1 to 6, further comprising: at least one of the underlying public service and the required middleware;

The underlying management component is further for deploying at least one of the underlying public service and the required middleware based on the internal resource cluster.

9. The system of claim 8, wherein the system further comprises a controller configured to control the controller,

The underlying management component is further configured to create a third virtual instance cluster based on the internal resource cluster, wherein at least one of the underlying public service and the required middleware is deployed in the third virtual instance cluster.

10. The deployment method of the cloud resource management system is characterized by being applied to the cloud resource management system, wherein the cloud resource management system comprises a cloud resource management node, a bottom management component and an external resource management component, and the method comprises the following steps:

the cloud resource management node deploys the bottom management component;

the bottom layer management component manages an internal resource cluster, and deploys the external resource management component based on the internal resource cluster;

The external resource management component manages an external resource cluster, wherein the external resource management component comprises a basic management component, the basic management component manages a basic resource group in the external resource cluster, a virtual instance is created based on the basic resource group, and a tenant service is deployed in the virtual instance.

11. The method of claim 10, wherein the external resource management component further comprises an extension management component, the method further comprising:

The basic management component deploys the expansion management component based on the basic resource group;

The expansion management component receives an expansion resource group in the external resource cluster, creates a virtual instance based on the expansion resource group, and deploys the service of the tenant in the virtual instance.

12. The method of claim 10, wherein the external resource management component further comprises an extension management component, the method further comprising:

The basic management component deploys the expansion management component based on the basic resource group, and the expansion management component is used for managing the expansion resource group in the external resource cluster;

the basic management component creates a virtual instance based on the rest resource groups which are not occupied by the expansion management component in the basic resource groups, and the service of the tenant is deployed in the virtual instance.

13. The method of claim 11 or 12, wherein the base management component deploys the extension management component based on the base resource group, comprising:

The base management component creates a first virtual instance cluster based on the base resource group, and deploys the extension management component in the first virtual instance cluster.

14. The method of claim 11 or 12, wherein the base management component deploys the extension management component based on the base resource group, comprising:

the base management component creates a first virtual instance cluster based on the base resource group;

The underlying management component deploys the extension management component in the first virtual instance cluster.

15. The method of any of claims 10 to 14, wherein the underlying management component deploys the external resource management component based on the internal resource cluster, comprising:

The underlying management component creates a second virtual instance cluster based on the internal resource cluster, and deploys the external resource management component in the second virtual instance cluster.

16. The method of any of claims 10 to 15, wherein the underlying management component comprises at least one of the underlying public service and essential middleware.

17. The method according to any one of claims 10 to 15, further comprising:

the underlying management component deploys at least one of the underlying public service and the required middleware based on the internal resource cluster.

18. The method of claim 17, wherein the underlying management component deploys at least one of the underlying public service and middleware based on the internal resource cluster, comprising:

the underlying management component creates a third virtual instance cluster based on the internal resource cluster, in which at least one of the underlying public service and the required middleware is deployed.

19. A cluster of computing devices comprising a plurality of computing devices, the plurality of computing devices comprising a plurality of processors and a plurality of memories, the plurality of memories having program instructions stored therein, the plurality of processors executing the program instructions to cause the cluster of computing devices to perform the method of any of claims 10 to 18.

20. A computer readable storage medium comprising program instructions which, when run on a computing device, cause the computing device to perform the method of any of claims 10 to 18.

21. A computer program product, characterized in that the computer program product, when run on a computer, causes the computer to perform the method according to any of claims 10 to 18.