Label generation method and device

Abstract

The embodiments of this specification provide a tag generation method and device, the method comprising receiving a tag generation request sent by a user, wherein the tag generation request carries the user's attribute information, a tag identifier, and a tag generation condition corresponding to the tag identifier; determining the user's cloud resources based on the user's attribute information; and setting the tag identifier as a target tag for the cloud resource if the cloud resource meets the tag generation condition. Specifically, the tag generation method generates a target tag for the cloud resource that meets the condition based on the tag identifier set by the user and the tag generation condition corresponding to the tag identifier, and automatically establishes a binding relationship between the cloud resource and the target tag, without the need for manual maintenance by the user, thereby improving the user experience.

Description

Technical Field

[0001] The embodiments of the present specification relate to the field of computer technology, and in particular to a label generation method. Background Art

[0002] With the maturity and development of cloud computing technology, the trend of enterprise-level projects migrating from traditional data centers to cloud platforms is becoming more and more obvious. Enterprise-level projects are characterized by abundant resources, large scale, and multiple project types. Therefore, effective management of cloud resources on the cloud platform can effectively improve operation and maintenance efficiency. Among them, cloud resources refer to various data stored in the cloud platform.

[0003] Currently, in order to enable users to conveniently manage cloud resources in the cloud platform by adding tags to cloud resources in the cloud platform, users need to create and delete tags for cloud resources one by one through the cloud resource operation page, which is cumbersome. In addition, when adding new cloud resources, users need to manually add tags to the newly added cloud resources, which has a poor user experience. Summary of the invention

[0004] In view of this, the present specification provides a label generation method. One or more embodiments of the present specification also relate to a label generation device, a label generation system, a computing device, and a computer-readable storage medium to solve the technical defects existing in the prior art.

[0005] According to a first aspect of an embodiment of this specification, a tag generation method is provided, including:

[0006] Receiving a label generation request sent by a user, wherein the label generation request carries attribute information of the user, a label identifier, and a label generation condition corresponding to the label identifier;

[0007] Determining cloud resources of the user based on attribute information of the user;

[0008] In a case where the cloud resource meets the tag generation condition, the tag identifier is set as a target tag for the cloud resource.

[0009] According to a second aspect of an embodiment of this specification, there is provided a label generation device, including:

[0010] A request receiving module is configured to receive a tag generation request sent by a user, wherein the tag generation request carries attribute information of the user, a tag identifier, and a tag generation condition corresponding to the tag identifier;

[0011] a cloud resource determination module, configured to determine the cloud resources of the user based on the attribute information of the user;

[0012] The tag generation module is configured to set the tag identifier as a target tag of the cloud resource when the cloud resource meets the tag generation condition.

[0013] According to a third aspect of an embodiment of this specification, a label generation system is provided, including:

[0014] The client is used to provide a label condition input method, receive a label identifier and a corresponding label generation condition set by a user through the label condition input method, generate a label generation request, the label generation request carries the attribute information of the user, the label identifier and the label generation condition corresponding to the label identifier, and send the label generation request to the cloud;

[0015] The cloud end is used to receive the tag generation request, determine the cloud resources of the user based on the attribute information of the user, and set the tag identifier as the target tag of the cloud resource when the cloud resource meets the tag generation condition.

[0016] According to a fourth aspect of an embodiment of this specification, a computing device is provided, including:

[0017] Memory and processor;

[0018] The memory is used to store computer executable instructions, and the processor is used to execute the computer executable instructions. When the computer executable instructions are executed by the processor, the steps of the above-mentioned label generation method are implemented.

[0019] According to a fifth aspect of the embodiments of this specification, a computer-readable storage medium is provided, which stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, the steps of the above-mentioned label generation method are implemented.

[0020] An embodiment of the present specification implements a label generation method and device, wherein the label generation method includes receiving a label generation request sent by a user, wherein the label generation request carries attribute information of the user, a label identifier, and a label generation condition corresponding to the label identifier; determining the cloud resources of the user based on the attribute information of the user; and setting the label identifier as a target label of the cloud resource when the cloud resource meets the label generation condition.

[0021] Specifically, the tag generation method generates a target tag for cloud resources that meet the tag identifier set by the user and the tag generation condition corresponding to the tag identifier, so as to establish a binding relationship between the target tag and the cloud resource. Subsequently, when the cloud resource does not meet the target tag, the target tag can be automatically deleted. When the user has a new cloud asset that meets the tag generation condition, a binding relationship can be automatically established with the target tag, without the need for manual maintenance by the user, thereby improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 is a flow chart of a label generation method provided by an embodiment of this specification;

[0023] Figure 2 is a schematic diagram of a target label generated by a label generation method provided by an embodiment of this specification;

[0024] Figure 3 It is a structural schematic diagram of a label generation device provided by an embodiment of this specification;

[0025] Figure 4 It is a structural block diagram of a computing device provided by an embodiment of this specification. DETAILED DESCRIPTION

[0026] Many specific details are described in the following description to facilitate a full understanding of this specification. However, this specification can be implemented in many other ways than those described herein, and those skilled in the art can make similar generalizations without violating the connotation of this specification, so this specification is not limited to the specific implementation disclosed below.

[0027] The terms used in one or more embodiments of this specification are only for the purpose of describing specific embodiments, and are not intended to limit one or more embodiments of this specification. The singular forms of "a", "said" and "the" used in one or more embodiments of this specification and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used in one or more embodiments of this specification refers to and includes any or all possible combinations of one or more associated listed items.

[0028] It should be understood that although the terms first, second, etc. may be used to describe various information in one or more embodiments of this specification, this information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of one or more embodiments of this specification, the first may also be referred to as the second, and similarly, the second may also be referred to as the first. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

[0029] First, the terms involved in one or more embodiments of this specification are explained.

[0030] Cloud server: ECS, Elastic Compute Service.

[0031] VPC: (Virtual Private Cloud, private network.

[0032] RDS: Relational Database Service, relational database.

[0033] SLB: Server Load Balancer, load balancing.

[0034] Tags: specific texts, such as finance and temporary, can be tags respectively; there can also be multiple combinations, such as defining two layers of text as one tag, such as department-finance as one tag, and function-development as one tag. Users can add specific tags to cloud assets (cloud resources) under their name according to specific project logic to manage and query cloud assets by category.

[0035] Smart tags: Through specific conditions, the system automatically binds tags to cloud assets.

[0036] Currently, there are two types of tags: one is user-defined tags: tags maintained by users themselves, which can be applied to any cloud assets in batches. However, this requires a lot of maintenance costs, as not only existing cloud assets need to be tagged, but also new cloud assets need to be tagged; the other is system tags, which are generally cloud resources created by second-party cloud products and tagged with specific system tags to identify the creator, which has great limitations.

[0037] Based on this, in this specification, a label generation method is provided. This specification also involves a label generation device, a label generation system, a computing device, and a computer-readable storage medium, which are described in detail one by one in the following embodiments.

[0038] See also Figure 1 , Figure 1A flowchart of a label generation method provided according to an embodiment of the present specification is shown, which specifically includes the following steps.

[0039] Step 102: receiving a tag generation request sent by a user, wherein the tag generation request carries attribute information of the user, a tag identifier, and a tag generation condition corresponding to the tag identifier.

[0040] In practical applications, the tag generation method is applied to a cloud platform. Through the tag generation method, target tags can be quickly and conveniently created and deleted for cloud resources in the cloud platform, thereby saving operation and maintenance costs and improving user experience.

[0041] Among them, the user's attribute information includes but is not limited to the user's cloud account or cloud ID on the cloud platform; the tag identifier can be understood as any type of tag name, such as a tag name composed of text, numbers and / or characters, such as the tag identifier: finance; the tag generation condition corresponding to the tag identifier can be understood as the tag identifier can be generated when the tag generation condition is met, that is, different tag identifiers can correspond to different tag generation conditions.

[0042] In specific implementation, the label generation conditions include resource information of at least one dimension, conditional relationships, and resource attribute values, wherein the resource information of at least one dimension includes cost, resource attributes, and performance; the conditional relationships include include, do not include, equal to, and greater than; and the resource attribute values ​​include string type, numeric type, and percentage type.

[0043] Among them, resource attributes include but are not limited to instance name (a cloud resource can be called an instance), bandwidth peak, etc.; performance includes but is not limited to the performance of the cloud server (such as CPU usage, memory usage, disk usage, etc.), the performance of the relational database, etc.

[0044] Taking the label generation condition including two dimensions of resource information, conditional relationship and resource attribute value as an example, if the two dimensions of resource information include resource attributes: ECS, ECS performance: CPU usage; the conditional relationship includes equal, and, less than; the resource attribute value includes 30%, then the label generation condition formed by the combination of the above information can be: resource attribute: ECS, instance name equal to temporary business, and performance: CPU usage less than 30%.

[0045] Then, when the tag is marked as: CPU usage is too high, it can be understood that all cloud resources that meet the tag generation conditions in the cloud platform will be labeled with "CPU usage is too high" in the future.

[0046] In the embodiments of this specification, the label generation conditions can utilize resource information, conditional relationships, and resource attribute values ​​in multiple dimensions, and can be freely selected and combined to create according to actual needs. This can meet the user's needs for creating target labels for cloud resources in various situations in the cloud platform, thereby improving the user experience.

[0047] Specifically, receiving a tag generation request sent by a user can be understood as the cloud platform receiving a tag generation request sent by the user, which carries the user's attribute information, a tag identifier, and a tag generation condition corresponding to the tag identifier.

[0048] Step 104: Determine the cloud resources of the user based on the attribute information of the user.

[0049] Continuing with the above example, if the user's attribute information is the cloud account registered by the user on the cloud platform, determining the user's cloud resources based on the user's attribute information can be understood as: based on the cloud account registered by the user on the cloud platform, obtaining all cloud resources of the cloud account on the cloud platform, that is, the cloud resources used by the user on the cloud platform.

[0050] Specifically, determining the cloud resources of the user based on the attribute information of the user includes:

[0051] When the cloud resources of the user are created, or if the cloud resources of the user have been created, the available cloud resources of the user are determined based on the attribute information of the user.

[0052] In specific implementation, when a user's cloud resources are created, the user's cloud resources can be determined based on the user's attribute information; or if the user's cloud resources have been created before, the user's available cloud resources can also be determined based on the user's attribute information.

[0053] In actual applications, unusable cloud resources generally have no reference value. In order to save computing resources, after receiving the tag generation request sent by the user, the cloud platform only determines the usable cloud resources currently created or previously created by the user on the cloud platform, so that when the user's usable cloud resources meet the tag generation conditions, target tags can be added to the usable cloud resources based on the tag generation conditions.

[0054] For example, if the cloud resources created by the user include cloud resource 1, cloud resource 2 and cloud resource 3; among which, the life cycle of cloud resource 1 and cloud resource 2 has not yet ended and they are usable cloud resources, and the life cycle of initial cloud resource 3 has ended and it is an unusable cloud resource; then based on the user's attribute information, the user's usable cloud resources are determined to be cloud resource 1 and cloud resource 2.

[0055] Step 106: When the cloud resource meets the tag generation condition, the tag identifier is set as the target tag of the cloud resource.

[0056] Using the above example, if the tag identifier is "CPU usage is too high", the tag generation condition of the tag identifier is "resource attribute: ECS, instance name equals temporary business, and performance: CPU usage is less than 30%"; in actual application, first determine the user's cloud resources based on the user's attribute information, for example, including cloud resource 1, cloud resource 2 and cloud resource 3; then match each cloud resource with the tag generation condition, and when a cloud resource meets the tag generation condition, set the above tag identifier as the target tag of the cloud resource. For example, the cloud resources that meet the tag generation condition include cloud resource 1 and cloud resource 2, then set the tag identifier as the target tag of cloud resource 1 and cloud resource 2, that is, cloud resource 1 and cloud resource 2 are respectively marked with the target tag of "CPU usage is too high".

[0057] The label generation method provided in the embodiment of this specification can filter the cloud resources of the user that meet the label generation conditions through the label generation conditions, and automatically generate target labels for the filtered cloud resources that meet the label generation conditions, that is, use the label identifier corresponding to the label generation conditions as the target label.

[0058] In addition, since users will continuously update cloud resources on the cloud platform, such as creating new cloud resources, when creating new cloud resources, the tag generation method provided in the embodiment of this specification can be used to automatically determine whether the newly created cloud resources meet the tag generation conditions corresponding to the tag identifier, and when the created new cloud resources meet the tag generation conditions, the target tag is automatically set for the created new cloud resources. The specific implementation method is as follows:

[0059] After the tag identifier is set as the target tag of the cloud resource, the method further includes:

[0060] When the user creates a new cloud resource, it is determined whether the newly created cloud resource meets the tag generation condition.

[0061] If so, the tag identifier is set as the target tag of the newly created cloud resource.

[0062] Specifically, when a user creates a new cloud resource, the cloud platform will automatically determine whether the newly created cloud resource meets the preset tag generation conditions. If so, the tag identifier corresponding to the tag generation condition is set as the target tag of the newly created cloud resource.

[0063] In actual applications, users will set multiple tag identifiers for their cloud resources in the cloud platform, and each tag identifier corresponds to different tag generation conditions; then when the user creates a new cloud resource in the cloud platform, the newly created cloud resource can be matched with the tag generation condition corresponding to each tag identifier, and finally the tag identifier corresponding to the successfully matched tag generation condition is automatically used as its target tag.

[0064] The above embodiment is an automatic creation process of a target tag. When the life cycle of a cloud resource with a target tag is over (i.e. released), the target tag of the cloud resource can be automatically deleted based on the tag generation method provided in the embodiment of this specification, so as to improve the efficiency of creating and deleting the target tag of the cloud resource and facilitate management. The specific implementation method is as follows:

[0065] After the tag identifier is set as the target tag of the cloud resource, the method further includes:

[0066] When the user's cloud resources are released, the target tag of the cloud resources is deleted.

[0067] Continuing with the above example, assuming that there are cloud resources 1 and cloud resources 2 with target tags set, then when cloud resources 1 and / or cloud resources 2 are released, the cloud platform can automatically delete the target tags of cloud resources 1 and / or cloud resources 2, thereby improving the user's tag deletion experience.

[0068] In specific implementation, users can adjust the label generation conditions in real time on the cloud platform. When the label generation conditions change, it is necessary to determine whether each cloud resource corresponding to the label identifier of the label generation condition still meets the changed label generation conditions. If so, the target label of the cloud resource is retained; if not, the target label of the cloud resource is deleted. The specific implementation method is as follows:

[0069] After the tag identifier is set as the target tag of the cloud resource, the method further includes:

[0070] When the label generation condition changes, it is determined whether the cloud resource meets the changed label generation condition.

[0071] If yes, the target tag of the cloud resource is not deleted.

[0072] If not, the target tag of the cloud resource is deleted.

[0073] In the embodiments of the present specification, when the label generation conditions change, the cloud resources are triggered to match the changed label generation conditions again. When matching, the target label of the cloud resource is retained. When mismatching, the corresponding target label is configured for the cloud resource, thereby ensuring the accuracy of the target label of the cloud resource.

[0074] At the same time, since the cloud resources in the cloud platform also change in real time, the changed cloud resources may not meet the label generation conditions corresponding to the target label. At this time, it is not appropriate for the changed cloud resources to use the previous target label. Therefore, based on this property of cloud resources, the label generation method provided in the embodiment of this specification can judge in real time whether the cloud resources still meet the label generation conditions corresponding to the current target label according to the characteristics of real-time changes in cloud resources. If it is determined that the changed cloud resources do not meet the label generation conditions corresponding to the current target label, the target label will be deleted in time, and the changed cloud resources will be matched with the label generation conditions corresponding to other target labels. If it is determined that the changed cloud resources meet the label generation conditions corresponding to other target labels, its target label will be updated in time. The specific implementation method is described as follows:

[0075] After the tag identifier is set as the target tag of the cloud resource, the method further includes:

[0076] Performing resource update detection on a target cloud resource based on a preset time interval, wherein the target cloud resource is a cloud resource with a target tag set;

[0077] When it is determined that the target cloud resource does not satisfy the tag generation condition, the target tag of the target cloud resource is deleted.

[0078] The preset time interval can be set according to actual application, such as 2 seconds, 5 seconds, 6 seconds, etc.

[0079] In practical applications, it is not excluded to perform resource update detection on the target cloud resource in real time. As long as it is determined that the target cloud resource does not meet the label generation condition corresponding to the current target label, the target label of the target cloud resource is deleted.

[0080] In specific implementation, a user may set multiple target tags, and each target tag corresponds to a different tag generation condition. Then, after deleting the target tag of the target cloud resource, the target cloud resource can be matched with other tag generation conditions, and the target tag corresponding to the successfully matched tag generation condition can be used as the target tag of the cloud resource.

[0081] In addition, since cloud resources in the cloud platform change in real time, cloud resources that did not previously meet the label generation conditions corresponding to the target label may also meet the label generation conditions of the target label after the change. Then, if a cloud resource meets a certain label generation condition, the label identifier corresponding to the label generation condition can be used as the target label of the cloud resource. The specific implementation method is as follows:

[0082] After the tag identifier is set as the target tag of the cloud resource, the method further includes:

[0083] Performing update detection on other cloud resources of the user except the target cloud resource based on a preset time interval, wherein the target cloud resource is a cloud resource with a target tag set;

[0084] When it is determined that the other cloud resources meet the tag generation condition, the tag identifier is set as a target tag for the other cloud resources.

[0085] The preset time interval can be set according to actual application, such as 2 seconds, 5 seconds, 6 seconds, etc.

[0086] In practical applications, it is not ruled out that real-time resource update detection is performed on cloud resources other than the target cloud resources. As long as it is determined that cloud resources other than the target cloud resources meet the label generation conditions corresponding to the target label, the target label is added to the cloud resources other than the target cloud resources.

[0087] Continuing with the above example, the target cloud resources include cloud resource 1 and cloud resource 2, and the cloud resources other than the target cloud resources are cloud resource 3.

[0088] In actual applications, the cloud platform will perform real-time detection on cloud resource 3, and if it is determined that cloud resource 3 meets the label generation condition corresponding to the target label, the target label will be added to cloud resource 3. The actual scenario can be understood as follows: the cloud platform will perform real-time detection on cloud resource 3, and if it is determined that cloud resource 3 meets a certain label generation condition, the label identifier corresponding to the label generation condition will be added to cloud resource 3 as the target label.

[0089] In addition, in order to improve the flexibility of labeling smart labels for cloud resources, users can also adjust the label generation conditions to regenerate target labels for cloud resources based on the adjusted label generation conditions. The specific implementation method is as follows:

[0090] After the tag identifier is set as the target tag of the cloud resource, the method further includes:

[0091] An adjustment instruction for the label generation condition sent by the user is received, and the label generation condition is adjusted based on the adjustment instruction.

[0092] The adjustment instructions include but are not limited to instructions for modifying, deleting, or adding content in the label generation conditions.

[0093] The label generation method provided in the embodiments of this specification can adjust the content of the label generation conditions according to the adjustment instructions for the label generation conditions sent by the user, so that the user can flexibly adjust the label generation conditions according to actual needs, thereby improving the user experience.

[0094] The tag generation method provided in the embodiment of this specification generates a target tag for a cloud resource that meets the condition based on the tag identifier set by the user and the tag generation condition corresponding to the tag identifier, so as to establish a binding relationship between the target tag and the cloud resource. Subsequently, when the cloud resource does not meet the target tag, the target tag can be automatically deleted. When the user has a new cloud asset that meets the tag generation condition, a binding relationship can be automatically established with the target tag, without the need for manual maintenance by the user, thereby improving the user experience.

[0095] See also Figure 2 , Figure 2 A schematic diagram showing a target label generated by a label generation method provided in accordance with an embodiment of the present specification is shown.

[0096] Figure 2 The smart tag in the embodiment can be understood as the target tag of the above embodiment. The smart tag is divided into two parts. The first part is the definition of the smart tag, that is, the generation of the smart tag; the second part is the use value of the smart tag, that is, the beneficial effect of the smart tag.

[0097] Specifically, the definition of smart tags includes: user-defined tags, the composition of specific conditions, and the triggering time of specific conditions.

[0098] Among them, user-defined tags can be understood as label identifiers of the above-mentioned embodiments. Such user-defined tags do not require users to actively maintain labels for resources. Users only need to set specific conditions for entry and exit of smart tags, and the system will automatically add or remove smart tags when specific conditions change.

[0099] The composition of a specific condition includes the dimension of the condition, the condition relationship and the specific value; the dimensions include but are not limited to the dimensions such as cost, resource attribute, performance, etc., and the cost includes but is not limited to the unit VCPU cost, unit duration cost, cumulative cost, cumulative duration, etc., the resource attributes include but are not limited to ECS (such as instance name, bandwidth peak, etc.), VPC, RDS, SLB, etc., the performance includes but is not limited to ECS (such as CPU usage, memory usage, disk usage, etc.), RDS, etc., the condition relationship includes but is not limited to include, does not include, equal to, etc., the specific value can be understood as the specific value in the resource attribute, which can be a numeric type, a string type, etc.

[0100] When used specifically, a specific condition consisting of the above dimensions, conditional relationships, and specific values ​​is used, for example: Resource attributes: ECS: instance name equals temporary business, And performance: CPU usage is less than 30%.

[0101] Triggering timing of specific conditions: The relationship between smart tags and resource lifecycles, that is, smart tags are created and released according to the resource lifecycle, and when the dimension values ​​in specific conditions (such as cost, performance, and attributes) change, the smart tags of resources are re-determined.

[0102] The value of using smart tags includes: users can be freed from the tedious work of tag maintenance, existing instances (original existing cloud resources) no longer need to be tagged one by one, and incremental instances (newly added cloud resources) will also be tagged according to specific conditions; a large picture of cross-cloud products / resource types can allow users to more intuitively control assets on the cloud platform through tags / smart tags; and real-time monitoring is possible. Since the resources associated with smart tags change in real time, the smart tags of the resources can be adjusted in real time based on the real-time changes of the resources associated with the smart tags.

[0103] The smart tags generated by the tag generation method provided in the embodiments of this specification automatically bind the tags to cloud resources according to specific conditions set by the user. When the specific conditions are met or not met, the tags are automatically added or deleted without the need for manual maintenance by the user. Tags can be bound and unbound throughout the resource life cycle according to the specific conditions set by the user. Users no longer need to manage tags for existing and incremental resources, but only need to maintain customized tag generation conditions, which greatly improves the user experience.

[0104] Corresponding to the above method embodiment, this specification also provides a label generation device embodiment, Figure 3 FIG. 1 shows a schematic diagram of a label generation device provided by an embodiment of the present specification. Figure 3 As shown, the device comprises:

[0105] The request receiving module 302 is configured to receive a tag generation request sent by a user, wherein the tag generation request carries attribute information of the user, a tag identifier, and a tag generation condition corresponding to the tag identifier;

[0106] A cloud resource determination module 304 is configured to determine the cloud resources of the user based on the attribute information of the user;

[0107] The tag generation module 306 is configured to set the tag identifier as a target tag of the cloud resource if the cloud resource meets the tag generation condition.

[0108] Optionally, the cloud resource determination module 304 is further configured to:

[0109] When the cloud resources of the user are created, or if the cloud resources of the user have been created, the available cloud resources of the user are determined based on the attribute information of the user.

[0110] Optionally, the device further includes: a resource creation module configured to:

[0111] When the user creates a new cloud resource, it is determined whether the newly created cloud resource meets the tag generation condition.

[0112] If so, the tag identifier is set as the target tag of the newly created cloud resource.

[0113] Optionally, the device further includes: a resource releasing module configured to:

[0114] When the user's cloud resources are released, the target tag of the cloud resources is deleted.

[0115] Optionally, the device further includes: a condition change module configured to:

[0116] When the label generation condition changes, it is determined whether the cloud resource meets the changed label generation condition.

[0117] If yes, the target tag of the cloud resource is not deleted.

[0118] If not, the target tag of the cloud resource is deleted.

[0119] Optionally, the device further includes: a first resource updating module configured to:

[0120] Performing resource update detection on a target cloud resource based on a preset time interval, wherein the target cloud resource is a cloud resource with a target tag set;

[0121] When it is determined that the target cloud resource does not satisfy the tag generation condition, the target tag of the target cloud resource is deleted.

[0122] Optionally, the device further comprises:

[0123] The second resource updating module is configured as follows:

[0124] Performing update detection on other cloud resources of the user except the target cloud resource based on a preset time interval, wherein the target cloud resource is a cloud resource with a target tag set;

[0125] When it is determined that the other cloud resources meet the tag generation condition, the tag identifier is set as a target tag for the other cloud resources.

[0126] Optionally, the label generation conditions include resource information of at least one dimension, conditional relationships, and resource attribute values, wherein the resource information of at least one dimension includes cost, resource attributes, and performance; the conditional relationships include include, do not include, equal to, and greater than; and the resource attribute values ​​include string type, numeric type, and percentage type.

[0127] The label generation device provided in the embodiment of this specification generates a target label for a cloud resource that meets the condition according to the label identifier set by the user and the label generation condition corresponding to the label identifier, so as to establish a binding relationship between the target label and the cloud resource. Subsequently, when the cloud resource does not meet the target label, the target label can be automatically deleted. When the user has a new cloud asset that meets the label generation condition, a binding relationship can be automatically established with the target label, without the need for manual maintenance by the user, thereby improving the user experience.

[0128] The above is a schematic scheme of a label generation device of this embodiment. It should be noted that the technical scheme of the label generation device and the technical scheme of the label generation method described above are of the same concept, and the details not described in detail in the technical scheme of the label generation device can be found in the description of the technical scheme of the label generation method described above.

[0129] Corresponding to the above method embodiment, this specification also provides a label generation system embodiment, which includes:

[0130] The client is used to provide a label condition input method, receive a label identifier and a corresponding label generation condition set by a user through the label condition input method, generate a label generation request, the label generation request carries the attribute information of the user, the label identifier and the label generation condition corresponding to the label identifier, and send the label generation request to the cloud;

[0131] The cloud end is used to receive the tag generation request, determine the cloud resources of the user based on the attribute information of the user, and set the tag identifier as the target tag of the cloud resource when the cloud resource meets the tag generation condition.

[0132] The above is a schematic scheme of a label generation system of this embodiment. It should be noted that the technical scheme of the label generation system and the technical scheme of the label generation method described above are of the same concept, and the details not described in detail in the technical scheme of the label generation system can be found in the description of the technical scheme of the label generation method described above.

[0133] Figure 4 The block diagram of a computing device 400 according to one embodiment of the present specification is shown. The components of the computing device 400 include but are not limited to a memory 410 and a processor 420. The processor 420 is connected to the memory 410 via a bus 430, and the database 450 is used to store data.

[0134] The computing device 400 also includes an access device 440 that enables the computing device 400 to communicate via one or more networks 460. Examples of these networks include a public switched telephone network (PSTN), a local area network (LAN), a wide area network (WAN), a personal area network (PAN), or a combination of communication networks such as the Internet. The access device 440 may include one or more of any type of network interface (e.g., a network interface card (NIC)) wired or wireless, such as an IEEE 802.11 wireless local area network (WLAN) wireless interface, a World Wide Interoperability for Microwave Access (Wi-MAX) interface, an Ethernet interface, a universal serial bus (USB) interface, a cellular network interface, a Bluetooth interface, a near field communication (NFC) interface, and the like.

[0135] In one embodiment of the present specification, the above components of the computing device 400 and Figure 4 Other components not shown in the figure may also be connected to each other, for example, via a bus. It should be understood that Figure 4 The computing device structure block diagram shown is only for the purpose of illustration, and is not intended to limit the scope of this specification. Those skilled in the art can add or replace other components as needed.

[0136] Computing device 400 may be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., a tablet computer, a personal digital assistant, a laptop computer, a notebook computer, a netbook, etc.), a mobile phone (e.g., a smart phone), a wearable computing device (e.g., a smart watch, smart glasses, etc.), or other types of mobile devices, or a stationary computing device such as a desktop computer or PC. Computing device 400 may also be a mobile or stationary server.

[0137] The processor 420 is used to execute the following computer executable instructions, which implement the steps of the above-mentioned label generation method when executed by the processor.

[0138] The above is a schematic scheme of a computing device of this embodiment. It should be noted that the technical scheme of the computing device and the technical scheme of the above-mentioned tag generation method belong to the same concept, and the details not described in detail in the technical scheme of the computing device can be referred to the description of the technical scheme of the above-mentioned tag generation method.

[0139] An embodiment of the present specification further provides a computer-readable storage medium storing computer-executable instructions, which can implement the steps of the above-mentioned label generation method when executed by a processor.

[0140] The above is a schematic scheme of a computer-readable storage medium of this embodiment. It should be noted that the technical scheme of the storage medium and the technical scheme of the above-mentioned tag generation method belong to the same concept, and the details not described in detail in the technical scheme of the storage medium can be referred to the description of the technical scheme of the above-mentioned tag generation method.

[0141] An embodiment of the present specification further provides a computer program, wherein when the computer program is executed in a computer, the computer is caused to execute the steps of the above-mentioned label generation method.

[0142] The above is an illustrative solution of a computer program of this embodiment. It should be noted that the technical solution of the computer program and the technical solution of the above-mentioned tag generation method belong to the same concept, and the details not described in detail in the technical solution of the computer program can be referred to the description of the technical solution of the above-mentioned tag generation method.

[0143] The above is a description of a specific embodiment of the present specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0144] The computer instructions include computer program codes, which may be in source code form, object code form, executable files or some intermediate forms, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, USB flash drive, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium, etc. It should be noted that the content contained in the computer-readable medium may be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media do not include electric carrier signals and telecommunication signals.

[0145] It should be noted that, for the above-mentioned method embodiments, for the sake of simplicity of description, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the embodiments of this specification are not limited by the order of the actions described, because according to the embodiments of this specification, some steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the embodiments of this specification.

[0146] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0147] The preferred embodiments of this specification disclosed above are only used to help explain this specification. The optional embodiments do not describe all the details in detail, nor do they limit the invention to only the specific implementation methods described. Obviously, many modifications and changes can be made according to the content of the embodiments of this specification. This specification selects and specifically describes these embodiments in order to better explain the principles and practical applications of the embodiments of this specification, so that technicians in the relevant technical field can well understand and use this specification. This specification is only limited by the claims and their full scope and equivalents.

Claims

1. A label generation method, comprising: Receive a tag generation request sent by a user, wherein the tag generation request carries attribute information of the user, a tag identifier, and a tag generation condition corresponding to the tag identifier, wherein the tag generation condition is created according to a selection combination of resource information of at least one dimension, a conditional relationship, and a resource attribute value by the user; Determining the cloud resources of the user based on the attribute information of the user; In the case where the cloud resource meets the tag generation condition, setting the tag identifier as a target tag for the cloud resource; Performing resource update detection on a target cloud resource based on a preset time interval, wherein the target cloud resource is a cloud resource with a target tag set; If it is determined that the target cloud resource does not meet the label generation condition, deleting the target label of the target cloud resource; The updated target cloud resource is matched with the tag generation conditions corresponding to other target tags. If it is determined that the updated target cloud resource satisfies the tag generation conditions corresponding to other target tags, the target tag corresponding to the target cloud resource is updated.

2. The tag generation method according to claim 1, wherein determining the cloud resources of the user based on the attribute information of the user comprises: When the cloud resources of the user are created, or if the cloud resources of the user have been created, the available cloud resources of the user are determined based on the attribute information of the user.

3. The tag generation method according to claim 1, after setting the tag identifier as the target tag of the cloud resource, further comprising: When the user creates a new cloud resource, it is determined whether the newly created cloud resource meets the tag generation condition. If so, the tag identifier is set as the target tag of the newly created cloud resource.

4. The tag generation method according to claim 1, after setting the tag identifier as the target tag of the cloud resource, further comprising: When the user's cloud resources are released, the target tag of the cloud resources is deleted.

5. The tag generation method according to claim 1, after setting the tag identifier as the target tag of the cloud resource, further comprising: When the label generation condition changes, it is determined whether the cloud resource meets the changed label generation condition. If yes, the target tag of the cloud resource is not deleted. If not, the target tag of the cloud resource is deleted.

6. The tag generation method according to claim 1, after setting the tag identifier as the target tag of the cloud resource, further comprising: Performing update detection on other cloud resources of the user except the target cloud resource based on a preset time interval, wherein the target cloud resource is a cloud resource with a target tag set; When it is determined that the other cloud resources meet the tag generation condition, the tag identifier is set as a target tag for the other cloud resources.

7. The tag generation method according to any one of claims 1 to 6, wherein the tag generation condition comprises at least one dimension of resource information, conditional relationship, and resource attribute value, wherein: The resource information of at least one dimension includes cost, resource attribute, and performance; the conditional relationship includes include, does not include, is equal to, and is greater than; and the resource attribute value includes a string type, a number type, and a percentage type.

8. A label generating device, comprising: A request receiving module, configured to receive a tag generation request sent by a user, wherein the tag generation request carries attribute information of the user, a tag identifier, and a tag generation condition corresponding to the tag identifier, wherein the tag generation condition is created according to the user's selection of resource information of at least one dimension, a conditional relationship, and a resource attribute value; a cloud resource determination module, configured to determine the cloud resources of the user based on the attribute information of the user; A label generation module, configured to set the label identifier as a target label of the cloud resource if the cloud resource meets the label generation condition; The first resource update module is configured to perform resource update detection on the target cloud resource based on a preset time interval, wherein the target cloud resource is a cloud resource with a target tag set; if it is determined that the target cloud resource does not meet the tag generation condition, delete the target tag of the target cloud resource; match the updated target cloud resource with the tag generation conditions corresponding to other target tags, and if it is determined that the updated target cloud resource meets the tag generation conditions corresponding to other target tags, update the target tag corresponding to the target cloud resource.

9. A label generation system, comprising: The client is used to provide a label condition input method, receive a label identifier and a corresponding label generation condition set by a user through the label condition input method, generate a label generation request, wherein the label generation request carries the attribute information of the user, the label identifier and the label generation condition corresponding to the label identifier, and send the label generation request to the cloud, wherein the label generation condition is created according to the user's selection of resource information, conditional relationship and resource attribute value of at least one dimension; A cloud end, configured to receive the tag generation request, determine the cloud resource of the user based on the attribute information of the user, and set the tag identifier as a target tag of the cloud resource if the cloud resource meets the tag generation condition; Performing resource update detection on a target cloud resource based on a preset time interval, wherein the target cloud resource is a cloud resource with a target tag set; If it is determined that the target cloud resource does not meet the label generation condition, deleting the target label of the target cloud resource; The updated target cloud resource is matched with the tag generation conditions corresponding to other target tags. If it is determined that the updated target cloud resource satisfies the tag generation conditions corresponding to other target tags, the target tag corresponding to the target cloud resource is updated.

10. A computing device comprising: Memory and processor; The memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions. When the computer-executable instructions are executed by the processor, the steps of the label generation method according to any one of claims 1 to 7 are implemented.

11. A computer-readable storage medium storing computer-executable instructions, wherein the computer-executable instructions, when executed by a processor, implement the steps of the label generation method according to any one of claims 1 to 7.

12. A computer program product, characterized in that The method comprises computer instructions, which, when executed by a processor, implement the steps of the label generation method according to any one of claims 1 to 7.

Images