CN113452776B

CN113452776B - PaaS platform service scheduling method and device and PaaS platform

Info

Publication number: CN113452776B
Application number: CN202110713429.5A
Authority: CN
Inventors: 朱婷婷; 方骅; 杨子超; 杨一鸣
Original assignee: Industrial and Commercial Bank of China Ltd ICBC
Current assignee: Industrial and Commercial Bank of China Ltd ICBC
Priority date: 2021-06-25
Filing date: 2021-06-25
Publication date: 2022-12-09
Anticipated expiration: 2041-06-25
Also published as: CN113452776A

Abstract

The embodiment of the application provides a PaaS platform service scheduling method, a PaaS platform service scheduling device and a PaaS platform, which can be used in the technical field of cloud computing, and the method comprises the following steps: determining a switch opening state and a whole-region popularization state corresponding to a target service identifier in a PaaS platform based on a service gray switch of a non-gray container preset in the PaaS platform according to the target service identifier corresponding to a service deployment request aiming at the PaaS platform; and if the switch opening state and the all-region popularization state corresponding to the target service identification are both displayed to be opened, sending a service deployment request to a gray-scale container to call the corresponding gray-scale service, wherein the gray-scale container is pre-deployed in the PaaS platform based on the same configuration of the non-gray-scale container. The method and the device can effectively improve the reliability and efficiency of the PaaS platform service scheduling, reduce the change scale and the backspacing operation risk of the PaaS platform caused by service change, and improve the service continuity in the PaaS platform service scheduling process.

Description

PaaS platform service scheduling method and device and PaaS platform

Technical Field

The application relates to the technical field of data processing, in particular to the technical field of cloud computing, and specifically relates to a PaaS platform service scheduling method and device and a PaaS platform.

Background

The Platform as a Service (PaaS) is a cloud computing Service mode, in a typical hierarchy of cloud computing, a Platform as a Service layer is between a software as a Service (SaaS) and an infrastructure as a Service (IaaS), and a software environment which is dependent on application running is targeted to be solved, and the software environment comprises middleware, an application framework and the like, so that the development and operation and maintenance mode is greatly simplified.

In the PaaS platform application, a PaaS platform application process serves as a service provider, and services are registered on a virtual server through a PaaS container so as to provide services for a consumer. When the service version is modified and upgraded, the current PaaS container needs to be stopped, the latest PaaS mirror image in the remote mirror image warehouse needs to be pulled, and a new PaaS container needs to be started to realize the operation, wherein the PaaS mirror image comprises the program, the configuration and the operation environment of the whole application. Since the mirror image needs to be updated every time of service upgrade, that is, upgrade of the PaaS application is full, all services need to be redeployed as long as one service is changed. Therefore, if the current reconstruction has a great defect and needs to be backed off immediately, the full-scale back-off is needed, the risk of back-off operation is high, and the business continuity is influenced in the back-off process.

Disclosure of Invention

Aiming at the problems in the prior art, the application provides a PaaS platform service scheduling method, device and platform, which can effectively improve the reliability and efficiency of the PaaS platform service scheduling, can effectively reduce the change scale of the PaaS platform caused by service change, can effectively reduce the rollback operation risk in the PaaS platform service scheduling process, and improve the service continuity in the PaaS platform service scheduling process.

In order to solve the technical problem, the application provides the following technical scheme:

in a first aspect, the present application provides a PaaS platform service scheduling method, including:

determining a switch opening state and a whole-region popularization state corresponding to a target service identifier in a PaaS platform based on a service gray switch of a non-gray container preset in the PaaS platform according to the target service identifier corresponding to a service deployment request of the PaaS platform;

and if the switch opening state and the all-region popularization state corresponding to the target service identification are both displayed to be opened, sending the service deployment request to a gray container to call the corresponding gray service, wherein the gray container is pre-deployed in the PaaS platform based on the same configuration of the non-gray container.

Further, still include:

if the switch opening state corresponding to the target service identification is opened and the all-region promotion state corresponding to the target service identification is not opened, acquiring target keyword information corresponding to the service deployment request;

and searching whether the target keyword information is contained in a preset keyword white list, and if so, sending the service deployment request to a gray level container to call the corresponding gray level service.

Further, the keyword white list comprises a region white list and a user white list which are pre-stored locally in a non-gray container; the target keyword information comprises a target region identifier and a target user identifier corresponding to the service deployment request;

correspondingly, the step of searching whether the preset keyword white list contains the target keyword information or not, and if yes, sending the service deployment request to a gray scale container to call the corresponding gray scale service includes:

searching whether the target area identifier is included in each area identifier stored in the area white list, and searching whether the target user identifier is included in each user identifier stored in the user white list;

and if the region white list contains the target region identification and/or if the user white list contains the target user identification, sending the service deployment request to a gray scale container to call corresponding gray scale service.

Further, before determining a switch-on state and a whole-region promotion state corresponding to the target service identifier in the PaaS platform based on a service grayscale switch of a non-grayscale container preset in the PaaS platform according to the target service identifier corresponding to the service deployment request for the PaaS platform, the method further includes:

judging whether a gray level strategy aiming at the PaaS platform is initialized, if so, judging whether a preset gray level main switch aiming at the PaaS platform is in an opened state;

and if the gray master switch is in an opened state, acquiring a target service identifier from a currently received service deployment request aiming at the PaaS platform.

Further, the determining, according to a target service identifier corresponding to a service deployment request for a PaaS platform, a switch-on state and a whole-region promotion state corresponding to the target service identifier in the PaaS platform based on a service grayscale switch of a non-grayscale container preset in the PaaS platform includes:

calling a gray switch comparison table corresponding to a service gray switch prestored in a non-gray container local, wherein the gray switch comparison table is used for storing the corresponding relation among each service identifier, the switch opening state and the all-region popularization state;

and searching whether the service identification of the gray switch comparison table contains the target service identification, and if so, calling a switch opening state and a full-area popularization state of the target service identification corresponding to the gray switch comparison table.

Further, still include:

and if the switch opening state corresponding to the target service identification is not opened, sending the service deployment request to the non-gray scale container to call the corresponding non-gray scale service.

Further, still include:

if the gray-scale strategy aiming at the PaaS platform is not initialized or if a preset gray-scale main switch aiming at the PaaS platform is in an unopened state, the service deployment request is sent to the non-gray-scale container to call the corresponding non-gray-scale service.

In a second aspect, the present application provides a PaaS platform service scheduling apparatus, including:

the system comprises a switch application module, a service deployment module and a service deployment module, wherein the switch application module is used for determining a switch opening state and a whole-region popularization state corresponding to a target service identifier in a PaaS platform based on a service gray switch of a non-gray container preset in the PaaS platform according to the target service identifier corresponding to the service deployment request for the PaaS platform;

and the gray level scheduling module is used for sending the service deployment request to a gray level container to call the corresponding gray level service if the switch opening state and the all-region promotion state corresponding to the target service identification are both opened, wherein the gray level container is pre-deployed in the PaaS platform based on the same configuration of the non-gray level container.

In a third aspect, the present application provides a PaaS platform, including: a non-grayscale container and a grayscale container pre-deployed in the PaaS platform based on the same configuration of the non-grayscale container;

and a PaaS platform service scheduling device is arranged in the non-gray level container and is used for executing the PaaS platform service scheduling method.

In a fourth aspect, the present application provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the PaaS platform service scheduling method when executing the program.

In a fifth aspect, the present application provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the PaaS platform service scheduling method.

According to the technical scheme, the PaaS platform service scheduling method, the PaaS platform service scheduling device and the PaaS platform provided by the application comprise the following steps: determining a switch opening state and a whole-region popularization state corresponding to a target service identifier in a PaaS platform based on a service gray switch of a non-gray container preset in the PaaS platform according to the target service identifier corresponding to a service deployment request aiming at the PaaS platform; if the switch opening state and the all-region promotion state corresponding to the target service identifier are both displayed to be opened, the service deployment request is sent to a gray scale container to call the corresponding gray scale service, wherein the gray scale container is pre-deployed in the PaaS platform based on the same configuration of the non-gray scale container, the switch opening state and the all-region promotion state corresponding to the target service identifier in the PaaS platform are determined based on a preset service gray scale switch, the service deployment request is sent to the gray scale container to call the corresponding gray scale service, the effectiveness and the reliability of whether the gray scale service can be really provided for the service deployment request can be effectively improved, and the efficiency and the automation degree of providing the gray scale service for the service deployment request can be effectively improved, the method can effectively improve the reliability and efficiency of the PaaS platform service scheduling, gray-scale containers are pre-deployed in the PaaS platform based on the same configuration of non-gray-scale containers in the PaaS platform to provide gray-scale services for the PaaS platform, the change scale of the PaaS platform caused by service change can be effectively reduced, the rollback operation risk in the PaaS platform service scheduling process can be effectively reduced, the service continuity in the PaaS platform service scheduling process is improved, the problem of high risk of full rollback of PaaS architecture application is solved, the service continuity is ensured, the advantage of freely defining a route is also reserved, and the problems of system link extension and system performance limitation of the gray-scale release method are solved.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 is a schematic structural diagram of a PaaS platform in an embodiment of the present application.

Fig. 2 is a first flowchart of a PaaS platform service scheduling method in an embodiment of the present application.

Fig. 3 is a schematic flowchart of a second method for scheduling PaaS platform service in this embodiment.

Fig. 4 is a third flowchart of a PaaS platform service scheduling method in this embodiment.

Fig. 5 is a fourth flowchart illustrating a PaaS platform service scheduling method in an embodiment of the present application.

Fig. 6 is a fifth flowchart illustrating a PaaS platform service scheduling method in this embodiment.

Fig. 7 is a sixth flowchart illustrating a PaaS platform service scheduling method in an embodiment of the present application.

Fig. 8 is a seventh flowchart illustrating a PaaS platform service scheduling method in an embodiment of the present application.

Fig. 9 is a schematic structural diagram of a PaaS platform service scheduling apparatus in this embodiment.

Fig. 10 is a schematic diagram of an overall implementation architecture of a PaaS platform service scheduling method in an application example of the present application.

Fig. 11 is a technical framework diagram of a non-grayscale container in an application example of the present application.

Fig. 12 is a schematic diagram of a gray-scale service routing and scheduling flow in a PaaS platform service scheduling method in an application example of the present application.

Fig. 13 is a schematic structural diagram of an electronic device in an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application without making any creative effort belong to the protection scope of the present application.

It should be noted that the PaaS platform service scheduling method, device and PaaS platform disclosed in the present application can be used in the technical field of cloud computing, and can also be used in any field except the technical field of cloud computing.

In the PaaS platform application, a PaaS platform application process serves as a service provider, and services are registered on a virtual server through a PaaS container so as to provide services for a consumer. When the service version is modified and upgraded, the current PaaS container needs to be stopped, the latest PaaS mirror image in the remote mirror image warehouse needs to be pulled, and a new PaaS container needs to be started to realize the operation, wherein the PaaS mirror image comprises the program, the configuration and the operation environment of the whole application. Since the mirror image needs to be updated every time of service upgrade, that is, upgrade of the PaaS application is full, all services need to be redeployed as long as one service is changed. Therefore, if the immediate rollback is needed when the expected modification has a great defect, the full rollback is needed, the rollback operation risk is high, and the business continuity is influenced in the rollback process.

Based on this, the gray scale release idea in the IT architecture is considered to be applied to solve the problem, and there are three kinds of gray scales of a code logic layer, a network or WEB layer, and a freely defined routing gray scale. The gray level of the code logic layer is that new and old codes are deployed in the same set of application server, and the system stability is not well optimized; the new and old codes are deployed in different application servers by the network or WEB layer gray scale, but the loads of the network server and the WEB server are increased, and complex gray scale rules are not supported; the method can realize more complex gray rule, but prolongs system processing link, influences system processing performance, and increases consumption of server resources. The three methods have merits and disadvantages respectively, and the third method is most widely applied.

That is, even if the above-described grayscale distribution method is applied to the PaaS platform, the problem that the system link of the grayscale distribution process is extended and the system performance is limited in the PaaS platform service scheduling process may occur.

Therefore, aiming at the problems that the efficiency of the PaaS platform service scheduling is low, the change is large, the backspacing operation risk is high, the service continuity is influenced in the backspacing process and the like caused by the service change of the existing PaaS platform service scheduling mode, the embodiment of the application respectively provides a PaaS platform service scheduling method, a PaaS platform service scheduling device, a PaaS platform and an electronic equipment computer readable storage medium, and according to a target service identifier corresponding to a service deployment request of the PaaS platform and based on a service gray switch of a non-gray container preset in the PaaS platform, a switch opening state and a whole-area popularization state corresponding to the target service identifier in the PaaS platform are determined; if the switch-on state and the all-region promotion state corresponding to the target service identifier are both displayed to be on, the service deployment request is sent to a gray-scale container to call the corresponding gray-scale service, wherein the gray-scale container is pre-deployed in the PaaS platform based on the same configuration of the non-gray-scale container, the switch-on state and the all-region promotion state corresponding to the target service identifier in the PaaS platform are determined based on a preset service gray-scale switch, the service deployment request is sent to the gray-scale container to call the corresponding gray-scale service, effectiveness and reliability of whether the gray-scale service can be provided to the service deployment request or not can be effectively improved, efficiency and automation degree of providing the gray-scale service to the service deployment request can be effectively improved, reliability and efficiency of PaaS platform service scheduling can be effectively improved, the gray-scale service can be provided to the PaaS platform based on the same configuration of the non-gray-scale container in the PaaS platform to be pre-deployed in the PaaS platform to provide the gray-scale service to the PaaS platform, and the gray-scale service deployment request can be effectively changed, and the problem of continuous operation of a PaaS system backspacing process is solved, and the problem of a high-level service backspacing system is solved, and the problem of a high-back-off risk problem of a high-line service is solved.

In one or more embodiments of the present application, both the non-grayscale container and the grayscale container may be a server or a server cluster in the PaaS platform.

In one or more embodiments of the application, a grayscale container is added on the basis of the prior art to separately deploy a grayscale mirror, so as to form a mode in which a non-grayscale container and a grayscale container in a PaaS platform provide services to the outside jointly. The deployment and the configuration of the gray level container are completely the same as those of the original non-gray level container, the difference between the deployment and the configuration of the gray level container and those of the original non-gray level container is that the gray level modification content is newly added in the gray level container, and in the mode, compared with the non-gray level container, the PaaS platform service scheduling device is added. The PaaS platform service scheduling device may be an independent server, or may be a functional module in a non-grayscale container in the PaaS platform, for example, a grayscale router gray router, or the like.

Based on the above content, the present application further provides a PaaS platform for implementing the PaaS platform service scheduling method provided in one or more embodiments of the present application, where, referring to fig. 1, the PaaS platform includes a non-grayscale container and a grayscale container, the non-grayscale container is provided with a PaaS platform service scheduling device, the PaaS platform service scheduling device may be in communication connection with a client device outside the PaaS platform by itself or through a third-party server or the like, and is configured to receive a service deployment request for the PaaS platform sent by the client device, where the service deployment request for the PaaS platform includes a service identifier for representing a unique identifier of a service deployment type for the PaaS platform, and determines the service identifier as a current target service identifier, such as a113, when the service deployment request is processed; the service deployment request for the PaaS platform may further include target keyword information corresponding to the target service identifier, and may include key information such as a region and a user identifier that request execution of service deployment, for example, a certain service deployment request for the PaaS platform includes "service identifier: a113, area identification: shanghai, user identification: USER13235", and the like.

In addition, after the PaaS platform service scheduling device sends the service deployment request to the grayscale container to call the corresponding grayscale service or sends the service deployment request to the service deployment module of the non-grayscale container where the PaaS platform service scheduling device is located or the service deployment modules of other non-grayscale containers, the service deployment result information sent by the service deployment module of the grayscale container or the non-grayscale container can be received, and the service deployment result information is sent to the client device to be displayed and informed, so that a user who sends the service deployment request can timely and intuitively know information such as service deployment conditions.

It is understood that the client devices may include smart phones, tablet electronic devices, network set-top boxes, portable computers, desktop computers, personal Digital Assistants (PDAs), in-vehicle devices, smart wearable devices, and the like. Wherein, intelligence wearing equipment can include intelligent glasses, intelligent wrist-watch, intelligent bracelet etc..

In another practical application scenario, a part of the aforementioned PaaS platform service scheduling apparatus performing the PaaS platform service scheduling may be executed in the server as described above, or all operations may be completed in the client device. The selection may be specifically performed according to the processing capability of the client device, the limitation of the user usage scenario, and the like. This is not a limitation of the present application. If all the operations are completed in the client device, the client device may further include a processor for performing specific processing of the service data processing.

The client device may have a communication module (i.e., a communication unit) and may be communicatively connected to a remote server to implement data transmission with the server. The server may include a server on the task scheduling center side, and in other implementation scenarios, the server may also include a server on an intermediate platform, for example, a server on a third-party server platform that is communicatively linked to the task scheduling center server. The server may include a single computer device, or may include a server cluster formed by a plurality of servers, or a server structure of a distributed apparatus.

The server and the client device may communicate using any suitable network protocol, including network protocols not yet developed at the filing date of this application. The network protocol may include, for example, a TCP/IP protocol, a UDP/IP protocol, an HTTP protocol, an HTTPS protocol, or the like. Of course, the network Protocol may also include, for example, an RPC Protocol (Remote Procedure Call Protocol), a REST Protocol (Representational State Transfer Protocol), and the like used above the above Protocol.

The following embodiments and application examples are specifically and individually described in detail.

In order to solve the problems that the efficiency of PaaS platform service scheduling is low, the change is large, the rollback operation risk is high, the service continuity is affected in the rollback process and the like due to service change in the existing PaaS platform service scheduling method, an embodiment of a PaaS platform service scheduling method is provided in the present application, and referring to fig. 2, the PaaS platform service scheduling method executed by a PaaS platform service scheduling device specifically includes the following contents:

step 100: according to a target service identifier corresponding to a service deployment request of a PaaS platform, based on a service gray switch of a non-gray container preset in the PaaS platform, determining a switch opening state and a whole-region popularization state corresponding to the target service identifier in the PaaS platform.

In step 100, when a service consumer calls a service, the service consumer requests to default to a non-grayscale container in a PaaS platform application process, a PaaS platform service scheduling device in the non-grayscale container pulls a grayscale policy, and then service request routing and scheduling are performed according to the grayscale policy; then, in the following step 200, if the gray level strategy is satisfied, the service request is routed to the gray level container, and the gray level service is called; if the gray policy is not satisfied, the non-gray service is called.

Step 200: and if the switch opening state and the all-region popularization state corresponding to the target service identification are both displayed to be opened, sending the service deployment request to a gray container to call the corresponding gray service, wherein the gray container is pre-deployed in the PaaS platform based on the same configuration of the non-gray container.

In step 200, when a service needs to be modified and upgraded, the modified content of the service with higher business risk or larger rollback risk may be implemented on the grayscale mirror, instead of the corresponding modification on the grayscale mirror and the version before modification is retained. The PaaS framework isolates high-risk service transformation and low-risk service transformation, the high-risk service which is transformed in the present period is routed to the gray-scale container for processing through the gray-scale strategy, and the transformed low-risk service and the non-transformed service are directly processed in the non-gray-scale container. When the service on the rollback gray level mirror image is required to be modified, only the gray level strategy corresponding to the called service needs to be deleted, and the service request is not routed to the gray level container; i.e. directly processed by the non-greyscale container, i.e. invoking the service before modification. The rollback operation is simple, and the problem of full rollback in the prior art is also solved.

As can be seen from the above description, in the PaaS platform service scheduling method provided in the embodiment of the present application, the switch-on state and the all-region promotion state corresponding to the target service identifier in the PaaS platform are determined based on the preset service grayscale switch, and the service deployment request is sent to the grayscale container to call the corresponding grayscale service, so that effectiveness and reliability of whether to actually provide the grayscale service to the service deployment request can be effectively improved, and efficiency and automation degree of providing the grayscale service to the service deployment request can be effectively improved, and further reliability and efficiency of PaaS platform service scheduling can be effectively improved.

In order to further improve the intelligent degree and reliability of sending the service deployment request to the grayscale container to call the corresponding grayscale service, in an embodiment of the PaaS platform service scheduling method provided by the present application, referring to fig. 3, after step 100 in the PaaS platform service scheduling method, the following contents are further specifically included:

step 300: and if the switch opening state corresponding to the target service identifier is opened and the all-region promotion state corresponding to the target service identifier is not opened, acquiring target keyword information corresponding to the service deployment request.

Step 400: and searching whether the target keyword information is contained in a preset keyword white list, and if so, sending the service deployment request to a gray level container to call the corresponding gray level service.

As can be seen from the above description, according to the PaaS platform service scheduling method provided in the embodiment of the present application, when the switch-on state corresponding to the target service identifier is turned on and the global promotion state corresponding to the target service identifier is not turned on, whether the target keyword information is included in the preset keyword white list is searched for, so that the intelligent degree and reliability of sending the service deployment request to the grayscale container to invoke the corresponding grayscale service can be further improved, and the intelligent degree and reliability of the PaaS platform service scheduling can be further improved.

In order to further solve the problems of system link extension and limited system performance of the existing gray scale publishing method, in an embodiment of the PaaS platform service scheduling method provided by the present application, the keyword white list includes a regional white list and a user white list pre-stored locally in a non-gray scale container; the target keyword information comprises a target region identifier and a target user identifier corresponding to the service deployment request; referring to fig. 4, a step 400 in the PaaS platform service scheduling method specifically includes the following contents:

step 410: and searching whether the target area identifier is included in each area identifier stored in the area white list, and searching whether the target user identifier is included in each user identifier stored in the user white list.

Step 420: and if the region white list contains the target region identification and/or if the user white list contains the target user identification, sending the service deployment request to a gray scale container to call corresponding gray scale service.

Specifically, the service gray level routing keywords are divided into two categories, namely area keywords and user keywords, and the service gray level routing keywords can be specifically displayed as an area white list and a user white list. Therefore, the gray policy can be configured according to a combination of the service gray switch, the region white list, and the user white list.

It can be understood that the service gray switch comprises three parts of a service name, a switch state and whether the service is promoted in all regions, the region white list content is a region number, and the user white list is a user account.

As can be seen from the above description, in the PaaS platform service scheduling method provided in the embodiment of the present application, a set of grayscale policies composed of three dimensions of a service, a region, and a user is determined by a PaaS platform service scheduling device in a non-grayscale container, so as to implement routing and scheduling of non-grayscale and grayscale services. The gray level routing and scheduling are realized in a non-gray level container without configuring an independent routing container, so that the problems of high risk of full backspacing of PaaS framework application and service continuity are solved, the advantage of freely defining the routing is reserved, and the problems of system link extension and system performance limitation of the gray level release method are solved.

In order to provide an effective and reliable data basis for a subsequent grayscale service determination process, referring to fig. 5, an embodiment of a PaaS platform service scheduling method provided in the present application further includes the following steps before step 100 in the PaaS platform service scheduling method:

step 010: judging whether a gray scale strategy for the PaaS platform is initialized, if so, executing a step 020;

step 020: judging whether a preset gray level main switch for the PaaS platform is in an opened state or not;

if the gray-scale master switch is in an opened state, executing a step 030;

step 030: and acquiring a target service identifier from a currently received service deployment request aiming at the PaaS platform.

Specifically, in a specific example, the PaaS platform service scheduling apparatus may be a gray-scale router gray router, and three global variables may be predefined in the gray-scale router gray router: "globalproyflag", "service name + GrayFlag", "service name + RouteKey" respectively correspond to a gray level master switch, a service gray level switch, and a service gray level routing keyword (i.e. the keyword information or target keyword information mentioned in the embodiment of the present application) in the gray level policy, and the service gray level routing keyword is divided into a region keyword and a user keyword, and may be specifically displayed as a region white list and a user white list.

As can be seen from the above description, according to the PaaS platform service scheduling method provided in the embodiment of the present application, whether the PaaS platform can currently execute a process of providing gray scale service judgment is determined according to a gray scale policy initialization state and a preset gray scale master on-off state for the PaaS platform, so that an effective and reliable data basis can be provided for a subsequent gray scale service judgment process, the intelligent degree and reliability of sending the service deployment request to a gray scale container to call a corresponding gray scale service can be further improved, and the intelligent degree and reliability of the PaaS platform service scheduling can be further improved.

In order to further improve the efficiency and reliability of determining the switch-on state and the all-region promotion state corresponding to the target service identifier in the PaaS platform, in an embodiment of the PaaS platform service scheduling method provided by the present application, referring to fig. 6, step 100 in the PaaS platform service scheduling method specifically includes the following contents:

step 110: and calling a gray switch comparison table corresponding to the service gray switch prestored in the non-gray container local, wherein the gray switch comparison table is used for storing the corresponding relation among each service identifier, the switch opening state and the all-region popularization state.

Step 120: and searching whether the service identification of the gray switch comparison table contains the target service identification, and if so, calling a switch opening state and a full-area popularization state of the target service identification corresponding to the gray switch comparison table.

As can be seen from the above description, the PaaS platform service scheduling method provided in the embodiment of the present application can further improve the efficiency and reliability of determining the switch-on state and the all-region promotion state corresponding to the target service identifier in the PaaS platform by using the grayscale switch comparison table including the correspondence between each service identifier, the switch-on state, and the all-region promotion state, and further can further improve the intelligent efficiency and reliability of the PaaS platform service scheduling.

In order to further improve the reliability and the applicability comprehensiveness of the PaaS platform service scheduling, in an embodiment of the PaaS platform service scheduling method provided in the present application, referring to fig. 7, the following contents are further specifically included after step 100 in the PaaS platform service scheduling method:

step 500: and if the switch opening state corresponding to the target service identification is not opened, sending the service deployment request to the non-gray scale container to call the corresponding non-gray scale service.

As can be seen from the above description, according to the PaaS platform service scheduling method provided in the embodiment of the present application, when the switch on state corresponding to the target service identifier is not on, the service deployment request is sent to the non-grayscale container to invoke the corresponding non-grayscale service, so that the reliability and the application comprehensiveness of the PaaS platform service scheduling can be further improved, and further, the intelligent degree and the reliability of the PaaS platform service scheduling can be further improved.

In order to further improve the reliability and the applicability comprehensiveness of the PaaS platform service scheduling, in an embodiment of the PaaS platform service scheduling method provided by the present application, referring to fig. 8, the following contents are further specifically included after step 010 in the PaaS platform service scheduling method:

if it is determined that the gray scale strategy for the PaaS platform is not initialized in step 010, or if it is determined that the preset gray scale master switch for the PaaS platform is in an unopened state in step 020, step 600 is executed.

Step 600: if the gray-scale strategy aiming at the PaaS platform is not initialized or if a preset gray-scale main switch aiming at the PaaS platform is in an unopened state, the service deployment request is sent to the non-gray-scale container to call the corresponding non-gray-scale service.

As can be seen from the above description, according to the PaaS platform service scheduling method provided in the embodiment of the present application, when the grayscale policy for the PaaS platform is not initialized or the preset grayscale master switch for the PaaS platform is in the unopened state, the service deployment request is sent to the non-grayscale container to call the corresponding non-grayscale service, so that the reliability and the comprehensive applicability of the PaaS platform service scheduling can be further improved, and the intelligence degree and the reliability of the PaaS platform service scheduling can be further improved.

In terms of software, in order to solve the problems that service change in the existing PaaS platform service scheduling manner causes low efficiency, large change, high risk of rollback operation, and influence on service continuity during rollback, the present application provides an embodiment of a PaaS platform service scheduling apparatus for executing all or part of the contents in the PaaS platform service scheduling method, where reference is made to fig. 9, and the PaaS platform service scheduling apparatus specifically includes the following contents:

the switch application module 10 is configured to determine, according to a target service identifier corresponding to a service deployment request for a PaaS platform, a switch on state and a whole-region popularization state corresponding to the target service identifier in the PaaS platform based on a service grayscale switch of a non-grayscale container preset in the PaaS platform.

In the switch application module 10, when a service consumer calls a service, a request is sent to a non-grayscale container in a PaaS platform application process by default, a PaaS platform service scheduling device in the non-grayscale container pulls a grayscale policy, and then service request routing and scheduling are performed according to the grayscale policy; then in the following step 200, if the gray level strategy is satisfied, the service request is routed to the gray level container, and the gray level service is called; if the gray policy is not satisfied, the non-gray service is called.

And a grayscale scheduling module 20, configured to send the service deployment request to a grayscale container to invoke a corresponding grayscale service if both the switch-on state and the all-region promotion state corresponding to the target service identifier are already turned on, where the grayscale container is pre-deployed in the PaaS platform based on the same configuration of the non-grayscale container.

In the grayscale scheduling module 20, when a service needs to be modified and upgraded, the modified content of the service with a higher business risk or a higher rollback risk may be implemented on the grayscale mirror, instead of correspondingly modifying and retaining the version before modification on the grayscale mirror. The PaaS architecture isolates high-risk service transformation and low-risk service transformation, the high-risk service transformed in the current period is routed to a gray scale container for processing through a gray scale strategy, and the transformed low-risk service and the non-transformed service are directly processed in a non-gray scale container. When the service on the rollback gray level mirror image is required to be modified, only the gray level strategy corresponding to the called service needs to be deleted, and the service request is not routed to the gray level container; i.e. directly processed by the non-greyscale container, i.e. invoking the service before modification. The rollback operation is simple, and the difficulty of full rollback in the prior art is also avoided.

The embodiment of the PaaS platform service scheduling apparatus provided in the present application may be specifically configured to execute the processing flow of the embodiment of the PaaS platform service scheduling method in the foregoing embodiment, and the function of the embodiment is not described herein again, and reference may be made to the detailed description of the embodiment of the method.

As can be seen from the above description, the PaaS platform service scheduling apparatus provided in the embodiment of the present application determines, based on a preset service grayscale switch, a switch-on state and a full-area promotion state corresponding to the target service identifier in the PaaS platform, and sends the service deployment request to the grayscale container to call a corresponding grayscale service, so that effectiveness and reliability of whether to actually provide a grayscale service to the service deployment request can be effectively improved, and efficiency and automation degree of providing a grayscale service to the service deployment request can be effectively improved, and further reliability and efficiency of PaaS platform service scheduling can be effectively improved.

Based on the foregoing PaaS platform service scheduling apparatus, an embodiment of the present application further provides a PaaS platform, which specifically includes, referring to fig. 1, the following contents:

a non-grayscale container and a grayscale container pre-deployed in the PaaS platform based on the same configuration of the non-grayscale container; and a PaaS platform service scheduling device is arranged in the non-gray level container and is used for executing the PaaS platform service scheduling method.

On the basis that the PaaS platform comprises the non-gray-scale container, the gray-scale container is newly added to independently deploy the gray-scale mirror image, and a mode that the non-gray-scale container and the gray-scale container provide services to the outside jointly is formed. The deployment and the configuration of the gray-scale container are completely the same as those of the original non-gray-scale container, the difference between the deployment and the configuration is that gray-scale modification content is newly added in the gray-scale container, when a service consumer calls a service, the service consumer requests the non-gray-scale container which is sent to a PaaS platform application process in a default mode, a PaaS platform service scheduling device in the non-gray-scale container pulls a gray-scale strategy, then service request routing and scheduling are carried out according to the gray-scale strategy, and if the gray-scale strategy is met, the service request is routed to the gray-scale container, and the gray-scale service is called; if the gray strategy is not satisfied, the non-gray service is called.

The embodiment of the PaaS platform provided in the present application may be specifically configured to execute the processing flow of the embodiment of the PaaS platform service scheduling method and/or the embodiment of the PaaS platform service scheduling apparatus in the foregoing embodiment, and the functions of the embodiment are not described herein again, and reference may be made to the detailed description of the embodiment of the PaaS platform service scheduling method and/or the embodiment of the PaaS platform service scheduling apparatus.

As can be seen from the above description, in the PaaS platform provided in the embodiment of the present application, the switch-on state and the all-region promotion state corresponding to the target service identifier in the PaaS platform are determined based on the preset service grayscale switch, and the service deployment request is sent to the grayscale container to call the corresponding grayscale service, so that effectiveness and reliability of whether to actually provide the grayscale service to the service deployment request can be effectively improved, efficiency and automation degree of providing the grayscale service to the service deployment request can be effectively improved, and further, reliability and efficiency of scheduling the PaaS platform service can be effectively improved.

In order to further explain the scheme, the application also provides a specific application example of a PaaS platform service scheduling method realized by using a gray-scale router GrayRouter, which relates to the field of PaaS platforms, in particular to a PaaS architecture service continuity method based on gray-scale scheduling, and the application example provides the PaaS platform service scheduling method suitable for the PaaS architecture in order to solve the problems of high operation risk and service abnormity when the application process of the PaaS platform is completely returned, overcome the defects of the current gray-scale release method and fully play the advantages of the gray-scale release method. The novel PaaS application process architecture of the application example adds a gray level container on the basis of the original container, and both groups of containers provide services to the outside; and a gray level strategy consisting of three dimensions of service, region and user is judged by a gray level routing service class GrayRouter in the non-gray level container to realize the routing and scheduling of the non-gray level and gray level service. The gray level routing and scheduling are realized in a non-gray level container without configuring an independent routing container, so that the problems of high risk of full backspacing of PaaS framework application and service continuity are solved, the advantage of freely defining the routing is reserved, and the problems of system link extension and system performance limitation of the gray level release method are solved.

In the application example, a non-gray-scale PaaS container and gray-scale PaaS container combination mode is adopted in a PaaS application process architecture based on gray-scale scheduling, the non-gray-scale PaaS container is upgraded through a non-gray-scale PaaS mirror image, and the corresponding registered service is a non-gray-scale service; the gray-scale PaaS container is upgraded through a gray-scale PaaS mirror image, and the corresponding registered service is a gray-scale service; and acquiring a gray strategy and judging a route through the non-gray container to realize service scheduling of the non-gray container and the gray container.

The PaaS platform service scheduling method realized by the GrayRouter comprises the following contents:

integral realization framework of PaaS platform service scheduling method

Referring to fig. 10, in the application example of the present application, on the basis of the prior art, a grayscale container is newly added to separately deploy a grayscale mirror, and a mode in which a non-grayscale container and a grayscale container jointly provide a service to the outside is formed. The deployment and the configuration of the gray level container are completely the same as those of the original non-gray level container, the difference between the deployment and the configuration is that the gray level modification content is newly added in the gray level container, and the gray level router GrayRouter is added in the non-gray level container in the mode compared with the original non-gray level container.

Referring to the technical framework of the non-grayscale container shown in fig. 11, when a service consumer calls a service, the service consumer requests to default to the non-grayscale container in the PaaS platform application process, a grayscale router grayrrouter in the non-grayscale container will pull a grayscale policy, then service request routing and scheduling are performed according to the grayscale policy, and if the grayscale policy is satisfied, a service request is routed to the grayscale container, and a grayscale service is called; if the gray policy is not satisfied, the non-gray service is called.

Gray-scale service routing and scheduling process in PaaS platform service scheduling method

The gray-scale service routing and scheduling process in the PaaS platform service scheduling method based on gray-scale scheduling of the application example is realized in a gray-scale router GrayRouter. Three global variables are defined in GrayRouter:

the service gray level routing keywords are divided into two types, namely area keywords and user keywords, and can be specifically displayed as an area white list and a user white list. Therefore, the gray policy can be configured according to a combination of the service gray switch, the region white list, and the user white list.

The service gray switch comprises three parts of a service name, a switch state and whether the service is promoted in all regions, the content of a region white list is a region number, and a user white list is a user account.

Referring to fig. 12, a gray level service routing and scheduling flow in the paas platform service scheduling method is specifically as follows:

step 1: the gray level router GrayRouter determines whether the gray level strategy is initialized, so that an effective gray level strategy example can be obtained, and if the value is 'non null', the step 2 is continuously executed; if the transaction request is null, the transaction request is routed to a non-gray level container to be processed as a non-gray level policy, and a non-gray level service is called.

Step 2: checking whether a total gray switch Globalgray flag is in an open state, and if so, continuing to execute the step 3; if not, the transaction request is routed to a non-gray container for processing when the gray strategy is not met, and the non-gray service is called.

And step 3: checking whether a service gray switch 'service name + GrayFlag' is in an open state, and if so, continuing to execute the step 4; if not, the transaction request is routed to a non-gray container for processing and calling non-gray service when the gray strategy is not met.

And 4, step 4: matching the service name in the service gray switch, and if the matching is successful, continuing to execute the step 5; if not, the transaction request is routed to a non-gray container for processing and calling non-gray service when the gray strategy is not satisfied.

And 5: checking whether the called service gray is promoted in all regions, if the called service gray is promoted in all regions, not checking a white list, directly and remotely calling the gray service of a registration center, processing the service gray by a gray container, and calling the gray service; if the popularization is not comprehensive, the method continues.

Step 6: obtaining a routing keyword in a service gray level routing keyword 'service name + RouteKey', matching a region white list or a user white list, and if the matching is available, remotely calling a gray level service of a registration center; if the white list cannot be matched, the transaction request is routed to a non-gray container for processing, and a non-gray service is called.

In a specific example of gray level service routing and scheduling in the PaaS platform service scheduling method, the gray level policy is successfully matched, and a service request is routed to a gray level container for processing, which specifically comprises the following contents:

step 11, a service consumer sends a service calling request to a service provider, wherein the request comprises fixed format information such as a service name, a calling area, a user account and the like;

step 12, after receiving the request, the non-gray level container of the service provider is processed by some base classes and then reaches a gray level router GrayRouter of the non-gray level container;

and step 13, the gray level router GrayRouter acquires and matches a gray level strategy according to a gray level service route and a scheduling rule, judges that the 'GlobalGrayFlag' is opened, the 'service name + GrayFlag' is opened and is not comprehensive popularization, the service name is successfully matched, the 'service name + RouteKey' middle region white list is successfully matched, and finally the service request route is distributed to a gray level container for processing.

In another specific example of the gray level service routing and scheduling in the PaaS platform service scheduling method, the gray level policy matching fails, and the service request is processed by a non-gray level container, which specifically includes the following contents:

step 23: the gray level router GrayRouter acquires and matches a gray level strategy according to a gray level service routing and scheduling rule, judges whether GlobalGrayFlag is open, whether the service name + GrayFlag is open or not for comprehensive popularization, and if the service name matching is unsuccessful, the subsequent service name + RouteKey check is not performed any more, and finally the service request is processed by a non-gray level container.

In the PaaS framework based on gray-scale scheduling of the application example, when a service needs to be modified and upgraded, the modified content of the service with higher business risk or higher backspacing risk is realized on a gray-scale mirror image, but the version before modification is correspondingly modified and reserved on the non-gray-scale mirror image. The PaaS framework isolates high-risk service transformation and low-risk service transformation, the high-risk service which is transformed in the present period is routed to the gray-scale container for processing through the gray-scale strategy, and the transformed low-risk service and the non-transformed service are directly processed in the non-gray-scale container. When the service on the rollback gray level mirror image is required to be modified, only the gray level strategy corresponding to the called service needs to be deleted, and the service request does not need to be routed to a gray level container; i.e. directly processed by the non-greyscale container, i.e. invoking the service before modification. The rollback operation is simple, and the problem of full rollback in the prior art is also solved.

According to the application example, a PaaS architecture service continuity method based on gray level scheduling introduces a group of gray level containers on the basis of a group of normal containers in the prior art, and the two groups of containers provide services to the outside simultaneously. When a customer calls the service, the GrayRouter in the non-gray level container omits a route to the corresponding container according to the gray level policy, and calls the non-gray level service or the gray level service to process the customer request, so that the transaction request closed loop is realized.

According to the application example, the PaaS architecture service continuity method based on gray level scheduling realizes isolation of high-risk transformation, low-risk transformation and unmodified content. The grayscale container uses different images than the non-grayscale container, the grayscale container corresponds to the grayscale image, and the non-grayscale container corresponds to the non-grayscale image. The difference between the two mirrors is that high-risk service modifications are only implemented in grayscale mirroring, rather than in grayscale mirroring where such modifications remain as pre-modification versions. Therefore, when the high-risk service modification needs rollback, the gray strategy can be adjusted, the operation of restarting a container in the prior art is avoided, the full rollback of the service modification is also avoided, and the influence on the service continuity caused by manual misoperation or container restarting due to the rollback of the existing PaaS framework is greatly reduced. Meanwhile, the gray-scale service routing and scheduling method of the application example not only retains the advantages of the user-defined gray-scale routing, but also avoids the influence of performance reduction caused by the addition of routing server nodes to the user-defined routing.

In terms of hardware, in order to solve the problems of low efficiency, large change, high risk of rollback operation, influence on service continuity during rollback, and the like of PaaS platform service scheduling caused by service change in the existing PaaS platform service scheduling method, the present application provides an embodiment of an electronic device for implementing all or part of the contents in the PaaS platform service scheduling method, where the electronic device specifically includes the following contents:

fig. 13 is a schematic block diagram of a system configuration of an electronic device 9600 according to an embodiment of the present application. As shown in fig. 13, the electronic device 9600 can include a central processor 9100 and a memory 9140; the memory 9140 is coupled to the central processor 9100. Notably, this fig. 13 is exemplary; other types of structures may also be used in addition to or in place of the structure to implement telecommunications or other functions.

In an embodiment, the PaaS platform service scheduling functionality may be integrated into a central processor. Wherein the central processor may be configured to control:

As can be seen from the above description, in the electronic device provided in the embodiment of the present application, the switch-on state and the all-region promotion state corresponding to the target service identifier in the PaaS platform are determined based on the preset service grayscale switch, and the service deployment request is sent to the grayscale container to call the corresponding grayscale service, so that effectiveness and reliability of whether the grayscale service can be actually provided to the service deployment request can be effectively improved, efficiency and automation degree of providing the grayscale service to the service deployment request can be effectively improved, and further, reliability and efficiency of scheduling the PaaS platform service can be effectively improved.

In another embodiment, the PaaS platform service scheduling apparatus may be configured separately from the central processor 9100, for example, the PaaS platform service scheduling apparatus may be configured as a chip connected to the central processor 9100, and the PaaS platform service scheduling function may be implemented by the control of the central processor.

As shown in fig. 13, the electronic device 9600 may further include: a communication module 9110, an input unit 9120, an audio processor 9130, a display 9160, and a power supply 9170. It is noted that the electronic device 9600 also does not necessarily include all of the components shown in fig. 13; in addition, the electronic device 9600 may further include components not shown in fig. 13, which can be referred to in the prior art.

As shown in fig. 13, the central processor 9100, which is sometimes referred to as a controller or operational control, can include a microprocessor or other processor device and/or logic device, the central processor 9100 receives input and controls the operation of the various components of the electronic device 9600.

The memory 9140 can be, for example, one or more of a buffer, a flash memory, a hard drive, a removable media, a volatile memory, a non-volatile memory, or other suitable device. The information relating to the failure may be stored, and a program for executing the information may be stored. And the central processing unit 9100 can execute the program stored in the memory 9140 to realize information storage or processing, or the like.

The input unit 9120 provides input to the central processor 9100. The input unit 9120 is, for example, a key or a touch input device. The power supply 9170 is used to provide power to the electronic device 9600. The display 9160 is used for displaying display objects such as images and characters. The display may be, for example, an LCD display, but is not limited thereto.

The memory 9140 can be a solid state memory, e.g., read Only Memory (ROM), random Access Memory (RAM), a SIM card, or the like. There may also be a memory that holds information even when power is off, can be selectively erased, and is provided with more data, an example of which is sometimes called an EPROM or the like. The memory 9140 could also be some other type of device. The memory 9140 includes a buffer memory 9141 (sometimes referred to as a buffer). The memory 9140 may include an application/function storage portion 9142, the application/function storage portion 9142 being used for storing application programs and function programs or for executing a flow of operations of the electronic device 9600 by the central processor 9100.

The memory 9140 can also include a data store 9143, the data store 9143 being used to store data, such as contacts, digital data, pictures, sounds, and/or any other data used by an electronic device. The driver storage portion 9144 of the memory 9140 may include various drivers for the electronic device for communication functions and/or for performing other functions of the electronic device (e.g., messaging applications, contact book applications, etc.).

The communication module 9110 is a transmitter/receiver 9110 that transmits and receives signals via an antenna 9111. The communication module (transmitter/receiver) 9110 is coupled to the central processor 9100 to provide input signals and receive output signals, which may be the same as in the case of a conventional mobile communication terminal.

A plurality of communication modules 9110, such as a cellular network module, a bluetooth module, and/or a wireless local area network module, can be provided in the same electronic device based on different communication technologies. The communication module (transmitter/receiver) 9110 is also coupled to a speaker 9131 and a microphone 9132 via an audio processor 9130 to provide audio output via the speaker 9131 and receive audio input from the microphone 9132, thereby implementing ordinary telecommunications functions. The audio processor 9130 may include any suitable buffers, decoders, amplifiers and so forth. In addition, the audio processor 9130 is also coupled to the central processor 9100, thereby enabling recording locally through the microphone 9132 and enabling locally stored sounds to be played through the speaker 9131.

An embodiment of the present application further provides a computer-readable storage medium capable of implementing all steps in the PaaS platform service scheduling method in the foregoing embodiment, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements all steps of the PaaS platform service scheduling method whose execution subject is a server or a client in the foregoing embodiment, for example, when the processor executes the computer program, the processor implements the following steps:

step 100: according to a target service identification corresponding to a service deployment request of a PaaS platform, based on a service gray switch of a non-gray container preset in the PaaS platform, determining a switch opening state and a whole-region popularization state corresponding to the target service identification in the PaaS platform.

Step 200: and if the switch opening state and the all-region promotion state corresponding to the target service identification are both displayed to be opened, sending the service deployment request to a gray level container to call the corresponding gray level service, wherein the gray level container is pre-deployed in the PaaS platform based on the same configuration of the non-gray level container.

As can be seen from the above description, in the computer-readable storage medium provided in the embodiment of the present application, the switch-on state and the all-region promotion state corresponding to the target service identifier in the PaaS platform are determined based on the preset service grayscale switch, and the service deployment request is sent to the grayscale container to call the corresponding grayscale service, so that effectiveness and reliability of whether to actually provide the grayscale service to the service deployment request can be effectively improved, efficiency and automation degree of providing the grayscale service to the service deployment request can be effectively improved, and further, reliability and efficiency of scheduling the PaaS platform service can be effectively improved.

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, apparatus, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein. The present invention has been described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (devices), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks. These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

The principle and the implementation mode of the invention are explained by applying specific embodiments in the invention, and the description of the embodiments is only used for helping to understand the method and the core idea of the invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, the specific embodiments and the application range may be changed, and in summary, the content of the present specification should not be construed as a limitation to the present invention.

Claims

1. A PaaS platform service scheduling method is characterized by comprising the following steps:

if the switch opening state and the all-region popularization state corresponding to the target service identification are both displayed to be opened, sending the service deployment request to a gray container to call corresponding gray level service, wherein the gray container is pre-deployed in the PaaS platform based on the same configuration of the non-gray container;

further comprising:

2. The PaaS platform service scheduling method of claim 1, wherein the keyword white list comprises a regional white list and a user white list pre-stored locally in a non-grayscale container; the target keyword information comprises a target region identifier and a target user identifier corresponding to the service deployment request;

correspondingly, the step of searching whether the target keyword information is included in the preset keyword white list, and if yes, sending the service deployment request to a gray scale container to call a corresponding gray scale service includes:

searching whether each area identifier stored in the area white list contains the target area identifier or not, and searching whether each user identifier stored in the user white list contains the target user identifier or not;

3. The PaaS platform service scheduling method according to claim 1, wherein before determining a switch-on state and a whole-region promotion state corresponding to a target service identifier in a PaaS platform based on a service grayscale switch of a non-grayscale container preset in the PaaS platform according to the target service identifier corresponding to a service deployment request for the PaaS platform, the method further comprises:

judging whether a gray scale strategy aiming at the PaaS platform is initialized, if so, judging whether a preset gray scale main switch aiming at the PaaS platform is in an opened state;

4. The PaaS platform service scheduling method according to claim 1, wherein the determining of the switch-on state and the whole-region promotion state corresponding to the target service identifier in the PaaS platform based on a service gray-scale switch of a non-gray-scale container preset in the PaaS platform according to the target service identifier corresponding to the service deployment request for the PaaS platform comprises:

and searching whether the target service identification is included in each service identification of the gray switch comparison table, and if so, calling a switch opening state and a full-area popularization state of the target service identification corresponding to the gray switch comparison table.

5. The PaaS platform service scheduling method according to claim 1, further comprising:

and if the switch opening state corresponding to the target service identification is not opened, sending the service deployment request to the non-gray level container to call the corresponding non-gray level service.

6. The PaaS platform service scheduling method of claim 1, further comprising:

if the gray scale strategy for the PaaS platform is not initialized, or if a preset gray scale main switch for the PaaS platform is in an unopened state, the service deployment request is sent to the non-gray scale container to call the corresponding non-gray scale service.

7. A PaaS platform service scheduling device is characterized by comprising:

the system comprises a switch application module, a service deployment request module and a service deployment management module, wherein the switch application module is used for determining a switch opening state and a whole-region popularization state corresponding to a target service identifier in a PaaS platform based on a service gray switch of a non-gray container preset in the PaaS platform according to the target service identifier corresponding to the service deployment request aiming at the PaaS platform;

the gray scheduling module is used for sending the service deployment request to a gray container to call a corresponding gray service if the switch opening state and the all-region popularization state corresponding to the target service identification are both opened, wherein the gray container is pre-deployed in the PaaS platform based on the same configuration of the non-gray container;

the apparatus is further configured to:

8. A PaaS platform, comprising: a non-grayscale container and a grayscale container pre-deployed in the PaaS platform based on the same configuration of the non-grayscale container;

the non-gray scale container is provided with a PaaS platform service scheduling device, and the PaaS platform service scheduling device is used for executing the PaaS platform service scheduling method of any one of claims 1 to 6.

9. An electronic device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor implements the PaaS platform service scheduling method of any of claims 1 to 6 when executing the computer program.

10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, implements the PaaS platform service scheduling method according to any one of claims 1 to 6.