CN113301082A

CN113301082A - Resource management method, device, system and storage medium

Info

Publication number: CN113301082A
Application number: CN202010575628.XA
Authority: CN
Inventors: 林超
Original assignee: Alibaba Group Holding Ltd
Current assignee: Alibaba Group Holding Ltd
Priority date: 2020-06-22
Filing date: 2020-06-22
Publication date: 2021-08-24
Anticipated expiration: 2040-06-22
Also published as: CN113301082B

Abstract

The embodiment of the application provides a resource management method, equipment, a system and a storage medium. In the embodiment of the application, the plurality of edge cloud nodes comprise a plurality of resource objects, the plurality of resource objects provide a plurality of resources, the resource management node can divide the attribute description information of the plurality of resources provided by the plurality of resource objects into the first type of attribute description information and the second type of attribute description information, and store the first type of attribute description information and the second type of attribute description information in a classified manner, so that the structure and the type of hardware resources and software resources of the resource objects do not need to be concerned, the uniform management of heterogeneous resources is realized, and the management complexity is further reduced.

Description

Resource management method, device, system and storage medium

Technical Field

The present application relates to the field of cloud computing technologies, and in particular, to a resource management method, device, system, and storage medium.

Background

The traditional cloud computing adopts a centralized Data Center (DC) mode and has strong computing power. However, a great number of emerging mobile and internet of things device applications are emerging, and the cloud computing mode relying on the centralized DC can not meet the requirements of users well. In order to solve the problems of centralized cloud computing, edge cloud computing is carried out.

The edge cloud is composed of edge nodes distributed in the same region, particularly processes service requests of local users, and can quickly and flexibly provide cloud computing services for the users. However, not only the hardware configuration but also the software resources are diverse for the edge nodes. The management of these heterogeneous resources becomes a technical problem to be solved urgently in the edge cloud technology.

Disclosure of Invention

Various aspects of the present disclosure provide a resource management method, device, system, and storage medium, which are used to uniformly manage heterogeneous resources and help reduce the complexity of resource users.

An embodiment of the present application provides a network system, including: the system comprises a resource management node and a plurality of edge cloud nodes; the plurality of edge cloud nodes comprises a plurality of resource objects; the plurality of resource objects are for providing a plurality of resources;

the resource management node is configured to: acquiring attribute description information of a plurality of resources provided by the plurality of resource objects; classifying the attribute description information of the plurality of resources to obtain first class attribute description information and second class attribute description information; and classifying and storing the first type attribute description information and the second type attribute description information.

An embodiment of the present application further provides a resource management method, including:

acquiring attribute description information of a plurality of resources provided by a plurality of resource objects; wherein the plurality of resource objects are formed based on a plurality of edge cloud nodes;

classifying the attribute description information of the plurality of resources to obtain first class attribute description information and second class attribute description information;

and classifying and storing the first type attribute description information and the second type attribute description information.

An embodiment of the present application further provides a computer device, including: a memory and a processor; wherein the memory is used for storing a computer program;

the processor is coupled to the memory for executing the computer program for performing the steps in the above-described resource management method.

Embodiments of the present application also provide a computer-readable storage medium storing computer instructions, which, when executed by one or more processors, cause the one or more processors to perform the steps of the above-mentioned resource management method.

In the embodiment of the application, the plurality of edge cloud nodes comprise a plurality of resource objects, the plurality of resource objects provide a plurality of resources, the resource management node can divide the plurality of resources provided by the plurality of resource objects into the first type of attribute description information and the second type of attribute description information, and store the first type of attribute description information and the second type of attribute description information in a classified manner without concerning the structures and types of hardware resources and software resources of the resource objects, so that the uniform management of heterogeneous resources is realized, and the management complexity is further reduced.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:

fig. 1a is a schematic structural diagram of a network system according to an embodiment of the present application;

fig. 1b is a schematic structural diagram of a city cloud system provided in an embodiment of the present application;

fig. 1c is a schematic structural diagram of a data storage format according to an embodiment of the present application;

fig. 2 is a schematic flowchart of a resource management method according to an embodiment of the present application;

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

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail and completely with reference to the following specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

For edge nodes, not only the hardware structure is very different, but also the software resources are various. The management of these heterogeneous resources becomes a technical problem to be solved urgently in the edge cloud technology. In order to realize management of heterogeneous resources, in the embodiment of the application, a plurality of edge cloud nodes can provide a plurality of resources, and a resource management node can divide attribute description information of the plurality of resources provided by the plurality of edge cloud nodes into first-class attribute description information and second-class attribute description information and store the first-class attribute description information and the second-class attribute description information in a classified manner, so that the structure and the type of hardware resources and software resources of a resource object do not need to be concerned, unified management of the heterogeneous resources is realized, and further, the management complexity is favorably reduced.

The technical solutions provided by the embodiments of the present application are described in detail below with reference to the accompanying drawings.

It should be noted that: like reference numerals refer to like objects in the following figures and embodiments, and thus, once an object is defined in one figure or embodiment, further discussion thereof is not required in subsequent figures and embodiments.

Fig. 1a is a schematic structural diagram of a network system according to an embodiment of the present application. As shown in fig. 1a, the network system includes: a resource management node 11 and a plurality of edge cloud nodes 12. Plural means 2 or more.

The network system of the embodiment belongs to the category of edge clouds. The edge cloud is a cloud computing platform constructed on an edge infrastructure based on cloud computing technology and edge computing capability, and is a cloud platform with computing, network, storage, security and other capabilities at an edge position. The edge cloud is a cloud computing platform relatively close to the terminal, or is different from a central cloud or a traditional cloud computing platform, the central cloud or the traditional cloud computing platform may include a data center or a computer room with large-scale resources and centralized positions, the edge cloud is composed of a plurality of edge cloud nodes, the resource scale of a single edge cloud node 12 is small, but the number of the edge cloud nodes 12 is large, so that the coverage of the edge cloud is wider. In other words, the network system of the present embodiment is also a cloud computing platform constructed on an edge infrastructure based on cloud computing technology and the capability of edge computing, and is a network system constructed based on an infrastructure between a central cloud or a conventional cloud computing system and a terminal. The terminal related to this embodiment refers to a demand end of the cloud computing service, and may be, for example, a terminal or a user end in the internet or a terminal or a user end in the internet of things.

Optionally, the network system of this embodiment, a central network such as a central cloud or a conventional cloud computing platform, and a terminal are combined to form a "cloud-edge-end-three-body cooperation" network architecture, in the network architecture, tasks such as network forwarding, storage, computation, and intelligent data analysis may be placed in each edge cloud node 12 in the network system for processing, and as each edge cloud node 12 is closer to the terminal, response delay may be reduced, pressure on the central cloud or the conventional cloud computing platform may be reduced, and bandwidth cost may be reduced. Alternatively, the network system of this embodiment may also be directly combined with the terminal to form a "frontend-collaborative" network architecture. Alternatively, the network system of this embodiment may also be combined with a Mobile Edge Cloud (MEC) node, a data center, and other networks and terminals in a Mobile communication network or a Mobile communication network to form a "Cloud network cooperation" network architecture.

The network system of the present embodiment includes a plurality of edge cloud nodes 12, each edge cloud node 12 including a series of edge infrastructures including, but not limited to: a distributed Data Center (DC), a wireless room or cluster, an edge device such as a communication network of an operator, a core network device, a base station, an edge gateway, a home gateway, a computer device or a storage device, a corresponding network environment, and the like. It is noted that the location, capabilities, and infrastructure involved of different edge cloud nodes 12 may or may not be the same.

In this embodiment, a plurality of edge cloud nodes 12 may belong to the same edge available domain or may belong to different edge available domains. The coverage and the position of the edge usable field are not limited by the embodiment of the application. Alternatively, the edge available domain may be defined in units of administrative areas, for example, the edge cloud nodes 12 in one administrative area may be defined as one edge available domain, where the administrative area may be an area at various administrative division levels of province, city, county, etc. For example, an edge cloud node in a provincial administrative district may be defined as an edge available domain, an edge cloud node in an urban administrative district may be defined as an edge available domain, and so on. In addition, the edge available domain may be defined in units of cities, for example, the edge cloud nodes 12 in one city may be defined as one edge available domain, the edge cloud nodes 12 in several adjacent cities may be defined as one edge available domain, and so on.

On the basis of the edge available domain 12, the network system of the embodiment can implement localization or localization of cloud computing, is implemented as a cloud system in a localized or localized service scenario, belongs to an edge cloud computing form in a service localized or localized service scenario, and is a new edge cloud form. According to the coverage, location, etc. of the edge available domain, the cloud system in the localized or localized service scenario realized by the network system of this embodiment has different forms. For example, if the coverage of the edge available domain is in units of cities, that is, one edge available domain covers one or more adjacent cities, the network system of the embodiment may be implemented as a city cloud system, as shown in fig. 1 b. In the city cloud system shown in fig. 1B, the city cloud system includes a city a and a city B as an example, but is not limited thereto. Optionally, in this embodiment, the plurality of edge cloud nodes 12 in fig. 1a may be edge cloud nodes in a city a or a city B. The localized or localized service scene means that terminals or users of the cloud computing service are scattered in a local area or a certain specific area, the cloud computing service does not need to be deployed in the whole network, and only the application scene of the cloud computing service is deployed in the local area or the specific area.

On the basis of the edge available domain, the service demander can use the edge available domain as a service deployment unit, and can deploy the required cloud computing service in one or more edge available domains, so as to realize the localization or localization of the cloud computing service. In the embodiment of the present application, the cloud computing service is not limited, and may be, for example and without limitation: an online live broadcast service, an online education service, an online shopping service, an online game service, a mailbox service, a VR service, or the like.

In this embodiment, the central control node 13 uses the resource objects formed by the edge cloud nodes 12 as control objects, and can perform unified control on each resource object in aspects of resource scheduling, mirror image management, instance control, operation and maintenance, network, security, and the like, so as to place the cloud computing service into each resource object for processing. In terms of deployment implementation, the central management and control node 13 may be deployed in one or more cloud computing data centers, or may be deployed in one or more conventional data centers, or the central management and control node 13 may also be deployed in the network system of this embodiment, and forms the network system of this embodiment together with the resource management node 11 and the edge cloud node 12, which is not limited in this embodiment.

Optionally, the central management and control node 13 may manage and control the cloud computing service provided by the edge available domain in a time-sharing manner. For example, the central management and control node 13 may control the available edge domain to provide services such as live video (e.g., remote education) or audio-video communication (e.g., audio-video conference) during the daytime, and the central management and control node 13 may control the available edge domain to provide services such as video-on-demand or games during the nighttime; and so on. Alternatively, the central management and control node 13 may allocate resources provided by the edge available domain to the cloud computing service according to the service type. For example, the central management and control node 13 may allocate more computing resources, network resources, and the like to cloud computing services with higher real-time requirements (e.g., live video, audio and video communication, and the like); cloud computing services with relatively low real-time requirements (e.g., mail, etc.) provide fewer computing resources, network resources, etc.

Further, the network system of this embodiment, as an edge cloud computing form using a service localization or localization service scenario, requires that an edge available domain has higher stability, and also needs to ensure availability of cloud computing services deployed in the edge available domain. Based on this, in the present embodiment, each edge available domain includes a plurality of edge cloud nodes, and the plurality of edge cloud nodes 12 communicate with each other. The interworking here refers to network interworking between a plurality of edge cloud nodes 12, and data exchange between the edge cloud nodes can be performed. Optionally, a plurality of edge cloud nodes 12 may be located in the same intranet, and then the edge cloud nodes 12 are intercommunicated; alternatively, a plurality of edge cloud nodes 12 may be located in respective intranets, and then the intranet interworking between the edge cloud nodes 12 is performed. The intranet where the edge cloud node 12 is located may be a local area network. Thus, in one edge available domain, on one hand, cloud computing services can be dispersedly deployed on different edge cloud nodes 12 in the edge available domain, so as to achieve the purpose of multi-point disaster recovery; in addition, when a certain edge cloud node fails, is in a high risk state, or is unavailable, the cloud computing service on the edge cloud node 12 may be migrated to other edge cloud nodes in the edge available domain, so that the availability of the cloud computing service may be ensured. Optionally, when the edge cloud node 12 fails, is at high risk, or is unavailable, a corresponding exception handling procedure or troubleshooting procedure may also be started to ensure the availability of the edge available domain.

In this embodiment, the embodiment of intranet interworking between at least two edge cloud nodes 12 in the edge available domain is not limited. For example, intranet interworking between the edge cloud nodes 12 may be implemented by a physical dedicated line, or may also be implemented in a software manner, for example, the intranet between the edge cloud nodes 12 may be opened through a Virtual Private Network (VPN), and the like. In fig. 1b, the solid lines between edge cloud nodes 12 represent the interworking between edge cloud nodes 12.

In this embodiment, the edge cloud node 12 may provide various resources to the outside. In this embodiment, the resources provided by the edge cloud node 12 may include hardware resources and software resources. Among them, the hardware resources may include: such as computing resources like processors, storage resources like memory, disks, etc. The processor may be a CPU, a GPU, an FPGA, or the like. The software resources may include: bandwidth, network segment, network card configuration and other network resources.

In this embodiment, objects capable of providing resources are collectively defined as resource objects. As shown in FIG. 1c, a resource object may be 1 or more data centers; or may be one or more rooms in 1 data center; or one or more clusters in 1 machine room; or 1 or more physical machines in 1 cluster; or 1 or more disks in 1 physical machine, one or more network cards in 1 physical machine, processor board cards (such as CPU board cards or GPU board cards) in 1 physical machine, and the like. As shown in fig. 1c, for a base station, one resource object may be 1 or more base stations; or one or more machine rooms in 1 base station; or one or more clusters in 1 machine room; or 1 or more physical machines in 1 cluster; or 1 or more disks in 1 physical machine, one or more network cards in 1 physical machine, processor board cards (such as CPU board cards or GPU board cards) in 1 physical machine, and the like.

In this embodiment, the types of resources provided by the resource objects of different levels may be different. For example, for a resource object of 1 or more distributed data centers, computing resources, storage resources, and network resources may be provided. For another example, if the resource object is 1 or more physical machines, the computing resources, storage resources, and network resources may be provided. As another example, if the resource object is a disk, then a storage resource may be provided. For another example, if the resource object is a network card, the network resource can be provided.

Wherein the quantifiable attribute description information of the plurality of resources may include at least one of: the number of the resource objects, the number of disks provided by the resource objects, the disk storage space information, the number of CPU cores of the resource objects, the bandwidth information of the resource objects and the network card throughput of the resource objects.

The non-quantifiable attribute description information for the plurality of resources may include at least one of: the device type and the model of the resource object, the disk type provided by the resource object, the storage type of the disk, the network segment information of the resource object, the gateway information of the resource object, the virtual technology type adopted by the network card of the resource object and the information of the superior and inferior relations between the resource object and other resource objects. The Virtual technology adopted by the network card may be Edge Virtual gateway technology (EVS).

Through the information of the superior-inferior relation between the resource object and other resource objects, the resource object to which one resource object belongs can be determined, and the resource object to which the resource object belongs can also be determined, so that the hierarchical relation between the resource objects is formed, the tree structure between the resource objects is formed, and the resource management efficiency is improved.

Of course, the resource objects are different, and the quantifiable attribute description information and the non-quantifiable attribute description information of the resource objects may be different. For example, as shown in fig. 1c, for a computer room (IDC computer room) with resource objects of 1 or more data centers, the available resources are computing resources, storage resources, and network resources. Quantifiable attribute description information for a data center may include: the number of the machine rooms of the data center, the number of the CPUs of the machine room of the data center, the number of the CPU cores, the cache space of the CPUs, the number of the GPUs of the data center, the number of the CUDA cores of the GPUs, the memory data and size of the GPUs, and the like, the bandwidth of the data center, the number of the IP addresses of the data center, the number of the network cards of the machine room of the data center, the bandwidth of the network cards, the throughput of the network card data, and the like, and the memory space of the data center, but not limited thereto. The non-quantifiable attribute description information of the data center comprises the following components: the method comprises the steps of obtaining geographical position information of a data center, the equipment type and the model of a physical machine contained in the data center, the disk type and the storage type of a disk provided by the data center, network segment information of the data center, gateway information of the data center, the virtual technology type adopted by a network card in the data center and the information of the upper-lower level relation between the data center and other resource objects. For example, in some embodiments, 1 or more physical machines (more than 2 or 2) in 1 data center may also be regarded as 1 resource object, and the information of the upper and lower level relationship between the data center and other resource objects is expressed as: the relationship between the data center and the physical machine contained in the data center can determine which data center the physical machine belongs to through the upper and lower level relationship. Therefore, a tree structure among the resource objects is formed, and the resource management efficiency is improved.

For another example, for a resource object that is a physical machine, the quantifiable attribute description information may include: the resource object includes, but is not limited to, the number of physical machines, the number of CPUs of the physical machines, the number of CPU cores, a cache space of the CPUs, the number of GPUs of the physical machines, a Unified computing Device Architecture (CUDA) core number of the GPUs, the number of memories and the size of a storage space of the GPUs, and the like, the number of network cards of the physical machines, a network card bandwidth, a network card data throughput, and the like, and a memory space of the physical machines. The non-quantifiable attribute description information of the physical machine comprises the following components: the method comprises the steps of obtaining geographical position information of a physical machine, the equipment type and the model of the physical machine, the type of a magnetic disk provided by the physical machine, the storage type of the magnetic disk, gateway information of the physical machine, the type of a virtual technology adopted by a network card in the physical machine and the information of the superior-inferior relation between the physical machine and other resource objects. In some embodiments, as shown in fig. 1c, the upper level resource object of the physical machine is a data center computer room or an MEC computer room.

For another example, as shown in fig. 1c, for a network segment provided by a resource object for a data center, the quantifiable attribute description information may be: the number of IP addresses contained in the network segment, the number of used IP addresses of the network segment, the number of IP addresses still usable by the network and the like; the non-quantifiable attribute description information may be: the IP address contained in the network, the used IP address of the network segment, the IP address which can be used by the network, the superior-subordinate relation between the network segment and the data center, and the like.

For another example, as shown in fig. 1c, for a resource object that is 1 or more disks in a physical machine, the quantifiable attribute description information may include: the number of disks, disk storage space information, etc., but is not limited thereto. The non-quantifiable attribute description information of the disk comprises the following components: the type of the disk, the storage type of the disk, and the information of the relationship between the disk and other resource objects (physical machines).

For another example, as shown in fig. 1c, for 1 or more network cards in a physical machine as a resource object, the quantifiable attribute description information may include: number of network cards, network card throughput, etc., but is not limited thereto. The non-quantifiable attribute description information of the disk comprises the following components: gateway information, the virtual technology type used by the network card, and the information about the relationship between the network card and other resource objects (physical machines) in the upper and lower levels, but not limited thereto.

Since the types of resources provided by the resource objects of different layers may be different, it is impossible to manage all the resource objects in the same storage format. Accordingly, a resource management model can be respectively constructed for each type of resource object, and resource management of the resource object is realized. Wherein each resource management model corresponds to a table. Thus, when a resource user uses a resource provided by a resource object, it is necessary to call each table by using a plurality of resource query interfaces (e.g., API interfaces) to query the resource information of the resource object. This, undoubtedly, increases the resource utilization cost and complexity of the resource users.

In order to solve the above technical problem, the applicant finds that the attribute description information of the resource provided by the resource object can be classified into the first type attribute description information and the second type attribute description information no matter what kind of resource provider the resource object is. The classification standard is different, and the attributes and resource types of the description information corresponding to the first type attribute description information and the second type attribute description information are different. Optionally, the resources provided by the resource object all have quantifiable attributes and non-quantifiable attributes, and accordingly, the first type of attribute description information may be quantifiable attribute description information; the second type of attribute-describing information may be non-quantifiable attribute-describing information.

Based on the above analysis, in the present embodiment, the resource management node 11 is added to the network system. The resource management node 11 may be deployed in one or more distributed data centers, or may be deployed in one or more conventional data centers, which is not limited in this embodiment.

In this embodiment, the resource management node 11 may obtain attribute description information of a plurality of resources provided by the plurality of resource objects; classifying the attribute description information of the multiple resources to obtain first attribute description information and second attribute description information; and then, the resource management node 11 stores the first type of attribute description information and the second type of attribute description information in a classified manner, so that the uniform management of heterogeneous resources is realized. In the resource management method provided by the embodiment, the attribute description information of the resource provided by the resource object is classified and stored by the first type of attribute description information and the second type of attribute description information, and the structure and the type of the hardware resource and the software resource of the resource object do not need to be concerned, thereby being beneficial to reducing the management complexity.

In this embodiment, the classification criteria are different, and the attributes and resource types of the description information corresponding to the first type of attribute description information and the second type of attribute description information are different. Optionally, the resources provided by the resource object all have quantifiable attributes and non-quantifiable attributes, and accordingly, the first type of attribute description information may be quantifiable attribute description information; the second type of description information may be non-quantifiable attribute description information. Correspondingly, the resource management node 11 may classify the attribute description information of the multiple resources according to the attribute fields in the attribute description information of the multiple resources, so as to obtain quantifiable attribute description information and non-quantifiable attribute description information.

The description information for quantifiable attributes may include: but is not limited to, one or more of the total amount of resources for a resource of a certain attribute, the amount of resources already used for the resource of the attribute, the amount of resources still available, and the amount of resources reserved for the resource of the attribute. For example, for a bandwidth, the description information of the bandwidth may include: one or more of a total amount of bandwidth, an amount of bandwidth used, an amount of bandwidth still available, and an amount of reserved bandwidth.

The embodiment of the present application does not limit the specific implementation manner in which the resource management node 11 stores quantifiable attribute description information and non-quantifiable attribute description information in a classified manner. In some embodiments, the resource management node 11 may store quantifiable attribute description information and non-quantifiable attribute description information in a classification manner using a relational model. The relational model may also be referred to as a table (two-dimensional table), and a row in the two-dimensional table is referred to as a tuple; columns in the two-dimensional table, called attributes; the values of the columns are called attribute values. Based on this, the resource management node 11 can store quantifiable attribute description information and non-quantifiable attribute description information belonging to the same resource object into the same tuple; and storing the quantifiable attribute description information and the non-quantifiable attribute description information which belong to the same resource object under the quantifiable attribute field and the non-quantifiable attribute field in a classified manner to obtain a resource information table of a plurality of resource objects. Therefore, the attribute description information of the resources provided by a plurality of resource objects can be recorded by one resource information table, when a resource user uses the resources, the resource information of the resource objects can be inquired by calling the resource information table by using one resource inquiry interface (such as an API interface), and the inquiry cost and the inquiry complexity of the resource user for inquiring the resource information are further reduced.

In the embodiment of the application, some usage type tags can be set for the resource object. For example, in some application scenarios, one or some resource objects are reserved for the resource objects for testing of the network system, and these resource objects can only be used when the performance of the network system is tested, so the resource objects can be set with the tags for testing. For another example, in other application scenarios, a certain resource object or certain resource objects are dedicated to a certain user a, and only cloud computing service can be provided for the user a, and then a user a-specific tag can be set for the user-specific resource object. For another example, in still other application scenarios, the network system may reserve some resource objects as standby resource objects, and may set standby tags for the resource objects only when other resource objects of the same type fail; and so on.

In the above case, the attribute description information of the plurality of resources provided by the plurality of resource objects may further include: usage type tags for a plurality of resource objects. Accordingly, the resource management node 11 may store the usage type labels of the plurality of resource objects, and the quantifiable attribute description information and the non-quantifiable attribute description information in a classified manner.

Also, the resource management node 11 may store quantifiable attribute description information, non-quantifiable attribute description information, and usage type tags for a plurality of resource objects in a classification manner using a relational model. Optionally, the resource management node 11 may store quantifiable attribute description information, non-quantifiable attribute description information, and usage type tags belonging to the same resource object into the same tuple; and storing quantifiable attribute description information and non-quantifiable attribute description information which belong to the same resource object under a quantifiable attribute field, a non-quantifiable attribute field and a use type label field respectively to obtain a resource information table of a plurality of resource objects. Therefore, the attribute description information of the resources provided by a plurality of resource objects can be recorded by one resource information table, when a resource user uses the resources, the resource information of the resource objects can be inquired by calling the resource information table by using one resource inquiry interface (such as an API interface), and the inquiry cost and the inquiry complexity of the resource user for inquiring the resource information are further reduced.

In this embodiment, the resource user may be the central management node 13. As shown in fig. 1a and 1b, when joining the edge cloud system (the network system provided in this embodiment), the edge cloud node 12 may provide registration information to the central management node 13. Wherein, the registration information includes: the edge cloud node 12 provides attribute description information of the resource. Here, the attribute description information of the resource provided by the edge cloud node 12 may be understood as initial attribute description information of the resource provided by the edge cloud node 12.

Further, the central control node 13 may determine the resource object included in the edge cloud node 12 according to the granularity of the resource object, and provide the attribute description information of the multiple resources provided by the resource object included in the edge cloud node to the resource management node 11. Correspondingly, the resource management node 11 receives the attribute description information of the plurality of resources, divides the attribute description information of the plurality of resources into quantifiable attribute description information and non-quantifiable attribute description information according to the attribute fields in the attribute description information of the plurality of resources, and stores the quantifiable attribute description information and the non-quantifiable attribute description information in a classified manner.

Further, in the city cloud system shown in fig. 1b, one available edge domain may correspond to one resource management node 11. Accordingly, the registration information provided by the edge cloud node 12 to the central policing node 13 may also include an identification of available edge domains. Accordingly, the central management and control node 13 may provide the attribute description information of the resource provided by the edge cloud node 12 to the resource management node 11 corresponding to the identifier of the available edge domain according to the identifier of the available edge domain.

Alternatively, a plurality of available edge cloud domains may correspond to one resource management node 11. For the case that a plurality of available edge domains correspond to one resource management node 11, the resource management node 11 may maintain one resource information table for 1 available edge domain, or maintain one resource information table for a plurality of available edge domains. The registration information provided by the edge cloud node 12 to the central policing node 13 may also include an identification of available edge domains. Accordingly, the central management node 13 may provide the resource management node 11 with attribute description information carrying the identification of the available edge domains. Further, for the case that the resource management node 11 maintains one resource information table for 1 available edge domain, the resource management node 11 may determine the resource information table corresponding to the available edge domain according to the identifier of the available edge domain. For the case that the resource management node 11 can maintain one resource information table for a plurality of available edge domains, the resource management node 11 may determine, according to the identifier of the available edge domain, a portion corresponding to the available edge domain in the resource information table; and stores attribute description information of the resource provided by the edge cloud node 12 into the portion.

In this embodiment, the central management and control node 13 may further query the resource information table, and create a virtual instance according to the attribute description information recorded in the resource information table. The virtual instance may act as a resource consumer using the resources provided by the resource object. The virtual instance may be a container (Docker) instance, a virtual machine instance, or a container group instance. The container instance may be either a Function Computation (FC) based container instance or an ECI instance, etc. The container group instance may be a pod instance, etc. Optionally, the central management and control node 13 may query the resource information table through a resource query interface (e.g., an API interface) in a case that a virtual instance needs to be created; and creating the virtual instance according to the attribute description information recorded by the resource information table and the resource requirement information of the virtual instance to be created. The resource requirement information of the virtual instance to be created may include: the computing resources, the storage resources, the network resource information, and the like required by the virtual instance to be created, that is, the computing resources, the storage resources, the network resource information, and the like required by the virtual instance to be created. In addition, the resource requirement information of the virtual instance to be created may include: quantifiable attribute description information and non-quantifiable attribute description information for resources required by a virtual instance to be created.

Optionally, the central management and control node 13 selects a target resource object that can satisfy the resource demand information from the multiple resource objects according to the attribute description information and the resource demand information recorded in the resource information table. The number of target resource objects may be 1 or more, and a plurality means 2 or more. The number of target resource objects may be determined by the resources available from the target resource objects and the resources required by the virtual instance to be created. Further, the central management and control node 13 may create a virtual instance in the target resource object according to the image file corresponding to the virtual instance to be created.

Further, the central management and control node 13 may also provide the attribute description information of the resource occupied by the virtual instance to the resource management node 11. Correspondingly, the resource management node 11 divides the attribute description information of the resources occupied by the virtual instances into quantifiable attribute description information and non-quantifiable attribute description information according to the attribute fields of the attribute description information of the resources occupied by the virtual instances; and updating the resource information table according to quantifiable attribute description information and non-quantifiable attribute description information corresponding to the attribute description information of the resources occupied by the virtual instances. Optionally, for the quantifiable attribute field in the resource information table, the resource management node 11 may modify the quantifiable attribute description information stored in the resource information table according to the quantifiable attribute description information corresponding to the attribute description information of the resource occupied by the virtual instance. For example, assuming that the target resource object is a physical machine B in the data center, the quantifiable attribute description information of the resources occupied by the virtual instance includes: and if the bandwidth of the physical machine B is 100Mbps, the used bandwidth of the physical machine B stored in the resource information table can be increased by 100Mbps, and the usable bandwidth of the physical machine B can be reduced by 100 Mbps.

Further, as shown in fig. 1c, the resource management node 11 may also record the usage relationship between the virtual instance and the target resource object according to the attribute field of the attribute description information of the resource occupied by the virtual instance; the usage relationship includes: the attribute relation between the resources occupied by the virtual instances and the target resource objects, the resource attribute and the resource amount of the target resource objects occupied by the virtual instances, and the use time. The resource consumer shown in fig. 1c is a virtual instance, such as a virtual machine, a container group, or a function computing platform.

Further, in some embodiments, the central management and control node 13 may determine whether the resource usage state of the virtual instance is normal according to the resource demand information and the usage relationship. Optionally, for the resources of the same attribute C, the central management and control node 13 may obtain, from the resource demand information, the resource amount of the attribute C resource required by the virtual instance and the resource amount of the attribute C resource occupied by the virtual instance; further, if the resource amount of the attribute C resource occupied by the virtual instance is greater than the resource amount of the attribute C resource required by the virtual instance, it is determined that the resource usage state of the virtual instance is abnormal, that is, the virtual instance has a condition that the resource usage for the attribute C is excessive.

In addition to the above system embodiments, the present application embodiments also provide a resource management method. The following describes an exemplary resource management method provided in the embodiments of the present application from the perspective of a resource management node.

Fig. 2 is a flowchart illustrating a resource management method according to an embodiment of the present application. As shown in fig. 2, the method includes:

201. acquiring attribute description information of a plurality of resources provided by a plurality of resource objects; wherein the plurality of resource objects are formed based on a plurality of edge cloud nodes.

202. And classifying the attribute description information of the multiple resources to obtain first attribute description information and second attribute description information.

203. And classifying and storing the first type attribute description information and the second type attribute description information.

The resource management method provided by the embodiment mainly manages the resources provided by the edge cloud node. For the structure of the edge cloud network, the implementation form of the edge cloud node, and the description of the resources that can be provided by the edge cloud node, reference may be made to the related contents of the above system embodiment, and details are not described here.

In this embodiment, objects capable of providing resources are collectively defined as resource objects. For the implementation form of the resource object and the related description of the resource that can be provided by the resource object, reference may be made to the related contents of the above embodiments, which are not described herein again.

The non-quantifiable attribute description information for the plurality of resources may include at least one of: the device type and the model of the resource object, the disk type provided by the resource object, the storage type of the disk, the network segment information of the resource object, the gateway information of the resource object, the virtual technology type adopted by the network card of the resource object and the information of the superior and inferior relations between the resource object and other resource objects. The resource object can be determined according to the information of the superior-inferior relation between the resource object and other resource objects, and the resource object can also be determined to contain resource objects, so that a tree structure between the resource objects is formed, and the resource management efficiency is improved.

Of course, the resource objects are different, and the quantifiable attribute description information and the non-quantifiable attribute description information of the resource objects may be different. For descriptions of quantifiable attribute description information and non-quantifiable attribute description information of different resource objects, reference may be made to the above-described system embodiments, which are not described herein again.

In order to solve the above technical problem, the applicant finds that the attribute description information of the resource provided by the resource object can be classified into the first type attribute description information and the second type attribute description information no matter what kind of resource provider the resource object is. The classification standard is different, and the attributes and resource types of the description information corresponding to the first type attribute description information and the second type attribute description information are different. Optionally, the resources provided by the resource object all have quantifiable attributes and non-quantifiable attributes, and accordingly, the first type of attribute description information may be quantifiable attribute description information; the second type of description information may be non-quantifiable attribute description information.

Based on the above analysis, in step 201, attribute description information of a plurality of resources provided by the plurality of resource objects can be obtained; in step 202, classifying the attribute description information of the multiple resources to obtain first attribute description information and second attribute description information; then, in step 203, the first type attribute description information and the second type attribute description information are stored in a classified manner, so that unified management of heterogeneous resources is realized.

In the resource management method provided by this embodiment, the attribute description information of the resource provided by the resource object is classified and stored by the first type of attribute description information and the second type of attribute description information, and the structure and type of the hardware resource and the software resource of the resource object do not need to be concerned, which is further beneficial to reducing the management complexity.

In this embodiment, the classification criteria are different, and the attributes and resource types of the description information corresponding to the first type of attribute description information and the second type of attribute description information are different. Optionally, the resources provided by the resource object all have quantifiable attributes and non-quantifiable attributes, and accordingly, the first type of attribute description information may be quantifiable attribute description information; the second type of attribute-describing information may be non-quantifiable attribute-describing information. Accordingly, an alternative implementation of step 202 is: and classifying the attribute description information of the multiple resources according to attribute fields in the attribute description information of the multiple resources to obtain quantifiable attribute description information and non-quantifiable attribute description information.

The embodiment of the application does not limit the specific implementation of storing quantifiable attribute description information and non-quantifiable attribute description information in a classified manner. In some embodiments, quantifiable attribute description information and non-quantifiable attribute description information may be stored in a taxonomic model. The relational model may also be referred to as a table (two-dimensional table), and a row in the two-dimensional table is referred to as a tuple; columns in the two-dimensional table, called attributes; the values of the columns are called attribute values. Based on the method, quantifiable attribute description information and non-quantifiable attribute description information which belong to the same resource object can be stored in the same tuple; and storing the quantifiable attribute description information and the non-quantifiable attribute description information which belong to the same resource object under the quantifiable attribute field and the non-quantifiable attribute field in a classified manner to obtain a resource information table of a plurality of resource objects. Therefore, the attribute description information of the resources provided by a plurality of resource objects can be recorded by one resource information table, when a resource user uses the resources, the resource information of the resource objects can be inquired by calling the resource information table by using one resource inquiry interface (such as an API interface), and the inquiry cost and the inquiry complexity of the resource user for inquiring the resource information are further reduced.

In the embodiment of the application, some usage type tags can be set for the resource object. For the description of the usage type tag of the resource object, reference may be made to the related contents of the above system embodiment, and details are not repeated here. Accordingly, the attribute description information of the plurality of resources provided by the plurality of resource objects may further include: usage type tags for a plurality of resource objects. Accordingly, the usage type labels of the plurality of resource objects, quantifiable attribute description information and non-quantifiable attribute description information can be classified and stored.

Also, quantifiable attribute description information, non-quantifiable attribute description information, and usage type tags for multiple resource objects may be stored in a taxonomic manner with the relational model. Optionally, quantifiable attribute description information, non-quantifiable attribute description information and usage type tags belonging to the same resource object may be stored into the same tuple; and storing quantifiable attribute description information and non-quantifiable attribute description information which belong to the same resource object under a quantifiable attribute field, a non-quantifiable attribute field and a use type label field respectively to obtain a resource information table of a plurality of resource objects. Therefore, the attribute description information of the resources provided by a plurality of resource objects can be recorded by one resource information table, when a resource user uses the resources, the resource information of the resource objects can be inquired by calling the resource information table by using one resource inquiry interface (such as an API interface), and the inquiry cost and the inquiry complexity of the resource user for inquiring the resource information are further reduced.

In this embodiment, the resource user may be a central management and control node. For the description of the functions and deployment manners of the central control node, reference may be made to the relevant contents of the above system embodiments, and details are not described herein again.

In this embodiment, when joining the edge cloud system (the network system provided in this embodiment), the edge cloud node may provide registration information to the central management and control node. Wherein, the registration information includes: the edge cloud node provides the attribute description information of the resource. Here, the attribute description information of the resource provided by the edge cloud node may be understood as initial attribute description information of the resource provided by the edge cloud node.

Further, the central control node may determine the resource objects included in the edge cloud node according to the granularity of the resource objects, and provide the attribute description information of the plurality of resources provided by the resource objects included in the edge cloud node to the resource management node. Accordingly, an alternative implementation of step 201 is: attribute description information for a plurality of resources is received. Furthermore, the attribute description information of the multiple resources can be divided into quantifiable attribute description information and non-quantifiable attribute description information according to the attribute fields in the attribute description information of the multiple resources, and the quantifiable attribute description information and the non-quantifiable attribute description information are classified and stored.

In this embodiment, the central management and control node may further query the resource information table, and create the virtual instance according to the attribute description information recorded in the resource information table. The virtual instance may act as a resource consumer using the resources provided by the resource object. Optionally, the central management and control node may query the resource information table through a resource query interface (e.g., an API interface) when the virtual instance needs to be created; and creating the virtual instance according to the attribute description information recorded by the resource information table and the resource requirement information of the virtual instance to be created. The resource requirement information of the virtual instance to be created may include: the computing resources, the storage resources, the network resource information, and the like required by the virtual instance to be created, that is, the computing resources, the storage resources, the network resource information, and the like required by the virtual instance to be created. In addition, the resource requirement information of the virtual instance to be created may include: quantifiable attribute description information and non-quantifiable attribute description information for resources required by a virtual instance to be created.

Optionally, the central management and control node may select a target resource object that can satisfy the resource demand information from the plurality of resource objects according to the attribute description information and the resource demand information recorded in the resource information table. The number of target resource objects may be 1 or more, and a plurality means 2 or more. The number of target resource objects may be determined by the resources available from the target resource objects and the resources required by the virtual instance to be created. Further, the central management and control node may create a virtual instance in the target resource object according to the image file corresponding to the virtual instance to be created.

Further, the central management and control node can also provide the attribute description information of the resources occupied by the virtual instances to the resource management node. Correspondingly, the resource management node can receive the attribute description information of the resources occupied by the virtual instances, and divide the attribute description information of the resources occupied by the virtual instances into quantifiable attribute description information and non-quantifiable attribute description information according to the attribute fields of the attribute description information of the resources occupied by the virtual instances; and updating the resource information table according to quantifiable attribute description information and non-quantifiable attribute description information corresponding to the attribute description information of the resources occupied by the virtual instances.

Furthermore, the use relationship between the virtual instance and the target resource object can be recorded according to the attribute field of the attribute description information of the resource occupied by the virtual instance; the usage relationship includes: the attribute relation between the resources occupied by the virtual instances and the target resource objects, the resource attribute and the resource amount of the target resource objects occupied by the virtual instances, and the use time.

Further, in some embodiments, it may be determined whether the resource usage state of the virtual instance is normal according to the resource demand information and the usage relationship. Optionally, for the resources of the same attribute C, the resource amount of the attribute C resource required by the virtual instance and the resource amount of the attribute C resource occupied by the virtual instance may be obtained from the resource demand information; further, if the resource amount of the attribute C resource occupied by the virtual instance is greater than the resource amount of the attribute C resource required by the virtual instance, it is determined that the resource usage state of the virtual instance is abnormal, that is, the virtual instance has a condition that the resource usage for the attribute C is excessive.

It should be noted that the execution subjects of the steps of the methods provided in the above embodiments may be the same device, or different devices may be used as the execution subjects of the methods. For example, the execution subjects of steps 201 and 202 may be device a; for another example, the execution subject of step 201 may be device a, and the execution subject of step 202 may be device B; and so on.

In addition, in some of the flows described in the above embodiments and the drawings, a plurality of operations are included in a specific order, but it should be clearly understood that the operations may be executed out of the order presented herein or in parallel, and the sequence numbers of the operations, such as 201, 202, etc., are merely used for distinguishing different operations, and the sequence numbers do not represent any execution order per se. Additionally, the flows may include more or fewer operations, and the operations may be performed sequentially or in parallel.

Accordingly, embodiments of the present application also provide a computer-readable storage medium storing computer instructions, which, when executed by one or more processors, cause the one or more processors to perform the steps of the resource management method.

Fig. 3 is a schematic structural diagram of a computer device according to an embodiment of the present application. As shown in fig. 3, the computer apparatus includes: a memory 30a and a processor 30 b. The memory 30a is used for storing computer programs.

A processor is coupled to the memory for executing a computer program for: acquiring attribute description information of a plurality of resources provided by a plurality of resource objects; wherein the plurality of resource objects are formed based on a plurality of edge cloud nodes; classifying the attribute description information of multiple resources to obtain first attribute description information and second attribute description information; the first-type attribute description information and the second-type attribute description information are stored in the memory 30a in a classified manner.

Optionally, the first type of attribute description information is quantifiable attribute description information; the second type of attribute description information is non-quantifiable attribute description information.

Correspondingly, when the processor 30b stores the first-type attribute description information and the second-type attribute description information into the memory 30a in a classified manner, the processor is specifically configured to: and classifying the attribute description information of the multiple resources according to attribute fields in the attribute description information of the multiple resources to obtain quantifiable attribute description information and non-quantifiable attribute description information.

Wherein the quantifiable attribute description information includes: at least one of the number of resource objects, the number of disks provided by the resource objects, disk storage space information, the number of CPU cores of the resource objects, the bandwidth information of the resource objects and the network card throughput of the resource objects; the non-quantifiable attribute description information includes: the device type and the model of the resource object, the disk type provided by the resource object, the storage type of the disk, the network segment information of the resource object, the gateway information of the resource object, the virtual technology type adopted by the network card of the resource object and the information of the superior and inferior relations between the resource object and other resource objects.

In some embodiments, the computer device further comprises: a communication component 30 c. When acquiring the attribute description information of the plurality of resources provided by the plurality of resource objects, the processor 30b is specifically configured to: attribute description information of the plurality of resources provided by the central management node is received through the communication component 30 c.

In other embodiments, when the processor 30b classifies and stores the quantifiable attribute description information and the non-quantifiable attribute description information, it is specifically configured to: storing quantifiable attribute description information and non-quantifiable attribute description information which belong to the same resource object into the same tuple; storing quantifiable attribute description information and non-quantifiable attribute description information which belong to the same resource object under the quantifiable attribute field and the non-quantifiable attribute field in a classified manner to obtain a resource information table of a plurality of resource objects; and stores the resource information table into the memory 30 a.

Optionally, the processor 30b is further configured to: acquiring attribute description information of resources occupied by virtual instances; dividing the attribute description information of the resources occupied by the virtual instances into quantifiable attribute description information and non-quantifiable attribute description information according to the attribute fields of the attribute description information of the resources occupied by the virtual instances; and updating the resource information table according to the quantifiable attribute description information and the non-quantifiable attribute description information corresponding to the attribute description information of the resources occupied by the virtual instances.

Further, the processor 30b is further configured to: recording the use relationship between the virtual instance and the target resource object according to the attribute field of the attribute description information of the resource occupied by the virtual instance; wherein, the use relation comprises: the method comprises at least one of the affiliation between the resources occupied by the virtual instances and the target resource objects, the resource types and the resource amounts of the target resource objects occupied by the virtual instances, and the use time.

In still other embodiments, the attribute description information of the plurality of resources further includes: usage type tags for a plurality of resource objects. The processor 30b is further configured to: the usage type tags, quantifiable attribute description information, and non-quantifiable attribute description information of the plurality of resource objects are stored in the memory 30a in a sorted manner.

In some optional embodiments, as shown in fig. 3, the computer device may further include: power supply assembly 30d, etc. If the computer equipment is terminal equipment such as a computer, a smart phone and the like, the method can also comprise the following steps: display 30e and audio component 30 f. Only some of the components shown in fig. 3 are schematically depicted, and it is not meant that the computer device must include all of the components shown in fig. 3, nor that the computer device only includes the components shown in fig. 3.

In embodiments of the present application, the memory is used to store computer programs and may be configured to store other various data to support operations on the device on which it is located. Wherein the processor may execute a computer program stored in the memory to implement the corresponding control logic. The memory may be implemented by any type or combination of volatile or non-volatile memory devices, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.

In the embodiments of the present application, the processor may be any hardware processing device that can execute the above described method logic. Alternatively, the processor may be a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), or a Micro Controller Unit (MCU); programmable devices such as Field-Programmable Gate arrays (FPGAs), Programmable Array Logic devices (PALs), General Array Logic devices (GAL), Complex Programmable Logic Devices (CPLDs), etc. may also be used; or Advanced Reduced Instruction Set (RISC) processors (ARM), or System On Chips (SOC), etc., but is not limited thereto.

In embodiments of the present application, the communication component is configured to facilitate wired or wireless communication between the device in which it is located and other devices. The device in which the communication component is located can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, 4G, 5G or a combination thereof. In an exemplary embodiment, the communication component receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component may also be implemented based on Near Field Communication (NFC) technology, Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, or other technologies.

In the embodiment of the present application, the display screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the display screen includes a touch panel, the display screen may be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation.

In embodiments of the present application, a power supply component is configured to provide power to various components of the device in which it is located. The power components may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device in which the power component is located.

In embodiments of the present application, the audio component may be configured to output and/or input audio signals. For example, the audio component includes a Microphone (MIC) configured to receive an external audio signal when the device in which the audio component is located is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signal may further be stored in a memory or transmitted via a communication component. In some embodiments, the audio assembly further comprises a speaker for outputting audio signals. For example, for devices with language interaction functionality, voice interaction with a user may be enabled through an audio component, and so forth.

The computer device provided by this embodiment can divide the attribute description information of multiple resources provided by multiple resource objects into the first type of attribute description information and the second type of attribute description information, and store the first type of attribute description information and the second type of attribute description information in a classified manner, without considering the structures and types of hardware resources and software resources of the resource objects, thereby implementing unified management on heterogeneous resources, and further contributing to reducing management complexity.

It should be noted that, the descriptions of "first", "second", etc. in this document are used for distinguishing different messages, devices, modules, etc., and do not represent a sequential order, nor limit the types of "first" and "second" to be different.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A network system, comprising: the system comprises a resource management node and a plurality of edge cloud nodes; the plurality of edge cloud nodes comprises a plurality of resource objects; the plurality of resource objects are for providing a plurality of resources;

2. The system according to claim 1, wherein the first type of attribute description information is quantifiable attribute description information; the second type of attribute description information is non-quantifiable attribute description information.

3. The system according to claim 2, wherein the resource management node, when classifying the attribute description information of the plurality of resources, is specifically configured to:

and classifying the attribute description information of the plurality of resources according to attribute fields in the attribute description information of the plurality of resources to obtain the quantifiable attribute description information and the non-quantifiable attribute description information.

4. The system according to claim 2, wherein the resource management node, when storing the first type of attribute description information and the second type of attribute description information in a classified manner, is specifically configured to:

storing quantifiable attribute description information and non-quantifiable attribute description information which belong to the same resource object into the same tuple; and storing the quantifiable attribute description information and the non-quantifiable attribute description information which belong to the same resource object under the quantifiable attribute field and the non-quantifiable attribute field in a classified manner to obtain the resource information tables of the plurality of resource objects.

5. The system of claim 4, further comprising: a central control node;

the central control node is configured to: under the condition that a virtual instance needs to be created, inquiring the resource information table through a resource inquiry interface; and creating the virtual instance according to the attribute description information recorded by the resource information table and the resource requirement information of the virtual instance to be created.

6. The system according to claim 5, wherein the central management and control node, when creating the virtual instance, is specifically configured to:

selecting a target resource object capable of meeting the resource demand information from the plurality of resource objects according to the attribute description information recorded by the resource information table and the resource demand information;

and creating a virtual instance in the target resource object according to the image file corresponding to the virtual instance to be created.

7. The system of claim 5, wherein the central management node is further configured to: providing the attribute description information of the resources occupied by the virtual instances to the resource management node;

the resource management node is further configured to: dividing the attribute description information of the resources occupied by the virtual instances into quantifiable attribute description information and non-quantifiable attribute description information according to the attribute fields of the attribute description information of the resources occupied by the virtual instances; and updating the resource information table according to quantifiable attribute description information and non-quantifiable attribute description information corresponding to the attribute description information of the resources occupied by the virtual instances.

8. The system of claim 7, wherein the resource management node is further configured to: recording the use relationship between the virtual instance and the target resource object according to the attribute field of the attribute description information of the resource occupied by the virtual instance;

the usage relationship includes: the relationship between the resources occupied by the virtual instances and the target resource object, the resource types and the resource amounts of the target resource object occupied by the virtual instances, and the usage time.

9. The system of claim 8, wherein the central management node is further configured to: and determining whether the resource use state of the virtual instance is normal or not according to the resource demand information and the use relation.

10. The system of claim 2, wherein the attribute description information of the plurality of resources further comprises: a usage type tag for the plurality of resource objects;

the resource management node is further configured to: and classifying and storing the usage type labels of the resource objects, the quantifiable attribute description information and the non-quantifiable attribute description information.

11. The system according to any of claims 2-10, wherein said quantifiable attribute description information comprises: at least one of the number of resource objects, the number of disks provided by the resource objects, disk storage space information, memory space information of the resource objects, the number of CPU cores of the resource objects, bandwidth information of the resource objects and network card throughput of the resource objects;

the non-quantifiable attribute description information includes: the device type and the model of the resource object, the disk type provided by the resource object, the storage type of the disk, the network segment information of the resource object, the gateway information of the resource object, the virtual technology type adopted by the network card of the resource object and the information of the superior and inferior relations between the resource object and other resource objects.

12. The system according to any of claims 1-10, wherein the plurality of edge cloud nodes are located in the same available edge domain; the plurality of edge cloud nodes are communicated with each other; the available edge domains are divided by address location information of the plurality of edge cloud nodes.

13. A method for resource management, comprising:

14. The method according to claim 13, wherein the first type of attribute description information is quantifiable attribute description information; the first type of attribute description information is non-quantifiable attribute description information.

15. The system according to claim 14, wherein said classifying the attribute description information of the plurality of resources comprises:

16. The method according to claim 14, wherein the storing the first type attribute description information and the second type attribute description information in a classified manner comprises:

storing quantifiable attribute description information and non-quantifiable attribute description information which belong to the same resource object into the same tuple; and the number of the first and second groups,

and storing the quantifiable attribute description information and the non-quantifiable attribute description information which belong to the same resource object under the quantifiable attribute field and the non-quantifiable attribute field in a classified manner to obtain the resource information tables of the plurality of resource objects.

17. The method of claim 16, further comprising:

acquiring attribute description information of resources occupied by virtual instances;

dividing the attribute description information of the resources occupied by the virtual instances into quantifiable attribute description information and non-quantifiable attribute description information according to the attribute fields of the attribute description information of the resources occupied by the virtual instances;

and updating the resource information table according to quantifiable attribute description information and non-quantifiable attribute description information corresponding to the attribute description information of the resources occupied by the virtual instances.

18. The method of claim 17, further comprising:

recording the use relationship between the virtual instance and the target resource object according to the attribute field of the attribute description information of the resource occupied by the virtual instance;

19. The method of claim 14, wherein the attribute description information of the plurality of resources further comprises: a usage type tag for the plurality of resource objects; the method further comprises the following steps:

and classifying and storing the usage type labels, the quantifiable attribute description information and the non-quantifiable attribute description information of the plurality of resource objects.

20. The method according to any of claims 14-19, wherein said quantifiable attribute description information comprises: at least one of the number of resource objects, the number of disks provided by the resource objects, disk storage space information, the number of CPU cores of the resource objects, the bandwidth information of the resource objects and the network card throughput of the resource objects;

21. A computer device, comprising: a memory and a processor; wherein the memory is used for storing a computer program;

the processor is coupled to the memory for executing the computer program for performing the steps of the method of any of claims 13-20.

22. A computer-readable storage medium having stored thereon computer instructions, which, when executed by one or more processors, cause the one or more processors to perform the steps of the method of any one of claims 13-20.