CN111400054A - Network plug-in calling method and device, computer storage medium and electronic equipment - Google Patents
Network plug-in calling method and device, computer storage medium and electronic equipment Download PDFInfo
- Publication number
- CN111400054A CN111400054A CN201811609445.4A CN201811609445A CN111400054A CN 111400054 A CN111400054 A CN 111400054A CN 201811609445 A CN201811609445 A CN 201811609445A CN 111400054 A CN111400054 A CN 111400054A
- Authority
- CN
- China
- Prior art keywords
- interface
- calling
- network plug
- network
- plug
- 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 76
- 230000005540 biological transmission Effects 0.000 claims description 78
- 230000006870 function Effects 0.000 claims description 58
- 238000012545 processing Methods 0.000 claims description 5
- 230000001419 dependent effect Effects 0.000 claims description 4
- 230000010354 integration Effects 0.000 claims description 3
- 230000008569 process Effects 0.000 abstract description 10
- 238000010586 diagram Methods 0.000 description 6
- 230000003993 interaction Effects 0.000 description 3
- RJKFOVLPORLFTN-LEKSSAKUSA-N Progesterone Chemical compound C1CC2=CC(=O)CC[C@]2(C)[C@@H]2[C@@H]1[C@@H]1CC[C@H](C(=O)C)[C@@]1(C)CC2 RJKFOVLPORLFTN-LEKSSAKUSA-N 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 2
- 238000004590 computer program Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 238000004883 computer application Methods 0.000 description 1
- 230000008676 import Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000005096 rolling process Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000001052 transient effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
- G06F9/44526—Plug-ins; Add-ons
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The application discloses a method and a device for calling a network plug-in, a method and a device for creating an interface frame, a computer storage medium and electronic equipment, wherein the calling method comprises the following steps: acquiring a calling request for a network plug-in to be called transmitted by a container runtime interface; determining a calling interface used for calling the network plug-in the interface frame according to the calling request; obtaining a network plug-in matched with the network plug-in to be called according to the determined calling interface for calling the network plug-in the interface frame; transmitting the matched network plug-in to the container runtime interface. Because the interface framework can call the protocol based on the container network interface, the function requirement required by the container operation can be met, and a large amount of repeated code writing work caused by the need of providing different protocols aiming at different end sides in the calling process is avoided.
Description
Technical Field
The application relates to the technical field of computer application, in particular to a method and a device for calling a network plug-in. The application also relates to a method and a device for creating the interface framework. The application also relates to a computer storage medium and an electronic device.
Background
Kubernetes is a container orchestration system, which is a Google open-sourced container cluster management system, an open-sourced version of Google's multi-year large-scale container management technology Borg.
Kubernets contains a number of properties including: container-based application deployment, maintenance and rolling upgrades, load balancing and service discovery, cross-machine and cross-regional cluster scheduling, automatic scaling, and the like.
Currently, the Kuberrnets official defines the CNI (Container Network Interface) specification, namely: a generic interface is defined between the network plug-in and the container runtime. As the container industry has developed, and containers have been operated, not only a well-known one, including CoreOS rkt, super.sh runV, Google's gvsor, which are intended to interface with kubernets, another specification set forth by kubernets officials is required to be implemented: the CRI (Container Runtime Interface) needs to call services related to the CNI in the CRI Manager, and at present, Container runtimes known in the industry write their own CRI codes and also write their own CNI related codes, so as to implement the call of network plug-ins.
Disclosure of Invention
The application provides a method for calling a network plug-in, which aims to solve the technical problem of large code quantity when the network plug-in is called in the prior art.
The application provides a method for calling a network plug-in, which comprises the following steps:
acquiring a calling request for a network plug-in to be called transmitted by a container runtime interface;
determining a calling interface used for calling the network plug-in the interface frame according to the calling request;
obtaining a network plug-in matched with the network plug-in to be called according to the determined calling interface for calling the network plug-in the interface frame;
transmitting the matched network plug-in to the container runtime interface.
In some embodiments, further comprising:
and creating an interface frame for calling the network plug-in, wherein the interface frame comprises a calling interface for calling the network plug-in.
In some embodiments, the creating an interface framework for invoking a web plug-in includes:
and generating a data structure body for transmitting the interface parameters in the calling interface.
In some embodiments, the data structure of the request parameter in the call request is the defined data structure for passing the interface parameter in the call interface.
In some embodiments, further comprising:
adding a reserved field parameter for describing a network function in a calling interface of the interface framework;
the acquiring of the call request for the network plug-in to be called transmitted by the container runtime interface includes:
acquiring request parameters including field parameters requiring network functions in a calling request for the network plug-in to be called transmitted by a container runtime interface.
In some embodiments, the obtaining, according to the determined calling interface for calling the network plug-in the interface framework, the network plug-in matched with the network plug-in to be called includes:
modifying the reserved field parameters according to the field parameters;
and obtaining the network plug-in matched with the reserved field parameter according to the modified reserved field parameter.
In some embodiments, further comprising:
setting a transmission mode for transmitting calling information to the container runtime interface;
the transmitting the matched network plug-in to the container runtime interface includes:
and transmitting the matched network plug-in to the container runtime interface according to the transmission mode.
In some embodiments, the setting a transmission mode for transmitting the call information to the container runtime interface includes:
and setting a transmission mode for transmitting the calling information to the container runtime interface according to the calling request sent by the container runtime interface.
In some embodiments, the setting, according to the call request sent by the container runtime interface, a transmission manner for transmitting call information to the container runtime interface includes at least one of the following manners:
setting the calling mode as a mode of returning to a network plug-in according to the information which is carried by the calling request and determines to call the calling interface;
and setting the calling mode as a return-to-empty implementation mode according to the information which is carried by the calling request and used for calling the calling interface negatively.
The present application further provides a device for calling a network plug-in, including:
the acquisition unit is used for acquiring a calling request for the network plug-in to be called transmitted by the container runtime interface;
the determining unit is used for determining a calling interface used for calling the network plug-in the interface framework according to the calling request;
the obtaining unit is used for obtaining the network plug-in matched with the network plug-in to be called according to the determined calling interface used for calling the network plug-in the interface frame;
and the transmission unit is used for transmitting the matched network plug-in to the container runtime interface.
In some embodiments, further comprising:
the system comprises a creating unit used for creating an interface frame used for calling the network plug-in, wherein the interface frame comprises a calling interface for calling the network plug-in.
The application also provides a method for creating the interface framework, which comprises the following steps:
defining a calling interface for calling the network plug-in by a container runtime interface, wherein the calling interface comprises interface parameters;
generating a data structure body for transmitting the interface parameters in the calling interface;
setting a transmission mode for transmitting calling information to the container runtime interface;
and integrating the data structure body and the transmission mode to form an interface framework.
In some embodiments, the defining the container runtime interface calls a call interface of a web plug-in, including:
and adding a reserved field parameter for describing a network function in the calling interface.
In some embodiments, the setting a transmission mode for transmitting the call information to the container runtime interface includes:
and setting a transmission mode for transmitting the calling information to the container runtime according to the calling request sent by the container runtime.
In some embodiments, the setting, according to the call request sent by the container runtime interface, a transmission mode for transmitting call information to the container runtime, includes at least one of the following modes: the method comprises the following steps:
setting the calling mode as a mode of returning to a network plug-in according to the information which is carried by the calling request and determines to call the calling interface;
and setting the calling mode as a return-to-empty implementation mode according to the information which is carried by the calling request and used for calling the calling interface negatively.
In some embodiments, the integrating the data structure and the transmission means to form an interface framework includes:
and integrating the interface framework in a packet-dependent mode based on the data structure body and the transmission mode.
The present application also provides an interface framework creation apparatus, including:
the definition unit is used for defining a calling interface for calling the network plug-in by the interface when the container runs, wherein the calling interface comprises interface parameters;
the generating unit is used for generating a data structure body for transmitting the interface parameters in the calling interface;
the setting unit is used for setting a transmission mode for transmitting the calling information to the container runtime interface;
and the integration unit is used for integrating the data structure body and the transmission mode to form an interface frame.
The application also provides a computer storage medium for storing the data generated by the network platform and a program for processing the data generated by the network platform;
when read and executed by the processor, the program performs the following operations:
acquiring a calling request for a network plug-in to be called transmitted by a container runtime interface;
determining a calling interface used for calling the network plug-in the interface frame according to the calling request;
obtaining a network plug-in matched with the network plug-in to be called according to the determined calling interface for calling the network plug-in the interface frame;
transmitting the matched network plug-in to the container runtime interface.
The present application further provides an electronic device, comprising:
a processor;
a memory for storing a program for processing network platform generated data, the program when read and executed by the processor performing the following operations:
acquiring a calling request for a network plug-in to be called transmitted by a container runtime interface;
determining a calling interface used for calling the network plug-in the interface frame according to the calling request;
obtaining a network plug-in matched with the network plug-in to be called according to the determined calling interface for calling the network plug-in the interface frame;
transmitting the matched network plug-in to the container runtime interface.
Compared with the prior art, the method has the following advantages:
the application provides a calling method of a network plug-in, a calling request of the network plug-in to be called is operated through an acquired container, a calling interface used for calling the network plug-in an interface frame is determined according to the calling request, the network plug-in matched with the network plug-in to be called is obtained according to the determined calling interface, and the network plug-in is transmitted to the container operation interface, so that the upper layer container operation interface can be called through the interface frame when calling the bottom layer network plug-in, the interface frame can call a protocol based on the container network interface, the function requirement required in the operation of the container can be met, a large amount of repeated code writing work caused by providing different protocols aiming at different end sides in the calling process is avoided, and the function expansibility of the calling interface can be improved by adding a reserved field parameter used for describing network functions in the calling interface, namely, the network plug-in with the network function is determined to be transmitted to the container runtime interface according to the network function required in the call request.
In addition, the application also provides a method for creating an interface framework, which calls a calling interface of the network plug-in and a data structure body generated according to interface parameters in the calling interface by defining a container runtime interface; and setting up to the transmission mode of interface transmission calling information during the container operation, will data structure body and transmission mode integrate and form the interface frame, through the interface frame realizes the call of upper container operation interface to bottom network plug-in layer, avoids calling in-process need provide different agreements and a large amount of repeated code writing work that cause to different terminal sides, interface frame code interface is clear and simple, and can also include the reservation field parameter that is used for describing the network function in the calling interface, therefore the interface frame still has the extensible ability.
Drawings
FIG. 1 is a flowchart of an embodiment of a method for invoking a network plug-in provided by the present application;
FIG. 2 is a schematic diagram of an interaction process in a network plug-in calling method provided by the present application;
FIG. 3 is a schematic structural diagram of an embodiment of a calling device of a network plug-in provided in the present application;
FIG. 4 is a flow chart of an embodiment of a method for creating an interface framework provided by the present application;
fig. 5 is a schematic structural diagram of an embodiment of an interface framework creation apparatus provided in the present application.
Detailed Description
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present application. This application is capable of implementation in many different ways than those herein set forth and of similar import by those skilled in the art without departing from the spirit of this application and is therefore not limited to the specific implementations disclosed below.
The terminology used in the description herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. The description used in this application and in the appended claims is for example: the terms "a," "an," "first," and "second," etc., are not intended to be limiting in number or order, but rather are used to distinguish one type of information from another.
Referring to fig. 1, fig. 1 is a flowchart of an embodiment of a method for calling a network plug-in provided by the present application, where the method for calling the network plug-in includes:
step S101: and acquiring a calling request for the network plug-in to be called transmitted by the container runtime interface.
Some technical terms involved in the step S101 are explained first.
The container Runtime interface is an interface (API) for communicating with kubernets during the operation of the container, and is referred to as cri (container Runtime interface); the container runtime is an application located at the bottom layer of the Kubernetes node and responsible for starting and stopping the container, for example: docker, and the like; the so-called Kubernetes, which may be referred to as K8s, is an open source system for automatically deploying, extending, and managing containerized applications. Kubernetes manages container clusters (Pod), which can complete the network resource setting of container clusters (Pod) in the form of network plug-ins, and therefore, the network plug-ins need to be called to acquire network resources.
The specific implementation process of step S101 is that Kubernetes designs a container cluster object (Pod), and packages each service process into a corresponding Pod to make the service process become a container (container running) running in the Pod, and when the container is used, the container running needs to obtain corresponding data information to implement running or processing, so that a request for obtaining corresponding data information needs to be generated, and the data information needs to be transferred to a network plug-in at a bottom layer to find corresponding data information or obtain permission for running the container, and then the interface framework obtains a transfer request from an upper layer container running, where the transfer request includes the data information needed to be obtained by the container running interface, and the data information may be information for transferring the network plug-in.
Step S102: and determining a calling interface used for calling the network plug-in the interface framework according to the calling request.
Step S102 needs to obtain a call interface for calling a network plug-in the interface framework according to the call request to call the underlying network plug-in, and therefore, the method further includes:
and creating an interface frame for calling the network plug-in, wherein the interface frame comprises a calling interface for calling the network plug-in.
The call interface for calling the network plug-in may include an initialization interface (Init) for initializing a container runtime, a get network plug-in name interface (Getname), a get extended functions interface (GetCapabilities), a network setup interface (setup network), an offload network interface (teardown network), an abnormal state interface (statusror), a get Pod network information interface (getmodnetworkstatus), a load configuration file interface (L oadFromConfig), an update network configuration interface (updatepodcid), and the like.
Based on the above, in order to ensure the security of the interface parameter in the calling interface in the transmission process, the method may further include:
and generating a data structure body for transmitting the interface parameters in the calling interface.
The generating of the data structure body may specifically be generating the data structure body by encapsulating the obtained interface parameter of the call interface.
It can be understood that, when the container runtime interface sends a call request and a network plug-in is performed through a call interface in the interface framework, the data structure of the sent request parameter may be the same as the data structure of the interface parameter in the call interface in the interface framework, and therefore, in this embodiment, the data structure of the request parameter in the call request is the defined data structure for passing the interface parameter in the call interface.
In order to satisfy the requirement that the container runtime interface can obtain a network plug-in with corresponding functions according to the functions required to be provided, the method may further include:
and adding a reserved field parameter for describing a network function in a calling interface of the interface framework.
It should be noted that the reserved field parameter (indication) may be added for each calling interface, and the reserved field parameter and other parameters in the calling interface generate a data structure together; the reserved field parameter (announcement) can also be added to the call interface in a targeted manner as required.
The reserved field parameter may be identification information set for a certain network function, such as: the method is used for configuring and calling the network plug-in with the reserved field parameter A (also can be understood as network function A) in a configuration file in advance, when the network plug-in with the network function A is called through a container runtime interface, an underlying network plug-in layer searches the network plug-in with the reserved field parameter A, and when the network plug-in with the reserved field parameter A is found, the network plug-in is transmitted to the container runtime interface of an upper layer. The specific calling procedure may continue to look at the following only for the purpose of describing the contents of the reserved field parameters.
Based on the addition of the reserved field parameter for describing the network function, the step S101 obtains a call request for the network plug-in to be called from the container runtime interface transmission, including:
acquiring request parameters including field parameters requiring network functions in a calling request for the network plug-in to be called transmitted by a container runtime interface.
That is to say, the data structure body for acquiring the request parameter in the call request for the network plug-in to be called transmitted by the container runtime interface may include a field parameter requiring a network function. When the upper container runtime interface needs to call a network plug-in having a certain network function, a field parameter of the network function may be set in the call request, and then the request parameter and the field parameter are generated into a data structure and sent to the interface framework, and the interface framework refers to the description of step S103 after receiving the call request including the field parameter.
In this embodiment, the reserved field parameter may be set in the initialization interface.
In this embodiment, according to different requests sent by the upper container runtime interface, a transmission manner of the interface framework may be set, and therefore, the method may further include:
and setting a transmission mode for transmitting the calling information to the container operation.
The transmission of the call information by the set transmission method may be performed with respect to the call request sent by the container runtime interface.
The transmission mode can ensure that the upper layer container runtime interface transmits corresponding transmission information according to different call requests when sending the call requests, for example: if the sent call request is only that the network plug-in information does not need to be provided or does not exist, the null implementation can be returned, that is, no operation is performed, for example: when the calling request is information that any network plug-in is not called, empty implementation can be returned, and the empty implementation can be understood as empty operation; or, when the corresponding network plug-in is not found according to the calling request, the null implementation can be returned, and the null time can be understood as null information; if the network plug-in information is found to provide the need, the network plug-in information may be returned.
It will be appreciated that the invocation request may be sent from the upper container runtime without providing network plug-in information, which may be returned as a null implementation. When determining to call the network plug-in with the set network function according to the reserved field parameter in the call request, if the network plug-in without the set network function does not have the return empty information, and when the network plug-in providing the required network plug-in information or the network plug-in with the set network function is found, the information of the network plug-in or the information of the network plug-in with the network function can be returned. That is, when the network plug-in is transmitted to the container runtime, the network plug-in may be transmitted to the container runtime interface in different transmission manners according to parameter conditions in the call request.
Therefore, the transmission mode for transmitting the call information to the container runtime interface is set according to the call request sent by the container runtime interface, and includes at least one of the following modes:
setting the calling mode as a mode of returning to a network plug-in according to the information which is carried by the calling request and determines to call the calling interface;
and setting the calling mode as a return-to-empty implementation mode according to the information which is carried by the calling request and used for calling the calling interface negatively.
It should be noted that when the invocation request is only that the network plug-in information is not required to be provided or the network plug-in information required to be provided does not exist, no information may be returned, and therefore, the transmission mode may be only one mode for transmitting the network plug-in.
Step S103: and obtaining the network plug-in matched with the network plug-in to be called according to the determined calling interface for calling the network plug-in the interface frame.
Based on the above description of step S102, when a network plug-in is called, and a corresponding network plug-in needs to be called for a call request with a set network function requested in the call request, step S103 includes:
modifying the reserved field parameters according to the field parameters;
and obtaining the network plug-in matched with the reserved field parameter according to the modified reserved field parameter.
Referring to fig. 2 in conjunction with fig. 1, fig. 2 is a schematic diagram of an interaction process in a network plug-in calling method provided in the present application, and after an interface framework receives a calling request from an upper container runtime interface, a reserved field parameter in the calling interface is modified into a field parameter in the calling request, and then a network function network plug-in corresponding to the reserved field parameter is found in a network plug-in layer through the modified reserved field parameter, and a network plug-in end side sends a search result to the interface framework.
The specific implementation process of step S103 may be a network plug-in layer, and the network plug-in layer may implement the call of the network plug-in according to the information in the request parameter through a call interface, for example: the calling interface performs corresponding configuration according to the request parameters, such as: the parameters in the init interface need to initialize the needed configuration file path, self-defined plug-in naming, and information such as reserved field parameters. And after receiving the information sent by the calling interface, the network plug-in layer searches for the network plug-in matched with the information sent by the calling interface and transmits the network plug-in to the calling interface.
Step S104: transmitting the network plug-in to the container runtime interface.
The step S104 sends or provides the network plug-in to the container runtime interface according to the network plug-in obtained in the step S103; the network plug-in can provide corresponding network resource information for the upper-layer container through the container runtime interface. The network resource information of the container may include: the virtual network card, the IP address, the DNS, the network route and the like, and the network resource information can realize the corresponding network configuration of the container through the CNI network plug-in.
The above is a description of an embodiment of a method for calling a network plug-in provided by the present application. Corresponding to the foregoing embodiment of the method for invoking a network plug-in, the present application also discloses an embodiment of a device for invoking a network plug-in, please refer to fig. 3, since the device embodiment is basically similar to the method embodiment, the description is relatively simple, and related points can be referred to the partial description of the method embodiment. The device embodiments described below are merely illustrative.
As shown in fig. 3, fig. 3 is a schematic structural diagram of an embodiment of a network plug-in calling device provided in the present application. The device includes:
an obtaining unit 301, configured to obtain a call request for a network plug-in to be called, where the call request is transmitted from a container runtime interface.
The calling request comprises parameter information of the network plug-in to be called.
A determining unit 302, configured to determine, according to the call request, a call interface in the interface framework for calling the network plug-in.
The determining unit 302 needs to obtain a calling interface for calling a network plug-in an interface framework according to the call request in the obtaining unit 301 to call the underlying network plug-in, and therefore, the method further includes:
the system comprises a creating unit used for creating an interface frame used for calling the network plug-in, wherein the interface frame comprises a calling interface for calling the network plug-in.
The call interface for calling the network plug-in may include an initialization interface (Init) for initializing a container runtime, a get network plug-in name interface (Getname), a get extended functions interface (GetCapabilities), a network setup interface (setup network), an offload network interface (teardown network), an abnormal state interface (StatusError), a get Pod network information interface (getmodnetworkstatus), a load configuration file interface (L oadFromConfig), an update network configuration interface (updatepodeidcr), and the like
Based on the above, in order to ensure the security of the interface parameter in the calling interface in the transmission process, the method may further include:
and the generating unit is used for generating a data structure body for transmitting the interface parameters in the calling interface.
The generating of the data structure body may specifically be generating the data structure body by encapsulating the obtained interface parameter of the call interface.
It can be understood that, when the container runtime interface sends a call request and a network plug-in is performed through a call interface in the interface framework, the data structure of the sent request parameter may be the same as the data structure of the interface parameter in the call interface in the interface framework, and therefore, in this embodiment, the data structure of the request parameter in the call request is the defined data structure for passing the interface parameter in the call interface.
In order to satisfy the requirement that the container runtime interface can obtain a network plug-in with corresponding functions according to the functions required to be provided, the method may further include:
and the adding unit is used for adding a reserved field parameter for describing a network function in a calling interface of the interface framework.
It should be noted that the reserved field parameter (indication) may be added for each calling interface, and the reserved field parameter and other parameters in the calling interface generate a data structure together; the reserved field parameter (announcement) can also be added to the call interface in a targeted manner as required.
Based on the reserved field parameter added to describe the network function, the obtaining unit 301 obtains the call request for the network plug-in to be called from the container runtime interface, and specifically may be configured to obtain a request parameter including a field parameter requiring the network function in the call request for the network plug-in to be called from the container runtime interface. That is to say, the data structure body for acquiring the request parameter in the call request for the network plug-in to be called transmitted by the container runtime interface may include a field parameter requiring a network function. When the upper container runtime interface needs to call a network plug-in with a certain network function, a field parameter of the network function may be set in the call request, and then the request parameter and the field parameter are generated into a data structure and sent to the interface framework, and the interface framework refers to the description of the obtaining unit 303 after receiving the call request including the field parameter.
In this embodiment, the reserved field parameter may be set in the initialization interface.
In this embodiment, according to different requests sent by the upper container runtime interface, a transmission manner of the interface framework may be set, and therefore, the method may further include:
and the transmission unit is used for setting a transmission mode for transmitting the calling information to the container operation.
The transmission of the call information by the set transmission method may be performed with respect to the call request sent by the container runtime interface.
The transmission mode can ensure that when the upper container sends a call request, corresponding transmission information is transmitted according to different request requirements, for example: if the sent call request is only that the network plug-in information does not need to be provided or does not exist, the null implementation can be returned, that is, no operation is performed, for example: when the calling request is information that any network plug-in is not called, empty implementation can be returned, and the empty implementation can be understood as empty operation; or, when the corresponding network plug-in is not found according to the calling request, the null implementation can be returned, and the null time can be understood as null information; if the network plug-in information is found to provide the need, the network plug-in information may be returned.
It will be appreciated that the invocation request may be sent from the upper container runtime without providing network plug-in information, which may be returned as a null implementation. When determining to call the network plug-in with the set network function according to the reserved field parameter in the call request, if the network plug-in without the set network function does not have the return empty information, and when the network plug-in providing the required network plug-in information or the network plug-in with the set network function is found, the information of the network plug-in or the information of the network plug-in with the network function can be returned. That is, when the network plug-in is transmitted to the container runtime, the network plug-in may be transmitted to the container runtime interface in different transmission manners according to parameter conditions in the call request.
Therefore, the transmission mode for transmitting the call information to the container runtime interface is set according to the call request sent by the container runtime interface, and includes at least one of the following modes:
setting the calling mode as a mode of returning to a network plug-in according to the information which is carried by the calling request and determines to call the calling interface;
and setting the calling mode as a return-to-empty implementation mode according to the information which is carried by the calling request and used for calling the calling interface negatively.
It should be noted that when the invocation request is only that the network plug-in information is not required to be provided or the network plug-in information required to be provided does not exist, no information may be returned, and therefore, the transmission mode may be only one mode for transmitting the network plug-in.
An obtaining unit 303, configured to obtain, according to the determined call interface in the interface framework for calling the network plug-in, the network plug-in matched with the network plug-in to be called.
Based on the description of the determining unit 202, when the network plug-in is called, and a call request with a set network function is requested in the call request, the obtaining unit 303 may include:
a modification subunit, configured to modify the reserved field parameter according to the field parameter;
and the obtaining subunit is used for obtaining the network plug-in matched with the reserved field parameter according to the modified reserved field parameter.
As shown in fig. 2, fig. 2 is a schematic diagram of an interaction process in a network plug-in calling method provided by the present application, when an interface framework receives a call request from an upper container runtime interface, a reserved field parameter in the call interface is modified into a field parameter in the call request, then the modified reserved field parameter is used to find a network function network plug-in corresponding to the reserved field parameter in a network plug-in layer, and a network plug-in end side sends a search result to the interface framework.
The result of the network plug-in matched with the network plug-in to be called, which is obtained by the obtaining unit 303, may be obtained by sending through a network plug-in layer, that is, the network plug-in layer may implement calling of the network plug-in according to the information in the request parameter through a calling interface, for example: the calling interface performs corresponding configuration according to the request parameters, such as: the parameters in the init interface need to initialize the needed configuration file path, self-defined plug-in naming, and information such as reserved field parameters. And after receiving the information sent by the calling interface, the network plug-in layer searches for the network plug-in matched with the information sent by the calling interface and transmits the network plug-in to the calling interface.
A transmission unit 304, configured to transmit the network plug-in to the container runtime interface, that is, to send or provide the network plug-in to the container runtime interface according to the network plug-in obtained in the obtaining unit 304.
The above is a description of an embodiment of a network plug-in calling device provided in the present application, and with reference to the above contents, the present application further provides an interface framework creating method, please refer to fig. 4, where fig. 4 is a flowchart of an embodiment of an interface framework creating method provided in the present application, and the creating method includes:
step S401: defining a calling interface for calling the network plug-in by a container runtime interface, wherein the calling interface comprises interface parameters.
In this embodiment, the defined call interface may include an initialization interface (Init) for initializing a container runtime, a get network plug-in name interface (Getname), a get extended functionality interface (GetCapabilities), a get extended functionality list provided by a network plug-in, a network setup interface (setup network), which calls the network plug-in to set up a network after a Pod is created and before any other container is created, an unload network interface (teardown network), an exception status interface (StatusError), which obtains whether an exception status exists for a current network plug-in, a get Pod network information interface (getnetworkstatus), a load configuration file interface (L oadFromConfig), which loads interface parameters according to a network container interface (CNI) configuration file, an update network configuration interface (updatepodcid), a CIDR configuration for dynamically updating a network, and the like.
In order to satisfy the requirement that the container runtime interface can obtain a network plug-in with corresponding functions according to the functions required to be provided, the method may further include:
a reserved field parameter for describing a network function may be added in the call interface.
It should be noted that the reserved field parameter (indication) may be added for each calling interface, and the reserved field parameter and other parameters in the calling interface generate a data structure together; the reserved field parameter (announcement) can also be added to the call interface in a targeted manner as required.
In this embodiment, the reserved field parameter may be set in the initialization interface.
Step S402: and defining a data structure body for transmitting the interface parameters in the calling interface.
The definition of the data structure body may specifically be that the data structure body is generated by encapsulating the obtained interface parameters of the call interface.
The data structure may further include basic information required to describe a network created for a Pod, for example: namespace path, Pod id and/or network settings, etc., i.e., a configuration file that invokes a network plug-in.
It can be understood that, when the container runtime interface sends a call request and a network plug-in is performed through a call interface in the interface framework, the data structure of the sent request parameter may be the same as the data structure of the interface parameter in the call interface in the interface framework, and therefore, in this embodiment, the data structure of the request parameter in the received call request is the defined data structure that passes the interface parameter in the call interface.
The data structure may include data information of a configuration file related to the network plug-in, or data information of a configuration file related to the network plug-in, reserved field parameter information, and the like. Step S403: and setting a transmission mode for transmitting the calling information to the container runtime interface.
The transmission of the call information by the set transmission method may be performed with respect to the call request sent by the container runtime interface.
The transmission mode can ensure that the upper layer container runtime interface transmits corresponding transmission information according to different call requests when sending the call requests, for example: if the sent calling request is only the network plug-in information which does not need to be provided or the network plug-in information which needs to be provided does not exist, empty implementation can be returned; i.e. not performing any operations, such as: when the calling request is information that any network plug-in is not called, empty implementation can be returned, and the empty implementation can be understood as empty operation; or, when the corresponding network plug-in is not found according to the calling request, the null implementation can be returned, and the null time can be understood as null information; if the network plug-in information is found to provide the need, the network plug-in information may be returned.
It will be appreciated that the invocation request may be sent from the upper container runtime without providing network plug-in information, which may be returned as a null implementation. When determining to call the network plug-in with the set network function according to the reserved field parameter in the call request, if the network plug-in without the set network function does not have the return empty information, and when the network plug-in providing the required network plug-in information or the network plug-in with the set network function is found, the information of the network plug-in or the information of the network plug-in with the network function can be returned. That is, when the network plug-in is transmitted to the container runtime, the network plug-in may be transmitted to the container runtime interface in different transmission manners according to parameter conditions in the call request.
Therefore, the transmission mode for transmitting the call information to the container runtime interface is set according to the call request sent by the container runtime interface, and includes at least one of the following modes:
setting the calling mode as a mode of returning to a network plug-in according to the information which is carried by the calling request and determines to call the calling interface;
and setting the calling mode as a return-to-empty implementation mode according to the information which is carried by the calling request and used for calling the calling interface negatively.
It should be noted that when the invocation request is only that the network plug-in information is not required to be provided or the network plug-in information required to be provided does not exist, no information may be returned, and therefore, the transmission mode may be only one mode for transmitting the network plug-in.
It should be noted that when the invocation request is only that the network plug-in information is not required to be provided or the network plug-in information required to be provided does not exist, no information may be returned, and therefore, the transmission mode may be only one mode for transmitting the network plug-in. Wherein the return null implementation may be understood as not performing any operation.
Step S404: and integrating the data structure body and the transmission mode to form an interface framework.
In step S404, the interface framework may be integrated in a packet-dependent manner based on the data structure and the transmission manner.
In this embodiment, the container network interface calling protocol may be integrated into the interface framework, and the underlying network plug-in may be called by the container network runtime interface calling protocol.
For the description of the embodiment of the creation method of the interface framework provided by the present application, the description process of the creation embodiment of the interface framework is summarized, and specific contents may be combined with the description of the embodiment of the calling method of the network plug-in provided by the foregoing. Based on the method for creating the interface frame provided by the present application, the present application further discloses an embodiment of an apparatus for creating the interface frame, please refer to fig. 5, since the embodiment of the apparatus is basically similar to the embodiment of the method, the description is relatively simple, and related points can be referred to only part of the description of the embodiment of the method. The device embodiments described below are merely illustrative.
As shown in fig. 5, the interface framework creation apparatus provided in the present application includes:
the defining unit 501 is configured to define a calling interface for calling the network plug-in by the container runtime interface, where the calling interface includes interface parameters.
The call interface defined in the definition unit 501 may include an initialization interface (Init) for initializing a container runtime, a get network plug-in name interface (Getname), a get extended functions interface (GetCapabilities), a get extended functions list provided by a network plug-in, a network setup interface (setup network), which calls the network plug-in to set up a network after a Pod is created and before any other container is created, an unload network interface (teardownletwork), an exception state interface (StatusError), which obtains whether an exception state exists in a current network plug-in, a get Pod network information interface (getprodotstatus), a load configuration file interface (L oadFromConfig), which loads interface parameters according to a network container interface (CNI) configuration file, an update network configuration interface (updatepodicddr), which dynamically updates a CIDR configuration of the network, and the like.
It can be understood that, when the container runtime interface sends a call request and a network plug-in is performed through a call interface in the interface framework, the data structure of the sent request parameter may be the same as the data structure of the interface parameter in the call interface in the interface framework, and therefore, in this embodiment, the data structure of the request parameter in the received call request is the defined data structure that passes the interface parameter in the call interface.
The data structure may include data information of a configuration file related to the network plug-in, or data information of a configuration file related to the network plug-in, reserved field parameter information, and the like.
The generating unit 502 is configured to generate a data structure for transferring the interface parameter in the calling interface.
The definition of the data structure body may specifically be that the data structure body is generated by encapsulating the obtained interface parameters of the call interface.
A setting unit 503, configured to set a transmission mode for transmitting the call information to the container runtime interface.
The setting unit 503 may transmit the call information in a set transmission manner according to the call request sent by the container runtime interface.
The transmission mode can ensure that the upper layer container runtime interface transmits corresponding transmission information according to different call requests when sending the call requests, for example: if the sent calling request is only the network plug-in information which does not need to be provided or the network plug-in information which needs to be provided does not exist, empty implementation can be returned; i.e. not performing any operations, such as: when the calling request is information that any network plug-in is not called, empty implementation can be returned, and the empty implementation can be understood as empty operation; or, when the corresponding network plug-in is not found according to the calling request, the null implementation can be returned, and the null time can be understood as null information; if the network plug-in information is found to provide the need, the network plug-in information may be returned.
It will be appreciated that the invocation request may be sent from the upper container runtime without providing network plug-in information, which may be returned as a null implementation. When determining to call the network plug-in with the set network function according to the reserved field parameter in the call request, if the network plug-in without the set network function does not have the return empty information, and when the network plug-in providing the required network plug-in information or the network plug-in with the set network function is found, the information of the network plug-in or the information of the network plug-in with the network function can be returned. That is, when the network plug-in is transmitted to the container runtime, the network plug-in may be transmitted to the container runtime interface in different transmission manners according to parameter conditions in the call request.
Therefore, the transmission mode for transmitting the call information to the container runtime interface is set according to the call request sent by the container runtime interface, and includes at least one of the following modes:
setting the calling mode as a mode of returning to a network plug-in according to the information which is carried by the calling request and determines to call the calling interface;
and setting the calling mode as a return-to-empty implementation mode according to the information which is carried by the calling request and used for calling the calling interface negatively.
It should be noted that when the invocation request is only that the network plug-in information is not required to be provided or the network plug-in information required to be provided does not exist, no information may be returned, and therefore, the transmission mode may be only one mode for transmitting the network plug-in.
It should be noted that when the invocation request is only that the network plug-in information is not required to be provided or the network plug-in information required to be provided does not exist, no information may be returned, and therefore, the transmission mode may be only one mode for transmitting the network plug-in. Wherein the return null implementation may be understood as not performing any operation.
And an integrating unit 504, configured to integrate the data structure and the transmission mode to form an interface framework.
The integration unit 504 may specifically integrate the interface framework in a packet-dependent manner based on the data structure and the transmission manner.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
1. Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include non-transitory computer readable media (transient media), such as modulated data signals and carrier waves.
2. As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
Although the present application has been described with reference to the preferred embodiments, it is not intended to limit the present application, and those skilled in the art can make variations and modifications without departing from the spirit and scope of the present application, therefore, the scope of the present application should be determined by the claims that follow.
Claims (19)
1. A method for calling a network plug-in, comprising:
acquiring a calling request for a network plug-in to be called transmitted by a container runtime interface;
determining a calling interface used for calling the network plug-in the interface frame according to the calling request;
obtaining a network plug-in matched with the network plug-in to be called according to the determined calling interface for calling the network plug-in the interface frame;
transmitting the matched network plug-in to the container runtime interface.
2. The method for calling the network plug-in according to claim 1, further comprising:
and creating an interface frame for calling the network plug-in, wherein the interface frame comprises a calling interface for calling the network plug-in.
3. The method for invoking network plugin according to claim 2, wherein the creating an interface framework for invoking network plugin comprises:
and generating a data structure body for transmitting the interface parameters in the calling interface.
4. The method according to claim 3, wherein the data structure of the request parameter in the call request is the defined data structure for passing the interface parameter in the call interface.
5. The method for calling the network plug-in according to claim 2, further comprising:
adding a reserved field parameter for describing a network function in a calling interface of the interface framework;
the acquiring of the call request for the network plug-in to be called transmitted by the container runtime interface includes:
acquiring request parameters including field parameters requiring network functions in a calling request for the network plug-in to be called transmitted by a container runtime interface.
6. The method for calling the network plug-in according to claim 5, wherein the obtaining the network plug-in matched with the network plug-in to be called according to the determined calling interface for calling the network plug-in the interface framework comprises:
modifying the reserved field parameters according to the field parameters;
and obtaining the network plug-in matched with the reserved field parameter according to the modified reserved field parameter.
7. The method for calling the network plug-in according to claim 1, further comprising:
setting a transmission mode for transmitting calling information to the container runtime interface;
the transmitting the network plug-in to the container runtime interface includes:
and transmitting the network plug-in to the container runtime interface according to the transmission mode.
8. The method for calling the network plug-in according to claim 7, wherein the setting of a transmission mode for transmitting the calling information to the container runtime interface comprises:
and setting a transmission mode for transmitting the calling information to the container runtime interface according to the calling request sent by the container runtime interface.
9. The method for calling the network plug-in according to claim 8, wherein the setting of the transmission mode for transmitting the call information to the container runtime interface according to the call request sent by the container runtime interface includes at least one of the following modes:
setting the calling mode as a mode of returning to a network plug-in according to the information which is carried by the calling request and determines to call the calling interface;
and setting the calling mode as a return-to-empty implementation mode according to the information which is carried by the calling request and used for calling the calling interface negatively.
10. An apparatus for invoking a network plug-in, comprising:
the acquisition unit is used for acquiring a calling request for the network plug-in to be called transmitted by the container runtime interface;
the determining unit is used for determining a calling interface used for calling the network plug-in the interface framework according to the calling request;
the obtaining unit is used for obtaining the network plug-in matched with the network plug-in to be called according to the determined calling interface used for calling the network plug-in the interface frame;
and the transmission unit is used for transmitting the matched network plug-in to the container runtime interface.
11. The calling device of the network plug-in of claim 9, further comprising:
the system comprises a creating unit used for creating an interface frame used for calling the network plug-in, wherein the interface frame comprises a calling interface for calling the network plug-in.
12. A method for creating an interface framework, comprising:
defining a calling interface for calling the network plug-in by a container runtime interface, wherein the calling interface comprises interface parameters;
generating a data structure body for transmitting the interface parameters in the calling interface;
setting a transmission mode for transmitting calling information to the container runtime interface;
and integrating the data structure body and the transmission mode to form an interface framework.
13. The method for creating the interface framework according to claim 12, wherein the definition container runtime interface calls a calling interface of a network plug-in, comprising:
and adding a reserved field parameter for describing a network function in the calling interface.
14. The method for creating the interface framework according to claim 12, wherein the setting a transmission mode for transmitting the call information to the container runtime interface includes:
and setting a transmission mode for transmitting the calling information to the container runtime according to the calling request sent by the container runtime.
15. The method for creating the interface framework according to claim 14, wherein the setting of the transmission mode for transmitting the call information to the container runtime according to the call request sent by the container runtime interface includes at least one of the following modes: the method comprises the following steps:
setting the calling mode as a mode of returning to a network plug-in according to the information which is carried by the calling request and determines to call the calling interface;
and setting the calling mode as a return-to-empty implementation mode according to the information which is carried by the calling request and used for calling the calling interface negatively.
16. The method for creating an interface framework according to claim 12, wherein the integrating the data structure and the transmission method to form the interface framework comprises:
and integrating the interface framework in a packet-dependent mode based on the data structure body and the transmission mode.
17. An apparatus for creating an interface framework, comprising:
the definition unit is used for defining a calling interface for calling the network plug-in by the interface when the container runs, wherein the calling interface comprises interface parameters;
the generating unit is used for generating a data structure body for transmitting the interface parameters in the calling interface;
the setting unit is used for setting a transmission mode for transmitting the calling information to the container runtime interface;
and the integration unit is used for integrating the data structure body and the transmission mode to form an interface frame.
18. A computer storage medium for storing network platform generated data and a program for processing the network platform generated data;
when read and executed by the processor, the program performs the following operations:
acquiring a calling request for a network plug-in to be called transmitted by a container runtime interface;
determining a calling interface used for calling the network plug-in the interface frame according to the calling request;
obtaining a network plug-in matched with the network plug-in to be called according to the determined calling interface for calling the network plug-in the interface frame;
transmitting the matched network plug-in to the container runtime interface.
19. An electronic device, comprising:
a processor;
a memory for storing a program for processing network platform generated data, the program when read and executed by the processor performing the following operations:
acquiring a calling request for a network plug-in to be called transmitted by a container runtime interface;
determining a calling interface used for calling the network plug-in the interface frame according to the calling request;
obtaining a network plug-in matched with the network plug-in to be called according to the determined calling interface for calling the network plug-in the interface frame;
transmitting the matched network plug-in to the container runtime interface.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811609445.4A CN111400054B (en) | 2018-12-27 | 2018-12-27 | Network plug-in calling method and device, computer storage medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811609445.4A CN111400054B (en) | 2018-12-27 | 2018-12-27 | Network plug-in calling method and device, computer storage medium and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111400054A true CN111400054A (en) | 2020-07-10 |
| CN111400054B CN111400054B (en) | 2024-03-08 |
Family
ID=71430127
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811609445.4A Active CN111400054B (en) | 2018-12-27 | 2018-12-27 | Network plug-in calling method and device, computer storage medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111400054B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113220422A (en) * | 2021-06-03 | 2021-08-06 | 上海天旦网络科技发展有限公司 | Method and system for modifying Pod network interface based on operation of CNI plug-in K8s |
Citations (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030187869A1 (en) * | 2002-02-07 | 2003-10-02 | De Bonet Jeremy S. | Plug-in API for modulcar network transaction processing |
| US20040221299A1 (en) * | 2003-03-31 | 2004-11-04 | Simon Gibbs | Method and apparatus for developing interface protocols for peer to peer applications |
| JP2007310807A (en) * | 2006-05-22 | 2007-11-29 | Ricoh Co Ltd | Plug-in version management system |
| US20080295074A1 (en) * | 2007-05-25 | 2008-11-27 | Schneider James P | Data management interface with configurable plugins |
| CN101464805A (en) * | 2008-12-24 | 2009-06-24 | 中兴通讯股份有限公司 | Plug-in management method and system thereof |
| US20100106849A1 (en) * | 2008-10-28 | 2010-04-29 | Pixel8 Networks, Inc. | Network-attached media plug-in |
| US20100131652A1 (en) * | 2008-11-21 | 2010-05-27 | Brewis Deon C | Unified interface for configuring multiple networking technologies |
| CN102253840A (en) * | 2011-08-04 | 2011-11-23 | 深圳芯智汇科技有限公司 | Plugin management method and plugin manager |
| CN103294458A (en) * | 2012-02-28 | 2013-09-11 | 鼎亿数码科技(上海)有限公司 | Software development method based on plug-ins |
| CN104104708A (en) * | 2013-04-12 | 2014-10-15 | 宏达国际电子股份有限公司 | Access method of multiple cloud storage spaces and electronic communication device |
| CN107066295A (en) * | 2017-03-30 | 2017-08-18 | 青岛海信电器股份有限公司 | A kind of method and apparatus for the plug-in unit that terminal network application is loaded based on browser |
| CN107995326A (en) * | 2017-12-13 | 2018-05-04 | 北京搜狐新媒体信息技术有限公司 | The management method and device of a kind of capacitor network |
| US20180210745A1 (en) * | 2017-01-25 | 2018-07-26 | Ca, Inc. | Virtual service interface |
| CN108989091A (en) * | 2018-06-22 | 2018-12-11 | 杭州才云科技有限公司 | Based on the tenant network partition method of Kubernetes network, storage medium, electronic equipment |
-
2018
- 2018-12-27 CN CN201811609445.4A patent/CN111400054B/en active Active
Patent Citations (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030187869A1 (en) * | 2002-02-07 | 2003-10-02 | De Bonet Jeremy S. | Plug-in API for modulcar network transaction processing |
| US20040221299A1 (en) * | 2003-03-31 | 2004-11-04 | Simon Gibbs | Method and apparatus for developing interface protocols for peer to peer applications |
| JP2007310807A (en) * | 2006-05-22 | 2007-11-29 | Ricoh Co Ltd | Plug-in version management system |
| US20080295074A1 (en) * | 2007-05-25 | 2008-11-27 | Schneider James P | Data management interface with configurable plugins |
| US20100106849A1 (en) * | 2008-10-28 | 2010-04-29 | Pixel8 Networks, Inc. | Network-attached media plug-in |
| US20100131652A1 (en) * | 2008-11-21 | 2010-05-27 | Brewis Deon C | Unified interface for configuring multiple networking technologies |
| CN101464805A (en) * | 2008-12-24 | 2009-06-24 | 中兴通讯股份有限公司 | Plug-in management method and system thereof |
| CN102253840A (en) * | 2011-08-04 | 2011-11-23 | 深圳芯智汇科技有限公司 | Plugin management method and plugin manager |
| CN103294458A (en) * | 2012-02-28 | 2013-09-11 | 鼎亿数码科技(上海)有限公司 | Software development method based on plug-ins |
| CN104104708A (en) * | 2013-04-12 | 2014-10-15 | 宏达国际电子股份有限公司 | Access method of multiple cloud storage spaces and electronic communication device |
| US20180210745A1 (en) * | 2017-01-25 | 2018-07-26 | Ca, Inc. | Virtual service interface |
| CN107066295A (en) * | 2017-03-30 | 2017-08-18 | 青岛海信电器股份有限公司 | A kind of method and apparatus for the plug-in unit that terminal network application is loaded based on browser |
| CN107995326A (en) * | 2017-12-13 | 2018-05-04 | 北京搜狐新媒体信息技术有限公司 | The management method and device of a kind of capacitor network |
| CN108989091A (en) * | 2018-06-22 | 2018-12-11 | 杭州才云科技有限公司 | Based on the tenant network partition method of Kubernetes network, storage medium, electronic equipment |
Non-Patent Citations (6)
| Title |
|---|
| CONG XU等: "NewGuard:Realizing Network Qos for Kubernets", MIDDLEWARE\'18:PROCEEDINGS OF THE 19TH INTERNATIONAL MIDDLEWARE CONFERENCE INDUSTRY, pages 32 - 38 * |
| HAO ZENG等: "Measurement and Evaluation for Docker Container Networking", pages 105 - 108 * |
| MONSTER-Z: ""深入理解CNI"", pages 1 - 10 * |
| 徐飞: "基于Kubernetes的多租户网络隔离的设计与实现", 中国优秀硕士学位论文全文数据库信息科技辑, pages 139 - 172 * |
| 蔡燕萍;凌捷;黄万民;: "网络安全扫描系统中插件技术的研究与实现", 计算机工程与设计, no. 07 * |
| 赵才文;: "插件化软件开发方法初探", 电脑与电信, no. 11 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113220422A (en) * | 2021-06-03 | 2021-08-06 | 上海天旦网络科技发展有限公司 | Method and system for modifying Pod network interface based on operation of CNI plug-in K8s |
| CN113220422B (en) * | 2021-06-03 | 2022-09-30 | 上海天旦网络科技发展有限公司 | Method and system for modifying Pod network interface based on operation of CNI plug-in K8s |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111400054B (en) | 2024-03-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10701139B2 (en) | Life cycle management method and apparatus | |
| US10862760B2 (en) | Network functions virtualization | |
| CN104219127B (en) | A kind of creation method and equipment of virtual network example | |
| US10498625B1 (en) | Distributed testing service | |
| CN102857370A (en) | Resource allocating method and device | |
| MX2007014337A (en) | Coordinating reference counting between entities executing within separate address spaces. | |
| CN111431956A (en) | Cross-network service access method, device, system and storage medium | |
| CN111124589B (en) | Service discovery system, method, device and equipment | |
| CN111010304A (en) | Method for integrating Dubbo service and Kubernetes system | |
| US20230261950A1 (en) | Method of container cluster management and system thereof | |
| CN116800616A (en) | Management method and related device of virtualized network equipment | |
| CN114020444B (en) | Calling system and method for resource service application in enterprise digital middle station | |
| CN111400054A (en) | Network plug-in calling method and device, computer storage medium and electronic equipment | |
| CN114979286A (en) | Access control method, device and equipment for container service and computer storage medium | |
| CN112738181B (en) | Method, device and server for cluster external IP access | |
| CN114826869A (en) | Device management method and device management system | |
| CN112559164A (en) | Resource sharing method and device | |
| CN111324395A (en) | Calling method, calling device and computer-readable storage medium | |
| KR101997602B1 (en) | Resource Dependency Service Method for M2M Resource Management | |
| EP4318236A1 (en) | Management method and system for computing node | |
| CN113867776B (en) | Method and device for issuing middle-stage application, electronic equipment and storage medium | |
| CN113760325B (en) | Container environment updating method and device | |
| CN113010363B (en) | Container monitoring method under swarm clusters and shared service cloud platform | |
| CN116841720A (en) | Resource allocation method, apparatus, computer device, storage medium and program product | |
| CN114157455A (en) | Data transmission method, device, equipment and storage medium |
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 |