| Ploop - anyone using in production yet? [message #45856] |
Mon, 09 April 2012 21:13  |
Rene
Messages: 40
Registered: September 2006
|
Member |
|
|
Is anyone running ploop in production yet. It is in the stable release branch but the Wiki page still says it is not save for production use. Is the Wiki page outdated, or what?
Would there be any conflict running ploop on top of LVM?
|
|
|
|
|
|
|
|
|
|
|
|
| Re: Ploop - anyone using in production yet? [message #45951 is a reply to message #45856] |
Fri, 20 April 2012 01:01  |
VDSExtreme
Messages: 11
Registered: February 2012
Location: The Netherlands
|
Junior Member |
|
|
Some customers of us which are using their servers for testing purposes to bug-track our platforms, are pretty excited.
The only thing what needs to be fixed is the problems in backing up the containers. Please DON'T use VZDump to backup a ploop file system. This can cause a high unavailability of your containers.
As we can see the testing results, we have to do a lot to get everything better in combination of backups, snapshots and either control panels.
Kind regards,
VDS Extreme - Technical Department
|
|
|
|
| Re: Ploop - anyone using in production yet? [message #46122 is a reply to message #45857] |
Thu, 26 April 2012 16:44 |
|
|
Rene,
For simfs, diskspace parameter is basically a quota limit for given CT. For ploop, diskspace becomes the size of ploop device, and thus it can't be set arbitrarily high.
So, before trying to convert, set diskspace to some sensible value, for example
vzctl set 5000 --diskspace 10G --save
or smth. Then convert.
I have modified vzctl to check for too high value of diskspace and emit an error if it is the case.
Kir Kolyshkin
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
