JP7363167B2 - Container daemon, information processing device, container virtualization system, packet distribution method and program - Google Patents

Description

The present invention relates to a container daemon, an information processing device, a container-type virtualization system, a packet distribution method, and a program.

A technology called container virtualization that provides virtualization of an OS (Operating System) on one physical host is known. Container virtualization allows multiple containers to run on a single physical host. For example, a video conference service can be provided by a single physical host that runs an application container for making voice calls, an application container for distributing video, and an application container for distributing document materials. In order to provide comfortable video conferencing services, it is necessary to apply QoS (Quality of Service) requirements (e.g. delay time, jitter, bandwidth) to the communication traffic of each container according to the characteristics of the distributed content. preferable. In other words, it is necessary to be able to apply different QoS requirements to each container.

Tools such as DPDK (Data Plane Development Kit) are provided as an example of technology related to QoS improvement that can be applied to container-type virtualization environments. For example, when DPDK is introduced into a container, the communication traffic of that container becomes faster. Furthermore, by introducing the DPDK QoS (Quality of Service) framework into containers, it becomes possible not only to speed up communication traffic but also to adjust the priority of packet processing between containers. For example, in the case of the above-mentioned video conferencing service, it is possible to set the communication traffic priority of the audio call container higher than other containers (video, materials) to prevent audio delays during the conference.

Note that, regarding container virtualization technology, Patent Document 1 discloses a technology for automatically generating containers. For example, Patent Document 1 discloses an example of generating a container having characteristics according to SLA (Service Level Agreement).
Further, Patent Document 2 discloses a technology in which a CPU (Central Processing Unit) or an accelerator processes packets related to communication from a container based on settings of a lookup table. Patent Document 2 discloses changing the capacity of resources allocated to a lookup table depending on the bandwidth of a packet flow. For example, if the capacity of resources allocated to lookup tables is reduced, that amount of resources can be allocated to communication processing.
Further, Patent Document 3 discloses a transmission management system that transmits content data using relay devices according to service levels.

Special table 2019-503535 publication JP2019-33351A JP2017-38251A

However, it is not realistic to introduce a high-speed packet processing function such as DPDK to all containers. Furthermore, due to hardware limitations and other reasons, it is not always possible to introduce a high-speed packet processing function to all devices within a container environment. In a container virtualization environment, there is a need for a method to achieve network speedup and QoS control without modifying containers. Patent Documents 1 and 3 do not disclose a method for solving such problems. Further, the technique of Patent Document 2 assumes the existence of an accelerator, and requires a load for lookup table capacity allocation processing.

Therefore, an object of the present invention is to provide a container daemon, an information processing device, a container-type virtualization system, a packet distribution method, and a program that solve the above-mentioned problems.

According to one aspect of the present invention, a container daemon included in an information processing apparatus is configured to transfer packets to a destination where the container operates, based on setting information of a distribution destination of packets delivered from the container . The information processing apparatus includes a packet distribution unit that outputs to the OS of the information processing device or a packet high-speed processing layer installed in the OS .

According to another aspect of the present invention, an information processing device includes the container daemon described above, an OS, and a high-speed packet processing layer installed in the OS.

According to another aspect of the present invention, an information processing apparatus includes the container daemon described above and an OS having a function of performing priority control on processing of the packet.

According to another aspect of the present invention, a container virtualization system includes one or more of the above information processing devices, and a container orchestrator that controls containers operating on the information processing device. , the container orchestrator sets a destination for distributing the packet to a container daemon of the information processing device.

According to another aspect of the present invention, in the packet distribution method, a container daemon included in the information processing device distributes the packet to the container based on setting information of a distribution destination of the packet distributed from the container. It is output to the OS of the operating information processing device or a packet high-speed processing layer installed in the OS .

According to another aspect of the present invention, the program sends the packets to the computer of the information processing device based on the setting information of the distribution destination of the packets delivered from the container. A process of outputting to the OS of the processing device or a packet high-speed processing layer installed in the OS is executed.

According to the present invention, network QoS control according to SLA can be realized in a container-type virtualization environment without modifying the container side.

FIG. 1 is a first diagram showing a configuration example of a container-type virtualization system according to an embodiment of the present invention. FIG. 2 is a second diagram showing a configuration example of a container-type virtualization system according to an embodiment of the present invention. It is a 1st flowchart which shows an example of a process by one embodiment of this invention. 12 is a second flowchart illustrating an example of processing according to an embodiment of the present invention. FIG. 3 is a diagram showing an example of settings for packet distribution according to an embodiment of the present invention. FIG. 1 is a first diagram showing an application example of a container-type virtualization system according to an embodiment of the present invention. FIG. 2 is a second diagram illustrating an application example of a container-type virtualization system according to an embodiment of the present invention. FIG. 3 is a diagram showing the minimum configuration of a container daemon according to an embodiment of the present invention. 1 is a diagram showing an example of the hardware configuration of a container-type virtualization system in an embodiment of the present invention.

A container-type virtualization system according to one embodiment will be described below with reference to FIGS. 1 to 9.
(Explanation of configuration)
FIG. 1 is a first diagram showing a configuration example of a container-type virtualization system according to an embodiment of the present invention.
As shown in FIG. 1, the container virtualization system 1 includes a container orchestrator 10, container operating devices 20, 20a, 20b, and 20c, and a relay device 30.
The container orchestrator 10 is a computer in which software such as a Kubernetes master function is installed. The container operating devices 20 to 20c are computers in which Kubernetes node functions and software such as Docker are installed. The container orchestrator 10 is a master, and the container operating devices 20 to 20c are nodes. Containers operate in the container operating devices 20 to 20c. The relay device 30 is, for example, a computer in which software such as HAproxy is installed. The container orchestrator 10 and each of the container operating devices 20 to 20c are communicably connected via a message path NW1 (management plane). The container orchestrator 10 and the relay device 30 are communicably connected via a message path NW0 (management plane). Control information flows through message paths NW0 and NW1. Furthermore, the container operating devices 20 to 20c and the relay device 30 are communicably connected via a network NW2 (data plane). Further, the relay device 30 is connected to an external network NW3. For example, when a container running on the container operating device 20 or the like is accessed from various devices such as a PC, a tablet, or a smartphone connected to the external network NW3, the relay device 30 mediates the access and the container running on the container operating device 20 or the like is accessed. Realize communication with the container.

The container orchestrator 10 includes an instruction section 11, a selection section 12, and a storage section 13. The instruction unit 11 instructs the container operating devices 20 to 20c regarding packet distribution. The selection unit 12 selects, from among the container operating devices 20 to 20c, a container operating device that starts a container that provides a service requested by a user. The storage unit 13 stores information as to whether or not a high-speed packet processing function is installed for each of the container operating devices 20 to 20c. For example, the storage unit 13 stores information indicating that the high-speed packet processing function has been installed in the container operation device 20, and that the high-speed packet processing function has not been installed in the container operation devices 20a to 20c.

The container operation device 20 includes container groups 21-1, 21-2, and 21-3, a container daemon 22, a high-speed packet processing layer 24, an OS 25, a NIC (Network Interface Card) 28, and a designated NIC 29. Be prepared.
Each of the container groups 21-1 to 21-3 is one or more containers. For example, an application 211 runs on the container group 21-1, an application 212 runs on the container group 21-2, and an application 213 runs on the container group 21-3.
The container daemon 22 manages the container groups 21-1 to 21-3 that operate on the container operating device 20. For example, the container daemon 22 accepts various commands for the container groups 21-1 to 21-3, and starts or stops the container groups 21-1 to 21-3. Further, the container daemon 22 includes a packet distribution section 23. The packet distribution unit 23 distributes packets distributed by the container groups 21-1 to 21-3 to either the OS 25 or the packet high-speed processing layer 24 according to instructions from the instruction unit 11 of the container orchestrator 10. For example, if the services provided by the applications 211 and 212 are given priority over the services provided by the application 213, the packet distribution unit 23 processes the packets distributed by the container groups 21-1 and 21-2 at high speed. The packets distributed by the container group 21-3 are distributed to the layer 24 and distributed to the OS 25.

The packet high-speed processing layer 24 is software such as DPDK that speeds up packet processing. In this embodiment, it is assumed that software capable of QoS control (for example, DPDK QoS framework) is installed in the container operating device 20, as an example. The high-speed packet processing layer 24 bypasses the large overhead packet processing provided by the OS 25 and directly accesses the designated NIC 29 to perform communication. Therefore, the speed of the network can be increased. The high-speed packet processing layer 24 also includes a QoS control function 241. For example, if the priority of the communication traffic of the container group 21-1 is higher than the communication traffic of the container group 21-2, the QoS control function 241 controls the packets delivered by the container group 21-1 to the container group 21-1. It processes the packets with priority over the packets distributed by 21-2. The designated NIC 29 is installed for the packet high-speed processing layer 24, and the packet high-speed processing layer 24 occupies the designated NIC 29.

The OS 25 includes an OVS 26 and a kernel 27. OVS26 is a virtual switch. The kernel 27 performs general packet processing. Packets distributed from the container daemon 22 to the OS 25 are processed by the kernel 27 and distributed via the NIC 28. Packet processing by the kernel 27 has a higher load and takes more time than processing by the packet high-speed processing layer 24. Note that the kernel 27 may have a function (coloring function) of changing the value of DSCP (Differentiated Services Code Point) and IP Precedence of the packet header. Since the priority of packet processing can be changed by changing the values of DSCP and IP Precedence, QoS control is possible even when packet processing is performed via the OS 25.

FIG. 2 is a second diagram showing a configuration example of a container-type virtualization system according to an embodiment of the present invention. In FIG. 1, the configuration of the container operation device 20 including the high-speed packet processing layer 24 has been described. Next, with reference to FIG. 2, the configuration of the container operating device 20a in which the high-speed packet processing layer 24 is not installed will be described.

The container operation device 20a includes container groups 21-1a, 21-2a, and 21-3a, a container daemon 22a, an OS 25a, and a NIC 28a. The container daemon 22a includes a packet distribution section 23a, and the OS 25a includes an OVS 26a and a kernel 27a. The container operating device 20a does not have a configuration corresponding to the packet high-speed processing layer 24 and designated NIC 29 in FIG.
In an actual container-type virtualization environment, the packet high-speed processing layer 24 may not be installed due to various reasons such as hardware constraints and costs, or may not be installed yet even if it is planned to be installed. The container operating device 20a is a configuration example of a container host in such a case.

The container groups 21-1a to 21-3a, the container daemon 22a, the packet distribution unit 23a, the OS 25a, the OVS 26a, the kernel 27a, and the NIC 28a are the container groups 21-1 to 21-3 and the container daemon 22 described in FIG. 1, respectively. , the packet distribution unit 23, the OS 25, the OVS 26, the kernel 27, and the NIC 28.
In the case of the configuration shown in FIG. 2, for example, if the service provided by the application 211a has the highest priority, then the application 212a has the next highest priority, and then the application 213a has the second highest priority, the instruction unit of the container orchestrator 10 11 is a container daemon 22a which distributes all packets delivered by the container groups 21-1a to 21-3a to the OS 25a and processes packets delivered by the container groups 21-1a to 21-3a with the above priority. Instruct to.

The packet distribution unit 23a distributes packets distributed by the container groups 21-1a to 21-3a to the OS 25a according to instructions from the instruction unit 11. In addition, in the OS 25a, the kernel 27a, according to instructions from the instruction unit 11, gives top priority to packets delivered by the container group 21-1a, second priority to packets delivered by the container group 21-2a, and delivery to the container group 21-3a. The header of the packet is rewritten so that the packet is processed with the third priority. This makes it possible to perform QoS control of communication traffic even for container operating devices in which the high-speed packet processing layer 24 is not installed.

(motion)
Next, the operation of the container-type virtualization system 1 will be explained with reference to FIGS. 3 to 5.
FIG. 3 is a first flowchart illustrating an example of processing according to an embodiment of the present invention.
FIG. 5 is a diagram showing an example of settings for packet distribution according to an embodiment of the present invention.
First, the relay device 30 receives user traffic (step S1). User traffic includes the types of applications requested by users. For example, assume that application 211, application 212, and application 213 are requested. The relay device 30 notifies the container orchestrator 10 of the information received from the user via the message path NW0 (step S2).

(Example 1)
Information in which communication traffic priorities are set for each application is registered in advance in the storage unit 13 of the container orchestrator 10. For example, priority levels 1, 2, and 3 are set for application 211, application 212, and application 213, respectively (priority level 1 is the highest priority).
Further, in the storage unit 13, presence or absence of the introduction of the packet high-speed processing layer 24 is registered for each of the container operation devices 20 to 20c. For example, it is registered that the high-speed packet processing layer 24 has been installed in the container operation device 20, but the others have not been installed.
Furthermore, a setting is registered in the storage unit 13 that the communication traffic of applications with priority levels 1 and 2 will be processed by the packet high-speed processing layer 24.
These settings are registered in advance in the container orchestrator 10 by the administrator.

Based on these settings, the selection unit 12 of the container orchestrator 10 specifies a container operating device 20 that meets the priority requirements of the applications 211 to 213 from among the container operating devices 20 to 20c (step S3).

Next, the container orchestrator 10 deploys a container group 21-1 in which the application 211 operates, a container group 21-2 in which the application 212 operates, and a container group 21-3 in which the application 213 operates on the specified container operating device 20. (Step S4). At this time, the instruction unit 11 performs settings to instruct the container daemon 22 regarding the method of distributing packets distributed by the container groups 21-1 to 21-3 and QoS control. FIG. 5(a) shows an example of the setting contents. In this example, (1) packets delivered by container group 21-1 and container group 21-2 are output to the packet high-speed processing layer 24, and (2) priority is given to processing of packets delivered by container group 21-1. (3) Settings to instruct priority level 1 to be set to priority 1, priority level 2 to processing of packets delivered by container group 21-2, and (3) output of packets delivered by container group 21-3 to OS 25. conduct. This setting is stored in the container operating device 20, for example, as a setting file that the container daemon 22 refers to.
Note that the instruction unit 11 may also instruct the packets distributed by the container group 21-3 to be output to the packet high-speed processing layer 24.

(Example 2)
In addition, as another example of operation, the applications 211a to 213a are requested by the user in step S1, and the storage unit 13 of the container orchestrator 10 stores the applications 211a, 212a, and 213a with priority levels 4 and 4, respectively. 5 and 6 are set (priority 4 is the highest priority). In this case, since applications set with priorities 1 and 2 are not requested, it is possible to select container operation devices 20a to 20c in which the high-speed packet processing layer 24 is not installed. The selection unit 12 of the container orchestrator 10 specifies, for example, the container operating device 20a from among the container operating devices 20 to 20c (step S3).

Next, the container orchestrator 10 deploys a container group 21-1a in which the application 211a operates, a container group 21-2a in which the application 212a operates, and a container group 21-3a in which the application 213a operates on the specified container operating device 20a. (Step S4). At this time, the instruction unit 11 performs settings to instruct the container daemon 22a regarding the method of distributing packets delivered by the container groups 21-1a to 21-3a and QoS control. FIG. 5(b) shows an example of the setting contents. In the case of this example, (1) outputting the packets distributed by the container groups 21-1a to 21-3a to the OS 25a, (2) setting priority 4 to the processing of the packets distributed by the container group 21-1a, Settings are made to instruct priority 5 to be set for processing packets delivered by the container group 21-2a, and priority 6 to be set for processing packets delivered by the container group 21-3a. This setting is stored in the container operating device 20, for example, as a setting file that the container daemon 22 refers to.

Next, the packet distribution process when packets are actually distributed from the container group 21-1 etc. will be explained with reference to FIG.
FIG. 4 is a second flowchart illustrating an example of processing according to an embodiment of the present invention.
(For example 1)
First, packets are delivered independently from the container groups 21-1 to 21-3. The container daemon 22 acquires the distributed packet (step S11).
Next, the packet distribution unit 23 of the container daemon 22 operates depending on the presence or absence of the high-speed packet processing layer 24 (step S12). If the packet high-speed processing layer 24 is present, the packet distribution unit 23 adjusts whether to distribute the packet to the high-speed packet processing layer 24 or to the OS 25 based on the settings of the instruction unit 11 (step S13).

In the case of Example 1 above, the packet sorting unit 23 assigns priority 1 to the packet distributed from the container group 21-1, and assigns priority 2 to the packet distributed from the container group 21-2. and outputs it to the packet high-speed processing layer 24. In the packet high-speed processing layer 24, the QoS control function 241 performs priority control (step S14). The QoS control function 241 processes packets assigned priority 1 more preferentially. The high-speed packet processing layer 24 delivers the packets delivered from the container to the user side via the designated NIC 29 according to the set priority (step S15).

Further, for example, the packet distribution unit 23 outputs the packets distributed from the container group 21-3 to the OS 25. In the OS 25, the kernel 27 performs predetermined packet processing and delivers the packets delivered from the container to the user side via the NIC 28 (step S16).

(For example 2)
The container daemon 22a acquires packets distributed from the container groups 21a-1 to 21-3a (step S11).
Next, the packet distribution unit 23a of the container daemon 22a operates depending on the presence or absence of the high-speed packet processing layer (step S12). If there is no high-speed packet processing layer, the packet distribution unit 23a makes adjustments to distribute the packets to the OS 25 based on the settings from the instruction unit 11 (step S17). For example, in the case of Example 2 above, the packet sorting unit 23a assigns priority 4 to the packet distributed from the container group 21-1a, and assigns priority 5 to the packet distributed from the container group 21-2a. The packets distributed from the container group 21-3a are given a priority level of 6 and output to the OS 25a. In the OS 25a, a kernel 27a performs predetermined packet processing. Furthermore, the kernel 27a performs priority control (step S18). For example, the kernel 27a changes the priority of the packet by rewriting the IP Precedence or DSCP value of the packet header according to the priority instructed by the container daemon 22a. The kernel 27a distributes the packet after priority control to the user side via the NIC 28 (step S19).

According to this embodiment, distribution from containers can be performed by simply making the necessary settings for the container orchestrator 10 and installing the container daemon 22 without modifying the container group 21-1 etc. of the container operating device 20. Packet speeding and QoS control become possible.
For example, in the case of a container operation device 20 in which the packet high-speed processing layer 24 has been introduced, communication can be performed simply by setting the distribution to the packet high-speed processing layer 24 for the desired container group 21-1 etc. operating on the container operation device 20. Traffic can be sped up. Furthermore, by setting the priority, it is possible to adjust the priority between containers.

In addition, in the case of the container operating device 20a that does not have the high-speed packet processing layer 24 installed, the container group 21-1a etc. should be set to be distributed to the OS 25a, and the priority of the container groups 21-1a to 21-3a should be set. You can adjust the priority of communication traffic between containers.

Thereby, regardless of whether or not the high-speed packet processing layer 24 is introduced, it is possible to perform QoS control according to the SLA for the communication traffic of containers operating within the container-type virtualization system 1. Moreover, the application developer can concentrate on developing the application without considering the introduction of the high-speed packet processing layer 24 into the container. Additionally, it is possible to quickly develop and provide applications.

(Example 1)
FIG. 6 is a first diagram showing an application example of a container-type virtualization system according to an embodiment of the present invention.
FIG. 6 shows a container group 21-1 in which an application 211 for making voice calls operates, a container group 21-2 in which an application 212 for video distribution operates, and a container group 21- in which an application 213 for distributing materials operates. 3 shows an embodiment in which a video conferencing service is provided by a container operation device 20 including a container operating device 3.
The SLA levels of Gold, Silver, and Bronze are set for the application 211, the application 212, and the application 213, respectively. For example, the container orchestrator 10 configures the container daemon 22 as illustrated in FIG. 5(a). The audio data distributed from the container group 21-1 and the video data distributed from the container group 21-2 are distributed to the user side via the packet high-speed processing layer 24. The data of the materials distributed from the container group 21-3 is distributed to the user side via the OS 25.
In order to reliably deliver audio data during a conference, audio data is processed with top priority (Gold) to achieve delivery with low jitter and low delay. Video streaming is given an intermediate priority (Silver), and the priorities of audio and video are differentiated by the QoS control function 241 of the packet high-speed processing layer 24, but audio data is given higher priority than video streaming. Since the deterioration in the quality of document sharing has little impact on the conference, it is given a low priority (Bronze).

(Example 2)
FIG. 7 is a second diagram showing an application example of the container-type virtualization system according to an embodiment of the present invention.
FIG. 7 shows an example of application to IOT (Internet of Things) data processing and processing services.
Applications 211 that process medical data that involves human life or that cannot allow a reduction in processing speed are Gold.Although it is not a problem even if a time lag occurs, for example, the position of a moving object provided by GPS is Silver is set for the application 212 that requires a certain degree of real-time performance such as data processing, and Bronze is set for the application 213 that processes data such as weather data after a certain amount of time has passed.
In this case as well, the container orchestrator 10 performs settings for the container daemon 22 as illustrated in FIG. 5(a). The medical data distributed from the container group 21-1 and the position data distributed from the container group 21-2 are distributed to the user side via the packet high-speed processing layer 24. The weather data distributed from the container group 21-3 is distributed to the user side via the OS 25.
Even when independent services are provided by applications in each container as in this example, it is possible to perform priority control of communication traffic on a container-by-container basis according to the service level of each application.

The transition from application development to delivery is becoming faster as applications become microservices. However, the main focus is on application development and provision, and the provision of SLA associated with the network has been postponed. According to the present embodiment, it is possible to simultaneously provide services that satisfy SLA without impairing the advantages of container-based virtualization, such as rapid application development and rapid service provision. Further, regardless of the presence or absence of a high-speed packet processing layer in the container environment, it is possible to provide a service that satisfies the SLA by controlling packet processing with priority. Furthermore, it is possible to eliminate the effort and complicated operational management that occur when applying a high-speed packet processing layer within a container environment.

FIG. 8 is a diagram showing the minimum configuration of a container daemon according to an embodiment of the present invention.
As shown in FIG. 8, the container daemon 22 includes at least a packet distribution section 23.
The packet distribution unit 23 outputs the packet to the OS or high-speed packet processing layer on which the container runs, based on the settings of the distribution destination for the packet distributed from the container. The container daemon 22 may be provided with setting information on where packets are distributed based on the presence or absence of a high-speed packet processing layer and the priority of packet processing for each container.

FIG. 9 is a diagram showing an example of the hardware configuration of a container-type virtualization system according to an embodiment of the present invention.
The computer 900 includes a CPU 901, a main storage device 902, an auxiliary storage device 903, an input/output interface 904, and a communication interface 905. The container operating devices 20, 20a to 20c described above are implemented in a computer 900. The operations of each functional unit described above are stored in the auxiliary storage device 903 in the form of a program. The CPU 901 reads the program from the auxiliary storage device 903, expands it to the main storage device 902, and executes the above processing according to the program. Further, the CPU 901 reserves a storage area in the main storage device 902 according to the program. Further, the CPU 901 secures a storage area in the auxiliary storage device 903 to store the data being processed according to the program.

Note that in at least one embodiment, auxiliary storage device 903 is an example of a non-transitory tangible medium. Other examples of non-transitory tangible media include magnetic disks, magneto-optical disks, CD-ROMs, DVD-ROMs, semiconductor memories, etc. connected via the input/output interface 904. Further, when this program is distributed to the computer 900 via a communication line, the computer 900 that received the distribution may develop the program in the main storage device 902 and execute the above processing. Moreover, the program may be for realizing part of the functions described above. Further, the program may be a so-called difference file (difference program) that realizes the above-described functions in combination with other programs already stored in the auxiliary storage device 903.

In addition, it is possible to appropriately replace the components in the above-described embodiments with well-known components without departing from the spirit of the present invention. Further, the technical scope of the present invention is not limited to the above-described embodiments, and various changes can be made without departing from the spirit of the present invention.

1...Container-type virtualization system 10...Container orchestrator 11...Instruction section 12...Selection section 13...Storage section 20, 20a, 20b, 20c...Container operating device 21-1 , 21-2, 21-3, 21-1a, 21-2a, 21-3a... Container group 22, 22a... Container daemon 23, 23a... Packet sorting unit 24... Packet high-speed processing Layer 241...QoS control function 25, 25a...OS
26, 26a...OVS
27, 27a...Kernel 28, 28a...NIC
29...Specified NIC
30...Relay devices NW0, NW1...Message path NW2...Network NW3...External network 900...Computer 901...CPU
902... Main storage device 903... Auxiliary storage device 904... Input/output interface 905... Communication interface

Claims (10)

A container daemon included in the information processing device,
a packet distribution unit that outputs the packet to an OS of the information processing device on which the container operates or a packet high-speed processing layer installed in the OS, based on setting information of a distribution destination of the packet distributed from the container;
Container daemon with . comprising setting information of the distribution destination based on whether the high-speed packet processing layer is installed in the OS and the priority of packet processing for each container;
A container daemon according to claim 1. A container daemon according to claim 1 or 2,
OS and
a packet high-speed processing layer introduced into the OS;
An information processing device comprising: the container daemon outputs the packet having a higher priority than a predetermined priority to the packet high-speed processing layer;
outputting the packet having a lower priority than the predetermined priority to the OS;
The information processing device according to claim 3. The packet high-speed processing layer has a function of performing priority control on processing of the packet,
The information processing device according to claim 3 or 4. A container daemon according to claim 1 or 2,
an OS having a function of performing priority control regarding processing of the packet;
An information processing device comprising: one or more information processing devices according to any one of claims 3 to 6;
a container orchestrator that controls containers operating in the information processing device;
Equipped with
The container orchestrator configures a destination to which the packet is to be distributed to a container daemon of the information processing device.
Container-based virtualization system. The container orchestrator stores information as to whether a high-speed packet processing layer has been introduced for each information processing device,
When starting a container that executes a service that requires high-speed packet processing, selecting the information processing device in which the packet high-speed processing layer has been installed, and starting the container on the selected information processing device;
The container-type virtualization system according to claim 7. The container daemon included in the information processing device is
outputting the packet to an OS of the information processing device on which the container operates or a packet high-speed processing layer installed in the OS, based on setting information of a distribution destination of the packet delivered from the container;
Packet distribution method. In the computer of the information processing device ,
A process of outputting the packet to an OS of the information processing device on which the container operates or a packet high-speed processing layer installed in the OS, based on setting information of a distribution destination of the packet delivered from the container;
A program to run.

Images