Hi,
I am looking for a functionality similar to "Live Clone"...
i.e. I would like to clone an existing running container, such that the
clone is a copy of the original.
This would be similar to something like live migration without
suspending/stopping the original container.
Can anyone suggest a
which are running still be running if I restore from the snapshot?
Thanks
Nipun
On Thursday, April 10, 2014, Andrew Vagin wrote:
> On Wed, Apr 09, 2014 at 02:14:30AM -0400, Nipun Arora wrote:
> > Hi,
> >
> > I am looking for a functionality similar to "Live Clone"..
Hi All,
I was wondering if anyone can suggest what is the most optimal way to do
the following
1. Can anyone clarify if ploop is the best layout for minimum suspend time
during live migration?
2. I tried migrating a ploop device where I increased the --diskspace to
5G, and found that the suspend
EED)
Live migrating container...
The following has been used to create the container
vzctl create $1 --ostemplate centos-6-x86_64 --config basic --layout ploop
Thanks
Nipun
On Sat, Nov 22, 2014 at 12:09 PM, Nipun Arora
wrote:
> Hi All,
>
> I was wondering if anyone can suggest what
uring the suspend?
> It might also be useful for you to track the size of the dump file.
>
> Nipun Arora
> Saturday, November 22, 2014 12:09 PM
> Hi All,
>
> I was wondering if anyone can suggest what is the most optimal way to do
> the following
>
> 1. Can anyone c
olyshkin wrote:
>
> On 11/22/2014 09:09 AM, Nipun Arora wrote:
>
> Hi All,
>
> I was wondering if anyone can suggest what is the most optimal way to do
> the following
>
> 1. Can anyone clarify if ploop is the best layout for minimum suspend
> time during live migra
wrote:
>
> On 11/23/2014 04:59 AM, Nipun Arora wrote:
>
> Hi Kir,
>
> Thanks for the response, I'll update it, and tell you about the results.
>
> 1. A follow up question... I found that the write I/O speed of 500-1Mbps
> increased the suspend time to several minu
quot;0"
# CPU fair scheduler parameter
CPUUNITS="1000"
NETFILTER="stateless"
VE_ROOT="/vz/root/101"
VE_PRIVATE="/vz/private/101"
OSTEMPLATE="centos-6-x86_64"
ORIGIN_SAMPLE="basic"
HOSTNAME="test"
IP_ADDRESS="192.16
Nevermind, I figured it out by changing the fail counters in
/proc/user_beans
Thanks
Nipun
On Thu, Nov 27, 2014 at 7:14 PM, Nipun Arora
wrote:
> Thanks, the speed is improved by an order of magnitude :)
>
> btw. is there any benchmark, that you all have looked into for testing h
Hi folks,
I thought I'd ask this in a different thread to make it easier for people
like myself to search for answers through email archives :)
I think vswap should be made the "default" in OpenVZ rather than having a
complicated way to convert the containers to "vswap
containers".Understanding U
be
> secure enough.
>
> Kir.
>
>
>
>> On Fri, Nov 28, 2014 at 10:35 AM, CoolCold wrote:
>>
>>> Hello!
>>> I'd recommend set only ram/swap limits (via --ram/--swap) , letting other
>>> settings be mostly unlimited (while ram/swap li
Thanks.. This explanation is very useful
Nipun
On Friday, November 28, 2014, Kevin Holly [Fusl]
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 11/28/2014 03:47 PM, Nipun Arora wrote:
> > Hi folks,
> Hi Nipun!
>
> > 1. --cpu-limit puts a limit on
12 matches
Mail list logo
