Cloud resource display method and device, program product and storage medium

Abstract

Embodiments of the invention provide a cloud resource display method and device, a program product and a storage medium. The method comprises the steps of obtaining cloud resource description data provided by a user and constructed based on a preset cloud resource description grammar; based on a preset cloud resource description grammar, identifying description information of cloud resources contained in the cloud resource description data and a topological relation between the cloud resources; and based on the identification result, drawing a cloud resource architecture diagram for displaying the description information of the cloud resources and the topological relation between the cloud resources. According to the embodiment, the architecture diagram of the cloud resources of the user can be automatically displayed.

Description

Technical Field

[0001] This manual relates to the field of cloud computing technology, and in particular to cloud resource display methods, devices, program products and storage media. Background Technology

[0002] With the development of cloud computing technology, cloud providers offer users a rich variety of cloud resources. Therefore, users can select the necessary cloud resources to build the required clusters. The cloud resources built by users run in the background; how to help users perceive the various cloud resources they create is a technical problem that urgently needs to be solved. Summary of the Invention

[0003] To overcome the problems existing in related technologies, this manual provides cloud resource display methods, devices, program products and storage media.

[0004] According to a first aspect of the embodiments of this specification, a cloud resource display method is provided, the method comprising:

[0005] Obtain cloud resource description data provided by the user, constructed based on a preset cloud resource description syntax;

[0006] Based on a preset cloud resource description syntax, the description information of cloud resources and the topological relationships between cloud resources contained in the cloud resource description data are identified.

[0007] Based on the identification results, a cloud resource architecture diagram is drawn to display the descriptive information of the cloud resources and the topological relationships between the cloud resources.

[0008] According to a second aspect of the embodiments of this specification, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the method embodiments described in the first aspect above.

[0009] According to a third aspect of the embodiments of this specification, a computer-readable storage medium is provided, on which a computer program is stored, which, when executed by a processor, implements the steps of the method embodiments described in the first aspect above.

[0010] According to a fourth aspect of the embodiments of this specification, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps of the method embodiments described in the first aspect above.

[0011] The technical solutions provided in the embodiments of this specification may include the following beneficial effects:

[0012] In this embodiment, a cloud resource description syntax is pre-defined, enabling users to construct cloud resource description data based on this syntax. Therefore, upon receiving user-provided cloud resource description data, the syntax allows for accurate and rapid identification of the cloud resource description information and topological relationships between the cloud resources. This, in turn, allows for the creation of a cloud resource architecture diagram that displays the description information and topological relationships between the cloud resources. Thus, by drawing the cloud resource architecture diagram, users can perceive the overall architecture of the various cloud resources that were originally running in the background.

[0013] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0014] Figure 1 This is a flowchart illustrating a cloud resource display method according to an exemplary embodiment of this specification.

[0015] Figure 2A This specification illustrates a cloud resource architecture diagram based on an exemplary embodiment.

[0016] Figure 2B This is another cloud resource architecture diagram illustrated in this specification according to an exemplary embodiment.

[0017] Figure 3 This specification is a hardware structure diagram of a computer device housing a cloud resource display device, as illustrated in an exemplary embodiment.

[0018] Figure 4 This is a block diagram illustrating a cloud resource display device according to an exemplary embodiment of this specification. Detailed Implementation

[0019] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this specification. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this specification as detailed in the appended claims.

[0020] The terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to be limiting of this specification. The singular forms “a,” “the,” and “the” as used in this specification and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.

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

[0022] The user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this disclosure are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data shall comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation entry points shall be provided for users to choose to authorize or refuse.

[0023] Currently, cloud vendors offer a wide variety of cloud resources, allowing users to configure various types of cloud resources and specify their types and specifications as needed. These cloud resources run in the background, and research has shown that understanding the architectural topology of cloud resources is a crucial requirement for cloud users, greatly aiding in their comprehensive understanding of the current resource status.

[0024] Based on this, this specification provides a cloud resource display scheme. A cloud resource description syntax can be pre-set, allowing users to construct cloud resource description data based on this syntax. Thus, upon receiving user-provided cloud resource description data, the system can accurately and quickly identify the description information of the cloud resources and the topological relationships between them, based on this syntax. This allows for the creation of a cloud resource architecture diagram to display the description information and topological relationships of the cloud resources. Therefore, users can perceive the overall architecture of the various cloud resources running in the background through the drawn cloud resource architecture diagram. The following is a detailed description of this embodiment.

[0025] like Figure 1 As shown, Figure 1This is a flowchart illustrating a cloud resource display method according to an exemplary embodiment, comprising the following steps:

[0026] In step 102, cloud resource description data constructed by the user based on a preset cloud resource description syntax is obtained.

[0027] In step 104, based on a preset cloud resource description syntax, the description information of cloud resources and the topological relationships between cloud resources contained in the cloud resource description data are identified.

[0028] In step 106, based on the identification results, a cloud resource architecture diagram is drawn to display the descriptive information of the cloud resources and the topological relationships between the cloud resources.

[0029] The data processing methods provided in the embodiments of this specification can be executed by computer devices, including but not limited to physical servers, server clusters, cloud servers, smartphones / mobile phones, tablet computers, personal digital assistants (PDAs), laptop computers, and desktop computers, etc., which are devices with computing capabilities.

[0030] As an example, this method can be applied to a client-side application, where the client uses the method of this embodiment to draw a cloud resource architecture diagram and provide it to the user. Alternatively, it can be applied to a server-side application, where the server uses the method of this embodiment to draw a cloud resource architecture diagram and then provides it to the client for display. Another approach is to apply some steps to the server-side and some steps to the client-side; this embodiment does not limit this approach.

[0031] The cloud resources in this embodiment may include cloud product instances created by users based on cloud services, including but not limited to cloud resources such as Elastic Compute Service (ECS), Elastic High Performance Computing (E-HPC), Entry Summary Declaration (ENS), Function Compute (FC), HBase (Apache HBase), Virtual Private Cloud (VPC), or object storage services. This embodiment does not limit these resources.

[0032] In the field of cloud computing, Infrastructure as Code (IaC) can describe infrastructure using code (such as programming languages, JSON (JavaScript Object Notation, a lightweight data exchange format), YAML (YAML Ain't Markup Language, a format for configuration files), etc.) to present a visual cloud resource architecture diagram on the front end. Therefore, this embodiment designs the cloud resource description syntax in step 102, which can be used to define and describe information about cloud resources and specific syntax rules between cloud resources. The specific syntax can be set according to actual needs; it can be a custom syntax or an extension or modification of existing syntaxes. This embodiment does not limit this.

[0033] Based on this, this embodiment utilizes a cloud resource description syntax, enabling users to provide cloud resource description data written in a programming language. The execution entity of this embodiment can then automatically identify the resource based on this syntax. As an example, the cloud resource description syntax can specify that the description information for each cloud resource includes a resource identifier (ID) and various resource descriptions, or it can specify that each resource ID is followed by a resource description, or it can specify that resources are separated by specific symbols, etc.

[0034] As an example, the cloud resource description syntax can be provided to users so that they can understand the syntax and write cloud resource description data.

[0035] As an example, a function for constructing cloud resource description data can be provided so that users can construct cloud resource description data based on this function; alternatively, users can construct the cloud resource description data themselves and then provide it to the execution entity of this embodiment.

[0036] As an example, the data format of cloud resource description data can be various, such as text, JSON, or YAML, etc. In actual applications, it can be implemented as needed, and this embodiment does not limit it.

[0037] As an example, the cloud resource description syntax in this embodiment can be determined based on the definition syntax of the cloud resources to be created used in the Resource Orchestration Service (ROS). The Resource Orchestration Service is an automated deployment service that simplifies cloud resource management and adopts the IaC design philosophy. Developers and administrators can write templates, defining the required cloud resources (e.g., ECS instances, RDS database instances), dependencies between cloud resources, etc. The orchestration engine in the Resource Orchestration Service will automatically complete the creation and configuration of all resources based on the user-provided templates, achieving automated deployment and operation.

[0038] As an example, the cloud resource description syntax in this embodiment can be implemented based on the syntax used by the resource definition template in the resource orchestration service, thereby obtaining a resource data specification that is consistent with the resource orchestration service.

[0039] As an example, suppose the syntax used by the resource definition template in the resource orchestration service is as follows:

[0040] The Resources: / / identifier is used to indicate the following descriptive information about cloud resources.

[0041] Resource1: / / Resource logical ID, which is unique. Used to locate resources in Resources.

[0042]

[0043] The above syntax can be extended or modified to obtain the cloud resource description syntax of this embodiment. As an example, it can be:

[0044]

[0045] The above example illustrates various descriptive information following the logical ID of a cloud resource. In practical applications, this information can be expanded or modified as needed, and this embodiment does not impose any limitations on it. As an example, some descriptive information may need to be included in the cloud resource description data, while some descriptive information may be optional.

[0046] As can be seen from the above embodiments, cloud resource description data uses a predefined cloud resource description syntax, providing users with a standardized way to express and define cloud resources and their configurations. Through cloud resource description data, descriptive information about cloud resources can be extracted, including resource attributes, configurations, and states. Furthermore, cloud resource description data not only contains information about individual resources but also characterizes the relationships and dependencies between various cloud resources. Therefore, cloud resource description data provides the information needed to draw cloud resource architecture diagrams. Cloud resource architecture diagrams are generated based on the descriptive information and topological relationships in this data, used to visually demonstrate the structure and interactions of cloud resources.

[0047] In some examples, obtaining user-provided cloud resource description data constructed based on a preset cloud resource description syntax may include:

[0048] The cloud resource orchestration service obtains the configuration file of the cloud resource to be deployed by the user through the cloud resource orchestration service interface, and determines the cloud resource description data based on the configuration file; the configuration file is used by the cloud resource orchestration service to deploy the cloud resource.

[0049] In this embodiment, during the use of the cloud resource orchestration service, the user can provide the server with a configuration file of the cloud resource to be deployed. The configuration file is used by the cloud resource orchestration service to deploy the cloud resource. This embodiment can determine the cloud resource description data based on the configuration file. For example, the configuration file can be determined as the cloud resource description data, or the configuration file can be processed, such as format conversion, to determine the cloud resource description data. Thus, during the use of the cloud resource orchestration service, the user can deploy cloud resources and generate a cloud resource architecture diagram at the same time through the configuration file in the cloud resource orchestration service.

[0050] As an example, the description information for each cloud resource may include a logical identifier for the cloud resource and a description following the logical identifier. Each type of description may include a name and a value corresponding to the name. For example, the "Type" mentioned above represents the name of the resource type description information, and the user can write the corresponding value after the colon following "Type".

[0051] In the cloud resource description syntax, the above embodiment uses "Resources" as the preset resource identifier. Following "Resources" is the first-level information, namely the logical ID of the cloud resource. After the logical ID of the cloud resource is the second-level information, namely the description information of each cloud resource. For example:

[0052]

[0053] Following “Resources”, “Resource1” and “Resource2” are the logical identifiers of two cloud resources, located at the first level. “Resource1” contains various descriptive information about the cloud resource, and “Resource2” also contains various descriptive information about the cloud resource.

[0054] Based on this, the above syntax can be used to quickly and accurately identify the description information of cloud resources and the topological relationships between cloud resources contained in the cloud resource description data provided by the user.

[0055] As an example, identifying the descriptive information of cloud resources and the topological relationships between cloud resources contained in the cloud resource description data based on the cloud resource description syntax may include:

[0056] Obtain the text corresponding to the cloud resource description data;

[0057] After identifying the preset resource identifier from the text, the logical identifier of each cloud resource following the preset resource identifier is identified, as well as the descriptive information following the logical identifier of each cloud resource, to further determine the topological relationship between cloud resources.

[0058] Cloud resource description data can be files of various formats. In this embodiment, it can be text corresponding to the cloud resource description data, which consists of multiple characters. For example, taking the preset resource identifier as "Resources" as mentioned above, if the string "Resources" can be identified from the text, it can be determined that the description information of each cloud resource follows this string. If not, the cloud resource description data may be incorrect, and the identification process can be stopped, terminating the execution of this embodiment. After identifying the string "Resources", the logical identifier of each cloud resource following the preset resource identifier can be further identified, as well as the description information following the logical identifier of each cloud resource, to further determine the topological relationship between cloud resources.

[0059] Optionally, the topological relationships between cloud resources can be identified in various ways. For example, identifiers describing the topological relationships can be set, and users can include the topological relationships between cloud resources in the description information of cloud resources based on these identifiers. Alternatively, hierarchical relationships between different types of cloud resources can be pre-defined, thereby identifying the resource type information of each cloud resource. Based on the pre-defined hierarchical relationships between different types of cloud resources, the hierarchical relationships of each cloud resource in the user-provided cloud resource description data can be determined.

[0060] Based on this, this embodiment can accurately identify the description information of cloud resources from cloud resource description data based on cloud resource description syntax.

[0061] In some examples, identifying the descriptive information following the logical identifier of each cloud resource to further determine the topological relationships between cloud resources may include one or more of the following steps:

[0062] Identify the preset resource type identifier after the logical identifier of each cloud resource, and obtain the resource type information located after the preset resource type identifier; if multiple cloud resources have the same resource type information, determine the topological relationship between the multiple cloud resources with the same resource type information as the same level relationship;

[0063] If a first logical identifier of the first cloud resource is identified to be followed by a preset dependency identifier, a second logical identifier located after the preset dependency identifier is obtained, and the topological relationship between the second cloud resource corresponding to the second logical identifier and the first cloud resource is determined as a dependency relationship.

[0064] If a third logical identifier of a third cloud resource is identified, followed by a preset association identifier, a fourth logical identifier is obtained after the preset association identifier, and the topological relationship between the fourth cloud resource corresponding to the fourth logical identifier and the third cloud resource is determined as an association relationship.

[0065] In this embodiment, the logical identifier of each cloud resource can be identified in the cloud resource description data. Then, a preset identifier is searched after these logical identifiers, and then specific information following these identifiers is obtained.

[0066] As an example, the preset resource type identifier can be the string "Type" from the aforementioned embodiments. Following "Type," the user can fill in the type information for each cloud resource. Based on this, this embodiment can identify the resource type information following the preset resource type identifier. If multiple cloud resources have the same resource type information, the topological relationship between these multiple cloud resources with the same resource type information can be determined as a hierarchical relationship. Cloud resources of the same type have similar roles or functions in the architecture and can be managed and displayed at the same level.

[0067] As an example, the preset dependency identifier could be the string "DependsOn" from the aforementioned embodiments. After "DependsOn", the user can fill in the logical identifier of the cloud resource to which it depends. Therefore, if the first cloud resource is identified to have a preset dependency identifier, the second logical identifier following the preset dependency identifier can be obtained. Thus, the topological relationship between the second cloud resource corresponding to the second logical identifier and the first cloud resource can be determined as a dependency relationship, for example, the first cloud resource depends on the second cloud resource.

[0068] As an example, the preset association identifier can be the string "Ref", and the user can fill in the logical identifier of the associated (referenced) cloud resource. Therefore, if a preset association identifier is detected in a third cloud resource, the fourth logical identifier following the preset association identifier can be obtained. Thus, the topological relationship between the fourth cloud resource corresponding to the fourth logical identifier and the third cloud resource can be determined as an association.

[0069] Therefore, this embodiment can automatically extract the types of resources and their topological relationships from cloud resource description data, and then draw a cloud resource architecture diagram based on this information, which can help users understand the configuration, deployment and interrelationships of cloud resources more intuitively.

[0070] As an example, the drawing of a cloud resource architecture diagram to display the descriptive information of the cloud resources and the topological relationships between the cloud resources may include:

[0071] After obtaining the graphic corresponding to each cloud resource, a cloud resource architecture diagram is drawn in a preset canvas based on the graphic, description information, and topological relationship between cloud resources. In the cloud resource architecture diagram, the graphics of each cloud resource at the same level are drawn at the same image height. Among the graphics of cloud resources with dependency relationships, the graphics of child cloud resources that depend on the parent cloud resource are included in the graphics of the parent cloud resource. The graphics of cloud resources with association relationships are connected by lines to represent the association relationship.

[0072] In this embodiment, corresponding graphics can be pre-configured for each cloud resource type. These graphics can be icons, shapes, or other custom visual elements to represent different cloud resource types. The graphics differ between cloud resource types, and the differences may lie in color, shape, size, etc. The graphics of cloud resources can be laid out and drawn on a preset canvas based on the description information of the cloud resources and their topological relationships.

[0073] Cloud resources of the same type usually have the same function and typically play the same role in a user-created cloud resource cluster. Therefore, in this embodiment, the images corresponding to cloud resources with the same hierarchical relationship are drawn at the same image height on the canvas, so that cloud resources with the same hierarchical relationship are located at the same height in the cloud resource architecture diagram, indicating that they are in the same position or have similar functions in the cloud resource architecture diagram.

[0074] For cloud resources with dependencies, such as a sub-cloud resource depending on a parent cloud resource, the creation of the sub-cloud resource may need to be after the creation of the parent cloud resource. Therefore, this embodiment designs the sub-resource's graphic to be drawn within the parent resource's graphic, so as to intuitively show the dependencies between cloud resources.

[0075] For cloud resources with relationships, these graphics can be connected by lines to represent their relationships. Optionally, the lines can be directed or undirected, solid or dashed, etc. Alternatively, different lines can be used to distinguish the relationships between different cloud resources.

[0076] In other examples, the drawing of the cloud resource architecture diagram, used to display the descriptive information of the cloud resources and the topological relationships between the cloud resources, may further include:

[0077] If multiple cloud resources with different resource type information are identified, the hierarchical relationship between the multiple cloud resources with different resource type information is determined based on the preset hierarchical relationship of resource type information, and a cloud resource architecture diagram is drawn.

[0078] In this embodiment, the hierarchical relationship of different cloud resource types can also be pre-configured. For example, gateway-type cloud resources can be located above cloud servers, and cloud storage devices can be located below cloud servers. In practical applications, the hierarchical relationship of various cloud resource types can be configured as needed. Thus, this embodiment can create an accurate and hierarchical cloud resource architecture diagram, helping users better understand and manage cloud resources and the relationships between them.

[0079] Optionally, the cloud resource description data may contain all the descriptive information of the cloud resources, which may be displayed entirely through the cloud resource architecture diagram or only partially.

[0080] As an example, such as Figure 2A The diagram shown is a schematic representation of a cloud resource architecture according to an exemplary embodiment of this specification. Figure 2AIt contains five cloud resources named VPC, VSwitch (virtual switch), SLBLoadBalancer (load balancer), Listener (listener), and ECSInstance (cloud server instance). In the cloud resource architecture diagram, the graphic of each cloud resource includes a corresponding icon and a rounded rectangle. The size of the rounded rectangle is different in the graphic of different cloud resources.

[0081] As an example, the description information of cloud resources can be divided into the following categories:

[0082] Core resource information, such as ResourceId (resource ID) and / or ResourceName (resource name). This core resource information can be directly displayed in the resource's graphical representation within the cloud resource architecture diagram; for example, Figure 2A Taking resource names as an example, the resource name of each cloud resource is displayed in a graphical association with the resource, allowing users to see the resource name of each resource as a whole.

[0083] Basic resource information, such as CreateTime, Tags, ResourceGroupId, and IpAddresses. Users can interact with the cloud resource architecture diagram to view basic information about specific resources. For example, by triggering a graphical representation of a cloud resource in the cloud resource architecture diagram, the basic information of that cloud resource can be displayed in a window. Figure 2B The diagram shown is a schematic diagram of another cloud resource architecture according to an exemplary embodiment of this specification. Taking the user triggering the cloud resource "Load Balancing-APP001" as an example, when the user triggers the cloud resource, a window will be added to the cloud resource architecture diagram to display some basic information of the cloud resource.

[0084] Extended resource information, such as Metrics (monitoring data) and AlertingMetricRules (alarm data), can be presented with more information based on user needs. For example, similar to the basic information display method, extended information can be displayed in an additional window. Alternatively, cloud resources can be highlighted when certain alarm rules are met. For instance, if an alarm rule is not met, the cloud resource's graph might be a certain color (e.g., green), and if the rule is met, the graph might change to another color (e.g., red). This conveys to the user through the cloud resource architecture diagram that the cloud resource is in an alarm state.

[0085] The above Figure 2AThe diagram also illustrates the topological relationships between cloud resources. For example, VSwitch depends on SLBLoadBalancer, Listener, and ECSInstance; therefore, the graph of VSwitch contains the graphs of these three cloud resources. Similarly, VPC depends on VSwitch, and the graph of VPC contains the graph of VSwitch; that is, the graph of VSwitch is located inside the graph of VPC. Furthermore, SLBLoadBalancer is associated with both Listener and ECSInstance; therefore, the graphs of SLBLoadBalancer and Listener are connected by directed edges, and the graphs of ECSInstance are also connected by directed edges.

[0086] The above Figure 2B The diagram also illustrates the topological relationships between cloud resources. For example, the bottom layer of the cloud resource architecture diagram consists of three cloud resources of the same type, which are represented by the same icon. These three icons are located at the same height in the cloud resource architecture diagram, thus visually showing the same hierarchical relationship among the three.

[0087] Optionally, an export function can be added to the cloud resource architecture diagram. For example, if the user triggers the export function, the completed cloud resource architecture diagram can be exported as an image or PDF file.

[0088] In some examples, the descriptive information of the cloud resources shown in the cloud resource architecture diagram includes real-time values ​​of monitoring metrics, and the method further includes:

[0089] If the cloud resource description data is found to contain a preset monitoring indicator identifier, the monitoring indicator to be displayed is determined based on the monitoring indicator description information following the preset monitoring indicator identifier.

[0090] The real-time values ​​of the monitoring indicators are obtained through the preset interfaces corresponding to the monitoring indicators; the real-time values ​​are used to update and display the cloud resource architecture diagram based on a preset period.

[0091] In this embodiment, considering that some information in actual cloud resources is dynamically changing, such as some monitoring metrics that users are concerned about, the cloud resource architecture diagram can also dynamically display this descriptive information. Based on this, this embodiment designs a preset monitoring metric identifier, such as a string like "Metrics". After identifying the preset monitoring metric identifier from the cloud resource description data, the monitoring metric description information that follows it can be identified, thereby determining the monitoring metric to be displayed; for example, the monitoring metric description information may include the name of the monitoring metric and the value of the monitoring metric.

[0092] As an example, monitoring metrics may include CPU utilization, memory usage, network traffic, etc., and this embodiment does not limit these. Since the values ​​of cloud resource monitoring metrics can change in real time, this embodiment can obtain the real-time values ​​of the monitoring metrics through the preset interfaces corresponding to the monitoring metrics, and thus update and display the real-time values ​​in the cloud resource architecture diagram based on a preset period. The preset period may be 10 seconds, 1 minute, or 5 minutes, etc., and this embodiment does not limit these.

[0093] As an example, there are several ways to obtain the interface address of the preset interface corresponding to the monitoring metric. For instance, it can be provided by the cloud service provider, allowing the user to obtain the interface address of the monitoring metric for that cloud resource. Alternatively, the user can include the interface address in the cloud resource description data, thus identifying the interface address of the monitoring metric from the cloud resource description data. Optionally, the preset interface corresponding to the monitoring metric can be called according to a preset period to obtain the real-time value of the monitoring metric. Optionally, the monitoring metric description information includes the name and value of the monitoring metric. The value of the monitoring metric included in the monitoring metric description information can be updated by calling the preset interface corresponding to the monitoring metric, thereby drawing the cloud resource architecture diagram based on the updated monitoring metric value.

[0094] As can be seen from the above embodiments, the cloud resource architecture diagram not only shows the topology of the resources, but also provides real-time values ​​of cloud resource monitoring indicators, enabling users to have a more comprehensive understanding and management of the status of cloud resources.

[0095] In some examples, the method may also include:

[0096] Based on the monitoring indicator description information following the preset monitoring indicator identifier, alarm rules are determined.

[0097] In response to determining that the real-time value of the monitoring indicator conforms to the alarm rule, an alarm message is output to the user.

[0098] In this embodiment, the monitoring metric description information may also include alarm rules. These alarm rules can be set by the user and included in the cloud resource description data. Optionally, a preset alarm rule identifier can be designed, such as a custom string like "AlertingMetricRules". After identifying the preset alarm rule identifier contained in the monitoring metric description information from the cloud resource description data, the specific alarm rules following it can be identified. Optionally, the monitoring metric description information may contain one or more alarm rules. In the case of multiple alarm rules, they can be distinguished using different alarm rules.

[0099] As an example, let's set up alarm rules for the CPU utilization of an ECS instance. Specifically, the alarm rule could be: the maximum CPU utilization for three consecutive preset periods is greater than or equal to 85%. Based on this, after obtaining the real-time values ​​of the monitoring metrics, the real-time values ​​can be compared with the preset alarm rules to determine whether an alarm should be triggered. For example, when the CPU utilization is greater than 85% for three consecutive periods, an alarm is triggered. As an example, an alarm message can be output in the cloud resource architecture diagram. Besides the cloud resource architecture diagram, alarm messages can also be output to users through other methods.

[0100] As can be seen from the above embodiments, this embodiment allows users to set alarm rules. When the real-time values ​​of the monitoring indicators meet these preset alarm rules, alarm messages can be output in the cloud resource architecture diagram, enabling users to understand the operating status of cloud resources in a timely manner and take corresponding measures when viewing the cloud resource architecture diagram.

[0101] The following example illustrates cloud resource description data. The content following the symbol " / / " represents a comment.

[0102] Resources:

[0103] ECSInstance_001: / / is the logical ID of the cloud resource, which is unique. It can be set as a required field and is used to locate each cloud resource in Resources.

[0104] ResourceType:ALIYUN::ECS::Instance / / Resource type, can be set as required.

[0105] ResourceId: i-xxx / / The actual ID of the resource, i.e., the resource ID in the corresponding cloud product. This can be set as a required field.

[0106]

[0107]

[0108] The cloud resource description data above includes two cloud resources with logical IDs ECSInstance_001 and ECSVSwitch_001. For ECSInstance_001, its resource properties include a switch VSwitchID, which uses the "Ref" identifier to indicate the referenced cloud resource ECSVSwitch_001. Therefore, it can be determined that cloud resource ECSInstance_001 depends on cloud resource ECSVSwitch_001, and cloud resource ECSInstance_001 can only be created after cloud resource ECSVSwitch_001 is created.

[0109] In addition, the cloud resource ECSInstance_001 uses the identifier "Metrics" to describe two monitoring metrics: CPU average utilization (cpu_total) and memory utilization (memory_usedutilization). Furthermore, the identifier "AlertingMetricRules" describes the corresponding alarm rules for these monitoring metrics.

[0110] As can be seen from the above embodiments, this embodiment designs cloud resource description data based on the IaC concept. This data is compatible with the ROS template syntax in resource orchestration and can be a superset of the ROS template syntax, i.e., it includes the ROS template syntax but extends it with more syntax rules. It has good scalability and can be extended on the data plane, such as displaying monitoring data of cloud resources. In addition, integrators or users can customize resource topology and fine-grained control topology by generating their own data, thereby overcoming the inherent shortcomings of products like CloudSpeed ​​that do not expose data.

[0111] Corresponding to the aforementioned embodiments of the cloud resource display method, this specification also provides embodiments of the cloud resource display device and the computer equipment used thereon.

[0112] The embodiments of the cloud resource display device described in this specification can be applied to computer devices, such as servers or terminal devices. The device embodiments can be implemented through software, hardware, or a combination of both. Taking software implementation as an example, as a logical device, it is formed by its processor reading the corresponding computer program instructions from non-volatile memory into memory for execution. From a hardware perspective, such as... Figure 3 The diagram shown is a hardware structure diagram of the computer equipment containing the cloud resource display device described in this manual, including... Figure 3The processor 310, network interface 320, memory 330, and non-volatile memory 340 shown indicate that the computer program instructions corresponding to the cloud resource display device can be stored in memory, and the processor 310 can read and execute the computer program instructions from memory. In addition, the computer device housing the cloud resource display device in this embodiment may also include other hardware depending on the actual functions of the computer device, which will not be elaborated further.

[0113] like Figure 4 As shown, Figure 4 This is a block diagram illustrating a cloud resource display device according to an exemplary embodiment of this specification. The device includes:

[0114] The acquisition module 41 is used to: acquire cloud resource description data provided by the user and constructed based on a preset cloud resource description syntax;

[0115] The identification module 42 is used to: identify the description information of cloud resources and the topological relationship between cloud resources contained in the cloud resource description data based on the cloud resource description syntax.

[0116] The drawing module 43 is used to: draw a cloud resource architecture diagram based on the recognition results to display the descriptive information of the cloud resources and the topological relationship between the cloud resources.

[0117] In some examples, the identification module 42 is also used for:

[0118] Obtain the text corresponding to the cloud resource description data;

[0119] After identifying the preset resource identifier from the text, the logical identifier of each cloud resource following the preset resource identifier is identified, as well as the descriptive information following the logical identifier of each cloud resource, to further determine the topological relationship between cloud resources.

[0120] In some examples, the identification module 42 is also used for:

[0121] Identify the preset resource type identifier after the logical identifier of each cloud resource, and obtain the resource type information located after the preset resource type identifier; if multiple cloud resources have the same resource type information, determine the topological relationship between the multiple cloud resources with the same resource type information as the same level relationship;

[0122] If a first logical identifier of the first cloud resource is identified to be followed by a preset dependency identifier, a second logical identifier located after the preset dependency identifier is obtained, and the topological relationship between the second cloud resource corresponding to the second logical identifier and the first cloud resource is determined as a dependency relationship.

[0123] If a third logical identifier of a third cloud resource is identified, followed by a preset association identifier, a fourth logical identifier is obtained after the preset association identifier, and the topological relationship between the fourth cloud resource corresponding to the fourth logical identifier and the third cloud resource is determined as an association relationship.

[0124] In some examples, the drawing module 43 is also used for:

[0125] After obtaining the graphic corresponding to each cloud resource, a cloud resource architecture diagram is drawn in a preset canvas based on the graphic, description information, and topological relationship between cloud resources. In the cloud resource architecture diagram, the graphics of each cloud resource at the same level are drawn at the same image height. Among the graphics of cloud resources with dependency relationships, the graphics of child cloud resources that depend on the parent cloud resource are included in the graphics of the parent cloud resource. The graphics of cloud resources with association relationships are connected by lines to represent the association relationship.

[0126] In some examples, the drawing module 43 is also used for:

[0127] If multiple cloud resources with different resource type information are identified, the hierarchical relationship between the multiple cloud resources with different resource type information is determined based on the preset hierarchical relationship of resource type information, and a cloud resource architecture diagram is drawn.

[0128] In some examples, the cloud resource description information shown in the cloud resource architecture diagram includes real-time values ​​of monitoring metrics, and the identification module 42 is further used for:

[0129] If the description information of the target cloud resource is found to contain a preset monitoring indicator identifier, the monitoring indicator to be displayed is determined based on the monitoring indicator description information following the preset monitoring indicator identifier.

[0130] The real-time values ​​of the monitoring indicators are obtained through the preset interfaces corresponding to the monitoring indicators; the real-time values ​​are used to update and display the cloud resource architecture diagram based on a preset period.

[0131] In some examples, the device further includes an output module for:

[0132] Based on the monitoring indicator description information following the preset monitoring indicator identifier, alarm rules are determined.

[0133] In response to determining that the real-time value of the monitoring indicator conforms to the alarm rule, an alarm message is output in the cloud resource architecture diagram.

[0134] In some examples, the acquisition module 41 is also used for:

[0135] The cloud resource orchestration service obtains the configuration file of the cloud resource to be deployed by the user through the cloud resource orchestration service interface, and determines the cloud resource description data based on the configuration file; the configuration file is used by the cloud resource orchestration service to deploy the cloud resource.

[0136] The specific implementation process of the functions and roles of each module in the cloud resource display device can be found in the implementation process of the corresponding steps in the cloud resource display method, and will not be repeated here.

[0137] Accordingly, this specification also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the aforementioned cloud resource display method embodiment.

[0138] Accordingly, this specification also provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the steps of the cloud resource display method embodiment.

[0139] Accordingly, embodiments of this specification also provide a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of the cloud resource display method embodiments.

[0140] For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to in the description of the method embodiments. The device embodiments described above are merely illustrative. The modules described as separate components may or may not be physically separate, and the components shown as modules may or may not be physical modules, that is, they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of the solution in this specification according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0141] The above embodiments can be applied to one or more computer devices. The computer device is a device that can automatically perform numerical calculations and / or information processing according to pre-set or stored instructions. The hardware of the computer device includes, but is not limited to, microprocessors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital signal processors (DSPs), embedded devices, etc.

[0142] The computer device can be any electronic product that can interact with the user, such as a personal computer, tablet computer, smartphone, personal digital assistant (PDA), game console, interactive network television (IPTV), smart wearable device, etc.

[0143] The computer equipment may also include network equipment and / or user equipment. The network equipment includes, but is not limited to, a single network server, a server group consisting of multiple network servers, or a cloud based on cloud computing consisting of a large number of hosts or network servers.

[0144] The network in which the computer device is located includes, but is not limited to, the Internet, wide area network, metropolitan area network, local area network, and virtual private network (VPN).

[0145] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0146] The steps of the various methods described above are only for clarity. In practice, they can be combined into one step or some steps can be split into multiple steps. As long as they include the same logical relationship, they are all within the scope of protection of this patent. Adding insignificant modifications or introducing insignificant designs to the algorithm or process, but without changing the core design of the algorithm and process, are also within the scope of protection of this application.

[0147] While this specification contains numerous specific implementation details, these should not be construed as limiting the scope of any invention or the scope of the claims, but rather are primarily intended to describe features of specific embodiments of a particular invention. Certain features described in the various embodiments herein may also be implemented in combination in a single embodiment. Conversely, various features described in a single embodiment may also be implemented separately in various embodiments or in any suitable sub-combination. Furthermore, while features may function in certain combinations as described above and even initially claimed in this way, one or more features from a claimed combination may be removed from that combination in some cases, and a claimed combination may refer to a sub-combination or a variation thereof.

[0148] The terms "specific example" or "some examples," etc., refer to specific features, structures, materials, or characteristics described in connection with the embodiments or examples, which are included in at least one embodiment or example of this specification. In this specification, illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0149] Other embodiments of this specification will readily occur to those skilled in the art upon consideration of the specification and practice of the invention claimed herein. This specification is intended to cover any variations, uses, or adaptations that follow the general principles of this specification and include common knowledge or customary techniques in the art not claimed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this specification are indicated by the following claims.

[0150] It should be understood that this specification is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this specification is limited only by the appended claims.

[0151] The above description is merely a preferred embodiment of this specification and is not intended to limit this specification. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this specification should be included within the scope of protection of this specification.

Claims

1. A method for displaying cloud resources, the method comprising: Obtain cloud resource description data provided by the user, constructed based on a preset cloud resource description syntax; Based on the cloud resource description syntax, identify the description information of cloud resources and the topological relationships between cloud resources contained in the cloud resource description data; Based on the identification results, a cloud resource architecture diagram is drawn to display the descriptive information of the cloud resources and the topological relationships between the cloud resources.

2. The method according to claim 1, wherein identifying the description information of cloud resources and the topological relationships between cloud resources contained in the cloud resource description data based on the cloud resource description syntax includes: Obtain the text corresponding to the cloud resource description data; After identifying the preset resource identifier from the text, the logical identifier of each cloud resource following the preset resource identifier is identified, as well as the descriptive information following the logical identifier of each cloud resource, to further determine the topological relationship between cloud resources.

3. The method according to claim 2, wherein identifying the description information following the logical identifier of each cloud resource, and further determining the topological relationship between cloud resources, includes one or more of the following steps: Identify the preset resource type identifier after the logical identifier of each cloud resource, and obtain the resource type information located after the preset resource type identifier; if multiple cloud resources have the same resource type information, determine the topological relationship between the multiple cloud resources with the same resource type information as the same level relationship; If a first logical identifier of the first cloud resource is identified to be followed by a preset dependency identifier, a second logical identifier located after the preset dependency identifier is obtained, and the topological relationship between the second cloud resource corresponding to the second logical identifier and the first cloud resource is determined as a dependency relationship. If a third logical identifier of a third cloud resource is identified, followed by a preset association identifier, a fourth logical identifier is obtained after the preset association identifier, and the topological relationship between the fourth cloud resource corresponding to the fourth logical identifier and the third cloud resource is determined as an association relationship.

4. The method according to claim 3, wherein drawing a cloud resource architecture diagram to display the descriptive information of the cloud resources and the topological relationships between the cloud resources includes: After obtaining the graphic corresponding to each cloud resource, a cloud resource architecture diagram is drawn in a preset canvas based on the graphic, description information, and topological relationship between cloud resources. In the cloud resource architecture diagram, the graphics of each cloud resource at the same level are drawn at the same image height. Among the graphics of cloud resources with dependency relationships, the graphics of child cloud resources that depend on the parent cloud resource are included in the graphics of the parent cloud resource. The graphics of cloud resources with association relationships are connected by lines to represent the association relationship.

5. The method according to claim 4, wherein drawing a cloud resource architecture diagram for displaying the descriptive information of the cloud resources and the topological relationships between the cloud resources further includes: If multiple cloud resources with different resource type information are identified, the hierarchical relationship between the multiple cloud resources with different resource type information is determined based on the preset hierarchical relationship of resource type information, and a cloud resource architecture diagram is drawn.

6. The method according to claim 1, wherein the descriptive information of the cloud resources displayed in the cloud resource architecture diagram includes real-time values ​​of monitoring metrics, and the method further includes: If the cloud resource description data is found to contain a preset monitoring indicator identifier, the monitoring indicator to be displayed is determined based on the monitoring indicator description information following the preset monitoring indicator identifier. The real-time value of the monitoring indicator is obtained through the preset interface corresponding to the monitoring indicator; The real-time values ​​are used to update and display the cloud resource architecture diagram based on a preset period.

7. The method according to claim 6, further comprising: Based on the monitoring indicator description information following the preset monitoring indicator identifier, alarm rules are determined. In response to determining that the real-time value of the monitoring indicator conforms to the alarm rule, an alarm message is output in the cloud resource architecture diagram.

8. The method according to claim 1, wherein obtaining cloud resource description data constructed based on a preset cloud resource description syntax provided by the user includes: The configuration file of the cloud resource to be deployed by the user is obtained through the cloud resource orchestration service interface, and the description data of the cloud resource is determined based on the configuration file; The configuration file is used for deploying cloud resources using the cloud resource orchestration service.

9. A computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 8.

10. A computer program product comprising a computer program that, when executed by a processor, implements the steps of the method according to any one of claims 1 to 8.

11. A computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method according to any one of claims 1 to 8.

Images