







技术领域technical field
本发明涉及云资源管理领域,尤其是涉及一种异构云资源管理调度方法、装置及系统。The present invention relates to the field of cloud resource management, in particular to a method, device and system for managing and scheduling heterogeneous cloud resources.
背景技术Background technique
随着云平台在企业中的应用越来越广泛,企业对于的云平台需求也趋于多样化。在实际的信息化建设场景中,企业遵循国家安全可控体系,正逐步完成应用软件的国产替代目标。因此国产服务器设备与非国产服务器设备并存,是企业目前的信息建设的现状。对于云平台来说如何满足企业的现状,是各云平台厂家迫切需要解决的问题。As cloud platforms become more and more widely used in enterprises, the demands of enterprises on cloud platforms also tend to be diversified. In the actual informatization construction scenario, enterprises follow the national security and controllable system and are gradually completing the goal of domestic replacement of application software. Therefore, the coexistence of domestic server equipment and non-domestic server equipment is the current status of information construction of enterprises. For cloud platforms, how to meet the status quo of enterprises is an urgent problem that cloud platform manufacturers need to solve.
在传统的云平台下管理的云资源池(是面向物理资源划分的概念,一个云资源池也可以称之为一个虚拟化资源集群,简称虚拟化集群或者集群,虚拟化集群拥有一组独立的endpoint(端点);一个云资源池等于OpenStack(云平台)定义的某一个Region(分区))都是同一种 CPU架构的,要么都是x86架构,要么都是arm架构,无法兼容同一个资源池内有多种架构的宿主机。因为在异构资源池下,云平台还无法进行异构资源的调度,比如创建云主机来说:选择一个只支持x86架构的镜像,但云平台无法识别镜像支持的架构,只能是随机调度,如果调度到arm架构的宿主机上,那创建的云主机可能无法正常启动。The cloud resource pool managed under the traditional cloud platform (is a concept oriented to the division of physical resources, a cloud resource pool can also be called a virtualized resource cluster, referred to as a virtualized cluster or cluster, a virtualized cluster has a set of independent endpoint (endpoint); a cloud resource pool is equal to a certain Region (partition) defined by OpenStack (cloud platform)) is of the same CPU architecture, either x86 architecture or arm architecture, which cannot be compatible with the same resource pool. There are hosts of various architectures. Because under the heterogeneous resource pool, the cloud platform cannot perform the scheduling of heterogeneous resources. For example, when creating a cloud host: choose an image that only supports the x86 architecture, but the cloud platform cannot identify the architecture supported by the image, and can only schedule randomly. If it is scheduled to the host of the arm architecture, the created cloud host may not start normally.
为了解决这种异构调度的问题,目前在云平台建设过程中,一般都会将x86或arm架构的宿主机分到两个虚拟化资源池中,而且云平台厂商还需要发布x86版、arm版的云平台版本,无法实现同一云平台(云管理平台)对于异构资源的统一调度。In order to solve this problem of heterogeneous scheduling, currently in the process of cloud platform construction, hosts with x86 or arm architecture are generally divided into two virtualized resource pools, and cloud platform manufacturers also need to release x86 and arm versions. The version of the cloud platform cannot realize the unified scheduling of heterogeneous resources on the same cloud platform (cloud management platform).
发明内容SUMMARY OF THE INVENTION
本发明为了解决现有技术中存在的问题,创新提出了一种异构云资源管理调度方法、装置及系统,有效解决由于现有技术造成无法实现同一云平台(云管理平台)对于异构资源的统一调度的问题,实现了同一云平台对于异构资源的统一管理调度,降低了管理成本,提高了管理调度效率。In order to solve the problems existing in the prior art, the present invention innovatively proposes a method, device and system for managing and scheduling heterogeneous cloud resources, which effectively solves the problem that the same cloud platform (cloud management platform) cannot be implemented for heterogeneous resources due to the prior art. It realizes the unified management and scheduling of heterogeneous resources on the same cloud platform, reduces management costs, and improves management and scheduling efficiency.
本发明第一方面提供了一种异构云资源管理调度方法,包括:A first aspect of the present invention provides a heterogeneous cloud resource management and scheduling method, including:
在云资源池建立多个第一类型可用分区,在云管理平台中多个第二类型可用分区,每个所述第一类型可用分区用于存储同一宿主机架构对应的资源,所述第二类型可用分区与第一类型可用分区一一对应,用于建立云管理平台与第一类型可用分区之间的通信,并对每个第一类型可用分区以及第二类型可用分区设置分区架构标签;Establish multiple first-type AZs in the cloud resource pool, and multiple second-type AZs in the cloud management platform. Each of the first-type AZs is used to store resources corresponding to the same host architecture. The type AZs correspond to the first-type AZs one-to-one, and are used to establish communication between the cloud management platform and the first-type AZs, and a partition architecture label is set for each of the first-type AZs and the second-type AZs;
将云资源池内的所用资源均设置对应资源架构标签;Set the corresponding resource architecture label for all resources used in the cloud resource pool;
云管理平台通过分区架构标签以及资源架构标签实现对云资源池中不同第一类型可用分区内云资源的统一管理调度。The cloud management platform implements unified management and scheduling of cloud resources in different first-type available partitions in the cloud resource pool through partition architecture tags and resource architecture tags.
可选地,第二类型可用分区通过存储一一对应的第一类型可用分区的元数据信息,建立云管理平台与第一类型可用分区之间的通信。Optionally, the second type of availability zone establishes communication between the cloud management platform and the first type of availability zone by storing metadata information of the first type of availability zone in one-to-one correspondence.
可选地,云管理平台对云资源池中不同第一类型可用分区内云资源的统一管理调度具体包括:云管理平台对云资源池中不同第一类型可用分区内云资源的创建、操作过程中实现云资源的统一管理调度,其中,操作包括但不限于扩容、删除、修改。Optionally, the unified management and scheduling of the cloud resources in the different first-type available zones in the cloud resource pool by the cloud management platform specifically includes: the cloud management platform creates and operates the cloud resources in the different first-type available zones in the cloud resource pool. Realize the unified management and scheduling of cloud resources in the cloud, including but not limited to expansion, deletion, and modification.
进一步地,云管理平台对云资源池中不同第一类型可用分区内云资源的创建具体是:Further, the cloud management platform specifically creates cloud resources in different first-type availability zones in the cloud resource pool as follows:
云管理平台获取待创建云资源对应的架构类型,根据待创建云资源对应的架构类型以及分区架构标签,过滤筛选待创建云资源架构类型对应的第一类型可用分区,在筛选后的第一类型可用分区中创建云资源,并对创建后云资源设置资源架构标签,所述资源架构标签与筛选后第一类型可用分区对应的分区架构标签相同。The cloud management platform obtains the architecture type corresponding to the cloud resource to be created, and filters the first type of available partitions corresponding to the architecture type of the cloud resource to be created according to the architecture type corresponding to the cloud resource to be created and the partition architecture label. A cloud resource is created in an available partition, and a resource architecture label is set for the created cloud resource, and the resource architecture label is the same as the partition architecture label corresponding to the first type of available partition after screening.
可选地,云管理平台对云资源池中不同第一类型可用分区内云资源的操作具体是:Optionally, the operations performed by the cloud management platform on cloud resources in different first-type availability zones in the cloud resource pool are specifically:
云管理平台获取待操作云资源对应的架构类型,根据待操作云资源对应的架构类型、分区架构标签、资源架构标签,过滤筛选待操作云资源架构类型对应的第一类型可用分区,在筛选后的第一类型可用分区中对云资源进行对应操作。The cloud management platform obtains the architecture type corresponding to the cloud resource to be operated, and filters the first type of available partitions corresponding to the architecture type of the cloud resource to be operated according to the architecture type, partition architecture label, and resource architecture label corresponding to the cloud resource to be operated. Perform corresponding operations on cloud resources in the first type of available partitions.
进一步地,在筛选后的第一类型可用分区中对云资源进行对应操作之前,还包括:Further, before the corresponding operations are performed on the cloud resources in the filtered first-type AZ, the method further includes:
校验操作与筛选后的第一类型可用分区对应的架构类型是否匹配;如果匹配,则在筛选后的第一类型可用分区中对云资源进行对应操作;如果不匹配,返回给云管理平台对应的提示信息。Check whether the operation matches the architecture type corresponding to the filtered first-type AZ; if it matches, perform the corresponding operation on the cloud resource in the filtered first-type AZ; if it does not match, return it to the cloud management platform prompt information.
进一步地,校验操作与筛选后的第一类型可用分区对应的架构类型是否匹配具体包括:Further, whether the verification operation matches the architecture type corresponding to the filtered first-type AZ specifically includes:
获取操作名称、筛选后的第一类型可用分区对应的架构类型,根据操作名称筛选架构操作矩阵,其中架构操作矩阵存储有架构类型与可支持操作的对应关系;Obtain the operation name and the architecture type corresponding to the filtered first-type available partition, and filter the architecture operation matrix according to the operation name, wherein the architecture operation matrix stores the corresponding relationship between the architecture type and the supported operations;
对比架构操作矩阵的筛选结果与筛选后的第一类型可用分区对应的架构类型进行对比,判断操作与筛选后的第一类型可用分区对应的架构类型是否匹配,如果对比一致,操作与筛选后的第一类型可用分区对应的架构类型匹配;如果对比不一致,操作与筛选后的第一类型可用分区对应的架构类型不匹配。Compare the filtering results of the architecture operation matrix with the architecture types corresponding to the filtered first-type available partitions to determine whether the operation matches the architecture type corresponding to the filtered first-type available partitions. The architecture types corresponding to the first-type AZs match; if the comparison is inconsistent, the operation does not match the architecture types corresponding to the filtered first-type AZs.
可选地,对操作与筛选后的第一类型可用分区对应的架构类型是否匹配的校验与云资源实际进行的对应操作不关联。Optionally, the check of whether the operation matches the architecture type corresponding to the filtered first-type AZ is not related to the corresponding operation actually performed by the cloud resource.
本发明第二方面提供了一种异构云资源管理调度装置,包括:A second aspect of the present invention provides a heterogeneous cloud resource management and scheduling device, including:
建立模块,在云资源池建立多个第一类型可用分区,在云管理平台中多个第二类型可用分区,每个所述第一类型可用分区用于存储同一宿主机架构对应的资源,所述第二类型可用分区与第一类型可用分区一一对应,用于建立云管理平台与第一类型可用分区之间的通信,并对每个第一类型可用分区以及第二类型可用分区设置分区架构标签;The establishment module establishes multiple first-type available partitions in the cloud resource pool, multiple second-type available partitions in the cloud management platform, and each of the first-type available partitions is used to store resources corresponding to the same host architecture, so The second-type AZs are in one-to-one correspondence with the first-type AZs, and are used to establish communication between the cloud management platform and the first-type AZs, and set partitions for each of the first-type AZs and the second-type AZs schema tag;
设置模块,将云资源池内的所用资源均设置对应资源架构标签;Set the module to set the corresponding resource architecture label for all resources in the cloud resource pool;
管理调度模块,云管理平台通过分区架构标签以及资源架构标签实现对云资源池中不同第一类型可用分区内云资源的统一管理调度。The management scheduling module, the cloud management platform realizes the unified management and scheduling of cloud resources in different first-type available partitions in the cloud resource pool through the partition architecture label and the resource architecture label.
本发明第三方面提供了一种异构云资源管理调度系统,包括:云管理平台以及云资源池,云资源池,建立多个第一类型可用分区,每个所述第一类型可用分区用于存储同一宿主机架构对应的资源,并对每个第一类型可用分区设置分区架构标签,对云资源池内的所用资源均设置对应资源架构标签;云管理平台建立多个第二类型可用分区,所述第二类型可用分区用于建立云管理平台与云资源池中第一类型可用分区之间的通信,并对每个第二类型可用分区设置分区架构标签;通过分区架构标签以及资源架构标签实现对云资源池中不同第一类型可用分区内云资源的统一管理调度。A third aspect of the present invention provides a heterogeneous cloud resource management and scheduling system, including: a cloud management platform and a cloud resource pool, the cloud resource pool, establishing a plurality of first-type availability partitions, each of the first-type availability partitions uses It is used to store resources corresponding to the same host architecture, set a partition architecture label for each first-type available partition, and set a corresponding resource architecture label for all resources in the cloud resource pool; the cloud management platform establishes multiple second-type available partitions, The second type of available partition is used to establish communication between the cloud management platform and the first type of available partition in the cloud resource pool, and to set a partition architecture label for each second type of available partition; through the partition architecture label and the resource architecture label Realize unified management and scheduling of cloud resources in different first-type availability zones in the cloud resource pool.
本发明采用的技术方案包括以下技术效果:The technical scheme adopted in the present invention includes the following technical effects:
1、本发明有效解决由于现有技术造成无法实现同一云平台(云管理平台)对于异构资源的统一调度的问题,实现了同一云平台对于异构资源的统一管理调度,降低了管理成本,提高了管理调度效率。1. The present invention effectively solves the problem that the same cloud platform (cloud management platform) cannot realize the unified scheduling of heterogeneous resources due to the prior art, realizes the unified management and scheduling of heterogeneous resources by the same cloud platform, and reduces the management cost, Improved management and scheduling efficiency.
2、本发明技术方案在筛选后的第一类型可用分区中对云资源进行对应操作之前,还包括:校验操作与筛选后的第一类型可用分区对应的架构类型是否匹配;如果匹配,则在筛选后的第一类型可用分区中对云资源进行对应操作;如果不匹配,返回给云管理平台对应的提示信息,进一步地保证了操作与目标云资源架构类型可支持操作的一致性,避免了因为操作与目标云资源架构类型可支持操作不一致,导致针对目标资源操作失败。2. The technical solution of the present invention further includes: verifying whether the operation matches the architecture type corresponding to the filtered first-type available partition before performing the corresponding operation on the cloud resources in the filtered first-type available partition; if it matches, then Perform corresponding operations on the cloud resources in the filtered first-type available partitions; if they do not match, return the corresponding prompt information to the cloud management platform, further ensuring the consistency of the operations and the supported operations of the target cloud resource architecture type, avoiding The reason is that the operation on the target resource fails because the operation is inconsistent with the operation supported by the target cloud resource architecture type.
3、本发明技术方案对操作与筛选后的第一类型可用分区对应的架构类型是否匹配的校验与云资源实际进行的对应操作不关联,避免了因为对操作与筛选后的第一类型可用分区对应的架构类型是否匹配的校验对于云资源实际进行的对应业务操作的影响。3. The technical solution of the present invention checks whether the operation matches the architecture type corresponding to the filtered first type of available partition, which is not related to the corresponding operation actually performed by the cloud resources, which avoids the need for the operation and the filtered first type of available partition. Checking whether the architecture types corresponding to the partitions match affects the corresponding business operations actually performed by the cloud resources.
应当理解的是以上的一般描述以及后文的细节描述仅是示例性和解释性的,并不能限制本发明。It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention.
附图说明Description of drawings
为了更清楚说明本发明实施例或现有技术中的技术方案,下面将对实施例或现有技术描述中所需要使用的附图作简单介绍,显而易见的,对于本领域普通技术人员而言,在不付出创造性劳动的前提下,还可以根据这些附图获得其他的附图。In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the accompanying drawings that need to be used in the description of the embodiments or the prior art. Obviously, for those of ordinary skill in the art, On the premise of no creative work, other drawings can also be obtained from these drawings.
图1为本发明方案中实施例一方法的流程示意图;Fig. 1 is the schematic flow chart of the method of Example 1 in the scheme of the present invention;
图2为本发明方案中实施例一方法中云管理平台与云资源池的分区示意图;FIG. 2 is a schematic diagram of the partition of the cloud management platform and the cloud resource pool in the method of Embodiment 1 in the solution of the present invention;
图3为本发明方案中实施例一方法中云资源池的第一类型可用分区中资源创建示意图;FIG. 3 is a schematic diagram of resource creation in the first type of availability zone of the cloud resource pool in the method according to Embodiment 1 of the solution of the present invention;
图4为本发明方案中实施例一方法中步骤S3的部分流程示意图 (一);Fig. 4 is the partial schematic flow chart (1) of step S3 in the embodiment one method in the present invention scheme;
图5为本发明方案中实施例一方法中步骤S3的部分流程示意图 (二);Fig. 5 is the partial schematic flow chart (two) of step S3 in the embodiment one method in the present invention scheme;
图6为本发明方案中实施例一方法中步骤S304的流程示意图;6 is a schematic flowchart of step S304 in the method of Embodiment 1 in the solution of the present invention;
图7为本发明方案中实施例二装置的结构示意图;FIG. 7 is a schematic structural diagram of the device of Example 2 in the solution of the present invention;
图8为本发明方案中实施例三系统的结构示意图。FIG. 8 is a schematic structural diagram of the system of Example 3 in the solution of the present invention.
具体实施方式Detailed ways
为能清楚说明本方案的技术特点,下面通过具体实施方式,并结合其附图,对本发明进行详细阐述。下文的公开提供了许多不同的实施例或例子用来实现本发明的不同结构。为了简化本发明的公开,下文中对特定例子的部件和设置进行描述。此外,本发明可以在不同例子中重复参考数字和/或字母。这种重复是为了简化和清楚的目的,其本身不指示所讨论各种实施例和/或设置之间的关系。应当注意,在附图中所图示的部件不一定按比例绘制。本发明省略了对公知组件和处理技术及工艺的描述以避免不必要地限制本发明。In order to clearly illustrate the technical features of the solution, the present invention will be described in detail below through specific embodiments and in conjunction with the accompanying drawings. The following disclosure provides many different embodiments or examples for implementing different structures of the invention. In order to simplify the disclosure of the present invention, the components and arrangements of specific examples are described below. Furthermore, the present invention may repeat reference numerals and/or letters in different instances. This repetition is for the purpose of simplicity and clarity and does not in itself indicate a relationship between the various embodiments and/or arrangements discussed. It should be noted that the components illustrated in the figures are not necessarily drawn to scale. Descriptions of well-known components and processing techniques and processes are omitted from the present invention to avoid unnecessarily limiting the present invention.
实施例一Example 1
如图1所示,本发明提供了一种异构云资源管理调度方法,包括:As shown in FIG. 1 , the present invention provides a method for managing and scheduling heterogeneous cloud resources, including:
S1,在云资源池建立多个第一类型可用分区,在云管理平台中多个第二类型可用分区,每个所述第一类型可用分区用于存储同一宿主机架构对应的资源,所述第二类型可用分区与第一类型可用分区一一对应,用于建立云管理平台与第一类型可用分区之间的通信,并对每个第一类型可用分区以及第二类型可用分区设置分区架构标签;S1, multiple first-type availability zones are established in the cloud resource pool, multiple second-type available zones are established in the cloud management platform, and each of the first-type available zones is used to store resources corresponding to the same host architecture, and the The second-type AZs correspond to the first-type AZs one-to-one, and are used to establish communication between the cloud management platform and the first-type AZs, and set a partition structure for each of the first-type AZs and the second-type AZs Label;
S2,将云资源池内的所用资源均设置对应资源架构标签;S2, set corresponding resource architecture labels for all resources in the cloud resource pool;
S3,云管理平台通过分区架构标签以及资源架构标签实现对云资源池中不同第一类型可用分区内云资源的统一管理调度。S3, the cloud management platform implements unified management and scheduling of cloud resources in different first-type available partitions in the cloud resource pool through the partition architecture label and the resource architecture label.
在步骤S1中,如图2所示,在云资源池建立多个第一类型可用分区,在云管理平台中多个第二类型可用分区,每个第一类型可用分区用于存储同一宿主机架构对应的资源,第二类型可用分区与第一类型可用分区一一对应,用于建立云管理平台与第一类型可用分区之间的通信,具体地,第二类型可用分区通过存储一一对应的第一类型可用分区的元数据信息,建立云管理平台与第一类型可用分区之间的通信,即第二类型可用分区作为云管理平台与第一类型可用分区之间通信调度的接口;并对每个第一类型可用分区以及第二类型可用分区均设置分区架构标签。可用分区,即AZ(Availability Zone)是一个逻辑概念,可以简单理解为一组节点的集合,这组节点具有独立的电力供应设备,比如一个个独立供电的机房,一个个独立供电的机架都可以被划分成可用分区。In step S1, as shown in FIG. 2, multiple first-type AZs are established in the cloud resource pool, and multiple second-type AZs are created in the cloud management platform, and each first-type AZ is used to store the same host The resources corresponding to the architecture, the second-type AZs correspond one-to-one with the first-type AZs, which are used to establish communication between the cloud management platform and the first-type AZs. Specifically, the second-type AZs are in one-to-one correspondence through storage The metadata information of the first type of availability zone, establishes the communication between the cloud management platform and the first type of availability zone, that is, the second type of availability zone is used as an interface for communication scheduling between the cloud management platform and the first type of availability zone; and A partition schema label is set for each type 1 AZ and each type 2 AZ. Availability Zone, AZ (Availability Zone) is a logical concept, which can be simply understood as a set of nodes. This group of nodes has independent power supply equipment, such as independent power supply equipment rooms and independent power supply racks. Can be divided into available partitions.
第一类型可用分区中的资源可以是硬件资源,也可以是软件资源,还可以是硬件+软件资源,具体地,云资源可以是镜像、云主机(宿主机对应的虚拟机)、云主机快照、云硬盘、云硬盘快照、云主机备份、云硬盘备份等,也可以是其他类型的资源,本发明在此不做限制。The resources in the first type of available partitions can be hardware resources, software resources, or hardware+software resources. Specifically, cloud resources can be images, cloud hosts (virtual machines corresponding to the host), and cloud host snapshots. , cloud hard disk, cloud hard disk snapshot, cloud host backup, cloud hard disk backup, etc., and may also be other types of resources, which are not limited in the present invention.
在步骤S2中,将云资源池内的所用资源均设置对应资源架构标签,然后将资源架构标签与分区架构标签进行匹配,与分区架构标签相同的资源架构标签对应的资源存储至对应的第一类型可用分区中,即第一类型可用分区对应的分区架构标签与第一类型可用分区中存储的资源对应的资源架构标签相同。划分后,云资源池中每个第一类型可用分区中分别存储与该第一类型可用分区架构对应的资源。例如,第一类型可用分区a1对应的分区架构标签为x86,则第一类型可用分区a1中存储的资源对应的资源架构标签也为x86;第一类型可用分区a2对应的分区架构标签为飞腾,则第一类型可用分区a2中存储的资源对应的资源架构标签也为飞腾;第一类型可用分区a3对应的分区架构标签为鲲鹏,则第一类型可用分区a3中存储的资源对应的资源架构标签也为鲲鹏;依次类推。In step S2, all resources in the cloud resource pool are set with corresponding resource architecture tags, then the resource architecture tags are matched with the partition architecture tags, and the resources corresponding to the resource architecture tags that are the same as the partition architecture tags are stored in the corresponding first type In the available partition, that is, the partition architecture label corresponding to the first type of availability zone is the same as the resource architecture label corresponding to the resource stored in the first type of availability zone. After the division, resources corresponding to the architecture of the first type of availability zone are respectively stored in each of the first-type availability zones in the cloud resource pool. For example, if the partition architecture label corresponding to the first-type AZ a1 is x86, the resource architecture label corresponding to the resources stored in the first-type AZ a1 is also x86; the partition architecture label corresponding to the first-type AZ a2 is Feiteng, Then the resource architecture label corresponding to the resource stored in the first type of availability zone a2 is also Feiteng; the partition architecture label corresponding to the first type of availability zone a3 is Kunpeng, then the resource architecture label corresponding to the resources stored in the first type of availability zone a3 Also Kunpeng; and so on.
在步骤S3中,云管理平台对云资源池中不同第一类型可用分区内云资源的统一管理调度具体包括:云管理平台对云资源池中不同第一类型可用分区内云资源的创建、操作过程中实现云资源的统一管理调度,其中,操作包括但不限于扩容、删除、修改。In step S3, the unified management and scheduling of cloud resources in different first-type availability zones in the cloud resource pool by the cloud management platform specifically includes: the cloud management platform creates and operates cloud resources in different first-type availability zones in the cloud resource pool. In the process, the unified management and scheduling of cloud resources is realized, and the operations include but are not limited to expansion, deletion, and modification.
其中,如图3所示,云管理平台对云资源池中不同第一类型可用分区内云资源的创建具体是:Among them, as shown in Figure 3, the cloud management platform specifically creates cloud resources in different first-type availability zones in the cloud resource pool as follows:
云管理平台获取待创建云资源对应的架构类型,根据待创建云资源对应的架构类型以及分区架构标签,过滤筛选(可以通过架构过滤器,即AZ filter执行)待创建云资源架构类型对应的第一类型可用分区,在筛选后的第一类型可用分区中通过调用云资源对应的架构类型对应的容器镜像创建云资源,并对创建后云资源设置资源架构标签,所述资源架构标签与筛选后第一类型可用分区对应的分区架构标签相同。容器镜像是不同架构下的同源代码,当在云资源池中的某一个第一类型可用分区中进行资源创建时,可以调用与该第一类型可用分区对应的架构类型相同的容器进行资源创建。The cloud management platform obtains the architecture type corresponding to the cloud resource to be created, and filters (can be executed through the architecture filter, that is, AZ filter) according to the architecture type corresponding to the cloud resource to be created and the partition architecture label. One type of availability zone, in the filtered first type of availability zone, create a cloud resource by calling the container image corresponding to the architecture type corresponding to the cloud resource, and set a resource architecture label for the created cloud resource, the resource architecture label and the filtered The partition schema labels corresponding to the first type of available partitions are the same. Container images are the same source code under different architectures. When resources are created in a first-type AZ in the cloud resource pool, a container of the same architecture type corresponding to the first-type AZ can be called to create resources. .
进一步地,如图4所示,云管理平台对云资源池中不同第一类型可用分区内云资源的操作具体是:Further, as shown in FIG. 4 , the operations performed by the cloud management platform on cloud resources in different first-type availability zones in the cloud resource pool are as follows:
S301,云管理平台获取待操作云资源对应的架构类型;S301, the cloud management platform obtains the architecture type corresponding to the cloud resource to be operated;
S303,根据待操作云资源对应的架构类型、分区架构标签、资源架构标签,过滤筛选待操作云资源架构类型对应的第一类型可用分区;S303, filter and filter the first type of available partitions corresponding to the architecture type of the cloud resource to be operated according to the architecture type, partition architecture label, and resource architecture label corresponding to the cloud resource to be operated;
S305,在筛选后的第一类型可用分区中对云资源进行对应操作。其中,操作包括但不限于扩容、删除、修改等。S305, perform corresponding operations on the cloud resources in the filtered first-type available partitions. Among them, operations include but are not limited to expansion, deletion, modification, etc.
优选地,如图5所示,在步骤S305之前,还包括:Preferably, as shown in FIG. 5, before step S305, it further includes:
S304,校验操作与筛选后的第一类型可用分区对应的架构类型是否匹配;如果判断结果为是,则执行步骤S305;如果判断结果为否,则执行步骤S306;S304, verifying whether the operation matches the architecture type corresponding to the filtered first-type available partition; if the judgment result is yes, execute step S305; if the judgment result is no, execute step S306;
S305,则在筛选后的第一类型可用分区中对云资源进行对应操作;S305, performing corresponding operations on the cloud resources in the filtered first-type available partitions;
S306,返回给云管理平台对应的提示信息。S306, returning the corresponding prompt information to the cloud management platform.
如图6所示,步骤S304具体包括:As shown in Figure 6, step S304 specifically includes:
S3041,获取操作名称、筛选后的第一类型可用分区对应的架构类型,根据操作名称筛选架构操作矩阵,其中架构操作矩阵存储有架构类型与可支持操作的对应关系;S3041, obtaining the operation name and the architecture type corresponding to the filtered first-type available partition, and filtering the architecture operation matrix according to the operation name, wherein the architecture operation matrix stores the corresponding relationship between the architecture type and the supported operations;
S3042,对比架构操作矩阵的筛选结果与筛选后的第一类型可用分区对应的架构类型进行对比,判断操作与筛选后的第一类型可用分区对应的架构类型是否匹配,如果判断结果为是,则执行步骤S3043;如果判断结果为否,则执行步骤S3044;S3042: Compare the screening result of the architecture operation matrix with the architecture type corresponding to the filtered first-type available partition, and determine whether the operation matches the architecture type corresponding to the filtered first-type available partition. If the determination result is yes, then Go to step S3043; if the judgment result is no, go to step S3044;
S3043,操作与筛选后的第一类型可用分区对应的架构类型匹配;S3043, the operation matches the architecture type corresponding to the filtered first-type available partition;
S3044,操作与筛选后的第一类型可用分区对应的架构类型不匹配。S3044, the operation does not match the architecture type corresponding to the filtered availability partition of the first type.
优选地,对操作与筛选后的第一类型可用分区对应的架构类型是否匹配的校验与云资源实际进行的对应操作不关联。即将对操作与筛选后的第一类型可用分区对应的架构类型是否匹配的校验与云资源实际进行的对应业务操作解耦。Preferably, the check of whether the operation matches the architecture type corresponding to the filtered first-type availability partition is not related to the corresponding operation actually performed by the cloud resource. That is, the verification of whether the operation matches the architecture type corresponding to the filtered first-type AZ is decoupled from the corresponding business operation actually performed by the cloud resource.
需要说明的是,本发明技术方案中步骤可以通过硬件或软件语言编程实现,实现的思路与步骤相对应,也可以通过其他方式实现,本发明在此不做限制。另外,本发明技术方案中架构指的是宿主机架构,即宿主机中CPU架构。It should be noted that the steps in the technical solution of the present invention can be implemented by hardware or software language programming, and the ideas of implementation correspond to the steps, and can also be implemented by other means, which are not limited in the present invention. In addition, the architecture in the technical solution of the present invention refers to the host computer architecture, that is, the CPU architecture in the host computer.
本发明有效解决由于现有技术造成无法实现同一云平台(云管理平台)对于异构资源的统一调度的问题,实现了同一云平台对于异构资源的统一管理调度,降低了管理成本,提高了管理调度效率。The invention effectively solves the problem that the same cloud platform (cloud management platform) cannot realize the unified scheduling of heterogeneous resources due to the existing technology, realizes the unified management and scheduling of heterogeneous resources by the same cloud platform, reduces the management cost, and improves the Manage scheduling efficiency.
本发明技术方案在筛选后的第一类型可用分区中对云资源进行对应操作之前,还包括:校验操作与筛选后的第一类型可用分区对应的架构类型是否匹配;如果匹配,则在筛选后的第一类型可用分区中对云资源进行对应操作;如果不匹配,返回给云管理平台对应的提示信息,进一步地保证了操作与目标云资源架构类型可支持操作的一致性,避免了因为操作与目标云资源架构类型可支持操作不一致,导致针对目标资源操作失败。The technical solution of the present invention further includes: verifying whether the operation matches the architecture type corresponding to the filtered first-type available partition before performing the corresponding operation on the cloud resources in the filtered first-type available partition; Perform corresponding operations on the cloud resources in the first type of available partition after the The operation is inconsistent with the supported operation of the target cloud resource schema type, resulting in the failure of the operation on the target resource.
本发明技术方案对操作与筛选后的第一类型可用分区对应的架构类型是否匹配的校验与云资源实际进行的对应操作不关联,避免了因为对操作与筛选后的第一类型可用分区对应的架构类型是否匹配的校验对于云资源实际进行的对应业务操作的影响。The technical solution of the present invention checks whether the operation matches the architecture type corresponding to the filtered first-type available partition, which is not related to the corresponding operation actually performed by the cloud resources, avoiding the need for the operation to correspond to the filtered first-type available partition. Checking whether the architecture types of the cloud resources match or not affects the corresponding business operations actually performed by the cloud resources.
实施例二Embodiment 2
如图7所示,本发明技术方案还提供了一种异构云资源管理调度装置,包括:As shown in FIG. 7 , the technical solution of the present invention also provides a heterogeneous cloud resource management and scheduling device, including:
建立模块101,在云资源池建立多个第一类型可用分区,在云管理平台中多个第二类型可用分区,每个所述第一类型可用分区用于存储同一宿主机架构对应的资源,所述第二类型可用分区与第一类型可用分区一一对应,用于建立云管理平台与第一类型可用分区之间的通信,并对每个第一类型可用分区以及第二类型可用分区设置分区架构标签;Establishing
设置模块102,将云资源池内的所用资源均设置对应资源架构标签;The
管理调度模块103,云管理平台通过分区架构标签以及资源架构标签实现对云资源池中不同第一类型可用分区内云资源的统一管理调度。
在建立模块101中,如图2所示,在云资源池建立多个第一类型可用分区,在云管理平台中多个第二类型可用分区,每个第一类型可用分区用于存储同一宿主机架构对应的资源,第二类型可用分区与第一类型可用分区一一对应,用于建立云管理平台与第一类型可用分区之间的通信,具体地,第二类型可用分区通过存储一一对应的第一类型可用分区的元数据信息,建立云管理平台与第一类型可用分区之间的通信,即第二类型可用分区作为云管理平台与第一类型可用分区之间通信调度的接口;并对每个第一类型可用分区以及第二类型可用分区均设置分区架构标签。可用分区,即AZ(Availability Zone)是一个逻辑概念,可以简单理解为一组节点的集合,这组节点具有独立的电力供应设备,比如一个个独立供电的机房,一个个独立供电的机架都可以被划分成可用分区。In the
第一类型可用分区中的资源可以是硬件资源,也可以是软件资源,还可以是硬件+软件资源,具体地,云资源可以是镜像、云主机(宿主机对应的虚拟机)、云主机快照、云硬盘、云硬盘快照、云主机备份、云硬盘备份等,也可以是其他类型的资源,本发明在此不做限制。The resources in the first type of available partitions can be hardware resources, software resources, or hardware+software resources. Specifically, cloud resources can be images, cloud hosts (virtual machines corresponding to the host), and cloud host snapshots. , cloud hard disk, cloud hard disk snapshot, cloud host backup, cloud hard disk backup, etc., and may also be other types of resources, which are not limited in the present invention.
在设置模块102中,将云资源池内的所用资源均设置对应资源架构标签,然后将资源架构标签与分区架构标签进行匹配,与分区架构标签相同的资源架构标签对应的资源存储至对应的第一类型可用分区中,即第一类型可用分区对应的分区架构标签与第一类型可用分区中存储的资源对应的资源架构标签相同。划分后,云资源池中每个第一类型可用分区中分别存储与该第一类型可用分区架构对应的资源。例如,第一类型可用分区a1对应的分区架构标签为x86,则第一类型可用分区a1中存储的资源对应的资源架构标签也为x86;第一类型可用分区a2对应的分区架构标签为飞腾,则第一类型可用分区a2 中存储的资源对应的资源架构标签也为飞腾;第一类型可用分区a3 对应的分区架构标签为鲲鹏,则第一类型可用分区a3中存储的资源对应的资源架构标签也为鲲鹏;依次类推。In the
在管理调度模块103中,云管理平台对云资源池中不同第一类型可用分区内云资源的统一管理调度具体包括:云管理平台对云资源池中不同第一类型可用分区内云资源的创建、操作过程中实现云资源的统一管理调度,其中,操作包括但不限于扩容、删除、修改。In the
其中,云管理平台对云资源池中不同第一类型可用分区内云资源的创建具体是:Specifically, the cloud management platform creates cloud resources in different first-type availability zones in the cloud resource pool as follows:
云管理平台获取待创建云资源对应的架构类型,根据待创建云资源对应的架构类型以及分区架构标签,过滤筛选(可以通过架构过滤器,即AZ filter执行)待创建云资源架构类型对应的第一类型可用分区,在筛选后的第一类型可用分区中通过调用云资源对应的架构类型对应的容器镜像创建云资源,并对创建后云资源设置资源架构标签,所述资源架构标签与筛选后第一类型可用分区对应的分区架构标签相同。容器镜像是不同架构下的同源代码,当在云资源池中的某一个第一类型可用分区中进行资源创建时,可以调用与该第一类型可用分区对应的架构类型相同的容器进行资源创建。The cloud management platform obtains the architecture type corresponding to the cloud resource to be created, and filters (can be executed through the architecture filter, that is, AZ filter) according to the architecture type corresponding to the cloud resource to be created and the partition architecture label. One type of availability zone, in the filtered first type of availability zone, create a cloud resource by calling the container image corresponding to the architecture type corresponding to the cloud resource, and set a resource architecture label for the created cloud resource, the resource architecture label and the filtered The partition schema labels corresponding to the first type of available partitions are the same. Container images are the same source code under different architectures. When resources are created in a first-type AZ in the cloud resource pool, a container of the same architecture type corresponding to the first-type AZ can be called to create resources. .
本发明有效解决由于现有技术造成无法实现同一云平台(云管理平台)对于异构资源的统一调度的问题,实现了同一云平台对于异构资源的统一管理调度,降低了管理成本,提高了管理调度效率。The invention effectively solves the problem that the same cloud platform (cloud management platform) cannot realize the unified scheduling of heterogeneous resources due to the existing technology, realizes the unified management and scheduling of heterogeneous resources by the same cloud platform, reduces the management cost, and improves the Manage scheduling efficiency.
本发明技术方案在筛选后的第一类型可用分区中对云资源进行对应操作之前,还包括:校验操作与筛选后的第一类型可用分区对应的架构类型是否匹配;如果匹配,则在筛选后的第一类型可用分区中对云资源进行对应操作;如果不匹配,返回给云管理平台对应的提示信息,进一步地保证了操作与目标云资源架构类型可支持操作的一致性,避免了因为操作与目标云资源架构类型可支持操作不一致,导致针对目标资源操作失败。The technical solution of the present invention further includes: verifying whether the operation matches the architecture type corresponding to the filtered first-type available partition before performing the corresponding operation on the cloud resources in the filtered first-type available partition; Perform corresponding operations on the cloud resources in the first type of available partition after the The operation is inconsistent with the supported operation of the target cloud resource schema type, resulting in the failure of the operation on the target resource.
本发明技术方案对操作与筛选后的第一类型可用分区对应的架构类型是否匹配的校验与云资源实际进行的对应操作不关联,避免了因为对操作与筛选后的第一类型可用分区对应的架构类型是否匹配的校验对于云资源实际进行的对应业务操作的影响。The technical solution of the present invention checks whether the operation matches the architecture type corresponding to the filtered first-type available partition, which is not related to the corresponding operation actually performed by the cloud resources, avoiding the need for the operation to correspond to the filtered first-type available partition. Checking whether the architecture types of the cloud resources match or not affects the corresponding business operations actually performed by the cloud resources.
实施例三Embodiment 3
如图8所示,本发明技术方案还提供了一种异构云资源管理调度系统,包括:云管理平台201以及云资源池202,云资源池202,建立多个第一类型可用分区,每个所述第一类型可用分区用于存储同一宿主机架构对应的资源,并对每个第一类型可用分区设置分区架构标签,对云资源池内的所用资源均设置对应资源架构标签;云管理平台 201建立多个第二类型可用分区,所述第二类型可用分区用于建立云管理平台201与云资源池202中第一类型可用分区之间的通信,并对每个第二类型可用分区设置分区架构标签;通过分区架构标签以及资源架构标签实现对云资源池202中不同第一类型可用分区内云资源的统一管理调度。As shown in FIG. 8 , the technical solution of the present invention also provides a heterogeneous cloud resource management and scheduling system, including: a
具体地,第二类型可用分区通过存储一一对应的第一类型可用分区的元数据信息,建立云管理平台201与第一类型可用分区之间的通信,即第二类型可用分区作为云管理平台201与第一类型可用分区之间通信调度的接口;并对每个第一类型可用分区以及第二类型可用分区均设置分区架构标签。可用分区,即AZ(Availability Zone)是一个逻辑概念,可以简单理解为一组节点的集合,这组节点具有独立的电力供应设备,比如一个个独立供电的机房,一个个独立供电的机架都可以被划分成可用分区。Specifically, the second-type AZ establishes communication between the
第一类型可用分区中的资源可以是硬件资源,也可以是软件资源,还可以是硬件+软件资源,具体地,云资源可以是镜像、云主机(宿主机对应的虚拟机)、云主机快照、云硬盘、云硬盘快照、云主机备份、云硬盘备份等,也可以是其他类型的资源,本发明在此不做限制。The resources in the first type of available partitions can be hardware resources, software resources, or hardware+software resources. Specifically, cloud resources can be images, cloud hosts (virtual machines corresponding to the host), and cloud host snapshots. , cloud hard disk, cloud hard disk snapshot, cloud host backup, cloud hard disk backup, etc., and may also be other types of resources, which are not limited in the present invention.
云资源池202在内部所用资源均设置对应资源架构标签,然后将资源架构标签与分区架构标签进行匹配,与分区架构标签相同的资源架构标签对应的资源存储至对应的第一类型可用分区中,即第一类型可用分区对应的分区架构标签与第一类型可用分区中存储的资源对应的资源架构标签相同。划分后,云资源池202中每个第一类型可用分区中分别存储与该第一类型可用分区架构对应的资源。例如,第一类型可用分区a1对应的分区架构标签为x86,则第一类型可用分区 a1中存储的资源对应的资源架构标签也为x86;第一类型可用分区a2 对应的分区架构标签为飞腾,则第一类型可用分区a2中存储的资源对应的资源架构标签也为飞腾;第一类型可用分区a3对应的分区架构标签为鲲鹏,则第一类型可用分区a3中存储的资源对应的资源架构标签也为鲲鹏;依次类推。The resources used in the
云管理平台201对云资源池202中不同第一类型可用分区内云资源的统一管理调度具体包括:云管理平台201对云资源池202中不同第一类型可用分区内云资源的创建、操作过程中实现云资源的统一管理调度,其中,操作包括但不限于扩容、删除、修改。The unified management and scheduling of the cloud resources in the different first-type availability zones in the
其中,云管理平台201对云资源池202中不同第一类型可用分区内云资源的创建具体是:Specifically, the
云管理平台201获取待创建云资源对应的架构类型,根据待创建云资源对应的架构类型以及分区架构标签,过滤筛选(可以通过架构过滤器,即AZ filter执行)待创建云资源架构类型对应的第一类型可用分区,在筛选后的第一类型可用分区中通过调用云资源对应的架构类型对应的容器镜像创建云资源,并对创建后云资源设置资源架构标签,所述资源架构标签与筛选后第一类型可用分区对应的分区架构标签相同。容器镜像是不同架构下的同源代码,当在云资源池202中的某一个第一类型可用分区中进行资源创建时,可以调用与该第一类型可用分区对应的架构类型相同的容器进行资源创建。The
本发明有效解决由于现有技术造成无法实现同一云平台(云管理平台)对于异构资源的统一调度的问题,实现了同一云平台对于异构资源的统一管理调度,降低了管理成本,提高了管理调度效率。The invention effectively solves the problem that the same cloud platform (cloud management platform) cannot realize the unified scheduling of heterogeneous resources due to the existing technology, realizes the unified management and scheduling of heterogeneous resources by the same cloud platform, reduces the management cost, and improves the Manage scheduling efficiency.
本发明技术方案在筛选后的第一类型可用分区中对云资源进行对应操作之前,还包括:校验操作与筛选后的第一类型可用分区对应的架构类型是否匹配;如果匹配,则在筛选后的第一类型可用分区中对云资源进行对应操作;如果不匹配,返回给云管理平台对应的提示信息,进一步地保证了操作与目标云资源架构类型可支持操作的一致性,避免了因为操作与目标云资源架构类型可支持操作不一致,导致针对目标资源操作失败。The technical solution of the present invention further includes: verifying whether the operation matches the architecture type corresponding to the filtered first-type available partition before performing the corresponding operation on the cloud resources in the filtered first-type available partition; Perform corresponding operations on the cloud resources in the first type of available partition after the The operation is inconsistent with the supported operation of the target cloud resource schema type, resulting in the failure of the operation on the target resource.
本发明技术方案对操作与筛选后的第一类型可用分区对应的架构类型是否匹配的校验与云资源实际进行的对应操作不关联,避免了因为对操作与筛选后的第一类型可用分区对应的架构类型是否匹配的校验对于云资源实际进行的对应业务操作的影响。The technical solution of the present invention checks whether the operation matches the architecture type corresponding to the filtered first-type available partition, which is not related to the corresponding operation actually performed by the cloud resources, avoiding the need for the operation to correspond to the filtered first-type available partition. Checking whether the architecture types of the cloud resources match or not affects the corresponding business operations actually performed by the cloud resources.
上述虽然结合附图对本发明的具体实施方式进行了描述,但并非对本发明保护范围的限制,所属领域技术人员应该明白,在本发明的技术方案的基础上,本领域技术人员不需要付出创造性劳动即可做出的各种修改或变形仍在本发明的保护范围以内。Although the specific embodiments of the present invention have been described above in conjunction with the accompanying drawings, they do not limit the scope of protection of the present invention. Those skilled in the art should understand that on the basis of the technical solutions of the present invention, those skilled in the art do not need to pay creative work. Various modifications or deformations that can be made are still within the protection scope of the present invention.
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210073785.XACN114443295B (en) | 2022-01-21 | 2022-01-21 | A heterogeneous cloud resource management and scheduling method, device and system |
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210073785.XACN114443295B (en) | 2022-01-21 | 2022-01-21 | A heterogeneous cloud resource management and scheduling method, device and system |
| Publication Number | Publication Date |
|---|---|
| CN114443295Atrue CN114443295A (en) | 2022-05-06 |
| CN114443295B CN114443295B (en) | 2024-01-12 |
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210073785.XAActiveCN114443295B (en) | 2022-01-21 | 2022-01-21 | A heterogeneous cloud resource management and scheduling method, device and system |
| Country | Link |
|---|---|
| CN (1) | CN114443295B (en) |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115225535A (en)* | 2022-07-27 | 2022-10-21 | 济南浪潮数据技术有限公司 | Consistency detection method and related components of a cloud platform |
| CN115514634A (en)* | 2022-09-07 | 2022-12-23 | 上海浪潮云计算服务有限公司 | Cloud center management method and device |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107395748A (en)* | 2017-08-21 | 2017-11-24 | 京东方科技集团股份有限公司 | Heterogeneous distributed cloud resource management method and system |
| CN107948254A (en)* | 2017-11-10 | 2018-04-20 | 上海华讯网络系统有限公司 | Mix the big data processing frame arranging system and method for cloud platform |
| CN108062248A (en)* | 2017-12-08 | 2018-05-22 | 华胜信泰信息产业发展有限公司 | Method for managing resource, system, equipment and the storage medium of isomery virtual platform |
| CN110362409A (en)* | 2019-07-19 | 2019-10-22 | 深圳前海微众银行股份有限公司 | Based on a plurality of types of resource allocation methods, device, equipment and storage medium |
| US20200151023A1 (en)* | 2018-11-13 | 2020-05-14 | Microsoft Technology Licensing, Llc | Deploying cloud-native services across control planes |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107395748A (en)* | 2017-08-21 | 2017-11-24 | 京东方科技集团股份有限公司 | Heterogeneous distributed cloud resource management method and system |
| CN107948254A (en)* | 2017-11-10 | 2018-04-20 | 上海华讯网络系统有限公司 | Mix the big data processing frame arranging system and method for cloud platform |
| CN108062248A (en)* | 2017-12-08 | 2018-05-22 | 华胜信泰信息产业发展有限公司 | Method for managing resource, system, equipment and the storage medium of isomery virtual platform |
| US20200151023A1 (en)* | 2018-11-13 | 2020-05-14 | Microsoft Technology Licensing, Llc | Deploying cloud-native services across control planes |
| CN110362409A (en)* | 2019-07-19 | 2019-10-22 | 深圳前海微众银行股份有限公司 | Based on a plurality of types of resource allocation methods, device, equipment and storage medium |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115225535A (en)* | 2022-07-27 | 2022-10-21 | 济南浪潮数据技术有限公司 | Consistency detection method and related components of a cloud platform |
| CN115514634A (en)* | 2022-09-07 | 2022-12-23 | 上海浪潮云计算服务有限公司 | Cloud center management method and device |
| Publication number | Publication date |
|---|---|
| CN114443295B (en) | 2024-01-12 |
| Publication | Publication Date | Title |
|---|---|---|
| CN111488241B (en) | Method and system for realizing agent-free backup and recovery operation in container arrangement platform | |
| JP5427574B2 (en) | Virtual computer migration management method, computer using the migration management method, virtualization mechanism using the migration management method, and computer system using the migration management method | |
| WO2018177107A1 (en) | Data migration method, migration server, and storage medium | |
| CN103034527B (en) | Hybrid virtualization cloud computing resource optimization control method and system | |
| CN101320339B (en) | Information-processing equipment and system therefor | |
| CN103118073B (en) | Virtual machine data persistence storage system and method in cloud environment | |
| CN113986450B (en) | Virtual machine backup method and device | |
| CN114443295B (en) | A heterogeneous cloud resource management and scheduling method, device and system | |
| CN103049317A (en) | Highly-concurrent data fast write system and method based on queues in cloud environment | |
| CN113157411B (en) | Celery-based reliable configurable task system and device | |
| CN108108119B (en) | Configuration method and device for extensible storage cluster things | |
| CN109408201B (en) | Transaction Management Method Based on Distributed Database | |
| CN103019809B (en) | Business processing device and method, and business processing control device | |
| CN109522145A (en) | A kind of virtual-machine fail automatic recovery system and its method | |
| CN105677481B (en) | A kind of data processing method, system and electronic equipment | |
| WO2023016414A1 (en) | Credential rotation method, computing device, and storage medium | |
| CN115617493A (en) | A task management scheduling method for a distributed multi-cloud management platform | |
| CN104461705A (en) | Service access method, storage controllers and cluster storage system | |
| CN114598604B (en) | Monitoring method, monitoring device and terminal for virtual network function instance information | |
| CN104504348A (en) | Data protecting method based on high availability storage system | |
| US20240176651A1 (en) | Auto time optimization for migration of applications | |
| US20240256575A1 (en) | Access authorization for report data in a multi-tenancy data management system | |
| CN113032141B (en) | AI platform resource switching method, system and medium | |
| WO2024174306A1 (en) | Transaction hosting method and apparatus based on shared storage database cluster | |
| US10365864B2 (en) | Information processing system and operation redundantizing method |
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP03 | Change of name, title or address | Address after:Building 9, No.1, guanpu Road, Guoxiang street, Wuzhong Economic Development Zone, Wuzhong District, Suzhou City, Jiangsu Province Patentee after:Suzhou Yuannao Intelligent Technology Co.,Ltd. Country or region after:China Address before:Building 9, No.1, guanpu Road, Guoxiang street, Wuzhong Economic Development Zone, Wuzhong District, Suzhou City, Jiangsu Province Patentee before:SUZHOU LANGCHAO INTELLIGENT TECHNOLOGY Co.,Ltd. Country or region before:China |