CN116775076A - Upgrading method and device for applications in cluster, storage medium and electronic equipment - Google Patents

Abstract

The application discloses an upgrading method and device for applications in a cluster, a storage medium and electronic equipment. To the field of financial technology or other fields, wherein the method comprises: receiving a target upgrading request, wherein the target upgrading request is used for requesting upgrading of target applications deployed in a cluster; responding to the target upgrading request, and detecting a target operation type of target upgrading operation corresponding to the target application; acquiring a second cluster resource amount according to a target operation type, wherein the second cluster resource amount is used for indicating the minimum cluster resource amount required by the upgrading process of the target application; allocating standby cluster resources for the target application according to the first cluster resource amount and the second cluster resource amount currently occupied by the target application; and executing the target upgrading operation on the target application by using the standby cluster resource and the current cluster resource corresponding to the first cluster resource quantity. The application solves the technical problem of lower robustness of upgrading application in the cluster in the related technology.

Description

Upgrading method and device for applications in cluster, storage medium and electronic equipment

Technical Field

The present application relates to the field of financial science and technology or other fields, and in particular, to a method and apparatus for upgrading an application in a cluster, a storage medium, and an electronic device.

Background

In a multi-cluster scene, the application in the upgrading cluster can improve the efficiency of cluster processing tasks, so that the data computing capacity of the cluster is improved. Currently, upgrading of applications in a cluster depends on whether resources of the cluster are sufficient, and in the case of insufficient resources, pod (the smallest resource management component in a container, k8s, pod is also the resource object of the smallest running containerized application) in the cluster is always in the condition of insufficient resources, and one Pod represents one process running in the cluster, at this time, pod is caused to be in a state of waiting for resources, and start and subsequent other created Pod are in a competing state, so that application upgrading fails. The resource use condition in the cluster cannot be known in the application upgrading process, and whether the cluster resource is sufficient or not influences whether the application can normally complete the upgrading, so that the stability of successful application upgrading is influenced, and the robustness of the application upgrading is low.

In view of the above problems, no effective solution has been proposed at present.

Disclosure of Invention

The embodiment of the application provides a method and a device for upgrading applications in a cluster, a storage medium and electronic equipment, and aims to at least solve the technical problem of low robustness of upgrading applications in the cluster in the related technology.

According to an aspect of an embodiment of the present application, there is provided an upgrade method for an application in a cluster, the method including: receiving a target upgrading request, wherein the target upgrading request is used for requesting upgrading of target applications deployed in a cluster; responding to the target upgrading request, and detecting a target operation type of target upgrading operation corresponding to the target application; acquiring a second cluster resource amount according to the target operation type, wherein the second cluster resource amount is used for indicating the minimum cluster resource amount required by the upgrading process of the target application; allocating standby cluster resources for the target application according to the first cluster resource amount and the second cluster resource amount currently occupied by the target application; and executing the target upgrading operation on the target application by using the standby cluster resource and the current cluster resource corresponding to the first cluster resource quantity.

Further, obtaining a second cluster resource amount according to the target operation type includes: acquiring a target update parameter type corresponding to the target operation type from the operation type and the update parameter type which have the corresponding relation; reading target update parameters belonging to the target update parameter type from controller information of a target container controller corresponding to the target application; and inputting the target updating parameters into a target operation function corresponding to the target operation type to obtain the second cluster resource quantity.

Further, obtaining a target update parameter type corresponding to the target operation type from the operation type and the update parameter type with the corresponding relation comprises the following steps: in the case that the target operation type is a creation type, determining the target update parameter type includes: a container number type and a hard and soft limit type, wherein the container number type is used for indicating the number of containers included in the target application after upgrading; in the case that the target operation type is a scroll type, determining the target update parameter type includes: the system comprises a container number type, a container parameter type and a soft and hard limit type, wherein the container number type is used for indicating the number of containers included in the target application after upgrading, and the container parameter type is used for indicating that the target application is allowed to exceed the maximum number of containers required after upgrading in the upgrading process.

Further, inputting the target update parameter to a target operation function corresponding to the target operation type to obtain the second cluster resource amount, including: in the case that the target operation type is a creation type, calculating the second cluster resource amount by the following target operation function: replica is a soft and hard limit value, wherein Replica is a target update parameter belonging to the container quantity type, and the soft and hard limit value is a target update parameter belonging to the soft and hard limit type; and under the condition that the target operation type is a rolling type, calculating the second cluster resource amount through the following target operation function: ceil (Replica) is a soft and hard limit value, wherein Replica is a target update parameter belonging to the container number type, the soft and hard limit value is a target update parameter belonging to the soft and hard limit type, maxsurg is a target update parameter belonging to the container parameter type, and ceil is an upward rounding.

Further, allocating standby cluster resources for the target application according to the first cluster resource amount and the second cluster resource amount currently occupied by the target application, including: calculating a difference between the second cluster resource amount and the first cluster resource amount to obtain a standby cluster resource amount under the condition that the first cluster resource amount is smaller than the second cluster resource amount; and allocating the standby cluster resources which are larger than or equal to the standby cluster resources for the target application.

Further, the detecting the target operation type of the target upgrade operation corresponding to the target application includes: the target container controller corresponding to the target application is obtained, and the target upgrading operation is sent out in response to the target upgrading request, wherein the target container controller is used for managing a target container of the target application, and the target upgrading operation is used for realizing the upgrading of the target application by updating the target container; detecting the target operation type of the target upgrading operation, wherein the operation type of the upgrading operation of the application comprises: scroll type, and, create type.

Further, after executing the target upgrade operation on the target application using the standby cluster resource and the current cluster resource corresponding to the first cluster resource amount, the method further includes: detecting whether the target application is upgraded or not under the condition that the target operation type is a rolling type; and under the condition that the target application is detected to finish upgrading, releasing unused cluster resources of the target application after upgrading.

According to another aspect of the embodiment of the present application, there is also provided an upgrade apparatus applied in a cluster, the apparatus including: the system comprises a receiving module, a target upgrading module and a processing module, wherein the receiving module is used for receiving a target upgrading request, and the target upgrading request is used for requesting upgrading of target applications deployed in a cluster; the detection module is used for responding to the target upgrading request and detecting a target operation type of target upgrading operation corresponding to the target application; the acquisition module is used for acquiring a second cluster resource amount according to the target operation type, wherein the second cluster resource amount is used for indicating the minimum cluster resource amount required by the upgrading process of the target application; the allocation module is used for allocating standby cluster resources for the target application according to the first cluster resource amount and the second cluster resource amount currently occupied by the target application; and the upgrading module is used for executing the target upgrading operation on the target application by using the standby cluster resource and the current cluster resource corresponding to the first cluster resource quantity. According to another aspect of the embodiments of the present application, there is also provided a computer readable storage medium having a computer program stored therein, wherein the computer program is configured to execute the above-described upgrading method of an application in a cluster when running.

According to another aspect of an embodiment of the present application, there is also provided an electronic device including one or more processors; and the memory is used for storing one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors are enabled to execute the programs, wherein the programs are set to execute the upgrading method applied in the cluster when running.

In the embodiment of the application, a target upgrading request for requesting to upgrade a target application deployed in a cluster is received first; then, responding to the target upgrading request, and detecting a target operation type of target upgrading operation corresponding to the target application; acquiring a second cluster resource amount for indicating the minimum cluster resource amount required by the target application upgrading process according to the target operation type; the standby cluster resources are distributed for the target application according to the first cluster resource quantity and the second cluster resource quantity occupied by the target application currently; and finally, upgrading the target application by using the standby cluster resources and the current cluster resources corresponding to the first cluster resource quantity.

In the process, the target operation type of the target upgrading operation corresponding to the target application requesting upgrading is detected, the minimum cluster resource amount required in the target application upgrading process is determined according to the target operation type, standby cluster resources are allocated for the target application according to the cluster resource amount currently occupied by the target application and the minimum cluster resource amount required by the target application upgrading, the purpose of upgrading the target application by using the standby cluster resources and the cluster resources currently occupied by the target application is achieved, the condition that the cluster resources required in the upgrading process of the target application are sufficient is ensured, the upgrading failure of the target application caused by insufficient cluster resources is avoided, and the upgrading process of the target application is enabled to be more stable, so that the technical effect of improving the robustness of the upgrading application in the cluster is achieved, and the technical problem of lower robustness of the upgrading application in the cluster in the related technology is solved.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this specification, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute a limitation on the application. In the drawings:

FIG. 1 is a flow chart of an alternative method of upgrading an application in a cluster according to an embodiment of the application;

FIG. 2 is a schematic diagram of an upgrade application in a scroll type according to an alternative embodiment of the present application;

FIG. 3 is a schematic diagram of an application for upgrading to create a type according to an alternative embodiment of the present application;

FIG. 4 is a flow chart of acquiring a second amount of resources according to an alternative embodiment of the present application;

FIG. 5 is a flow chart of a target application after an upgrade has been completed in accordance with an alternative embodiment of the present application;

FIG. 6 is a flow chart of an upgrade applied in a cluster in accordance with an alternative embodiment of the present application;

FIG. 7 is a schematic diagram of an upgrade apparatus applied in a cluster in accordance with an alternative embodiment of the present application;

fig. 8 is a schematic diagram of an alternative electronic device according to an embodiment of the application.

Detailed Description

In order that those skilled in the art will better understand the present application, a technical solution in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present application without making any inventive effort, shall fall within the scope of the present application.

It should be noted that the terms "first," "second," and the like in the description and the claims of the present application and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the application described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

It should be noted that the upgrading method, device, storage medium and electronic device applied in the cluster disclosed by the application can be used in the field of financial science and technology, and can also be used in any field except the field of financial science and technology.

It should be noted that, the user information (including but not limited to user equipment information, user personal information, etc.) and the data (including but not limited to data for analysis, stored data, displayed data, electronic medical records, etc.) related to the present application are information and data authorized by the user or fully authorized by each party, and the collection, use and processing of the related data need to comply with the related laws and regulations and standards of the related country and region, and provide corresponding operation entries for the user to select authorization or rejection.

Example 1

According to an embodiment of the present application, there is provided a method embodiment of an upgrade method applied in a cluster, it being noted that the steps shown in the flowchart of the figures may be performed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases the steps shown or described may be performed in an order different from that herein.

FIG. 1 is a flow chart of an alternative method of upgrading an application in a cluster, as shown in FIG. 1, according to an embodiment of the application, the method comprising the steps of:

step S102, receiving a target upgrading request, wherein the target upgrading request is used for requesting upgrading of target applications deployed in a cluster;

Step S104, responding to the target upgrading request, and detecting a target operation type of target upgrading operation corresponding to the target application;

step S106, obtaining a second cluster resource amount according to the target operation type, wherein the second cluster resource amount is used for indicating the minimum cluster resource amount required by the upgrading process of the target application;

step S108, allocating standby cluster resources for the target application according to the first cluster resource amount and the second cluster resource amount currently occupied by the target application;

step S110, executing the target upgrade operation on the target application by using the standby cluster resource and the current cluster resource corresponding to the first cluster resource amount.

In step S102, the target upgrade request may be, but is not limited to, an upgrade instruction for the target application triggered by clicking, selecting, etc. an upgrade page of the application in the cluster deployed in the embodiment on the cluster client by the user.

Alternatively, in this embodiment, a plurality of servers may be deployed in a cluster, and one server may include a plurality of applications, and one or more applications that need to be upgraded may be determined as a target application.

Alternatively, in this embodiment, the cluster may be, but is not limited to, kubernetes (k 8s cluster), an open source system for automatically deploying, expanding and managing containerized applications, and the target application may be, but is not limited to, one or more containerized applications, including resource objects pod (containers) that minimize running the containerized application.

In step S104, the target upgrade operation may, but is not limited to, upgrade the version of the target application such that the function of the target application is more comprehensive or such that the operation of the target application is more stable, and in the k8S cluster, the application may be deployed through a discover (controller used to manage release in k 8S) object and the function of the upgrade application may be implemented in a declarative manner.

Alternatively, in the present embodiment, in the k8s cluster, the target operation type may be, but is not limited to, determined according to the operation manner performed by the delete object when upgrading the application.

Optionally, in this embodiment, before detecting the target operation type of the target upgrade operation corresponding to the target application, all the depth information of the target application may be, but not limited to, stored in the pre-storage database, so as to quickly read the depth information.

In one exemplary embodiment, the target operation type of the target upgrade operation corresponding to the target application may be detected, but is not limited to, in response to the target upgrade request in the following manner: the target container controller corresponding to the target application is obtained, and the target upgrading operation is sent out in response to the target upgrading request, wherein the target container controller is used for managing a target container of the target application, and the target upgrading operation is used for realizing the upgrading of the target application by updating the target container; detecting the target operation type of the target upgrading operation, wherein the operation type of the upgrading operation of the application comprises: scroll type, and, create type.

Alternatively, in this embodiment, the container controller may be a replyment object used to manage the issued controller in the k8s cluster, in order to better solve the problem of service orchestration, and indirectly manage the Pod by replyment object management Replicaset (abbreviated as RS, which is an implementation of the Pod controller type, and is used to ensure that the number of Pod object copies managed by the replyment object management replyment object can exactly meet the desired number at any time), that is: reployment manages replicaset, which manages pod. A container controller may manage containers for one application, but is not limited to, and may also manage containers for a group of all applications of the same type.

Alternatively, in this embodiment, the container may be the smallest resource management component Pod in k8s, where Pod is also the smallest resource object running the containerized application, and one Pod represents one process running in the cluster. The target container controller is the container controller corresponding to the target application program, and upgrades the target application by updating a plurality of Pods in the target application.

Optionally, in the present embodiment, in the k8s cluster, the upgrade operations performed by the upgrade object are generally of two types: rolling update and re-creation update, in this embodiment, a rolling type is taken as a rolling update policy, and a creation type is taken as a re-creation update policy as an example.

In an alternative embodiment, there is provided a schematic diagram of upgrading an application in a scroll type, and fig. 2 is a schematic diagram of upgrading an application in a scroll type according to an alternative embodiment of the present application, as shown in fig. 2, if an upgrade operation type of the application is a scroll type, its specific operation is: when deleting a part of old version pod resources, supplementing and creating a part of new version pod objects to carry out application upgrading, and deleting and creating pod resources under the same ReplicaSet controller object by the scrolling update operation of the reployment controller, wherein the number of pod objects of the old controller is continuously reduced while the number of pod objects of the new controller is continuously increased until the old controller does not own pod objects any more and the number of copies of the new controller completely accords with the expected value.

Alternatively, in the present embodiment, an advantage of upgrading an application in a scroll type is that during the upgrade, the service provided by the application in the container is not interrupted, but the application program is required to be able to cope with a case where new and old versions work simultaneously, for example, the new and old versions are compatible with the same database scheme, etc. However, during the update operation, the response content obtained by different clients may come from different versions of the application. The scrolling update function of the depoyment can enable us to rapidly upgrade the application program without interrupting the service, thereby improving the availability and flexibility of the application program.

In an alternative embodiment, there is provided a schematic diagram of an upgrade application with creation type, and fig. 3 is a schematic diagram of an upgrade application with creation type according to an alternative embodiment of the present application, as shown in fig. 3, and if an upgrade operation type of an application is creation type, its specific operations are: the pod object of the existing version V1 is first deleted, and then the new version of the resource object is recreated by the controller based on the new template V2. In general, a create update policy may be used when new and old versions of an application are not compatible, because upgrading an application with a create type may result in temporary unavailability during application replacement, with the benefit that it does not have intermediate state, and the user accesses to either the new or old version of the application.

In step S106, the second cluster resource amount may be, but is not limited to, a minimum value indicating the amount of resources of the cluster resources that can be occupied by the application to normally complete the upgrade, that is, if the amount of cluster resources allocated to the target application to be upgraded is smaller than the second cluster resource amount, the resources of the target application to be upgraded will be insufficient, and since the creation of the duplicate depends on whether the resources of the current cluster are sufficient, under the condition of insufficient resources, the Pod under the duplicate will always be under the condition of insufficient resources, which will cause the Pod to be in a waiting state, and the Pod created by the beginning and the subsequent other pods will be in a competition state, and will not normally complete the rolling update under the condition of insufficient resources.

Alternatively, in this embodiment, the second cluster resource amount may be, but is not limited to, determined according to the operation type of the target upgrade operation, if the upgrade operation has two operation types in total: the operation type 1 and the operation type 2, when the target upgrade type is the operation type 1, the corresponding second cluster resource amount 1 can be obtained according to the operation type 1; in the case that the target upgrade type is operation type 2, the corresponding second cluster resource amount 2 may be obtained according to operation type 2.

In one exemplary embodiment, the second amount of cluster resources may be obtained from the target operation type in the following manner, but is not limited to: acquiring a target update parameter type corresponding to the target operation type from the operation type and the update parameter type which have the corresponding relation; reading target update parameters belonging to the target update parameter type from controller information of a target container controller corresponding to the target application; and inputting the target updating parameters into a target operation function corresponding to the target operation type to obtain the second cluster resource quantity.

Alternatively, in this embodiment, the update parameter type may be, but is not limited to, a type of parameter variable related to an application upgrade process, the target update parameter type may be, but is not limited to, a type of parameter variable related to a target application upgrade process that is required to determine the second cluster resource amount, and the target update parameter may be, but is not limited to, one or more parameter variables related to a target application upgrade process that belong to the target update parameter type.

Alternatively, in the present embodiment, the controller information of the target container controller may be, but is not limited to, acquired from a pre-stored database in which all the depth information in the cluster is pre-stored.

In an alternative embodiment, there is provided a flow of obtaining a second resource amount, and fig. 4 is a flow chart of obtaining the second resource amount according to an alternative embodiment of the present application, and as shown in fig. 4, the operation type and the update parameter type having a correspondence relationship include: if the operation type 1 corresponds to the update parameter type 1 and the operation type 2 corresponds to the update parameter type 2, the process of obtaining the second resource amount when the target operation type is the operation type 1 is as follows: acquiring a target update parameter type as an update parameter type 1; reading an update parameter 1 (target update parameter) from controller information of a target container controller corresponding to a target application; and inputting the update parameter 1 into the operation function 1 (the operation function corresponding to the operation type 1) to obtain a second cluster resource quantity 1. The process of obtaining the second resource amount when the target operation type is operation type 2 is as follows: acquiring a target update parameter type as an update parameter type 2; reading an update parameter 2 (target update parameter) from controller information of a target container controller corresponding to a target application; and inputting the updated parameter 2 into the operation function 2 (the operation function corresponding to the operation type 2) to obtain a second cluster resource quantity 2.

In one exemplary embodiment, the target update parameter type corresponding to the target operation type may be obtained from the operation type and the update parameter type having a correspondence relationship in the following manner, but is not limited to: in the case that the target operation type is a creation type, determining the target update parameter type includes: a container number type and a hard and soft limit type, wherein the container number type is used for indicating the number of containers included in the target application after upgrading; in the case that the target operation type is a scroll type, determining the target update parameter type includes: the system comprises a container number type, a container parameter type and a soft and hard limit type, wherein the container number type is used for indicating the number of containers included in the target application after upgrading, and the container parameter type is used for indicating that the target application is allowed to exceed the maximum number of containers required after upgrading in the upgrading process.

Alternatively, in the present embodiment, the container number type may include, but is not limited to, a field type that may indicate the number of containers included in the upgraded target application, an operator type, a resource object type in the cluster, and so on.

Alternatively, in the present embodiment, the soft-hard constraint type may include, but is not limited to, a soft constraint type and a hard constraint type, the hard constraint refers to an absolute constraint on the resource node and the data block, and the user is not allowed to exceed this constraint in any case; while a soft limit refers to a limit that a user may exceed the soft limit for a certain time frame. If the resource is continuously applied within the scope of the hard limit, the system gives warning information when the user logs in and can still continuously apply for the residual time of the resource. If the time period is reached, the user's hard disk usage still exceeds the soft limit, and the system will not allow the user to apply for hard disk resources again.

Alternatively, in the present embodiment, the container parameter types may include, but are not limited to, types that include variables that may indicate that the target application allows more than the maximum number of containers required after an upgrade during the upgrade.

In an exemplary embodiment, the second cluster resource amount may be obtained by, but not limited to, inputting the target update parameter to a target operation function corresponding to the target operation type in the following manner: in the case that the target operation type is a creation type, calculating the second cluster resource amount by the following target operation function:

Replica is a soft and hard limit value, wherein Replica is a target update parameter belonging to the container quantity type, and the soft and hard limit value is a target update parameter belonging to the soft and hard limit type;

and under the condition that the target operation type is a rolling type, calculating the second cluster resource amount through the following target operation function:

ceil (Replica) is a soft and hard limit value, where Replica is a target update parameter belonging to the container number type, soft and hard limit value is a target update parameter belonging to the soft and hard limit type, maxsurg is a target update parameter belonging to the container parameter type, ceil (rounding function, returning a minimum integer header file greater than or equal to a specified expression) is rounded up.

Optionally, in this embodiment, replica (duplicate) is a field parameter that may indicate the number of containers included in the target application after the upgrade, where Replica may be defined by, but is not limited to, a set of fields, including a selection operator to identify the set of available Pod, a value to indicate the number of copies that should be maintained, a Pod template to specify that a new Pod should be created to satisfy the number of copies condition, and so on. Each Replica can realize the existence value by creating and deleting Pod as required to enable the number of copies to reach the expected value. The provided Pod templates may be used when Replica needs to create a new Pod. The Replica is connected to the affiliated Pod through metadata. Ownerreferences (field representing affiliated object) field on the Pod, which gives the owner resource of the current object. The Pod obtained by Replica contains the identification information of the owner Replica in its own ownerrrefferences (field representing the dependency between resources) field. It is through this connection that the Replica knows the state of the Pod set it maintains and plans its operational behavior accordingly. Replica can use its selection operator to identify the Pod set to be obtained. If a Pod does not have an OwnerReference or its OwnerReference is not a controller and it matches to a selection operator of a reply, then the Pod is immediately acquired by the reply.

Alternatively, in this embodiment, the soft and hard limit values may include, but are not limited to, a soft limit value and a hard limit value of a cluster resource where the target application is located, maxsuge (maximum number of unavailable Pod), which is a parameter that may indicate that the maximum number of desired Pod may be exceeded during the upgrade.

Optionally, in this embodiment, the target operation type is when created: reading a Replica (copy number, equivalent to Pod number) field and a corresponding soft and hard limit in the reployment, wherein the required minimum resource value is a Replica soft and hard limit value; when the target operation type is rolling update, a maxsource field in the replyment is read, and the minimum resource value required by shrinkage is ceil [ Replica ] maxsource ] soft and hard limit value.

In step S108, the first cluster resource amount may be, but is not limited to, obtained from actual resource usage of all applications in the cluster, so as to obtain the resource amount of the cluster resource currently occupied by the target application.

Optionally, in this embodiment, the resource amount of the standby cluster resource may be determined according to, but not limited to, the resource amount of the cluster resource currently occupied by the target application and the resource amount of the minimum cluster resource required by the upgrading process of the target application, so as to allocate the standby cluster resource meeting the condition to the target application, so that the situation that the upgrading failure is caused by insufficient resources in the upgrading process of the target application does not occur, and stability and robustness of the upgrading process of the target application are improved.

In one exemplary embodiment, standby cluster resources may be allocated to the target application according to the first amount of cluster resources and the second amount of cluster resources currently occupied by the target application in the following manner: calculating a difference between the second cluster resource amount and the first cluster resource amount to obtain a standby cluster resource amount under the condition that the first cluster resource amount is smaller than the second cluster resource amount; and allocating the standby cluster resources which are larger than or equal to the standby cluster resources for the target application.

Optionally, in this embodiment, it may be, but not limited to, judging whether the first cluster resource amount currently occupied by the target application can enable the target application to successfully complete the upgrading process according to the minimum cluster resource amount required in the upgrading process of the target application, if the first cluster resource amount currently occupied by the target application is smaller than the minimum cluster resource amount (the second cluster resource amount) required in the upgrading process of the target application, which means that the target application may not pull up the pod due to insufficient resources at this time, so as to cause upgrading failure, and at this time, calculating a difference value between the minimum cluster resource amount required in the upgrading process of the target application and the first cluster resource amount currently occupied by the target application, and determining the difference value as the standby cluster resource amount. The vertical expansion capability of the cluster can be automatically used for adding the standby cluster resources to the target application, and the sum of the standby cluster resources and the current occupied first cluster resources of the target application meets the second cluster resources, so that the target application can successfully complete the upgrading process.

Optionally, in this embodiment, if the first cluster resource amount currently occupied by the target application is greater than the minimum cluster resource amount (the second cluster resource amount) required in the upgrading process of the target application, it indicates that the cluster resource of the current target application is sufficient, and no operation is needed at this time, and the target application is updated after completion.

In step S110, a target upgrade operation corresponding to the target operation type may be performed on the target application using the current cluster resource corresponding to the standby cluster resource and the first cluster resource amount using the deeployment.

In an exemplary embodiment, after the target upgrade operation is performed on the target application using the standby cluster resource and the current cluster resource corresponding to the first cluster resource amount, the upgrade method of the application in the following cluster may be, but is not limited to, adopted: detecting whether the target application is upgraded or not under the condition that the target operation type is a rolling type; and under the condition that the target application is detected to finish upgrading, releasing unused cluster resources of the target application after upgrading.

In an alternative embodiment, a process after the target application finishes upgrading is provided, fig. 5 is a flowchart after the target application finishes upgrading according to an alternative embodiment of the present application, and as shown in fig. 5, in the case that the target operation type is a rolling type, whether the target application finishes upgrading is detected, and in the case that the target application finishes upgrading, unnecessary cluster resources unused by the target application after upgrading are released, so that the cluster resource utilization rate is improved.

In an alternative embodiment, a flow of upgrades of applications in a cluster is provided, fig. 6 is a flow chart of upgrades of applications in a cluster according to an alternative embodiment of the application, as shown in fig. 6, the upgrade may be pre-stored first: storing each applied replyment into a database for fast reading of replyment information; and secondly detecting the operation type of the Deployment: to clearly calculate the usage size of the resource value, detecting the operation of the depoyment as a rolling update or creating operation, wherein the resource conditions required by the two operations are different; when the operation type is creation: reading a Replica (copy number, equivalent to Pod number) field and a corresponding soft and hard limit in the reployment, wherein the required minimum resource value is a Replica soft and hard limit value; when the operation type is rolling update, reading a maxsource field in the reployment, wherein the minimum resource value required is ceil [ Replica ] maxsource ] soft and hard limit values; then detecting cluster resource use conditions; under the condition of sufficient cluster resources, no operation is performed; in the case of insufficient cluster resources: if the upgrade operation is a creation type, automatically using the vertical expansion capability to automatically add resources for the cluster; if the upgrade operation is a rolling update type, automatically using the vertical expansion capability to automatically add resources for the cluster, and automatically releasing redundant resources after the rolling update is completed.

Optionally, in this embodiment, in a multi-cluster scenario, by sensing the resource usage conditions of different partitions of the cluster, the proportion of the deployment of the cluster container, the lower limit of the application template usage resources, and the additional vertical expansion capability, when the application issues and scrolls the upgrade template, the resource limit of the current template in the current cluster is automatically adjusted, and the application low-intelligence operation is increased. When the lower limit of the application resources is not met, the vertical expansion capability is automatically started, the application is automatically assisted to add resources, the resource control capability of the cluster is improved, and therefore the robustness of application upgrading in the cluster is improved.

From the foregoing, it can be seen that a target upgrade request is first received for requesting an upgrade of a target application deployed in a cluster; then, responding to the target upgrading request, and detecting a target operation type of target upgrading operation corresponding to the target application; acquiring a second cluster resource amount for indicating the minimum cluster resource amount required by the target application upgrading process according to the target operation type; the standby cluster resources are distributed for the target application according to the first cluster resource quantity and the second cluster resource quantity occupied by the target application currently; and finally, upgrading the target application by using the standby cluster resources and the current cluster resources corresponding to the first cluster resource quantity.

In the method, the target operation type of the target upgrading operation corresponding to the target application requesting upgrading is detected, the minimum cluster resource amount required in the upgrading process of the target application is determined according to the target operation type, the standby cluster resource is allocated for the target application according to the current occupied cluster resource amount of the target application and the minimum cluster resource amount required by the target application upgrading, the purpose of upgrading the target application by using the standby cluster resource and the current occupied cluster resource of the target application is achieved, the sufficient quantity of the cluster resource required in the upgrading process of the target application is ensured, the upgrading failure of the target application caused by insufficient cluster resource is avoided, the upgrading process of the target application is enabled to be more stable, the technical effect of improving the robustness of the upgrading application in the cluster is achieved, and the technical problem of lower robustness of the upgrading application in the cluster in the related technology is solved.

It should be noted that the steps illustrated in the flowcharts of the figures may be performed in a computer system such as a set of computer executable instructions, and that although a logical order is illustrated in the flowcharts, in some cases the steps illustrated or described may be performed in an order other than that illustrated herein.

Example 2

According to an embodiment of the present application, there is provided an embodiment of an upgrade apparatus applied in a cluster, where fig. 7 is a schematic diagram of an alternative upgrade apparatus applied in a cluster according to an embodiment of the present application, as shown in fig. 7, and the apparatus includes:

a receiving module 702, configured to receive a target upgrade request, where the target upgrade request is used to request upgrading of a target application deployed in a cluster;

a first detection module 704, configured to respond to the target upgrade request, and detect a target operation type of a target upgrade operation corresponding to the target application;

an obtaining module 706, configured to obtain a second cluster resource amount according to the target operation type, where the second cluster resource amount is used to indicate a minimum cluster resource amount required by an upgrade process of the target application;

an allocation module 708, configured to allocate standby cluster resources for the target application according to the first cluster resource amount currently occupied by the target application and the second cluster resource amount;

and an upgrade module 710, configured to execute the target upgrade operation on the target application by using the standby cluster resource and the current cluster resource corresponding to the first cluster resource amount.

It should be noted that the receiving module 702, the first detecting module 704, the obtaining module 706, the allocating module 708, and the upgrading module 710 correspond to the steps S102 to S110 in the above embodiment 1, and the five modules are the same as the examples and application scenarios implemented by the corresponding steps, but are not limited to the disclosure of the above embodiment 1.

The upgrading device for the application in the cluster provided in the embodiment 2 of the present application firstly receives a target upgrading request for requesting to upgrade a target application deployed in the cluster; then, responding to the target upgrading request, and detecting a target operation type of target upgrading operation corresponding to the target application; acquiring a second cluster resource amount for indicating the minimum cluster resource amount required by the target application upgrading process according to the target operation type; the standby cluster resources are distributed for the target application according to the first cluster resource quantity and the second cluster resource quantity occupied by the target application currently; and finally, upgrading the target application by using the standby cluster resources and the current cluster resources corresponding to the first cluster resource quantity.

In the device, the target operation type of the target upgrading operation corresponding to the target application requesting upgrading is detected, the minimum cluster resource amount required in the upgrading process of the target application is determined according to the target operation type, the standby cluster resource is allocated for the target application according to the current occupied cluster resource amount of the target application and the minimum cluster resource amount required by the target application upgrading, the purpose of upgrading the target application by using the standby cluster resource and the current occupied cluster resource of the target application is achieved, the sufficient quantity of the cluster resource required in the upgrading process of the target application is ensured, the upgrading failure of the target application caused by insufficient cluster resource is avoided, and the upgrading process of the target application is enabled to be more stable, so that the technical effect of improving the robustness of the upgrading application in the cluster is achieved, and the technical problem of lower robustness of the upgrading application in the related technology is solved.

Optionally, the first detection module includes: the first obtaining unit is used for obtaining a target container controller corresponding to the target application to respond to the target upgrading request and send out the target upgrading operation, wherein the target container controller is used for managing a target container of the target application, and the target upgrading operation is used for realizing the upgrading of the target application by updating the target container; the detection unit is used for detecting the target operation type of the target upgrading operation, wherein the operation type of the upgrading operation of the application comprises the following steps: scroll type, and, create type.

Optionally, the acquiring module includes: the second acquisition unit is used for acquiring a target update parameter type corresponding to the target operation type from the operation type and the update parameter type which have the corresponding relation; the reading unit is used for reading the target update parameters belonging to the target update parameter type from the controller information of the target container controller corresponding to the target application; and the input unit is used for inputting the target updating parameters into the target operation function corresponding to the target operation type to obtain the second cluster resource quantity.

Optionally, the second obtaining unit is configured to: in the case that the target operation type is a creation type, determining the target update parameter type includes: a container number type and a hard and soft limit type, wherein the container number type is used for indicating the number of containers included in the target application after upgrading; in the case that the target operation type is a scroll type, determining the target update parameter type includes: the system comprises a container number type, a container parameter type and a soft and hard limit type, wherein the container number type is used for indicating the number of containers included in the target application after upgrading, and the container parameter type is used for indicating that the target application is allowed to exceed the maximum number of containers required after upgrading in the upgrading process.

Optionally, the input unit is configured to: in the case that the target operation type is a creation type, calculating the second cluster resource amount by the following target operation function: replica is a soft and hard limit value, wherein Replica is a target update parameter belonging to the container quantity type, and the soft and hard limit value is a target update parameter belonging to the soft and hard limit type; and under the condition that the target operation type is a rolling type, calculating the second cluster resource amount through the following target operation function: ceil (Replica) is a soft and hard limit value, wherein Replica is a target update parameter belonging to the container number type, the soft and hard limit value is a target update parameter belonging to the soft and hard limit type, maxsurg is a target update parameter belonging to the container parameter type, and ceil is an upward rounding.

Optionally, the allocation module includes: a calculating unit, configured to calculate a difference between the second cluster resource amount and the first cluster resource amount to obtain a standby cluster resource amount when the first cluster resource amount is smaller than the second cluster resource amount; and the allocation unit is used for allocating the standby cluster resources which are larger than or equal to the standby cluster resources for the target application.

Optionally, the upgrading device applied in the cluster further includes: the second detection module is used for detecting whether the target application is upgraded or not under the condition that the target operation type is a rolling type; and the releasing module is used for releasing unused cluster resources of the target application after upgrading under the condition that the target application is detected to finish upgrading.

Example 3

According to another aspect of the embodiments of the present application, there is also provided a computer readable storage medium having a computer program stored therein, wherein the computer program is configured to execute the above-described method of upgrading an application in a cluster at run-time.

Example 4

According to another aspect of an embodiment of the present application, there is also provided an electronic device, wherein fig. 8 is a schematic diagram of an alternative electronic device according to an embodiment of the present application, as shown in fig. 8, the electronic device including one or more processors; and the memory is used for storing one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors are enabled to execute the programs, wherein the programs are set to execute the upgrading method applied in the cluster when running.

As shown in fig. 8, an embodiment of the present application provides an electronic device, where the device includes a processor, a memory, and a program stored in the memory and executable on the processor, and when the processor executes the program, the following steps are implemented:

receiving a target upgrading request, wherein the target upgrading request is used for requesting upgrading of target applications deployed in a cluster; responding to the target upgrading request, and detecting a target operation type of target upgrading operation corresponding to the target application; acquiring a second cluster resource amount according to the target operation type, wherein the second cluster resource amount is used for indicating the minimum cluster resource amount required by the upgrading process of the target application; allocating standby cluster resources for the target application according to the first cluster resource amount and the second cluster resource amount currently occupied by the target application; and executing the target upgrading operation on the target application by using the standby cluster resource and the current cluster resource corresponding to the first cluster resource quantity.

Optionally, the processor further implements the following steps when executing the program: acquiring a target update parameter type corresponding to the target operation type from the operation type and the update parameter type which have the corresponding relation; reading target update parameters belonging to the target update parameter type from controller information of a target container controller corresponding to the target application; and inputting the target updating parameters into a target operation function corresponding to the target operation type to obtain the second cluster resource quantity.

Optionally, the processor further implements the following steps when executing the program: in the case that the target operation type is a creation type, determining the target update parameter type includes: a container number type and a hard and soft limit type, wherein the container number type is used for indicating the number of containers included in the target application after upgrading; in the case that the target operation type is a scroll type, determining the target update parameter type includes: the system comprises a container number type, a container parameter type and a soft and hard limit type, wherein the container number type is used for indicating the number of containers included in the target application after upgrading, and the container parameter type is used for indicating that the target application is allowed to exceed the maximum number of containers required after upgrading in the upgrading process.

Optionally, the processor further implements the following steps when executing the program: in the case that the target operation type is a creation type, calculating the second cluster resource amount by the following target operation function: replica is a soft and hard limit value, wherein Replica is a target update parameter belonging to the container quantity type, and the soft and hard limit value is a target update parameter belonging to the soft and hard limit type; and under the condition that the target operation type is a rolling type, calculating the second cluster resource amount through the following target operation function: ceil (Replica) is a soft and hard limit value, wherein Replica is a target update parameter belonging to the container number type, the soft and hard limit value is a target update parameter belonging to the soft and hard limit type, maxsurg is a target update parameter belonging to the container parameter type, and ceil is an upward rounding.

Optionally, the processor further implements the following steps when executing the program: calculating a difference between the second cluster resource amount and the first cluster resource amount to obtain a standby cluster resource amount under the condition that the first cluster resource amount is smaller than the second cluster resource amount; and allocating the standby cluster resources which are larger than or equal to the standby cluster resources for the target application.

Optionally, the processor further implements the following steps when executing the program: the target container controller corresponding to the target application is obtained, and the target upgrading operation is sent out in response to the target upgrading request, wherein the target container controller is used for managing a target container of the target application, and the target upgrading operation is used for realizing the upgrading of the target application by updating the target container; detecting the target operation type of the target upgrading operation, wherein the operation type of the upgrading operation of the application comprises: scroll type, and, create type.

Optionally, the processor further implements the following steps when executing the program: detecting whether the target application is upgraded or not under the condition that the target operation type is a rolling type; and under the condition that the target application is detected to finish upgrading, releasing unused cluster resources of the target application after upgrading.

The foregoing embodiment numbers of the present application are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.

In the foregoing embodiments of the present application, the descriptions of the embodiments are emphasized, and for a portion of this disclosure that is not described in detail in this embodiment, reference is made to the related descriptions of other embodiments.

In the several embodiments provided in the present application, it should be understood that the disclosed technology may be implemented in other manners. The above-described embodiments of the apparatus are merely exemplary, and the division of units may be a logic function division, and there may be another division manner in actual implementation, for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be through some interfaces, units or modules, or may be in electrical or other forms.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.

The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be embodied in essence or a part contributing to the prior art or all or part of the technical solution in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method of the various embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a removable hard disk, a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely a preferred embodiment of the present application and it should be noted that modifications and adaptations to those skilled in the art may be made without departing from the principles of the present application, which are intended to be comprehended within the scope of the present application.

Claims (10)

1. An upgrade method for an application in a cluster, comprising:

receiving a target upgrading request, wherein the target upgrading request is used for requesting upgrading of target applications deployed in a cluster;

responding to the target upgrading request, and detecting a target operation type of target upgrading operation corresponding to the target application;

acquiring a second cluster resource amount according to the target operation type, wherein the second cluster resource amount is used for indicating the minimum cluster resource amount required by the upgrading process of the target application;

allocating standby cluster resources for the target application according to the first cluster resource amount and the second cluster resource amount currently occupied by the target application;

and executing the target upgrading operation on the target application by using the standby cluster resource and the current cluster resource corresponding to the first cluster resource quantity.

2. The method of claim 1, wherein the obtaining a second amount of cluster resources according to the target operation type comprises:

Acquiring a target update parameter type corresponding to the target operation type from the operation type and the update parameter type which have the corresponding relation;

reading target update parameters belonging to the target update parameter type from controller information of a target container controller corresponding to the target application;

and inputting the target updating parameters into a target operation function corresponding to the target operation type to obtain the second cluster resource quantity.

3. The method according to claim 2, wherein the obtaining the target update parameter type corresponding to the target operation type from the operation type and the update parameter type having the correspondence relation includes:

in the case that the target operation type is a creation type, determining the target update parameter type includes: a container number type and a hard and soft limit type, wherein the container number type is used for indicating the number of containers included in the target application after upgrading;

in the case that the target operation type is a scroll type, determining the target update parameter type includes: the system comprises a container number type, a container parameter type and a soft and hard limit type, wherein the container number type is used for indicating the number of containers included in the target application after upgrading, and the container parameter type is used for indicating that the target application is allowed to exceed the maximum number of containers required after upgrading in the upgrading process.

4. The method of claim 3, wherein the inputting the target update parameter to the target operation function corresponding to the target operation type to obtain the second cluster resource amount includes:

in the case that the target operation type is a creation type, calculating the second cluster resource amount by the following target operation function:

replica is a soft-hard limit,

wherein Replica is a target update parameter belonging to the container quantity type, and the soft and hard limit value is a target update parameter belonging to the soft and hard limit type;

and under the condition that the target operation type is a rolling type, calculating the second cluster resource amount through the following target operation function:

ceil [ Replica max merge ] soft and hard limit values,

wherein Replica is a target update parameter belonging to the container quantity type, the soft and hard limit value is a target update parameter belonging to the soft and hard limit type, maxsuge is a target update parameter belonging to the container parameter type, and ceil is an upward rounding.

5. The method of claim 1, wherein the allocating standby cluster resources for the target application based on the first amount of cluster resources and the second amount of cluster resources currently occupied by the target application comprises:

Calculating a difference between the second cluster resource amount and the first cluster resource amount to obtain a standby cluster resource amount under the condition that the first cluster resource amount is smaller than the second cluster resource amount;

and allocating the standby cluster resources which are larger than or equal to the standby cluster resources for the target application.

6. The method of claim 1, wherein detecting a target operation type of a target upgrade operation corresponding to the target application comprises:

the target container controller corresponding to the target application is obtained, and the target upgrading operation is sent out in response to the target upgrading request, wherein the target container controller is used for managing a target container of the target application, and the target upgrading operation is used for realizing the upgrading of the target application by updating the target container;

detecting the target operation type of the target upgrading operation, wherein the operation type of the upgrading operation of the application comprises: scroll type, and, create type.

7. The method of claim 1, wherein after performing the target upgrade operation on the target application using the backup cluster resource and a current cluster resource corresponding to the first amount of cluster resources, the method further comprises:

Detecting whether the target application is upgraded or not under the condition that the target operation type is a rolling type;

and under the condition that the target application is detected to finish upgrading, releasing unused cluster resources of the target application after upgrading.

8. An upgrade apparatus for use in a cluster, comprising:

the system comprises a receiving module, a target upgrading module and a processing module, wherein the receiving module is used for receiving a target upgrading request, and the target upgrading request is used for requesting upgrading of target applications deployed in a cluster;

the first detection module is used for responding to the target upgrading request and detecting a target operation type of target upgrading operation corresponding to the target application;

the acquisition module is used for acquiring a second cluster resource amount according to the target operation type, wherein the second cluster resource amount is used for indicating the minimum cluster resource amount required by the upgrading process of the target application;

the allocation module is used for allocating standby cluster resources for the target application according to the first cluster resource amount and the second cluster resource amount currently occupied by the target application;

and the upgrading module is used for executing the target upgrading operation on the target application by using the standby cluster resource and the current cluster resource corresponding to the first cluster resource quantity.

9. A computer readable storage medium, characterized in that a computer program is stored in the computer readable storage medium, wherein the computer program is arranged to execute, at run-time, the upgrade method of the application in the cluster according to any one of the claims 1 to 7.

10. An electronic device comprising one or more processors and a memory for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method of upgrading applied in a cluster of any of claims 1-7.