Cluster resource release control method and device, medium, equipment and program product

Abstract

A cluster resource release control method and apparatus, a medium, a device and a program product, the method comprising: in response to a trigger operation on a resource release page, displaying the resource release page, the resource release page being used for performing resource release on a cluster; in response to a resource publishing operation on the resource publishing page, at least two publishing granularities are determined, a state machine is allocated for each publishing granularity, and the at least two publishing granularities comprise a first publishing granularity for publishing according to resources and a second publishing granularity for publishing according to clusters; the state machine is used for representing the resource release state of the corresponding release granularity; and in response to state switching of the state machine, performing resource release according to the release granularity corresponding to the state machine. According to the method, multi-granularity resource release state control is realized through the state machines with different release granularities, so that the resource release state of mass clusters can be flexibly and accurately perceived and controlled, and the method can be suitable for complicated multi-resource and multi-cluster release scenes.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and in particular to a cluster resource release control method, device, medium, equipment and program product. Background Art

[0002] With the development of cluster technology, cluster technology has been widely used. In edge computing scenarios, publishing multiple resources to massive clusters in one release is a common publishing mode. Therefore, how to flexibly and accurately control the resource publishing status of massive clusters has become an urgent problem to be solved. Summary of the invention

[0003] This section is provided to introduce the concepts in a brief form, which will be described in detail in the detailed implementation section below. This section is not intended to identify the key features or essential features of the technical solution claimed for protection, nor is it intended to be used to limit the scope of the technical solution claimed for protection.

[0004] In a first aspect, the present disclosure provides a resource release control method for a cluster, the method comprising: In response to a trigger operation on a resource publishing page, displaying the resource publishing page, wherein the resource publishing page is used to publish resources to the cluster; In response to a resource publishing operation on the resource publishing page, at least two publishing granularities are determined, and a state machine is allocated for each of the publishing granularities, wherein the at least two publishing granularities include a first publishing granularity for publishing by resource and a second publishing granularity for publishing by cluster, and the state machine is used to characterize the resource publishing state of the corresponding publishing granularity; In response to the state switching of the state machine, resources are published according to the publishing granularity corresponding to the state machine.

[0005] In a second aspect, the present disclosure provides a resource release control device for a cluster, the device comprising: A display module, configured to display the resource publishing page in response to a trigger operation on the resource publishing page, wherein the resource publishing page is used to publish resources to the cluster; A determination module, configured to determine at least two publishing granularities in response to a resource publishing operation on the resource publishing page, and to allocate a state machine for each of the publishing granularities, wherein the at least two publishing granularities include a first publishing granularity for publishing by resource and a second publishing granularity for publishing by cluster, and the state machine is used to characterize the resource publishing state of the corresponding publishing granularity; The publishing module is used to respond to the state switching of the state machine and publish resources according to the publishing granularity corresponding to the state machine.

[0006] In a third aspect, the present disclosure provides a computer-readable medium having a computer program stored thereon, which implements the steps of the method described in the first aspect when the program is executed by a processing device.

[0007] In a fourth aspect, the present disclosure provides an electronic device, including: a storage device having a computer program stored thereon; A processing device is used to execute the computer program in the storage device to implement the steps of the method in the first aspect.

[0008] In a fifth aspect, the present disclosure provides a computer program product, comprising a computer program, which implements the steps of the method described in the first aspect when executed by a processor.

[0009] Through the above technical solution, in response to the resource publishing operation on the resource publishing page, at least two publishing granularities can be determined, and a state machine can be allocated for each publishing granularity, and then in response to the state switching of the state machine, resources are published according to the publishing granularity corresponding to the state machine, wherein the at least two publishing granularities include a first publishing granularity for publishing by resource and a second publishing granularity for publishing by cluster. By adopting this method, multi-granular resource publishing state control is realized through state machines for different publishing granularities, so that the resource publishing state of massive clusters can be flexibly and accurately sensed and controlled, which can be applicable to complex multi-resource and multi-cluster publishing scenarios.

[0010] Other features and advantages of the present disclosure will be described in detail in the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and the originals and elements are not necessarily drawn to scale. In the drawings: Figure 1 It is a flow chart of a method for controlling resource release of a cluster according to an exemplary embodiment of the present disclosure; Figure 2 is a schematic diagram showing a multi-granularity release according to an exemplary embodiment of the present disclosure; Figure 3 is a schematic diagram of a multi-level state machine according to an exemplary embodiment of the present disclosure; Figure 4 is a schematic diagram of a resource publishing page according to an exemplary embodiment of the present disclosure; Figure 5 is a state flow diagram of a resource state machine according to an exemplary embodiment of the present disclosure; Figure 6 is a state flow diagram of a cluster state machine according to an exemplary embodiment of the present disclosure; Figure 7 is a state flow diagram of a batch state machine according to an exemplary embodiment of the present disclosure; Figure 8 is a state flow diagram of a publishing state machine according to an exemplary embodiment of the present disclosure; Fig. 9 is a structural block diagram of a resource release control device of a cluster according to an exemplary embodiment of the present disclosure; Fig.10 It is a schematic structural diagram of an electronic device according to an exemplary embodiment of the present disclosure. DETAILED DESCRIPTION

[0012] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as being limited to the embodiments described herein, which are instead provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not intended to limit the scope of protection of the present disclosure.

[0013] It should be understood that the various steps described in the method embodiments of the present disclosure may be performed in different orders and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present disclosure is not limited in this respect.

[0014] The term "including" and its variations used herein are open inclusions, i.e., "including but not limited to". The term "based on" means "based at least in part on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". The relevant definitions of other terms will be given in the following description.

[0015] It should be noted that the concepts such as "first" and "second" mentioned in the present disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0016] It should be noted that the modifications of "one" and "plurality" mentioned in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, it should be understood as "one or more".

[0017] The names of the messages or information exchanged between multiple devices in the embodiments of the present disclosure are only used for illustrative purposes and are not used to limit the scope of these messages or information.

[0018] All actions of acquiring signals, information or data in the present disclosure are carried out in compliance with the relevant data protection laws and policies of the country where they are located, and with the authorization given by the owner of the corresponding device.

[0019] It is understandable that before using the technical solutions disclosed in the embodiments of the present disclosure, the types, scope of use, usage scenarios, etc. of the personal information involved in the present disclosure should be informed to the user and the user's authorization should be obtained in an appropriate manner in accordance with relevant laws and regulations.

[0020] For example, in response to receiving an active request from a user, a prompt message is sent to the user to clearly prompt the user that the operation requested to be performed will require obtaining and using the user's personal information. Thus, the user can autonomously choose whether to provide personal information to software or hardware such as an electronic device, application, server, or storage medium that performs the operation of the technical solution of the present disclosure according to the prompt message.

[0021] As an optional but non-limiting implementation, in response to receiving an active request from the user, the prompt information may be sent to the user in the form of a pop-up window, in which the prompt information may be presented in text form. In addition, the pop-up window may also carry a selection control for the user to choose "agree" or "disagree" to provide personal information to the electronic device.

[0022] It is understandable that the above notification and the process of obtaining user authorization are merely illustrative and do not constitute a limitation on the implementation of the present disclosure. Other methods that meet the relevant laws and regulations may also be applied to the implementation of the present disclosure.

[0023] At the same time, it is understandable that the data involved in this technical solution (including but not limited to the data itself, the acquisition or use of the data) shall comply with the requirements of relevant laws, regulations and relevant provisions.

[0024] Taking the K8s cluster (Kubernetes, a distributed cluster based on container technology) in the edge scenario as an example, there are several K8s clusters running in a data center. Each K8s cluster is composed of several nodes. The nodes can be physical machines or virtual machines. Several virtual machines can be deployed on a physical machine.

[0025] Publishing multiple K8s resources to massive clusters in one release is a common release mode in edge computing scenarios. In addition to the large number of resources and clusters, the release process also involves various operations, such as retrying resource failures and rolling back cluster failures. Therefore, how to flexibly and accurately control the resource release status of massive clusters has become an urgent problem to be solved.

[0026] In view of this, the present disclosure provides a method, device, medium, equipment and program product for controlling resource release of a cluster to solve the above technical problems. Among them, the cluster in the embodiment of the present disclosure can be a K8s cluster or other clusters, and the present disclosure does not limit this.

[0027] The embodiments of the present disclosure are further explained below with reference to the accompanying drawings.

[0028] Figure 1 is a flowchart of a cluster resource release control method according to an exemplary embodiment of the present disclosure, referring to Figure 1 , the method may include the following steps: S101: In response to a triggering operation on a resource publishing page, displaying the resource publishing page.

[0029] The resource publishing page is used to publish resources to the cluster.

[0030] For example, on the resource publishing page, you can select the resources to be published and the cluster to publish the resources.

[0031] S102: In response to a resource publishing operation on a resource publishing page, determine at least two publishing granularities, and allocate a state machine for each publishing granularity, wherein the at least two publishing granularities include a first publishing granularity for publishing by resource and a second publishing granularity for publishing by cluster, and the state machine is used to characterize the resource publishing status of the corresponding publishing granularity.

[0032] S103: In response to the state switching of the state machine, resources are published according to the publishing granularity corresponding to the state machine.

[0033] By adopting the above method, multi-granularity resource release status control is realized through state machines for different release granularities, so that the resource release status of massive clusters can be flexibly and accurately sensed and controlled, which can be applicable to complex multi-resource and multi-cluster release scenarios.

[0034] Take the resource release of edge computing scenario as an example. Figure 2As shown, a release can include multiple batches, a batch can include multiple clusters, and multiple resources can be released in a cluster, which is determined according to the specific needs, and the present disclosure does not limit this. Then, according to the above-mentioned different release granularities, corresponding state machines are respectively allocated, namely, the resource state machine corresponding to the resource, the cluster state machine corresponding to the cluster, the batch state machine corresponding to the batch, and the release state machine corresponding to the release round. One release corresponds to a release state machine, a release state machine can include one to more batch state machines, a batch state machine can include one to more cluster state machines, and a cluster state machine can include one to more resource state machines.

[0035] In a possible manner, in response to a resource publishing operation on a resource publishing page, at least two publishing granularities are determined, and for each publishing granularity, a state machine is allocated, including: in response to a resource publishing operation on a resource publishing page, a first publishing granularity and a second publishing granularity are determined, and at least one resource corresponding to the first publishing granularity and at least one cluster corresponding to the second publishing granularity are determined, each cluster including at least one resource; a cluster state machine is allocated to each cluster, and for each cluster, a resource state machine is allocated to each resource in the cluster, wherein the cluster state machine is used to characterize the resource publishing state of the corresponding cluster, and the resource state machine is used to characterize the resource publishing state of the corresponding resource.

[0036] For example, Figure 3 As shown in the figure, assuming that n resources to be released and y clusters for resource release are determined on the resource release page, a cluster state machine can be allocated to each of the y clusters, and then a resource state machine can be allocated to each of the n resources to be released in each cluster, where y and n are positive integers. In this way, resource release at the resource granularity and cluster granularity can be achieved, and the resource release status of each cluster and the resource release status of each resource in each cluster can be accurately sensed and controlled.

[0037] In a possible manner, in response to a resource publishing operation on a resource publishing page, at least two publishing granularities are determined, and a state machine is allocated for each publishing granularity, and further includes: in response to the resource publishing operation on the resource publishing page, a third publishing granularity for publishing in batches is determined, and at least one batch corresponding to the third publishing granularity is determined, and each batch includes at least one cluster; a batch state machine is allocated to each batch, and the batch state machine is used to characterize the resource publishing state of the corresponding batch. A cluster state machine is allocated to each cluster, including: for each batch, a cluster state machine is allocated to each cluster in the batch.

[0038] For example, continue to refer to Figure 3, assuming that in the resource publishing page, n resources to be published and y clusters for resource publishing are determined, the y clusters can be divided into x batches for publishing, for example, the first batch includes m clusters, where m and x are positive integers, and m is less than or equal to y. The batches can be divided manually or automatically according to a preset batch division strategy, which is not limited in the present disclosure.

[0039] For example, a batch state machine can be assigned to each of the x batches, and then a state machine can be assigned to each cluster in each batch state machine, and a resource state machine can be assigned to each of the n resources to be released in each cluster. In this way, resource release at the resource granularity, cluster granularity, and batch granularity can be achieved, and the resource release status of each batch, the resource release status of each cluster in each batch, and the resource release status of each resource in each cluster can be accurately sensed and controlled.

[0040] In a possible manner, in response to a resource publishing operation on a resource publishing page, at least two publishing granularities are determined, and a state machine is allocated for each publishing granularity, and further includes: in response to the resource publishing operation on the resource publishing page, a fourth publishing granularity for publishing according to a publishing round composed of all batches is determined, and a publishing round corresponding to the fourth publishing granularity is determined; a publishing state machine is allocated to the publishing round, and the publishing state machine is used to characterize the resource publishing state of the publishing round. Allocating a batch state machine to each batch includes: allocating a batch state machine to each batch in the publishing round.

[0041] For example, continue to refer to Figure 3 , assuming that in the resource release page, n resources to be released and y clusters for resource release are determined in this release round, and the y clusters can be divided into x batches for release. Then a release state machine can be allocated for this release round, and then a batch state machine can be allocated for each of the x batches in this release round, and then a state machine can be allocated for each cluster in each batch state machine, and a resource state machine can be allocated for each of the n resources to be released in each cluster.

[0042] This makes it possible to achieve resource release at resource granularity, cluster granularity, batch granularity, and the release granularity corresponding to a single release, and to accurately perceive and control the resource release status of each release, the resource release status of each batch in each round of release, the resource release status of each cluster in each batch, and the resource release status of each resource in each cluster.

[0043] It is worth noting that, in practical applications, the above-mentioned publishing granularity can be adjusted according to needs, such as performing finer-grained division, etc., and the present disclosure does not impose any restrictions on this.

[0044] In a possible manner, the method also includes: synchronously displaying the resource publishing status corresponding to the publishing round on the resource publishing page according to the current status of the publishing state machine; in response to a batch expansion operation on the publishing round on the resource publishing page, displaying the batch information corresponding to each batch included in the publishing round, and synchronously displaying the resource publishing status corresponding to each batch on the resource publishing page according to the current status of the batch state machine corresponding to each batch; in response to a cluster expansion operation on the selected batch on the resource publishing page, displaying the cluster information corresponding to each cluster included in the selected batch, and synchronously displaying the resource publishing status corresponding to each cluster on the resource publishing page according to the current status of the cluster state machine corresponding to each cluster; in response to a cluster expansion operation on the selected cluster on the resource publishing page, displaying the resource information corresponding to each resource in the selected cluster, and synchronously displaying the resource publishing status corresponding to each resource on the resource publishing page according to the current status of the resource state machine corresponding to each resource.

[0045] For example, resource publishing status of different granularities can be displayed on different pages, such as Figure 4 As shown, the resource publishing status can also be displayed on the same page by granularity and level. The specific settings can be made according to the needs, and the present disclosure does not limit this.

[0046] For example, the granularity information of the corresponding release granularity can be displayed on the page, such as round name, batch name, cluster name, resource name, etc., and the present disclosure does not limit this. And according to the state machine corresponding to the different release granularities, the resource release status of the corresponding release granularity is synchronously displayed, such as unreleased status, release status, release failure status, release completion status, release skip status, release rollback status, release pause status, etc. It is also possible to operate the resource release of different release granularities, such as starting or pausing the resource release of this release round, pausing, continuing or skipping the resource release of a batch, pausing, continuing, rolling back or skipping the resource release of a cluster, and retrying or skipping the resource release of a resource. The release status and release operation can be determined according to the actual business scenario, and the present disclosure does not limit this.

[0047] It should be understood that the related technologies only support simple status transitions such as publishing in progress, publishing failure, and publishing completion, which cannot meet the complex application scenarios of multiple resources and multiple clusters. The present disclosure supports the display and control of multi-granularity and multi-type resource publishing status, so that the resource publishing status of each publishing granularity and the resource publishing operations that can be performed can be clearly understood, so as to flexibly and accurately perceive and control the resource publishing status of massive clusters, which can be applicable to complex multi-resource and multi-cluster publishing scenarios.

[0048] In a possible manner, in response to a state switch of a state machine, resources are published according to a publishing granularity corresponding to the state machine, including: in response to a target resource state machine corresponding to the target resource switching from an unpublished state to a publishing state, the publication of the target resource is started; or, in the case of a target resource publication failure, in response to a republishing operation on the target resource in a resource publication page, the target resource state machine is switched from a publishing failure state to a publishing state, and the target resource is republished; or, in the case of a target resource publication failure, in response to a skip publication operation on the target resource in the resource publication page, the target resource state machine is switched from a publishing failure state to a skip state, and the publication of the target resource is skipped.

[0049] For example, the resource state machine is the smallest granularity state machine that can control the state flow of a resource published to a cluster. Figure 5 As shown, the resource state machine is in the unpublished state, indicating that the resource has not yet started to be published. When a resource state machine in the unstarted state switches to the publishing state, it means that the corresponding resource is being published to the cluster. If the publishing fails, it will turn to the failed state, indicating that the corresponding resource has failed to be published. If the publishing is successful, it will turn to the completed state, indicating that the corresponding resource has been published. Figure 5 Italic text indicates automatic triggering, and underlined text indicates manual operation.

[0050] For example, when the resource state machine is in a failed state, you can manually retry the publishing operation, for example, by clicking Figure 4 , the resource status will switch to the publishing status and the resource will be published again. You can also manually skip publishing the resource, for example, click Figure 4 If the "Skip" control corresponding to the resource shown is clicked, the resource state machine will switch to the skip state, indicating that the corresponding resource has been skipped and will not be published. This enables the transfer and control of resource publishing status at the resource granularity.

[0051] Of course, the publishing operation can also be automatically retried after failure, and the publishing operation can be skipped after the number of retries reaches a preset number. The specific settings can be made according to needs, and the present disclosure does not impose any restrictions on this.

[0052] In a possible manner, in response to the state switching of the state machine, resources are released according to the release granularity corresponding to the state machine, including: in response to the target cluster state machine corresponding to the target cluster switching from the unreleased state to the releasing state, starting the resource release of the target cluster; or, in response to the pausing release operation on the target cluster in the resource release page, switching the target cluster state machine from the releasing state to the paused state, and stopping the release of unreleased resources in the target cluster; or, in response to the continuing release operation on the target cluster in the paused state in the resource release page, switching the target cluster state machine from the paused state to the releasing state, and continuing the resource release of the target cluster; or, in the case that the target cluster state machine includes at least one resource state machine in a failed release state, switching the target cluster state machine from the releasing state to the failed release state, in response to the skip release operation on the target cluster in the resource release page, switching the target cluster state machine from the failed release state to the skipped state, and skipping the resource release of the target cluster.

[0053] For example, a cluster state machine controls the state flow of multiple resources published to a cluster as a whole. Therefore, there are several resources that need to be published, and several resource state machines are nested in the cluster state machine. Figure 6 As shown in the figure, the cluster state machine is in the unpublished state, indicating that the cluster has not started to publish resources. When a cluster state machine in the unstarted state switches to the publishing state, it means that the corresponding cluster is currently publishing resources. At this time, you can pause the operation, such as triggering Figure 4 Click the "Pause" control corresponding to the cluster in the cluster state machine, and the cluster state machine will switch to the paused state. In the paused state, the publishing system will not start the resource state machine in the cluster state machine that is in the publishing state, that is, it will not publish unpublished resources. Figure 6 The italic text indicates automatic triggering, the underlined text indicates manual operation, and the bracketed text indicates resource state machine state triggering.

[0054] For example, you can continue publishing operations on the paused cluster state machine, such as triggering Figure 4 If you click the "Continue" control corresponding to the cluster in the cluster, the cluster state machine switches to the publishing state. When the cluster state machine is in the failed state, it means that there is a failed resource state machine in the corresponding cluster state machine. You can manually skip the publishing operation for the cluster. For example, click Figure 4 If the "Skip" control corresponding to the cluster shown is clicked, the cluster state machine will switch to the skip state, indicating that the corresponding cluster has been skipped and no resources will be released. This enables the transfer and control of resource release status at the cluster granularity.

[0055] In a possible manner, the method also includes: in a case where the target cluster state machine includes at least one resource state machine in a publishing failure state, switching the target cluster state machine from a publishing state to a publishing failure state, and in response to a rollback publishing operation on the target cluster in a resource publishing page, rolling back the resources of the target cluster to the last published resources in the target cluster, and switching the target cluster state machine from the publishing failure state to the rollback state.

[0056] For example, continue to refer to Figure 6 When the cluster state machine is in a failed state, you can manually roll back the cluster. For example, click Figure 4 The "Rollback" control corresponding to the cluster shown will roll back the resources in the corresponding cluster to the last released resources, and after the rollback is completed, the cluster state machine will switch to the rollback state.

[0057] Of course, the publishing operation may be automatically rolled back or skipped after a failure. This may be specifically set according to the requirements, and the present disclosure does not impose any restrictions on this.

[0058] In a possible manner, in response to the state switching of the state machine, resources are released according to the release granularity corresponding to the state machine, including: in response to the target batch state machine corresponding to the target batch switching from the unreleased state to the releasing state, starting the resource release of the target batch; or, in response to the pausing release operation on the target batch in the resource release page, switching the target batch state machine from the releasing state to the paused state, and suspending the release of the unreleased clusters and the releasing clusters in the target batch; or, in response to the continuing release operation on the target batch in the resource release page, switching the target batch state machine from the paused state to the releasing state, and continuing the resource release of the target batch; or, in the case that the target batch state machine includes at least one cluster state machine in the failed release state, switching the target batch state machine from the releasing state to the failed release state, in response to the skip release operation on the target batch in the resource release page, switching the target batch state machine from the failed release state to the skipped state, and skipping the resource release of the target batch.

[0059] For example, a batch state machine controls the overall state flow of all clusters in a batch. Therefore, if there are several clusters in a batch, there are several cluster state machines nested in the batch state machine. Figure 7 As shown, the batch state machine is in the unpublished state, indicating that the batch has not started to publish resources. When a batch state machine in the unstarted state switches to the publishing state, it means that the corresponding batch is in the process of publishing resources. At this time, you can pause the operation, such as triggering Figure 4The batch state machine will switch to the paused state by clicking the "Pause" control corresponding to the batch in the batch state machine. In the paused state, the publishing system will not start the cluster state machine in the batch state machine that is in the publishing state, that is, it will not publish the unpublished clusters, and will pause the cluster state machine in the publishing state, that is, pause the cluster in the publishing state. Figure 7 The italic text indicates automatic triggering, the underlined text indicates manual operation, and the bracketed text indicates cluster state machine state triggering.

[0060] For example, the batch state machine in the paused state can be continued to publish, such as triggering Figure 4 If you click the "Continue" control corresponding to the batch in the batch, the batch state machine switches to the publishing state. When the batch state machine is in the failed state, it means that there is a cluster state machine in the failed state in the corresponding batch state machine. You can manually skip the publishing operation for the batch, for example, click Figure 4 If the "Skip" control corresponding to the batch shown is clicked, the batch state will switch to the skip state, indicating that the corresponding batch has been skipped and no resources will be released. This enables the transfer and control of resource release status at the batch granularity.

[0061] Of course, the publishing operation may also be automatically skipped after a failure, which may be specifically set according to needs, and the present disclosure does not impose any limitation on this.

[0062] In a possible manner, in response to the state switching of the state machine, resources are released according to the release granularity corresponding to the state machine, including: in response to a confirm release operation on a release round, switching the release state machine from an unreleased state to a releasing state, and starting the release of resources for the release round; or, in response to a pause release operation on a release round in a resource release page, switching the release state machine from a releasing state to a paused state, and suspending the release of unreleased batches and releasing batches in the release round; or, in response to a continue release operation on a release round in a paused state in a resource release page, switching the release state machine from a paused state to a releasing state, and continuing the release of resources for the release round; or, in a case where the release state machine includes at least one batch state machine in a release failure state, switching the release state machine from a releasing state to a release failure state, in response to a skip release operation on a release round in a resource release page, switching the release state machine from a release failure state to a skipped state, and skipping the release of resources for the release round.

[0063] For example, a release state machine controls the overall state flow of all batches in a release. Therefore, a release corresponds to a release state machine, and if there are several batches in a release, there are several batch state machines nested in the release state machine. Figure 8As shown, the publishing state machine is in the unpublished state, indicating that the resource publishing has not yet started. In response to the user's publishing confirmation operation, the publishing state machine in the unstarted state can be switched to the publishing state, indicating that the resource publishing operation is in progress in the corresponding publishing round. Of course, you can also set a scheduled release. When the time condition of the scheduled release is met, the resource publishing operation of the publishing round is automatically performed. The specific setting can be based on demand, and this disclosure does not limit this. Among them, Figure 8 The underlined text indicates manual operation, and the bracketed text indicates the batch state machine state trigger.

[0064] For example, when the current release round is releasing resources, you can pause the operation, such as triggering Figure 4 The "Pause" control corresponding to the release round in the release state machine will switch to the paused state. In the paused state, the release system will not start the batch state machine in the release state in the release state machine, that is, it will not release the unreleased batches, and will pause the batch state machine in the release state, that is, pause the batch being released.

[0065] For example, the publishing state machine in the paused state can be continued to publish, such as triggering Figure 4 , the publishing state machine switches to the publishing state. When the publishing state machine is in the failed state, it means that there is a batch state machine in the corresponding publishing state machine that is in the failed state. You can manually skip the publishing operation for this publishing round, and the publishing state machine switches to the skipped state, indicating that the corresponding publishing round has been skipped and no resources will be published. This enables the transfer and control of the resource publishing state corresponding to the publishing granularity of one release.

[0066] In a possible manner, initiating the release of resources in a release round includes: when the number of batch state machines in a batch intermediate state in the release state machine is not greater than the preset batch concurrent number, switching the batch state machine corresponding to the unreleased batch in the release state machine from an unreleased state to a releasing state, wherein the batch intermediate state includes at least one of a releasing state, a failed release state, and a paused state; when the number of cluster state machines in a cluster intermediate state in the batch state machine corresponding to the unreleased batch is not greater than the preset cluster concurrent number, switching the cluster state machine corresponding to the unreleased cluster in the batch state machine corresponding to the unreleased batch from an unreleased state to a releasing state, wherein the cluster intermediate state includes at least one of a releasing state, a failed release state, and a paused state; when the number of resource state machines in a resource intermediate state in the cluster state machine corresponding to the unreleased cluster is not greater than the preset resource concurrent number, switching the resource state machine corresponding to the unreleased resource in the cluster state machine corresponding to the unreleased cluster from an unreleased state to a releasing state, and initiating the release of the unreleased resources, wherein the resource intermediate state includes a releasing state and / or a failed release state.

[0067] For example, in response to a confirmed release operation for a release round, the release state machine is switched from an unreleased state to a releasing state, and the release of resources for the release round is started. When the release system detects that the number of batches in the batch intermediate state in the release state machine does not reach the batch concurrent number, a batch state machine will be scheduled for the release state machine, and the batch state machine in the unstarted state will be switched to the releasing state. It should be noted that when the release state machine is in a paused state, the release system will not schedule a new batch state machine for this release state machine, even if the number of batch state machines in the batch intermediate state in the release state machine does not reach the batch concurrent number at this time.

[0068] For example, when the publishing system detects that the number of clusters in the cluster intermediate state in the current batch does not reach the number of cluster concurrency, it will schedule a cluster state machine for this batch state machine and switch a cluster state machine in the unstarted state to the publishing state. It should be noted that when the batch is in the paused state, the publishing system will not schedule a new cluster state machine for this batch, even if the number of cluster state machines in the cluster intermediate state of the batch state machine does not reach the number of cluster concurrency.

[0069] For example, when the publishing system detects that the number of resources in the current cluster in the intermediate state does not reach the number of concurrent resources, it will schedule a resource state machine for this cluster state machine and convert a resource state machine in the unstarted state to the publishing state. It should be noted that when the cluster is in the paused state, the publishing system will not schedule a new resource state machine for this cluster, even if the number of resource state machines in the current cluster state machine in the intermediate state does not reach the number of concurrent resources.

[0070] It is worth noting that in one release, multiple batches, multiple clusters, and multiple resources all support parallel release operations, and the specific number of concurrent operations can be set according to demand, and this disclosure does not limit this, thereby achieving multi-granular resource release status control.

[0071] In a possible manner, the method also includes: for each cluster state machine, in response to each resource state machine in the cluster state machine being in a resource termination state, switching the cluster state machine to a completion state, wherein the resource termination state includes a completion state and / or a skip state; for each batch state machine, in response to each cluster state machine in the batch state machine being in a cluster termination state, switching the batch state machine to a completion state, wherein the cluster termination state includes at least one of a completion state, a skip state, and a rollback state; in response to each batch state machine in the release state machine being in a batch termination state, switching the release state machine to a completion state, wherein the batch termination state includes a completion state and / or a skip state.

[0072] For example, Figure 6 As shown in FIG. 1 , when each resource state machine in a cluster state machine is in the resource termination state, the cluster state machine is switched to the completion state. Figure 7 As shown in , when each cluster state machine in a batch of state machines is in the cluster termination state, the batch state machine is switched to the completion state. Figure 8 As shown, when each batch state machine in the publishing state machine is in the batch termination state, the publishing state machine is switched to the completion state, thereby realizing multi-granularity resource publishing state control.

[0073] Based on the same concept, the embodiment of the present disclosure provides a resource release control device for a cluster, such as Fig. 9 As shown, the resource release control device 900 of the cluster includes: A display module 901 is used to display a resource publishing page in response to a trigger operation on the resource publishing page, where the resource publishing page is used to publish resources to the cluster; A determination module 902 is used to determine at least two publishing granularities in response to a resource publishing operation on a resource publishing page, and allocate a state machine for each publishing granularity, wherein the at least two publishing granularities include a first publishing granularity for publishing by resource and a second publishing granularity for publishing by cluster, and the state machine is used to characterize the resource publishing state of the corresponding publishing granularity; The publishing module 903 is used to respond to the state switching of the state machine and publish resources according to the publishing granularity corresponding to the state machine.

[0074] Optionally, the determining module 902 is used to: In response to a resource publishing operation on the resource publishing page, determining the first publishing granularity and the second publishing granularity, and determining at least one resource corresponding to the first publishing granularity and at least one cluster corresponding to the second publishing granularity, each of the clusters including at least one resource; A cluster state machine is allocated to each of the clusters, and a resource state machine is allocated to each of the resources in the cluster for each of the clusters, wherein the cluster state machine is used to represent the resource publishing state of the corresponding cluster, and the resource state machine is used to represent the resource publishing state of the corresponding resource.

[0075] Optionally, the determining module 902 is further configured to: In response to a resource publishing operation on the resource publishing page, determining a third publishing granularity for publishing in batches, and determining at least one batch corresponding to the third publishing granularity, each of the batches including at least one cluster; Allocating a batch state machine to each batch, the batch state machine being used to characterize the resource release status of the corresponding batch; The allocating a cluster state machine to each cluster comprises: For each of the batches, a cluster state machine is allocated to each cluster in the batch.

[0076] Optionally, the determining module 902 is further configured to: In response to a resource publishing operation on the resource publishing page, determining a fourth publishing granularity for publishing according to publishing rounds consisting of all batches, and determining a publishing round corresponding to the fourth publishing granularity; Allocating a publishing state machine to the publishing round, the publishing state machine being used to characterize the resource publishing state of the publishing round; The allocating a batch state machine to each batch includes: A batch state machine is allocated to each batch in the release round.

[0077] Optionally, the publishing module 903 is used to: In response to the target resource state machine corresponding to the target resource switching from an unpublished state to a published state, starting the publication of the target resource; or, In the case where the target resource fails to be published, in response to a re-publishing operation on the target resource in the resource publishing page, the target resource state machine is switched from a publishing failure state to a publishing state, and the target resource is re-published; or, In the case where the target resource fails to be published, in response to a skip publishing operation on the target resource in the resource publishing page, the target resource state machine is switched from a publishing failure state to a skip state, and publishing of the target resource is skipped.

[0078] Optionally, the publishing module 903 is used to: In response to a target cluster state machine corresponding to the target cluster switching from an unpublished state to a publishing state, starting resource publishing of the target cluster; or, In response to a pause publishing operation on the target cluster in the resource publishing page, switching the target cluster state machine from a publishing state to a paused state, and stopping publishing of unpublished resources in the target cluster; or, In response to a continue publishing operation on the target cluster in the paused state in the resource publishing page, switching the target cluster state machine from the paused state to the publishing state, and continuing the resource publishing of the target cluster; or, In a case where the target cluster state machine includes at least one resource state machine in a publishing failure state, the target cluster state machine is switched from a publishing state to a publishing failure state, and in response to a skip publishing operation on the target cluster in the resource publishing page, the target cluster state machine is switched from a publishing failure state to a skip state, and resource publishing of the target cluster is skipped.

[0079] Optionally, the resource release control device 900 of the cluster further includes a rollback module, and the rollback module is used to: In a case where the target cluster state machine includes at least one resource state machine in a publishing failure state, the target cluster state machine is switched from a publishing state to a publishing failure state, and in response to a rollback publishing operation on the target cluster in the resource publishing page, the resources of the target cluster are rolled back to the last published resources in the target cluster, and the target cluster state machine is switched from a publishing failure state to a rollback state.

[0080] Optionally, the publishing module 903 is used to: In response to the target batch state machine corresponding to the target batch switching from the unpublished state to the published state, starting the release of resources of the target batch; or, In response to a pause operation on the target batch in the resource publishing page, the target batch state machine is switched from a publishing state to a paused state, and the release of unpublished clusters and publishing clusters in the target batch is suspended; or, In response to a continue publishing operation on the target batch in the paused state in the resource publishing page, switching the target batch state machine from the paused state to the publishing state, and continuing the resource publishing of the target batch; or, In a case where the target batch state machine includes at least one cluster state machine in a publishing failure state, the target batch state machine is switched from a publishing state to a publishing failure state, and in response to a skip publishing operation for the target batch in the resource publishing page, the target batch state machine is switched from a publishing failure state to a skip state, and resource publishing of the target batch is skipped.

[0081] Optionally, the publishing module 903 is used to: In response to a confirmation publishing operation for the publishing round, switching the publishing state machine from an unpublished state to a publishing state, and starting resource publishing for the publishing round; or, In response to a pause operation on the release round in the resource release page, the release state machine is switched from a release state to a pause state, and the release of unreleased batches and release batches in the release round is suspended; or, In response to a continuing publishing operation on the publishing round in the paused state in the resource publishing page, switching the publishing state machine from the paused state to the publishing state, and continuing the resource publishing of the publishing round; or, In a case where the publishing state machine includes at least one batch state machine in a publishing failure state, the publishing state machine is switched from a publishing in progress state to a publishing failure state, and in response to a skip publishing operation for the publishing round in the resource publishing page, the publishing state machine is switched from the publishing failure state to the skip state, and the resource publishing of the publishing round is skipped.

[0082] Optionally, the publishing module 903 is used to: When the number of batch state machines in the batch intermediate state in the publishing state machine is not greater than the preset batch concurrent number, the batch state machines corresponding to the unpublished batches in the publishing state machine are switched from the unpublished state to the publishing state, wherein the batch intermediate state includes at least one of the publishing state, the publishing failure state and the paused state; When the number of cluster state machines in the cluster intermediate state in the batch state machine corresponding to the unpublished batch is not greater than the preset cluster concurrent number, the cluster state machine corresponding to the unpublished cluster in the batch state machine corresponding to the unpublished batch is switched from the unpublished state to the publishing state, wherein the cluster intermediate state includes at least one of the publishing state, the publishing failure state and the paused state; When the number of resource state machines in the resource intermediate state in the cluster state machine corresponding to the unpublished cluster is not greater than the preset resource concurrent number, the resource state machines corresponding to the unpublished resources in the cluster state machine corresponding to the unpublished cluster are switched from the unpublished state to the publishing state, and the publication of the unpublished resources is started, wherein the resource intermediate state includes the publishing state and / or the publishing failure state.

[0083] Optionally, the resource release control device 900 of the cluster further includes a completion module, and the completion module is used to: For each cluster state machine, in response to each resource state machine in the cluster state machine being in a resource termination state, switching the cluster state machine to a completion state, wherein the resource termination state includes a completion state and / or a skip state; For each batch state machine, in response to each cluster state machine in the batch state machine being in a cluster termination state, switching the batch state machine to a completion state, wherein the cluster termination state includes at least one of a completion state, a skip state, and a rollback state; In response to each batch state machine in the publishing state machine being in a batch termination state, the publishing state machine is switched to a completion state, where the batch termination state includes a completion state and / or a skip state.

[0084] Optionally, the cluster resource release control device 900 further includes an expansion module, and the expansion module is used to: According to the current state of the publishing state machine, synchronously displaying the resource publishing state corresponding to the publishing round on the resource publishing page; In response to an expansion operation on a batch of the release round on the resource release page, batch information corresponding to each batch included in the release round is displayed, and according to a current state of a batch state machine corresponding to each batch, a resource release state corresponding to each batch is synchronously displayed on the resource release page; In response to the cluster expansion operation on the selected batch in the resource publishing page, cluster information corresponding to each cluster included in the selected batch is displayed, and according to the current state of the cluster state machine corresponding to each cluster, the resource publishing state corresponding to each cluster is synchronously displayed on the resource publishing page; In response to a cluster expansion operation on a selected cluster in the resource publishing page, resource information corresponding to each resource in the selected cluster is displayed, and the resource publishing status corresponding to each resource is synchronously displayed on the resource publishing page according to the current status of the resource state machine corresponding to each resource.

[0085] Based on the same concept, an embodiment of the present disclosure further provides a computer-readable medium on which a computer program is stored. When the program is executed by a processing device, the steps of the resource release control method of the above cluster are implemented.

[0086] Based on the same concept, the present disclosure also provides an electronic device, which may include: a storage device having a computer program stored thereon; The processing device is used to execute the computer program in the storage device to implement the steps of the resource release control method of the cluster.

[0087] Based on the same concept, an embodiment of the present disclosure further provides a computer program product, including a computer program, which implements the steps of the above-mentioned cluster resource release control method when executed by a processor.

[0088] Reference below Fig.10 , which shows a schematic diagram of the structure of an electronic device 1000 suitable for implementing the embodiment of the present disclosure. The terminal device in the embodiment of the present disclosure may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), vehicle terminals (such as vehicle navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Fig.10 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0089] like Fig.10 As shown, the electronic device 1000 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 1001, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage device 1008 to a random access memory (RAM) 1003. In the RAM 1003, various programs and data required for the operation of the electronic device 1000 are also stored. The processing device 1001, the ROM 1002, and the RAM 1003 are connected to each other via a bus 1004. An input / output (I / O) interface 1005 is also connected to the bus 1004.

[0090] Typically, the following devices may be connected to the I / O interface 1005: an input device 1006 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 1007 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 1008 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 may allow the electronic device 1000 to communicate with other devices wirelessly or by wire to exchange data. Although Fig.10The electronic device 1000 is shown with various devices, but it should be understood that it is not required to implement or possess all the devices shown. More or fewer devices may be implemented or possessed instead.

[0091] In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a non-transitory computer-readable medium, and the computer program contains program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device 1009, or installed from a storage device 1008, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment of the present disclosure are executed.

[0092] It should be noted that the computer-readable medium mentioned above in the present disclosure may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present disclosure, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. Computer readable signal media may also be any computer readable medium other than computer readable storage media, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer readable medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

[0093] In some embodiments, any currently known or future developed network protocol such as HTTP (HyperText Transfer Protocol) can be used for communication, and can be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), an internet (e.g., the Internet), and a peer-to-peer network (e.g., an ad hoc peer-to-peer network), as well as any currently known or future developed network.

[0094] The computer-readable medium may be included in the electronic device, or may exist independently without being incorporated into the electronic device.

[0095] The computer-readable medium carries one or more programs. When the one or more programs are executed by the electronic device, the electronic device: displays a resource publishing page in response to a trigger operation on the resource publishing page, and the resource publishing page is used to publish resources to a cluster; determines at least two publishing granularities in response to a resource publishing operation on the resource publishing page, and allocates a state machine for each publishing granularity, wherein the at least two publishing granularities include a first publishing granularity for publishing by resource and a second publishing granularity for publishing by cluster, and the state machine is used to characterize the resource publishing state of the corresponding publishing granularity; and publishes resources according to the publishing granularity corresponding to the state machine in response to a state switch of the state machine.

[0096] Computer program code for performing the operations of the present disclosure may be written in one or more programming languages ​​or a combination thereof, including, but not limited to, object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., through the Internet using an Internet service provider).

[0097] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some implementations as replacements, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0098] The modules involved in the embodiments described in the present disclosure may be implemented by software or hardware, wherein the name of a module does not, in some cases, limit the module itself.

[0099] The functions described above herein may be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.

[0100] In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0101] The above description is only a preferred embodiment of the present disclosure and an explanation of the technical principles used. Those skilled in the art should understand that the scope of disclosure involved in the present disclosure is not limited to the technical solutions formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above disclosed concept. For example, the above features are replaced with the technical features with similar functions disclosed in the present disclosure (but not limited to) by each other to form a technical solution.

[0102] In addition, although each operation is described in a specific order, this should not be understood as requiring these operations to be performed in the specific order shown or in a sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Similarly, although some specific implementation details are included in the above discussion, these should not be interpreted as limiting the scope of the present disclosure. Some features described in the context of a separate embodiment can also be implemented in a single embodiment in combination. On the contrary, the various features described in the context of a single embodiment can also be implemented in multiple embodiments individually or in any suitable sub-combination mode.

[0103] Although the subject matter has been described in language specific to structural features and / or method logic actions, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. On the contrary, the specific features and actions described above are merely example forms of implementing the claims. Regarding the device in the above embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.

Claims

1. A cluster resource release control method, characterized in that: The method comprises: In response to a trigger operation on a resource publishing page, displaying the resource publishing page, wherein the resource publishing page is used to publish resources to the cluster; In response to a resource publishing operation on the resource publishing page, at least two publishing granularities are determined, and a state machine is allocated for each of the publishing granularities, wherein the at least two publishing granularities include a first publishing granularity for publishing by resource and a second publishing granularity for publishing by cluster, and the state machine is used to characterize the resource publishing state of the corresponding publishing granularity; In response to the state switching of the state machine, resources are published according to the publishing granularity corresponding to the state machine.

2. The cluster resource release control method according to claim 1, characterized in that: The step of determining at least two publishing granularities in response to the resource publishing operation on the resource publishing page, and allocating a state machine for each of the publishing granularities, includes: In response to a resource publishing operation on the resource publishing page, determining the first publishing granularity and the second publishing granularity, and determining at least one resource corresponding to the first publishing granularity and at least one cluster corresponding to the second publishing granularity, each of the clusters including at least one resource; A cluster state machine is allocated to each of the clusters, and a resource state machine is allocated to each of the resources in the cluster for each of the clusters, wherein the cluster state machine is used to represent the resource publishing state of the corresponding cluster, and the resource state machine is used to represent the resource publishing state of the corresponding resource.

3. The cluster resource release control method according to claim 2, characterized in that: In response to the resource publishing operation on the resource publishing page, determining at least two publishing granularities, and allocating a state machine for each of the publishing granularities, further includes: In response to a resource publishing operation on the resource publishing page, determining a third publishing granularity for publishing in batches, and determining at least one batch corresponding to the third publishing granularity, each of the batches including at least one cluster; Allocating a batch state machine to each batch, the batch state machine being used to characterize the resource release status of the corresponding batch; The allocating a cluster state machine to each cluster comprises: For each of the batches, a cluster state machine is allocated to each cluster in the batch.

4. The cluster resource release control method according to claim 3, characterized in that: In response to the resource publishing operation on the resource publishing page, determining at least two publishing granularities, and allocating a state machine for each of the publishing granularities, further includes: In response to a resource publishing operation on the resource publishing page, determining a fourth publishing granularity for publishing according to publishing rounds consisting of all batches, and determining a publishing round corresponding to the fourth publishing granularity; Allocating a publishing state machine to the publishing round, the publishing state machine being used to characterize the resource publishing state of the publishing round; The allocating a batch state machine to each batch includes: A batch state machine is allocated to each batch in the release round.

5. The cluster resource release control method according to any one of claims 2 to 4, characterized in that: The responding to the state switching of the state machine and publishing resources according to the publishing granularity corresponding to the state machine includes: In response to the target resource state machine corresponding to the target resource switching from an unpublished state to a published state, starting the publication of the target resource; or, In the case where the target resource fails to be published, in response to a republishing operation on the target resource in the resource publishing page, the target resource state machine is switched from a publishing failure state to a publishing state, and the target resource is republished; or, In the case where the target resource fails to be published, in response to a skip publishing operation on the target resource in the resource publishing page, the target resource state machine is switched from a publishing failure state to a skip state, and publishing of the target resource is skipped.

6. The cluster resource release control method according to any one of claims 2 to 4, characterized in that: The responding to the state switching of the state machine and publishing resources according to the publishing granularity corresponding to the state machine includes: In response to the target cluster state machine corresponding to the target cluster switching from the unpublished state to the published state, starting the resource publishing of the target cluster; or, In response to a pause publishing operation on the target cluster in the resource publishing page, switching the target cluster state machine from a publishing state to a paused state, and stopping publishing of unpublished resources in the target cluster; or, In response to a continue publishing operation on the target cluster in the paused state in the resource publishing page, switching the target cluster state machine from the paused state to the publishing state, and continuing the resource publishing of the target cluster; or, In a case where the target cluster state machine includes at least one resource state machine in a publishing failure state, the target cluster state machine is switched from a publishing state to a publishing failure state, and in response to a skip publishing operation on the target cluster in the resource publishing page, the target cluster state machine is switched from a publishing failure state to a skip state, and resource publishing of the target cluster is skipped.

7. The cluster resource release control method according to claim 6, characterized in that: The method further comprises: In a case where the target cluster state machine includes at least one resource state machine in a publishing failure state, the target cluster state machine is switched from a publishing state to a publishing failure state, and in response to a rollback publishing operation on the target cluster in the resource publishing page, the resources of the target cluster are rolled back to the last published resources in the target cluster, and the target cluster state machine is switched from a publishing failure state to a rollback state.

8. The cluster resource release control method according to claim 3 or 4, characterized in that: The responding to the state switching of the state machine and publishing resources according to the publishing granularity corresponding to the state machine includes: In response to the target batch state machine corresponding to the target batch switching from the unpublished state to the published state, starting the release of resources of the target batch; or, In response to a pause operation on the target batch in the resource publishing page, the target batch state machine is switched from a publishing state to a paused state, and the release of unpublished clusters and publishing clusters in the target batch is suspended; or, In response to a continue publishing operation on the target batch in the paused state in the resource publishing page, switching the target batch state machine from the paused state to the publishing state, and continuing the resource publishing of the target batch; or, In a case where the target batch state machine includes at least one cluster state machine in a publishing failure state, the target batch state machine is switched from a publishing state to a publishing failure state, and in response to a skip publishing operation for the target batch in the resource publishing page, the target batch state machine is switched from a publishing failure state to a skip state, and resource publishing of the target batch is skipped.

9. The cluster resource release control method according to claim 4, characterized in that: The responding to the state switching of the state machine and publishing resources according to the publishing granularity corresponding to the state machine includes: In response to a confirmation publishing operation for the publishing round, switching the publishing state machine from an unpublished state to a publishing state, and starting resource publishing for the publishing round; or, In response to a pause operation on the release round in the resource release page, the release state machine is switched from a release state to a pause state, and the release of unreleased batches and release batches in the release round is suspended; or, In response to a continuing publishing operation on the publishing round in the paused state in the resource publishing page, switching the publishing state machine from the paused state to the publishing state, and continuing the resource publishing of the publishing round; or, In a case where the publishing state machine includes at least one batch state machine in a publishing failure state, the publishing state machine is switched from a publishing in progress state to a publishing failure state, and in response to a skip publishing operation for the publishing round in the resource publishing page, the publishing state machine is switched from the publishing failure state to the skip state, and the resource publishing of the publishing round is skipped.

10. The cluster resource release control method according to claim 9, characterized in that: The initiating the resource release of the release round includes: When the number of batch state machines in the batch intermediate state in the publishing state machine is not greater than the preset batch concurrent number, the batch state machines corresponding to the unpublished batches in the publishing state machine are switched from the unpublished state to the publishing state, wherein the batch intermediate state includes at least one of the publishing state, the publishing failure state and the paused state; When the number of cluster state machines in the cluster intermediate state in the batch state machine corresponding to the unpublished batch is not greater than the preset cluster concurrent number, the cluster state machine corresponding to the unpublished cluster in the batch state machine corresponding to the unpublished batch is switched from the unpublished state to the publishing state, wherein the cluster intermediate state includes at least one of the publishing state, the publishing failure state and the paused state; When the number of resource state machines in the resource intermediate state in the cluster state machine corresponding to the unpublished cluster is not greater than the preset resource concurrent number, the resource state machines corresponding to the unpublished resources in the cluster state machine corresponding to the unpublished cluster are switched from the unpublished state to the publishing state, and the publication of the unpublished resources is started, wherein the resource intermediate state includes the publishing state and / or the publishing failure state.

11. The cluster resource release control method according to claim 4 or 9, characterized in that: The method further comprises: For each cluster state machine, in response to each resource state machine in the cluster state machine being in a resource termination state, switching the cluster state machine to a completion state, wherein the resource termination state includes a completion state and / or a skip state; For each batch state machine, in response to each cluster state machine in the batch state machine being in a cluster termination state, switching the batch state machine to a completion state, wherein the cluster termination state includes at least one of a completion state, a skip state, and a rollback state; In response to each batch state machine in the publishing state machine being in a batch termination state, the publishing state machine is switched to a completion state, where the batch termination state includes a completion state and / or a skip state.

12. The cluster resource release control method according to claim 4 or 9, characterized in that: The method further comprises: According to the current state of the publishing state machine, synchronously displaying the resource publishing state corresponding to the publishing round on the resource publishing page; In response to an expansion operation on a batch of the release round on the resource release page, batch information corresponding to each batch included in the release round is displayed, and according to a current state of a batch state machine corresponding to each batch, a resource release state corresponding to each batch is synchronously displayed on the resource release page; In response to the cluster expansion operation on the selected batch in the resource publishing page, cluster information corresponding to each cluster included in the selected batch is displayed, and according to the current state of the cluster state machine corresponding to each cluster, the resource publishing state corresponding to each cluster is synchronously displayed on the resource publishing page; In response to a cluster expansion operation on a selected cluster in the resource publishing page, resource information corresponding to each resource in the selected cluster is displayed, and the resource publishing status corresponding to each resource is synchronously displayed on the resource publishing page according to the current status of the resource state machine corresponding to each resource.

13. A resource release control device for a cluster, characterized in that: The device comprises: A display module, configured to display the resource publishing page in response to a trigger operation on the resource publishing page, wherein the resource publishing page is used to publish resources to the cluster; A determination module, configured to determine at least two publishing granularities in response to a resource publishing operation on the resource publishing page, and to allocate a state machine for each of the publishing granularities, wherein the at least two publishing granularities include a first publishing granularity for publishing by resource and a second publishing granularity for publishing by cluster, and the state machine is used to characterize the resource publishing state of the corresponding publishing granularity; The publishing module is used to respond to the state switching of the state machine and publish resources according to the publishing granularity corresponding to the state machine.

14. A computer readable medium having a computer program stored thereon, characterized in that: When the program is executed by a processing device, the steps of the method described in any one of claims 1 to 12 are implemented.

15. An electronic device, characterized in that: include: a storage device having at least one computer program stored thereon; At least one processing device, configured to execute the at least one computer program in the storage device to implement the steps of the method according to any one of claims 1 to 12.

16. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 12 are implemented.

Images