| 1 | | This experiment illustrates how to accomplish service migrations using containers. |
| | 1 | == Container Service Migration == |
| | 2 | |
| | 3 | === Description === |
| | 4 | Containers run at the user-space process over the Kernel and have better bandwidth and CPU performance as compared to VMs. The shared resource dynamic container migration approach, therefore, can be used to address deteriorating application QoS, arising from the processing latency (system load) and/or the network latency (user mobility). |
| | 5 | |
| | 6 | This tutorial demonstrates how to accomplish service migrations using containers. |
| | 7 | |
| | 8 | === Prerequisites === |
| | 9 | In order to access the testbed, create a reservation, and have it approved by the reservation service. Access to the resources is granted after the reservation is confirmed. Please follow the process shown on [wiki:cosmos_workflow the COSMOS work flow page] to get started. |
| | 10 | |
| | 11 | === Resources required === |
| | 12 | Three nodes are required to run this experiment. |
| | 13 | |
| | 14 | === Topology === |
| | 15 | The following topology is used in this experiment. The registry node stores the container layer information which can be queried by any of the nodes. The migration from the source to the destination takes place using multiple container layers. |
| | 16 | |
| | 17 | |
| | 18 | |
