Component deployment method and apparatus, device, storage medium, and program product

Abstract

The present disclosure provides a component deployment method and apparatus, a device, a storage medium, and a program product. The method comprises: in response to a deployment instruction for a target component, acquiring a component configuration file of the target component, the component configuration file being obtained by configuring a target component template; determining at least one node in a cluster on the basis of the component configuration file; and deploying the target component in a target component node on the basis of the component configuration file and the at least one node, the at least one node comprising the target component node. The component deployment efficiency is improved.

Description

[0001] Component deployment method, device, equipment, storage medium and program product The present disclosure claims priority to Chinese patent application No. 202410867083.8, filed on June 28, 2024 with the Chinese Patent Office, entitled "Component deployment method, device, equipment, storage medium and program product", the entire content of which is incorporated herein by reference. TECHNICAL FIELD The present disclosure relates to the field of computers, and in particular to a component deployment method, device, equipment, storage medium and program product. BACKGROUND A cluster can include multiple nodes (e.g., physical servers or virtual machines, etc.). A user can expand and deploy different components on the cluster (e.g., a high-performance computing (HPC) cluster) to enable the cluster to provide different services. With the continuous rise of cloud computing and artificial intelligence, HPC cluster deployment and use are becoming more and more widespread, and the scene is becoming more and more rich, and different industries require more and more diversified software and services integrated on the HPC cluster. In the related art, due to the diversification and differentiation of various industry software and services, each component is manually deployed in the cluster (including installing each component and configuring related services, etc.). However, in the above manner, manual deployment of each component usually involves a large number of repetitive and tedious operations, resulting in low efficiency of deploying components. SUMMARY Aspects of the present disclosure provide a component deployment method, device, equipment, storage medium and program product to solve the problem of low efficiency of deploying components. In a first aspect, an embodiment of the present disclosure provides a component deployment method, comprising: in response to a deployment instruction of a target component, obtaining a component configuration file of the target component, the component configuration file being obtained by configuring a target component template; determining at least one node in a cluster according to the component configuration file; and deploying the target component in a target component node according to the component configuration file and the at least one node, the at least one node including the target component node. In a possible implementation, deploying the target component in the target component node according to the component configuration file and the at least one node comprises: performing parsing processing on the component configuration file to obtain cluster configuration information, resource configuration information, and component service configuration information; and deploying the target component according to the cluster configuration information, the resource configuration information, the component service configuration information, and the at least one node, the cluster configuration information being used to configure the target component node, the resource configuration information being used to deploy component resources corresponding to the target component, and the component service configuration information being used to deploy the target component.In a possible implementation, the deploying the target component in the target component node according to the cluster configuration information, the resource configuration information, the component service configuration information, and the at least one node includes: deploying component resources corresponding to the target component according to the resource configuration information; if the target component node is not included in the cluster, performing configuration processing on the target component node according to the cluster configuration information, so as to add the target component node to the cluster; and deploying the target component in the target component node according to the component service configuration information and the component resources. In a possible implementation, the component service configuration information includes a first download address corresponding to a target component installation package and a second download address corresponding to a target component script; and the deploying the target component in the target component node according to the component service configuration information and the component resources includes: downloading the target component installation package through the target component node according to the first download address; downloading the target component script through the target component node according to the second download address; and executing the target component script through the target component node, so as to deploy the target component in the target component node according to the target component installation package. In a possible implementation, the cluster configuration information includes types and versions of at least one object; and the configuration processing on the target component node according to the cluster configuration information includes: for any one object, determining, through the target component node, an object installation package and an object script corresponding to the object according to the type and the version of the object; and installing, through the target component node, the object installation package according to the execution of the object script, so as to perform the configuration processing on the target component node. In a possible implementation, the at least one node includes a target scheduling node; and the method further includes: determining, through the target component node, the target scheduling node; sending, through the target component node, a node joining request to the target scheduling node, the node joining request including an identifier of the target component node and object-related information of the at least one object; and receiving, through the target component node, a node joining response corresponding to the node joining request and sent by the target scheduling node. In a possible implementation, the resource configuration information includes at least one instance configuration information, at least one network address, and a network address allocation strategy; and the deploying the component resources corresponding to the target component according to the resource configuration information includes: creating at least one instance according to the at least one instance configuration information; and configuring network addresses for the at least one instance according to the at least one network address and the network address allocation strategy, so as to deploy the component resources, the component resources including the at least one instance.In a possible implementation, the component configuration file further includes general service configuration information, and the general service configuration information includes configuration information of at least one general service; the method further includes: for any one of the general services, determining, in the configuration information of the general service, an interface corresponding to the general service; and invoking the general service through the interface to deploy a general service required by the target component. In a possible implementation, the method further includes: obtaining a service request corresponding to the target component, and determining a request type of the service request, the request type including a non-resource application type and a resource application type; and processing the service request according to the request type. In a possible implementation, the request type is the non-resource application type; and processing the service request according to the request type includes: determining a corresponding request result according to the service request; and sending the request result to the user equipment. In a possible implementation, the request type is the resource application type; and processing the service request according to the request type includes: obtaining a resource configuration parameter of a target task in the service request; sending the resource configuration parameter to a target scheduling node, so that the target scheduling node determines at least one computing node according to the resource configuration parameter; and invoking the at least one computing node to perform computing processing on the target task. In a possible implementation, the method further includes: in response to a creation instruction or a selection instruction, obtaining the target component template, the creation instruction being used to create the target component template, and the selection instruction being used to obtain the target component template; and in response to a configuration instruction for the target component template, performing configuration processing on the target component template to obtain the component configuration file, and saving the component configuration file. In a possible implementation, the method further includes: in response to an update configuration instruction, performing update configuration processing on the component configuration file to obtain an update configuration file; and performing update processing on the target component according to the update configuration file. In a possible implementation, the method further includes: receiving a first state query request sent by user equipment, the first state query request including an identifier of the target component node and an identifier of the target component; sending a second state query request to the target component node according to the identifier of the target component node, the second state query request including the identifier of the target component; receiving a second query result corresponding to the second state query request sent by the target component node, and determining the second query result as a first query result corresponding to the first state query request; and sending the first query result to the user equipment.In a possible implementation, the method further includes: receiving a first operation request sent by a user device, the first operation request including an identifier of the target component node, an identifier of the target component, and an identifier of a target operation; sending a second operation request to the target component node according to the identifier of the target component node, the second operation request including the identifier of the target component and the identifier of the target operation; receiving a second operation result sent by the target component node, and determining the second operation result as a first operation result corresponding to the first operation request, the second operation result being an operation result obtained by the target component node performing the target operation on the target component according to the identifier of the target operation; and sending the first operation result to the user device. In a possible implementation, the method further includes: receiving a first unloading request sent by a user device, the first unloading request including an identifier of the target component node and an identifier of the target component; sending a second unloading request to the target component node according to the identifier of the target component node, the second unloading request including the identifier of the target component; receiving a second unloading result corresponding to the second unloading request sent by the target component node, and determining the second unloading result as a first unloading result corresponding to the first unloading request; and sending the first unloading result to the user device. In a second aspect, an embodiment of the present disclosure provides a component deployment apparatus, the apparatus including: a first obtaining module, a determining module, and a deployment module, wherein the first obtaining module is configured to: in response to a deployment instruction of a target component, obtain a component configuration file of the target component, the component configuration file being obtained by configuring a target component template; the determining module is configured to: according to the component configuration file, determine at least one node in a cluster; and the deployment module is configured to: according to the component configuration file and the at least one node, deploy the target component in a target component node, the at least one node including the target component node. In a possible implementation, the deployment module is specifically configured to: perform parsing processing on the component configuration file to obtain cluster configuration information, resource configuration information, and component service configuration information, the cluster configuration information being used to configure the target component node, the resource configuration information being used to deploy a component resource corresponding to the target component, and the component service configuration information being used to deploy the target component; and deploy the target component in the target component node according to the cluster configuration information, the resource configuration information, the component service configuration information, and the at least one node.In a possible implementation, the deployment module is specifically configured to: deploy component resources corresponding to the target component according to the resource configuration information; if the target component node is not included in the cluster, perform configuration processing on the target component node according to the cluster configuration information, so as to add the target component node to the cluster; and deploy the target component in the target component node according to the component service configuration information and the component resources. In a possible implementation, the component service configuration information includes a first download address corresponding to a target component installation package and a second download address corresponding to a target component script; and the deployment module is specifically configured to: download the target component installation package through the target component node according to the first download address; download the target component script through the target component node according to the second download address; and execute the target component script through the target component node, so as to deploy the target component in the target component node according to the target component installation package. In a possible implementation, the cluster configuration information includes types and versions of at least one object; the at least one node includes a target scheduling node; and the deployment module is specifically configured to: for any one object, determine an object installation package and an object script corresponding to the object through the target component node according to the type and the version of the object; and install the object installation package through the target component node by executing the object script through the target component node, so as to perform configuration processing on the target component node. In a possible implementation, the deployment module is further configured to: determine the target scheduling node through the target component node; send a node joining request to the target scheduling node through the target component node, the node joining request including an identifier of the target component node and object-related information of the at least one object; and receive a node joining response corresponding to the node joining request sent by the target scheduling node through the target component node. In a possible implementation, the resource configuration information includes at least one instance configuration information, at least one network address, and a network address allocation strategy; and the deployment module is specifically configured to: create at least one instance according to the at least one instance configuration information; and configure network addresses for the at least one instance according to the at least one network address and the network address allocation strategy, so as to deploy the component resources, the component resources including the at least one instance.In a possible implementation, the component configuration file further includes general service configuration information, and the general service configuration information includes configuration information of at least one general service; and the deployment module is specifically configured to: for any one of the general services, determining, in the configuration information of the general service, an interface corresponding to the general service; and invoking the general service through the interface, to deploy a general service required by the target component. In a possible implementation, the apparatus further includes a second acquisition module and a configuration module, where the second acquisition module is configured to: in response to a creation instruction or a selection instruction, acquire the target component template, the creation instruction being used to create the target component template, and the selection instruction being used to acquire the target component template; and the configuration module is configured to: in response to a configuration instruction for the target component template, perform configuration processing on the target component template, to obtain the component configuration file, and save the component configuration file. In a possible implementation, the apparatus further includes an update module, which is configured to: in response to an update configuration instruction, perform update configuration processing on the component configuration file, to obtain an update configuration file; and perform update processing on the target component according to the update configuration file. In a possible implementation, the apparatus further includes a receiving module and a sending module, where the receiving module is configured to: receive a first state query request sent by a user device, the first state query request including an identifier of the target component node and an identifier of the target component; the sending module is configured to: according to the identifier of the target component node, send a second state query request to the target component node, the second state query request including the identifier of the target component; the receiving module is further configured to: receive a second query result corresponding to the second state query request sent by the target component node, and determine the second query result as a first query result corresponding to the first state query request; and the sending module is further configured to: send the first query result to the user device.In a possible implementation, the receiving module is further configured to receive a first operation request sent by a user equipment, the first operation request comprising an identifier of the target component node, an identifier of the target component, and an identifier of a target operation; the sending module is further configured to send, according to the identifier of the target component node, a second operation request to the target component node, the second operation request comprising the identifier of the target component and the identifier of the target operation; the receiving module is further configured to receive a second operation result corresponding to the second operation request sent by the target component node, and determine the second operation result as a first operation result corresponding to the first operation request, the second operation result being an operation result obtained by the target component node performing the target operation on the target component according to the identifier of the target operation; and the sending module is further configured to send the first operation result to the user equipment. In a possible implementation, the receiving module is further configured to receive a first unloading request sent by a user equipment, the first unloading request comprising an identifier of the target component node and an identifier of the target component; the sending module is further configured to send, according to the identifier of the target component node, a second unloading request to the target component node, the second unloading request comprising the identifier of the target component; the receiving module is further configured to receive a second unloading result corresponding to the second unloading request sent by the target component node, and determine the second unloading result as a first unloading result corresponding to the first unloading request; and the sending module is further configured to send the first unloading result to the user equipment. In a third aspect, an embodiment of the present disclosure provides a component usage apparatus, which comprises: a third obtaining module and a processing module, the third obtaining module is configured to obtain a service request corresponding to the target component, and determine a request type of the service request, the request type comprising a non-resource application type and a resource application type; and the processing module is configured to process the service request according to the request type. In a possible implementation, the request type is the non-resource application type; and the processing module is specifically configured to: determine a request result corresponding to the service request; and send the request result to a user equipment. In a possible implementation, the request type is the resource application type, and the service request comprises resource configuration parameters of a target task; and the processing module is specifically configured to: obtain the resource configuration parameters of the target task in the service request; send the resource configuration parameters to a target scheduling node, so that the target scheduling node determines at least one computing node according to the resource configuration parameters; and invoke the at least one computing node to process the target task.In a fourth aspect, an embodiment of the present disclosure provides a management and control server, comprising: a memory and a processor; the memory stores computer-executable instructions; and the processor executes the computer-executable instructions stored in the memory, so that the processor executes the method in any one of the first aspect. In a fifth aspect, an embodiment of the present disclosure provides an assembly deployment system, the system comprising a user device and a management and control server, wherein the management and control server is configured to execute the method in any one of the first aspect. In a sixth aspect, an embodiment of the present disclosure provides a computer-readable storage medium, the computer-readable storage medium storing computer-executable instructions, the computer-executable instructions being configured to implement the method in any one of the first aspect when executed by a processor. In a seventh aspect, an embodiment of the present disclosure provides a computer program product, comprising a computer program, the computer program being configured to implement the method in any one of the first aspect when executed by a processor. The assembly deployment method, device, equipment, storage medium and program product provided by the embodiments of the present disclosure, the management and control server can respond to the deployment instruction of the target assembly, obtain the component configuration file of the target assembly, and determine at least one node in the cluster according to the component configuration file, and then deploy the target assembly in the target assembly node according to the component configuration file and the at least one node. Since the management and control server can automatically deploy the target assembly in the target assembly node in the cluster according to the component configuration file, human intervention is not required for deployment, which not only saves manpower, but also improves the efficiency of deploying the assembly. Moreover, since the component template is replicable and extensible, the component configuration file is obtained based on the target assembly template, which improves the efficiency and convenience of obtaining the component configuration file. BRIEF DESCRIPTION OF DRAWINGS The accompanying drawings described herein are used to provide further understanding of the present disclosure, constitute a part of the present disclosure, and are used to explain the illustrative embodiments of the present disclosure and their descriptions, and do not constitute an improper limitation on the present disclosure.In the drawings: Fig. 1 is a schematic diagram of a related art; Fig. 2 is a schematic diagram of another related art; Fig. 3 is a schematic diagram of a scenario according to an example embodiment of the present disclosure; Fig. 4 is a system architecture diagram according to an example embodiment of the present disclosure; Fig. 5 is a technical comparison diagram according to an example embodiment of the present disclosure; Fig. 6 is a flow diagram of a component deployment method according to an example embodiment of the present disclosure; Fig. 7 is a flow diagram of another component deployment method according to an example embodiment of the present disclosure; Fig. 8 is a flow diagram of a target component usage method according to an example embodiment of the present disclosure; Fig. 9 is a schematic diagram of a component-related process according to an example embodiment of the present disclosure; Fig. 10 is a structural diagram of a component deployment apparatus according to an example embodiment of the present disclosure; Fig. 11 is a structural diagram of another component deployment apparatus according to an example embodiment of the present disclosure; Fig. 12 is a structural diagram of a component usage apparatus according to an example embodiment of the present disclosure; Fig. 13 is a structural diagram of a management and control server according to an example embodiment of the present disclosure; Fig. 14 is a schematic diagram of a component deployment system according to an example embodiment of the present disclosure; Fig. 15 is a schematic diagram of another component deployment system according to an example embodiment of the present disclosure. It needs to be noted that, the user information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in the present disclosure are all information and data authorized by the user or authorized by all parties, and the collection, use and processing of the related data need to comply with relevant laws, regulations and standards, and provide corresponding operation portal for the user to select authorization or refusal. In order to make the purpose, technical scheme and advantages of the present disclosure clearer, the technical scheme of the present disclosure will be described clearly and completely in combination with specific embodiments of the present disclosure and corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present disclosure, not all the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by those of ordinary skill in the art without creative labor belong to the scope of protection of the present disclosure. In the following, in order to facilitate the understanding of the technical scheme of the present disclosure, the concepts involved in the present disclosure are first explained.

[0002] (1) Component: an independent deployment unit in a software system, encapsulating a combination of data, objects and methods.

[0003] (2) Infrastructure as Code (IaC): A method of managing and configuring IT infrastructure through writing code. Through this method, the definition and configuration of infrastructure can be version-controlled, automatically deployed, and continuously integrated as code, so as to realize the repeatability, manageability, and scalability of infrastructure, which can help organizations more efficiently manage and configure their IT infrastructure, and improve the stability, reliability, and security of the system.

[0004] (3) Scheduler: The core component of HPC cluster responsible for job management and computing resource scheduling and allocation.

[0005] (4) Account Management: The identity verification service in HPC cluster, responsible for centralized control of user access to cluster resources and allocation of permissions.

[0006] (5) Network Address Translation (NAT) Gateway: Network address translation service, providing NAT proxy capabilities, such as Source Network Address Translation (SNAT) and Destination Network Address Translation (DNAT).

[0007] (6) Cluster Management Node: The management node of the entire cluster, also known as the head node. The cluster management node can be used to deploy scheduler jobs and resource management services, user management services, data management services, etc. This node is unique in the cluster, and new computing nodes and target component nodes in the cluster will be managed by this node into the entire cluster. It should be noted that in this disclosure, the management server is the cluster management node.

[0008] (7) Computing Node: Used to provide computing resources, which can include Central Processing Unit (CPU) resources, or heterogeneous Graphics Processing Unit (GPU) / Field Programmable Gate Array (FPGA) resources, etc.

[0009]

[0010] ​(8) file storage: used for storing data and files in the cluster. Next, first in combination with FIG. 1 and FIG. 2, the related art is described. FIG. 1 is a schematic diagram of a related art. Please refer to FIG. 1, the cloud platform can include cloud services, cloud monitoring nodes, and clusters. In this related art, the basic process of installing components in the cluster is as follows: in step 1-1, the user can initialize the cluster through the cluster management tool and the configuration file. The cluster management tool can provide a command line interface (Command Line Interface, CLI), and the user can input text commands in the CLI to make the cluster management tool perform corresponding operations according to the file commands. The configuration file can include cluster configuration information (for example, the number of nodes, node types, and storage configuration, etc.). In step 1-2, the configuration file can be parsed and processed by the cloud service to obtain the cluster configuration information, and the cluster is constructed based on the cluster configuration information. The cluster can include a login node and a plurality of computing nodes. In step 1-3, the cloud service can be used to deploy and start the cluster using component snapshots, and deploy shared storage in the cluster. In step 1-4, the user can log in to the login node and submit a computing task. In step 1-5, the login node can send the number of computing tasks to the cloud monitoring node according to the computing task. In step 1-6, the cloud monitoring node can trigger an automatic scaling event according to the number of tasks and the task threshold to increase or decrease the number of computing nodes according to the number of tasks. In step 1-7, the login node can assign computing tasks to a plurality of computing nodes to process the computing tasks through the plurality of computing nodes. In step 17, the user can also delete and terminate the cluster resources through the cluster management tool. In the related art shown in FIG. 1, the configuration file can be parsed and processed by the cloud service to obtain the cluster configuration information, and the cluster is constructed based on the cluster configuration information, and then the cluster can be deployed through the component snapshot. However, every time a new component is installed in the cluster, it needs to be manually adapted and manually created a snapshot corresponding to the component, resulting in low efficiency of installing components, and being unable to flexibly configure related services for components. FIG. 2 is a schematic diagram of another related art. Please refer to FIG. 2, in this related art, the basic process of installing components in the cluster is as follows: in step 2-1, the cluster toolkit can be downloaded in the software platform, and the cluster toolkit can include a cluster engine. The cluster toolkit can include tools needed to build and manage the cluster. The file corresponding to the cluster engine can be a binary file.In step 2-2, the user can edit the cluster configuration file, and configure the node, storage, network and other cluster information in the cluster configuration file. The cluster configuration file can specify the required computing modules in detail, and the method of customizing these modules. The format of the cluster configuration file can be a readable data serialization standard (YAML Ain't Markup Language, YAML) format or a lightweight data exchange format (JavaScript Object Notation, JSON) format. In step 2-3, the cluster engine can be executed based on the cluster configuration file and the computing module, to create a cluster deployment folder and output a related command line for deploying the cluster. In step 2-4, the command line output in step 2-3 is executed to deploy the cluster resources. In step 2-5, the user can submit a job, which can be combined with a cloud monitoring tool to analyze and monitor the cluster resource status. In step 2-6, the user can delete and terminate the cluster resources. In the related art shown in FIG. 2, the cluster deployment folder can be created by the cluster engine based on the cluster configuration file, and the related command line is output, and the command is executed to complete the creation of the HPC cluster. The related art does not involve the expansion and integration of various components, and the user needs to manually configure and install the components after the cluster is created, and then manually design and implement the operation and maintenance management scheme after the installation is completed. In the related art shown in FIGS. 1 and 2, the components need to be manually deployed by the user when the components are installed in the cluster, which leads to low efficiency of deploying the components. FIG. 3 is a scene schematic diagram provided by an exemplary embodiment of the present disclosure. Please refer to FIG. 3, the target component template can be provided in the cluster. The user can configure the target component template to obtain a component configuration file. The management server can automatically deploy the target component according to the component configuration file. In the related art, the user usually needs to manually deploy each component (including installing each component and configuring related services) in the cluster. However, in the above manner, manually deploying each component usually involves a large number of repetitive operations, which leads to low efficiency of deploying the components. To solve the above technical problem, the present embodiment provides a component deployment method. In the present embodiment, the target component template can be provided in the cluster. The user can configure the target component template to obtain a component configuration file of the target component. The management server can determine at least one node in the cluster according to the component configuration file, and deploy the target component in the target component node according to the component configuration file and the at least one node.Since the management and control server can automatically deploy the target component based on the component configuration file, manual deployment is not required, not only saving manpower, but also improving the efficiency of deploying the component; and since the component template is replicable and extensible, the component configuration file is obtained based on the target component template, improving the efficiency and convenience of obtaining the component configuration file, further improving the efficiency of deploying the component. Next, the system architecture of the present disclosure is described in combination with FIG. 4. FIG. 4 is a system architecture diagram provided by an exemplary embodiment of the present disclosure. Referring to FIG. 4, the cluster can include a cluster template and a cluster resource. The cluster template can include a component template. The component template can be customized. The cluster resource can include a management and control node, a computing node, a storage node, and a component node. The customized component can be at least one of the following: a workflow component, an iterative development environment component, application software, third-party service software, monitoring software, and distributed software. The user can configure the component template to obtain a component configuration file, and then can deploy the customized component in the component node according to the component configuration file in an IaC implementation manner, so that the one-key deployment and extension of the customized component service in the cluster can be implemented, and the management and operation and maintenance of the customized service component can be efficiently and flexibly implemented in combination with various general-purpose services in the cluster. Next, the difference between the technical solution in the present disclosure and the related technologies shown in the embodiments of FIG. 1 and FIG. 2 is described in combination with FIG. 5. FIG. 5 is a technical difference comparison diagram provided by an exemplary embodiment of the present disclosure. Referring to FIG. 5, the difference between the present technical solution and the related technology 1 (i.e., the related technology shown in the embodiment of FIG. 1) and the related technology 2 (i.e., the related technology shown in the embodiment of FIG. 2) is that: in the related technology 1 and the related technology 2, the component needs to be manually deployed and maintained by a person, and template configuration and extension are not supported. In the present technical solution, the cluster is provided with a component template and a component node. The present technical solution has the following advantages:

[0011] (1) The user can configure the component template to obtain a component configuration file, and then can automatically deploy the customized component in the component node in an IaC implementation manner according to the component configuration file, without human intervention, avoiding a large number of repetitive operations involved in manually deploying the component, and improving the efficiency of deploying the component.

[0012] (2) The component template is obtained by abstracting and constructing the characteristics of industry software and services, and the component template is replicable and extensible, improving the efficiency and convenience of obtaining the component configuration file, and further improving the efficiency of deploying the component.

[0013] (3) The component template can fuse various cloud services and cloud resources. A component configuration file is obtained by configuring the component template, and a custom component is automatically deployed according to the component configuration file, without the need to additionally specially configure cloud services and cloud resources for the component, thereby improving the efficiency of configuring cloud services and cloud resources for the component.

[0014] (4) A unified interface can be abstracted from the component template, so that the component template has cross-platform and portability, and can be used on various cloud platforms. In the following, the technical solutions shown in the present disclosure will be described in detail through specific embodiments. It should be noted that the following several embodiments can exist independently, or can be combined with each other, and for the same or similar content, the description will not be repeated in different embodiments. The execution subject of the embodiments of the present disclosure can be a management and control server, or a component deployment device arranged in the management and control server. The component deployment device can be implemented by software, or by the combination of software and hardware. The component deployment device can be a processor in the management and control server. In order to facilitate understanding, in the following, the execution subject is taken as the management and control server for example to describe. FIG. 6 is a flowchart of a component deployment method provided by an exemplary embodiment of the present disclosure. Please refer to FIG. 6, the method can include:

[0015] S601、 In response to a deployment instruction for a target component, a component configuration file of the target component is obtained. The target component refers to a component to be deployed in a cluster. Optionally, the target component can include n services, where n is an integer greater than or equal to 0. The target component can be any one of the following: a workflow component, an iterative development environment component, application software, third-party service software, etc. The workflow component can provide application services for automatically managing business processes of the cluster, including setting resource requirements for each step, setting dependencies, and setting schedulers. The iterative development environment component can provide a development environment for data analysis, testing, etc. The third-party service software refers to software provided by a third-party software provider. Optionally, the cluster can be a cloud HPC cluster, an HPC hybrid cloud cluster, an HPC serverless cluster. The deployment instruction can be used to instruct the deployment of the target component. The component configuration file is obtained by a user configuring a target component template. Optionally, the cluster can include multiple custom templates. The multiple custom templates can be templates of different types or different purposes. The custom template can be any one custom by a user. For example, the multiple custom templates can include a computing resource configuration template, a storage resource configuration template, a network resource configuration template, at least one component template, etc. At least one component template is newly added by the present disclosure, and the component template is an abstraction of the features of HPC industry software and services. The target component template can be any one of the at least one component template. The target component template can be used to configure component information of the target component to obtain the component configuration file. The target component template can be already in the cluster, i.e., the target component template is included in the multiple custom templates; or it can be newly created. The component configuration file can include information required to deploy the target component. The component configuration file can be used to deploy the target component. The format of the component configuration file can be YAML or JSON. Optionally, the component configuration file can be stored in a preset storage space, which can be located in a management and control server or in a public storage space of the cluster. Optionally, the user can log in to the management and control server through a user device and send a deployment instruction for the target component to the management and control server through the user device. The management and control server can obtain the component configuration file of the target component in the preset storage space in response to the deployment instruction for the target component.

[0016] 5602、 According to the component configuration file, at least one node in the cluster is determined. The at least one node can be a node required when the target component is deployed. The at least one node can be a physical server, a virtual machine, or a container. Optionally, the at least one node can include a target scheduling node and a target component node. The scheduling node can be used to manage and coordinate resource allocation and task scheduling in the cluster. The cluster can include at least one scheduling node. Optionally, the target scheduling node can be a calling node closest to the target component node. The target component node can be used to deploy the target component. Optionally, the target component node can be a node that has joined the cluster or a node that has not joined the cluster. Optionally, the component configuration file can include an identifier of the target scheduling node and an identifier of the target component node. The management and control server can determine the identifier of the target scheduling node and the identifier of the target component node in the component configuration file, determine the target scheduling node according to the identifier of the target scheduling node, and determine the target component node according to the identifier of the target component node

[0017] 5603、 According to the component configuration file and the at least one node, a target component is deployed in a target component node. The target component node can be included in the at least one node. The target component node can be used to deploy the target component. In an optional embodiment, the target component can be deployed according to the component configuration file and the at least one node by: performing parsing processing on the component configuration file to obtain cluster configuration information, resource configuration information, and component service configuration information; and deploying the target component according to the cluster configuration information, the resource configuration information, the component service configuration information, and the at least one node. Since the management and control server can automatically deploy the target component in the cluster according to the cluster configuration information, the resource configuration information, the component service configuration information, and the at least one node, human intervention is not required for deployment, which not only saves manpower but also improves the efficiency of deploying the component. The cluster configuration information can include configuration information for adding the target component node to the cluster. According to the cluster configuration information, the target component node can be added to the cluster. Optionally, the cluster configuration information can include: the type and version of a scheduler, and the type and version of a domain account service. The resource configuration information can include information of a component resource required for deploying the target component. The component resource can include at least one of: an instance resource, a storage resource, a network resource, and the like. The component service configuration information can include service configuration information of the target component. Optionally, the component service configuration information can include a download address of a target component installation package, a download address of a target component script, a target component deployment method, a target component viewing method, a target component start / stop method, and a target component uninstallation method, and the like. Optionally, if the target component includes n services, the component service configuration information can include service configuration information of the n services. The service configuration information of each service can include: a service deployment method, a service viewing method, a service start / stop method, and a service uninstallation method, and the like. Optionally, the management and control server can also obtain basic configuration information by performing parsing processing on the component configuration file. The basic configuration information can include a target component name and a target component version number. Optionally, the basic configuration information can also include description information, tags, icons, and the like corresponding to the target component. The management and control server can deploy the target component in the cluster according to the cluster configuration information, the resource configuration information, the component service configuration information, and the at least one node. It should be noted that the management and control server automatically deploys the target component in the target component node according to the component configuration file, which is an IaC implementation manner.In the embodiment of the present disclosure, the management server can obtain the component configuration file of the target component in response to the deployment instruction of the target component, and determine at least one node in the cluster according to the component configuration file, and then deploy the target component in the target component node according to the component configuration file and the at least one node. In the present scheme, the component template can be compatible with the docking and integration of various IaC schemes, and the target component can be automatically deployed in the cluster according to the component configuration file, without human intervention in the deployment, which not only saves manpower, but also improves the efficiency of deploying the component. Moreover, the component template is replicable and extensible, the component configuration file is obtained based on the target component template, which improves the efficiency and convenience of obtaining the component configuration file. In the following, the component deployment method is described in detail based on the embodiment shown in FIG. 6 in combination with FIG. 7. FIG. 7 is a flowchart of another component deployment method provided by an exemplary embodiment of the present disclosure. Referring to FIG. 7, the method can include the following steps.

[0018] S701, in response to a creation instruction or a selection instruction, obtaining a target component template. The creation instruction can be used to create the target component template. The selection instruction can be used to obtain the target component template. Optionally, obtaining the target component template can include the following two cases: Case 1: The target component template already exists in the cluster. In this case, the management server can obtain the target component template in response to the selection instruction of the user. Optionally, the user can log in to the management server through the user device, and send the selection instruction to the management server through the user device, so that the management server can obtain the target component template in response to the selection instruction of the user. Case 2: The target component template does not exist in the cluster. In this case, the management server can create the target component template in response to the creation instruction of the user. Optionally, the user can log in to the management server through the user device, and send the creation instruction to the management server through the user device, so that the management server can create the target component template in response to the creation instruction of the user. Optionally, the target component template can include five parts, namely, basic configuration, cluster configuration, resource configuration, general service configuration, and component service configuration. The first four configurations can be directly deployed, while the component service configuration is a service configuration item of software, which needs to be provided with a corresponding software installation package and configuration script by the developer in combination with the specific software. For example, the target component template can be as shown in Table 1: Optionally, a unified interface is abstracted for any component template, so that the component template has cross-platform and portability, and the component template can be called on various cloud platforms through the interface corresponding to the component template.

[0019] S702、 In response to the configuration instruction of the target component template, the target component template is configured to generate a component configuration file, and the component configuration file is saved. For example, the management and control server can respond to the user's configuration instruction of the target component template, and configure the target component template as shown in Table 1 to obtain the content as shown in Table 2. Then the management and control server can generate a component configuration file according to the content in Table 2, and save the component configuration file in a preset storage space.

[0020] 5703、 In response to the deployment instruction of the target component, the component configuration file of the target component is obtained.

[0021] 5704、 According to the component configuration file, at least one node in the cluster is determined. It should be noted that the execution process of steps S703-S704 can refer to steps S601-S602.

[0022] 5705、 The component configuration file is parsed to obtain cluster configuration information, resource configuration information, and component service configuration information. For example, if the component configuration file is generated according to the content shown in Table 2, the management and control server can parse the component configuration file to obtain the cluster configuration information, resource configuration information, and component service configuration information as shown in Table 2; It can also obtain the basic configuration information and general service configuration information as shown in Table 2.

[0023] 5706、 Deploy the component resource corresponding to the target component according to the resource configuration information. The resource configuration information is information corresponding to the resource configuration. Optionally, the resource configuration information includes at least one instance configuration information, at least one network address, and a network address allocation policy. In an optional embodiment, the component resource corresponding to the target component can be deployed according to the resource configuration information in the following manner: at least one instance is created according to the at least one instance configuration information; and the network address is configured to the at least one instance according to the at least one network address and the network address allocation policy, so as to deploy the component resource. The component resource can include at least one instance. Since the identification of the target component node is included in the resource configuration information, the management server can optionally determine the target component node according to the identification of the target component node, and create at least one instance in the target component node according to the at least one instance configuration information. Optionally, if the target component node is a physical server, the instance can be a virtual machine; if the target component node is a virtual machine, the instance can be a container. For example, if the resource configuration information is as shown in Table 2, and the instance configuration information 1 of instance 1 includes 2 vCPUs and 10 GB, the management server can create instance 1 in node 002 according to the instance configuration information 1, and instance 1 can include 2 vCPUs and the corresponding storage space is 10 GB. The management server can also allocate the network address to instance 1 according to the network address allocation policy. Optionally, the management server can start the component resource after creating the component resource.

[0024] 5707、 Determine whether the target component node is included in the cluster. If yes, it indicates that the target component node has joined the cluster, and S712 can be performed; if no, it indicates that the target component node has not joined the cluster, and therefore 8708-8711 can be performed to add the target component node to the cluster. It should be noted that if the target component node is included in the cluster, the target component node does not need to be configured according to the cluster configuration information.

[0025] 5708、 The target component node is configured according to the cluster configuration information, so as to join the cluster. Optionally, the management server can send the cluster configuration information to the target component node, so that the target component node obtains the cluster configuration information. Optionally, the cluster configuration information includes the type and version of at least one object. For example, the object can be a scheduler or a domain account service. Optionally, the target component node can be configured according to the cluster configuration information in the following manner: for any object, the target component node determines the object installation package and the object script corresponding to the object according to the type and version of the object; the target component node executes the object script and installs the object installation package in the target component node, so as to configure the target component node. Since any object has a corresponding type and version, the object installation package and the object script corresponding to the object can be determined according to the type and version of the object. For example, if the cluster configuration information is as shown in Table 2, and the target component node is node 002, node 002 can determine the scheduler installation package and the scheduler script according to the type and version of the scheduler, and then node 002 can execute the scheduler script and install the scheduler installation package in node 002; similarly, node 002 can determine the domain account service installation package and the domain account service script according to the type and version of the domain account service, and then node 002 can execute the domain account service script and install the domain account service installation package in node 002, so as to configure node 002.

[0026] 5709、 The target component node determines the target scheduling node. Since the target component node can obtain the cluster configuration information, the cluster configuration information can include the identifier of the target scheduling node, and the target component node can determine the target scheduling node according to the identifier of the target scheduling node. For example, the target component node can determine that the target scheduling node is node 001.

[0027] 5710、 The target component node sends a node joining request to the target scheduling node. The node joining request can be used to request that the target component node joins the cluster. The node joining request includes the identifier of the target component node and the object-related information of at least one object. For any object, since the object has been installed in the target component node, the object-related information of the object refers to the related information of the object in the target component node. For example, if the object is a scheduler, the object-related information can include the version of the scheduler, the installation location of the scheduler, and the running state of the scheduler; if the object is a domain account service, the object-related information can include the domain name to which the target component node belongs and the domain account.

[0028] 5711、 The target component node receives a node joining response corresponding to the node joining request sent by the target scheduling node. The node joining response can include a node joining success response or a node joining failure response. After receiving the node joining request sent by the target component node, the target scheduling node can perform verification processing on the request information (i.e., the identifier of the target component node and the object-related information of at least one object) in the node joining request. If the verification is passed, the target scheduling node can generate a node joining success response in response to the node joining request, and send the node joining success response to the target component node, so that the target component node can receive the node joining success response. If the verification fails, the target scheduling node can generate a node joining failure response in response to the node joining request, and send the node joining failure response to the target component node, so that the target component node can receive the node joining failure response.

[0029] 5712、 According to the component service configuration information and the component resource, the target component is deployed in the target component node. Optionally, the management server can send the component service configuration information to the target component node, so that the target component node obtains the component service configuration information. Optionally, the component service configuration information includes a first download address corresponding to the target component installation package and a second download address corresponding to the target component script. Optionally, the first download address and the second download address can be the same download address, or can be different download addresses. In an optional embodiment, the target component can be installed in the target component node according to the component service configuration information and the component resource by the following manner: the target component installation package is downloaded by the target component node according to the first download address; the target component script is downloaded by the target component node according to the second download address; and the target component script is executed by the target component node to deploy the target component according to the target component installation package. For example, if the component service configuration information is as shown in Table 2, the target component node can download the target component installation package according to address 1, and download the target component script according to address 2, and then execute the target component script to install the target component according to the target component installation package, so as to realize the deployment of the target component. Optionally, after the component is successfully installed in the target component node, the target component node can send a component deployment success notification to the management server; and after receiving the component deployment success notification, the management server can generate an ID (identifier) of the target component, and send the ID of the target component to the user equipment, so that the user can know the ID of the target componento

[0030] S713, deploy the general service required by the target component according to the general service configuration information. Optionally, after step S712 is performed, step S713 can also be performed to deploy the general service required by the target component, so that the target component can invoke the general service when in use. The general service configuration information includes configuration information of at least one general service. For any one general service, the configuration information of the general service can include an interface for invoking the general service, and can also include other related information. For example, as shown in Table 2, if the general service is the network security group service, the service information of the network security group service can include port 1, port 2, port 3, and interface 1. Optionally, the general service required by the target component can be deployed according to the general service configuration information in the following manner: determining the configuration information of at least one general service in the general service configuration information; for any one general service, determining the interface corresponding to the general service in the configuration information of the general service; and invoking the general service through the interface to deploy the general service required by the target component. For example, for the network security group service, the configuration information of the network security group service can include port 1, port 2, port 3, and interface 1, and the management server can invoke the network security group service according to interface 1 to deploy the network security group service required by the target component. Optionally, step S713 can also be performed by the target component node. It should be noted that the various processing steps (S701-S713) shown in the embodiment of FIG. 7 do not constitute a specific limitation on the component deployment process. In other embodiments of the present disclosure, the component deployment process can include more or fewer steps than the embodiment of FIG. 7. For example, the component deployment process can include some steps in the embodiment of FIG. 7, or some steps in the embodiment of FIG. 7 can be replaced by steps with the same function, or some steps in the embodiment of FIG. 7 can be split into multiple steps, etc. In the embodiments of the present disclosure, the management server can obtain the target component template in response to a creation instruction or a selected instruction, and perform configuration processing on the target component template in response to a configuration instruction for the target component template, to generate a component configuration file and save the component configuration file. The management server can obtain the component configuration file of the target component in response to a deployment instruction for the target component, and determine at least one node in the cluster according to the component configuration file. The management server can perform parsing processing on the component configuration file to obtain cluster configuration information, resource configuration information, and component service configuration information, and can deploy the component resources corresponding to the target component according to the resource configuration information. If the target component node is not included in the cluster, the management server can perform configuration processing on the target component node according to the cluster configuration information to add the target component node to the cluster.The management server can also determine the target scheduling node through the target component node, send a node joining request to the target scheduling node through the target component node, and receive a node joining response corresponding to the node joining request sent by the target scheduling node through the target component node. The management server can deploy the target component in the target component node according to the component service configuration information and the component resource, and can also deploy the general service required by the target component according to the general service configuration information. Since the component template can be compatible with the docking and integration of various IaC schemes, and the target component can be automatically deployed in the cluster according to the component configuration file without human intervention, not only the manpower is saved, but also the efficiency of deploying the component is improved; and the component template is abstracted and constructed based on the characteristics of industry software and services, the component template is replicable and extensible, the component configuration file is obtained based on the target component template, the efficiency and convenience of obtaining the component configuration file are improved, and the efficiency of deploying the component is further improved; various cloud services and cloud resources can also be integrated in the component template, the component configuration file is obtained by configuring the component template, and the custom component is automatically deployed according to the component configuration file, without the need to additionally specially configure cloud services and cloud resources for the component, thereby improving the efficiency of configuring cloud services and cloud resources for the component; a unified interface can also be abstracted from the component template, so that the component template has cross-platform and portability, can be used on various cloud platforms, and the efficiency of deploying the component on various cloud platforms is improved. It should be noted that the steps shown in the embodiments of FIGS. 6 and 7 can also be executed by the target component node, that is, the target component node can obtain the target component template in response to a creation instruction or a selection instruction, and perform configuration processing on the target component template in response to a configuration instruction for the target component template, generate a component configuration file, and save the component configuration file. The target component node can obtain the component configuration file of the target component in response to a deployment instruction for the target component, and determine at least one node in the cluster according to the component configuration file. The target component node can perform parsing processing on the component configuration file to obtain cluster configuration information, resource configuration information, and component service configuration information, and can deploy the component resource corresponding to the target component according to the resource configuration information. If the target component node is not included in the cluster, the target component node can determine the cluster configuration according to the cluster configuration. S704, S705, S706, S712, or S713, and selectively performs according to the specific update content of the updated configuration file. In addition, since the target component node where the target component is located has joined the cluster, steps S708, S709, S710, and S711 do not need to be performed again during the update processing. Optionally, after the target component is updated, the target component node can also restart the target component and send a component update notification to the management and control server. The component update notification can include a component update success notification and a component update failure notification. For example, if the component service configuration information is as shown in Table 2, if the update configuration instruction indicates that the component installation path in the component service configuration is updated to path 2, the management and control server can update the component installation path in the component service configuration to path 2 in response to the update configuration instruction, that is, perform the update configuration processing on the component configuration file, and then an updated configuration file can be obtained. The component installation path in the updated configuration file is path 2. The management and control server can update the installation path of the target component to path 2 according to the updated configuration file through the target component node to update the target component. After the target component is updated, the target component node can restart the target component. If the update is successful, the target component node can send a component update success notification to the management and control server. In another optional embodiment, the target component node can also perform the update configuration processing on the component configuration file in response to the update configuration instruction to obtain an updated configuration file, and update the target component according to the updated configuration file. Optionally, after the target component is updated, the target component node can also restart the target component and generate a component update notification. The component update notification can include a component update success notification and a component update failure notification. For example, if the component service configuration information is as shown in Table 2, if the update configuration instruction indicates that the component installation path in the component service configuration is updated to path 2, the target component node can update the component installation path in the component service configuration to path 2 in response to the update configuration instruction, that is, perform the update configuration processing on the component configuration file, and then an updated configuration file can be obtained. The component installation path in the updated configuration file is path 2. The target component node can update the installation path of the target component to path 2 according to the updated configuration file through the target component node to update the target component. After the target component is updated, the target component node can restart the target component. If the update is successful, the target component node can generate a component update success notification.In an optional embodiment, the management server can receive a first state query request sent by a user device; send a second state query request to a target component node according to an identifier of the target component node; receive a second query result corresponding to the second state query request sent by the target component node, and determine the second query result as a first query result corresponding to the first state query request; and send the first query result to the user device. The first state query request can include the identifier of the target component node and an identifier of a target component. The second state query request can include the identifier of the target component. The first state query request and the second state query request can both be used to request the working state of the target component in the target component node. The working state can include a normal state and an abnormal state. Optionally, the working state can also include a running state and an idle state, etc. The first query result and the second query result can both include the working state of the target component. In another optional embodiment, the target component node can query the working state of the target component and determine a query result in response to a state query operation of the target component by a user. Optionally, if the target component node has a display screen, the query result can be displayed. In an optional embodiment, the management server can receive a first operation request sent by a user device; send a second operation request to a target component node according to an identifier of the target component node; receive a second operation result corresponding to the second operation request sent by the target component node, and determine the second operation result as a first operation result corresponding to the first operation request; and send the first operation result to the user device. The first operation request can include the identifier of the target component node, the identifier of the target component, and an identifier of a target operation. The second operation request can include the identifier of the target component and the identifier of the target operation. The identifier of the target operation is used to identify the target operation. Optionally, the target operation can be starting, stopping, restarting, etc. The first operation request and the second operation request can both be used to request the target component node to perform the target operation on the target component according to the identifier of the target operation. The second operation result is an operation result obtained by the target component node performing the target operation on the target component according to the identifier of the target operation. In another optional embodiment, the target component node can obtain a target operation instruction of the target component by a user, perform the target operation on the target component according to the target operation instruction, and generate an operation result. Optionally, if the target component node has a display screen, the operation result can be displayed. The target operation instruction can be a start component instruction, a stop component instruction, a restart component instruction, etc., and the corresponding target operation can be starting, stopping, restarting, etc.In an optional embodiment, the management server can receive a first uninstall request sent by the user device; send a second uninstall request to the target component node according to the identifier of the target component node; receive a second uninstall result corresponding to the second uninstall request sent by the target component node, and determine the second uninstall result as the first uninstall result corresponding to the first uninstall request; and send the first uninstall result to the user device. The first uninstall request can include the identifier of the target component node and the identifier of the target component. The second uninstall request can include the identifier of the target component. The first uninstall request and the second uninstall request can both be used to request the target component node to uninstall the target component. In another optional embodiment, the target component node can obtain an uninstall instruction of the target component from the user, uninstall the target component according to the uninstall instruction, and generate an uninstall result. Optionally, if the target component node has a display screen, the uninstall result can be displayed. The above embodiments of FIG. 6 and FIG. 7 both illustrate the process of deploying the target component. Next, the use process of the target component is described in combination with FIG. 8. FIG. 8 is a flowchart of a target component use method provided in an exemplary embodiment of the present disclosure. Please refer to FIG. 8, the method can include: S80K The target component node obtains a service request corresponding to the target component, and determines the request type of the service request. The service request can be used to request the target component to provide corresponding services. The request type of the service request includes a non-resource application type and a resource application type. The non-resource application type means that the service request is used to request management, query, and configuration, and does not involve allocation of specific computing resources. The resource application type means that the service request is used to request allocation, use, or release of specific computing resources, etc. The user device can send the service request to the target component node, so that the target component node obtains the service request corresponding to the target component. The target component node can determine the request type of the service request.

[0031] S802, The target component node processes the service request according to the request type. Optionally, processing the service request according to the request type can include the following two cases: Case 1: The request type is a non-resource application type. In this case, the target component node can determine the corresponding request result according to the service request and send the request result to the user equipment. For example, if the service request is a Web service request and does not involve cluster resource scheduling and allocation, that is, the request type of the service request is a non-resource application type, the target component can determine the corresponding request result according to the Web service request and send the request result to the user equipment. Case 2: The request type is a resource application type. In this case, the service request can include resource configuration parameters of the target task. The target component node can obtain the resource configuration parameters of the target task in the service request and send the resource configuration parameters to the target scheduling node to enable the target scheduling node to determine at least one computing node according to the resource configuration parameters; and call the at least one computing node to process the target task. Optionally, the resource configuration parameters can include a total amount of tasks of the target task and an identifier of the at least one computing node. The target scheduling node can determine the at least one computing node according to the identifier of the at least one computing node in the resource configuration parameters and determine a task allocation amount corresponding to each computing node according to the total amount of tasks of the target task, so that the target component node can allocate the corresponding task allocation amount to each computing node according to the task allocation amount of each computing node. The sum of the task allocation amounts of the at least one computing node is equal to the total amount of tasks. After the at least one computing node obtains the task allocation amount, the target component node can call the at least one computing node to process the target task. Optionally, any computing node can send a task allocation success notification to the target component node after receiving the task allocation amount. For example, if the service request includes a total amount of tasks of the target task and identifiers of three computing nodes, and the target component is a workflow component, the workflow component can parse the resource configuration parameters in the service request, that is, the total amount of tasks of the target task and the identifiers of the three computing nodes. The workflow component can send the resource configuration parameters to the target scheduling node to enable the target scheduling node to determine the three computing nodes according to the identifiers of the three computing nodes and determine the task allocation amounts corresponding to the three computing nodes, respectively, according to the total amount of tasks.Suppose the three computing nodes are computing node 1, computing node 2, and computing node 3, the task allocation quantity 1 corresponding to the computing node 1 is 100, the task allocation quantity 2 corresponding to the computing node 2 is 150, and the task allocation quantity 2 corresponding to the computing node 3 is 50, then the target component node can allocate tasks to the three computing nodes corresponding to the task allocation quantity. The target component node can call the three computing nodes to process the target task. In the embodiment of the present disclosure, the target component node can obtain the service request corresponding to the target component, determine the request type of the service request, and then process the service request according to the request type. Through the target component, the user can be provided with customized personalized services. Next, on the basis of any of the above embodiments, combined with FIG. 9, taking an HPC cluster as an example, the above component deployment process, use process, and the like are further described. FIG. 9 is a schematic diagram of a component-related process provided by an exemplary embodiment of the present disclosure. Please refer to FIG. 9, which includes seven processes, namely, a configuration process, a deployment process, a use process, an update process, a state query process, an operation process, and an uninstallation process O.

[0032] The HPC cluster can include a management and control server, a target scheduling node, a target component node, and a computing node.

[0033] (1) In the configuration process, the following steps 1.1-1.5 are included: step 1.1: the user can log in to the management and control server through the user equipment, and create a target component template. Step 1.2: the management and control server can save the template information of the target component template created by the user. Step 1.3: the management and control server can generate an ID of the target component template, and send the ID of the target component template to the user equipment. Step 1.4: the user can log in to the management and control server through the user equipment, and configure the target component template. Step 1.5: the management and control server can generate a component configuration file based on the user's configuration of the target component template, and save the component configuration file.

[0034] (2) In the deployment process, the following steps 2.1-2.10 are included: Step 2.1: A user can send a deployment instruction for a target component to a management server through a user device. Step 2.2: The management server can obtain a component configuration file, and parse the component configuration file to obtain cluster configuration information, resource configuration information, component service configuration information, and general service configuration information. Step 2.3: The management server can deploy component resources corresponding to the target component in a target component node according to the resource configuration information. Step 2.4: If the target component node is not included in the cluster, the target component node can perform configuration processing on the target component node according to the cluster configuration information. Step 2.5: The target component node can send a node joining request to a target scheduling node to request to join the cluster. Step 2.6: The target scheduling node can perform verification processing on the node joining request to obtain a verification result, and then can generate a node joining response according to the verification result, and send the node joining response to the target component node. Step 2.7: The target component node can deploy the target component in the target component node according to the component service configuration information and the component resources. Step 2.8: The target component node can send a component deployment success notification to the management server. Step 2.9: The management server can generate an ID of the target component, and send the ID of the target component to the user device. Step 2.10: The management server can deploy general services required by the target component according to the general service configuration information.

[0035] (3) In use, when the request type of the service request is a non-resource application type, the following step 3.2 can be performed; when the request type of the service request is a resource application type, the following steps 3.3-3.7 can be performed; step 3.1: the user equipment can send a service request to the target component node, and the request type of the service request is a non-resource application type. Step 3.2: the target component node can determine a request result according to the service request, and send the request result to the user equipment. Step 3.3: the user equipment can send a service request to the target component node, and the request type of the service request can be a resource application type, and the service request can include resource configuration parameters of the target task. Step 3.4: the target component node can obtain the resource configuration parameters of the target task in the service request, and send the resource configuration parameters to the target scheduling node. Step 3.5: the target scheduling node determines at least one computing node according to the resource configuration parameters, and determines a task allocation amount corresponding to each computing node according to the total amount of the target task, so as to allocate computing resources. Step 3.6: the target component node can allocate the corresponding task allocation amount to each computing node according to the task allocation amount of each computing node, so as to allocate the target task. Step 3.7: after the computing node receives the task allocation amount, the computing node can send a task allocation success notification to the target component node.

[0036] (4) In the updating process, the following steps 4.1-4.6 are included: step 4.1: the user can send an update configuration instruction to the management and control server through the user equipment. Step 4.2: the management and control server can obtain an update configuration file, and parse the update configuration file to obtain resource configuration update information and component service configuration update information. Step 4.3: the management and control server can update the component resources corresponding to the target component in the target component node according to the resource configuration update information. Step 4.4: the target component node can update and restart the target component in the target component node according to the component service configuration update information and the component resources. Step 4.5: the target component node can send a component update success notification to the management and control server. Step 4.6: the management and control server can send a component update success notification to the user equipment.

[0037] (5) In the state query process, the following steps 5.1-5.4 are included: Step 5.1: The user equipment can send a first state query request to the management and control server, and the first state query request can include the identification of the target component node and the identification of the target component. Step 5.2: The management and control server can send a second state query request to the target component node according to the identification of the target component node, and the second state query request can include the identification of the target component. Step 5.3: The target component node can determine the working state of the target component according to the identification of the target component in the second state query request, determine a second query result, and send the second query result to the management and control server. The second query result can include the working state of the target component. Step 5.4: The management and control server can determine the second query result as a first query result corresponding to the first state query request, and send the first query result to the user equipment. The first query result can include the working state of the target component.

[0038] (6) In the operation process, the following steps 6.1-6.5 are included: Step 6.1: The user equipment can send a first operation request to the management and control server, and the first operation request can include the identification of the target component node, the identification of the target component, and the target operation identification. Step 6.2: The management and control server can send a second operation request to the target component node according to the identification of the target component node. The second operation request can include the identification of the target component and the target operation identification. Step 6.3: The target component node can perform the target operation on the target component according to the target operation identification in the second operation request, and obtain a second operation result. Step 6.4: The target component node can send the second operation result to the management and control server. Step 6.5: The management and control server can determine the second operation result as a first operation result corresponding to the first operation request, and send the first operation result to the user equipment.

[0039] (7) In the operation process, the following steps 7.1-step 7.5 are included: step 7.1: the user equipment can send a first uninstall request to the management server, and the first uninstall request can include the identification of the target component node and the identification of the target component. Step 7.2: the management server can send a second uninstall request to the target component node according to the identification of the target component node. The second uninstall request can include the identification of the target component. Step 7.3: the target component node can uninstall the target component according to the second uninstall request to obtain a second uninstall result. Step 7.4: the target component node can send the second uninstall result to the management server. Step 7.5: the management server can determine the second uninstall result as the first uninstall result corresponding to the first uninstall request, and As shown in FIG. 10, the component deployment apparatus 10 comprises a first acquisition module 11, a determination module 12 and a deployment module 13. The first acquisition module 11 is configured to acquire a component configuration file of a target component in response to a deployment instruction of the target component, wherein the component configuration file is obtained by configuring a target component template. The determination module 12 is configured to determine at least one node in a cluster according to the component configuration file. The deployment module 13 is configured to deploy the target component in a target component node according to the component configuration file and the at least one node, wherein the at least one node comprises the target component node. The component deployment apparatus provided in the embodiment of the present disclosure can execute the technical solutions shown in the method embodiments, and the implementation principles and the beneficial effects are similar, which will not be repeated here. In a possible implementation, the deployment module 13 is specifically configured to: perform parsing processing on the component configuration file to obtain cluster configuration information, resource configuration information and component service configuration information, wherein the cluster configuration information is used for configuring the target component node, the resource configuration information is used for deploying a component resource corresponding to the target component, and the component service configuration information is used for deploying the target component; and deploy the target component in the target component node according to the cluster configuration information, the resource configuration information, the component service configuration information and the at least one node. In a possible implementation, the deployment module 13 is specifically configured to: deploy the component resource corresponding to the target component according to the resource configuration information; if the target component node is not included in the cluster, perform configuration processing on the target component node according to the cluster configuration information to add the target component node to the cluster; and deploy the target component in the target component node according to the component service configuration information and the component resource. In a possible implementation, the component service configuration information comprises a first download address corresponding to a target component installation package and a second download address corresponding to a target component script. The deployment module 13 is specifically configured to: download the target component installation package through the target component node according to the first download address; download the target component script through the target component node according to the second download address; and execute the target component script through the target component node to deploy the target component in the target component node according to the target component installation package.In a possible implementation, the cluster configuration information includes a type and a version of at least one object; the at least one node includes a target scheduling node; and the deployment module 13 is specifically configured to: for any one object, determining, by the target component node, an object installation package and an object script corresponding to the object according to the type and the version of the object; executing, by the target component node, the object script, installing the object installation package on the target component node, and performing configuration processing on the target component node. In a possible implementation, the at least one node includes a target scheduling node; and the deployment module 13 is further configured to: determining, by the target component node, the target scheduling node; sending, by the target component node, a node joining request to the target scheduling node, where the node joining request includes an identifier of the target component node and object-related information of the at least one object; and receiving, by the target component node, a node joining response corresponding to the node joining request and sent by the target scheduling node. In a possible implementation, the resource configuration information includes at least one instance configuration information, at least one network address, and a network address allocation strategy; and the deployment module 13 is specifically configured to: creating at least one instance according to the at least one instance configuration information; and configuring a network address for the at least one instance according to the at least one network address and the network address allocation strategy, to deploy the component resource, where the component resource includes the at least one instance. In a possible implementation, the component configuration file further includes general service configuration information, where the general service configuration information includes configuration information of at least one general service; and the deployment module 13 is specifically configured to: for any one of the general services, determining an interface corresponding to the general service in the configuration information of the general service; and invoking the general service through the interface, to deploy a general service required by the target component. The component deployment apparatus provided in the embodiments of the present disclosure can implement the technical solutions shown in the method embodiments, and has similar implementation principles and beneficial effects, which will not be repeated here. FIG. 11 is a structural schematic diagram of another component deployment apparatus provided in the example embodiments of the present disclosure.Referring to FIG. 11, based on the embodiment shown in FIG. 10, the component deployment apparatus 10 further comprises a second acquisition module 14 and a configuration module 15, wherein the second acquisition module 14 is configured to acquire the target component template in response to a creation instruction or a selection instruction, the creation instruction being used to create the target component template, and the selection instruction being used to acquire the target component template; and the configuration module 15 is configured to perform configuration processing on the target component template in response to a configuration instruction for the target component template, to obtain the component configuration file, and save the component configuration file. The component deployment apparatus provided by the embodiments of the present disclosure can implement the technical solutions shown in the method embodiments, and the implementation principles and beneficial effects are similar, which will not be repeated here. In a possible implementation, the apparatus further comprises an update module 16, which is configured to perform update configuration processing on the component configuration file in response to an update configuration instruction, to obtain an update configuration file; and perform update processing on the target component according to the update configuration file. In a possible implementation, the apparatus further comprises a receiving module 17 and a sending module 18, wherein the receiving module 17 is configured to receive a first state query request sent by a user equipment, the first state query request comprising an identifier of the target component node and an identifier of the target component; the sending module 18 is configured to send a second state query request to the target component node according to the identifier of the target component node, the second state query request comprising the identifier of the target component; the receiving module 17 is further configured to receive a second query result corresponding to the second state query request sent by the target component node, and determine the second query result as a first query result corresponding to the first state query request; and the sending module 18 is further configured to send the first query result to the user equipment.In a possible implementation, the receiving module 17 is further configured to receive a first operation request sent by a user equipment, wherein the first operation request comprises an identifier of the target component node, an identifier of the target component, and an identifier of a target operation; the sending module 18 is further configured to send, according to the identifier of the target component node, a second operation request to the target component node, wherein the second operation request comprises the identifier of the target component and the identifier of the target operation; the receiving module 17 is further configured to receive a second operation result sent by the target component node, and determine the second operation result as a first operation result corresponding to the first operation request, wherein the second operation result is an operation result obtained by performing the target operation on the target component according to the identifier of the target operation; and the sending module 18 is further configured to send the first operation result to the user equipment. In a possible implementation, the receiving module 17 is further configured to receive a first unloading request sent by a user equipment, wherein the first unloading request comprises an identifier of the target component node and an identifier of the target component; the sending module 18 is further configured to send, according to the identifier of the target component node, a second unloading request to the target component node, wherein the second unloading request comprises the identifier of the target component; the receiving module 17 is further configured to receive a second unloading result corresponding to the second unloading request sent by the target component node, and determine the second unloading result as a first unloading result corresponding to the first unloading request; and the sending module 18 is further configured to send the first unloading result to the user equipment. The component deployment apparatus provided in the embodiments of the present disclosure can implement the technical solutions shown in the method embodiments, and the implementation principles and beneficial effects are similar, which will not be repeated here. FIG. 12 is a structural schematic diagram of a component usage apparatus provided in an exemplary embodiment of the present disclosure. Referring to FIG. 12, the component usage apparatus 20 comprises a third obtaining module 21 and a processing module 22. The third obtaining module 21 is configured to obtain a service request corresponding to the target component, and determine a request type of the service request, wherein the request type comprises a non-resource application type and a resource application type. The processing module 22 is configured to process the service request according to the request type. In a possible implementation, the request type is the non-resource application type. The processing module 22 is specifically configured to: determine a request result corresponding to the service request; and send the request result to a user equipment.In a possible implementation, the request type is a resource application type, and the resource configuration parameter of the target task is included in the service request; the processing module 22 is specifically configured to: acquire the resource configuration parameter of the target task in the service request; send the resource configuration parameter to a target scheduling node, so that the target scheduling node determines at least one computing node according to the resource configuration parameter; and invoke the at least one computing node to process the target task. The component deployment system provided by the embodiment of the present disclosure can execute the technical solutions shown in the above method embodiments, and the implementation principles and beneficial effects are similar, which will not be repeated here. FIG. 13 is a structural schematic diagram of a management and control server according to an exemplary embodiment of the present disclosure. Referring to FIG. 13, the management and control server 30 can include a processor 31 and a memory 32. Exemplarily, the processor 31, the memory 32, and various parts are connected to each other through a bus 33. The memory 32 stores computer execution instructions; and the processor 31 executes the computer execution instructions stored in the memory 32, so that the processor 31 executes the method shown in the above method embodiments. FIG. 14 is a schematic diagram of a component deployment system according to an exemplary embodiment of the present disclosure. Referring to FIG. 14, the component deployment system can include a user device and a management and control server. The user device and the management and control server can communicate with each other. The management and control server can be as shown in FIG. 13, and can be used to execute any of the above embodiments. FIG. 15 is another schematic diagram of a component deployment system according to an exemplary embodiment of the present disclosure. Referring to FIG. 15, on the basis of the embodiment shown in FIG. 14, the component deployment system can further include a target component node and a target scheduling node. The management and control server, the target component node, and the target scheduling node can be located in a cluster. The target component can be used to deploy a target component; and the target scheduling node can be used to manage and coordinate resource allocation and task scheduling in the cluster. The component deployment system provided by the embodiment of the present disclosure can execute the technical solutions shown in the above method embodiments, and the implementation principles and beneficial effects are similar, which will not be repeated here. Accordingly, the present disclosure provides a computer-readable storage medium, which stores computer execution instructions, and when the computer execution instructions are executed by a processor, the computer execution instructions are used to implement the method described in the above method embodiments. Accordingly, the present disclosure can also provide a computer program product, which includes a computer program, and when the computer program is executed by a processor, the computer program can implement the method shown in the above method embodiments. Those skilled in the art should understand that the embodiments of the present disclosure can be provided as a method, a system, or a computer program product. Therefore, the present disclosure can adopt a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects.Moreover, the disclosure can take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and so forth) embodying computer-usable program code. The disclosure is described in reference to the flow diagrams and / or block diagrams of the methods, apparatus (systems), and computer program products according to embodiments of the disclosure. It will be understood that each block of the flow diagrams and / or block diagrams, and combinations of blocks in the flow diagrams and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processing device, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flow diagrams and / or block diagrams. These computer program instructions can also be stored in a computer- readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instructions which implement the functions specified in the flow diagrams and / or block diagrams. The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flow diagrams and / or block diagrams. In one typical configuration, the computer device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory. The memory can include non-persistent memory and / or persistent memory, which can be embodied as random access memory (RAM), read only memory (ROM), flash memory, or the like. The memory is an example of computer-readable media. Computer-readable media can include persistent and non-persistent, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules, or other data.Examples of storage media of a computer include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital versatile discs (DVDs) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information for access by a computing device. In context with the present document, computer readable medium does not encompass transitory media, such as modulated data signals and carrier waves. It is also noted that the terms "comprising", "comprises", "including", "includes" or any other variation thereof are intended to cover a non-exclusive inclusion, such that a process, method, article or apparatus that comprises a list of elements does not include only those elements but can include other elements not expressly listed or inherent to such process, method, article or apparatus. An element proceeded by "comprises... a" does not, without further constraints, exclude the presence of additional identical elements in the process, method, article or apparatus that comprises the element. The above-described embodiments of the disclosure are merely given as examples and are not intended to limit the disclosure. The disclosure can be variously changed and modified without departing from the spirit and scope of the disclosure. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the disclosure shall be included in the scope of the disclosure.

Claims

Claims 1. A component deployment method, wherein, include: In response to a deployment command for a target component, the component configuration file of the target component is obtained, wherein the component configuration file is obtained by configuring the target component template; Based on the component configuration file, identify at least one node in the cluster; Based on the component configuration file and the at least one node, the target component is deployed in the target component node, wherein the at least one node includes the target component node.

2. The method according to claim 1, wherein, Deploying the target component in a target component node based on the component configuration file and the at least one node includes: parsing the component configuration file to obtain cluster configuration information, resource configuration information, and component service configuration information, wherein the cluster configuration information is used to configure the target component node, the resource configuration information is used to deploy the component resources corresponding to the target component, and the component service configuration information is used to deploy the target component; and deploying the target component in the target component node based on the cluster configuration information, the resource configuration information, the component service configuration information, and the at least one node.

3. The method according to claim 2, wherein, Based on the cluster configuration information, the resource configuration information, the component service configuration information, and the at least one node, deploying the target component in the target component node includes: deploying component resources corresponding to the target component based on the resource configuration information; if the cluster does not include the target component node, configuring the target component node according to the cluster configuration information to add the target component node to the cluster; and deploying the target component in the target component node based on the component service configuration information and the component resources.

4. The method according to claim 3, wherein, The component service configuration information includes the first download address corresponding to the target component installation package and the second download address corresponding to the target component script; Deploying the target component in the target component node according to the component service configuration information and the component resources includes: downloading the target component installation package through the target component node according to the first download address; downloading the target component script through the target component node according to the second download address; and executing the target component script through the target component node to deploy the target component in the target component node according to the target component installation package.

5. The method according to claim 3 or 4, wherein, The cluster configuration information includes at least one object type and version; The target component node is configured according to the cluster configuration information, including: for any object, the object installation package and object script corresponding to the object are determined by the target component node according to the type and version of the object; The object script is executed through the target component node, and the object installation package is installed on the target component node to perform configuration processing on the target component node.

6. The method according to claim 5, wherein, The at least one node includes a target scheduling node; the method further includes: determining the target scheduling node through the target component node; sending a node join request to the target scheduling node through the target component node, the node join request including the identifier of the target component node and object-related information of the at least one object; The target component node receives the node join response corresponding to the node join request sent by the target scheduling node. 25 7. The method according to any one of claims 3-6, wherein, The resource configuration information includes at least one instance configuration information, at least one network address, and a network address allocation strategy; Deploying the component resources corresponding to the target component according to the resource configuration information includes: creating at least one instance according to the at least one instance configuration information; Based on the at least one network address and the network address allocation policy, a network address is configured for the at least one instance to deploy the component resource, the component resource including the at least one instance.

8. The method according to any one of claims 1-7, wherein, The component configuration file also includes general service configuration information, which includes configuration information for at least one general service. The method further includes: for any one of the general services, determining the interface corresponding to the general service in the configuration information of the general service; and calling the general service through the interface to deploy the general services required by the target component.

9. The method according to any one of claims 1-8, wherein, The method further includes: obtaining the service request corresponding to the target component, and determining the request type of the service request, wherein the request type includes non-resource request type and resource request type; and processing the service request according to the request type.

10. The method according to claim 9, wherein, The request type is non-resource request type; the service request is processed according to the request type, including: determining the corresponding request result according to the service request; and sending the request result to the user equipment.

11. The method according to claim 9 or 10, wherein, The request type is resource request type; according to the request type, the service request is processed, including: obtaining the resource configuration parameters of the target task from the service request; sending the resource configuration parameters to the target scheduling node, so that the target scheduling node determines at least one computing node according to the resource configuration parameters; and calling the at least one computing node to perform computing processing on the target task.

12. The method according to any one of claims 1-11, wherein, The method further includes: in response to a creation instruction or a selection instruction, obtaining the target component template, wherein the creation instruction is used to create the target component template, and the selection instruction is used to obtain the target component template; in response to a configuration instruction for the target component template, performing configuration processing on the target component template to obtain the component configuration file, and saving the component configuration file.

13. The method according to any one of claims 1-12, wherein, The method further includes: responding to an update configuration command, performing update configuration processing on the component configuration file to obtain an update configuration file; and performing update processing on the target component according to the update configuration file.

14. The method according to any one of claims 1-13, wherein, The method further includes: receiving a first status query request sent by a user equipment, the first status query request including an identifier of the target component node and an identifier of the target component; sending a second status query request to the target component node based on the identifier of the target component node, the second status query request including the identifier of the target component; receiving a second query result corresponding to the second status query request sent by the target component node, and determining the second query result as a first query result corresponding to the first status query request; and sending the first query result to the user equipment.

15. The method according to any one of claims 1-14, wherein, The method further includes: The system receives a first operation request from a user equipment, the first operation request including an identifier of a target component node, an identifier of a target component, and an identifier of a target operation; based on the identifier of the target component node, it sends a second operation request to the target component node, the second operation request including the identifier of the target component and the identifier of the target operation; it receives a second operation result from the target component node, and determines the second operation result as the first operation result corresponding to the first operation request, the second operation result being the operation result obtained by the target component node performing the target operation on the target component based on the identifier of the target operation; and it sends the first operation result to the user equipment.

16. The method according to any one of claims 1-15, wherein, The method further includes: receiving a first uninstallation request sent by a user equipment, the first uninstallation request including an identifier of the target component node and an identifier of the target component; sending a second uninstallation request to the target component node according to the identifier of the target component node, the second uninstallation request including the identifier of the target component; receiving a second uninstallation result corresponding to the second uninstallation request sent by the target component node, and determining the second uninstallation result as a first uninstallation result corresponding to the first uninstallation request; and sending the first uninstallation result to the user equipment.

17. A component deployment apparatus, wherein, The apparatus includes: a first acquisition module, a determination module, and a deployment module, wherein the first acquisition module is configured to, in response to a deployment instruction for a target component, acquire a component configuration file of the target component, the component configuration file being obtained by configuring a target component template; the determination module is configured to, based on the component configuration file, determine at least one node in the cluster; the deployment module is configured to, based on the component configuration file and the at least one node, deploy the target component in a target component node, the at least one node including the target component node.

18. A management server, wherein, include: At least one processor; The system includes a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, which, when executed by the at least one processor, cause the management server to perform the method according to any one of claims 1-16.

19. A component deployment system, wherein, The system includes user equipment and a management server, wherein the management server is used to execute the method according to any one of claims 1-16.

20. A computer-readable storage medium, wherein, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, implement the method as described in any one of claims 1-16.

21. A computer program product, comprising a computer program, wherein, When the computer program is executed by the processor, it implements the method as described in any one of claims 1T6.

Images