CN116389561A - Application deployment method, device and system based on computing power network - Google Patents
Application deployment method, device and system based on computing power network Download PDFInfo
- Publication number
- CN116389561A CN116389561A CN202310654082.0A CN202310654082A CN116389561A CN 116389561 A CN116389561 A CN 116389561A CN 202310654082 A CN202310654082 A CN 202310654082A CN 116389561 A CN116389561 A CN 116389561A
- Authority
- CN
- China
- Prior art keywords
- application
- access information
- information
- access
- target computing
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 43
- 230000004044 response Effects 0.000 claims abstract description 14
- 238000005516 engineering process Methods 0.000 description 4
- 230000008447 perception Effects 0.000 description 3
- 210000004899 c-terminal region Anatomy 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000007175 bidirectional communication Effects 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- 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/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- 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/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Health & Medical Sciences (AREA)
- Computing Systems (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Stored Programmes (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Small-Scale Networks (AREA)
Abstract
The application relates to the technical field of application access, solves the problem that an end user at an end side cannot directly access and configure an application deployed in a cluster for the calculation network or edge calculation at the end side in the prior art, and discloses an application deployment method, device and system based on the calculation network, wherein the method comprises the following steps: the method comprises the steps of obtaining an application deployment request containing first application information and second application information, scheduling corresponding computing nodes for deploying the first application and the second application according to the application deployment request, routing data of the second application to the corresponding first application, and sending application deployment request response and access information so as to form an access link.
Description
Technical Field
The application relates to the technical field of application deployment, in particular to an application deployment method, device and system based on a computing network.
Background
The architecture of the internet of things can be divided into three layers: a perception layer, a network layer and an application layer. The sensing layer is composed of various IoT devices, including temperature and humidity sensors, two-dimensional code tags, RFID tags, readers, cameras, infrared rays, GPS sensing terminals, and the like. The perception layer is the source of thing recognition object, collection information of thing networking. The network layer is composed of various networks including the Internet, a broadcast and television network, a network management system, an internet of things (IoT) platform and the like, is a central of the whole internet of things and is responsible for transmitting and processing information acquired by the perception layer. The application layer is an interface of the Internet of things and a user, and is combined with industry requirements to realize intelligent application of the Internet of things, such as Mobile APP or Web Portal.
In the prior art, application access is generally performed through cloud platforms such as K8S, the number of instances is selected during deployment, and then unified access is performed directly through modes such as an API gateway of a K8S cluster and an Ingress service.
The current application access mode is mainly oriented to enterprise users at the B end, namely when the enterprise users are accessed outside the cluster in an API mode and the like, the enterprise users are generally accessed through interfaces such as a C/S architecture, a Rest/GRPC and the like.
However, the deployment mode has a fatal problem, namely for the end-side computing power network or edge computing, because of the architecture problem of K8S, the application deployed through K8S at present needs to be remotely accessed through a gateway, and is generally given to a B-end user, and the problem that a C-end generally needs to be solved in a toBtoC mode; on the other hand, since the devices at the C-terminal, such as the home, are generally located in the intranet, and cannot be accessed due to the lack of public IP, the end user at the end side (i.e., the C-terminal user) cannot directly access and configure the applications deployed in the cluster, that is, if one user contributes to several devices at his home through the computing network, some processing applications are deployed therein, such as a camera face recognition application encapsulated by a container, since the container itself cannot provide access to the front end like a virtual machine, and due to the isolation of the container, there is currently no very general or standard container direct deployment method, so that the user cannot directly access through the container application deployed on his computing device, and at the same time, when the application detects that there is a stranger or dangerous person visiting, the application cannot intuitively alert the user and directly present real-time alert content or real-time video stream to the client.
Disclosure of Invention
The application aims to solve the problem that an end user at an end side cannot directly access and configure applications deployed in a cluster for the end side computing power network or edge computing in the prior art, and provides an application deployment method, device and system aiming at the end side computing power network and the edge computing power network, especially for a family side computing power network.
In a first aspect, an application deployment method based on a computing power network is provided, including:
acquiring an application deployment request, wherein the application deployment request comprises a deployment instruction, first application information and second application information;
scheduling corresponding computing power nodes for deploying the first application and/or the second application according to the application deployment request;
the data of the second application is routed to the corresponding first application in a mode of API gateway registration;
and sending the application deployment request response and the access information so as to form an access link.
In one possible implementation, the deploying the first application and the second application includes:
scheduling a first target computing node according to the first application information, and sending a first application deployment request to the first target computing node so that the first target computing node deploys a first application;
receiving first access information of a first application in response to the completion of the deployment of the first application;
sending a second application deployment request to a second target computing node to enable the second target computing node to deploy a second application, wherein the second application deployment request comprises second application information and first access information;
the method for routing the data of the second application to the corresponding first application through the API gateway registration comprises the following steps:
receiving first access information of a first application and/or second access information of a second application;
registering an API gateway according to the first access information and/or the second access information so that the second application data can be routed to the first application;
and returning third access information of the API gateway.
In another possible implementation manner, the deploying the first application or the second application includes:
scheduling a first target computing node according to the first application information, and sending a first application deployment request to the first target computing node so that the first target computing node deploys a first application;
the method for routing the data of the second application to the corresponding first application through the API gateway registration comprises the following steps:
registering an API gateway according to the first access information;
sending a second application deployment request to a second target computing node to enable the second target computing node to deploy a second application, wherein the second application deployment request comprises second application information, first access information and third access information of an API gateway so that second application data can be routed to the first application;
and returning third access information of the API gateway.
Further, the first access information and the second access information each include all or part of a web address or path required for accessing the application, and the first access information and the second access information further include, but are not limited to, one or more of the following information: source IP, source port, destination IP, destination port, and protocol type.
Further, the application market forms a complete access link according to the returned third access information, wherein the third access information comprises the registered identification.
Further, the first target computing node and the second target computing node are the same node, or
The first target computing node and the second target computing node are different nodes.
In a second aspect, an application deployment apparatus based on a computing network is provided, including:
the system comprises an acquisition module, a storage module and a control module, wherein the acquisition module is used for acquiring an application deployment request, and the application deployment request comprises a deployment instruction, first application information and second application information;
the scheduling module is used for scheduling the corresponding computing power nodes for deploying the first application and the second application according to the application deployment request;
the routing module is used for routing the data of the second application to the corresponding first application in a mode of API gateway registration;
and the response module is used for sending the application deployment request response and the access information so as to form an access link.
In a third aspect, an application deployment system based on a computing network is provided, comprising:
the application market is used for sending an application deployment request according to the user demand and forming an access link according to the third access information;
an orchestration scheduling platform for executing a program or instruction that when executed implements a method as in any one of the implementations of the first aspect;
the computing power node is used for providing a first target computing power node, a second target computing power node and registering an API gateway.
In a fourth aspect, a computer readable storage medium is provided, the computer readable medium storing program code for execution by a device, the program code comprising steps for performing the method as in any one of the implementations of the first aspect.
In a fifth aspect, there is provided an electronic device comprising a processor, a memory and a program or instruction stored on the memory and executable on the processor, which when executed by the processor implements a method as in any of the implementations of the first aspect.
The application has the following beneficial effects: by respectively deploying the first application and the second application, wherein the first application is an application which is packaged by a container or a non-container, the second application is an application which is developed and packaged by a front-end technology and can be loaded and operated by a browser, and the like, when the application in the application market is selected and deployed, information carrying the first application and the second application is deployed and registered to an API gateway, so that a user can directly access the application deployed on an computing node through an access link.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application, illustrate and explain the application and are not to be construed as limiting the application.
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of a method of computing network based application deployment of embodiment 1 of the present application;
FIG. 2 is a block diagram of the architecture of the computing network-based application deployment apparatus of embodiment 3 of the present application;
FIG. 3 is a schematic diagram of a computing network-based application deployment system of embodiment 4 of the present application;
fig. 4 is an internal schematic view of the electronic device of embodiment 6 of the present application.
Reference numerals:
100. an application market; 200. arranging a scheduling platform; 300. and calculating force nodes.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
Example 1
As shown in fig. 1, an application deployment method based on a computing power network according to embodiment 1 of the present application includes: acquiring an application deployment request, wherein the application deployment request comprises a deployment instruction, first application information and second application information; scheduling corresponding computing power nodes for deploying the first application and/or the second application according to the application deployment request; the data of the second application is routed to the corresponding first application in a mode of API gateway registration; the method comprises the steps of respectively deploying a first application and a second application, wherein the first application is an application packaged by a container or a non-container, the second application is an application which is developed and packaged by a front-end technology such as a webpage, javaScript and the like and can be loaded and operated through a browser, when the application in an application market is selected and deployed, the information carrying the first application and the second application is deployed and registered to an API gateway respectively, so that a user can directly access the application deployed on an computing node through the access link, and the application deployment light application engine and the front-end and back-end registration and matching are performed through the API gateway, so that an access channel of the first application can be effectively opened, the user can directly load a second application resource through the browser, and access relevant configuration and results of the first application.
In one possible embodiment, the application deployment method based on the computing power network includes:
s100, acquiring an application deployment request, wherein the application deployment request comprises a deployment instruction, first application information and second application information;
specifically, when the application is released in the application market, the application comprises a front-end application and a back-end application, wherein when the first application is the front-end application, the second application is the back-end application; when the first application is a back-end application, the second application is a front-end application, the back-end application is an application packaged by a container or a non-container, the front-end application is an application which is developed and packaged by using a front-end technology and can be loaded and operated through a browser, and the application needs to be an integral application for a user, and the front-end application and the back-end application are released, which is required to be developed and released by an application developer or provider.
S200, arranging and scheduling corresponding computing power nodes for deploying the first application and the second application according to the application deployment request;
illustratively, taking a first application deployed first as an example, comprising:
s201, scheduling a first target computing node according to the first application information, and sending a first application deployment request to the first target computing node so that the first target computing node deploys a first application;
the first application information comprises N nodes which are required to occupy when the first application runs, each node occupies CPU of x Core and memory of x GB, the first application information is ordered in all accessed nodes according to a scheduling algorithm such as resource priority, and the first N nodes are selected as first target computing nodes to deploy the first application.
S202, receiving first access information of a first application in response to the completion of the deployment of the first application;
wherein the first access information includes, but is not limited to, one or more of the following: the source IP, source port, destination IP, destination port and protocol type will return the first access information after the first application is deployed, where the first access information generally includes 5-tuple content in a Socket (two programs on the network implement data exchange through a bidirectional communication connection, and one end of the connection is called a Socket), that is, the source IP, source port, destination IP, destination port and protocol type, because the IP is many times the same when accessing, and the protocol is determined in advance, so only the port is basically needed as necessary information.
S203, sending a second application deployment request to the second target computing node so as to enable the second target computing node to deploy a second application, wherein the second application deployment request comprises second application information and first access information;
in addition, generally, the front-end and back-end access efficiency is considered, the second target computing node and the first target computing node select the same node, and the second target computing node may also select another node (for example, other computing nodes in the same intranet or network segment) according to other scheduling policies, and send a second application deployment request to the node, where the second application deployment request carries the second application information and the first access information in step S202.
S300, data of the second application are routed to the corresponding first application in a mode of API gateway registration;
specifically, the routing the data of the second application to the corresponding first application by the API gateway registration method includes:
s301, receiving first access information of a first application and second access information of a second application;
wherein the first access information and the second access information each comprise all or part of a web address or path required for accessing the application, and the first access information and the second access information further comprise one or more of the following information, but are not limited to: source IP, source port, destination IP, destination port, and protocol type.
S302, registering an API gateway according to the first access information and/or the second access information so that second application data can be routed to the first application;
specifically, after the second application deployment is completed, the second target computing node performs registration of the API gateway according to the second access information and the first access information, so that the second application data can be routed to the first application, where the first access information is, for example, an IP and a port of a node where the first application is located, an ID of a container, and the like, so that when the second application accesses, a message can be routed to the corresponding first application (container) through the information such as the IP and the port.
S303, returning third access information of the API gateway;
specifically, after the API gateway is successfully registered, the API gateway sends third access information to the second computing node, where the third access information includes a registered identifier, and the registered identifier is, for example, an index number or a hash number after the registration and association of the previous first application information, so that front and back ends can be registered and matched through the API gateway, and further, an access channel of the front and back ends is effectively opened.
In addition, after the second computing node receives the third access information, the second access information is acquired, and the second access information comprises all or part of websites or paths required by the access application, so that a user can directly load second application resources through a browser and access relevant configuration and results of the first application.
S400, sending an application deployment request response and access information so as to form an access link;
specifically, the application market forms a complete access link according to the returned third access information, where the third access information includes the registered identifier, and an access entry is required for the user, for example: a URL (universal resource locator, generic name Uniform Resource Locator) where the second application and the subsequent application information just deployed need to be organized into access links in order to find the corresponding previous first application.
After the user selects to install the application in the application market, the application is actually installed and run on the computing node, and the first access information of the application of the method is returned and presented to the client, which is an exemplary mobile phone, a tablet, a computer or other intelligent terminals, and the application is actually run on the computing node after the user clicks, so that the user can directly access the application deployed on the computing node through the access link.
Example 2
Of course, one application of the first application and the second application may be deployed first, then the API gateway registration is performed, and finally the other application is deployed, and the application deployment method based on the computing network specifically includes:
s100, acquiring an application deployment request, wherein the application deployment request comprises a deployment instruction, first application information and second application information;
specifically, when the application is released in the application market, the application comprises a front-end application and a back-end application, wherein when the first application is the front-end application, the second application is the back-end application; when the first application is a back-end application, the second application is a front-end application, the back-end application is an application packaged by a container or a non-container, the front-end application is an application which is developed and packaged by using a front-end technology and can be loaded and operated through a browser, and the application needs to be an integral application for a user, and the front-end application and the back-end application are released, which is required to be developed and released by an application developer or provider.
S200, arranging and scheduling corresponding computing power nodes for deploying a first application or a second application according to the application deployment request;
illustratively, taking a first application deployed first as an example, comprising:
s201, scheduling a first target computing node according to the first application information, and sending a first application deployment request to the first target computing node so that the first target computing node deploys a first application;
the first application information comprises N nodes which are required to occupy when the first application runs, each node occupies CPU of x Core and memory of x GB, the first application information is ordered in all accessed nodes according to a scheduling algorithm such as resource priority, and the first N nodes are selected as first target computing nodes to deploy the first application.
S300, data of the second application are routed to the corresponding first application in a mode of API gateway registration;
specifically, the routing the data of the second application to the corresponding first application by the API gateway registration method includes:
s301, registering an API gateway according to first access information;
specifically, after the first application deployment is completed, the registration of the API gateway is performed according to the first access information of the first application;
s302, sending a second application deployment request to the second target computing node to enable the second target computing node to deploy a second application, wherein the second application deployment request comprises second application information, first access information and third access information of an API gateway, so that second application data can be routed to the first application;
specifically, after the registration of the API gateway is completed, the second application is deployed according to the second application information, the first access information and third access information of the API gateway, so that the second application data can be routed to the first application, wherein the third access information comprises the registered identifier.
S303, returning third access information of the API gateway;
specifically, after the registration of the API gateway is successful, the API gateway sends third access information to the second computing node, and the registered identifier is, for example, an index number or a hash number after the registration and association of the previous first application information, so that the registration and matching of the front end and the rear end can be performed through the API gateway, and further the access channels of the front end and the rear end can be effectively opened.
In addition, after the second computing node receives the third access information, the second access information is acquired, and the second access information comprises all or part of websites or paths required by the access application, so that a user can directly load second application resources through a browser and access relevant configuration and results of the first application.
S400, sending an application deployment request response and access information so as to form an access link;
specifically, the application market forms a complete access link according to the returned third access information, where the third access information includes the registered identifier, and an access entry is required for the user, for example: a URL (universal resource locator, generic name Uniform Resource Locator) where the second application and the subsequent application information just deployed need to be organized into access links in order to find the corresponding previous first application.
After the user selects to install the application in the application market, the application is actually installed and run on the computing node, and the first access information of the application of the method is returned and presented to the client, which is an exemplary mobile phone, a tablet, a computer or other intelligent terminals, and the application is actually run on the computing node after the user clicks, so that the user can directly access the application deployed on the computing node through the access link.
Example 3
As shown in fig. 2, an application deployment apparatus based on a computing network according to embodiment 2 of the present application includes:
the system comprises an acquisition module, a storage module and a control module, wherein the acquisition module is used for acquiring an application deployment request, and the application deployment request comprises a deployment instruction, first application information and second application information;
the scheduling module is used for scheduling the corresponding computing power nodes for deploying the first application and the second application according to the application deployment request;
the routing module is used for routing the data of the second application to the corresponding first application in a mode of API gateway registration;
and the response module is used for sending the application deployment request response and the access information so as to form an access link.
Through the device, when the application in the application market is selected and deployed, the information carrying the first application and the second application is deployed and registered to the API gateway respectively, so that a user can directly access the application deployed on the computing node through the access link.
Example 4
As shown in fig. 3, an application deployment system based on a computing network according to embodiment 3 of the present application includes:
an application market 100, configured to send an application deployment request according to a user requirement, and form an access link according to third access information;
the computing power node 300 is configured to provide a first target computing power node, a second target computing power node, and a registration API gateway.
As shown in fig. 3, in one possible embodiment the specific workflow of the application deployment system is:
101. the user selects an application to be deployed through an application market, and the application market sends an application deployment request carrying a first application and a second application;
102. after receiving the deployment request, the scheduling platform selects a target computing node according to the resource requirement condition of the first application (such as the need to occupy xCore CPU, xGB memory and the like), and sends the deployment request to the target computing node 1;
103. after the target computing node 1 finishes deploying the first application, returning first access information of the first application, such as a port and the like;
104. the scheduling platform continues to deploy the second application to the target computing node 2, generally, the front end access efficiency and the back end access efficiency are considered, the target computing node 2 and the target computing node 1 select the same node, and can also select another node (such as other computing nodes of the same intranet or network segment) according to other scheduling strategies, and send a second application deployment request to the node, wherein the second application deployment request carries second application information and first access information of the first application in the last step;
105. the second application engine registers the API gateway according to the second access information and the first access information of the front application and the first application so that the front-end access can be routed to the first application;
106. the API gateway returns the registered access result and optionally carries the registered identifier;
107. after the second application engine deploys the second application, returning third access information;
108. the scheduling platform returns a deployment result and carries 107 returned third access information;
109. and the application market forms a complete access link according to the returned third access information.
Through the device, when the application in the application market is selected and deployed, the information carrying the first application and the second application is deployed and registered to the API gateway respectively, so that a user can directly access the application deployed on the computing node through the access link.
Example 5
A computer readable storage medium according to embodiment 4 of the present application stores program code for execution by a device, the program code including steps for performing the method as in any one of implementation modes of embodiment 1 or embodiment 2 of the present application;
wherein the computer readable storage medium may be a Read Only Memory (ROM), a static storage device, a dynamic storage device, or a random access memory (random access memory, RAM); the computer readable storage medium may store program code which, when executed by a processor, is adapted to perform the steps of a method as in any one of the implementations of embodiment 1 of the present application.
Example 6
As shown in fig. 4, embodiment 5 of the present application relates to an electronic device, where the electronic device includes a processor, a memory, and a program or an instruction stored on the memory and executable on the processor, where the program or the instruction implements a method as in any one of the implementation manners of embodiment 1 or embodiment 2 of the present application when executed by the processor;
the processor may be a general-purpose central processing unit (central processing unit, CPU), microprocessor, application specific integrated circuit (application specific integrated circuit, ASIC), graphics processor (graphics processing unit, GPU) or one or more integrated circuits for executing relevant programs to implement the methods of any of the implementations of embodiment 1 of the present application.
The processor may also be an integrated circuit electronic device with signal processing capabilities. In implementation, each step of the method in any implementation of embodiment 1 of the present application may be implemented by an integrated logic circuit of hardware in a processor or an instruction in a software form.
The processor may also be a general purpose processor, a digital signal processor, an Application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (field programmable gatearray, FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be embodied directly in a hardware decoding processor or in a combination of hardware and software modules in the decoding processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads information in the memory, and in combination with its hardware, performs functions necessary for execution by the units included in the data processing apparatus of the embodiment of the present application, or executes a method in any implementation manner of embodiment 1 of the present application.
The above is only a preferred embodiment of the present application; the scope of protection of the present application is not limited in this respect. Any person skilled in the art, within the technical scope of the present disclosure, shall cover the protection scope of the present application by making equivalent substitutions or alterations to the technical solution and the improved concepts thereof.
Claims (10)
1. An application deployment method based on a computing power network, comprising the following steps:
acquiring an application deployment request, wherein the application deployment request comprises a deployment instruction, first application information and second application information;
scheduling corresponding computing power nodes for deploying the first application and/or the second application according to the application deployment request;
the data of the second application is routed to the corresponding first application in a mode of API gateway registration;
and sending the application deployment request response and the access information so as to form an access link.
2. The method of claim 1, wherein deploying the first application and the second application comprises:
scheduling a first target computing node according to the first application information, and sending a first application deployment request to the first target computing node so that the first target computing node deploys a first application;
receiving first access information of a first application in response to the completion of the deployment of the first application;
sending a second application deployment request to a second target computing node to enable the second target computing node to deploy a second application, wherein the second application deployment request comprises second application information and first access information;
the method for routing the data of the second application to the corresponding first application through the API gateway registration comprises the following steps:
receiving first access information of a first application and/or second access information of a second application;
registering an API gateway according to the first access information and/or the second access information so that the second application data can be routed to the first application;
and returning third access information of the API gateway.
3. The method of claim 1, wherein deploying the first application or the second application comprises:
scheduling a first target computing node according to the first application information, and sending a first application deployment request to the first target computing node so that the first target computing node deploys a first application;
the method for routing the data of the second application to the corresponding first application through the API gateway registration comprises the following steps:
registering an API gateway according to the first access information;
sending a second application deployment request to a second target computing node to enable the second target computing node to deploy a second application, wherein the second application deployment request comprises second application information, first access information and third access information of an API gateway so that second application data can be routed to the first application;
and returning third access information of the API gateway.
4. A method of computing-network-based application deployment as claimed in claim 2 or 3, wherein the first and second access information each comprise all or part of a web address or path required to access an application, the first and second access information further comprising, but not limited to, one or more of the following: source IP, source port, destination IP, destination port, and protocol type.
5. The method of claim 1, wherein the application marketplace forms a complete access link from returned third access information, wherein the third access information includes a registered identity.
6. A method of deployment of a computing network-based application as claimed in claim 2 or 3, wherein the first target computing node and the second target computing node are the same node, or
The first target computing node and the second target computing node are different nodes.
7. An application deployment apparatus based on a computing network, comprising:
the system comprises an acquisition module, a storage module and a control module, wherein the acquisition module is used for acquiring an application deployment request, and the application deployment request comprises a deployment instruction, first application information and second application information;
the scheduling module is used for scheduling the corresponding computing power nodes for deploying the first application and the second application according to the application deployment request;
the routing module is used for routing the data of the second application to the corresponding first application in a mode of API gateway registration;
and the response module is used for sending the application deployment request response and the access information so as to form an access link.
8. An application deployment system based on a computing network, comprising:
the application market is used for sending an application deployment request according to the user demand and forming an access link according to the third access information;
scheduling platform for executing a program or instruction which when executed implements the method of any one of claims 1-6;
the computing power network is used for providing a first target computing power node, a second target computing power node and registering an API gateway.
9. A computer readable storage medium storing program code for execution by a device, the program code comprising steps for performing the method of any one of claims 1-6.
10. An electronic device comprising a processor, a memory, and a program or instruction stored on the memory and executable on the processor, which when executed by the processor, implements the method of any of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310654082.0A CN116389561B (en) | 2023-06-05 | 2023-06-05 | Application deployment method, device and system based on computing power network |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310654082.0A CN116389561B (en) | 2023-06-05 | 2023-06-05 | Application deployment method, device and system based on computing power network |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116389561A true CN116389561A (en) | 2023-07-04 |
| CN116389561B CN116389561B (en) | 2023-08-08 |
Family
ID=86961937
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310654082.0A Active CN116389561B (en) | 2023-06-05 | 2023-06-05 | Application deployment method, device and system based on computing power network |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116389561B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109818902A (en) * | 2017-11-21 | 2019-05-28 | 中国电信股份有限公司 | Automatic service deployment method, service dispatch management module and EPG platform |
| US20210336788A1 (en) * | 2020-04-24 | 2021-10-28 | Netapp, Inc. | Management services api gateway |
| CN114885024A (en) * | 2022-04-28 | 2022-08-09 | 远景智能国际私人投资有限公司 | Routing method, device, equipment and medium of application example |
| CN115221237A (en) * | 2021-04-19 | 2022-10-21 | 中国移动通信集团设计院有限公司 | Node deployment method, application chain deployment method, device, server and computer program |
-
2023
- 2023-06-05 CN CN202310654082.0A patent/CN116389561B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109818902A (en) * | 2017-11-21 | 2019-05-28 | 中国电信股份有限公司 | Automatic service deployment method, service dispatch management module and EPG platform |
| US20210336788A1 (en) * | 2020-04-24 | 2021-10-28 | Netapp, Inc. | Management services api gateway |
| CN115221237A (en) * | 2021-04-19 | 2022-10-21 | 中国移动通信集团设计院有限公司 | Node deployment method, application chain deployment method, device, server and computer program |
| CN114885024A (en) * | 2022-04-28 | 2022-08-09 | 远景智能国际私人投资有限公司 | Routing method, device, equipment and medium of application example |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116389561B (en) | 2023-08-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP6811263B2 (en) | Publication and discovery of M2M-IOT services | |
| US10798157B2 (en) | Technologies for transparent function as a service arbitration for edge systems | |
| US11012839B2 (en) | Cross-resource subscription for M2M service layer | |
| EP3664372B1 (en) | Network management method and related device | |
| US20140289366A1 (en) | Service providing method and system for instance hosting | |
| EP2957085B1 (en) | Service layer resource propagation across domains | |
| CN103942225A (en) | Method and system for invoking resources of Hybrid App client and client | |
| US20140214921A1 (en) | System and method for identification of an application executed on a mobile device | |
| CN108306844B (en) | Method for API communication between server and client | |
| CN112799825A (en) | Task processing method and network equipment | |
| CN114205342A (en) | Routing method, electronic device, medium, and program product for service debugging | |
| CN109343983A (en) | Information interacting method, device, equipment and storage medium between functional module | |
| US10225358B2 (en) | Page push method, device, server and system | |
| CN112818270B (en) | Data cross-domain transfer method and device and computer equipment | |
| CN116389561B (en) | Application deployment method, device and system based on computing power network | |
| US10298716B2 (en) | Server, client device and methods therein for handling cached content resources | |
| CN113014626A (en) | Data service management method and device, storage medium and electronic device | |
| CN113127775A (en) | Page loading method, device, equipment and storage medium | |
| JP6412641B2 (en) | Communication link transmission method, apparatus and terminal | |
| CN114567678A (en) | Resource calling method and device of cloud security service and electronic equipment | |
| WO2018132557A1 (en) | Dynamic protocol switching | |
| CN113568720A (en) | Process management, development and configuration method, device, electronic equipment and storage medium | |
| CN109460215B (en) | Application control method and device | |
| CN113596105A (en) | Content acquisition method, edge node and computer-readable storage medium | |
| KR20210128096A (en) | Apparatus and method for interworking among internet of things platforms |
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 |