Changes

Jump to navigation Jump to search
no edit summary
Line 1: Line 1:  
Welcome to Linux Plumbers Conference 2015
 
Welcome to Linux Plumbers Conference 2015
 +
 +
[[Image:LPC-microconf-2015.jpg|right|thumb|300px]]
    
The structure will be short introductions to an issue or topic followed by a discussion with the audience.
 
The structure will be short introductions to an issue or topic followed by a discussion with the audience.
Line 21: Line 23:  
* Question: is there a mechanism/plugin/whatever to migrate a container that is tied to a FPGA or a GPU, so they should be migrated together?
 
* Question: is there a mechanism/plugin/whatever to migrate a container that is tied to a FPGA or a GPU, so they should be migrated together?
 
Answer: yes, there is a tool for it.
 
Answer: yes, there is a tool for it.
      
== CRIU in HPC ==
 
== CRIU in HPC ==
Line 34: Line 35:  
* key features of CRIU project: upstream inclusion, transparent solution wo pre-loading or re-compilation, most functionality in userspace, using standard interfaces as much as possible
 
* key features of CRIU project: upstream inclusion, transparent solution wo pre-loading or re-compilation, most functionality in userspace, using standard interfaces as much as possible
 
* summary: transparent migration works, OpenMPI supports CRIU (but keeps breaking as OpenMPI moves forward very fast), Parallel migration has WIP status
 
* summary: transparent migration works, OpenMPI supports CRIU (but keeps breaking as OpenMPI moves forward very fast), Parallel migration has WIP status
      
== CRIU on PowerPC ==
 
== CRIU on PowerPC ==
Line 47: Line 47:  
* The vector register save/restore can get confused in some rare signal call stack cases. Fixing this is in the todo list.
 
* The vector register save/restore can get confused in some rare signal call stack cases. Fixing this is in the todo list.
 
* A hindrance to getting docker up and running in CRIU/ppc is that the images it downloads at build/startup are x86_64 images. Help requested.
 
* A hindrance to getting docker up and running in CRIU/ppc is that the images it downloads at build/startup are x86_64 images. Help requested.
      
== CRIU Support in Docker for Native Checkpoint and Restore ==
 
== CRIU Support in Docker for Native Checkpoint and Restore ==
Line 72: Line 71:  
* CRIU part of live migration: perform nodes compat checks, pre-dumps in a loop, copy fs if not shared, don't forget container config
 
* CRIU part of live migration: perform nodes compat checks, pre-dumps in a loop, copy fs if not shared, don't forget container config
 
* P.Haul migrate container is two steps
 
* P.Haul migrate container is two steps
* More information about P.Haul: written in Python, source code https://github.com/xemul/p.haul/, can migrate OpenVZ container (How-to https://github.com/xemul/p.haul/blob/master/test/mtouch/HOWTO), call rsync on chroot-ed container
+
* More information about P.Haul: written in Python, source code https://github.com/checkpoint-restore/p.haul/, can migrate OpenVZ container (How-to https://github.com/checkpoint-restore/p.haul/blob/master/test/mtouch/HOWTO), call rsync on chroot-ed container
 
* P.Haul future: Docker/LXC support, smarter interations, shared FS autodetection, post-copy live migration, send images over the wire (CRIU)
 
* P.Haul future: Docker/LXC support, smarter interations, shared FS autodetection, post-copy live migration, send images over the wire (CRIU)
 
* Discussion of P.Haul started
 
* Discussion of P.Haul started
 
LXC has a similar concept, but slightly different. Consensus seems to be easy to achieve as to how to merge (it just needs coding effort).
 
LXC has a similar concept, but slightly different. Consensus seems to be easy to achieve as to how to merge (it just needs coding effort).
 
Predump allows process to continue running, vs full dump which is a freeze
 
Predump allows process to continue running, vs full dump which is a freeze
      
== Rebootless Kernel Update and its verification ==
 
== Rebootless Kernel Update and its verification ==
Line 93: Line 91:  
* evaluation: microbenchmark
 
* evaluation: microbenchmark
 
* Conclusion: implement native support for page cache, hugepages; on-demand restore with usefaultd; need to overhaul kexec
 
* Conclusion: implement native support for page cache, hugepages; on-demand restore with usefaultd; need to overhaul kexec
      
== Using CRIU for Computer Architecture and Software Studies ==
 
== Using CRIU for Computer Architecture and Software Studies ==
62

edits

Navigation menu