CN111880902A - Pod creation method, device, equipment and readable storage medium - Google Patents
Pod creation method, device, equipment and readable storage medium Download PDFInfo
- Publication number
- CN111880902A CN111880902A CN202010745369.0A CN202010745369A CN111880902A CN 111880902 A CN111880902 A CN 111880902A CN 202010745369 A CN202010745369 A CN 202010745369A CN 111880902 A CN111880902 A CN 111880902A
- Authority
- CN
- China
- Prior art keywords
- pod
- network
- creation
- plug
- task
- 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.)
- Withdrawn
Links
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/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45504—Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators
-
- 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/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- 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/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45562—Creating, deleting, cloning virtual machine instances
-
- 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/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45591—Monitoring or debugging support
-
- 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/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45595—Network integration; Enabling network access in virtual machine instances
Abstract
The invention discloses a method, a device, equipment and a readable storage medium for pod creation, wherein the method comprises the following steps: receiving a pod creation request, and determining a pod creation task and a network type corresponding to the pod creation task; determining a target cni plug-in corresponding to the network type from cni plug-ins of the agents; sending pod create task to target cni plug-in; and after the pod is created, establishing communication connection between the pod and the container cloud platform. The method can be suitable for a domestic container cloud platform, and can be used for randomly specifying the network type of the pod when the pod is created through the proxy cni plug-in, so that the multi-network plane of the Kubernetes cloud platform is realized, and the customer requirements of different scenes are met.
Description
Technical Field
The present invention relates to the field of computer and network technologies, and in particular, to a method, an apparatus, a device, and a readable storage medium for creating a pod.
Background
The physical hosts in the network are managed uniformly through the container cloud platform, the resources of the physical hosts can be virtualized, and the virtualized resources are scheduled, arranged and monitored, so that the maximization of the resource utilization rate can be realized.
The container cloud platform may be developed based on kubernets, with the physical host virtualized as the smallest scheduling unit pod in kubernets. Kubernetes is an open-source application for managing containerization on multiple hosts in a cloud platform, and supports automated deployment, large-scale scalable, and application containerization management. And Pod is the smallest basic unit created or deployed by Kubernetes, and several container applications are contained in one Pod.
With the advent of a localization server, cloud native services are relatively deficient under a localization ecology, a traditional kubernets network is generally realized by a single network plane, and the mode obviously does not meet requirements in a scene with relatively high requirements on the network. In the beginning of Kubernetes design, the strategy of One Pod One IP is always followed, namely, One Pod allocates One network card and One IP address.
In summary, how to effectively solve the problems of implementing multiple network planes in a Kubernetes-based container cloud platform and the like is a technical problem which needs to be solved urgently by those skilled in the art at present.
Disclosure of Invention
The invention aims to provide a pod creation method, a pod creation device, a pod creation apparatus and a readable storage medium, which can realize multiple network planes by means of proxy of multiple cni plug-ins, so that a container cloud platform can meet customer requirements of different scenes.
In order to solve the technical problems, the invention provides the following technical scheme:
a pod creation method, comprising:
receiving a pod creation request, and determining a pod creation task and a network type corresponding to the pod creation task;
determining a target cni plug-in corresponding to the network type from cni plug-ins of the agents;
sending the pod create task to the target cni plug-in;
and after the pod is created, establishing a communication connection between the pod and the container cloud platform.
Preferably, the receiving a pod creation request, and determining a pod creation task and a network type corresponding to the pod creation task includes:
receiving and analyzing the pod creation request to obtain the pod creation task and the network types corresponding to the networks in the pod;
judging whether the network types corresponding to the networks are the same or not;
if not, determining the type of the main network and the type of the auxiliary network according to preset network main and auxiliary settings or network main and auxiliary settings appointed by a request;
and if so, determining the network type corresponding to each network as the network type corresponding to the pod creation task.
Preferably, if the network type includes the primary network type and the secondary network type, determining a target cni plug-in corresponding to the network type from cni plug-ins of the slave agent includes:
from the cni plug-ins of the agent, a first cni plug-in corresponding to the primary network type and a second cni plug-in corresponding to the secondary network type are determined.
Preferably, the sending the pod creation task to the target cni plug-in includes:
splitting the pod creation task into a main network creation task and a secondary network creation task;
sending the primary network creation task to the first cni plug-in;
sending the secondary web creation task to the second cni plug-in.
Preferably, the establishing a communication connection between the pod and the container cloud platform includes:
establishing a communication connection between a main network in the pod and the container cloud platform.
Preferably, the process of creating the pod comprises:
creating a plurality of network interfaces for the pod;
setting the first cni plug-in as a master plug-in so that the master plug-in configures and manages each network interface.
Preferably, the method further comprises the following steps:
receiving a container deletion request, and recording deletion information corresponding to the container deletion request;
and feeding back the deletion information to the corresponding cni plug-in.
A pod creation apparatus comprising:
the request analysis module is used for receiving a pod creation request and determining a pod creation task and a network type corresponding to the pod creation task;
the plug-in determining module is used for determining a target cni plug-in corresponding to the network type from cni plug-ins of the agents;
a task allocation module for sending the pod create task to the target cni plug-in;
and the communication configuration module is used for establishing communication connection between the pod and the container cloud platform after the pod is created.
A pod creation device, comprising:
a memory for storing a computer program;
a processor for implementing the steps of the pod creation method described above when executing the computer program.
A readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the above-described pod creation method.
By applying the method provided by the embodiment of the invention, the pod creation request is received, and the pod creation task and the network type corresponding to the pod creation task are determined; determining a target cni plug-in corresponding to the network type from cni plug-ins of the agents; sending pod create task to target cni plug-in; and after the pod is created, establishing communication connection between the pod and the container cloud platform.
When a pod creation request is received, a pod creation task and a network type corresponding to the pod creation task are determined. Then, a target cni plug-in corresponding to the network type is determined from cni plug-ins of the agent, a pod creation task is sent to the target cni plug-in, and after the pod creation is completed, communication connection between the pod and the container cloud platform is established. Therefore, the method can be suitable for a domestic container cloud platform, and the network type can be randomly specified when the pod is created through the proxy cni plug-in, so that the multi-network plane of the Kubernetes cloud platform is realized, and the customer requirements of different scenes are met.
Accordingly, embodiments of the present invention further provide a pod creation apparatus, a device, and a readable storage medium corresponding to the pod creation method, which have the above technical effects and are not described herein again.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a flow chart of an implementation of a pod creation method in an embodiment of the present invention;
FIG. 2 is a schematic view of a pod created in an embodiment of the present invention;
fig. 3 is a schematic structural diagram of a pod creation apparatus according to an embodiment of the present invention;
FIG. 4 is a schematic structural diagram of a pod creation device according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of a pod creation device according to an embodiment of the present invention.
Detailed Description
In order that those skilled in the art will better understand the disclosure, the invention will be described in further detail with reference to the accompanying drawings and specific embodiments. It is to be understood that the described embodiments are merely exemplary of the invention, and not restrictive of the full scope of the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The core of the embodiment of the invention is to provide a pod creation method, which can be applied to a home-made container cloud platform, wherein the container cloud platform is built based on a home-made architecture (such as dragon core and Shenwei architecture). Specifically, the method may be performed by an instur CNI controller (i.e., a container network interface plug-in (CNI) that may create multiple network interfaces for a pod in a container cloud platform) or other control device or means capable of creating multiple network interfaces for a pod. For convenience of description, the following takes the example of executing the method in the instur cni controller, and details how to implement the multiple network planes are described, and for the process of implementing the method in other devices or apparatuses, reference may be made to this, and details are not described here.
Referring to fig. 1, fig. 1 is a flowchart illustrating a pod creation method according to an embodiment of the present invention, where the method includes the following steps:
s101, receiving a pod creation request, and determining a pod creation task and a network type corresponding to the pod creation task.
It should be noted that, in the embodiment of the present invention, the instur cni controller acts as an arbitration and proxy for other cni plug-ins, arbitrates different networks respectively corresponding to the proxied cni plug-ins in the actual pod creation process, selects one network to act as a master plug-in, and configures a management network interface.
The pod creation request may specifically be a creation request initiated by a user, or may also be a creation request initiated by a platform. In the pod creation request, the number of created pods, network data in the pods, network types of the networks, various types of resource setting information, and the like may be carried.
It should be noted that only one network may be included in one pod, or a plurality of networks may be included. Thus, after the Inspur cni controller receives a pod create request, the pod create task, as well as the network type, is first determined. Specifically, when the network in the created pod is a single type of network, the determined network type is only one; when the network types corresponding to the networks in the created pod are different, the determined network types include at least two types. The step S101 may specifically include:
step one, receiving and analyzing a pod creation request to obtain a pod creation task and network types corresponding to networks in the pod;
step two, judging whether the network types corresponding to the networks are the same;
step three, if not, determining the main network type and the auxiliary network type according to preset network main and auxiliary settings or network main and auxiliary settings appointed by the request;
and step four, if so, determining the network type corresponding to each network as the network type corresponding to the pod creation task.
For convenience of description, the above four steps will be described in combination.
After receiving the pod creation request, the Inspur cni controller first parses the pod creation request to obtain a pod creation task. The pod creation task may specifically be to create a pod of a specified network number, a network type corresponding to each specified network, and a specified network resource allocation.
Since the Inspur cni controller is capable of creating multiple network interfaces for a pod, in embodiments of the present invention, networks of different network types may be included in a pod.
Therefore, after the network type corresponding to each network in the pod is determined, the network type corresponding to the whole pod can be determined. Specifically, if the network types corresponding to the networks in the pod are the same, and if the network types are macvlan, the network type of the pod is determined to be macvlan; if two networks of different network types exist in the pod, it is necessary to determine which is the primary network and which is the secondary network, and the master-slave status between the network types, that is, the primary network type and the secondary network type, can be determined according to the preset network master-slave setting or the network master-slave setting specified in the request. For example, it is preset that, when a pod of a specific calico network and macvlan network needs to be created, the calico is made to be the primary network and the macvlan is made to be the secondary network, that is, the calico is the primary network type and the macvlan is the secondary network type.
Calico is a pure three-layer network scheme, can provide communication among multiple hosts for virtual machines and containers, does not use overlay network drive, adopts virtual routing to replace virtual switching, and each virtual router transmits reachable information to other virtual or physical routers through a BGP protocol. The macvlan is one of network virtualization technologies provided by linux kernel, and can virtualize a physical network card into a plurality of virtual network cards, and each virtual network card has a mac address and an IP address of the virtual network card.
After the network type of the pod is determined, the operation of step S102 can be performed.
S102, a target cni plug-in corresponding to the network type is determined from cni plug-ins of the proxy.
In an embodiment of the invention, the Inspur cni controller may proxy cni plug-ins corresponding to a plurality of common network types, such as the cni plug-in of macvlan, the cni plug-in of Calico.
Specifically, if the network type is a single type, only the target cni plug-in corresponding to the network type is determined; if the network types include at least two types, the target cni plug-in corresponding to each network type is determined. That is, the number and types of target cni plug-ins determined are related to the network type of each network in the pod.
Specifically, if the network type includes a primary network type and a secondary network type, step S102 specifically determines, from cni plug-ins of the slave agent, a first cni plug-in corresponding to the primary network type and a second cni plug-in corresponding to the secondary network type.
The first and second network plug-ins do not mean that the corresponding network plug-ins themselves have a precedence or primary-secondary relationship, but mean that for the current pod creation, the first cni plug-in corresponds to the primary network type, and the second cni plug-in corresponds to the secondary network type. That is to say, based on different user requirements, when creating a pod, the determined first cni plug-in may be a cni plug-in of macvlan, a cni plug-in of Calico, or a cni plug-in corresponding to another network type; of course, the second cni plug-in may also be a cni plug-in of macvlan, may also be a cni plug-in of Calico, and may also be a cni plug-in corresponding to other network types; the first cni card is different from the second cni card for the same pod, while their first cni card may be the same for different pods.
S103, sending the pod creation task to the target cni plug-in.
After the target cni plug-in is determined, a pod create task may be sent to the target cni plug-in. After the target cni plug-in receives the pod create task, it can execute the task, just do pod create.
Specifically, when there are two target cni plug-ins, step S103 may specifically include:
splitting a pod creation task into a main network creation task and a secondary network creation task;
step two, sending a main network creating task to the first cni plug-in;
and step three, sending a secondary network creation task to a second cni plug-in.
For convenience of description, the above three steps will be described in combination.
When networks of different network types exist in the pod to be created, the creation tasks of the different networks can be sent to the corresponding cni network plug-ins respectively for creation. That is, for the pod creation task, the task is divided in units of each network, and a primary network creation task and a secondary network creation task are obtained. The corresponding create tasks are then sent to the corresponding cni plug-ins, respectively.
And S104, after the pod is built, establishing communication connection between the pod and the container cloud platform.
It should be noted that, in the process of creating a pod, particularly when it is necessary to create multiple networks for a pod, the process of creating a pod includes:
step one, a plurality of network interfaces are established for the pod;
and step two, setting the first cni plug-in as a main plug-in so that the main plug-in can configure and manage each network interface.
Wherein the number of network interfaces (ports) is related to the number of network types of each network in the pod. For example, if the pod includes A, B and C different types of networks, the corresponding ports of the pod have ports respectively corresponding to A, B, C.
That is, the Inspur cni controller creates multiple network interfaces for the pod so that the corresponding cni plug-in can manage the network therein. To avoid conflict in management of multiple cni plug-ins, the first cni plug-in may be configured as a master plug-in, and thus the master plug-in may be configured to manage various network interfaces, such as whether to enable a network in a pod.
After the creation task is sent to the corresponding cni plug-in, the cni plug-in may be supervised, or whether the pod is created is determined by receiving cni plug-in feedback reply message.
Upon determining that the pod creation is complete, a communication connection between the pod and the container cloud platform can be established. In this way, the container cloud platform can perform communication interaction and management with the pod through the communication connection.
When establishing the communication connection, the communication connection between the main network in the pod and the container cloud platform may be specifically established. For example, a communication connection between the IP of the main network in the pod and the container cloud platform is utilized. Namely, the pod is ensured to still express as onePo IP to the outside, so that the management difficulty is reduced, and the change of a software system is reduced.
Preferably, in practical applications, the pod needs to be deleted and the IP is recycled, possibly due to changes of services or requirements. Thus, when a pod needs to be deleted, the Inspur cni controller can perform the following steps:
step one, receiving a container deletion request, and recording deletion information corresponding to the container deletion request;
and step two, feeding back the deletion information to the corresponding cni plug-in.
That is, in terms of the existing manner in which an cni plugin corresponding to a specific network directly receives a delete request, in the embodiment of the present invention, the inspur cni controller intercepts the request, records delete information, and distributes the delete information to the proxied cni plugin, thereby finally realizing deletion of pod and IP recovery.
For example, the following steps are carried out: referring to fig. 2, fig. 2 is a schematic view of a pod created in the embodiment of the present invention. As can be seen, the pod commonly shares a port eth1 and a port sth0, where the port eth1 corresponds to the calico network and the port sth0 corresponds to the macvlan network, and the kubernetes container cloud platform can support multiple network planes by means of the instur CNI controller acting on the macvlan network and the calico network corresponding plug-ins.
By applying the method provided by the embodiment of the invention, the pod creation request is received, and the pod creation task and the network type corresponding to the pod creation task are determined; determining a target cni plug-in corresponding to the network type from cni plug-ins of the agents; sending pod create task to target cni plug-in; and after the pod is created, establishing communication connection between the pod and the container cloud platform.
When a pod creation request is received, a pod creation task and a network type corresponding to the pod creation task are determined. Then, a target cni plug-in corresponding to the network type is determined from cni plug-ins of the agent, a pod creation task is sent to the target cni plug-in, and after the pod creation is completed, communication connection between the pod and the container cloud platform is established. Therefore, the method can be suitable for a domestic container cloud platform, and the network type can be randomly specified when the pod is created through the proxy cni plug-in, so that the multi-network plane of the Kubernetes cloud platform is realized, and the customer requirements of different scenes are met.
Corresponding to the above method embodiment, the embodiment of the present invention further provides a pod creation apparatus, and the pod creation apparatus described below and the pod creation method described above may be referred to in correspondence with each other.
Referring to fig. 3, the apparatus includes the following modules:
the request analysis module 101 is configured to receive a pod creation request, and determine a pod creation task and a network type corresponding to the pod creation task;
the plug-in determining module 102 is configured to determine a target cni plug-in corresponding to the network type from cni plug-ins of the agent;
the task allocation module 103 is used for sending the pod creation task to the target cni plug-in;
and the communication configuration module 104 is configured to establish a communication connection between the pod and the container cloud platform after the pod is created.
The device provided by the embodiment of the invention is applied to receive the pod creation request and determine the pod creation task and the network type corresponding to the pod creation task; determining a target cni plug-in corresponding to the network type from cni plug-ins of the agents; sending pod create task to target cni plug-in; and after the pod is created, establishing communication connection between the pod and the container cloud platform.
When a pod creation request is received, a pod creation task and a network type corresponding to the pod creation task are determined. Then, a target cni plug-in corresponding to the network type is determined from cni plug-ins of the agent, a pod creation task is sent to the target cni plug-in, and after the pod creation is completed, communication connection between the pod and the container cloud platform is established. Therefore, the device can be suitable for a domestic container cloud platform, the network type can be randomly specified when a pod is created through the proxy cni plug-in, the multi-network plane of the Kubernetes cloud platform is realized, and the customer requirements of different scenes are met.
In a specific embodiment of the present invention, the request analysis module 101 is specifically configured to receive and analyze a pod creation request, and obtain a pod creation task and a network type corresponding to each network in a pod; judging whether the network types corresponding to the networks are the same or not; if not, determining the type of the main network and the type of the auxiliary network according to preset network main and auxiliary settings or network main and auxiliary settings appointed by a request; if so, determining the network type corresponding to each network as the network type corresponding to the pod creation task.
In an embodiment of the present invention, if the network type includes a primary network type and a secondary network type, the plug-in determination module 102 is specifically configured to determine, from cni plug-ins of the proxy, a first cni plug-in corresponding to the primary network type and a second cni plug-in corresponding to the secondary network type.
In a specific embodiment of the present invention, the task allocation module 103 is specifically configured to split the pod creation task into a primary network creation task and a secondary network creation task; sending a primary network creation task to a first cni plug-in; the secondary web creation task is sent to the second cni plug-in.
In an embodiment of the present invention, the communication configuration module 104 is specifically configured to establish a communication connection between the main network in the pod and the container cloud platform.
In a specific embodiment of the present invention, the portal management module is configured to create a plurality of network interfaces for the pod; a first cni plug-in is provided as a master plug-in such that the master plug-in configuration manages the various network interfaces.
In one embodiment of the present invention, the method further comprises:
the Pod deleting module is used for receiving the container deleting request and recording deleting information corresponding to the container deleting request; the deletion information is fed back to the corresponding cni plug-in.
Corresponding to the above method embodiment, the embodiment of the present invention further provides a pod creation device, and a pod creation device described below and a pod creation method described above may be referred to in correspondence with each other.
Referring to fig. 4, the pod creation apparatus includes:
a memory 332 for storing a computer program;
a processor 322 for implementing the steps of the pod creation method of the above-described method embodiments when executing the computer program.
Specifically, referring to fig. 5, fig. 5 is a schematic diagram illustrating a specific structure of a pod creating apparatus provided in this embodiment, the pod creating apparatus may generate a relatively large difference due to different configurations or performances, and may include one or more processors (CPUs) 322 (e.g., one or more processors) and a memory 332, where the memory 332 stores one or more computer applications 342 or data 344. Memory 332 may be, among other things, transient or persistent storage. The program stored in memory 332 may include one or more modules (not shown), each of which may include a sequence of instructions operating on a data processing device. Still further, the central processor 322 may be configured to communicate with the memory 332 to execute a series of instruction operations in the memory 332 on the pod creating device 301.
The pod creation apparatus 301 may also include one or more power supplies 326, one or more wired or wireless network interfaces 350, one or more input-output interfaces 358, and/or one or more operating systems 341.
The steps in the pod creation method described above may be implemented by the structure of the pod creation device.
Corresponding to the above method embodiment, the embodiment of the present invention further provides a readable storage medium, and a readable storage medium described below and a pod creation method described above may be referred to in correspondence with each other.
A readable storage medium, on which a computer program is stored, which, when executed by a processor, implements the steps of the pod creation method of the above-described method embodiments.
The readable storage medium may be a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and various other readable storage media capable of storing program codes.
Those of skill would further appreciate that the various illustrative components and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
Claims (10)
1. A pod creation method, comprising:
receiving a pod creation request, and determining a pod creation task and a network type corresponding to the pod creation task;
determining a target cni plug-in corresponding to the network type from cni plug-ins of the agents;
sending the pod create task to the target cni plug-in;
and after the pod is created, establishing a communication connection between the pod and the container cloud platform.
2. The pod creation method according to claim 1, wherein the receiving a pod creation request and determining a pod creation task and a network type corresponding to the pod creation task comprises:
receiving and analyzing the pod creation request to obtain the pod creation task and the network types corresponding to the networks in the pod;
judging whether the network types corresponding to the networks are the same or not;
if not, determining the type of the main network and the type of the auxiliary network according to preset network main and auxiliary settings or network main and auxiliary settings appointed by a request;
and if so, determining the network type corresponding to each network as the network type corresponding to the pod creation task.
3. The pod creation method of claim 2, wherein if the network type comprises the primary network type and the secondary network type, determining a target cni plug-in corresponding to the network type from cni plug-ins of the slave agent comprises:
from the cni plug-ins of the agent, a first cni plug-in corresponding to the primary network type and a second cni plug-in corresponding to the secondary network type are determined.
4. A pod creation method as described in claim 3 wherein said sending said pod creation task to said target cni plug-in comprises:
splitting the pod creation task into a main network creation task and a secondary network creation task;
sending the primary network creation task to the first cni plug-in;
sending the secondary web creation task to the second cni plug-in.
5. The pod creation method of claim 3, wherein establishing the communication connection between the pod and the container cloud platform comprises:
establishing a communication connection between a main network in the pod and the container cloud platform.
6. The pod creation method of claim 3, wherein the process of creating the pod comprises:
creating a plurality of network interfaces for the pod;
setting the first cni plug-in as a master plug-in so that the master plug-in configures and manages each network interface.
7. The pod creation method of claim 1, further comprising:
receiving a container deletion request, and recording deletion information corresponding to the container deletion request;
and feeding back the deletion information to the corresponding cni plug-in.
8. A pod creation apparatus, comprising:
the request analysis module is used for receiving a pod creation request and determining a pod creation task and a network type corresponding to the pod creation task;
the plug-in determining module is used for determining a target cni plug-in corresponding to the network type from cni plug-ins of the agents;
a task allocation module for sending the pod create task to the target cni plug-in;
and the communication configuration module is used for establishing communication connection between the pod and the container cloud platform after the pod is created.
9. A pod creation device, comprising:
a memory for storing a computer program;
a processor for implementing the steps of the pod creation method as claimed in any of claims 1 to 7 when executing the computer program.
10. A readable storage medium, characterized in that the readable storage medium has stored thereon a computer program which, when being executed by a processor, carries out the steps of the pod creation method according to any of the claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010745369.0A CN111880902A (en) | 2020-07-29 | 2020-07-29 | Pod creation method, device, equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010745369.0A CN111880902A (en) | 2020-07-29 | 2020-07-29 | Pod creation method, device, equipment and readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111880902A true CN111880902A (en) | 2020-11-03 |
Family
ID=73201993
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010745369.0A Withdrawn CN111880902A (en) | 2020-07-29 | 2020-07-29 | Pod creation method, device, equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111880902A (en) |
Cited By (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112910685A (en) * | 2021-01-13 | 2021-06-04 | 新华三大数据技术有限公司 | Method and device for realizing unified management of container network |
| CN113127152A (en) * | 2021-04-09 | 2021-07-16 | 浪潮软件科技有限公司 | Method and device for realizing multiple network planes of kubernetes container |
| CN113220422A (en) * | 2021-06-03 | 2021-08-06 | 上海天旦网络科技发展有限公司 | Method and system for modifying Pod network interface based on operation of CNI plug-in K8s |
| CN113485788A (en) * | 2021-06-30 | 2021-10-08 | 中国民航信息网络股份有限公司 | Container resource allocation method, device, server and computer storage medium |
| CN113726859A (en) * | 2021-08-13 | 2021-11-30 | 浪潮电子信息产业股份有限公司 | Method, device, equipment and storage medium for redirecting istio traffic |
| CN114356214A (en) * | 2021-11-30 | 2022-04-15 | 新浪网技术(中国)有限公司 | Method and system for providing local storage volume for kubernets system |
| CN114500279A (en) * | 2021-12-30 | 2022-05-13 | 天翼云科技有限公司 | Plug-in configuration method and device |
| CN114938331A (en) * | 2022-05-20 | 2022-08-23 | 国网江苏省电力有限公司 | Single-physical-port multi-network access method and device in container scene, storage medium and electronic equipment |
| CN115001962A (en) * | 2021-03-01 | 2022-09-02 | 瞻博网络公司 | Container network interface with multiple types of interfaces |
| CN115225482A (en) * | 2022-06-10 | 2022-10-21 | 中电云数智科技有限公司 | Method and device for configuring Pod network based on Kubernetes |
| CN115250197A (en) * | 2022-06-02 | 2022-10-28 | 苏州思萃工业互联网技术研究所有限公司 | Device for automatically creating container discovery service |
| CN115314376A (en) * | 2022-08-01 | 2022-11-08 | 北京金山云网络技术有限公司 | Method and device for deploying network plug-ins in cluster, electronic equipment and storage medium |
| CN115250197B (en) * | 2022-06-02 | 2024-04-12 | 苏州思萃工业互联网技术研究所有限公司 | Device for automatically creating container discovery service |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109246846A (en) * | 2017-05-05 | 2019-01-18 | 展讯通信（上海）有限公司 | Measuring configuration method, measurement method, dispatching method and the device of dual link, storage medium, base station, terminal |
| CN110536344A (en) * | 2019-05-16 | 2019-12-03 | Oppo广东移动通信有限公司 | A kind of measurement report method, electronic equipment and storage medium |
| CN111371627A (en) * | 2020-03-24 | 2020-07-03 | 广西梯度科技有限公司 | Method for setting multiple IP (Internet protocol) in Pod in Kubernetes |
-
2020
- 2020-07-29 CN CN202010745369.0A patent/CN111880902A/en not_active Withdrawn
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109246846A (en) * | 2017-05-05 | 2019-01-18 | 展讯通信（上海）有限公司 | Measuring configuration method, measurement method, dispatching method and the device of dual link, storage medium, base station, terminal |
| CN110536344A (en) * | 2019-05-16 | 2019-12-03 | Oppo广东移动通信有限公司 | A kind of measurement report method, electronic equipment and storage medium |
| CN111371627A (en) * | 2020-03-24 | 2020-07-03 | 广西梯度科技有限公司 | Method for setting multiple IP (Internet protocol) in Pod in Kubernetes |
Cited By (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112910685B (en) * | 2021-01-13 | 2022-04-01 | 新华三大数据技术有限公司 | Method and device for realizing unified management of container network |
| CN112910685A (en) * | 2021-01-13 | 2021-06-04 | 新华三大数据技术有限公司 | Method and device for realizing unified management of container network |
| CN115001962A (en) * | 2021-03-01 | 2022-09-02 | 瞻博网络公司 | Container network interface with multiple types of interfaces |
| CN113127152A (en) * | 2021-04-09 | 2021-07-16 | 浪潮软件科技有限公司 | Method and device for realizing multiple network planes of kubernetes container |
| CN113220422B (en) * | 2021-06-03 | 2022-09-30 | 上海天旦网络科技发展有限公司 | Method and system for modifying Pod network interface based on operation of CNI plug-in K8s |
| CN113220422A (en) * | 2021-06-03 | 2021-08-06 | 上海天旦网络科技发展有限公司 | Method and system for modifying Pod network interface based on operation of CNI plug-in K8s |
| CN113485788B (en) * | 2021-06-30 | 2023-08-29 | 中国民航信息网络股份有限公司 | Container resource allocation method and device, server and computer storage medium |
| CN113485788A (en) * | 2021-06-30 | 2021-10-08 | 中国民航信息网络股份有限公司 | Container resource allocation method, device, server and computer storage medium |
| CN113726859A (en) * | 2021-08-13 | 2021-11-30 | 浪潮电子信息产业股份有限公司 | Method, device, equipment and storage medium for redirecting istio traffic |
| CN114356214A (en) * | 2021-11-30 | 2022-04-15 | 新浪网技术(中国)有限公司 | Method and system for providing local storage volume for kubernets system |
| CN114356214B (en) * | 2021-11-30 | 2023-12-01 | 新浪技术（中国）有限公司 | Method and system for providing local storage volume for kubernetes system |
| CN114500279A (en) * | 2021-12-30 | 2022-05-13 | 天翼云科技有限公司 | Plug-in configuration method and device |
| CN114500279B (en) * | 2021-12-30 | 2024-03-08 | 天翼云科技有限公司 | Plug-in configuration method and device |
| CN114938331A (en) * | 2022-05-20 | 2022-08-23 | 国网江苏省电力有限公司 | Single-physical-port multi-network access method and device in container scene, storage medium and electronic equipment |
| CN115250197A (en) * | 2022-06-02 | 2022-10-28 | 苏州思萃工业互联网技术研究所有限公司 | Device for automatically creating container discovery service |
| CN115250197B (en) * | 2022-06-02 | 2024-04-12 | 苏州思萃工业互联网技术研究所有限公司 | Device for automatically creating container discovery service |
| CN115225482B (en) * | 2022-06-10 | 2023-10-20 | 中电云数智科技有限公司 | Method and device for carrying out Pod container network configuration based on Kubernetes |
| CN115225482A (en) * | 2022-06-10 | 2022-10-21 | 中电云数智科技有限公司 | Method and device for configuring Pod network based on Kubernetes |
| CN115314376A (en) * | 2022-08-01 | 2022-11-08 | 北京金山云网络技术有限公司 | Method and device for deploying network plug-ins in cluster, electronic equipment and storage medium |
| CN115314376B (en) * | 2022-08-01 | 2024-01-19 | 北京金山云网络技术有限公司 | Method and device for deploying network plug-ins in cluster, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111880902A (en) | Pod creation method, device, equipment and readable storage medium | |
| US9999030B2 (en) | Resource provisioning method | |
| US10698717B2 (en) | Accelerator virtualization method and apparatus, and centralized resource manager | |
| US10419326B2 (en) | Method for implementing network virtualization and related apparatus and communications system | |
| EP3163797B1 (en) | Service orchestration method and apparatus in software-defined networking, and storage medium | |
| CN112905305B (en) | VPP-based cluster type virtualized data forwarding method, device and system | |
| EP3249871A1 (en) | Method and device for updating network service descriptor | |
| CN102316043B (en) | Port virtualization method, switch and communication system | |
| CN110224917B (en) | Data transmission method, device and system and server | |
| CN110830574B (en) | Method for realizing intranet load balance based on docker container | |
| CN114172905B (en) | Cluster network networking method, device, computer equipment and storage medium | |
| EP3737039B1 (en) | Method for transmitting request message and apparatus | |
| CN110716787A (en) | Container address setting method, apparatus, and computer-readable storage medium | |
| US20220318071A1 (en) | Load balancing method and related device | |
| CN114301914B (en) | Cloud edge cooperation method, cloud edge cooperation device and storage medium | |
| CN113067739B (en) | High-density container network deployment method and system | |
| CN113127144B (en) | Processing method, processing device and storage medium | |
| Alam et al. | Software defined networks: Review and architecture | |
| CN110795209B (en) | Control method and device | |
| CN116069447A (en) | Virtual machine NUMA topology generation method, device, equipment and medium | |
| CN113656181A (en) | Method and device for issuing real-time application cluster instance resources | |
| CN113535402A (en) | Load balancing processing method and device based on 5G MEC and electronic equipment | |
| CN112241323A (en) | Computing resource discovery and management method and system based on FPGA server | |
| KR20200081799A (en) | The multiple virtual network communication system and method using virtual router | |
| CN114938375B (en) | Container group updating equipment and container group updating method |
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 | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20201103 |
|
| WW01 | Invention patent application withdrawn after publication |