CN112468463B - Device and method for arranging scene capacity based on cloud native capacity gateway - Google Patents
Device and method for arranging scene capacity based on cloud native capacity gateway Download PDFInfo
- Publication number
- CN112468463B CN112468463B CN202011275416.6A CN202011275416A CN112468463B CN 112468463 B CN112468463 B CN 112468463B CN 202011275416 A CN202011275416 A CN 202011275416A CN 112468463 B CN112468463 B CN 112468463B
- Authority
- CN
- China
- Prior art keywords
- scene
- capability
- capacity
- gateway
- script
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/34—Graphical or visual programming
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0807—Network architectures or network communication protocols for network security for authentication of entities using tickets, e.g. Kerberos
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/104—Peer-to-peer [P2P] networks
- H04L67/1074—Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
Abstract
The invention relates to a device and a method for arranging scene capacity based on a cloud native capacity gateway.A user configures and stores a scene capacity arrangement script through a console; configuring scene capacity by a user, and associating the scene capacity with the editing script; a user starts a scene capacity service module and informs a container arrangement engine to load a scene capacity service; the scene capability service module is initialized according to the scene capability configuration; the external application initiates scene capability calling through a capability gateway; the capability gateway calls an authentication center module to authenticate the initiated scene capability; after the authentication is passed, the capability gateway calls a scene capability service module; the scene capacity service module carries out air conditioner expansion and contraction capacity according to the load of the external application request and maps corresponding atomic capacity service according to the arrangement script; and finally, returning the calling result of the atomic capability in the arrangement flow and returning the calling result to the application. The invention is realized through the script, and the atomic capability can be arranged into the scene capability without a hard coding mode.
Description
Technical Field
The invention relates to the technical field of communication and internet, in particular to a device and a method for arranging scene capacity based on a cloud native capacity gateway.
Background
With the rapid development of the communication and internet industries, nowadays more and more enterprises build middleboxes to support application innovation with rapid response to business demands. The capability gateway is an important component of the middle station, the capability gateway realizes the functions of request routing, calling authentication, current limiting and the like, and the front-end application completes data interaction by calling the API of the capability gateway.
Most of the current capability gateways are realized based on open-source micro-service frameworks (Spring Cloud, dubbo, etc.). Different micro services have different URL addresses, and one micro service generally provides API capabilities of a plurality of atoms, for example, in an operator equity marketing scene, one equity exchange may call equity recommendation micro services, equity acceptance micro services, payment micro services, equity exchange micro services and the like. Therefore, the front-end application needs to interact with the capability gateway for many times, sequential logic call relations exist among the micro services, and even functions such as parameter verification, parameter mapping and the like are involved.
The capability gateway realized based on Spring Cloud and Dubbo frames can not realize dynamic elastic expansion for high concurrency scenes, has single supported service type, generally realizes synchronous remote calling, and does not support service calling of method type, condition type, cycle type and the like.
The prior art generally has the following problems:
only the atomic API capability is realized, and the capability arrangement adopts a hard coding mode or a newly added capability adaptation mode;
the capability type is single, only synchronous remote service nodes are supported, and conditional nodes and cycle nodes are not supported;
micro-services are generally realized based on Spring Cloud or Dubbo architecture, and lack elastic expansion and contraction capability;
the editing process is generally stored based on a file mode, and the updating or reading performance is low.
Disclosure of Invention
In view of this, the present invention provides a device and a method for editing scene capabilities based on a cloud native capability gateway, which can implement the editing of atomic capabilities into scene capabilities through a script without a hard coding manner.
The invention is realized by adopting the following scheme: a scene capability arranging device based on a cloud native capability gateway comprises a capability gateway, an authentication center module, a scene capability service module, a console, a scene capability arranging script warehouse and a scene capability script; a user performs scene capability arrangement based on atomic capability through the console to generate an arrangement script, calls a scene capability script warehouse for updating, and initializes the scene capability service module; the external application calls the scene capacity request to reach the capacity gateway, the capacity gateway uniformly accesses all the capacity calls to the capacity gateway, and the gateway layer is responsible for accessing and outputting; then the capability gateway calls an authentication center module to realize capability generation Token, verification Token, calling authentication and access control through the authentication center module; after the authentication center module passes the authentication, a scene capability service module is called, the scene capability service module realizes the scene capability through script arrangement, and the new scene capability is brought into the capability gateway again for management; and the scene capability service module calls the atomic capability according to the editing script and finally returns the atomic capability to the application side.
Further, the invention also provides a method for arranging the scene capacity based on the cloud native capacity gateway, which comprises the following steps:
step S1: a user configures and stores a scene capacity arranging script through a control console and informs a scene capacity arranging script warehouse;
step S2: configuring scene capacity by a user, and associating the scene capacity with the editing script;
and step S3: a user starts a scene ability service module and informs a container arrangement engine to load the scene ability service;
and step S4: the scene ability service module is initialized according to the scene ability configuration;
step S5: initiating scene capability calling by an external application through a capability gateway;
step S6: the capability gateway calls an authentication center module to authenticate the initiated scene capability;
step S7: after the authentication is passed, the capability gateway calls a scene capability service module;
step S8: the scene capacity service module performs dynamic expansion and contraction capacity according to the load of the external application request;
step S9: the scene capacity service module maps corresponding atomic capacity services according to the editing script and calls a plurality of atomic capacity services;
step S10: and finally, calling a plurality of atomic capabilities in the step S9 of the arranging flow, and returning the result of calling the plurality of atomic capabilities to the external application.
Further, the specific process of starting the scene capability service and the dynamic scaling is as follows:
step Sa, the administrator logs on the console to start the newly added scene ability;
step Sb, the console initiates an application deployment instruction to the k8s cluster ApiServer through the API;
the K8s cluster pulls a scene capacity service mirror image from a mirror image warehouse and starts a scene capacity service;
the capability gateway receives the application to initiate the scene capability call, finally requests to route to the scene capability, the scene capability executes the arranging process according to the scene script warehouse, and returns the scene capability call result to the external application;
and step Se, when the external application calls the scene capacity load to be higher, K8S carries out dynamic expansion and contraction capacity aiming at the scene capacity service according to the load and the expansion and contraction capacity configuration strategy.
Further, the specific content of the dynamic scaling in step Se is as follows:
the K8S platform regularly checks whether indexes monitored by the scene capacity service pods exceed a set threshold, and once a stretching condition is triggered, the indexes exceed the set threshold, a request is sent to K8S to modify the number of the pods running the scene capacity service; k8s responds to the request, and then refreshes the pod number of the telescopic object once; after the telescopic object is modified, the number of the posts can be increased or reduced through a list/watch mechanism, and the purpose of dynamic telescopic is achieved; otherwise, no action is taken.
Compared with the prior art, the invention has the following beneficial effects:
(1) The invention realizes the capability of arranging the atomic capability into the scene capability without a hard coding mode through the script.
(2) The present invention supports multiple node types including: conditional nodes, cyclic nodes, etc.
(3) The invention realizes the scene capacity based on kubernets and can elastically expand and contract the capacity according to the load.
(4) The invention is based on a distributed cache editing script warehouse, and meets the high concurrency scene.
Drawings
FIG. 1 is a schematic diagram of an embodiment of the present invention.
FIG. 2 is a data model diagram of a scenario capability service according to an embodiment of the present invention.
FIG. 3 is a flowchart illustrating a scenario capability arrangement process according to an embodiment of the present invention.
Fig. 4 is a flowchart illustrating a scenario capability execution according to an embodiment of the present invention.
FIG. 5 is a timing diagram of the new scene capability according to an embodiment of the present invention.
FIG. 6 is a timing diagram illustrating the start-up scene capability and dynamic scalability according to an embodiment of the present invention.
Detailed Description
The invention is further explained by the following embodiments in conjunction with the drawings.
It should be noted that the following detailed description is exemplary and is intended to provide further explanation of the disclosure. Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs.
It is noted that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments according to the present application. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, and it should be understood that when the terms "comprises" and/or "comprising" are used in this specification, they specify the presence of stated features, steps, operations, devices, components, and/or combinations thereof, unless the context clearly indicates otherwise.
As shown in fig. 1, the present embodiment provides a device for editing scene capabilities based on a cloud native capability gateway, including a capability gateway, an authentication center module, a scene capability service module, a console, a scene capability editing script warehouse, and a scene capability script; a user performs scene capability arrangement based on atomic capability through the console to generate an arrangement script, calls a scene capability script warehouse for updating, and initializes the scene capability service module; the external application calls a scene capacity request to reach a capacity gateway, the capacity gateway uniformly accesses all the capacity calls to the capacity gateway, and a gateway layer is responsible for accessing and outputting; then the capability gateway calls an authentication center module to realize capability generation Token, verification Token, calling authentication and access control through the authentication center module; after the authentication center module passes the authentication, a scene capability service module is called, the scene capability service module realizes the scene capability through script arrangement, and the new scene capability is brought into the capability gateway again for management; and the scene capability service module calls the atomic capability according to the editing script and finally returns the atomic capability to the application side.
The control console is used for providing a visual process editing interface (a web interface can be dragged and arranged), an arranging script is generated after arranging is finished, and a scene capability script warehouse is called for updating; the scene capacity editing script warehouse is used for providing script version management, uniformly updating and storing the scene capacity scripts and loading the distributed cache; the scenario capability script is used for describing the atomic capability, capability type and calling flow of which the scenario capability is arranged by.
Preferably, the embodiment further provides a method for arranging the scene capability based on the cloud native capability gateway, which includes the following steps:
step S1: a user configures and stores a scene capacity arranging script through a control console and informs a scene capacity arranging script warehouse;
step S2: configuring scene capacity by a user, and associating the scene capacity with the editing script;
and step S3: a user starts a scene capacity service module and informs a container arrangement engine to load a scene capacity service;
and step S4: the scene capability service module is initialized according to the scene capability configuration;
step S5: initiating scene capability calling by an external application through a capability gateway;
step S6: the capability gateway calls an authentication center module to authenticate the initiated scene capability;
step S7: after the authentication is passed, the capability gateway calls a scene capability service module;
step S8: the scene capacity service module performs dynamic expansion and contraction capacity according to the load of the external application request;
step S9: the scene capacity service module maps corresponding atomic capacity services according to the editing script and calls a plurality of atomic capacity services;
step S10: and finally, calling a plurality of atomic capabilities in the step S9 of the arranging flow, and returning the result of calling the plurality of atomic capabilities to the external application.
In this embodiment, the specific process of starting the scene capability service and the dynamic scaling is as follows:
step Sa, the administrator logs on the console to start the newly added scene ability;
step Sb, the console initiates an application deployment instruction to the k8s cluster ApiServer through the API;
the K8s cluster pulls a scene capacity service mirror image from a mirror image warehouse and starts a scene capacity service;
the method comprises the following steps that a capability gateway receives a scene capability call initiated by an application, finally requests to route to the scene capability, the scene capability executes an arrangement process according to a scene script warehouse, and returns a scene capability call result to an external application;
and step Se, when the external application calls the scene capacity load to be higher, K8S carries out dynamic capacity expansion aiming at the scene capacity service according to the load plus a capacity expansion configuration strategy.
In this embodiment, the K8S platform periodically checks whether an index monitored by the scene capability service pod exceeds a set threshold (for example, if cpu exceeds 80%, automatic capacity expansion is performed; peak request is decreased, and if cpu is lower than 80%, automatic capacity contraction is not triggered), and once a scaling condition is triggered, that is, the index exceeds the set threshold, a request is sent to K8S to modify the number of pods running the scene capability service; k8s responds to the request, and then refreshes the pod number of the telescopic object once; after the telescopic object is modified, the number of the posts can be increased or reduced through a list/watch mechanism, and the purpose of dynamic telescopic is achieved; otherwise, no action is taken.
Preferably, in this embodiment, as shown in fig. 1, the apparatus for scenario orchestration based on a cloud native capability gateway includes:
1) Capability gateway: the gateway layer is responsible for access and output, and the capability gateway well solves the problems of calling, unified access and the like under micro services. Typically including access control, flow control, capability authentication, service routing, etc. And (4) an authentication center: providing functions of generating a Token, verifying the Token, calling authentication, accessing control and the like; .
2) Scene capability service: and scene capacity is realized through script arrangement, and new scene capacity is newly brought into capacity gateway management. The assembly loads a capability script stored in a script warehouse and executes a scene capability service, and the service is designed based on a cloud original thought and can be deployed on a kubernets platform to achieve dynamic expansion and contraction capacity according to load.
3) A console: providing a visual flow editing interface (a web interface can be dragged and arranged), generating an arrangement script after arrangement, and calling a scene capability script warehouse for updating.
4) Scenario capability orchestration script repository: and script version management is provided, the scene capacity scripts are updated and stored in a unified mode, the distributed cache is loaded, and high-performance script execution capacity is provided.
5) Scenario capability script: and the scene capability arrangement script is used for describing that the scene capability is arranged by the atomic capability, the capability type, the calling flow and the like.
Preferably, in this embodiment, the scene capability arrangement specifically includes:
as shown in fig. 2, (1) a data model of scene capabilities for supporting implementation of a cloud-native capability gateway-based scene capability orchestration;
1) Scene capability: a scene capability unique identifier ID, a scene capability name, a scene capability description, an associated arrangement process and an associated deployment description;
2) Arranging a flow model: arranging a unique flow identification ID, a flow name, a request parameter, an output parameter and a flow description;
3) Node model: node identification ID, node name, node description, node input parameter, node type and next execution node;
4) Atomic capability: an atomic capability unique identifier ID, a capability name and a capability description;
5) Deployment model: the deployment description model uniquely identifies ID, minimum pod number, maximum pod number, cpu usage percentage.
Business logic is modeled as scenario capabilities, orchestration flows, nodes, atomic capabilities, deployment descriptions. The orchestration process is the implementation of coordination logic. A node is the implementation of a specific task in the business logic. The implementation of orchestration flows and nodes is performed in the context capabilities. The scene capability is realized by calling the atomic capability corresponding to the arrangement flow or the node to execute the task, and the task result is returned to the scene capability service. The scenario capability service can be implemented as a completely stateless service to enable unlimited horizontal expansion.
The model implements part of the code as follows
Node model implementation code
Process model implementation code
The layout process adopts a self-defined Flow definition Language (AFDL), which is abbreviated as AFDL.
Wherein:
1) scene _ availability is a root node of scene layout, and each flow is defaulted to correspond to two variables, namely in and out. in represents the input variable of the flow, and the variable name corresponds to the element name of the input message XML or json. out represents the output variable of the flow;
2) service _ flow is a capability orchestration flow node, which is a child node of scene _ availability;
3) the task _ node is a task node, and one capacity arranging flow can comprise a plurality of task nodes;
4) The if node and the task _ node are combined into a conditional node;
5) The for node and the task _ node are combined into a cycle node;
6) The assign _ value node is a variable or parameter assignment;
7) call nodes are atomic capability calls;
8) deployment is a deployment node, and dynamic scaling configuration of scene capability is configured;
(2) Orchestrating flow execution
The execution of the arrangement flow needs to divide the components into fine parts, preferably, the components are divided into one component by independently realizing the class of one function, the principle of single responsibility is embodied, and the execution functions are divided into fine parts so as to be flexibly combined in each flow executed by the flow;
a scene capability orchestration flow definition is an XML document. For example:
as shown in fig. 3, the scene capability orchestration flow configures:
description of the flow:
1) Configuring and storing a scene capacity editing script by a user through a console, and informing a scene capacity editing script warehouse;
2) Configuring scene capacity by a user, and associating the scene capacity with the editing script;
3) Enabling the scene capacity service by a user, and informing a container arrangement engine to load the scene capacity service;
4) The scene capability service is initialized according to the scene capability configuration;
as shown in FIG. 4, scenario capability execution
Description of the flow:
1) Initiating scene capability calling by an external application through a capability gateway;
2) The capability gateway calls an authentication center to authenticate the initiated scene capability;
3) After the authentication is passed, the capability gateway calls the scene capability service;
4) Mapping corresponding atomic capability services according to the scene capability according to the editing script;
5) Finally, returning the calling result of the atomic capability in the arrangement flow and returning the calling result to the application;
in the embodiment, the following scenes need to be considered when the arrangement function is performed, and the function points mainly start from usability, flexibility, expansibility, stability and consistency, and most importantly, the transaction is stable, and problems occur, so that the problems can be quickly positioned. Therefore, the call flow needs to be monitored, an exception handling mechanism and scene capacity need to be managed by adopting a cloud-based native technology, and the capacity can be dynamically expanded and contracted according to the load called by external application, so that the high availability and stability of the system are ensured.
(3) Process monitoring
How to quickly locate the problem when the problem occurs in the complex arrangement logic, a call chain technology is adopted, which nodes are executed in the process, the execution of the nodes consumes time, what is the result of executing the record, and the corresponding log needs to be recorded when the problem occurs in the node, and the abnormal direct monitoring alarm can also be generated by connecting a monitoring platform.
(4) Exception mechanism
And (4) the whole process is abnormal, and abnormal logs are recorded and displayed through a log platform.
Scene capacity service deployment and dynamic capacity expansion and reduction processes:
(1) As shown in fig. 5, the new scene capability arrangement:
description of the flow:
1) The administrator logs in the console and updates (adds, deletes and modifies) the scene capability editing script;
2) Updating a scene capacity editing script by the console;
3) The console informs a scene capability editing script warehouse, and the script warehouse updates editing scripts in the cache;
(2) As shown in FIG. 6, the scenario capability service and the dynamic scaling capacity are started
The scene capacity arranging device based on the cloud native capacity gateway can dynamically expand and contract the pod number of the service running the scene capacity according to certain indexes (such as CPU load indexes), so that the service running on the scene capacity arranging device has certain self-adaptive capacity to the change of the indexes. The system periodically checks whether the monitored indicator triggers a scaling condition. Once the scaling condition is triggered, a request is sent to k8s to modify the number of pods running the scenario capability service. k8s responds to the request and then refreshes the pod number of the scaled object once. After the telescopic object is modified, the number of the posts can be increased or reduced naturally through a list/watch mechanism, and the purpose of dynamic telescopic is achieved.
Description of the flow:
1) The administrator logs in the console to start the newly added scene capability;
2) The control console initiates an application deployment instruction to the k8s cluster ApiServer through the API;
3) The K8s cluster pulls a scene capacity service mirror image from the mirror image warehouse and starts the scene capacity service;
4) And the capability gateway receives the calling of the application initiated scene capability, finally requests the routing to the scene capability, and the scene capability executes the arranging process according to the scene script warehouse and returns the result.
5) The scene capacity service carries out dynamic expansion and contraction capacity according to the load and an expansion and contraction capacity configuration strategy;
preferably, the present embodiment implements a data model and an execution flow of the scene capability.
Preferably, the embodiment adopts a cloud native technology and is based on a dynamic capacity expansion scenario capability arranging service of a load, and is based on a distributed cache script warehouse.
Preferably, the embodiment provides a scenario capability concept, that is, atomic capabilities are combined according to a certain logic to meet the capability of a certain service scenario, and are packaged into a scenario capability on the basis of the atomic capabilities based on a cloud native technology, and the scenario capability is generated through scripted arrangement based on the atomic capabilities, and the method and the device can be based on containerization dynamic expansion.
The above description is only a preferred embodiment of the present invention, and all the equivalent changes and modifications made according to the claims of the present invention should be covered by the present invention.
Claims (1)
1. A method for arranging scene ability based on a cloud native ability gateway is characterized in that: the device comprises a scene capability arranging device based on a cloud native capability gateway, wherein the device comprises a capability gateway, an authentication center module, a scene capability service module, a console, a scene capability arranging script warehouse and a scene capability script; a user conducts scene capability arrangement based on atomic capability through the console to generate an arrangement script, calls a scene capability script warehouse to update, and initializes the scene capability service module; the external application calls a scene capacity request to reach a capacity gateway, the capacity gateway uniformly accesses all the capacity calls to the capacity gateway, and a gateway layer is responsible for accessing and outputting; then the capability gateway calls an authentication center module to realize capability generation Token, verification Token, calling authentication and access control through the authentication center module; after the authentication center module passes the authentication, a scene capability service module is called, the scene capability service module realizes the scene capability through script arrangement, and the new scene capability is brought into the capability gateway again for management; the scene capability service module calls the atomic capability according to the editing script and finally returns the atomic capability to the application side;
the method comprises the following steps:
step S1: configuring and storing a scene capacity editing script by a user through a console, and informing a scene capacity editing script warehouse;
step S2: configuring scene capacity by a user, and associating the scene capacity with the editing script;
and step S3: a user starts a scene ability service module and informs a container arrangement engine to load the scene ability service;
and step S4: the scene capability service module is initialized according to the scene capability configuration;
step S5: initiating scene capability calling by an external application through a capability gateway;
step S6: the capability gateway calls an authentication center module to authenticate the initiated scene capability;
step S7: after the authentication is passed, the capability gateway calls a scene capability service module;
step S8: the scene capacity service module performs dynamic expansion and contraction capacity according to the load of the external application request;
step S9: the scene capacity service module maps corresponding atomic capacity services according to the editing script and calls a plurality of atomic capacity services;
step S10: finally, a plurality of atomic capabilities in the step S9 of the arranging flow are called, and the result obtained after the plurality of atomic capabilities are called is returned to the external application;
the specific process of starting the scene capacity service and the dynamic expansion capacity comprises the following steps:
step Sa, the administrator logs on the console to start the newly added scene ability;
step Sb, the console initiates an application deployment instruction to the k8s cluster ApiServer through the API;
the K8s cluster pulls a scene capacity service mirror image from a mirror image warehouse and starts a scene capacity service;
the method comprises the following steps that a capability gateway receives a scene capability call initiated by an application, finally requests to route to the scene capability, the scene capability executes an arrangement process according to a scene script warehouse, and returns a scene capability call result to an external application;
step Se, when the external application calls that the scene capacity load is higher, K8S carries out dynamic expansion and contraction capacity aiming at the scene capacity service according to the load and the expansion and contraction capacity configuration strategy;
the specific content of the dynamic expansion and contraction capacity in the step Se is as follows:
the K8S platform regularly checks whether indexes monitored by the scene capacity service pods exceed a set threshold, and once a stretching condition is triggered, the indexes exceed the set threshold, a request is sent to K8S to modify the number of the pods running the scene capacity service; k8s responds to the request, and then refreshes the pod number of the telescopic object once; after the telescopic object is modified, the number of the posts can be increased or reduced through a list/watch mechanism, and the purpose of dynamic telescopic is achieved; otherwise, no action is taken.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011275416.6A CN112468463B (en) | 2020-11-13 | 2020-11-13 | Device and method for arranging scene capacity based on cloud native capacity gateway |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011275416.6A CN112468463B (en) | 2020-11-13 | 2020-11-13 | Device and method for arranging scene capacity based on cloud native capacity gateway |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112468463A CN112468463A (en) | 2021-03-09 |
| CN112468463B true CN112468463B (en) | 2023-04-11 |
Family
ID=74837359
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011275416.6A Active CN112468463B (en) | 2020-11-13 | 2020-11-13 | Device and method for arranging scene capacity based on cloud native capacity gateway |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112468463B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114143373B (en) * | 2021-11-02 | 2023-11-28 | 福建福诺移动通信技术有限公司 | Capacity scheduling engine optimizing system and method based on BPMN specification |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107395731A (en) * | 2017-07-28 | 2017-11-24 | 郑州云海信息技术有限公司 | A kind of adjusting method and device of the container cluster based on service orchestration |
| CN108769100A (en) * | 2018-04-03 | 2018-11-06 | 郑州云海信息技术有限公司 | A kind of implementation method and its device based on kubernetes number of containers elastic telescopics |
| CN109471658A (en) * | 2018-11-19 | 2019-03-15 | 四川长虹电器股份有限公司 | A method of the fast construction target drone environment based on container |
| CN110175077A (en) * | 2019-05-27 | 2019-08-27 | 浪潮云信息技术有限公司 | A kind of method and system based on order management container resource |
| CN110704164A (en) * | 2019-09-30 | 2020-01-17 | 珠海市新德汇信息技术有限公司 | Cloud native application platform construction method based on Kubernetes technology |
| CN111078315A (en) * | 2019-12-12 | 2020-04-28 | 拉扎斯网络科技（上海）有限公司 | Microservice arranging and executing method and system, architecture, equipment and storage medium |
| CN111158708A (en) * | 2019-12-25 | 2020-05-15 | 上海精鲲计算机科技有限公司 | Task arrangement engine system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11086725B2 (en) * | 2019-03-25 | 2021-08-10 | Robin Systems, Inc. | Orchestration of heterogeneous multi-role applications |
-
2020
- 2020-11-13 CN CN202011275416.6A patent/CN112468463B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107395731A (en) * | 2017-07-28 | 2017-11-24 | 郑州云海信息技术有限公司 | A kind of adjusting method and device of the container cluster based on service orchestration |
| CN108769100A (en) * | 2018-04-03 | 2018-11-06 | 郑州云海信息技术有限公司 | A kind of implementation method and its device based on kubernetes number of containers elastic telescopics |
| CN109471658A (en) * | 2018-11-19 | 2019-03-15 | 四川长虹电器股份有限公司 | A method of the fast construction target drone environment based on container |
| CN110175077A (en) * | 2019-05-27 | 2019-08-27 | 浪潮云信息技术有限公司 | A kind of method and system based on order management container resource |
| CN110704164A (en) * | 2019-09-30 | 2020-01-17 | 珠海市新德汇信息技术有限公司 | Cloud native application platform construction method based on Kubernetes technology |
| CN111078315A (en) * | 2019-12-12 | 2020-04-28 | 拉扎斯网络科技（上海）有限公司 | Microservice arranging and executing method and system, architecture, equipment and storage medium |
| CN111158708A (en) * | 2019-12-25 | 2020-05-15 | 上海精鲲计算机科技有限公司 | Task arrangement engine system |
Non-Patent Citations (1)
| Title |
|---|
| 容器技术在移动核心网的应用;何宇锋等;《移动通信》;20180315(第03期);第32-37页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112468463A (en) | 2021-03-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106951233B (en) | Mixed-mode smart phone application development framework system | |
| CN102868736B (en) | A kind of cloud computing Monitoring framework design basis ground motion method and cloud computing treatment facility | |
| CN106371889B (en) | Method and device for realizing high-performance cluster system of scheduling mirror image | |
| US9537717B2 (en) | Policy enforcement point provisioning | |
| CN111857873A (en) | Method for realizing cloud native container network | |
| WO2016184175A1 (en) | Database processing method and apparatus | |
| CN112035228A (en) | Resource scheduling method and device | |
| Da et al. | Kalimucho: middleware for mobile applications | |
| CN108632299A (en) | Enhance method, apparatus, electronic equipment and the storage medium of registration center's availability | |
| CN113204353B (en) | Big data platform assembly deployment method and device | |
| CN110308987B (en) | Method for updating connection parameters of distributed training tasks on container cloud | |
| CN112468463B (en) | Device and method for arranging scene capacity based on cloud native capacity gateway | |
| CN111064626B (en) | Configuration updating method, device, server and readable storage medium | |
| Justino et al. | Outsourcing resource-intensive tasks from mobile apps to clouds: Android and aneka integration | |
| CN110365743B (en) | Zookeeper-based implementation method of load balancer supporting multiple customizable load algorithms | |
| CN109005163B (en) | HTTP dynamic request service calling method | |
| CN113157737B (en) | Service instance association relation dynamic construction system | |
| CN115811481A (en) | Interactive service testing method and device, computer equipment and storage medium | |
| CN114461249A (en) | Micro-service deployment method, device, code server and storage medium | |
| CN114640610A (en) | Service management method and device based on cloud protogenesis and storage medium | |
| CN113626001A (en) | API dynamic editing method and device based on script | |
| CN109117152B (en) | Service generation system and method | |
| US20200099788A1 (en) | Context data management interface for contact center | |
| Navaneeth et al. | Building a Backend-as-a-Service Platform in Kubernetes | |
| US20240106907A1 (en) | Entity for implementing a service in a network, application device, and method for executing an operation of a service |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |