Techniques to run one or more containers on a virtual machine
AssigneeIntel Corporation
InventorsYao Zu Dong, Kun Tian
Life of this patent
Estimating the term…
Abstract
Examples may include techniques to run one or more containers on a virtual machine (VM). Examples include cloning a first VM to result in a second VM. The cloned first VM may run at least a set of containers capable of separately executing one or more applications. In some examples, some cloned containers are stopped at either the first or second VMs to allow for at least some resources provisioned to support the first or second VMs to be reused or recycled at a hosting node. In other examples, the second VM is migrated from the hosting node to a destination hosting node to further enable resources to be reused or recycled at the hosting node.
Claims25
At least one non-transitory machine readable medium comprising a plurality of instructions that in response to being executed by a system at a node cause the system to:
- clone a first virtual machine (VM) arranged to run at least one set of containers that includes a first container and a second container that are separately capable of executing respective first and second applications, the cloning to result in a second VM arranged to at least temporarily run the first and second containers concurrent with the first and second containers arranged to run at the first VM;
- switch a network connection for the second container arranged to run at the first VM to cause input/output packets associated with the second container capable of executing the second application to be re-routed from the first VM to the second VM;
- drop output packets generated by the second application executed by the second container arranged to run at the first VM following the switch of the network connection;
- and
- drop output packets generated by the first application executed by the first container arranged to run at the second VM.
An apparatus comprising:
- circuitry at a node configured to host a first virtual machine (VM) arranged to run at least one set of containers that includes a first container and a second container that are separately capable of executing respective first and second applications;
- a clone component for execution by the circuitry to clone the first VM to result in a second VM arranged to at least temporarily run the first and second containers concurrent with the first and second containers arranged to run at the first VM;
- a re-route component for execution by the circuitry to switch a network connection for the second container arranged to run at the first VM to cause input/output packets associated with the second container capable of executing the second application to be re-routed from the first VM to the second VM;
- a first drop component for execution by the circuitry to drop output packets generated by the second application executed by the second container arranged to run at the first VM following the switch of the network connection;
- and
- a second drop component for execution by the circuitry to drop output packets generated by the first application executed by the first container arranged to run at the second VM.
A method comprising:
- cloning, by circuitry at a node, a first virtual machine (VM) arranged to run at least one set of containers that includes a first container and a second container that are separately capable of executing respective first and second applications, the cloning to result in a second VM arranged to at least temporarily run the first and second containers concurrently with the first and second containers running at the first VM;
- switching a network connection for the second container running at the first VM to cause input/output packets associated with the second container executing the second application to be re-routed from the first VM to the second VM;
- dropping output packets generated by the second application executed by the second container running at the first VM following switching of the network connection;
- and
- dropping output packets generated by the first application executed by the first container running at the second VM.
Dependencies are inferred from the claim text.