CN111858042B - Method and device for verifying micro-service governance quota opening based on domestic cloud platform - Google Patents

Abstract

The invention provides a method and a device for checking the opening of a micro-service administration quota based on a domestic cloud platform, wherein the method comprises the following steps: s1, when an application needs to be started for micro-service treatment, counting a resource quota required by starting the micro-service treatment in the current environment; s2, verifying whether the available resource amount of the virtual data center where the application is located meets the resource quota required by starting micro-service treatment; and S3, when the available resource amount of the virtual data center where the application is located does not meet the resource quota required for starting the micro-service treatment, deleting the low-priority deletable resource of the current virtual data center until the available resource amount of the virtual data center where the application is located meets the resource quota required for starting the micro-service treatment, and starting the micro-service treatment in the application. The method and the device realize the advanced verification whether the quota meets the condition of starting the micro-service management when the application in the domestic cloud platform is used for starting the micro-service management, avoid the failure of restarting the workload due to insufficient quota, and improve the fault tolerance of the domestic cloud platform.

Description

Method and device for verifying opening of microservice governance quota based on localized cloud platform

technical field

The invention belongs to the technical field of microservice governance, and in particular relates to a method and device for verifying opening of microservice governance quotas based on a localized cloud platform.

Background technique

Pod, a process running on a node, has a certain life cycle.

istio-proxy, istio proxy, Istio is a microservice management, protection and monitoring framework open sourced by Google, IBM and Lyft.

There is a virtual data center in the domestic cloud platform. After microservice governance is enabled for an application in a virtual data center, the workload of the application will be restarted, and an istio-proxy container will be added to each Pod of the workload. Therefore, after enabling service governance for an application, the resources required by the application will greatly increase. If the available resources of the current virtual data center cannot meet the requirements of enabling microservice governance for the application, the microservice will be enabled without the user's knowledge. Governance operations will cause the workload under the application to fail to restart, making the entire application unusable.

This is the deficiency of the existing technology. Therefore, in view of the above-mentioned defects in the prior art, it is very necessary to provide a method and device for verifying the opening of microservice governance quotas based on a localized cloud platform.

Contents of the invention

Aiming at the defect in the prior art that if the microservice management operation is performed without the user's knowledge, the workload under the application will fail to restart, resulting in the failure of the entire application to be used. The present invention provides a cloud platform based on localization. The method and device for verifying the opening of microservice management quotas are used to solve the above technical problems.

In the first aspect, the present invention provides a method for verifying the opening of microservice governance quotas based on a localized cloud platform, including the following steps:

S1. When the application needs to be enabled as microservice governance, count the resource quota required to enable microservice governance in the current environment;

S2. Check whether the amount of resources available in the virtual data center where the application is located satisfies the resource quota required for enabling microservice governance;

S3. When the amount of resources available in the virtual data center where the application is located does not meet the resource quota required for enabling microservice governance, delete the low-priority resources that can be deleted in the current virtual data center until the amount of available resources in the virtual data center where the application is located meets the requirements for enabling microservice governance. The resource quota required for service governance, enable microservice governance in the application.

Further, the specific steps of step S1 are as follows:

S11. When the application needs to enable microservice governance, traverse all the workloads of the current application in turn, and count the number of workload instances N;

S12. Obtain the amount of resources M occupied by a single container of istio-proxy in the current environment by querying the configuration file;

S13. Calculate the resource quota required for enabling microservice governance in the current environment S=the number of workload instances N*the resource amount M occupied by a single container of istio-proxy. The resource quota required to enable the application microservice governance is the product of the number of workload instances under the application and the amount of resources occupied by the istio-proxy container.

Further, in step S11, when a workload has auto-scaling resources, the maximum number of instances of the auto-scaling resource is used as the number of instances of the workload. The maximum number of instances of an auto scaling resource is the number of available instances, so the maximum number of instances should be used.

Further, in step S12, obtain the CPU and the amount of memory resources occupied by the istio-proxy single container of the current environment by querying the configuration file;

In step S13, the resource quota S required to enable microservice governance in the current environment includes the required total CPU usage S1 and the required total memory usage S2;

Total required CPU usage S1 = number of workload instances N*istio-proxy CPU usage M1 occupied by a single container;

Total required memory usage S2 = number of workload instances N*istio-proxy CPU usage M2 occupied by a single container. The resource quota required for Qiwei service governance usually includes the total required CPU usage and the total required memory usage, but is not limited thereto.

Further, the specific steps of step S2 are as follows:

S21. Count all the workloads of the virtual data center where the application is located, count the total usage of the workload database, calculate the amount of available resources in the database, and check whether the amount of available resources in the database meets the resources required to start microservice governance;

If so, go to step S22;

If not, go to step S3;

S22. Count the amount of resources occupied by the bottom layer of all workloads in the virtual data center where the application is located, calculate the amount of available resources at the bottom layer of the workload, and check whether the amount of available resources at the bottom layer of the workload meets the requirements for enabling microservice governance, and enter step S3. Quota verification checks whether the quota is sufficient from two aspects. On the one hand, it counts all the workloads under the virtual data center and the total usage of the workload database; on the other hand, in order to avoid inaccurate resource data in the database, Traverse the amount of resources occupied by all workloads under the virtual data center. Allows the application to enable microservices governance if the required quotas are satisfied both in the database and in the underlying resources.

Further, the specific steps of step S3 are as follows:

S31. When the amount of resources available in the virtual data center where the application is located does not meet the resource quota required for enabling microservice governance, enter step S32;

When the amount of resources available in the virtual data center where the application is located satisfies the resource quota required for enabling microservice governance, enter step S33;

S32. Detect whether there is a deletable low-priority application in the virtual data center where the application is located;

If yes, delete the low-priority application and return to step S21;

If not, prompt the user that the resources are insufficient, and the microservice management cannot be enabled, and end;

S33. Enable microservice governance for the application. Deleting low-priority applications can realize cooperative scheduling when the available resources of the virtual data center are insufficient, and meet the requirements for enabling microservice governance.

In the second aspect, the present invention provides a device for verifying the opening of microservice governance quotas based on a localized cloud platform, including:

The required resource quota statistics module is used to count the resource quota required to enable microservice governance in the current environment when the application needs to be enabled for microservice governance;

The resource verification module is used to verify whether the amount of resources available in the virtual data center where the application is located satisfies the resource quota required for enabling microservice governance;

The resource deletion module is used to delete the low-priority deletable resources of the current virtual data center until the available resources of the virtual data center where the application is located when the amount of resources available in the virtual data center where the application is located does not meet the resource quota required for enabling microservice governance The amount meets the resource quota required to enable microservice governance, and enable microservice governance in the application.

Further, the required resource quota statistics module includes:

The workload instance statistics unit is used to sequentially traverse all the workloads of the current application when the application needs to enable microservice governance, and count the number of workload instances N;

The resource occupation query unit of a single container is used to obtain the amount of resources M occupied by a single container of istio-proxy in the current environment by querying the configuration file;

The required resource quota calculation unit is used to calculate the resource quota required for enabling microservice governance in the current environment S=the number of workload instances N*the resource amount M occupied by a single container of istio-proxy.

Further, the resource verification module includes:

The database resource verification unit is used to count all workloads in the virtual data center where the application is located, count the total usage of the workload database, calculate the amount of available resources in the database, and verify whether the amount of available resources in the database meets the requirements for enabling microservice governance required resources;

The underlying resource verification unit is used to count the amount of resources occupied by all workloads in the virtual data center where the application is located, calculate the amount of available resources at the bottom of the workload, and verify whether the amount of available resources at the bottom of the workload meets the requirements for enabling microservice governance.

Further, the resource deletion module includes:

The deletable application judgment unit is used to detect whether there is a deletable low-priority application in the virtual data center where the application is located when the amount of resources available in the virtual data center where the application is located does not meet the resource quota required for enabling microservice governance;

The microservice governance enabling unit is used to enable microservice governance for the application when the amount of resources available in the virtual data center where the application is located satisfies the resource quota required for enabling microservice governance;

The low-priority application deletion unit is used to delete the low-priority application when there is a deletable low-priority application in the virtual data center where the application is located;

The user prompt unit is used to prompt the user that resources are insufficient and microservice management cannot be started when there is no deletable low-priority application in the virtual data center where the application is located.

The beneficial effect of the present invention is that,

The method and device for verifying the opening of micro-service governance quotas based on the localized cloud platform provided by the present invention can realize the early verification of whether the quota meets the conditions for opening the micro-service governance when the application in the localized cloud platform starts the micro-service governance, Avoid workload restart failures due to insufficient quotas, and improve the fault tolerance of the localized cloud platform.

In addition, the design principle of the present invention is reliable, the structure is simple, and has very wide application prospects.

It can be seen that, compared with the prior art, the present invention has outstanding substantive features and remarkable progress, and the beneficial effects of its implementation are also obvious.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, for those of ordinary skill in the art, In other words, other drawings can also be obtained from these drawings on the premise of not paying creative work.

Fig. 1 is a schematic flow diagram of the method of the present invention;

Fig. 2 is the second schematic flow diagram of the method of the present invention;

Fig. 3 is a schematic diagram of the system of the present invention;

In the figure, 1- required resource quota statistics module; 1.1- workload instance statistics unit; 1.2- single container resource occupation query unit; 1.3- required resource quota calculation unit; 2- resource verification module; 2.1- database resource calibration 2.2-bottom resource verification unit; 3-resource deletion module; 3.1-deletable application judgment unit; 3.2-microservice governance opening unit; 3.3-low priority application deletion unit; 3.4-user prompt unit.

detailed description

In order to enable those skilled in the art to better understand the technical solutions in the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described The embodiments are only some of the embodiments of the present invention, not all of them. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts shall fall within the protection scope of the present invention.

Example 1:

As shown in Figure 1, the present invention provides a method for verifying the opening of microservice governance quotas based on a localized cloud platform, including the following steps:

S1. When the application needs to be enabled as microservice governance, count the resource quota required to enable microservice governance in the current environment;

S2. Check whether the amount of resources available in the virtual data center where the application is located satisfies the resource quota required for enabling microservice governance;

S3. When the amount of resources available in the virtual data center where the application is located does not meet the resource quota required for enabling microservice governance, delete the low-priority resources that can be deleted in the current virtual data center until the amount of available resources in the virtual data center where the application is located meets the requirements for enabling microservice governance. The resource quota required for service governance, enable microservice governance in the application.

Example 2:

As shown in Figure 2, the present invention provides a method for verifying the opening of microservice governance quotas based on a localized cloud platform, including the following steps:

S1. When the application needs to be enabled as microservice governance, count the resource quota required to enable microservice governance in the current environment; the specific steps are as follows:

S11. When the application needs to enable microservice governance, traverse all the workloads of the current application in turn, and count the number of workload instances N;

S12. Obtain the amount of resources M occupied by a single container of istio-proxy in the current environment by querying the configuration file;

S13. Calculate the resource quota required for enabling microservice governance in the current environment S=number of workload instances N*istio-proxy resources occupied by a single container M;

S2. Verify that the amount of resources available in the virtual data center where the application is located meets the resource quota required for enabling microservice governance; the specific steps are as follows:

S21. Count all the workloads of the virtual data center where the application is located, count the total usage of the workload database, calculate the amount of available resources in the database, and check whether the amount of available resources in the database meets the resources required to start microservice governance;

If so, go to step S22;

If not, go to step S3;

S22. Count the amount of resources occupied by the bottom layer of all workloads in the virtual data center where the application is located, calculate the amount of available resources at the bottom layer of the workload, and check whether the amount of available resources at the bottom layer of the workload meets the requirements for enabling micro-service management, and enter step S3;

S3. When the amount of resources available in the virtual data center where the application is located does not meet the resource quota required for enabling microservice governance, delete the low-priority resources that can be deleted in the current virtual data center until the amount of available resources in the virtual data center where the application is located meets the requirements for enabling microservice governance. For the resource quota required for service governance, enable microservice governance in the application; the specific steps are as follows:

S31. When the amount of resources available in the virtual data center where the application is located does not meet the resource quota required for enabling microservice governance, enter step S32;

When the amount of resources available in the virtual data center where the application is located satisfies the resource quota required for enabling microservice governance, enter step S33;

S32. Detect whether there is a deletable low-priority application in the virtual data center where the application is located;

If yes, delete the low-priority application and return to step S21;

If not, prompt the user that the resources are insufficient, and the microservice management cannot be enabled, and end;

S33. Enable microservice governance for the application.

In the above-mentioned embodiment 2, in step S11, when a workload has auto-scaling resources, the maximum number of instances of the auto-scaling resource is used as the number of instances of the workload.

In the above-mentioned embodiment 2, in step S12, obtain the CPU and the amount of memory resources occupied by the istio-proxy single container of the current environment by querying the configuration file;

In step S13, the resource quota S required to enable microservice governance in the current environment includes the required total CPU usage S1 and the required total memory usage S2;

Total required CPU usage S1 = number of workload instances N*istio-proxy CPU usage M1 occupied by a single container;

The total amount of required memory usage S2 = the number of workload instances N* the CPU usage M2 occupied by a single container of istio-proxy.

Example 3:

As shown in Figure 3, the present invention provides a device for verifying the opening of microservice governance quotas based on a localized cloud platform, including:

The required resource quota statistics module 1 is used to count the resource quotas required to enable microservice governance in the current environment when the application needs to be started as microservice governance; the required resource quota statistics module 1 includes:

The workload instance statistics unit 1.1 is used to traverse all the workloads of the current application in turn and count the number of workload instances N when the application needs to enable microservice governance;

The single container resource occupation query unit 1.2 is used to obtain the amount of resources M occupied by a single container of istio-proxy in the current environment by querying the configuration file;

The required resource quota calculation unit 1.3 is used to calculate the resource quota required for enabling microservice governance in the current environment S=the number of instances of the workload N*istio-proxy resource amount M occupied by a single container;

The resource verification module 2 is used to verify whether the amount of resources available in the virtual data center where the application is located satisfies the resource quota required for enabling microservice governance; the resource verification module 2 includes:

The database resource verification unit 2.1 is used to count all workloads in the virtual data center where the application is located, count the total usage of the workload database, calculate the amount of available resources in the database, and verify whether the amount of available resources in the database meets the requirements for starting microservices resources needed for governance;

The underlying resource verification unit 2.2 is used to count the amount of resources occupied by the bottom layer of all workloads in the virtual data center where the application is located, calculate the amount of available resources at the bottom layer of the workload, and verify whether the amount of available resources at the bottom layer of the workload meets the requirements for enabling microservice governance;

The resource deletion module 3 is used to delete the low-priority deletable resources of the current virtual data center until the resources available in the virtual data center where the application is located do not meet the resource quota required for enabling microservice governance. The amount of resources meets the resource quota required for enabling microservice governance, and microservice governance is enabled in the application; resource deletion module 3 includes:

The deletable application judging unit 3.1 is used to detect whether there is a deletable low-priority application in the virtual data center where the application is located when the amount of resources available in the virtual data center where the application is located does not meet the resource quota required for enabling microservice governance;

The microservice governance opening unit 3.2 is used to enable microservice governance for the application when the amount of resources available in the virtual data center where the application is located satisfies the resource quota required for enabling microservice governance;

The low-priority application deletion unit 3.3 is configured to delete the low-priority application when there is a deletable low-priority application in the virtual data center where the application is located;

The user prompting unit 3.4 is used to prompt the user that the microservice management cannot be started due to insufficient resources when there is no deletable low-priority application in the virtual data center where the application is located.

Although the present invention has been described in detail in conjunction with preferred embodiments with reference to the accompanying drawings, the present invention is not limited thereto. Without departing from the spirit and essence of the present invention, those skilled in the art can make various equivalent modifications or replacements to the embodiments of the present invention, and these modifications or replacements should be within the scope of the present invention/any Those skilled in the art can easily think of changes or substitutions within the technical scope disclosed in the present invention, and all should be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims (4)

1. A method for verifying the opening of microservice governance quotas based on a localized cloud platform, characterized in that it comprises the following steps: S1. When the application needs to be enabled as microservice governance, count the resource quota required to enable microservice governance in the current environment; the specific steps are as follows: S11. When the application needs to enable microservice governance, traverse all the workloads of the current application in turn, and count the number of workload instances N; S12. Obtain the amount of resources M occupied by a single container of istio-proxy in the current environment by querying the configuration file; S13. Calculate the resource quota required for enabling microservice governance in the current environment S=the number of instances of the workload N*the amount of resources M occupied by a single container of istio-proxy; S2. Verify whether the amount of resources available in the virtual data center where the application is located satisfies the resource quota required for enabling microservice governance; the specific steps of step S2 are as follows: S21. Count all the workloads of the virtual data center where the application is located, count the total usage of the workload database, calculate the amount of available resources in the database, and check whether the amount of available resources in the database meets the resources required to start microservice governance; If so, go to step S22; If not, go to step S3; S22. Count the amount of resources occupied by the bottom layer of all workloads in the virtual data center where the application is located, calculate the amount of available resources at the bottom layer of the workload, and check whether the amount of available resources at the bottom layer of the workload meets the requirements for enabling micro-service management, and enter step S3; S3. When the amount of resources available in the virtual data center where the application is located does not meet the resource quota required for enabling microservice governance, delete the low-priority resources that can be deleted in the current virtual data center until the amount of available resources in the virtual data center where the application is located meets the requirements for enabling microservice governance. For the resource quota required for service governance, enable microservice governance in the application; the specific steps of step S3 are as follows: S31. When the amount of resources available in the virtual data center where the application is located does not meet the resource quota required for enabling microservice governance, enter step S32; When the amount of resources available in the virtual data center where the application is located satisfies the resource quota required for enabling microservice governance, enter step S33; S32. Detect whether there is a deletable low-priority application in the virtual data center where the application is located; If yes, delete the low-priority application and return to step S21; If not, prompt the user that resources are insufficient and microservice management cannot be enabled, and end; S33. Enable microservice governance for the application. 2. The method for verifying the opening of microservice governance quotas based on a localized cloud platform as claimed in claim 1, characterized in that in step S11, when a certain workload has elastic scaling resources, the scaling resource The maximum number of instances serves as the number of instances for this workload. 3. The method for verifying the opening of microservice governance quotas based on the localized cloud platform as claimed in claim 1, wherein, in step S12, the CPU and the occupied CPU of the istio-proxy single container of the current environment are obtained by querying the configuration file amount of memory resources; In step S13, the resource quota S required to enable microservice governance in the current environment includes the total required CPU usage S1 and the required total memory usage S2; Total required CPU usage S1=Number of workload instances N*CPU usage M1 occupied by a single container of istio-proxy; Total required memory usage S2 = number of workload instances N * memory usage M2 occupied by a single container of istio-proxy. 4. A device for verifying the opening of microservice governance quotas based on a localized cloud platform, characterized in that it includes: The required resource quota statistics module (1) is used to count the resource quotas required to enable microservice governance in the current environment when the application needs to be started as microservice governance; the required resource quota statistics module (1) includes: The workload instance statistics unit (1.1) is used to traverse all the workloads of the current application in turn and count the number of workload instances N when the application needs to enable microservice governance; Single container resource occupation query unit (1.2), which is used to obtain the amount of resources M occupied by a single container of istio-proxy in the current environment by querying the configuration file; The required resource quota calculation unit (1.3) is used to calculate the resource quota required for enabling microservice governance in the current environment S=number of workload instances N*istio-proxy resources occupied by a single container M; The resource verification module (2) is used to verify whether the amount of resources available in the virtual data center where the application is located satisfies the resource quota required for enabling microservice governance; the resource verification module (2) includes: The database resource verification unit (2.1) is used to count all the workloads of the virtual data center where the application is located, count the total usage of the workload database, calculate the amount of available resources in the database, and verify whether the amount of available resources in the database meets the requirements of opening Resources required for microservice governance; The underlying resource verification unit (2.2) is used to count the amount of resources occupied by the underlying resources of all workloads in the virtual data center where the application is located, calculate the amount of available resources at the underlying layer of the workload, and verify whether the amount of available resources at the underlying layer of the workload meets the requirements for starting microservices governance; The resource deletion module (3), used to delete the low-priority deletable resources of the current virtual data center until the virtual data center where the application resides The amount of available resources meets the resource quota required to enable microservice governance, and enable microservice governance in the application; the resource deletion module (3) includes: The deletable application judgment unit (3.1) is used to detect whether there is a deletable low-priority application in the virtual data center where the application is located when the amount of resources available in the virtual data center where the application is located does not meet the resource quota required for enabling microservice governance; The microservice governance enabling unit (3.2) is used to enable microservice governance for the application when the amount of resources available in the virtual data center where the application is located satisfies the resource quota required for enabling microservice governance; The low-priority application deletion unit (3.3) is used to delete the low-priority application when there is a deletable low-priority application in the virtual data center where the application is located; The user prompt unit (3.4) is used to prompt the user that resources are insufficient and microservice management cannot be enabled when there is no deletable low-priority application in the virtual data center where the application is located.

Images