CN109358965B - Cloud computing cluster resource scheduling method, medium, device and computing equipment - Google Patents

Cloud computing cluster resource scheduling method, medium, device and computing equipment Download PDF

Info

Publication number
CN109358965B
CN109358965B CN201811114998.2A CN201811114998A CN109358965B CN 109358965 B CN109358965 B CN 109358965B CN 201811114998 A CN201811114998 A CN 201811114998A CN 109358965 B CN109358965 B CN 109358965B
Authority
CN
China
Prior art keywords
node
service
resource
attribute information
determining
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201811114998.2A
Other languages
Chinese (zh)
Other versions
CN109358965A (en
Inventor
张晓龙
陈林亮
崔云娜
管强
岳文远
廖跃华
陈谔
尧飘海
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hangzhou Netease Shuzhifan Technology Co ltd
Original Assignee
Hangzhou Langhe Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hangzhou Langhe Technology Co Ltd filed Critical Hangzhou Langhe Technology Co Ltd
Priority to CN201811114998.2A priority Critical patent/CN109358965B/en
Publication of CN109358965A publication Critical patent/CN109358965A/en
Application granted granted Critical
Publication of CN109358965B publication Critical patent/CN109358965B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G06F11/3006—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3055—Monitoring arrangements for monitoring the status of the computing system or of the computing system component, e.g. monitoring if the computing system is on, off, available, not available

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • Software Systems (AREA)
  • Mathematical Physics (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

The embodiment of the invention provides a cloud computing cluster resource scheduling method, medium, device and computing equipment. The cloud computing cluster resource scheduling method comprises the following steps: acquiring service request information; determining at least one creating node according to the service request information; scheduling the creation node for creating a cloud host. The technical scheme provided by the application can be used for scheduling the cloud computing cluster resources based on the nodes, is favorable for improving the resource utilization rate, reduces the operation cost, is friendly to operation and maintenance, improves the elastic expansion capacity of the cloud resources, and brings better experience for users.

Description

Cloud computing cluster resource scheduling method, medium, device and computing equipment
Technical Field
The embodiment of the invention relates to the field of cloud computing, in particular to a cloud computing cluster resource scheduling method, medium, device and computing equipment.
Background
This section is intended to provide a background or context to the embodiments of the invention that are recited in the claims. The description herein is not admitted to be prior art by inclusion in this section.
The cloud computing service refers to the unified management and scheduling of a large number of computing resources connected by a network, so that a computing resource pool is formed to serve users on demand. The user obtains the required resources and services through the network in an on-demand, easily scalable manner. Resource scheduling is a primary function of cloud computing.
The resource scheduling is used for determining a computing node where a cloud host to be created is located, and the following conditions are required to be met: a) the computing node meets the resource requirement of the cloud host to be created; b) the computing node meets the additional business isolation attribute of the cloud host to be created. Currently, cloud computing cluster resources mainly adopt a scheduling scheme based on AZ (Available Zone). AZ is a collection of a group of computing nodes, network fault isolation and physical location (cabinet) isolation usually exist between AZs, and within the same AZ, the computing nodes have a group of same service isolation attributes, such as home dedicated users, service types, the same oversaled proportion, the same hardware and the like. When cloud computing is deployed, a group of AZs is planned, and the business isolation attribute of the AZs is determined. Then, when the cluster resource is used (i.e., the cloud host is created), AZ is explicitly given in the creation request by an upper layer Service (IAAS (Infrastructure as a Service) direct consumer). And the IAAS selects a proper node according to the requested AZ information and the use condition of the resource in the AZ.
The scheduling scheme based on AZ needs to use AZ as a unit in terms of deployment, operation and maintenance, and is a better method under the condition of less scale. However, with the expansion of the scale, especially in a public cloud environment, under the superposition of various PAAS (Platform as a Service) services, the AZ scheduling may have the following problems:
a) the resource idle rate is high. With the enlargement of the scale, the types of the service isolation attributes are more and more, and the scheduling scheme based on AZ can only increase the number of AZ. In general, for the purpose of operation and maintenance safety and reduction of operation and maintenance times, AZ is not small. However, the use of resources by users is not very easy to predict, so that a situation that part of resources cannot be effectively utilized necessarily occurs;
b) the operation and maintenance are complex. The number of AZs is too large, the nodes are dispersed and cannot be mutually complemented, capacity expansion needs occur, and the operation and maintenance times are inevitably increased. In addition, capacity monitoring and prediction is also a problem;
c) and (4) elastic expansibility. The increase in traffic types also requires the creation of a new series of AZ's, even if the original AZ's have abundant resources.
Disclosure of Invention
For this reason, an improved cloud computing cluster resource scheduling scheme is highly needed to improve the utilization rate of the cloud computing cluster resources.
In this context, embodiments of the present invention are intended to provide a cloud computing cluster resource scheduling method, medium, apparatus, and computing device.
In a first aspect of embodiments of the present invention, a cloud computing cluster resource scheduling method is provided, including the following steps: acquiring service request information; determining at least one creating node according to the service request information; scheduling the creation node for creating a cloud host.
In a second aspect of embodiments of the present invention, there is provided a computer-readable storage medium storing program code, which when executed as a processor, implements the cloud computing cluster resource scheduling method as described above.
In a third aspect of the embodiments of the present invention, there is provided a cloud computing cluster resource scheduling apparatus, including: the controller is used for acquiring service request information; a creating node determining module, configured to determine at least one creating node according to the service request information; the controller is further configured to schedule the creation node for creating a cloud host.
In a fourth aspect of embodiments of the present invention, there is provided a computing device comprising a processor and a storage medium storing program code, which when executed by the processor, implements the cloud computing cluster resource scheduling method as described above.
According to the cloud computing cluster resource scheduling method, medium, device and computing equipment provided by the embodiment of the invention, the cloud computing cluster resource can be scheduled based on the nodes, so that the resource utilization rate is favorably improved, the operation cost is reduced, the operation and maintenance are friendly, the elastic expansion capability of the cloud resource is improved, and better experience is brought to users.
Drawings
The above and other objects, features and advantages of exemplary embodiments of the present invention will become readily apparent from the following detailed description read in conjunction with the accompanying drawings. Several embodiments of the invention are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which:
fig. 1 is a flowchart of an embodiment of a cloud computing cluster resource scheduling method according to the present application;
fig. 2 is a flowchart of another embodiment of a cloud computing cluster resource scheduling method according to the present application;
fig. 3(a) is a schematic diagram of a specific embodiment of a cloud computing cluster resource scheduling method according to the present application;
fig. 3(b) is a schematic diagram of a specific embodiment of a cloud computing cluster resource scheduling method according to the present application;
FIG. 4 is a schematic diagram of a computer-readable storage medium according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of a cloud computing cluster resource scheduling apparatus according to an embodiment of the present application;
FIG. 6 is a schematic block diagram of a computing device according to an embodiment of the present application;
in the drawings, the same or corresponding reference numerals indicate the same or corresponding parts.
Detailed Description
The principles and spirit of the present invention will be described with reference to a number of exemplary embodiments. It is understood that these embodiments are given solely for the purpose of enabling those skilled in the art to better understand and to practice the invention, and are not intended to limit the scope of the invention in any way. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
As will be appreciated by one skilled in the art, embodiments of the present invention may be embodied as a system, apparatus, device, method, or computer program product. Accordingly, the present disclosure may be embodied in the form of: entirely hardware, entirely software (including firmware, resident software, micro-code, etc.), or a combination of hardware and software.
According to the embodiment of the invention, a method, a medium, a device and computing equipment for scheduling cloud computing cluster resources are provided.
In this document, it is to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. Moreover, any number of elements in the drawings are by way of example and not by way of limitation, and any nomenclature is used solely for differentiation and not by way of limitation.
The principles and spirit of the present invention are explained in detail below with reference to several representative embodiments of the invention.
Summary of The Invention
The inventor finds that the cloud computing cluster resource scheduling based on AZ is obviously rigid, one AZ only provides one upper-layer service and has an excessive isolation phenomenon, the cloud computing cluster resource scheduling based on nodes has a larger degree of freedom, and one AZ can provide a plurality of services as long as the hardware resources required by the services are consistent and the isolation requirement is not violated.
Having described the general principles of the invention, various non-limiting embodiments of the invention are described in detail below.
Application scene overview
According to the cloud computing cluster resource scheduling method, medium, device and computing equipment, cloud computing cluster resource scheduling is performed based on the nodes, the service isolation attribute is abstracted to be the label and is marked on the computing nodes, one node can be marked with various labels, and computing nodes meeting the conditions are screened out according to the service request of a user and used for creating the cloud host, so that the utilization rate of cloud computing resources is improved, the operation cost is reduced, the operation and maintenance are friendly, the elastic expansion capacity of the cloud resources is improved, and better experience is brought to the user.
Exemplary method
A method of cloud computing cluster resource scheduling according to an exemplary embodiment of the present invention is described below with reference to fig. 1-2. It should be noted that the above application scenarios are merely illustrated for the convenience of understanding the spirit and principles of the present invention, and the embodiments of the present invention are not limited in this respect. Rather, embodiments of the present invention may be applied to any scenario where applicable.
Fig. 1 is a flowchart illustrating an embodiment of a cloud computing cluster resource scheduling method according to the present application, where the method includes the following steps:
s101: acquiring service request information;
s102: determining at least one creating node according to the service request information;
s103: scheduling the creation node for creating a cloud host.
As an optional implementation manner, service request information of a user is obtained, where the service request information may include service attribute information and resource attribute information, and the service attribute information may include service isolation attribute requirements of the user on a creation node, which may include, but is not limited to, a user type, a service type, a copy domain, an oversale rate, and the like, for example, and is not limited herein. The resource attribute information may include a user's requirement for a resource of the creation node, and may include, but is not limited to, a computing resource (e.g., CPU, memory, etc.), a network resource, a storage resource, a special hardware resource, etc., for example. Optionally, the service request information may also include other requirements set forth by the user, and is not limited to include only the above.
As an optional implementation manner, at least one creation node is determined according to the service request information, a node meeting the requirements of the user in the service request information can be screened out from a plurality of nodes according to the service request information of the user to serve as a creation node, and the creation node is scheduled to be used for creating the cloud host.
In this embodiment, at least one screened creation node is selected. When the number of the screened creation nodes is just one, the creation nodes are called to be used for creating the cloud host, when the number of the screened creation nodes is two or more, descending arrangement can be carried out according to the condition of available resources of each creation node, one with the largest number of the available resources is generally scheduled to be used for creating the cloud host, one meeting the requirement can also be scheduled to be used for creating the cloud host in the screened creation nodes according to other requirements, and when the creation nodes meeting the service request information of the user cannot be screened, the user request fails. Generally, a monitoring system is arranged in a cloud platform and used for monitoring resource use conditions of each node and supplementing the nodes in time according to preset information so as to ensure that a user request cannot fail to the maximum extent.
According to the scheme for scheduling the cloud computing cluster resources based on the nodes, under the environment that more and more user requests are made, the saturation of cloud computing resource use is improved, the online operation and maintenance frequency is reduced, the operation and maintenance complexity is reduced, and the elastic expansibility is increased under the conditions that high availability, isolation and the like are not lost.
Fig. 2 is a flowchart illustrating another embodiment of a cloud computing cluster resource scheduling method according to the present application, where the method includes the following steps:
s201: adding a label to each node based on the service isolation attribute information of each node, and collecting the available resource condition of each node;
s202: acquiring service request information, wherein the service request information comprises service attribute information and resource attribute information;
s203: determining at least one creating node according to the service request information;
s204: scheduling the creation node for creating a cloud host.
As an optional implementation manner, before the service request information is obtained, a label may be added to each node based on the service isolation attribute information of each node, the label of each node is incorporated into the node label management system for unified management, the available resource condition of each node is collected, and the available resource condition of each node is incorporated into the node resource management system for unified management.
The label types can be established according to the service isolation attributes of each node, unified planning management is carried out, the contained labels are set for each label type, the binding relationship between each label and each node is managed, and the like. Or, a corresponding tag type may be established according to other attribute information of each node, and unified planning management is performed, where a service isolation attribute is taken as an example for description. The label types established according to the service isolation attribute may include, for example, a user type, a service type, a copy domain, an over-sale ratio, and the like, where the user type may also include, for example, a subdivided label, and the like may be, for example, a general user and an exclusive user, and so on. The management of the tags is not limited herein, and can be set by those skilled in the art as needed. The corresponding label can be bound for each node according to the actual situation of each node, so that the service isolation attribute information of the node can be judged according to the label, for example, and the label of each node is updated and checked at regular time to ensure the real-time property of the label information.
The method for acquiring the available resource condition of each node may acquire, for example, a computing resource, a network resource, a storage resource, a special hardware resource, and the like of each node, where acquiring the computing resource of each node may further include acquiring an available CPU size, an available memory size, and the like of each node, and so on. The available resource condition of each node may be collected at regular time, an available resource lower limit value may be set for each node, and when the available resource condition of a certain node is lower than the available resource lower limit value, the node is adjusted, or a new node is created, or other operations for expanding the available resource condition of the node are performed, which is not limited herein.
Additionally, the legitimacy of tagging each node may also be improved by checking additional attributes of the tag type when tagging each node. An additional attribute may be set for some tag types, for example, a "tag that a node must bind to", when checking the validity of tags of all nodes, it is checked whether each node binds to a tag included in a tag type with the additional attribute, if it is found that a node does not bind to a tag included in a tag type with the additional attribute, it is determined that the tag applied to the node is not legal and the binding of the node to the tag fails, an additional attribute may be set for some tag types, for example, a "tag that a node must uniquely bind to", when checking the validity of tags of all nodes, it is checked whether each node binds to tags included in two or more tag types with the additional attribute, if it is found that a node binds to tags included in two or more tag types with the additional attribute, it is determined that the node is not tagged legitimately and that the binding of the tag to the node fails. Therefore, the legality of labeling each node is improved by checking the additional attribute of the label type, and the legality of system data is further ensured.
As a first specific embodiment, determining at least one creating node according to the service request information may include the steps of: determining a first candidate node list according to the service attribute information; a first set of created nodes is determined from the resource attribute information based on the first list of candidate nodes. The nodes can be subjected to a first round of screening according to the service attribute information in the service request information of the user, the nodes meeting the service attribute information are listed as a first candidate node list, and then the nodes whose available resource conditions meet the resource attribute information are screened from the first candidate node list according to the resource attribute information in the service request information of the user and are determined as a first group of created nodes. The number of creating nodes in the first group of creating nodes is not limited herein, and when the number of creating nodes in the first group of creating nodes is exactly one, the creating nodes are called to create the cloud host, when the number of creating nodes in the first group of creating nodes is two or more, one creating node with the largest number of available resources is generally scheduled to be used for creating the cloud host, or one creating node meeting other conditions of a user is selected from the creating nodes, the creating node is called to create the cloud host, when no creating node is found in the first group of creating nodes, the user request fails, and when the number of creating nodes is the third condition, the processing method is similar to that described above, and is not described herein again.
As an optional implementation manner, determining the first candidate node list according to the service attribute information may include the following steps: extracting a service keyword based on the service attribute information; and determining a first candidate node list according to the corresponding relation between the service key words and the labels of each node. The correspondence between the service keyword and the tag of each node may be the same as, similar to (for example, word meaning is similar, word shape is similar, etc.) or other correspondence between the service keyword and the tag, and those skilled in the art may set the correspondence as needed. For example, when the correspondence between the service keyword and the label of each node is that the service keyword is identical to the content of the label, the label of each node in the first candidate node list must at least include the label with the keyword as the content, and so on.
As an alternative embodiment, determining the first group of created nodes according to the resource attribute information based on the first candidate node list may include the following steps: extracting resource keywords based on the resource attribute information; and determining a first group of created nodes according to the corresponding relation between the resource key words and the available resource conditions of each node based on the first candidate node list. The corresponding relationship between the resource keyword and the available resource condition of each node may be that the content of the quantity of the resource expressed by the resource keyword is the same as, similar to, or greater than or equal to the resource quantity requirement expressed by the resource keyword, or other corresponding relationships, and the like. For example, when the requirement for the storage space included in the resource key is 100G, the storage space indicated by the available resource condition of each node should be greater than or equal to 100G, and so on.
As a second specific embodiment, obtaining the service request information may include the following steps: acquiring a service attribute information expression; and acquiring resource attribute information. The process of obtaining the service attribute information expression may be to generate the service attribute information expression according to the service request information of the user, or to directly obtain the service attribute information expression from the user, which is not limited herein.
As an optional implementation manner, the determining at least one creating node according to the service request information includes the following steps: determining a second candidate node list according to the service attribute information expression; and determining a second group of creating nodes according to the resource attribute information based on the second candidate node list.
As an alternative implementation, determining the second candidate node list according to the service attribute information expression may include the following steps: extracting a service keyword expression based on the service attribute information expression; and determining a second candidate node list according to the matching relation between the business keyword expression and the label of each node. Extracting the service keyword based on the service attribute information expression may include a step of extracting the keyword according to the service attribute information expression and a step of logically connecting the extracted keyword according to the service attribute information expression, and the order of the two steps may be interchanged or even performed simultaneously in some cases. The service keyword expression may be formed by at least two service keywords connected by connecting words such as "and", "or", or "not", or may be other forms of service keyword expressions. For example, when the service keyword expression is two service keywords connected to "and", the node screened according to the service keyword expression must at least include a tag capable of matching with the two service keywords at the same time, and when the service keyword expression is two service keywords connected to "or", the nodes screened out according to the service keyword expression must contain at least one tag matching with one or two of the two service keywords, and when the service keyword expression is two service keywords connected by "not", the nodes screened according to the service keyword expression must at least include tags capable of matching the service keywords before the "not" and must not include tags matching the service keywords after the "not", and the connection words may not be limited to those mentioned above, and those skilled in the art may select the connection words as needed.
As an optional implementation manner, before determining the second candidate node list according to the service attribute information expression, the method further includes the following steps: and verifying the legality of the service attribute information expression. For example, the format of the service attribute information expression may be verified to be legal, whether the service attribute information expression includes the service attribute information that must be included in the specification may be verified, and the like, which is not limited herein.
As an alternative embodiment, determining the second group of created nodes according to the resource attribute information based on the second candidate node list may include the following steps: extracting resource keywords based on the resource attribute information; and determining a second group of created nodes according to the matching relation between the resource key words and the available resource conditions of each node based on the second candidate node list. The matching relationship between the resource keyword and the available resource condition of each node may be a requirement that the number of resources expressed by the resource keyword is the same as or similar to the number of resources expressed by the available resource condition, or the number of resources expressed by the available resource condition of each node is greater than or equal to the number of resources expressed by the resource keyword, or other matching relationships, and the like, and those skilled in the art may set the matching relationship as needed. For example, when the requirement for the storage space included in the resource key is 100G, the storage space indicated by the available resource condition of each node should be greater than or equal to 100G, and so on.
As an alternative implementation, before determining the second candidate node list according to the service keyword expression, the following steps may be included: and verifying the legality of the business keyword expression. For example, the format of the service keyword expression may be verified to be legal, whether the service keyword expression includes a service keyword that must be included in the specification may be verified, and the like, which is not limited herein.
In the above embodiments and specific examples, it is only one of the embodiments that the first or second candidate node list is determined according to the service attribute information, and then the first group or second group of created nodes is determined according to the resource attribute information based on the first or second candidate node list, and the two steps may also be interchanged, that is, the first or second candidate node list is determined according to the resource attribute information, and then the first group or second group of created nodes is determined according to the service attribute information based on the first or second candidate node list, which is not limited herein.
As a third specific embodiment, obtaining the service request information may include the following steps: acquiring a service request information expression; determining at least one creating node according to the service request information may include the steps of: and determining a third group of creating nodes according to the service request information expression. The form of the obtained service request information is directly a service request information expression, and the service request information expression simultaneously contains service attribute information, resource attribute information and other related information. And determining a third group of creation nodes directly according to the service request information expression.
As an optional implementation manner, determining the third group of creating nodes according to the service request information expression may include the following steps: extracting a service request keyword expression based on the service request information expression; and determining a third group of creation nodes according to the matching relation between the business request keyword expression and the label and available resource condition of each node. Extracting the service request keyword expression based on the service request information expression may include a step of extracting a keyword according to the service request information expression and a step of connecting the extracted keywords according to the service request information expression, and the order of the two steps may be interchanged or even performed simultaneously in some cases. The method for determining the third group of created nodes according to the matching relationship between the keyword expression of the service request and the label and available resource condition of each node is similar to the method for determining the nodes according to the matching relationship between the keyword expression and the label of the node, and is not repeated here.
As a specific example, when the service request information is: 1) two different exclusive users are supported, and all resources between the different users require isolation (AZ level); 2) each user requires two services of RDS (database service) and NVS (general cloud host); 3) each service requires the provision of high availability across AZ levels, i.e. two fault isolation domains. In the scheduling mode based on AZ, we need to deploy according to the scheme shown in fig. 3(a), at least 8 azis are needed to meet the requirements of two exclusive users, two services, and two fault isolation domains for each service, if there are more customers, with more service requirements, or with more fault isolation domains, the number of azis will increase dramatically, and nodes between the azis cannot be mutually complemented, and the condition of uneven resource usage will inevitably occur. As shown in fig. 3(b), which is a schematic diagram of a specific embodiment of a cloud computing cluster resource scheduling method according to the present application, according to the technical solution of the present application, fewer AZ may be used, and the following advantages are provided: a) two services for the same user do not have AZ isolation requirements (but still need to be on different compute nodes, e.g. with differences in storage). In the AZ scheduling scheme, we must also partition different azis to schedule the cloud hosts of different services onto different compute nodes. Based on node scheduling, the two services can be deployed simultaneously in the same AZ, so that the number of AZs is reduced. In fact, the nodes are various, such as over-sale ratio, physical devices and the like, and the advantages of the technical scheme of the application are more obvious under the condition that various user requests are superposed; b) if the user requires to continue to increase the service types, the following can be easily met: adding nodes in the existing AZ and marking the nodes as new service nodes; c) because various different nodes can be scheduled in one AZ, various resources can be balanced with less force, the utilization rate of the resources is improved, and the operation cost is reduced.
Therefore, aiming at overcoming the defects of the existing scheduling scheme based on AZ, the scheduling method and the scheduling device for cloud computing cluster resources based on the nodes are provided, so that the resource utilization rate is improved, the operation cost is reduced, the operation and maintenance are friendly, the elastic expansion capability of the cloud resources is improved, and better experience is brought to users.
Exemplary Medium
Having described the cloud computing cluster resource scheduling method according to an exemplary embodiment of the present invention, a computer-readable storage medium according to an exemplary embodiment of the present invention will be described with reference to fig. 4.
In some possible embodiments, aspects of the present invention may also be implemented as a computer-readable storage medium storing a program product, which when run on a terminal device, is configured to cause the terminal device to perform the steps of the cloud computing cluster resource scheduling method according to various exemplary embodiments of the present invention described in the section "exemplary method" above in this specification.
The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
As shown in fig. 4, a program product 400 of a cloud computing cluster resource scheduling method according to an embodiment of the present invention is described. Which may employ a portable compact disc read only memory (CD-ROM) and include program code that is executable on a terminal device, such as a personal computer. However, the program product of the present invention is not limited in this regard and, in the present document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A readable signal medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + +, or the like, as well as conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, or entirely on a remote computing device or server. In situations involving remote computing devices, the remote computing devices may be connected to the user computing device over any kind of network, including a local area network or a wide area network, or may be connected to external computing devices (e.g., over the internet using an internet service provider).
Exemplary devices
Having described the computer-readable storage medium of an exemplary embodiment of the present invention, a cloud computing cluster resource scheduling apparatus of an exemplary embodiment of the present invention is next described with reference to fig. 5.
Fig. 5 is a schematic structural diagram of a cloud computing cluster resource scheduling apparatus according to an embodiment of the present application, including: the controller is used for acquiring service request information; a creating node determining module, configured to determine at least one creating node according to the service request information; the controller is also configured to schedule the creation node for creating a cloud host.
Optionally, the creating node determining module includes: the node label management unit is used for adding labels to each node based on the service isolation attribute information of each node; and the node resource management unit is used for acquiring the available resource condition of each node.
Optionally, the service request information includes: service attribute information and resource attribute information.
Optionally, the node tag management unit is further configured to determine a first candidate node list according to the service attribute information;
the node resource management unit is further configured to determine a first set of created nodes according to the resource attribute information based on the first candidate node list.
Optionally, the node tag management unit is further configured to; extracting a service keyword based on the service attribute information; and determining a first candidate node list according to the corresponding relation between the service key words and the labels of each node.
Optionally, the node resource management unit is further configured to: extracting resource keywords based on the resource attribute information; and determining a first group of created nodes according to the corresponding relation between the resource key words and the labels of each node based on the first candidate node list.
Optionally, the controller is further configured to: acquiring a service attribute information expression; and acquiring resource attribute information.
Optionally, the node tag management unit is further configured to determine a second candidate node list according to the service attribute information expression; the node resource management unit is further configured to determine a second set of created nodes according to the resource attribute information based on the second candidate node list.
Optionally, the controller is further configured to verify the validity of the service attribute information expression.
Optionally, the node tag management unit is further configured to: extracting a service keyword expression based on the service attribute information expression; and determining a second candidate node list according to the matching relation between the business keyword expression and the label of each node.
Optionally, the node resource management unit is further configured to: extracting resource keywords based on the resource attribute information; and determining a second group of created nodes according to the matching relation between the resource key words and the labels of each node based on the second candidate node list.
Optionally, the controller is further configured to verify the validity of the service keyword expression.
Optionally, the controller is further configured to obtain a service request information expression;
the creating node determining module is further configured to determine a third group of creating nodes according to the service request information expression.
Optionally, the node tag management unit is further configured to extract a service request keyword expression based on the service request information; and the node resource management unit is also used for determining a third group of created nodes according to the matching relation between the business request keyword expression and the label of each node.
Exemplary computing device
Having described the cloud computing cluster resource scheduling method, medium, and apparatus of exemplary embodiments of the present invention, a computing device of an exemplary embodiment of the present invention is described next with reference to fig. 6.
As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or program product. Thus, various aspects of the invention may be embodied in the form of: an entirely hardware embodiment, an entirely software embodiment (including firmware, microcode, etc.) or an embodiment combining hardware and software aspects that may all generally be referred to herein as a "circuit," module "or" system.
In some possible embodiments, a computing device of a cloud computing cluster resource scheduling method according to the present invention may include at least one processor and at least one memory. Wherein the memory stores program code that, when executed by the processor, causes the processor to perform the steps of the cloud computing cluster resource scheduling method according to various exemplary embodiments of the present invention described in the "exemplary methods" section above in this specification.
A computing device 600 of the cloud computing cluster resource scheduling method according to this embodiment of the present invention is described below with reference to fig. 6. The computing device 600 of the cloud computing cluster resource scheduling method shown in fig. 6 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.
As shown in fig. 6, the computing device 600 of the cloud computing cluster resource scheduling method is represented in the form of a general-purpose computing device. The components of the computing device 600 of the cloud computing cluster resource scheduling method may include, but are not limited to: the at least one processor 601, the at least one memory 602, and a bus 603 that connects the various system components (including the processor 601 and the memory 602).
Bus 603 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures.
The memory 602 may include readable media in the form of volatile memory, such as Random Access Memory (RAM)6021 and/or cache memory 6022, and may further include read-only memory 6023.
The memory 602 may also include a program/utility 6025 having a set (at least one) of program modules 6024 that include, but are not limited to: an operating system, one or more application programs, other program modules, and program data, each of which, and in some combination, may comprise an implementation of a network environment.
The computing device 600 of the cloud computing cluster resource scheduling method may also communicate with one or more external devices 604 (e.g., keyboard, pointing device, bluetooth device, etc.), with one or more devices that enable a user to interact with the computing device 600 of the cloud computing cluster resource scheduling method, and/or with any device (e.g., router, modem, etc.) that enables the computing device 600 of the cloud computing cluster resource scheduling method to communicate with one or more other computing devices. Such communication may occur via input/output (I/O) interfaces 605. Moreover, the computing devices of the cloud computing cluster resource scheduling method may also communicate with one or more networks (e.g., local area networks, wide area networks, etc.) through the network adapter 606. As shown, the network adapter 606 communicates over a bus with other modules of the computing device 600 of the cloud computing cluster resource scheduling method. It should be appreciated that, although not shown in the figures, other hardware and/or software modules may be used in connection with the computing device of the cloud computing cluster resource scheduling method, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.
It should be noted that although in the above detailed description several units/modules or sub-units/modules of the cloud computing cluster resource scheduler are mentioned, such a division is merely exemplary and not mandatory. Indeed, the features and functionality of two or more of the units/modules described above may be embodied in one unit/module according to embodiments of the invention. Conversely, the features and functions of one unit/module described above may be further divided into embodiments by a plurality of units/modules.
Moreover, while the operations of the method of the invention are depicted in the drawings in a particular order, this does not require or imply that the operations must be performed in this particular order, or that all of the illustrated operations must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions.
While the spirit and principles of the invention have been described with reference to several particular embodiments, it is to be understood that the invention is not limited to the disclosed embodiments, nor is the division of aspects, which is for convenience only as the features in such aspects may not be combined to benefit. The invention is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.
According to the above description of the embodiments, the present application provides the following technical solutions:
scheme 1. a cloud computing cluster resource scheduling method, comprising the following steps:
acquiring service request information;
determining at least one creating node according to the service request information;
scheduling the creation node for creating a cloud host.
Scheme 2. the method according to scheme 1, wherein before the obtaining the service request information, further comprising the steps of:
adding a label to each node based on the service isolation attribute information of each node;
and collecting the available resource condition of each node.
Scheme 3. the method of scheme 2, wherein the service request information comprises:
service attribute information and resource attribute information.
Scheme 4. the method of scheme 3, wherein said determining at least one create node based on said service request information comprises the steps of:
determining a first candidate node list according to the service attribute information;
determining a first set of created nodes from the resource attribute information based on the first list of candidate nodes.
Scheme 5. the method of scheme 4, wherein said determining a first list of candidate nodes based on said service attribute information comprises the steps of:
extracting a service keyword based on the service attribute information;
and determining a first candidate node list according to the corresponding relation between the service key words and the label of each node.
Scheme 6. the method of scheme 4 or 5, wherein said determining a first set of created nodes from the resource attribute information based on the first candidate node list comprises:
extracting resource keywords based on the resource attribute information;
and determining a first group of created nodes according to the corresponding relation between the resource key words and the labels of each node based on the first candidate node list.
Scheme 7. the method of scheme 3, wherein the obtaining service request information comprises the steps of:
acquiring a service attribute information expression; and
and acquiring resource attribute information.
Scheme 8. the method of scheme 7, wherein said determining at least one create node based on said service request information comprises the steps of:
determining a second candidate node list according to the service attribute information expression;
determining a second set of created nodes from the resource attribute information based on the second candidate node list.
Scheme 9. the method according to scheme 8, wherein before said determining a second list of candidate nodes according to said service attribute information expression, further comprising the steps of:
and verifying the legality of the service attribute information expression.
Scheme 10. the method of scheme 8 or 9, wherein said determining a second list of candidate nodes according to said service attribute information expression comprises the steps of:
extracting a service keyword expression based on the service attribute information expression;
and determining a second candidate node list according to the matching relation between the service keyword expression and the label of each node.
Scheme 11. the method of any of schemes 8-10, wherein the determining a second set of created nodes from the resource attribute information based on the second list of candidate nodes comprises:
extracting resource keywords based on the resource attribute information;
and determining a second group of created nodes according to the matching relation between the resource key words and the labels of each node based on the second candidate node list.
Scheme 12. the method according to any of the schemes 10 or 11, wherein before said determining a second list of candidate nodes according to the service keyword expression comprises the steps of:
and verifying the legality of the service keyword expression.
Scheme 13 the method of scheme 2, wherein,
the acquiring the service request information comprises the following steps: acquiring a service request information expression;
the determining at least one creation node according to the service request information comprises the following steps: and determining a third group of creating nodes according to the service request information expression.
Scheme 14. the method of scheme 13, wherein said determining a third set of creating nodes according to said service request information expression comprises the steps of:
extracting a service request keyword expression based on the service request information expression;
and determining a third group of creation nodes according to the matching relation between the business request keyword expression and the label of each node.
Scheme 15 a computer readable storage medium storing program code which, when executed by a processor, implements a method as in one of schemes 1-14.
The scheme 16. a cloud computing cluster resource scheduling device, comprising:
the controller is used for acquiring service request information;
a creating node determining module, configured to determine at least one creating node according to the service request information;
the controller is further configured to schedule the creation node for creating a cloud host.
The apparatus of aspect 16, wherein the create node determining means comprises:
the node label management unit is used for adding labels to each node based on the service isolation attribute information of each node;
and the node resource management unit is used for acquiring the available resource condition of each node.
Scheme 18. the apparatus of scheme 17, wherein the service request information comprises:
service attribute information and resource attribute information.
The apparatus of claim 18, wherein,
the node label management unit is further used for determining a first candidate node list according to the service attribute information;
the node resource management unit is further configured to determine a first group of created nodes according to the resource attribute information based on the first candidate node list.
Scheme 20. the apparatus of scheme 19, wherein the node tag management unit is further configured to;
extracting a service keyword based on the service attribute information;
and determining a first candidate node list according to the corresponding relation between the service key words and the label of each node.
Scheme 21. the apparatus of scheme 19 or 20, wherein the node resource management unit is further configured to:
extracting resource keywords based on the resource attribute information;
and determining a first group of created nodes according to the corresponding relation between the resource key words and the labels of each node based on the first candidate node list.
The apparatus of aspect 18, wherein the controller is further configured to:
acquiring a service attribute information expression; and
and acquiring resource attribute information.
Scheme 23. the apparatus of scheme 22, wherein,
the node label management unit is also used for determining a second candidate node list according to the service attribute information expression;
the node resource management unit is further configured to determine a second group of created nodes according to the resource attribute information based on the second candidate node list.
The apparatus of claim 24, wherein the controller is further configured to,
and verifying the legality of the service attribute information expression.
Scheme 25. the apparatus of scheme 23 or 24, wherein the node tag management unit is further configured to:
extracting a service keyword expression based on the service attribute information expression;
and determining a second candidate node list according to the matching relation between the service keyword expression and the label of each node.
Scheme 26. the apparatus of any of schemes 23-25, wherein the node resource managing unit is further configured to:
extracting resource keywords based on the resource attribute information;
and determining a second group of created nodes according to the matching relation between the resource key words and the labels of each node based on the second candidate node list.
The apparatus of any of aspects 25 or 26, wherein the controller is further configured to,
and verifying the legality of the service keyword expression.
Scheme 28. the apparatus of scheme 17, wherein,
the controller is also used for acquiring a service request information expression;
the creating node determining module is further configured to determine a third group of creating nodes according to the service request information expression.
Scheme 29. the apparatus of scheme 28, wherein,
the node label management unit is also used for extracting a service request keyword expression based on the service request information;
and the node resource management unit is further used for determining a third group of created nodes according to the matching relation between the business request keyword expression and the label of each node.
Scheme 30. a computing device comprising a processor and a storage medium storing program code which, when executed by the processor, implements a method as in one of schemes 1-14.

Claims (22)

1. A cloud computing cluster resource scheduling method comprises the following steps:
adding a label for each node based on the service isolation attribute information of each node, wherein the label types established according to the service isolation attribute comprise a user type, a service type, a copy domain and an over-sale ratio;
collecting the available resource condition of each node;
acquiring service request information, wherein the service request information comprises service attribute information and resource attribute information;
determining at least one creating node according to the service request information, wherein the service attribute information comprises service isolation attribute requirements for the creating node, and the service isolation attribute information comprises the following steps:
determining a first candidate node list according to the service attribute information and the label, wherein the first candidate node list comprises:
extracting a service keyword based on the service isolation attribute requirement, wherein the service isolation attribute requirement comprises: one or a combination of a user type, a service type, a copy domain and a super sale rate;
determining a first candidate node list according to the corresponding relation between the service key words and the label of each node;
determining a first group of created nodes according to the resource attribute information based on the first candidate node list and the available resource condition of each node;
scheduling the creation node for creating a cloud host.
2. The method of claim 1, wherein said determining a first set of created nodes from the resource attribute information based on the first candidate node manifest comprises:
extracting resource keywords based on the resource attribute information;
and determining a first group of created nodes according to the corresponding relation between the resource key words and the labels of each node based on the first candidate node list.
3. The method of claim 1, wherein the obtaining service request information comprises:
acquiring a service attribute information expression; and
and acquiring resource attribute information.
4. The method of claim 3, wherein the determining at least one creating node according to the service request information comprises:
determining a second candidate node list according to the service attribute information expression;
determining a second set of created nodes from the resource attribute information based on the second candidate node list.
5. The method of claim 4, wherein prior to said determining a second list of candidate nodes according to said service attribute information expression, further comprising the steps of:
and verifying the legality of the service attribute information expression.
6. The method according to claim 4 or 5, wherein said determining a second list of candidate nodes according to said service attribute information expression comprises the steps of:
extracting a service keyword expression based on the service attribute information expression;
and determining a second candidate node list according to the matching relation between the service keyword expression and the label of each node.
7. The method according to any of claims 4-6, wherein said determining a second set of created nodes from said resource attribute information based on said second list of candidate nodes comprises the steps of:
extracting resource keywords based on the resource attribute information;
and determining a second group of created nodes according to the matching relation between the resource key words and the labels of each node based on the second candidate node list.
8. The method according to any of claims 6 or 7, wherein prior to said determining a second list of candidate nodes according to said traffic keyword expression comprises the steps of:
and verifying the legality of the service keyword expression.
9. The method of claim 1, wherein,
the acquiring the service request information comprises the following steps: acquiring a service request information expression;
the determining at least one creation node according to the service request information comprises the following steps: and determining a third group of creating nodes according to the service request information expression.
10. The method of claim 9, wherein said determining a third set of creating nodes according to said service request information expression comprises:
extracting a service request keyword expression based on the service request information expression;
and determining a third group of creation nodes according to the matching relation between the business request keyword expression and the label of each node.
11. A computer-readable storage medium storing program code which, when executed by a processor, implements a method according to one of claims 1 to 10.
12. A cloud computing cluster resource scheduling apparatus, comprising:
the node label management unit is used for adding labels to each node based on the service isolation attribute information of each node, and the label types established according to the service isolation attribute comprise user types, service types, copy domains and over-sale ratios;
a node resource management unit for collecting the available resource condition of each node
The controller is used for acquiring service request information, and the service request information comprises service attribute information and resource attribute information;
a create node determining module, configured to determine at least one create node according to the service request information, where the service attribute information includes a service isolation attribute requirement for the create node, and the node tag management unit is further configured to determine a first candidate node list according to the service attribute information and the tag, where the method includes:
extracting a service keyword based on the service isolation attribute requirement, wherein the service isolation attribute requirement comprises: one or a combination of a user type, a service type, a copy domain and a super sale rate;
determining a first candidate node list according to the corresponding relation between the service key words and the label of each node;
the node resource management unit is further configured to determine a first group of created nodes according to the resource attribute information based on the first candidate node list and the available resource condition of each node;
the controller is further configured to schedule the creation node for creating a cloud host.
13. The apparatus of claim 12, wherein the node resource management unit is further configured to:
extracting resource keywords based on the resource attribute information;
and determining a first group of created nodes according to the corresponding relation between the resource key words and the labels of each node based on the first candidate node list.
14. The apparatus of claim 12, wherein the controller is further configured to:
acquiring a service attribute information expression; and
and acquiring resource attribute information.
15. The apparatus of claim 14, wherein,
the node label management unit is also used for determining a second candidate node list according to the service attribute information expression;
the node resource management unit is further configured to determine a second group of created nodes according to the resource attribute information based on the second candidate node list.
16. The apparatus of claim 15, wherein the controller is further configured to,
and verifying the legality of the service attribute information expression.
17. The apparatus of claim 15 or 16, wherein the node tag management unit is further configured to:
extracting a service keyword expression based on the service attribute information expression;
and determining a second candidate node list according to the matching relation between the service keyword expression and the label of each node.
18. The apparatus of any of claims 15-17, wherein the node resource management unit is further configured to:
extracting resource keywords based on the resource attribute information;
and determining a second group of created nodes according to the matching relation between the resource key words and the labels of each node based on the second candidate node list.
19. The apparatus of any one of claims 17 or 18, wherein the controller is further configured to,
and verifying the legality of the service keyword expression.
20. The apparatus of claim 12, wherein,
the controller is also used for acquiring a service request information expression;
the creating node determining module is further configured to determine a third group of creating nodes according to the service request information expression.
21. The apparatus of claim 20, wherein,
the node label management unit is also used for extracting a service request keyword expression based on the service request information;
and the node resource management unit is further used for determining a third group of created nodes according to the matching relation between the business request keyword expression and the label of each node.
22. A computing device comprising a processor and a storage medium storing program code which, when executed by the processor, implements the method of one of claims 1 to 10.
CN201811114998.2A 2018-09-25 2018-09-25 Cloud computing cluster resource scheduling method, medium, device and computing equipment Active CN109358965B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201811114998.2A CN109358965B (en) 2018-09-25 2018-09-25 Cloud computing cluster resource scheduling method, medium, device and computing equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201811114998.2A CN109358965B (en) 2018-09-25 2018-09-25 Cloud computing cluster resource scheduling method, medium, device and computing equipment

Publications (2)

Publication Number Publication Date
CN109358965A CN109358965A (en) 2019-02-19
CN109358965B true CN109358965B (en) 2022-01-11

Family

ID=65351435

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201811114998.2A Active CN109358965B (en) 2018-09-25 2018-09-25 Cloud computing cluster resource scheduling method, medium, device and computing equipment

Country Status (1)

Country Link
CN (1) CN109358965B (en)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112714146B (en) * 2019-10-25 2023-01-13 中国移动通信有限公司研究院 Resource scheduling method, device, equipment and computer readable storage medium
CN112887353B (en) * 2019-11-29 2024-01-23 中国移动通信有限公司研究院 Information processing method, device, terminal and storage medium
CN111866054A (en) * 2019-12-16 2020-10-30 北京小桔科技有限公司 Cloud host building method and device, electronic equipment and readable storage medium
CN111200658A (en) * 2020-01-06 2020-05-26 紫光云技术有限公司 Direct connection distribution method for PCI (peripheral component interconnect) equipment of cloud host
CN113344311A (en) * 2020-03-03 2021-09-03 北京国双科技有限公司 Task execution method and device, storage medium, processor and electronic equipment
CN113810438B (en) * 2020-06-12 2023-05-23 中国移动通信有限公司研究院 Service computing resource scheduling and requesting method, node equipment and terminal
CN116112497A (en) * 2022-12-29 2023-05-12 天翼云科技有限公司 Node scheduling method, device, equipment and medium of cloud host cluster

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106101074A (en) * 2016-05-31 2016-11-09 北京大学 A kind of sacurity dispatching method based on user's classification towards big data platform
CN107241421A (en) * 2017-06-21 2017-10-10 北京云联万维技术有限公司 A kind of cloud host resource method for obligating and device

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102722413B (en) * 2012-05-16 2017-12-29 上海兆民云计算科技有限公司 The distributed resource scheduling method that a kind of desktop cloud cluster uses
CN103414739B (en) * 2013-06-19 2016-09-07 中金数据系统有限公司 Use Cloud Server automatic monitored control system and the method for automatic drift
US9699085B2 (en) * 2014-11-13 2017-07-04 Cisco Technology, Inc. Periodic advertisements of host capabilities in virtual cloud computing infrastructure
CN107515773A (en) * 2016-06-16 2017-12-26 北京易讯通信息技术股份有限公司 A kind of method that virtual machine is quickly created based on Openstack
CN108076112A (en) * 2016-11-15 2018-05-25 北京金山云网络技术有限公司 A kind of host dispatching method and device
CN108540510B (en) * 2017-03-02 2021-11-05 北京金山云网络技术有限公司 Cloud host creation method and device and cloud service system
CN107506145B (en) * 2017-08-28 2020-06-16 浪潮云信息技术有限公司 Physical storage scheduling method and cloud host creation method
CN108023930A (en) * 2017-10-25 2018-05-11 中电科华云信息技术有限公司 A kind of resource dynamic dispatching method and system based on SLA
CN108429768A (en) * 2018-05-29 2018-08-21 新华三云计算技术有限公司 Cloud data analysis service manages system, method and cloud server

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106101074A (en) * 2016-05-31 2016-11-09 北京大学 A kind of sacurity dispatching method based on user's classification towards big data platform
CN107241421A (en) * 2017-06-21 2017-10-10 北京云联万维技术有限公司 A kind of cloud host resource method for obligating and device

Also Published As

Publication number Publication date
CN109358965A (en) 2019-02-19

Similar Documents

Publication Publication Date Title
CN109358965B (en) Cloud computing cluster resource scheduling method, medium, device and computing equipment
US11442764B2 (en) Optimizing the deployment of virtual resources and automating post-deployment actions in a cloud environment
CN108537543B (en) Parallel processing method, device, equipment and storage medium for blockchain data
US9712535B1 (en) Security recommendation engine
US9413604B2 (en) Instance host configuration
CN101930449B (en) Client, brokerage server and method for providing cloud storage
US10116732B1 (en) Automated management of resource attributes across network-based services
KR20200027413A (en) Method, device and system for storing data
US11328073B1 (en) Robust data tagging
US11294758B2 (en) Automated methods and systems to classify and troubleshoot problems in information technology systems and services
AU2014209611B2 (en) Instance host configuration
US8966025B2 (en) Instance configuration on remote platforms
US20190199785A1 (en) Determining server level availability and resource allocations based on workload level availability requirements
CN102938784A (en) Method and system used for data storage and used in distributed storage system
US10025630B2 (en) Operating programs on a computer cluster
US10713265B2 (en) Methods and systems to quantize and compress time series data
US10243819B1 (en) Template generation based on analysis
US9176710B2 (en) Dynamically selecting service provider, computing system, computer, and program
US10154091B1 (en) Deploying infrastructure units according to resource hosting constraints
US9438529B1 (en) Computing process analysis by metrics profiling
CN113204345A (en) Page generation method and device, electronic equipment and storage medium
CN114039919A (en) Traffic scheduling method, medium, device and computing equipment
US10657230B2 (en) Analysis of output files
US11159402B1 (en) Virtual machine import/export risk assessment
CN113204425A (en) Method and device for process management internal thread, electronic equipment and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant
CP01 Change in the name or title of a patent holder

Address after: 310052 Room 301, Building No. 599, Changhe Street Network Business Road, Binjiang District, Hangzhou City, Zhejiang Province

Patentee after: Hangzhou NetEase Shuzhifan Technology Co.,Ltd.

Address before: 310052 Room 301, Building No. 599, Changhe Street Network Business Road, Binjiang District, Hangzhou City, Zhejiang Province

Patentee before: HANGZHOU LANGHE TECHNOLOGY Ltd.

CP01 Change in the name or title of a patent holder