CONTAINER MIGRATION EQUIPMENT, CONTAINER MIGRATION PROCESS AND CONTAINER MIGRATION PROGRAM

Abstract

A container migration facility causes the operating mode of a migration source proxy (120) to transition from a transfer mode of: receiving data transferred by a request source container (110) requesting data processing; and transferring the received data to a migration source container (130), which is a request target container, to a queue mode of saving the data instead of transferring it. After the operating mode of the migration source proxy has transitioned to queue mode, and the migration target container (150) is activated, the container migration facility causes the operating mode of the migration source proxy to transition to a queue send mode of sending the saved data to the migration target proxy.After the secure data has been sent, the container migration facility causes the request source container to change a data transfer destination from the migration source proxy to the migration destination proxy (140).

Description

Technical field

[0001] The present disclosure relates to the migration of a software container. State of the art

[0002] In recent years, open-source software (OSS) has frequently been used for the product development of embedded devices and systems. Furthermore, there are embedded devices on which third-party applications can be added after the products have been purchased.

[0003] If a non-significant application, such as an OSS, and an additional application behave anomalously, they can consume hardware and system resources and affect the operation of a significant application.

[0004] To prevent this problem, there is a method that performs software containerization of non-significant applications.

[0005] In this way, the impact of resource allocation resulting from the unusual operation of non-significant applications can be reduced, and stable operation of the significant application can be enabled.

[0006] Generally, an application consists of a variety of functions. Specific examples of these functions include a cloud communication function, a function for detecting AI anomalies, and a database function within the application. It should be noted that AI stands for artificial intelligence.

[0007] When containerizing an application, the individual functions are containerized, not the entire application, so that the impact of anomalous behavior can be reduced on a function-specific basis.

[0008] When such an application is run on a system, a multitude of containers run within that system, and functions are accessed between the containers. An example of such a mechanism is Representational State Transfer (REST).

[0009] This creates the need to migrate a work container to another facility, for example due to storage shortages at the facility, facility maintenance, and facility upgrades.

[0010] To move the work container, the container must first be stopped, and the necessary data must be transferred.

[0011] Patent literature 1 discloses a technique for reducing the unavailability time of a container by differential transfer of a container image.

[0012] However, even with this technique, container downtime cannot be reduced to zero. Therefore, if a request and data are transferred from another container to a stopped container, the destination container may not be able to accept the request and data.

[0013] Furthermore, there is a need to continuously process the collected data within a container, for example to collect sensor data, without losing the collected data even if the container migrates. Reference list patent literature

[0014] Patent Literature 1: JP 2019-530072 A Summary of the invention: Technical problem

[0015] The purpose of the present disclosure is to enable a container to be migrated without any data loss during the migration of the container. Solution to the problem

[0016] A container migration device according to the present disclosure migrates a container that performs data processing from a migration source device to a migration target device.

[0017] The migration source device is a device in which a migration source container and a migration source proxy operate.

[0018] The migration source device is a device in which a migration source container and a migration target proxy operate.

[0019] The container migration facility includes: a first transition unit to cause the migration source proxy's operating mode to change from a transfer mode of: receiving data transferred by a request source container requesting data processing; and transferring the received data to the migration source container, which is a request target container, to a queue mode of saving the data instead of transferring it; a second transition unit to cause the migration source proxy to transition to a queue mode after its operating mode has entered queue mode and the migration target container has been activated, and to a queue mode for sending the backed-up data to the migration target proxy; and a transmission target change unit to cause the request source container to change a data transmission target from the migration source proxy to the migration target proxy after the secure data has been sent. Advantageous effects of the invention

[0020] According to the present disclosure, it is possible to migrate a container without data loss while the container is migrating. Brief description of the drawings Fig. Figure 1 is a configuration representation of an information processing system 100 in embodiment 1. Fig. Figure 2 is a configuration representation of a migration source device 200 in embodiment 1. Fig. Figure 3 is a configuration representation of a migration management unit 230 in embodiment 1. Fig. Figure 4 is a configuration representation of a migration target device 300 in embodiment 1. Fig. Figure 5 is a schematic representation of a container migration process in embodiment 1. Fig. Figure 6 is a schematic representation of the container migration process in embodiment 1. Fig. Figure 7 is a schematic representation of the container migration process in embodiment 1. Fig. Figure 8 is a schematic representation of the container migration process in embodiment 1. Fig. Figure 9 is a flowchart of the container migration process in embodiment 1. Fig. Figure 10 shows a workflow of the information processing system 100 in embodiment 1. Fig. Figure 11 shows a workflow of the information processing system 100 in embodiment 1. Fig. Figure 12 shows a workflow of the information processing system 100 in embodiment 1. Fig. Figure 13 is a hardware configuration representation of the migration source device 200 in embodiment 1. Fig. 14 is a hardware configuration representation of the migration target device 300 in embodiment 1. Description of embodiments

[0021] In the embodiment and the drawings, identical or equivalent elements are designated with the same reference numeral. A description of an element designated with the same reference numeral as that of an element being described is omitted or simplified where appropriate. Arrows in the drawings primarily indicate data flows or processing sequences. Design 1.

[0022] One mode of migrating a container that performs data processing is described with reference to the Fig. 1 to 14 described.

[0023] In embodiment 1, a “container” refers to a software container or a functional block corresponding to a software container.

[0024] A "proxy" means a software proxy or a functional block that corresponds to a software proxy. *** Configuration Description ***

[0025] A configuration of an information processing system 100 is described with reference to Fig. 1 described.

[0026] The information processing system 100 is equipped with a migration source device 200 and a migration target device 300.

[0027] The migration source device 200 and the migration destination device 300 communicate with each other via a network 101.

[0028] Migration source device 200 and migration destination device 300 have different IP addresses. Note that IP stands for Internet Protocol.

[0029] The migration source device 200 has a request source container 110, a migration source proxy 120, and a migration source container 130.

[0030] The request source container 110 is a container that submits data and requests processing of that data.

[0031] The migration source proxy 120 is a proxy that receives the data from the request source container 110 before migration and transfers the received data to the migration source container 130.

[0032] The migration source container 130 is a pre-migration request target container.

[0033] The request target container is a container that processes the data submitted by the request source container 110.

[0034] The migration target device 300 has a migration target proxy 140 and a migration target container 150.

[0035] The migration source proxy 140 is a proxy that receives the data from the request source container 110 after the migration and transfers the received data to the migration target container 150.

[0036] The migration target container 150 is a post-migration request target container.

[0037] The Migration Source Device 200 serves as a container migration facility.

[0038] The container migration facility migrates a container that performs data processing from the migration source device 200 to the migration target device 300.

[0039] In Fig. 1. Arrows with solid lines indicate data flows before migration, arrows with broken lines indicate data flows after migration, and arrows with alternating long and short lines with dashed lines indicate data flows during migration.

[0040] A configuration of the migration source device 200 is described with reference to Fig. 2 described.

[0041] The migration source device 200 is a computer equipped with hardware components such as a processor 201, main memory 202, auxiliary storage device 203, communication device 204, and input / output interface 205. These hardware components are interconnected via a signal line.

[0042] The Processor 201 is an integrated circuit (IC) that performs computing and controls other hardware components. The Processor 201 is, for example, a CPU.

[0043] It should be noted that IC stands for Integrated Circuit.

[0044] It should be noted that CPU stands for Central Processing Unit.

[0045] The main memory (RAM) is a volatile or non-volatile memory device. It is also referred to as main memory or main storage. For example, RAM is a memory device. Data stored in RAM is backed up to auxiliary memory (AMO) as needed.

[0046] It should be noted that RAM stands for Random-Access Memory.

[0047] Auxiliary storage device 203 is a non-volatile storage device. Auxiliary storage device 203 is, for example, a ROM, a hard disk drive (HDD), flash memory, or a combination thereof. The data stored in auxiliary storage device 203 is loaded into main memory 202 as needed.

[0048] It should be noted that ROM stands for Read-Only Memory.

[0049] It should be noted that HDD stands for Hard Disk Drive.

[0050] The communication device 204 is a receiver and a transmitter. For example, the communication device 204 is a communication chip or a NIC. The migration source device 200 performs the communication via the communication device 204.

[0051] It should be noted that NIC stands for Network Interface Card.

[0052] The input / output interface 205 is a port to which an input device and an output device are connected. For example, the input / output interface 205 is a USB port, the input device is a keyboard and a mouse, and the output device is a display. Input to and output from the migration source device 200 is via the input / output interface 205.

[0053] It should be noted that USB stands for Universal Serial Bus.

[0054] The migration source device 200 is equipped with elements such as a container unit 210, a proxy unit 220, and a migration management unit 230. These elements are implemented by software.

[0055] Container unit 210 runs the request source container 110 and the migration source container 130.

[0056] Proxy unit 220 executes migration source proxy 120.

[0057] Migration Management Unit 230 is performing the container migration.

[0058] Auxiliary storage device 203 stores a migration source program that instructs a computer to operate as container unit 210, proxy unit 220, and migration management unit 230. The migration source program includes a container migration program that causes the computer to operate as migration management unit 230.

[0059] The migration source program is loaded into memory 202 and executed by processor 201.

[0060] Furthermore, the auxiliary storage device 203 stores an operating system. At least part of the operating system is loaded into the main memory 202 and executed by the processor 201.

[0061] The 201 processor executes the migration source program while running the OS.

[0062] It should be noted that OS stands for Operating System.

[0063] Input and output data of the migration source program are stored in a storage unit 290.

[0064] The main memory 202 operates as the memory unit 290. It should be noted that a memory device such as the auxiliary memory device 203, a register in the processor 201, and a cache memory in the processor 201 can operate as the memory unit 290 instead of the main memory 202, or together with the main memory 202.

[0065] The migration source device 200 can be equipped with a variety of processors that replace the processor 201.

[0066] The migration source program can be recorded (stored) in a computer-readable format on a non-volatile recording medium such as an optical disk and flash memory.

[0067] A configuration of the migration management unit 230 is described with reference to Fig. 3 described.

[0068] The migration management unit 230 is equipped with a migration target generation unit 231, a first transition unit 232, a migration source stop unit 233, a volume migration unit 234, a migration target activation unit 235, a second transition unit 236 and a transfer target change unit 237.

[0069] A configuration of the migration target device 300 is described with reference to Fig. 4 described.

[0070] The migration target device 300 is a computer equipped with hardware components such as a processor 301, main memory 302, auxiliary storage device 303, communication device 304, and an input / output interface 305. These hardware components are interconnected via a signal line.

[0071] The 301 processor is an integrated circuit (IC) that performs computing and controls other hardware components. The 301 processor is, for example, a CPU.

[0072] RAM 302 is a volatile or non-volatile memory device. It is also referred to as main memory or main storage. For example, RAM 302 is a memory module. Data stored in RAM 302 is backed up to auxiliary memory 303 as needed.

[0073] Auxiliary memory device 303 is a non-volatile memory device. Auxiliary memory device 303 can be, for example, a ROM, a hard disk drive (HDD), flash memory, or a combination thereof. Data stored in auxiliary memory device 303 is loaded into main memory 302 as needed.

[0074] The communication device 304 is a receiver and a transmitter. For example, the communication device 304 is a communication chip or a NIC. The migration target device 300 performs the communication via the communication device 304.

[0075] The input / output interface 305 is a port to which an input device and an output device are connected. For example, the input / output interface 305 is a USB port, the input device is a keyboard and a mouse, and the output device is a display. Input to and output from the migration target device 300 is via the input / output interface 305.

[0076] The migration target device 300 is equipped with elements such as a container unit 310 and a proxy unit 320. These elements are implemented by software.

[0077] Container unit 310 generates and executes the migration target container 150.

[0078] Proxy unit 320 generates and executes the migration target proxy 140.

[0079] Auxiliary storage unit 303 stores a migration target program that causes a computer to operate as the container unit 310 and the proxy unit 320. The migration target program is loaded into memory 302 and executed by processor 301.

[0080] Furthermore, the auxiliary memory device 303 stores an operating system. At least part of the operating system is loaded into the main memory 302 and executed by the processor 301.

[0081] The 301 processor executes the migration target program while running the OS.

[0082] Input and output data of the migration target program are stored in a storage unit 390.

[0083] The main memory 302 functions as the memory unit 390. It should be noted that a memory device such as the auxiliary memory device 303, a register in the processor 301, and a cache memory in the processor 301 can function as the memory unit 390 instead of the main memory 302, or together with the main memory 302.

[0084] The migration target device 300 can be equipped with a variety of processors that replace the processor 301.

[0085] The migration target program can be recorded (stored) in a computer-readable format on a non-volatile recording medium such as an optical disk and flash memory. *** Description of work processes ***

[0086] A workflow of the migration management unit 230 corresponds to a container migration procedure. A workflow of the migration management unit 230 also corresponds to a processing flow performed by the container migration program.

[0087] An overview of the container migration process is provided with reference to the Fig. 5 to 8 described.

[0088] Fig. Figure 5 shows a state of the pre-migration information processing system 100.

[0089] The request source container 110, the migration source proxy 120, and the migration source container 130 run in the migration source device 200.

[0090] The request source container 110 has transfer destination information 111. This transfer destination information 111 specifies the migration source proxy 120 as the data transfer destination. The proxy is identified, for example, by a port number or a URL. Note that URL stands for Uniform Resource Locator.

[0091] Migration source proxy 120 has a queue 121.

[0092] The migration source container 130 has a volume 131 and an image 132. Volume 131 is prepared in a read / write memory area. For data processing purposes, data is primarily read from and written to volume 131. Image 132 is prepared in a read-only area. A library, a program, etc., for data processing is stored in image 132.

[0093] The request source container 110 transmits a package to the migration source proxy 120. The package contains a data processing request and the data to be processed.

[0094] Migration source proxy 120 receives the packet transmitted by request source container 110 and queues the received packet in queue 121. Migration source proxy 120 then clears the packet's queue in the order it was queued and transfers the packet to migration source container 130.

[0095] The migration source container 130 receives the packet transferred by the migration source proxy 120 and processes the data in the received packet according to the request in the received packet.

[0096] Fig. Figure 6 shows a state of the information processing system 100 during migration (1).

[0097] Migration source proxy 120 receives the packet transmitted by request source container 110 and stores the received packet in queue 121 (queueing). Migration source proxy 120 then transfers the packet to migration source container 130.

[0098] Migration source container 130 is being stopped.

[0099] The migration target device 300 generates the migration target proxy 140 and the migration target container 150.

[0100] The migration target proxy 140 has a queue 141. Queue 141 corresponds to queue 121.

[0101] The migration source container 150 has a volume 151 and an image 152. Volume 151 corresponds to volume 131. Image 152 corresponds to image 132.

[0102] Fig. Figure 7 shows a state of the information processing system 100 during migration (2).

[0103] The migration target container 150 is activated.

[0104] The migration source proxy 120 transfers the package secured in queue 121 to the migration destination proxy 140 in the secured order.

[0105] Migration destination proxy 140 receives the packet transmitted by migration destination proxy 120 and adds the received packet to queue 141. Migration destination proxy 140 then removes the packet from the queue in the order in which it was added and transfers the packet to migration destination container 150.

[0106] The migration target container 150 receives the packet transferred from the migration target proxy 140 and processes the data in the received packet according to the request in the received packet.

[0107] Fig. Figure 8 shows a state of the post-migration information processing system 100.

[0108] The packet transfer from migration source proxy 120 to migration destination proxy 140 is complete.

[0109] The request source container 110 updates the transfer destination information 111 with the transfer destination information 112. The transfer destination information 112 specifies the migration target proxy 140 as the data transfer destination.

[0110] The request source container 110 sends a package to the migration target proxy 140.

[0111] The migration target proxy 140 receives the packet transmitted by the request source container 110 and queues the received packet in queue 141. The migration target proxy 140 then removes the packet from the queue in the order in which it was queued and transfers the packet to the migration target container 150.

[0112] The migration target container 150 receives the packet transferred from the migration target proxy 140 and processes the data in the received packet according to the request in the received packet.

[0113] The process of container migration is described with reference to the Fig. Described in sections 9 to 12.

[0114] Fig. Figure 9 shows a flowchart of the container migration process.

[0115] Fig. Figures 10 to 12 show the workflows of the Information Processing System 100.

[0116] Before the container migration begins, the migration source proxy 120 operates in a transfer mode.

[0117] The transfer mode is an operating mode in which data is received from the request source container 110 and transferred to a request destination container. At this point, the request destination container is the migration source container 130. The data is contained in the package.

[0118] Migration source container 130 is working.

[0119] The process following the start of the container migration is explained below.

[0120] In step S110, the migration target generation unit 231 causes the migration target device 300, the migration target container 150, and the migration target proxy 140 to be generated.

[0121] The migration target container 150 is generated in the following way.

[0122] The migration target generation unit 231 transmits a container generation request with image 132 of the migration source container 130 to the migration target device 300.

[0123] Container unit 310 receives the container generation request and generates the migration target container 150 using image 132.

[0124] It should be noted that container unit 310 did not activate migration target container 150. This means that migration target container 150 was stopped.

[0125] The migration target proxy 140 is generated in the following way.

[0126] The migration target generation unit 231 receives a proxy generation request to the migration device 300.

[0127] The proxy unit 320 generates the migration target proxy 140, activates the migration target proxy 140, and sets the operating mode of the migration target proxy 140 to transfer mode.

[0128] In step S120, the first transition unit 232 causes the operating mode of the migration source proxy 120 to change from transfer mode to a queue mode.

[0129] Queue mode is a working mode for saving data instead of transferring it.

[0130] The operating mode of the migration source proxy 120 changes as follows.

[0131] The first transition unit 232 instructs the proxy unit 220 to change its operating mode to queue mode.

[0132] Proxy unit 220 changes the operating mode of migration source proxy 120 to queue mode according to the instruction.

[0133] During queue mode, the migration source proxy 120 secures the data transmitted by the request source container 110 to the queue 121.

[0134] In step S130, the migration source stop unit 233 stops the migration source container 130.

[0135] The migration source container 130 is stopped in the following way.

[0136] The migration source stop unit 233 instructs the container unit 210 to stop the migration source container 130.

[0137] Container unit 210 stops migration source container 130 according to the instruction.

[0138] In step S140, the volume migration unit 234 migrates volume 131 from the migration source container 130 to the migration target container 150.

[0139] Volume 131 is migrated in the following manner.

[0140] The volume migration unit 234 transfers the volume 131 of the migration source container 130 to the migration target device 300.

[0141] Container unit 310 receives volume 131 and updates volume 151 of the migration target container 150 using volume 131.

[0142] In step S150, the migration target activation unit 235 activates the migration target container 150.

[0143] The migration source container 150 is activated in the following way.

[0144] The migration target activation unit 235 transmits a container activation request to the migration target device 300.

[0145] Container unit 310 receives the container activation request and activates the migration target container 150.

[0146] The migration target container 150 is starting its work process.

[0147] In step S160, the second transition unit 236 causes the operating mode of the migration source proxy 120 to change from queue mode to queue sending mode.

[0148] The queue send mode is a working mode for sending secured data to the migration target proxy 140.

[0149] The operating mode of the migration source proxy 120 changes as follows.

[0150] The second transition unit 236 instructs the proxy unit 220 to change its operating mode to queue transmission mode.

[0151] Proxy unit 220 changes the operating mode of migration source proxy 120 to queue transfer mode according to the instruction.

[0152] During queue send mode, the migration source proxy 120 transmits the data backed up in queue 121 to the migration target proxy 140 in the backed-up order.

[0153] When data is received from the request source container 110, the migration source proxy 120 queues the received data into queue 121. The queued data is then forwarded to the migration target proxy 140.

[0154] When all the data backed up in queue 121 has been transferred and queue 121 is empty, proxy unit 220 reports to migration management unit 230 that the sending is complete.

[0155] If data is subsequently received from the request source container 110, the migration source proxy 120 queues the received data into queue 121. The queued data is then forwarded to the migration target proxy 140.

[0156] In step S170, the transfer target change unit 237 causes the request source container 110 to change a data transfer target from the migration source proxy 120 to the migration target proxy 140.

[0157] The data transfer destination is changed in the following way.

[0158] The transfer target change unit 237 instructs the container unit 210 to change the transfer target to the migration target proxy 140.

[0159] Container unit 210 changes the transfer destination specified in the transfer destination information 111 from migration source proxy 120 to migration destination proxy 140 according to the instruction.

[0160] After step 5170, the container migration is complete.

[0161] After the container migration is complete, the request source container 110 transfers data to the migration target proxy 140.

[0162] The migration source proxy 140 receives the data from the request source container 110 and transfers the received data to the migration target container 150.

[0163] The migration target container 150 receives the data from the migration target proxy 140 and processes the received data. *** Description of the implementation example ***

[0164] The migration management unit 230 can be made available to the migration destination device 300 instead of the migration source device 200 or any other device.

[0165] Image 132 of migration source container 130 does not necessarily have to be transferred at the time of generation of migration destination container 150 (S110).

[0166] It is sufficient if image 132 is transferred before the migration target container 150 is activated. Image 132 can, for example, be transferred at the time of the migration of volume 131 (S140).

[0167] If image 132 is transferred in advance, the time required from stopping the migration source container 130 until the migration target container 150 has migrated can be reduced. *** Effect of embodiment 1 ***

[0168] Embodiment 1 provides a technique that makes it possible to perform processing with the container in the order of the request without losing a request from a function block of the request source while the container is stopped.

[0169] In embodiment 1, a communication proxy is introduced that allows a packet (a request, data) to be queued between containers. In embodiment 1, during the migration of a container, the container's operating mode is switched accordingly, so that the target container can process all packets sequentially without packet loss, even during the migration. *** Supplement to embodiment 1 ***

[0170] A configuration of the migration source device 200 is described with reference to Fig. 13 described.

[0171] The migration source device 200 is equipped with a processing circuit 209.

[0172] The processing circuit 209 is a piece of hardware that implements the container unit 210, the proxy unit 220, and the migration management unit 230.

[0173] The processing circuit209 can be dedicated hardware or a processor201 that executes the program stored in the main memory202.

[0174] If the processing circuit 209 is dedicated hardware, then the processing circuit 209 is, for example, a single circuit, a compound circuit, a programmed processor, a parallel programmed processor, an ASIC, or an FPGA.

[0175] It should be noted that ASIC stands for Application Specific Integrated Circuit.

[0176] It should be noted that FPGA stands for Field Programmable Gate Array.

[0177] The migration source device 200 can be equipped with a variety of processing circuits that replace the processing circuit 209.

[0178] In the processing circuit 209, some of the functions can be implemented by dedicated hardware, and the remaining functions can be implemented by software or firmware.

[0179] In this way, the functions of the migration source device 200 can be implemented by one or a combination of hardware, software and firmware.

[0180] A hardware configuration of the migration target device 300 is described with reference to Fig. 14 described.

[0181] The migration target device 300 is equipped with a processing circuit 309.

[0182] The processing circuit 309 is a hardware component that implements the container unit 310 and the proxy unit 320.

[0183] The processing circuit 309 can be dedicated hardware or a processor 301 that executes the program stored in the main memory 302.

[0184] If the processing circuit 309 is dedicated hardware, then the processing circuit 309 is, for example, a single circuit, a compound circuit, a programmed processor, a parallel programmed processor, an ASIC, or an FPGA.

[0185] The migration source device 200 can be equipped with a variety of processing circuits that replace the processing circuit 209.

[0186] In the 309 processing circuit, some of the functions can be implemented by dedicated hardware, and the remaining functions can be implemented by software or firmware.

[0187] In this way, the functions of the migration target device 300 can be implemented by one or a combination of hardware, software and firmware.

[0188] Embodiment 1 is an example of a preferred mode and is not intended to limit the technical scope of this disclosure. Embodiment 1 can be implemented in practice, either partially or in combination with another mode. The processes described using the flowcharts, etc., can be modified accordingly.

[0189] The word “unit” in each element of the migration source device 200 and the migration destination device 300 can be replaced by “process”, “stage”, “circuit” or “circuit”. Reference symbol list

[0190] 100: Information processing system; 101: Network; 110: Request source container; 111: Destination information; 112: Destination information; 120: Migration source proxy; 121: Queue; 130: Migration source container; 131: Volume; 132: Image; 140: Destination proxy; 141: Queue; 150: Destination container; 151: Volume; 152: Image; 200: Migration source device; 201: Processor; 202: Memory; 203: Auxiliary memory device; 204: Communication device; 205: Input / output interface; 209: Processing circuit; 210: Container unit; 220: Proxy unit; 230: Migration management unit; 231: Destination generation unit; 232: First transition unit; 233: Migration source stop unit; 234: Volume migration unit; 235: Migration destination activation unit; 236: Second transition unit; 237: Transfer destination change unit; 290: Storage unit; 300: Migration destination device; 301: Processor; 302: Main memory;303: Auxiliary storage device; 304: Communication device; 305: Input / output interface; 309: Processing circuit; 310: Container unit; 320: Proxy unit; 390: Storage unit.; QUOTES INCLUDED IN THE DESCRIPTION

[0000] This list of documents cited by the applicant was automatically generated and is included solely for the reader's convenience. The list is not part of the German patent or utility model application. The DPMA accepts no liability for any errors or omissions. Cited patent literature

[0000] JP 2019-530072 A

[0014]

Claims

[1] Container migration device that migrates a container performing data processing from a migration source device to a migration target device, wherein the migration source device is a device in which a migration source container and a migration source proxy operate, wherein the migration target device is a device in which a migration target container and a migration target proxy operate, where the container migration facility comprises: a first transition unit for causing an operation mode of the migration source proxy to transition from a transfer mode of: receiving data transmitted from a request source container that requests data processing; and transferring the received data to the migration source container that is a request target container, to a queue mode of saving the data instead of transferring it; a second transition unit for causing, after the working mode of the migration source proxy has transitioned to the queue mode and the migration target container is activated, the working mode of the migration source proxy to transition to a queue sending mode of sending the backed up data to the migration target proxy; and a transfer destination change unit for causing the request source container to change a data transfer destination from the migration source proxy to the migration destination proxy after the completion of sending the secured data. [2] Container migration device according to claim 1, comprising: a migration target generation unit for causing the migration target device to generate the migration target container and the migration target proxy; a migration source stop unit to stop the migration source container after the working mode of the migration source proxy enters the queue mode; a volume migration unit to migrate a volume from the migration source container to the migration target container after the migration source container is stopped; and a migration target activation unit to activate the migration target container after the volume has been migrated. [3] Container migration method of migrating a container that performs data processing from a migration source device to a migration target device, wherein the migration source device is a device in which a migration source container and a migration source proxy operate, wherein the migration target device is a device in which a migration target container and a migration target proxy operate, where the container migration process includes: Causing an operation mode of the migration source proxy to transition from a transfer mode of: receiving data transmitted from a request source container that requests data processing; and transferring the received data to the migration source container that is a request target container, to a queue mode of backing up the data instead of transferring it; after the working mode of the migration source proxy has transitioned to queue mode and the migration target container is activated, causing the working mode of the migration source proxy to transition to a queue sending mode of sending the backed up data to the migration target proxy; and After sending the backed up data, cause the request source container to change a data transfer destination from the migration source proxy to the migration target proxy. [4] Container migration method of migrating a container that performs data processing from a migration source device to a migration target device, wherein the migration source device is a device in which a migration source container and a migration source proxy operate, wherein the migration target device is a device in which a migration target container and a migration target proxy operate, where the container migration process includes: Receiving data transmitted from a request source container requesting data processing; and transferring the received data to the migration source container, which is a request target container; after receiving an instruction to transition from a transfer mode to a queue mode, receiving the data transferred from the request source container; and saving the received data instead of transferring it; and After receiving an instruction to transition from queue mode to queue sending mode, sending the backed up data to the migration target proxy. [5] Container migration program to migrate a container that performs data processing from a migration source device to a migration target device, wherein the migration source device is a device in which a migration source container and a migration source proxy operate, wherein the migration target device is a device in which a migration target container and a migration target proxy operate, where the container migration program is used to cause a computer to run: a first transition process of causing a working mode of the migration source proxy to transition from a transfer mode of: receiving data transmitted from a request source container that requests data processing; and transferring the received data to the migration source container that is a request target container, to a queue mode of saving the data instead of transferring it; a second transition process of causing, after the working mode of the migration source proxy has transitioned to the queue mode and the migration target container is activated, the working mode of the migration source proxy to transition to a queue sending mode of sending the backed up data to the migration target proxy; and a transfer destination change process of causing the request source container to change a data transfer destination from the migration source proxy to the migration destination proxy after completion of sending the secured data.

Images