[Devel] [Q] migrating inotify assigned on ploop device

[Igor]

On 01/12/2016 12:59 PM, Cyrill Gorcunov wrote:
> On Tue, Jan 12, 2016 at 12:51:05PM +0300, Igor wrote:
>> On 01/12/2016 12:42 PM, Cyrill Gorcunov wrote:
>>> On Tue, Jan 12, 2016 at 12:26:09PM +0300, Igor wrote:
>>>>>> Been talking to Pavel and the proper general solutions is "device namespace" which
>>>>>> require significant kernel update/rework so I don't consider it as a solution
>>>>>> which could be implemented in a day or two. Instead another option might be
>>>>>> to use CRIT tool and decode|encode device path on the fly via libvzctl or
>>>>>> p.haul project.
>>>>>>
>>>>>> Any other ideas comments?
>>>>> After another talk with Pavel it seems the only reasonable solution is
>>>>> to recode ploop names in all images when migrating with help of
>>>>> crit tool and p.haul? Nikita, could you please take a look and
>>>>> figure out if this may be implemented?
>>>> This is not only migration problem but suspend/resume in general, on CT
>>>> resume ploop decide is autogenerated.
>>> Then libvzctl should use crit decode|encode facility as well for ploop
>>> device name mapping.
>> What is api?
>> Can I pass some id to mark ploop on suspend/resume <ID:DEVICE>
>>
>> suspend
>> 17b176df-55b6-46c2-9284-67f4475588df : ploop1
>>
>> resume
>> 17b176df-55b6-46c2-9284-67f4475588df : ploop2
> I fear it's not that simple. Look, in CRIU bundle we've a tool named
I do not see any troubles. user provide mapping by ID
on restore criu have all information ID:OLD-DEVICE:NEW-DEVICE

Ok. let me know when your design will be ready.