Workflow deployment method, device, system and storage medium

By specifying the system identity for the workflow execution unit, read and write isolation of shared storage resources in Kubernetes distributed cluster in a multi-tenant environment is achieved, and the problem of data access security in shared storage space is solved and data security is ensured. Sex and access control.

CN112015524BActive Publication Date: 2024-11-29ALIBABA GROUP HOLDING LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN201910452307.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2019-05-28
Publication Date
2024-11-29
Estimated Expiration
2039-05-28

AI Technical Summary

Technical Problem

In a multi-tenant computing environment, how to ensure the security of data access in shared storage space is a difficult problem, especially when deploying workflows in a Kubernetes distributed cluster, how to achieve read and write isolation between different tenants It's a challenge.

Method used

During the workflow deployment process, each workflow execution unit specifies the system identity used at runtime, distinguishes its access permissions to shared storage resources in the distributed computing system, ensuring that each workflow execution unit runs based on its operation The corresponding memory access permissions of the system identity used to access shared storage resources, thereby realizing read and write isolation between different tenants.

Benefits of technology

It effectively ensures the security of data in shared storage resources, realizes read and write isolation between different tenants, ensures data access rights control, and solves the problem of data security in shared storage resources in multi-tenant environments.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN112015524B_ABST
    Figure CN112015524B_ABST
Patent Text Reader

Abstract

The embodiment of the present application provides a workflow deployment method, device, system and storage medium. In the embodiment of the present application, the workflow deployment is combined with a distributed computing system that can serve different tenants, allowing tenants to deploy workflows in their resource domains; during the workflow deployment process, a system identity used at runtime is specified for the workflow execution unit to distinguish the memory access rights of different workflow execution units to shared storage resources in the distributed computing system, and each workflow execution unit accesses the shared storage resources in the system based on the memory access rights corresponding to the system identity used at runtime, which can achieve read-write isolation between different tenants and ensure the security of data in shared storage resources.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of Internet technology, and in particular to a workflow deployment method, device, system and storage medium. Background Art

[0002] Faced with the high concurrency problem of workflows, some cloud container vendors have begun to pay attention to Kubernetes' distributed clusters, deploying workflows in Kubernetes-based distributed clusters, and using Kubernetes' scheduling capabilities to control and run workflows.

[0003] However, deploying workflows in a Kubernetes-based distributed cluster also faces some problems that need to be solved. Among them, how to ensure the security of data access in shared storage space in a multi-tenant computing environment is one of the problems to be solved. Summary of the invention

[0004] Multiple aspects of the present application provide a workflow deployment method, device, system and storage medium for deploying workflows in a multi-tenant computing environment and ensuring the security of data in a shared storage space.

[0005] The embodiment of the present application provides a distributed computing system, including: a master control node, a workflow management node, and resource domains corresponding to different tenants;

[0006] The workflow management node is used to obtain the system identity used by the workflow execution unit when it is running according to the workflow deployment information in the target resource domain; and transmit the system identity used by the workflow execution unit when it is running to the main control node;

[0007] The master control node is used to deploy the workflow execution unit to the working node in the target resource domain when the system identity used by the workflow execution unit during operation belongs to the system identity that the target resource domain is authorized to use; wherein the workflow execution unit accesses the shared storage resources of the distributed computing system based on the memory access permissions corresponding to the system identity used by the workflow execution unit during operation.

[0008] The embodiment of the present application also provides a distributed computing system implemented based on a container orchestration and scheduling system, including: a master control node, a workflow management node, and namespaces corresponding to different tenants;

[0009] The workflow management node is used to obtain the system identity used when the container required by the workflow to be deployed is run according to the workflow deployment information in the target namespace; and transmit the system identity used when the container is run to the master control node;

[0010] The master control node is used to deploy the container to the working node under the target namespace when the system identity used when the container is running belongs to the system identity that the target namespace is authorized to use; wherein the container accesses the shared storage resources of the distributed computing system based on the memory access permissions corresponding to the system identity used when it is running.

[0011] An embodiment of the present application also provides a workflow deployment method, which is applicable to a workflow management node, and the method includes: obtaining a system identity used by a workflow execution unit when it is running according to workflow deployment information in a target resource domain; transmitting the system identity used by the workflow execution unit when it is running to a master control node in a distributed computing system to which the workflow management node belongs, so that the master control node deploys the workflow execution unit to a working node in the target resource domain if the system identity used by the workflow execution unit when it is running belongs to a system identity that the target resource domain is authorized to use; wherein the workflow execution unit accesses the shared storage resources of the distributed computing system based on the memory access permission corresponding to the system identity used by it when it is running.

[0012] An embodiment of the present application also provides a workflow deployment method, which is applicable to a master control node, and the method includes: receiving a system identity identifier used by a workflow execution unit during operation sent by a workflow management node, wherein the workflow execution unit is an execution unit of a workflow that needs to be deployed in a target resource domain; if the system identity identifier used by the workflow execution unit during operation belongs to a system identity identifier that the target resource domain is authorized to use, deploying the workflow execution unit to a working node in the target resource domain; wherein the workflow execution unit accesses the shared storage resources of the distributed computing system based on the memory access permission corresponding to the system identity identifier used by the workflow execution unit during operation.

[0013] An embodiment of the present application also provides a work management node, including a memory and a processor; the memory is used to store a computer program; when the computer program is executed by the processor, the processor implements the steps in the method that can be executed by the work management node in the embodiment of the present application.

[0014] An embodiment of the present application also provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, the processor implements the steps of the method that can be executed by the work management node in the embodiment of the present application.

[0015] An embodiment of the present application also provides a master control node, including a memory and a processor; the memory is used to store a computer program; when the computer program is executed by the processor, the processor implements the steps in the method that can be executed by the master control node in the embodiment of the present application.

[0016] An embodiment of the present application further provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, the processor implements the steps of the method that can be executed by the main control node in the embodiment of the present application.

[0017] In an embodiment of the present application, workflow deployment is combined with a distributed computing system that can serve different tenants, allowing tenants to deploy workflows in their resource domains; during the workflow deployment process, a system identity used at runtime is specified for the workflow execution unit to distinguish the memory access rights of different workflow execution units to shared storage resources in the distributed computing system. Each workflow execution unit accesses the shared storage resources in the system based on the memory access rights corresponding to the system identity used at runtime, which can achieve read-write isolation between different tenants and ensure the security of data in shared storage resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0019] Figure 1a A schematic diagram of the structure of a distributed computing system provided for an exemplary embodiment of the present application;

[0020] Figure 1b A schematic diagram of the structure of a distributed computing system based on Kubernetes provided for an exemplary embodiment of the present application;

[0021] Figure 2a A flowchart of a workflow deployment method provided for an exemplary embodiment of the present application;

[0022] Figure 2b A flowchart of another workflow deployment method provided for an exemplary embodiment of the present application;

[0023] Figure 3 A schematic diagram of the structure of a workflow management node provided for an exemplary embodiment of the present application;

[0024] Figure 4 A schematic diagram of the structure of a master control node provided for an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0025] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in combination with the specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present application.

[0026] In response to the memory access security issues of data in shared storage resources faced by deploying workflows in a multi-tenant computing environment in the prior art, in some embodiments of the present application, workflow deployment is combined with a distributed computing system that can serve different tenants, allowing tenants to deploy workflows in their resource domains; during the workflow deployment process, a system identity used at runtime is specified for the workflow execution unit to distinguish the memory access rights of different workflow execution units to shared storage resources in the distributed computing system. Each workflow execution unit accesses the shared storage resources in the system based on the memory access rights corresponding to the system identity used at runtime, which can achieve read-write isolation between different tenants and ensure the security of data in shared storage resources.

[0027] The technical solutions provided by various embodiments of the present application are described in detail below in conjunction with the accompanying drawings.

[0028] Figure 1a FIG. 1 is a schematic diagram of a distributed computing system 10 provided in an exemplary embodiment of the present application. Figure 1a As shown, the distributed computing system 10 includes: a master control node 11, a workflow management node 13, and resource domains 14 corresponding to different tenants.

[0029] The distributed computing system 10 of this embodiment includes a variety of resources, such as computing resources, storage resources, and network resources, which can be provided by physical devices in the distributed computing system. The physical devices in the distributed computing system 10 include, but are not limited to: computer devices, sensor devices, storage devices, conventional servers, cloud servers, or server arrays, etc. The distributed computing system 10 of this embodiment can provide tenants with various resources on the one hand, and also allow tenants to deploy required services on these resources on the other hand.

[0030] Among them, different tenants can apply for their own resource domains in the distributed computing system 10, and deploy various required services in their own resource domains. Each tenant can apply for one or more resource domains. For each tenant, different services can be deployed in different resource domains, or the same service can be deployed in different resource domains. The resource domain of any tenant includes various resources that the tenant can enjoy exclusively, such as working nodes that can provide corresponding services to the tenant, various service programs deployed on the working nodes, etc. The embodiments of the present application do not limit the implementation form of the service program, for example, it may include various applications and / or operating systems, etc.

[0031] Among them, different tenants have different user identity credentials, and the user identity credentials of each tenant can uniquely identify the tenant. The user identity credentials of a tenant can be any information that can uniquely identify the tenant, for example, it can be the ID of the tenant in the distributed computing system 10, or it can be the tenant name, account number, telephone number, email address and / or home address registered by the tenant in the distributed computing system 10. In addition, in order to distinguish the resource domains of different tenants and different resource domains of the same tenant, each resource domain also has its own identifier, and the identifier of each resource domain can uniquely identify the resource domain. The identifier of a resource domain can be any information that can uniquely identify the resource domain, for example, it can be the ID, name and / or application time of the resource domain in the distributed computing system 10. In this embodiment, a correspondence between the user identity credentials of the tenant and the identifier of the resource domain of the tenant is maintained.

[0032] In order to better serve tenants, the distributed computing system 10 includes: a master node 11. The master node 11 is a management and control node in the distributed computing system 10, and is mainly responsible for at least one of resource management, service scheduling, node management and control, security control, system monitoring and error correction in the distributed computing system 10. Optionally, a series of processes related to system management and control can be run on the master node 11, and these processes can realize management capabilities such as resource management, service scheduling, node management and control, security control, system monitoring and error correction in the distributed computing system 10. The number of master nodes 11 can be one or more. The master node 11 can be deployed on a physical device or a virtual machine in the distributed computing system 10. In the case of multiple master nodes 11, multiple master nodes 11 can be deployed on multiple physical devices or virtual machines.

[0033] In addition to the master node 11, the distributed computing system 10 also includes a worker node 12. The worker node 12 is a service node in the distributed computing system 10 that can provide required services to tenants. The number of worker nodes 12 can be one or more. Optionally, in the case of multiple worker nodes 12, multiple worker nodes 12 can be centrally deployed on the same physical device or virtual machine, or can be dispersedly deployed on multiple physical devices or virtual machines. The worker nodes 12 in the distributed computing system 10 are distributed in the resource domains 14 of different tenants to carry executable units such as service programs or processes deployed by tenants.

[0034] In this embodiment, tenants can deploy workflows in their resource domains. In order to facilitate tenants to deploy workflows, the distributed computing system 10 also includes a workflow management node 13. The workflow management node 13 can be centrally deployed on one or more physical machines in the distributed computing system 10, or can be dispersedly deployed on multiple physical devices or virtual machines. The workflow management node 13 mainly provides workflow deployment capabilities for different tenants, so that different tenants can deploy workflows in their own resource domains 14. Among them, workflow deployment mainly refers to the process of determining a workflow execution unit with an execution order based on the workflow deployment information provided by the tenant, and deploying the workflow execution unit to the work node 12 in the tenant's resource domain 14. Furthermore, the workflow management node 13 can also monitor and manage the workflow execution unit after the workflow is successfully deployed. Among them, the workflow execution unit refers to the execution unit required to complete the workflow.

[0035] In the distributed computing system 10, in addition to the resource domains that are exclusive to each tenant, some global shared resources that can be shared by different tenants are also included. In this embodiment, the global shared resources mainly refer to shared storage resources that can be shared by different tenants. Shared storage resources can be local storage resources or network storage resources, such as network attached storage (NAS). For example, data of different tenants can be stored in shared storage resources, and different tenants can access the shared storage resources in the distributed computing system 10. In order to ensure the security of data access in shared storage resources, it is necessary to implement read-write isolation between different tenants to ensure the security of data access in shared storage resources.

[0036] In this embodiment, the distributed computing system 10 manages memory access to its shared storage resources based on the system identity, and each system identity corresponds to certain memory access permissions. Based on this, during the workflow deployment process, the system identity used at runtime is specified for the workflow execution unit, so that the memory access permissions of different workflow execution units to the shared storage resources in the distributed computing system 10 can be distinguished. Each workflow execution unit accesses the shared storage resources in the system based on the memory access permissions corresponding to the system identity used at runtime, which can achieve read-write isolation between different tenants and ensure the security of data in shared storage resources. The system identity can be a user identifier (Uid) or a user group identifier (Gid). Gid identifies a group of users.

[0037] Specifically, for the scenario of deploying workflows in the target resource domain, the workflow management node 13 can obtain the system identity used by the workflow execution unit when it is running according to the workflow deployment information in the target resource domain; and transmit the system identity used by the workflow execution unit when it is running to the master control node 11. Among them, the target resource domain can be any resource domain applied for by the target tenant, and the target tenant can be any tenant in the system. The target tenant can be an individual, an enterprise, a company, or a department of a company, etc. There are generally multiple workflow execution units, but of course, there can also be one. The workflow execution unit can be any service unit that can realize certain functions and has execution capabilities, such as a container, a virtual machine, a process, or a thread, etc.

[0038] On the side of the master control node 11, a system identity that the target resource domain is authorized to use is maintained in advance. Based on this, when the master control node 11 receives the system identity used by the workflow execution unit when it is running, sent by the workflow management node 13, it can determine whether the system identity used by the workflow execution unit when it is running belongs to the system identity that the target resource domain is authorized to use; and when it is determined that the system identity used by the workflow execution unit when it is running belongs to the system identity that the target resource domain is authorized to use, the workflow execution unit is deployed to the work node 12 in the target resource domain. For the workflow execution unit, during its operation, it can access the shared storage resources of the distributed computing system 10 based on the memory access permissions corresponding to the system identity used when it is running.

[0039] In an embodiment of the present application, in order to successfully deploy a workflow execution unit to a corresponding work node 12, in addition to the system identity used when the workflow execution unit is running, a workflow execution unit is also required. In an optional embodiment, the tenant can provide the workflow execution unit directly to the master control node 11, and the master control node 11 directly obtains the workflow execution unit submitted by the tenant. Alternatively, in another optional embodiment, the workflow management node 13 obtains the workflow execution unit with an execution order from the workflow deployment information, and provides the obtained workflow execution unit to the master control node 11. For the tenant, it only needs to interact with the workflow management node 13 during the workflow deployment process, and the operation is relatively simple.

[0040] Further optionally, if the master control node 11 manages with the workflow execution unit as the granularity, the workflow management node 13 can obtain the workflow execution unit from the workflow deployment information, and transmit the workflow execution unit to the master control node 11 according to the execution order between the workflow execution units. Or,

[0041] Further optionally, the master control node 11 manages in units of workflow execution unit models, and the workflow management node 13 can generate at least one workflow execution unit model identifiable by the master control node 11 according to the workflow deployment information, each workflow execution unit model includes at least one workflow execution unit; according to the temporal dependency relationship between at least one workflow execution unit model, at least one workflow execution unit model is sent to the master control node 11 in sequence, so that the master control node 11 can deploy the workflow execution unit in units of workflow execution unit models. Among them, the workflow execution unit model is a management model of the workflow execution unit.

[0042] For the master control node 11, it can receive at least one workflow execution unit model sent in sequence by the workflow management node 13; for each workflow execution unit model, it is determined whether the system identity used by the workflow execution unit in the workflow execution unit model during operation belongs to the system identity that the target resource domain is authorized to use; if the judgment result is yes, the workflow execution unit in the workflow execution unit model is deployed to the work node in the target resource domain. In this process, the master control node 11 can schedule the work nodes in the target resource domain so as to successfully deploy the workflow execution unit in each workflow execution unit model to the corresponding work node. Among them, the scheduling process for any work node can be to notify the work node that the workflow execution unit needs to be deployed, and send the workflow execution unit that needs to be deployed to the work node to the work node. Among them, the notification process and the process of sending the workflow execution unit can be the same communication process or different communication processes.

[0043] In an optional embodiment, in addition to the workflow execution unit and the system identity used by the workflow execution unit when running, the workflow deployment information may also include the identity of the target resource domain and the user identity credentials for applying for workflow deployment. Among them, the identity of the target resource domain is used to identify in which resource domain the workflow needs to be deployed; the user identity credentials are used to identify which tenant is applying for workflow deployment. Considering that different tenants have their own resource domains, the workflow management node 13 can also obtain the identity of the target resource domain and the user identity credentials for applying for workflow deployment from the workflow deployment information; send the identity of the target resource domain and the user identity credentials to the master control node 11, so that the master control node 11 can determine whether the identity of the target resource domain and the user identity credentials correspond, that is, to verify the legitimacy of the resource domain; and receive the determination result returned by the master control node 11. Further, when the master control node 11 determines that the identity of the target resource domain and the user identity credentials correspond, at least one workflow execution unit model is sent to the master control node 11 in sequence according to the temporal dependency relationship between at least one workflow execution unit model.

[0044] For the master control node 11, the correspondence between the identifiers of resource domains of different tenants and the user identity credentials of different tenants is also maintained. Based on the correspondence, after receiving the identifier and user identity credentials of the target resource domain sent by the workflow management node 13, the master control node 11 can query the maintained correspondence to determine whether the identifier of the target resource domain and the user identity credentials correspond, and return the determination result to the workflow management node 13.

[0045] Further optionally, the workflow management node 13 can send at least one workflow execution unit model to the master control node 11 in sequence according to the temporal dependency between at least one workflow execution unit model when the master control node 11 determines that the identifier of the target resource domain corresponds to the user identity credential, so that the master control node 11 can deploy the workflow execution unit in units of the workflow execution unit model. For the master control node 11, when it is determined that the identifier of the target resource domain corresponds to the user identity credential, it can continue to receive at least one workflow execution unit model sent in sequence by the workflow management node 13; for each workflow execution unit model, it is determined whether the system identity used by the workflow execution unit in the workflow execution unit model during operation belongs to the system identity that the target resource domain is authorized to use; if the judgment result is yes, the workflow execution unit in the workflow execution unit model is deployed to the working node in the target resource domain.

[0046] In an optional embodiment, each tenant includes an operation and maintenance manager and a workflow deployment personnel. The operation and maintenance manager is equivalent to the administrator of the tenant in the distributed computing system 10, and has global configuration and management authority, for example, he can apply for a resource domain from the distributed computing system 10, configure the security parameters of the resource domain, configure the use authority for different workflow deployment personnel, issue relevant parameters, etc. The workflow deployment personnel are mainly responsible for deploying workflows in the resource domain. Optionally, the master control node 11 can provide a resource domain security configuration interface for the operation and maintenance manager of the tenant, for the operation and maintenance manager to configure the security parameters of the resource domain. Among them, the security parameters of the resource domain may include but are not limited to: user identity credentials of the resource domain, the identifier of the resource domain, and the system identity identifier that the resource domain is authorized to use. For the operation and maintenance manager, the security parameters of the resource domain can be configured through the resource domain security configuration interface provided by the master control node 11. After the master control node 11 obtains the security parameters of the resource domain configured by the operation and maintenance manager, it can establish a corresponding relationship between these security parameters, mainly referring to the corresponding relationship between the user identity credentials of the resource domain, the identifier of the resource domain, and the system identity identifier that the resource domain is authorized to use.

[0047] For the target resource domain, the corresponding tenant is called the target tenant. The master control node 11 will also provide a resource domain security configuration interface to the operation and maintenance management personnel of the target tenant. For example, the master control node 11 can display the resource domain security configuration interface to the operation and maintenance management personnel based on the trigger operation of the operation and maintenance management personnel of the target tenant requesting access to the resource domain security configuration interface. Among them, the resource domain security configuration interface can be a web page, an application page or a command window, etc. Depending on the different implementation methods of the resource domain security configuration interface, the trigger operation of the operation and maintenance management personnel requesting access to the resource domain security configuration interface will also be different. Taking the resource domain security configuration interface as a web page as an example, the operation and maintenance management personnel can enter the link of the web page in the browser on the terminal device they use, click the access control to enter the login page, and enter the login account and password on the login page, and then display the web page in the browser of the terminal device they use.

[0048] The resource domain security configuration interface contains configuration items for security parameters related to the target resource domain. After viewing the resource domain security configuration interface, the target tenant's operation and maintenance management personnel can configure the security parameters of the target resource domain through the configuration items on the resource domain security configuration interface, such as the user identity credentials of the target resource domain, the identifier of the target resource domain, and the system identifier that the target resource domain is authorized to use. Among them, the system identifier that the target resource domain is authorized to use can be a system identifier range or a series of specific system identifiers.

[0049] After the master control node 11 obtains the security parameters of the target resource domain configured by the operation and maintenance management personnel of the target tenant, it can establish a correspondence between these security parameters, mainly referring to establishing a correspondence between the user identity credentials of the target resource domain, the identifier of the target resource domain, and the system identity identifier that the target resource domain is authorized to use. Furthermore, during the workflow deployment process, the system identity identifier used by the workflow execution unit during operation can be verified to be legal based on the system identity identifier that the target resource domain is authorized to use.

[0050] In the embodiment of the present application, the method by which the workflow management node 13 obtains the workflow deployment information is not limited. For example, the workflow management node 13 can provide a workflow deployment interface to the workflow deployment personnel, so that the workflow deployment personnel can configure the workflow deployment information on the workflow deployment interface; and obtain the workflow deployment information configured by the workflow deployment personnel on the workflow deployment interface. The workflow deployment information here can mainly include: the identifier of the target resource domain where the workflow needs to be deployed, the user identity credentials for applying for the deployment of the workflow, and the system identity identifier used when the workflow execution unit is running, etc.

[0051] For the workflow deployment personnel of the target tenant, when it is necessary to deploy a workflow, a trigger operation of requesting access to the workflow deployment interface can be issued. For the workflow management node 13, the workflow deployment interface can be displayed to the workflow deployment personnel based on the trigger operation of requesting access to the workflow deployment interface issued by the workflow deployment personnel of the target tenant. The workflow deployment interface contains the configuration items required for deploying the workflow. The workflow deployment personnel of the target tenant can configure the workflow deployment information through the configuration items on the workflow deployment interface, such as the identifier of the target resource domain where the workflow needs to be deployed, the user identity credentials for applying for the deployment of the workflow, and the system identity used by the workflow execution unit when running.

[0052] The workflow deployment interface may be a web page, an application page or a command window, etc. Depending on the different implementations of the workflow deployment interface, the triggering operation for the workflow deployment personnel to request access to the workflow deployment interface may also be different.

[0053] In an optional embodiment, after obtaining the workflow deployment information, the workflow management node 13 can obtain information such as the identifier of the target resource domain, the user identity credentials for applying for workflow deployment, and the system identity identifier used by the workflow execution unit at runtime from the workflow deployment information. First, the identifier of the target resource domain and the user identity credentials are sent to the master control node 11 so that the master control node 11 can determine whether the identifier of the target resource domain and the user identity credentials correspond, that is, to verify the legitimacy of the resource domain; and receive the determination result returned by the master control node 11. Further, when the master control node 11 determines that the identifier of the target resource domain and the user identity credentials correspond, at least one workflow execution unit model that can be identified by the master control node 11 is generated, and each workflow execution unit model contains at least one workflow execution unit; according to the temporal dependency relationship between at least one workflow execution unit model, at least one workflow execution unit model and the system identity identifier used by the workflow execution unit in the workflow execution unit model at runtime are sent to the master control node 11 in sequence. The main control node 11 receives at least one workflow execution unit model sent sequentially by the workflow management node 13; for each workflow execution unit model, it is determined whether the system identity identifiers used by the workflow execution units in the workflow execution unit model when running belong to the system identity identifiers that the target resource domain is authorized to use; if the judgment result is yes, the workflow execution units in the workflow execution unit model are deployed to the working nodes in the target resource domain.

[0054] In an embodiment of the present application, workflow deployment is combined with a distributed computing system that can serve different tenants, allowing tenants to deploy workflows in their resource domains; during the workflow deployment process, a system identity used at runtime is specified for the workflow execution unit to distinguish the memory access rights of different workflow execution units to shared storage resources in the distributed computing system. Each workflow execution unit accesses the shared storage resources in the system based on the memory access rights corresponding to the system identity used at runtime, which can achieve read-write isolation between different tenants and ensure the security of data in shared storage resources.

[0055] It is worth noting that in the distributed computing system 10 of the embodiment of the present application, the working node can be a containerized application. Based on this, a container orchestration scheduling system can be used in the system to create, manage, discover, access and configure the working nodes in the system, thereby freeing the operation and maintenance personnel of the system. The container orchestration scheduling system refers to a system that can automatically deploy, expand and manage containerized applications. For example, Kubernetes (abbreviated as K8s) can be used, but it is not limited to this. In addition, the distributed computing system 10 of the embodiment of the present application can be applied to various application scenarios, such as gene sequencing scenarios based on cloud computing.

[0056] Relying on the natural resource elasticity advantage of cloud computing, the genetic industry has seen a more significant reduction in data storage and large-scale computing costs based on massive data. In the embodiments of this application, Kubernetes technology and workflow deployment can be combined to provide a workflow solution for gene sequencing, which is conducive to improving key capabilities such as high-concurrency processing, resource scheduling, and large file storage that are relied on in the gene sequencing computing process.

[0057] Based on the above, the embodiment of the present application also provides a distributed computing system implemented based on the container orchestration scheduling system, such as Figure 1b The distributed computing system 20 includes: a master control node 21, namespaces 24 corresponding to different tenants, and a workflow management node 23. Each namespace 24 includes a work node 22.

[0058] In this embodiment, a container orchestration and scheduling system, such as Kubernetes, is used to logically divide the physical devices in the distributed computing system 20 into a master node 21 and a worker node 22. The master node 21 and the worker node 22 are deployed on the physical devices in the distributed computing system 20. Optionally, the master node 21 and the worker node 22 are deployed on different physical devices. Figure 1bIn the figure, a distributed computing system based on Kubernetes is used as an example. Among them, the master node 21 can be used as a control system of the container orchestration and scheduling system. A group of processes related to cluster management are running on the master node 21. Taking Kubernetes as an example, these processes include but are not limited to: kube-apiserver, kube-controller-manager and kube-scheduler, etc. These processes realize the resource management of the entire cluster, container group (such as Pod in Kubernetes) scheduling, elastic scaling, security control, system monitoring and error correction and other management capabilities, and are all completed automatically. The working node 22, as a service node in the distributed computing system 20, runs containerized applications. These working nodes 22 are distributed in the namespaces 24 of different tenants. On the working node 22, the container group is the smallest operating unit managed by the container orchestration and scheduling system, and the container group contains at least one container. Taking Kubernetes as an example, the smallest operating unit managed by Kubernetes is Pod. Pod is literally translated as pod. In this embodiment, it refers to a collection of a group of containers, that is, the container group described above. The working node 22 runs processes related to the container group in the container orchestration and scheduling system. Taking Kubernetes as an example, the processes related to the container group include but are not limited to: Kubernetes's kubelet and kube-proxy service processes, which are responsible for the creation, startup, monitoring, restart, and destruction of container groups (such as Pods) and the implementation of software-based load balancers.

[0059] Among them, the role-based access control (RBAC) authorization strategy is used in the container orchestration and scheduling system. Based on the RBAC authorization strategy, each tenant has different user credentials and their own namespaces in the distributed system 20, and the user credentials of each tenant can uniquely identify the tenant. The user credentials of the tenant can be any information that can uniquely identify the tenant, for example, it can be the ID of the tenant in the distributed system 20, or it can be the tenant name, account, telephone number, email address and / or home address registered by the tenant in the distributed system 20. Namespace is an important concept in the container orchestration and scheduling system, such as Kubernetes. By "assigning" the objects inside the distributed system 20 to different Namespaces, different projects, groups or user groups that are logically grouped are formed, so that different groups can be managed separately while sharing the resources of the entire system. For example, the container group (such as Pod), RC, and service (Service) created by the tenant in the distributed computing system 20 will be created in the Namespace corresponding to the tenant. Each namespace has its own identifier, such as an ID or name. In this embodiment, the corresponding relationship between the user identity credentials of the tenant and the identifier of the corresponding namespace is maintained.

[0060] In the distributed computing system 20, in addition to the private resources exclusively enjoyed by each tenant, some global shared resources that can be shared by different tenants are also included. In the present embodiment, the global shared resources mainly refer to the shared storage resources that can be shared by different tenants. The shared storage resources can be local storage resources or network storage resources, such as NAS. In the present embodiment, the tenant's request identity for the shared storage resources is based on the system identity at the time of container runtime, and each system identity corresponds to certain memory access permissions. It is worth noting that in a container orchestration and scheduling system, such as the Kubernetes framework, the system identity at the time of container runtime and the user identity credentials under the access control of the native RBAC of the container orchestration and scheduling system (such as Kubernetes) belong to two different account systems.

[0061] In this embodiment, different tenants can deploy workflows in their own namespaces with the help of the workflow management node 23 in the system, that is, the containers required for the workflows need to be deployed on the work node 22, and based on the native RBAC authorization policy of the container orchestration and scheduling system (such as Kubernetes), the logical isolation of the workflows deployed in the multi-tenant scenario can be realized on the namespace. However, there is no secure isolation capability of the container operation process to read and write shared storage resources in the native framework of the container orchestration and scheduling system (such as Kubernetes), and for the characteristics of massive data reading and writing and the privacy of genes themselves in the gene sequencing scenario and other similar scenarios, the secure isolation of the shared storage resources read and write during the container operation process is an urgent problem to be solved. Based on this, in this embodiment, by extending the designated user layer in the workflow deployment process, the system identity used in the runtime of the container required by the workflow is specified, and the container under the bound namespace is combined with the native (PodSecurityPolicy, PSP) model to verify the security parameters used in the runtime of the container under the bound namespace, ensuring the correctness of the system identity used in the runtime specified for the container, thereby realizing the secure isolation of the shared storage resources read and written by different containers at runtime in the multi-tenant scenario.

[0062] Based on the above, taking the deployment of a workflow in any namespace of any tenant as an example, the workflow deployment principle in the distributed computing system 20 is described. For the convenience of description and distinction, the any tenant is referred to as the target tenant, and any namespace of the tenant is referred to as the target namespace. The workflow deployment principle in the distributed computing system 20 is as follows:

[0063] The workflow management node 23 obtains the system identity used by the container runtime required by the workflow to be deployed according to the workflow deployment information in the target namespace; transmits the system identity used by the container runtime to the master control node 21; the master control node 21 compares the system identity used by the container runtime with the system identity that the target namespace is authorized to use; and if the system identity used by the container runtime belongs to the system identity that the target namespace is authorized to use, the container is deployed to the working node under the target namespace. In this way, the container can access the shared storage resources of the distributed computing system 20 based on the memory access permissions corresponding to the system identity used by it at runtime.

[0064] In an optional embodiment, considering that the minimum operating unit of the container orchestration and scheduling system is a container group, the workflow management node is also used to: generate at least one container group model that can be recognized by the master control node 21 according to the workflow deployment information, and each container group model contains at least one container; according to the timing dependency between at least one container group model, send at least one container group model to the master control node 21 in sequence, so that the master control node 21 can deploy the container in units of container group models. The master control node 21 can receive at least one container group model sent in sequence by the workflow management node 23; for each received container group model, determine whether the system identity used by the container in the container group model when running belongs to the system identity that the target namespace is authorized to use, and if the judgment result is yes, deploy the container in the container group model to the working node under the target namespace. Taking Kubernetes as an example, the minimum operating unit it manages is Pod, and the above container group model can be a Pod model.

[0065] In an optional embodiment, in addition to the container required by the workflow and the system identity used when the container is running, the workflow deployment information may also include the identifier of the target namespace and the user identity credentials for applying to deploy the workflow. Among them, the identifier of the target namespace is used to identify in which namespace the workflow needs to be deployed; the user identity credentials are used to identify which tenant is applying to deploy the workflow. Considering that different tenants have their own namespaces, the workflow management node 13 can also obtain the identifier of the target namespace and the user identity credentials for applying to deploy the workflow from the workflow deployment information; send the identifier of the target namespace and the user identity credentials to the master control node 11, so that the master control node 11 can determine whether the identifier of the target namespace and the user identity credentials correspond, that is, to verify the legitimacy of the namespace; and receive the determination result returned by the master control node 11.

[0066] For the master control node 11, the correspondence between the identifiers of the namespaces of different tenants and the user identity credentials of different tenants is also maintained. Based on the correspondence, after receiving the identifier and user identity credentials of the target namespace sent by the workflow management node 13, the master control node 11 can query the maintained correspondence to determine whether the identifier and user identity credentials of the target namespace correspond, and return the determination result to the workflow management node 13.

[0067] Further optionally, the workflow management node 13 can send at least one container group model to the master control node 11 in sequence according to the timing dependency between at least one container group model (such as a Pod model) when the master control node 11 determines that the identifier of the target namespace corresponds to the user identity credential, so that the master control node 11 can deploy containers in units of container group models. For the master control node 11, when it is determined that the identifier of the target namespace corresponds to the user identity credential, it can continue to receive at least one container group model sent in sequence by the workflow management node 13; for each container group model, it is determined whether the system identity used by the container in the container group model when it is running belongs to the system identity that the target namespace is authorized to use; if the judgment result is yes, the container in the container group model is deployed to the working node in the target namespace.

[0068] In an optional embodiment, the target tenant includes an operation and maintenance manager and a workflow deployment personnel. The operation and maintenance manager is equivalent to the administrator of the target tenant in the distributed computing system 20, and has global configuration and management authority, for example, it can apply for a namespace from the distributed computing system 20, configure the security parameters of the namespace, configure the use permissions for different workflow deployment personnel, issue relevant parameters, etc. The workflow deployment personnel are mainly responsible for deploying workflows in the namespace. Optionally, the master control node 11 can provide a namespace security configuration interface for the operation and maintenance manager of the target tenant, for the operation and maintenance manager to configure the security parameters of the target namespace. Among them, the security parameters of the target namespace may include but are not limited to: user identity credentials of the target namespace, the identifier of the target namespace, and the system identity identifier that the target namespace is authorized to use. For the operation and maintenance manager, the security parameters of the target namespace can be configured through the namespace security configuration interface provided by the master control node 11. After the master control node 11 obtains the security parameters of the target namespace configured by the operation and maintenance manager, it can establish a corresponding relationship between these security parameters, mainly referring to the corresponding relationship between the user identity credentials of the target namespace, the identifier of the target namespace, and the system identity identifier that the target namespace is authorized to use.

[0069] The namespace security configuration interface may be a web page, an application page, or a command window. Depending on the implementation of the namespace security configuration interface, the triggering operation for the operation and maintenance manager to request access to the namespace security configuration interface may also be different. For example, if the namespace security configuration interface is a web page, the operation and maintenance manager may enter the link of the web page in the browser of the terminal device he / she uses, click the access control to enter the login page, enter the login account and password on the login page, and then display the web page in the browser of the terminal device he / she uses.

[0070] In the embodiment of the present application, the way in which the workflow management node 23 obtains the workflow deployment information is not limited. For example, the workflow management node 23 is also used to provide a workflow deployment interface for the workflow deployment personnel of the target tenant, and obtain the workflow deployment information configured by the workflow deployment personnel on the workflow deployment interface. The workflow deployment information here includes the identifier of the target namespace, the user identity credentials for applying for the deployment of the workflow, and the system identity used by the container runtime required for the workflow to be deployed.

[0071] For the workflow deployer of the target tenant, when it is necessary to deploy a workflow, a trigger operation of requesting access to the workflow deployment interface can be issued. For the workflow management node 23, the workflow deployment interface can be displayed to the workflow deployer based on the trigger operation of requesting access to the workflow deployment interface issued by the workflow deployer of the target tenant. The workflow deployment interface contains the configuration items required for deploying the workflow. The workflow deployer of the target tenant can configure the workflow deployment information through the configuration items on the workflow deployment interface, such as the identifier of the target namespace where the workflow needs to be deployed, the user identity credentials for applying for the deployment of the workflow, and the system identity used by the container runtime.

[0072] The workflow deployment interface may be a web page, an application page or a command window, etc. Depending on the different implementations of the workflow deployment interface, the triggering operation for the workflow deployment personnel to request access to the workflow deployment interface may also be different.

[0073] In an optional embodiment, after obtaining the workflow deployment information, the workflow management node 23 can obtain information such as the identifier of the target namespace, the user identity credentials for applying for workflow deployment, and the system identity identifier used when the container is running from the workflow deployment information. First, the identifier of the target namespace and the user identity credentials are sent to the master control node 21 so that the master control node 21 can determine whether the identifier of the target namespace and the user identity credentials correspond, that is, to verify the legality of the namespace; and receive the determination result returned by the master control node 21. Further, when the master control node 21 determines that the identifier of the target namespace and the user identity credentials correspond, the workflow management node 23 generates at least one container group model recognizable by the master control node 21 according to the workflow deployment information, such as (Pod model), and each container group model contains at least one container; according to the temporal dependency between at least one container group model, at least one container group model and the system identity identifier used when the container in the container group model is running are sent to the master control node 21 in sequence. The master control node 21 receives at least one container group model sent sequentially by the workflow management node 13; for each container group model, it is determined whether the system identity identifiers used by the containers in the container group model when running belong to the system identity identifiers that the target namespace is authorized to use; if the judgment result is yes, the containers in the container group model are deployed to the working nodes in the target namespace.

[0074] It is worth noting that the workflow management node 23 of this embodiment can adopt but is not limited to: argo workflow engine. In the case of adopting the argo workflow engine, the function of the argo workflow engine can be extended according to the function of the workflow management node 23 of this application. Among them, by extending the native argo workflow engine, adding the function of transmitting the system identity used in the container runtime to the container, and by modifying the PSP verification function when deploying the container, the limitation of the native PSP verification of the container orchestration scheduling system (such as Kubernetes) on the security verification of the container in the container group model can be avoided, so that the system identity used in the runtime can be specified for the container and the security verification can be completed. Only containers that meet the security parameters specified in the PSP model will pass the verification and allow deployment. At the same time, it can solve the access rights of the container to the storage directory in the shared storage resource at the runtime, and realize the security isolation of read and write access to shared storage resources in a multi-tenant environment.

[0075] Figure 1b The distributed computing system 20 shown can be used as Figure 1a A specific implementation of the distributed computing system 10 shown in FIG. Figure 1a The distributed computing system 10 shown is the same or similar. For the contents not involved in this embodiment, please refer to the description of the previous embodiment and will not be repeated here.

[0076] Figure 2a A flowchart of a workflow deployment method provided for an exemplary embodiment of the present application is provided. This embodiment is described from the perspective of a workflow management node, such as Figure 2a As shown, the method includes:

[0077] 201a. According to the workflow deployment information in the target resource domain, obtain the system identity used by the workflow execution unit when it is running; wherein the workflow execution unit accesses the shared storage resources of the distributed computing system to which the workflow management node belongs based on the memory access permission corresponding to the system identity used by the workflow execution unit when it is running.

[0078] 202a. The system identity used by the workflow execution unit when running is transmitted to the master control node in the distributed computing system, so that the master control node can deploy the workflow execution unit to the working node in the target resource domain when the system identity used by the workflow execution unit when running is a system identity that the target resource domain is authorized to use.

[0079] Figure 2b A flowchart of a workflow deployment method provided for an exemplary embodiment of the present application. This embodiment is described from the perspective of a master control node, such as Figure 2b As shown, the method includes:

[0080] 201b. Receive a system identity identifier sent by the workflow management node and used when the workflow execution unit is running. The workflow execution unit is an execution unit of the workflow that needs to be deployed in the target resource domain.

[0081] 202b. When the system identity used by the workflow execution unit during operation belongs to the system identity that the target resource domain is authorized to use, the workflow execution unit is deployed to the working node in the target resource domain; wherein the workflow execution unit accesses the shared storage resources of the distributed computing system based on the memory access permission corresponding to the system identity used by the workflow execution unit during operation.

[0082] In an embodiment of the present application, the master control node and the workflow management node in the distributed computing system cooperate with each other to allow tenants to deploy workflows in their resource domains. During the workflow deployment process, a system identity identifier used at runtime can be specified for the workflow execution unit to distinguish the memory access rights of different workflow execution units to shared storage resources in the distributed computing system. Each workflow execution unit accesses the shared storage resources in the system based on the memory access rights corresponding to the system identity identifier used at runtime, which can achieve read-write isolation between different tenants and ensure the security of data in shared storage resources.

[0083] In an optional embodiment, in the above method embodiment, the workflow management node can also generate at least one workflow execution unit model identifiable by the master control node based on the workflow deployment information, each workflow execution unit model includes at least one workflow execution unit; according to the timing dependency relationship between at least one workflow execution unit model, at least one workflow execution unit model is sent to the master control node in sequence, so that the master control node can deploy the workflow execution unit in units of workflow execution unit model. Correspondingly, the master control node can also receive at least one workflow execution unit model sent in sequence by the workflow management node, each workflow execution unit model includes at least one workflow execution unit; for each workflow execution unit model, it is determined whether the system identity used by the workflow execution unit in the workflow execution unit model during operation belongs to the system identity that the target resource domain is authorized to use, and if the judgment result is yes, the workflow execution unit in the workflow execution unit model is deployed to the working node in the target resource domain.

[0084] In an optional embodiment, in the above method embodiment, the workflow management node can also obtain the identifier of the target resource domain and the user identity credentials for applying for workflow deployment from the workflow deployment information; send the identifier of the target resource domain and the user identity credentials to the master control node so that the master control node can determine whether the identifier of the target resource domain and the user identity credentials correspond; and receive the determination result of whether the identifier of the target resource domain and the user identity credentials correspond returned by the master control node. Correspondingly, the master control node can also receive the identifier of the target resource domain and the user identity credentials for applying for workflow deployment sent by the workflow management node; determine whether the identifier of the target resource domain and the user identity credentials correspond based on the correspondence relationship between the identifier of the resource domain and the user identity credentials maintained in advance, and return the determination result to the workflow management node.

[0085] Further, in the above method embodiment, the workflow management node can send at least one workflow execution unit model to the master control node in sequence according to the timing dependency between at least one workflow execution unit model when the master control node determines that the identifier of the target resource domain corresponds to the user identity credential, so that the master control node can deploy the workflow execution unit in units of the workflow execution unit model. For the master control node, when it is determined that the identifier of the target resource domain corresponds to the user identity credential, it can continue to receive at least one workflow execution unit model sent in sequence by the workflow management node; for each workflow execution unit model, it is determined whether the system identity used by the workflow execution unit in the workflow execution unit model during operation belongs to the system identity that the target resource domain is authorized to use; if the judgment result is yes, the workflow execution unit in the workflow execution unit model is deployed to the working node in the target resource domain.

[0086] In an optional embodiment, in the above method embodiment, the workflow management node can also provide a workflow deployment interface for the workflow deployment personnel of the target tenant, and obtain the workflow deployment information configured by the workflow deployment personnel on the workflow deployment interface; wherein the workflow deployment information includes the identifier of the target resource domain where the workflow needs to be deployed, the user identity credentials for applying for workflow deployment, and the system identity identifier used when the workflow execution unit is running; the target tenant corresponds to the target resource domain.

[0087] In an optional embodiment, in the above method embodiment, the master control node can also provide a resource domain security configuration interface for the operation and maintenance management personnel of the target tenant, so that the operation and maintenance management personnel can configure the security parameters of the target resource domain; the security parameters include the user identity credentials of the target resource domain, the identifier of the target resource domain, and the system identity identifier that the target resource domain is authorized to use; establish a correspondence between the user identity credentials of the target resource domain, the identifier of the target resource domain, and the range of running user identity identifiers that the target resource domain is authorized to use; wherein, the target tenant corresponds to the target resource domain.

[0088] It should be noted that in some of the processes described in the above embodiments and the accompanying drawings, multiple operations that appear in a specific order are included, but it should be clearly understood that these operations may not be executed in the order in which they appear in this article or executed in parallel, and the sequence numbers of the operations, such as 201a, 202a, etc., are only used to distinguish between different operations, and the sequence numbers themselves do not represent any execution order. In addition, these processes may include more or fewer operations, and these operations may be executed in sequence or in parallel. It should be noted that the descriptions of "first", "second", etc. in this article are used to distinguish different messages, devices, modules, etc., do not represent the order of precedence, and do not limit the "first" and "second" to be different types.

[0089] Figure 3 Schematic diagram of a node device provided by an exemplary embodiment of the present application. The node device can be implemented as a workflow management node in the aforementioned embodiment, such as Figure 3 As shown, the node device includes: a memory 31, a processor 32 and a communication component 33.

[0090] The memory 31 is used to store computer programs and can be configured to store various other data to support operations on the node device. Examples of such data include instructions for any application or method operating on the node device, contact data, phone book data, messages, pictures, videos, etc.

[0091] The processor 32 is coupled to the memory 31 and is used to execute the computer program in the memory 31 to:

[0092] According to the workflow deployment information in the target resource domain, obtain the system identity used by the workflow execution unit when it runs;

[0093] The system identity used by the workflow execution unit during operation is transmitted to the master node in the distributed computing system to which the workflow management node belongs through the communication component 33, so that the master node can deploy the workflow execution unit to the working node in the target resource domain when the system identity used by the workflow execution unit during operation belongs to the system identity that the target resource domain is authorized to use; wherein the workflow execution unit accesses the shared storage resources of the distributed computing system based on the memory access permissions corresponding to the system identity used by the workflow execution unit during operation.

[0094] In an optional embodiment, the processor 32 is also used to: generate at least one workflow execution unit model identifiable by the master control node based on the workflow deployment information, each workflow execution unit model includes at least one workflow execution unit; according to the timing dependency relationship between at least one workflow execution unit model, send at least one workflow execution unit model to the master control node in sequence through the communication component 33, so that the master control node can deploy the workflow execution unit in units of the workflow execution unit model.

[0095] In an optional embodiment, the processor 32 is also used to: obtain the identifier of the target resource domain and the user identity credentials for applying to deploy the workflow from the workflow deployment information before sending at least one workflow execution unit model to the master control node in sequence; send the identifier of the target resource domain and the user identity credentials to the master control node through the communication component 33, so that the master control node can determine whether the identifier of the target resource domain and the user identity credentials correspond; and receive the determination result of whether the identifier of the target resource domain and the user identity credentials correspond returned by the master control node.

[0096] In an optional embodiment, the processor 32 is also used to: provide a workflow deployment interface for the workflow deployment personnel of the target tenant, and obtain the workflow deployment information configured by the workflow deployment personnel on the workflow deployment interface; wherein the workflow deployment information includes the identifier of the target resource domain where the workflow needs to be deployed, the user identity credentials for applying for workflow deployment, and the system identity identifier used when the workflow execution unit is running; the target tenant corresponds to the target resource domain.

[0097] Further, if Figure 3 As shown, the node device also includes: a display 34, a power supply component 35, an audio component 36 and other components. Figure 3 Only some components are shown schematically, which does not mean that the node equipment only includes Figure 3 In addition, depending on the different forms of node equipment implementation, Figure 3 Components with dotted lines are optional, not required.

[0098] Accordingly, an embodiment of the present application further provides a computer-readable storage medium storing a computer program, which, when executed, can implement the steps that can be executed by the workflow management node in the above method embodiment.

[0099] Figure 4 FIG. 1 is a schematic diagram of the structure of another node device provided by an exemplary embodiment of the present application. The node device can be implemented as a master control node in the aforementioned embodiment, such as Figure 4 As shown, the node device includes: a memory 41, a processor 42 and a communication component 43.

[0100] The memory 41 is used to store computer programs and can be configured to store various other data to support operations on the node device. Examples of such data include instructions for any application or method operating on the node device, contact data, phone book data, messages, pictures, videos, etc.

[0101] The processor 42 is coupled to the memory 41 and is configured to execute the computer program in the memory 41 to:

[0102] Receiving, through the communication component 43, a system identity used by a workflow execution unit during operation sent by the workflow management node, where the workflow execution unit is an execution unit of a workflow that needs to be deployed in a target resource domain;

[0103] When the system identity used by the workflow execution unit when it is running belongs to the system identity that the target resource domain is authorized to use, the workflow execution unit is deployed to the working node in the target resource domain;

[0104] The workflow execution unit accesses the shared storage resources of the distributed computing system based on the memory access rights corresponding to the system identity used during its operation.

[0105] In an optional embodiment, the processor 42 is specifically used to: receive at least one workflow execution unit model sent in sequence by the workflow management node through the communication component 43, each workflow execution unit model including at least one workflow execution unit; for each workflow execution unit model, determine whether the system identity identifiers used by the workflow execution units in the workflow execution unit model during operation all belong to the system identity identifiers that the target resource domain is authorized to use; if the determination result is yes, deploy the workflow execution units in the workflow execution unit model to the working nodes in the target resource domain.

[0106] In an optional embodiment, the processor 42 is also used to: receive the identifier of the target resource domain and the user identity credentials for applying to deploy the workflow sent by the workflow management node through the communication component 43; determine whether the identifier of the target resource domain and the user identity credentials correspond based on the correspondence between the identifier of the resource domain and the user identity credentials maintained in advance, and return the determination result to the workflow management node.

[0107] In an optional embodiment, the processor 42 is also used to: provide a resource domain security configuration interface for the operation and maintenance management personnel of the target tenant, so that the operation and maintenance management personnel can configure the security parameters of the target resource domain; the security parameters include the user identity credentials of the target resource domain, the identifier of the target resource domain, and the system identity identifier that the target resource domain is authorized to use; establish a correspondence between the user identity credentials of the target resource domain, the identifier of the target resource domain, and the range of operating user identity identifiers that the target resource domain is authorized to use; wherein the target tenant corresponds to the target resource domain.

[0108] Further, if Figure 4 As shown, the node device also includes: a display 44, a power supply component 45, an audio component 46 and other components. Figure 4 Only some components are shown schematically, which does not mean that the node equipment only includes Figure 4 In addition, depending on the different forms of node equipment implementation, Figure 4 Components with dotted lines are optional, not required.

[0109] Accordingly, an embodiment of the present application further provides a computer-readable storage medium storing a computer program, which, when executed, can implement the steps that can be executed by the main control node in the above method embodiment.

[0110] Above Figure 3 and Figure 4 The memory in can be implemented by any type of volatile or non-volatile storage device or a combination of them, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk.

[0111] Above Figure 3 and Figure 4The communication component in is configured to facilitate wired or wireless communication between the device where the communication component is located and other devices. The device where the communication component is located can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component may also include a near field communication (NFC) module, a radio frequency identification (RFID) technology, an infrared data association (IrDA) technology, an ultra-wideband (UWB) technology, a Bluetooth (BT) technology, etc.

[0112] Above Figure 3 and Figure 4 The display in the embodiment includes a screen, which may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation.

[0113] Above Figure 3 and Figure 4 The power supply component in the device provides power to various components of the device where the power supply component is located. The power supply component may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the device where the power supply component is located.

[0114] Above Figure 3 and Figure 4 The audio component in can be configured to output and / or input audio signals. For example, the audio component includes a microphone (MIC), and when the device where the audio component is located is in an operating mode, such as a call mode, a recording mode, and a speech recognition mode, the microphone is configured to receive an external audio signal. The received audio signal can be further stored in a memory or sent via a communication component. In some embodiments, the audio component also includes a speaker for outputting an audio signal.

[0115] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0116] The present invention is described with reference to the flowchart and / or block diagram of the method, device (system), and computer program product according to the embodiment of the present invention. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the process and / or box in the flowchart and / or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0117] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0118] These computer program instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

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

[0120] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0121] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0122] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0123] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A distributed computing system, characterized in that: include: The master control node, workflow management node, and resource domains corresponding to different tenants; The workflow management node is used to obtain the system identity used by the workflow execution unit when it is running according to the workflow deployment information in the target resource domain; Transmitting the system identity used by the workflow execution unit when running to the main control node; The master control node is used to deploy the workflow execution unit to a working node in the target resource domain when the system identity used by the workflow execution unit during operation belongs to the system identity that the target resource domain is authorized to use; The workflow execution unit accesses the shared storage resources of the distributed computing system based on the memory access rights corresponding to the system identity used during its operation.

2. The system according to claim 1, characterized in that The workflow management node is also used for: Generating at least one workflow execution unit model identifiable by the master control node according to the workflow deployment information, each workflow execution unit model including at least one workflow execution unit; According to the temporal dependency relationship between the at least one workflow execution unit model, the at least one workflow execution unit model is sent to the main control node in sequence, so that the main control node deploys the workflow execution unit in units of the workflow execution unit model.

3. The system according to claim 2, characterized in that The master control node is specifically used for: Receiving the at least one workflow execution unit model sent sequentially by the workflow management node; For each workflow execution unit model, determine whether the system identity identifiers used by the workflow execution units in the workflow execution unit model during operation all belong to the system identity identifiers that the target resource domain is authorized to use; if the judgment result is yes, deploy the workflow execution units in the workflow execution unit model to the working nodes in the target resource domain.

4. The system according to claim 3, characterized in that The workflow management node is also used for: Acquire the identifier of the target resource domain and the user identity credential for applying for workflow deployment from the workflow deployment information; send the identifier of the target resource domain and the user identity credential to the master control node; as well as When the master control node determines that the identifier of the target resource domain corresponds to the user identity credential, the at least one workflow execution unit model is sent to the master control node in sequence according to the temporal dependency relationship between the at least one workflow execution unit model.

5. The system according to claim 4, characterized in that The master control node is also used for: According to the pre-maintained correspondence between the identifier of the resource domain and the user identity credential, it is determined whether the identifier of the target resource domain corresponds to the user identity credential, and the determination result is returned to the workflow management node.

6. The system according to any one of claims 1 to 5, characterized in that: The master control node is also used for: Providing a resource domain security configuration interface to the operation and maintenance management personnel of the target tenant, so that the operation and maintenance management personnel can configure the security parameters of the target resource domain; the security parameters include the user identity credentials of the target resource domain, the identifier of the target resource domain, and the system identity identifier that the target resource domain is authorized to use; A correspondence is established between the user identity credentials of the target resource domain, the identifier of the target resource domain, and the scope of the running user identity identifier that the target resource domain is authorized to use; wherein the target tenant corresponds to the target resource domain.

7. The system according to any one of claims 1 to 5, characterized in that: The workflow management node is also used for: Providing a workflow deployment interface to a workflow deployment personnel in a target tenant, and obtaining workflow deployment information configured by the workflow deployment personnel on the workflow deployment interface; The workflow deployment information includes the identifier of the target resource domain where the workflow needs to be deployed, the user identity credentials for applying for workflow deployment, and the system identity identifier used by the workflow execution unit when running; the target tenant corresponds to the target resource domain.

8. The system according to any one of claims 1 to 5, characterized in that: The system identity used by the workflow execution unit during operation is the user identity Uid or the user group identity Gid.

9. A distributed computing system based on a container orchestration and scheduling system, characterized in that: include: The master node, workflow management node, and namespaces corresponding to different tenants; The workflow management node is used to obtain the system identity used when the container required by the workflow to be deployed is run according to the workflow deployment information in the target namespace; and transmit the system identity used when the container is run to the master control node; The master control node is used to deploy the container to a working node under the target namespace when the system identity used when the container is running belongs to the system identity that the target namespace is authorized to use; The container accesses the shared storage resources of the distributed computing system based on the memory access permission corresponding to the system identity used by the container during runtime.

10. The system according to claim 9, characterized in that The workflow management node is also used for: Generating at least one container group model identifiable by the master control node according to the workflow deployment information, each container group model including at least one container; According to the temporal dependency relationship between the at least one container group model, the at least one container group model is sent to the main control node in sequence, so that the main control node deploys the container in units of the container group model.

11. The system according to claim 10, characterized in that The master control node is specifically used for: receiving the at least one container group model sent sequentially by the workflow management node; For each container group model, determine whether the system identities used by the containers in the container group model when running are all system identities that the target namespace is authorized to use. If the judgment result is yes, deploy the containers in the container group model to the working nodes under the target namespace.

12. The system according to any one of claims 9 to 11, characterized in that: The workflow management node is also used for: Providing a workflow deployment interface to a workflow deployment personnel of a target tenant, and obtaining workflow deployment information configured by the workflow deployment personnel on the workflow deployment interface; The workflow deployment information includes an identifier of a target namespace, a user identity credential for applying for workflow deployment, and a system identity identifier used when a container required for the workflow to be deployed is run; wherein the target tenant corresponds to the target namespace.

13. A workflow deployment method, applicable to a workflow management node, characterized in that: The method comprises: According to the workflow deployment information in the target resource domain, obtain the system identity used by the workflow execution unit when it runs; The system identity used by the workflow execution unit when running is transmitted to the master control node in the distributed computing system to which the workflow management node belongs, so that the master control node can deploy the workflow execution unit to the working node in the target resource domain when the system identity used by the workflow execution unit when running is a system identity that the target resource domain is authorized to use; The workflow execution unit accesses the shared storage resources of the distributed computing system based on the memory access rights corresponding to the system identity used during its operation.

14. The method according to claim 13, characterized in that Also includes: Generating at least one workflow execution unit model identifiable by the master control node according to the workflow deployment information, each workflow execution unit model including at least one workflow execution unit; According to the temporal dependency relationship between the at least one workflow execution unit model, the at least one workflow execution unit model is sent to the main control node in sequence, so that the main control node deploys the workflow execution unit in units of the workflow execution unit model.

15. The method according to claim 14, characterized in that Before sending the at least one workflow execution unit model to the main control node in sequence, the method further includes: Acquire the identifier of the target resource domain and the user identity credential for applying for workflow deployment from the workflow deployment information; sending the identifier of the target resource domain and the user identity credential to the master control node, so that the master control node can determine whether the identifier of the target resource domain and the user identity credential correspond to each other; and Receive a determination result returned by the master control node as to whether the identifier of the target resource domain corresponds to the user identity credential.

16. The method according to any one of claims 13 to 15, characterized in that: Also includes: Providing a workflow deployment interface to a workflow deployment personnel of a target tenant, and obtaining workflow deployment information configured by the workflow deployment personnel on the workflow deployment interface; The workflow deployment information includes the identifier of the target resource domain where the workflow needs to be deployed, the user identity credentials for applying for workflow deployment, and the system identity identifier used by the workflow execution unit when running; the target tenant corresponds to the target resource domain.

17. A workflow deployment method, applicable to a master control node, characterized in that: The method comprises: Receiving a system identity identifier used by a workflow execution unit when running, which is sent by a workflow management node, wherein the workflow execution unit is an execution unit of a workflow that needs to be deployed in a target resource domain; When the system identity used by the workflow execution unit during operation belongs to the system identity that the target resource domain is authorized to use, deploying the workflow execution unit to a working node in the target resource domain; The workflow execution unit accesses the shared storage resources of the distributed computing system based on the memory access rights corresponding to the system identity used during its operation.

18. The method according to claim 17, characterized in that Deploying the workflow execution unit to a working node in the target resource domain includes: Receiving at least one workflow execution unit model sent sequentially by the workflow management node, each workflow execution unit model including at least one workflow execution unit; For each workflow execution unit model, determine whether the system identity identifiers used by the workflow execution units in the workflow execution unit model during operation all belong to the system identity identifiers that the target resource domain is authorized to use. If the judgment result is yes, deploy the workflow execution units in the workflow execution unit model to the working nodes in the target resource domain.

19. The method according to claim 18, characterized in that Before receiving at least one workflow execution unit model sequentially sent by the workflow management node, the method further includes: Receiving the identifier of the target resource domain and the user identity credential for applying for workflow deployment sent by the workflow management node; According to the pre-maintained correspondence between the identifier of the resource domain and the user identity credential, it is determined whether the identifier of the target resource domain corresponds to the user identity credential, and the determination result is returned to the workflow management node.

20. The method according to any one of claims 17 to 19, characterized in that: Also includes: Providing a resource domain security configuration interface to the operation and maintenance management personnel of the target tenant, so that the operation and maintenance management personnel can configure the security parameters of the target resource domain; The security parameters include the user identity credentials of the target resource domain, the identifier of the target resource domain, and the system identity identifier that the target resource domain is authorized to use; A correspondence is established between the user identity credentials of the target resource domain, the identifier of the target resource domain, and the scope of the running user identity identifier that the target resource domain is authorized to use; wherein the target tenant corresponds to the target resource domain.

21. A node device, characterized in that: include: A memory and a processor; the memory is used to store a computer program; when the computer program is executed by the processor, the processor is caused to implement the steps in the method according to any one of claims 13 to 16.

22. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the processor is caused to execute the steps in the method according to any one of claims 13 to 16.

23. A node device, characterized in that: include: A memory and a processor; the memory stores a computer program, and when the computer program is executed by the processor, the processor implements the steps in the method according to any one of claims 17 to 20.

24. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the processor is caused to execute the steps in the method according to any one of claims 17 to 20.

Citation Information

Patent Citations

  • Big data resource management method, device and equipment and storage medium

    CN109656879A

  • Microservices based multi-tenant identity and data security management cloud service

    US20170331812A1