CN113127140A

CN113127140A - Resource management method, device and system

Info

Publication number: CN113127140A
Application number: CN201911415999.5A
Authority: CN
Inventors: 周正喜; 刘财宏; 管增辉; 赵鹏飞; 吴德新
Original assignee: Alibaba Group Holding Ltd
Current assignee: Alibaba Group Holding Ltd
Priority date: 2019-12-31
Filing date: 2019-12-31
Publication date: 2021-07-16
Anticipated expiration: 2039-12-31
Also published as: CN113127140B

Abstract

The application discloses a resource management method, device and system. The method comprises the steps of obtaining a resource description package, wherein the resource description package comprises first description information used for resource application and second description information used for resource reference, the first description information comprises resource variables of the applied resources, and the second description information comprises reference variables for referencing the resource variables of the resources; and acquiring the actual value of the reference variable in the second description information based on the first description information. Thus, support is provided for automatically deploying, extending, and managing containerized applications.

Description

Resource management method, device and system

Technical Field

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

Background

Kubernetes (K8 s for short) is an open source system for deploying, expanding and managing containerized applications, and provides a mechanism for deploying, planning, updating and maintaining applications. Helm Charts is a package structure, which is a collection of files that describe a related set of Kubernets resources, containing one or more services that can run on the Kubernets platform.

The operation of these services mostly needs to rely on a range of underlying resources such as databases, DNS, VIP, physical IP, Volumes, etc. In order to acquire related resources, Helm Charts needs to be clearly described and can be recognized by kubernets, so as to prepare basic resources for the Helm Charts and create basic resources for each service. However, with the rapid development of the internet, some services may need to refer to global resources or resources of other services, and the traditional application deployment and management mechanism has become difficult to meet the demand.

Therefore, an improved resource management scheme is needed to improve the resource management efficiency.

Disclosure of Invention

The purpose of the present disclosure is to provide a resource management method, device and system to improve the resource management efficiency.

According to a first aspect of the present disclosure, there is provided a resource management method, including: acquiring a resource description packet, wherein the resource description packet comprises first description information used for resource application and second description information used for resource reference, the first description information comprises resource variables of the applied resource, and the second description information comprises reference variables for referring to the resource variables of the resource; and acquiring the actual value of the reference variable in the second description information based on the first description information.

Optionally, the step of obtaining the actual value of the reference variable in the second description information may include: and acquiring the actual value of the reference variable in the second description information based on the first description information and the global resource description information.

Optionally, the step of obtaining the resource description packet may include: obtaining one or more resource description packages, the method may further include: determining a resource dependency relationship between the one or more resource description packages, wherein the resource dependency relationship characterizes a resource reference relationship between the one or more resource description packages.

Optionally, the resource dependency relationship between the one or more resource description packages may be determined based on a reference variable included in the second description information of the one or more resource description packages.

Optionally, the method may further include: and constructing a relation graph representing the resource reference relation, wherein in the relation graph, one resource description packet containing the referenced resource variable points to another resource description packet which refers to the resource variable in the resource description packet.

Optionally, the relationship graph is a directed acyclic graph.

Optionally, the method further comprises: and sequentially processing the one or more resource description packages based on the resource dependency relationship so as to obtain the actual values of the reference variables in the second description information of the one or more resource description packages.

Optionally, the step of sequentially processing the one or more resource description packets includes: under the condition that a preset keyword exists in the reference variable of the resource description package, assigning the reference variable in the resource description package as the resource variable to be referred to; and under the condition that no preset key word exists in the reference variables of the resource description package, assigning the reference variables in the resource description package as global resource variables, wherein the preset key word represents that reference relations to other resource description packages exist.

Optionally, the method may further include: storing the resource variables declared exposed by the one or more resource description packages in global resource variables; and acquiring the actual value of the reference variable in the second description information based on the first description information and the global resource description information.

Optionally, the second description information includes at least one of: a reference variable of a resource applied by the resource description package; reference variables for resource variables exposed for other resource description packages; a reference variable for a global resource variable.

Optionally, the first description information further includes a resource attribute of the applied resource, and the actual value of the reference variable in the second description information includes the resource attribute. Or, the first description information further includes resource type information of the applied resource.

Optionally, the method may further include: maintaining a resource list comprising names, version information of the one or more resource description packages and resource attribute information of the applied resources, wherein the resource list is used for obtaining resources and/or dependency analysis.

Optionally, the method may further include: deploying a running environment of the resource description package on the terminal; acquiring the resource applied by the resource description packet; and deploying the service corresponding to the resource description package on the terminal based on the operating environment and the applied resource.

Optionally, the resource description packet is a chat packet; and/or the first descriptive information and/or the second descriptive information are characterized based on a yaml file; and/or the method is applied to kubernets.

According to a second aspect of the present disclosure, there is also provided a resource management method, including: preparing a resource description package, wherein the resource description package comprises first description information used for resource application and second description information used for resource reference, the first description information comprises resource variables of the applied resource, and the second description information comprises reference variables for referring to the resource variables of the resource; and sending the resource description packet to a resource management device.

Optionally, the method may further include: and the resource application equipment receives a resource description packet returned by the resource management equipment, wherein second description information included in the resource description packet returned by the resource management equipment is an actual value of a reference variable.

According to a third aspect of the present disclosure, a resource management method is also provided. The resource application equipment prepares a resource description packet and sends the resource description packet to the resource management equipment, wherein the resource description packet comprises first description information used for resource application and second description information used for resource reference, the first description information comprises resource variables of the applied resource, and the second description information comprises reference variables for referencing the resource variables of the resource. And the resource management equipment acquires the resource description packet from the resource application equipment, acquires the actual value of the reference variable in the second description information based on the first description information, processes the resource description packet to enable the second description information to be the actual value of the reference variable, and returns the processed resource description packet to the resource application equipment. And the resource application equipment receives the resource description packet returned by the resource management equipment, and acquires the resource applied by the resource description packet and/or deploys the service corresponding to the resource description packet based on the returned resource description packet.

According to a fourth aspect of the present disclosure, a service deployment method is also provided. The resource management device acquires a resource description packet from the resource application device, wherein the resource description packet comprises first description information used for resource application and second description information used for resource reference, the first description information comprises resource variables of the applied resource, and the second description information comprises reference variables for referring to the resource variables of the resource. And the resource management equipment acquires the actual value of the reference variable in the second description information based on the first description information, processes the resource description packet so that the second description information is the actual value of the reference variable, and returns the processed resource description packet to the resource application equipment. The resource application equipment deploys the running environment of the resource description package on the terminal, acquires the resource applied by the resource description package based on the returned resource description package, and deploys the service corresponding to the resource description package on the terminal based on the running environment and the applied resource.

According to a fifth aspect of the present disclosure, there is also provided a resource management system, including: the resource application equipment is used for preparing a resource description packet and sending the resource description packet to the resource management equipment, wherein the resource description packet comprises first description information used for resource application and second description information used for resource reference, the first description information comprises resource variables of the applied resource, and the second description information comprises reference variables for referencing the resource variables of the resource; and the resource management equipment is used for acquiring the resource description packet, acquiring the actual value of the reference variable in the second description information based on the first description information, and returning the resource description packet to the resource application equipment, wherein the returned second description information included in the resource description packet is the actual value of the reference variable.

Optionally, the resource application device may: deploying a running environment of the resource description package on the terminal; acquiring the resource applied by the resource description packet based on the resource description packet returned by the resource management equipment; and deploying the service corresponding to the resource description package on the terminal based on the operating environment and the applied resource.

According to a sixth aspect of the present disclosure, there is also provided a resource management apparatus, including: a resource description package obtaining device, configured to obtain a resource description package, where the resource description package includes first description information used for a resource application and second description information used for resource reference, the first description information includes a resource variable of the applied resource, and the second description information includes a reference variable that refers to the resource variable of the resource; and the processing device is used for acquiring the actual value of the reference variable in the second description information based on the first description information.

According to a seventh aspect of the present disclosure, there is also provided a computing device comprising: a processor; and a memory having executable code stored thereon, which when executed by the processor, causes the processor to perform the method as described above.

According to an eighth aspect of the present disclosure, there is also provided a non-transitory machine-readable storage medium having stored thereon executable code, which when executed by a processor of an electronic device, causes the processor to perform the method as described above.

Therefore, by providing a set of complete system resource management scheme which defines the description information of various resources related to the resource description package, the required resources can be conveniently acquired by statically analyzing and processing the description information, and the application and/or creation of the resources are statically solved. And moreover, a resource dependence processing mode based on the resource description package is provided, so that when the service corresponding to the resource description package is deployed, the service can be directly deployed without waiting and inquiring the resource creation process, and the deployment of products and even the whole operating environment is greatly accelerated.

Drawings

The above and other objects, features and advantages of the present disclosure will become more apparent by describing in greater detail exemplary embodiments thereof with reference to the attached drawings, in which like reference numerals generally represent like parts throughout.

FIG. 1 shows a schematic diagram of a resource management system according to one embodiment of the present disclosure.

FIG. 2 shows a flow diagram of resource management according to one embodiment of the present disclosure.

FIG. 3 shows a schematic diagram of a relationship diagram according to one embodiment of the present disclosure.

FIG. 4 shows a flow diagram of a resource management method according to one embodiment of the present disclosure.

Fig. 5 shows a schematic structural diagram of a resource management device according to an embodiment of the present disclosure.

FIG. 6 shows a schematic structural diagram of a computing device, according to one embodiment of the present disclosure.

Detailed Description

Preferred embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While the preferred embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. 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.

Kubernetes (K8 s for short) is an open source system for deploying, expanding and managing containerized applications, providing mechanisms for application deployment, planning, updating, and maintenance with the objective of making deploying containerized applications simple and efficient.

Helm is a tool to manage Kubernets application packages, often using a packaging format called chart. Charts is a package structure used by Helm, is a collection of files describing a related set of kubernets resources, containing one or more services (or applications) that can run on the kubernets platform. In the disclosed embodiment, Charts may also be referred to as "Helm Charts".

Most of the services represented by Charts need to rely on a range of underlying resources, such as databases, DNS, VIP, physical IP, Volumes, etc. These Helm Charts need to be well described and can be parsed by Kubernets in order to prepare the underlying resources and create the underlying resources for the respective services in order to obtain the relevant resources.

The present disclosure provides a set of complete system resource management schemes, which defines the description information of multiple resources related to the resource description package, so that the required resources can be conveniently obtained by statically analyzing and processing the description information, and the application and/or creation of the resources are statically solved. And moreover, a resource dependence processing mode based on the resource description package is provided, so that when the service corresponding to the resource description package is deployed, the service can be directly deployed without waiting and inquiring the resource creation process, and the deployment of products and even the whole operating environment is greatly accelerated.

The resource management scheme described above may be applicable to open source systems that automatically deploy, extend, and manage containerized applications, such as kubernets.

In the following examples of the present disclosure, kubernets will be taken as an example to explain the resource management scheme of the present disclosure. It should be understood that the application scenario of the resource management scheme of the present disclosure is not limited thereto.

As shown in fig. 1, the resource management system of the present disclosure may include a resource application device 110 and a resource management device 120. The resource application device 110 applies for resources for corresponding service deployment on the terminal 130.

The resource application apparatus 110 may prepare a resource description packet and may be able to transmit the prepared resource description packet to the resource management apparatus 120.

The resource description packets may be Chart packets, each of which may correspond to one or more services, such as wordpress, database, DNS or VIP, information handling services, data handling services, and the like.

The resource description package prepared by the resource application device 110 may include a set of files describing the relevant resources, such as resource application files, resource reference files, and the like. The resource application file may include first description information for the resource application, and the first description information may include resource variables of the applied resource. The resource reference file may include second description information for resource reference, and the second description information may include reference variables that reference resource variables of the resource.

The resource management device 120 can receive the resource description package sent by the resource application device 110, and can perform analysis processing on the resource description package, so that the resource description package can be used for product deployment.

In the embodiment of the present disclosure, the analysis processing may include, for example, processing related to resource dependency analysis, basic resource acquisition, resource variable rendering, and the like between resource description packages. These processes may be understood as static processes, i.e. they are implemented only for the description information and/or global resource description information contained in the resource description package.

The processed resource description package can be sent to a resource application device, so that the resource application device can deploy and run corresponding services on a related terminal. Here, the terminal may be any terminal device capable of running the service represented by the resource description package, including but not limited to a computer, a smart phone, a tablet computer, and the like.

Specifically, the resource application device may first deploy, on the terminal, an operating environment of a resource description package, then may obtain, based on the resource description package returned by the resource management device, a resource applied by the resource description package, and then deploy, on the terminal, a service corresponding to the resource description package based on the operating environment and the applied resource.

In one embodiment, the resource management device 120 may be a cloud platform. The cloud platform can be a full-stack cloud platform facing enterprise-level users, can be based on a distributed architecture of cloud products, and provides an open, unified and credible enterprise-level cloud platform for the users aiming at the use characteristics of an enterprise-level market. And moreover, the user can develop and deploy with the environment anywhere, and the online and localized deployment of the cloud platform can be freely extended.

Referring to fig. 2, the overall flow of resource management may include a prepare resource description package stage 21, a resource description package processing stage 22, and a service deployment stage 23 based on the resource description package.

Additionally, in one embodiment, the service deployment phase may include the prepare resource description package phase, the resource description package processing phase, and the service deployment phase described above. The resource management scheme of the present disclosure is flexible in implementation, and the details of the present disclosure are not limited in its specific implementation. It should be understood that the embodiments of the present disclosure are at least for the purpose of illustrating the implementation flow of the present disclosure, and not for the purpose of limiting the same.

The following describes the whole resource management scheme implemented by the resource management system shown in fig. 1 in detail by taking the flowchart shown in fig. 2 as an example. It should be understood that the following description is only illustrative and not restrictive of the resource description scheme of the present disclosure, and that the resource management scheme of the present disclosure may also be implemented in any other suitable manner or method, and the present disclosure is not limited thereto.

Prepare resource description package phase

With reference to fig. 1 and 2, first, in step S210, a resource description package is prepared.

Here, the resource description package may be prepared by the resource applying apparatus 110 based on the relevant specification. The resource application device may also provide the resource description file (including information such as resource types and references defining resource variables for requirements of the resource application device) to the resource management device, and the resource management device packages the resource description file to obtain a corresponding resource description package.

The resource application device 110 may be any resource application device, such as a service developer.

In the embodiment of the present disclosure, one or more resource description packages may be prepared by one resource application apparatus. Alternatively, a plurality of resource description packages may be prepared by a plurality of resource application devices, and one or more resource description packages may be obtained by a resource management device by separately packaging based on the resource description file provided by the resource application device, which is not limited in this disclosure.

In one embodiment, the resource description packet may be a Charts packet. Chart can be organized as a collection of files within a directory, the name of which is the name of Chart.

The prepared one or more resource description packets may be, for example, Chart A, Chart B, Chart C, … …, Chart O, Chart P, etc., as shown in FIG. 2. Each resource description package may have the same implementation, e.g., a fixed syntax implementation.

1) Charts structure

Taking the WordPress application as an example, Chart describing WordPress may be stored in the WordPress/directory. Within this directory, the Charts structure description can be as follows:

yarl is YAML format, and is used for describing basic information of chart, including the name of chart.

Yaml is used to store variables used in template files in templates directory.

YAML is a YAML format used to describe the demand for various resources.

value-adapter. yaml is a subset of the variables in value. yaml that are used to reference resource variables (e.g., DNS domain names, database user names, etc.) in resource. yaml.

Templates is used for storing Chart template files, and mainly comprises various description files of Kubernets resources (resources). The template file may be, for example, a Go template.

Txt is an introduction document used for introducing some information after the deployment of the chat to the terminal deploying the chat, such as how to use the chat, list default settings, and the like.

2) Resource application

In the Charts structure, the resource application, which is the requirement for various resources, can be defined in resource.

In embodiments of the present disclosure, the resource.yaml may comprise at least two parts: a Required resource (resource Required) part and a service Registration (service Registration) part.

The Required resource (resource Required) part may include some information for declaring the resource Required to apply for, and may include, for example, a resource type, a resource attribute, a value of the resource attribute, and the like.

The service Registration (service Registration) section may include exposed resource variables and values of the exposed resource variables, etc. Based on that one Chart is a service Registration part, other Charts can refer to the resource corresponding to the resource variable exposed by the Chart. Wherein, the resource variable exposed to the outside by Chart may also be referred to as a global resource variable.

For example, using a database resource as an example, its resource of Chart may include the following:

in the above section of resourceRequired, "db", i.e. resource type-database; the name, the user and the password are resource attributes which are respectively a database name, a database user name and a database password; "mq", "msg", "Te 83_ yr3& Y" are values of the resource attribute, and correspond to the database name, the database username, and the database password, respectively.

In the serviceRegistration part, "db _ name", "db _ user", and "db _ password" are exposed resource variables; "$ { db.mq.name }", "$ { db.mq.user }", "$ { db.mq.password }" are the values of the exposed resource variables.

Using DNS/VIP resources as an example, Chart's resource. yaml may include the following:

similar to resource.yaml of Chart, which takes database resources as an example, above, in resource.yaml of Chart, which takes DNS/VIP resources as an example, the resource required section describes some information on demand for DNS resources and/or VIP resources, while the serviceRegistration describes resource variables exposed to the outside and the values of the exposed resource variables, so that the outside (e.g., other Chart) can access domain names of DNS named wordpress through proxy _ endpoint. And will not be described in detail herein.

In one embodiment, resource.yaml may further include some global variables, for example, which may be used to define requirement descriptions of Docker Registry addresses, platform root domain names, network types, and the like.

In this section, the global variable may be defined, for example, by $ { global: RESOURCE _ NAME }. For example, the Docker Registry address is described by $ { global: Docker Registry }. And will not be described in detail herein.

3) Resource referencing

In the Charts structure, references to various resources, i.e., resource references, can be described in values-adapter. Yaml file can be used to determine the resource dependency relationship between the Chart and the resource requested by the Chart or the resource requested by other Chart or the global resource.

In embodiments of the present disclosure, the resource references mentioned in values-adapter. yaml may include resource references of multiple aspects, for example, references of Chart to resource variables of its own application, references of Chart to other Chart exposed resource variables, or references of Chart to global resource variables, etc.

In one embodiment, the resource references described above may be described, for example, in the form of reference variables.

For example, the reference of Chart to the resource variable of its own application may be described by the following reference variables:

“${RESOURCE_TYPE.RESOURCE_NAME.RESOURCE_ATTRIBUTE}”

wherein "RESOURCE _ TYPE" represents the referenced RESOURCE TYPE, "RESOURCE _ NAME" represents the referenced RESOURCE NAME, and "RESOURCE _ ATTRIBUTE" represents the referenced RESOURCE ATTRIBUTE.

Alternatively, references to resource variables exposed by other Charts by Chart can be described, for example, by the following reference variables:

“${chart:CHART_NAME:SERVICEREGISTRATION_VAR}”

wherein, "Chart _ NAME" represents the NAME of Chart of the referenced Chart, and "SERVICEREGISTRATION _ VAR" represents the NAMEs of resource variables exposed to the outside by other Charts.

"$ { Chart: } can be used as a reference relation indicating that there is a description package for other resources, and when the predetermined keyword is found in one Chart, it can be obtained that the one Chart references the resource related to the resource variable exposed by the other Chart.

Based on the information realized by the fixed grammar, the specified resource type, name and attribute can be displayed during writing, and when resource reference is carried out among different services, the information such as the Binding Secret name and the type of the resource attribute does not need to be clarified.

So far, the resource description package of the present disclosure has been described in detail in conjunction with fig. 1 and 2.

Compared with the structural description of Helm Charts by Kubernets community, the resource description package, i.e. Charts package, of the present disclosure adds two yacml files, namely resource.

The resource description package of the present disclosure may describe resource references in values-adapter.yaml by defining various resource types in resource required in resource.yaml. The definition mode does not limit the concrete implementation mode of the same resource and can shield the implementation details of concrete resource entities. For example, for a database resource, its resource type can be defined as db, without concern for whether its underlying Mysql implementation, MariaDB implementation, or other implementations, can be adapted, and without altering the Chart baseline.

Moreover, the Charts package disclosed by the invention is simple in structure, conforms to Kubernets community specifications, and can be compatible with the Kubernets community Charts structure.

Moreover, based on the Charts structure disclosed by the disclosure, when the processing is completed and the service deployment is carried out, the variables in the value-indicators can take effect through a Helm Chart installation command (Helm install Chart-f values-indicators-yall), and the deployment is completed.

Resource description packet processing phase

After completing the preparation of the resource description package, the resource application device 110 may provide (e.g., transmit) the prepared resource description package to the resource management device 120. As described above, the resource management device may also prepare the resource description package based on the resource description file provided by the resource application device and perform corresponding processing.

The resource management device 120 can obtain the resource description package sent by the resource application device 110, and in step S220, analyze and process the resource description package, so that the resource description package can be used for product deployment.

In the embodiment of the present disclosure, the analysis processing may include, for example, processing related to resource dependency analysis, basic resource acquisition, resource variable rendering, and the like between resource description packages. The processes are static processes, that is, the processes are implemented by performing static analysis only on the description information and the global resource description information included in the resource description packet.

1) Resource dependent analysis

Referring to fig. 2, in step S220, a dependency analysis process may be performed on a plurality of resource description packages.

In one aspect, a value-adapter. yaml file for each resource description package may be analyzed to determine resource dependencies between two or more resource description packages. Resource dependencies may characterize resource reference relationships between one or more resource description packages.

On the other hand, global analysis can be performed on each resource description packet, and information contained in each resource description packet is collected and implemented in a list form.

During the analysis process described above, analysis can be performed by referencing variables across Chart. After the dependency analysis processing, a relation graph and a Chart list which characterize the dependency of Chart on resources can be obtained.

In the relationship diagram, one resource description package, which may contain referenced resource variables, points to another resource description package that references resource variables in the one resource description package.

In this Chart list, information included in each Chart may be summarized, for example, with the Chart name as a key.

Based on the Chart resource dependency relationship diagram and the Chart list, it is convenient to implement acquisition of the basic resource applied by each Chart or implement dependency analysis between the Charts in the subsequent processing, which will be described in detail below and will not be described herein again.

It should be understood that, in the analysis process, the process of obtaining the Chart list may be performed first, and then the process of obtaining the relationship graph may be performed, or the process of obtaining the relationship graph may be performed first, and then the process of obtaining the Chart list may be performed, and the processes of obtaining the relationship graph and obtaining the Chart list may also be performed simultaneously, which is not limited by the present disclosure.

Relationship diagram

The relationship graph may characterize the resource dependencies between Charts. When analyzing the values-adapter. yaml files of the various resource description packages, a relationship graph representing the resource reference relationship can be constructed. In addition, in the relationship diagram, one resource description package that can contain the referenced resource variable points to another resource description package that references the resource variable in the one resource description package.

In one embodiment, the relationship graph may be a directed acyclic graph as shown in FIG. 3.

Referring to fig. 3, ChartA points to ChartB, ChartB points to ChartC and ChartO, ChartC and ChartO points to ChartP, that is, it indicates that in the directed acyclic graph, ChartB refers to the resource related to ChartA, ChartC and ChartO refer to the resource related to ChartB, ChartP refers to the resource related to ChartC and ChartO.

It should be understood that fig. 3 only uses charts such as ChartA, ChartB, ChartC, ChartO, ChartP as an example, and schematically shows the resource dependency relationship between charts, but does not have any limitation on the resource dependency relationship. In practical application, the corresponding directed acyclic graph is obtained by combining the actual contents of a plurality of Charts. Under the condition that the number of Charts is large or the reference relationship among the Charts is more complex, the directed acyclic graph representing the resource reference relationship is also more complex, and is not described herein again.

Chart List

The Chart list may be a summary of information included in a plurality of resource description packages, including but not limited to information included in a plurality of files involved in describing the structure of the resource description package, for example, self information (e.g., Chart name, Chart version, etc.) of the resource description package, resource information applied, a resource variable declared to be exposed, a reference variable characterizing a resource application, and the like.

In one embodiment, a Chart list may include multiple Chart objects, each corresponding to a Chart packet (i.e., a resource description packet). In other embodiments, a Chart list may also be obtained corresponding to each resource description packet, and the specific implementation form of the Chart list is not limited by the present disclosure.

Taking an example that one Chart list summarizes information included in a plurality of resource description packets, the structure of the Chart list may be as follows:

the Chart list includes a plurality of Chart objects, that is, "0 ═ Chart } < >," 1 ═ Chart } < >, "… ….

Each Chart object may include the following data structure:

where "name" corresponds to the name of Chart, "version" corresponds to the version of Chart, "values _ adapter" corresponds to the contents of the card handled in the value _ adapter. yaml file of Chart, "resource _ variables" corresponds to the attribute information of all resources applied for one Chart, and "service _ registration _ variables" corresponds to the resource variables exposed by the Chart statement.

Based on the Chart list, in the subsequent analysis processing, the acquisition of the resource applied by each resource description packet can be conveniently realized, the dependency analysis of each resource description packet can be realized, and the processing based on each Chart is not needed.

In other words, in the embodiment of the present disclosure, the resource description package based on the ". yaml" file is processed as the list of Chart objects, and in the subsequent analysis processing, even in the product deployment process, the corresponding basic resource can be conveniently obtained or the product deployment can be completed without waiting and querying the resource creation process.

2) Basic resource acquisition

Here, "acquiring" may be considered as static acquiring, that is, analyzing and processing the description information in the charts to obtain a description file of how to acquire the resource requested by the charts, such as a resource application variable information list and a basic resource application information set, so as to facilitate the subsequent service deployment stage 23 to acquire the required resource, and statically solve the application and/or creation of the resource.

Resource application variable information list

Based on the Chart list, a resource application variable information list can be obtained through processing. The resource application variable information list may include all resource variables applied by each Chart and their corresponding actual values.

The resource _ variables of each Chart object can be obtained from the Chart list, and the actual values corresponding to the resources related to the resource _ variables are obtained, so as to obtain the resource application variable information list.

The structure of the resource application variable information list may be as follows:

chart-a

-dns

-vip

chart-b

-dns

-vip

chart-c

-dns

-vip

……

taking a database resource as an example, for example, the attribute information of the resource applied by Chart may be obtained in the following manner, so as to obtain the basic resource application information set:

wherein, the content indicates that the resource applied by Chart is obtained from resource _ required of Chart; judging whether the Chart applies for database resources or not; acquiring resources of all database types from resources applied by Chart; and (4) assigning, namely filling the acquired actual values of the database resources into 'resource _ variables' to obtain a resource application variable information list.

The resulting resource application variable information list may be used as input for a subsequent resource variable rendering stage.

Basic resource application information set

On the basis of the resource application variable information list, a basic resource application information set corresponding to a plurality of resource description packets (i.e., Chart packets) can be obtained.

The basic resource application information set may, for example, summarize resource information of resources desired to be applied by a plurality of resource description packages according to resource classification.

The structure of the basic resource application information set may be as follows:

db:

-name:

user:

password:

-name:

user:

password:

dns:

vip:

……

based on the basic resource application information set, the resources applied by the multiple resource description packages can be applied and obtained in the subsequent service deployment stage 23.

3) Resource variable rendering

Subsequently, based on the above directed acyclic graph, the resource application variable information list, and the global resource description information, in step S230, a variable in the values-adapter. Based on the Chart package including the values-adapter. yaml file, the service represented by Chart can be deployed, and product deployment and operation are completed.

The global resource description information may include a global resource variable and an actual value corresponding to the global resource variable, and may further include a variable exposed to the outside by Chart and a corresponding actual value, which are stored in the process of processing each Chart packet and serve as the global resource variable.

Specifically, in conjunction with the directed acyclic graph shown in fig. 3, Chart a may be processed first, Chart B may be processed later, Chart C and Chart O may be processed later, and ChartP may be processed last.

Therein, the "service _ registration _ variables" portion of Chart A, which represents the resource variables that Chart A exposes to the outside, may be processed first.

That is, in the case that there is a resource variable that needs to be exposed to the outside, preprocessing is performed on each variable declared to be exposed by Chart a, so that service _ registration _ variables exposed to the outside of Chart a are normalized.

When the resource variables exposed to the outside of Chart A contain the preset keywords, for example, the keywords "$ { Chart" indicating that the reference relationship to other resource description packages exists are assigned to the resource variables exposed to the outside of Chart A as the variables needing to be exposed between Charts. And under the condition that the externally exposed resource variable of Chart A does not contain a preset keyword, assigning the externally exposed resource variable of Chart A as a global resource variable.

In addition, in this process, the name of Chart may also be used as a key, and all variables exposed to outside by Chart a are stored in a global resource variable (univarial _ variables), so that when subsequently processing Chart B, the reference of Chart B to the Chart a resource can be acquired.

Meanwhile, rendering reference variables to the resources in the values-adapter.yaml file into corresponding actual values based on resource application variables (resource _ variables) and global resource variables (univeral _ variables).

And then, based on the same processing mode as that for Chart A, processing Chart B, ChartC, O and Chart P, and finishing the variable rendering of all Chart.

After the processing is completed, the plurality of charts may be packaged respectively, wherein each Chart includes a rendered values-adapter. In this way, the resource description packet (chart packet) is processed, so that the reference variable therein is rendered as the actual value of the reference variable. The processed resource description packet may then be returned to the resource application device 110. On this basis, the service represented by each Chart can be deployed.

Here, because of the previous processing, the basic dependent resources are ready, and when deployment is performed, variables in the values-adapters-.

Service deployment phase

At this stage, the service represented by each Chart may be deployed on a terminal of the runtime environment (e.g., kubernets platform) that has deployed the resource description package.

On the basis of the preprocessing, in step S241, a resource application may be submitted through the basic resource application information set, so as to create a resource applied by the Chart for the relevant Chart and obtain the resource applied by the resource description package.

Then, in step S242, deployment and operation may be completed based on the operation environment (operation state) and the requested resource, that is, the service corresponding to the resource description package (i.e., Chart) is deployed on the terminal.

The resource management scheme of the present disclosure has been described in detail with reference to fig. 1-3.

The resource management scheme disclosed by the invention provides a complete system solution resource application and reference scheme, can cover dependency description of various resources such as DNS, VIP, a database, a physical IP and a magnetic disk which are depended by the Kubernets product, simultaneously provides a reference scheme of the Kubernets product for the resources, and also provides a reference scheme of the Kubernets product for exposed resource variables of other Kubernets products.

The resource management scheme disclosed by the invention can realize cross-application resource reference and exposure, is not limited to single application management, and is more convenient to configure with platform-level resources. The application side (such as a resource application device) only needs to declare the required resource type and define the reference of the resource variable, and the platform side (such as a resource management side) performs unified dependency analysis, variable rendering and resource creation without individually processing declaration, creation and reference of the resource for each application.

The resource management scheme disclosed by the invention defines various resource types in resource Required of resource. yaml, does not limit the specific implementation mode of the same resource, shields the implementation details of specific resource entities, does not need to care about the specific implementation of the resource and does not need to change a Chart baseline. In addition, the method and the device have a uniform resource variable rendering mechanism, and can uniformly process all the resources of all the applications without developing and adapting each resource.

Moreover, the resource management scheme disclosed by the invention statically solves the application and creation of resources in a resource dependence processing mode, and can be directly deployed without waiting and inquiring the resource creation process when the product is deployed, so that the speed of deploying Kubernets products is increased, and even the deployment process of the whole Kubernets platform is increased.

The resource management scheme as described above may also be implemented as a resource management method, which may be implemented by a resource management apparatus. FIG. 4 shows a flow diagram of a resource management method according to one embodiment of the present disclosure. Fig. 5 shows a schematic structural diagram of a resource management device 500 according to an embodiment of the present disclosure.

As shown in fig. 4, in step S410, a resource description package including first description information for a resource application and second description information for resource reference may be obtained, for example, by the resource description package obtaining device 510 shown in fig. 5, where the first description information includes a resource variable of the applied resource, and the second description information includes a reference variable that references the resource variable of the resource.

In step S420, for example, the processing device 520 shown in fig. 5 may obtain an actual value of the reference variable in the second description information based on the first description information.

In an embodiment of the present disclosure, the step of obtaining an actual value of the reference variable in the second description information may include: and acquiring the actual value of the reference variable in the second description information based on the first description information and the global resource description information.

In this embodiment of the present disclosure, the step of obtaining the resource description packet may include: obtaining one or more resource description packages, the resource management method may further include: determining a resource dependency relationship between the one or more resource description packages, wherein the resource dependency relationship characterizes a resource reference relationship between the one or more resource description packages.

In the embodiment of the present disclosure, the resource dependency relationship between the one or more resource description packages may be determined based on a reference variable included in the second description information of the one or more resource description packages.

In this embodiment of the present disclosure, a relationship graph characterizing the resource reference relationship may also be constructed, where in the relationship graph, one resource description package containing the referenced resource variable points to another resource description package that references the resource variable in the one resource description package. Preferably, the relational graph is a directed acyclic graph.

In this embodiment of the present disclosure, the one or more resource description packages may be further sequentially processed based on the resource dependency relationship, so as to obtain an actual value of a reference variable in the second description information of the one or more resource description packages.

In this embodiment of the present disclosure, the step of sequentially processing the one or more resource description packets includes: under the condition that a preset keyword exists in the reference variable of the resource description package, assigning the reference variable in the resource description package as the resource variable to be referred to; and under the condition that no preset key word exists in the reference variables of the resource description package, assigning the reference variables in the resource description package as global resource variables, wherein the preset key word represents that reference relations to other resource description packages exist.

In this disclosure, the resource variables declared exposed by the one or more resource description packages may also be stored in a global resource variable, and then the actual values of the reference variables in the second description information may be obtained based on the first description information and the global resource description information.

In an embodiment of the present disclosure, the second description information includes at least one of: a reference variable of a resource applied by the resource description package; reference variables for resource variables exposed for other resource description packages; a reference variable for a global resource variable.

In the embodiment of the present disclosure, the first description information may further include a resource attribute of the applied resource, and the actual value of the reference variable in the second description information includes the resource attribute. Alternatively, the first description information may further include resource type information of the requested resource.

In this disclosure, a resource list may be further maintained, where the resource list includes names and version information of the one or more resource description packages and resource attribute information of the applied resources, and the resource list may be used to obtain resources and/or perform dependency analysis.

In the embodiment of the present disclosure, a running environment of the resource description package may also be deployed on the terminal; acquiring the resource applied by the resource description packet; and deploying the service corresponding to the resource description package on the terminal based on the operating environment and the applied resource.

In the disclosed embodiment, the resource description packet may be a Chart packet. The first descriptive information and/or the second descriptive information may be characterized based on a yaml file. The resource management method of the present disclosure can be applied to kubernets.

In another embodiment, the method can also be implemented as a resource management method implemented by a resource application device.

Specifically, the resource application device may prepare a resource description packet including first description information for resource application and second description information for resource reference, the first description information including a resource variable of the applied resource, the second description information including a reference variable that references the resource variable of the resource, and send the resource description packet to the resource management device.

And then, the resource application device can receive a resource description packet returned by the resource management device, wherein the second description information included in the resource description packet returned by the resource management device is an actual value of the reference variable. Based on the received resource description packet returned by the resource management device, deployment of relevant services corresponding to the resource description packet can be performed.

For example, the runtime environment of the resource description package may be deployed on the endpoint; acquiring the resource applied by the resource description packet based on the resource description packet returned by the resource management equipment; and deploying the service corresponding to the resource description package on the terminal based on the operating environment and the applied resource.

Referring to fig. 6, computing device 600 includes memory 610 and processor 620.

The processor 620 may be a multi-core processor or may include a plurality of processors. In some embodiments, processor 620 may include a general-purpose host processor and one or more special coprocessors such as a Graphics Processor (GPU), a Digital Signal Processor (DSP), or the like. In some embodiments, processor 620 may be implemented using custom circuits, such as an Application Specific Integrated Circuit (ASIC) or a Field Programmable Gate Array (FPGA).

The memory 610 may include various types of storage units, such as system memory, Read Only Memory (ROM), and permanent storage. Wherein the ROM may store static data or instructions that are required by the processor 620 or other modules of the computer. The persistent storage device may be a read-write storage device. The persistent storage may be a non-volatile storage device that does not lose stored instructions and data even after the computer is powered off. In some embodiments, the persistent storage device employs a mass storage device (e.g., magnetic or optical disk, flash memory) as the persistent storage device. In other embodiments, the permanent storage may be a removable storage device (e.g., floppy disk, optical drive). The system memory may be a read-write memory device or a volatile read-write memory device, such as a dynamic random access memory. The system memory may store instructions and data that some or all of the processors require at runtime. In addition, the memory 610 may include any combination of computer-readable storage media, including various types of semiconductor memory chips (DRAM, SRAM, SDRAM, flash memory, programmable read-only memory), magnetic and/or optical disks, may also be employed. In some embodiments, memory 610 may include a removable storage device that is readable and/or writable, such as a Compact Disc (CD), a digital versatile disc read only (e.g., DVD-ROM, dual layer DVD-ROM), a Blu-ray disc read only, an ultra-dense disc, a flash memory card (e.g., SD card, min SD card, Micro-SD card, etc.), a magnetic floppy disk, or the like. Computer-readable storage media do not contain carrier waves or transitory electronic signals transmitted by wireless or wired means.

The memory 610 has stored thereon processable code, which, when processed by the processor 620, causes the processor 620 to perform the above-mentioned resource management methods.

The resource management method, apparatus and system according to the present disclosure have been described in detail above with reference to the accompanying drawings.

Furthermore, the method according to the present disclosure may also be implemented as a computer program or computer program product comprising computer program code instructions for performing the above-mentioned steps defined in the above-mentioned method of the present disclosure.

Alternatively, the present disclosure may also be embodied as a non-transitory machine-readable storage medium (or computer-readable storage medium, or machine-readable storage medium) having stored thereon executable code (or a computer program, or computer instruction code) which, when executed by a processor of an electronic device (or computing device, server, etc.), causes the processor to perform the various steps of the above-described method according to the present disclosure.

Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the disclosure herein may be implemented as electronic hardware, computer software, or combinations of both.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems and methods according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

Having described embodiments of the present invention, the foregoing description is intended to be exemplary, not exhaustive, and not limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is chosen in order to best explain the principles of the embodiments, the practical application, or improvements made to the technology in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.

Claims

1. A method of resource management, comprising:

acquiring a resource description packet, wherein the resource description packet comprises first description information used for resource application and second description information used for resource reference, the first description information comprises resource variables of the applied resource, and the second description information comprises reference variables for referring to the resource variables of the resource; and

and acquiring the actual value of the reference variable in the second description information based on the first description information.

2. The method of claim 1, wherein the step of obtaining the actual value of the reference variable in the second description information comprises:

and acquiring the actual value of the reference variable in the second description information based on the first description information and the global resource description information.

3. The method of claim 2, wherein the step of obtaining the resource description packet comprises:

one or more resource description packages are obtained,

the method further comprises the following steps:

determining a resource dependency relationship between the one or more resource description packages, wherein the resource dependency relationship characterizes a resource reference relationship between the one or more resource description packages.

4. The method of claim 3, wherein,

and determining the resource dependency relationship among the one or more resource description packages based on the reference variable included in the second description information of the one or more resource description packages.

5. The method of claim 4, further comprising:

and constructing a relation graph representing the resource reference relation, wherein in the relation graph, one resource description packet containing the referenced resource variable points to another resource description packet which refers to the resource variable in the resource description packet.

6. The method of claim 5, wherein,

the relationship graph is a directed acyclic graph.

7. The method of claim 5, further comprising:

and sequentially processing the one or more resource description packages based on the resource dependency relationship so as to obtain the actual values of the reference variables in the second description information of the one or more resource description packages.

8. The method of claim 7, wherein the step of sequentially processing the one or more resource description packets comprises:

under the condition that a preset keyword exists in the reference variable of the resource description package, assigning the reference variable in the resource description package as the resource variable to be referred to;

assigning the reference variables in the resource description package as global resource variables in the case that the predetermined key words do not exist in the reference variables of the resource description package,

wherein the predetermined keyword indicates that there is a reference relationship to other resource description packages.

9. The method of claim 8, further comprising:

storing the resource variables declared exposed by the one or more resource description packages in global resource variables; and

10. The method of claim 1, wherein the second descriptive information includes at least one of:

a reference variable of a resource applied by the resource description package;

reference variables for resource variables exposed for other resource description packages;

a reference variable for a global resource variable.

11. The method of claim 1, wherein the first descriptive information further includes resource attributes of the requested resource,

the actual value of the reference variable in the second description information includes the resource attribute.

12. The method of claim 1, wherein the first description information further includes resource type information of the requested resource.

13. The method of claim 1, further comprising:

maintaining a resource list including names of the one or more resource description packages, version information, and resource attribute information of the requested resource,

wherein the resource list is used to obtain resources and/or dependency analysis.

14. The method of claim 13, further comprising:

deploying a running environment of the resource description package on the terminal;

acquiring the resource applied by the resource description packet; and

and deploying the service corresponding to the resource description package on the terminal based on the operating environment and the applied resource.

15. The method of claim 1, wherein,

the resource description packet is a Chart packet; and/or

The first description information and/or the second description information are characterized based on a yaml file; and/or

The method is applied to Kubernetes.

16. A method of resource management, comprising:

preparing a resource description package, wherein the resource description package comprises first description information used for resource application and second description information used for resource reference, the first description information comprises resource variables of the applied resource, and the second description information comprises reference variables for referring to the resource variables of the resource; and

and sending the resource description packet to a resource management device.

17. The method of claim 16, further comprising:

and the resource application equipment receives a resource description packet returned by the resource management equipment, wherein second description information included in the resource description packet returned by the resource management equipment is an actual value of a reference variable.

18. A method of resource management, comprising:

the resource application equipment prepares a resource description packet and sends the resource description packet to the resource management equipment, wherein the resource description packet comprises first description information used for resource application and second description information used for resource reference, the first description information comprises resource variables of the applied resource, and the second description information comprises reference variables for referencing the resource variables of the resource;

the resource management equipment acquires the resource description packet from the resource application equipment, acquires the actual value of the reference variable in the second description information based on the first description information, processes the resource description packet to enable the second description information to be the actual value of the reference variable, and returns the processed resource description packet to the resource application equipment;

and the resource application equipment receives the resource description packet returned by the resource management equipment, and acquires the resource applied by the resource description packet and/or deploys the service corresponding to the resource description packet based on the returned resource description packet.

19. A service deployment method, comprising:

the resource management equipment acquires a resource description packet from resource application equipment, wherein the resource description packet comprises first description information used for resource application and second description information used for resource reference, the first description information comprises resource variables of the applied resource, and the second description information comprises reference variables for referring to the resource variables of the resource;

the resource management equipment acquires the actual value of the reference variable in the second description information based on the first description information, processes the resource description packet so that the second description information is the actual value of the reference variable, and returns the processed resource description packet to the resource application equipment;

the resource application equipment deploys the running environment of the resource description package on the terminal, acquires the resource applied by the resource description package based on the returned resource description package, and deploys the service corresponding to the resource description package on the terminal based on the running environment and the applied resource.

20. A resource management system, comprising:

the resource application equipment is used for preparing a resource description packet and sending the resource description packet to the resource management equipment, wherein the resource description packet comprises first description information used for resource application and second description information used for resource reference, the first description information comprises resource variables of the applied resource, and the second description information comprises reference variables for referencing the resource variables of the resource;

and the resource management equipment is used for acquiring the resource description packet, acquiring the actual value of the reference variable in the second description information based on the first description information, and returning the resource description packet to the resource application equipment, wherein the returned second description information included in the resource description packet is the actual value of the reference variable.

21. The system of claim 20, wherein the resource application device:

acquiring the resource applied by the resource description packet based on the resource description packet returned by the resource management equipment; and

22. A resource management apparatus, comprising:

a resource description package obtaining device, configured to obtain a resource description package, where the resource description package includes first description information used for a resource application and second description information used for resource reference, the first description information includes a resource variable of the applied resource, and the second description information includes a reference variable that refers to the resource variable of the resource; and

and the processing device is used for acquiring the actual value of the reference variable in the second description information based on the first description information.

23. A computing device, comprising:

a processor; and

a memory having executable code stored thereon, which when executed by the processor, causes the processor to perform the method of any of claims 1-17.

24. A non-transitory machine-readable storage medium having stored thereon executable code, which when executed by a processor of an electronic device, causes the processor to perform the method of any of claims 1-17.