Ploop/Getting started - Revision history

Sergey Bronnikov: Marked this version for translation

2015-12-25T22:30:49Z

Marked this version for translation

Sergey Bronnikov: add 'translate' tags

2015-12-25T22:30:24Z

add 'translate' tags

178.172.239.243: /* Requirements */

2015-10-23T14:08:32Z

‎Requirements

Unixservice: /* Converting an existing CT */ added section about removing old container files that are not needed anymore

2015-05-17T16:48:01Z

‎Converting an existing CT: added section about removing old container files that are not needed anymore

Kir: /* Converting an existing CT */ fix reference to diskinodes

2014-11-24T18:51:36Z

‎Converting an existing CT: fix reference to diskinodes

Kir: minor formatting fixes

2014-11-11T03:46:07Z

minor formatting fixes

Kir: add --diskinodes for vzctl create

2014-11-11T03:43:08Z

add --diskinodes for vzctl create

Kir: more info and links to diskinodes

2014-11-11T03:41:29Z

Kir: /* Converting an existing CT */ add rm DISKINODES

2014-11-11T02:30:19Z

‎Converting an existing CT: add rm DISKINODES

Corradofiore: /* Requirements */

2014-09-20T14:31:46Z

‎Requirements

@@ Line 1: / Line 1: @@
 <translate>
 This article describes how to use container-in-a-file technology aka [[ploop]]
-== Requirements ==
+== Requirements == <!--T:2-->
 The following is required for ploop to work:
 # [[Download/kernel/rhel6|RHEL6-based OpenVZ kernel]], i.e. 042stabXXX.
 # <code>/vz</code> partition formatted as <code>ext4</code> and mounted in ordered mode, or residing on NFSv3. No other filesystem is supported.
 # ploop library and tools installed (run <code>yum install ploop</code>).
-== Making a CT on ploop ==
+== Making a CT on ploop == <!--T:5-->
-=== Global configuration ===
+=== Global configuration === <!--T:6-->
 In global VZ configuration file [[Man/vz.conf.5|/etc/vz/vz.conf]], set
-  VE_LAYOUT=ploop
+  <!--T:8-->
 This means that all new containers you will create will have ploop layout by default.
 You don't have to set this option if you don't want ploop to be default. Alternatively, you can:
 * use <code>--layout</code> option of <code>vzctl create</code> command;
 * convert existing container to ploop.
-=== Creating a new CT ===
+=== Creating a new CT === <!--T:12-->
 To create a new container on ploop, use:
-  vzctl create ''CTID'' [--layout ploop] [--diskspace ''nnn''G] [--diskinodes ''mmm'']
+  <!--T:14-->
 # You can omit <code>--layout</code> option if you have set <code>VE_LAYOUT=ploop</code> in {{Man|vz.conf|5}}
 # You can specify initial file system size using <code>--diskspace</code> option (example: 10G for 10 gigabytes)
@@ Line 36: / Line 47: @@
 # If <code>--diskinodes</code> is not specified, 1 inode per 16K of disk space will be created (see [[../diskinodes/]] for more info)
-=== Converting an existing CT ===
+=== Converting an existing CT === <!--T:16-->
 . Stop the container:
   vzctl stop ''CTID''
 . Set some sane diskspace value, and reset the [[../diskinodes/]] value. New value for diskspace will be used as a size of newly created ploop image. Here is the example to set diskspace to 10 gigabytes:
   vzctl set ''CTID'' --diskspace 10G --diskinodes 0 --save
 . Convert:
   vzctl convert ''CTID''
 . Once your CT is well tested, you can free disk space by removing files that may have remained from the old container file system in /vz/root/''CTID''. VERY CAREFULLY (and after testing your converted container) you can stop, remove old files and start container again, e.g.:
   vzctl stop ''CTID''
@@ Line 52: / Line 67: @@
   vzctl start ''CTID''
-== Resizing a ploop image ==
+== Resizing a ploop image == <!--T:21-->
 Ploop image can be resized in both directions (i.e. either shrank or grown). Ploop also supports online/live resize so you don't have to stop a CT to do resize.
 To resize a ploop CT image, use
-  vzctl set ''CTID'' --diskspace ''nnn''G --save
+  <!--T:24-->
 Note that
 * resize can safely be performed online (i.e. when container is running)
@@ Line 65: / Line 84: @@
 * there is no way to limit or change the number of inodes available for an existing container (i.e. option <code>--diskinodes</code> is ignored); see [[../diskinodes/]] for more details
-== Showing disk space usage / limits ==
+== Showing disk space usage / limits == <!--T:26-->
 You can use {{Man|vzlist|8}} to see CT disk space usage and limits in a uniform way for any containers (simfs or ploop, started or stopped).
 The field '''diskspace''' is showing the current disk space usage, and the fields '''diskspace.s''' and '''diskspace.h''' are showing the filesystem size (or disk space quotas, for simfs case).
 The field '''diskinodes''' is showing the current inodes usage, and the fields '''diskinodes.s''' and '''diskinodes.h''' are showing the filesystem size (or disk inodes quotas, for simfs case).
 Examples:
-  vzlist -o smart_name,diskspace.h,diskspace
+  <!--T:31-->
   vzlist -o smart_name,diskinodes.h,diskinodes
 On a lower level, same info can be obtained via '''ploop info''' command:
-  ploop info /vz/private/501/root.hdd/DiskDescriptor.xml
+  <!--T:33-->
-== Using disk quotas inside container ==
+== Using disk quotas inside container == <!--T:34-->
 If you want to use standard Linux per-user and per-group disk quota inside a container, you have to enable it using
-  vzctl set ''CTID'' --quotaugidlimit 1000 --save
+  <!--T:36-->
 Note that:
 * unlike with simfs, <code>--quotaugidlimit</code> argument can be any non-zero value;
 * enabling or disabling in-container disk quotas requires a container restart, so you might find <code>--setmode</code> option helpful.
 See {{Man|vzctl|8}} for more details.
-== See also ==
+== See also == <!--T:39-->
 * [[Ploop]]
 * [[Ploop/backup]]

@@ Line 1: / Line 1: @@
 This article describes how to use container-in-a-file technology aka [[ploop]]
@@ Line 100: / Line 101: @@
 * {{Man|vz.conf|5}}
 * {{Man|vzctl|8}}
 [[Category: Storage]]
 [[Category: HOWTO]]

@@ Line 6: / Line 6: @@
 # [[Download/kernel/rhel6|RHEL6-based OpenVZ kernel]], i.e. 042stabXXX.
-# <code>/vz</code> partition formatted as <code>ext4</code> and mounted in ordered mode, or residing on NFS. No other filesystem is supported.
+# <code>/vz</code> partition formatted as <code>ext4</code> and mounted in ordered mode, or residing on NFSv3. No other filesystem is supported.
 # ploop library and tools installed (run <code>yum install ploop</code>).

@@ Line 45: / Line 45: @@
 . Convert:
   vzctl convert ''CTID''
 == Resizing a ploop image ==

@@ Line 40: / Line 40: @@
   vzctl stop ''CTID''
-. Set some sane diskspace value, and reset the [[../diskinodes/] value. New value for diskspace will be used as a size of newly created ploop image. Here is the example to set diskspace to 10 gigabytes:
+. Set some sane diskspace value, and reset the [[../diskinodes/]] value. New value for diskspace will be used as a size of newly created ploop image. Here is the example to set diskspace to 10 gigabytes:
   vzctl set ''CTID'' --diskspace 10G --diskinodes 0 --save

@@ Line 39: / Line 39: @@
   vzctl set ''CTID'' --diskspace 10G --save
-. Convert:
+. Comment out <code>DISKINODES</code> setting from CT config (see [[../diskinodes/]] for more info):
-  vzctl convert ''CTID''
+ sed -i.bak 's/^DISKINODES=/#DISKINODES=/g' /etc/vz/conf/''CTID''.conf
 == Resizing a ploop image ==