<div dir="ltr"><div>I have a few followup queries. For my purposes, I have modified the live migration script to allow me to do cloning... i.e. I start both the containers instead of deleting the original. I need to do this "cloning" from time to time for the same target container... </div><div><br></div><div>1. Which means that lets say we cloned container C1 to container C2, and let both execute at time t0, this works with no apparent loss of service.</div><div><br></div><div>2. Now at time t1 I would like to again clone C1 to C2, and would like to optimize the rsync process as most of the ploop file for C1 and C2 should still be the same (i.e. less time to sync). Can anyone suggest what would be the best way to realize the second point? </div><div><br></div><div><br></div><div>As a background: I use the following command when I do vzmigrate, I was wondering if there are any other options that need to be used, for e.g. as reported vzfsync etc, </div><div><div><br></div><div><p style="margin:0px;font-size:14px;font-family:Monaco">vzmigrate --online --times --live 192.168.122.10 101</p><p style="margin:0px;font-size:14px;font-family:Monaco">Starting live migration of CT 101 to 192.168.122.10</p><p style="margin:0px;font-size:14px;font-family:Monaco">Preparing remote node</p><p style="margin:0px;font-size:14px;font-family:Monaco">Syncing private</p><p style="margin:0px;font-size:14px;font-family:Monaco">Usage: vzfsync {-s|-d} [-n] file [file ...]</p><p style="margin:0px;font-size:14px;font-family:Monaco"> -s, --sync do fsync()</p><p style="margin:0px;font-size:14px;font-family:Monaco"> -d, --datasync do fdatasync()</p><p style="margin:0px;font-size:14px;font-family:Monaco"> -n, --dontneed do fadvise(DONTNEED)</p><p style="margin:0px;font-size:14px;font-family:Monaco">
</p><p style="margin:0px;font-size:14px;font-family:Monaco">Live migrating container...</p><div><br></div><div>The following has been used to create the container</div><div><br></div><div><p style="margin:0px;font-size:14px;font-family:Monaco">vzctl create $1 --ostemplate centos-6-x86_64 --config basic --layout ploop</p><p style="margin:0px;font-size:14px;font-family:Monaco"><br></p></div><div><br></div><p style="margin:0px;font-size:14px;font-family:Monaco">Thanks</p><p style="margin:0px;font-size:14px;font-family:Monaco">Nipun</p></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Nov 22, 2014 at 12:09 PM, Nipun Arora <span dir="ltr"><<a href="mailto:nipunarora2512@gmail.com" target="_blank">nipunarora2512@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi All,<div><br></div><div>I was wondering if anyone can suggest what is the most optimal way to do the following</div><div><br></div><div>1. Can anyone clarify if ploop is the best layout for minimum suspend time during live migration?</div><div><br></div><div>2. I tried migrating a ploop device where I increased the --diskspace to 5G, and found that the suspend time taken by live migration increased to 57 seconds (mainly undump and restore increased)... whereas a 2G diskspace was taking 2-3 seconds suspend time... Is this expected?</div><div><br></div><div>3. I tried running a write intensive workload, and found that beyond 100-150Kbps, the suspend time during live migration rapidly increased? Is this an expected trend?</div><div><br></div><div>I am using vzctl 4.7, and ploop 1.11 in centos 6.5</div><div><br></div><div>Thanks</div><span class="HOEnZb"><font color="#888888"><div>Nipun</div></font></span></div>
</blockquote></div><br></div>