Changes

! task

! task

! assignee

! assignee

! comments

! comments

|-

|-

| crtools/kernel || memory snapshot || xemul@ || - || need to take mem snapshot in kernel for iterative migration, (probably) rebootless upgrade and HA

| crtools/kernel || memory snapshot || xemul@ || need to take mem snapshot in kernel for iterative migration, (probably) rebootless upgrade and HA

|-

|-

| crtools || TCP socket migration with changed IP || xemul@ || - || it might make sense to migrate a tcp connection on a box with changed IP address _if_ both boxes are NAT-ed to the destination. We will then have to go to NAT box and fix the conntracks, but this might make sense.

| crtools || TCP socket migration with changed IP || xemul@ || it might make sense to migrate a tcp connection on a box with changed IP address _if_ both boxes are NAT-ed to the destination. We will then have to go to NAT box and fix the conntracks, but this might make sense.

|-

|-

| crtools/kernel || madvise bits || - || - || currently we just drop these bits, since we have no API to find them out on dump

| crtools/kernel || madvise bits || - || currently we just drop these bits, since we have no API to find them out on dump

|-

|-

| crtools || Shared objects (mm/fs/fdtable) support || avagin@ || not implemented || Now we have the kcmp syscall and can do it. The first candidate is mm sharing, as we do know, that MySQL does so sometimes.

| crtools || Shared objects (mm/fs/fdtable) support || avagin@ || Now we have the kcmp syscall and can do it. The first candidate is mm sharing, as we do know, that MySQL does so sometimes.

|-

|-

| kernel || Provide own defconfig || gorcunov@ || not implemented || suggested by avagin@

| kernel || Provide own defconfig || gorcunov@ || suggested by avagin@

|-

|-

| crtools || Paranoid dumping and restoring || - || - || Make paranoid checks for what we dump. E.g. pgid being valid (withing session) and fds drained from parasite are valid

| crtools || Paranoid dumping and restoring || - || Make paranoid checks for what we dump. E.g. pgid being valid (withing session) and fds drained from parasite are valid

|-

|-

| kernel || Proc fdinfo extension || gorcunov@ || in progress || Need to rework and resubmit the patches

| kernel || Proc fdinfo extension || gorcunov@ || Need to rework and resubmit the patches

|-

|-

| kernel/crtools || posix timers || skinsbursky@ || - || Need new kernel API for a) listing existing timers and b) fetching timer notify configuration.

| kernel/crtools || posix timers || skinsbursky@ || Need new kernel API for a) listing existing timers and b) fetching timer notify configuration.

|-

|-

| crtools || Smart paths resolution || - || - || Need a way to resolve paths to overmounted files. There are two ways: 1. Move mounts, that overlap the desired path temprarily. 2. When creating a new mount pre-open an fd keeping the mountpoint. Later, do accurate path resolve and call openat() on proper mountpoint fd

| crtools || Smart paths resolution || - || Need a way to resolve paths to overmounted files. There are two ways: 1. Move mounts, that overlap the desired path temprarily. 2. When creating a new mount pre-open an fd keeping the mountpoint. Later, do accurate path resolve and call openat() on proper mountpoint fd

|-

|-

| kernel/crtools || TCP connection fixup || - || - || When we turn repair off a window probe is sent by kernel. It can be lost and we leave with stuck connection. Plus, the keepalive timer isn't rearmed on repaired socket connect, probably this is the way to solve this.

| kernel/crtools || TCP connection fixup || - || When we turn repair off a window probe is sent by kernel. It can be lost and we leave with stuck connection. Plus, the keepalive timer isn't rearmed on repaired socket connect, probably this is the way to solve this.

|-

|-

| crtools || Iptables || - || - || This is easy. Need to run ipdables-save and iptables-restore

| crtools || Iptables || - || This is easy. Need to run ipdables-save and iptables-restore

|-

|-

| kernel/crtools || Auto namespaces detection || - || - || Now we "detect" them by looking at cmdline options

| kernel/crtools || Auto namespaces detection || - || Now we "detect" them by looking at cmdline options

|-

|-

| crtools || Migration w/o intermediate disk || Adrian Reber || - || -

| crtools || Migration w/o intermediate disk || Adrian Reber || -

|-

|-

| kernel/crtools || TUN/TAP || - || - || -

| kernel/crtools || TUN/TAP || - || -

|-

|-

| kernel/crtools || tcpdump || xemul@ || - || The diag modules extensions are on their way to net-next. Next is -- socket filters

| kernel/crtools || tcpdump || xemul@ || The diag modules extensions are on their way to net-next. Next is -- socket filters

|-

|-

| vzkernel/crtools || OpenVZ kernel support || - || - || Within 3.5 and RHEL7 port

| vzkernel/crtools || OpenVZ kernel support || - || Within 3.5 and RHEL7 port

|-

|-

| crtools || More sockoptions || - || - ||

| crtools || More sockoptions || - || -

|-

|-

| crtools || Bridges in container || - || - ||

| crtools || Bridges in container || - ||

|-

|-

| crtools || cgroups in container || - || - ||

| crtools || cgroups in container || - ||

|-

|-

| crtools/kernel || NFS || - || - ||

| crtools/kernel || NFS || - ||

|-

|-

| crtools/kernel || VDSO || - || - || issues: VDSO may change between kernels; vsyscall may change between kernels; VDSO mapping should be VDSO mapping, not regular one

| crtools/kernel || VDSO || - || issues: VDSO may change between kernels; vsyscall may change between kernels; VDSO mapping should be VDSO mapping, not regular one

|-

|-

| crtools || Unmap a restorer VMA || - || - || [https://docs.google.com/spreadsheet/ccc?key=0Au56mM6UWU8mdGhmYURYZGZhbmxBLWVmVnhBT3VXVHc#gid=0 Lots] of ideas were generated so far.

| crtools || Unmap a restorer VMA || - || [https://docs.google.com/spreadsheet/ccc?key=0Au56mM6UWU8mdGhmYURYZGZhbmxBLWVmVnhBT3VXVHc#gid=0 Lots] of ideas were generated so far.

|-

|-

| crtools || file locks || - || - || It's hard to do it carefully. We need to make sure that all lock users are taken into dump. Only support it inside container?

| crtools || file locks || - || It's hard to do it carefully. We need to make sure that all lock users are taken into dump. Only support it inside container?

|}

|}