https://wiki.openvz.org/api.php?action=feedcontributions&user=Kir&feedformat=atomOpenVZ Virtuozzo Containers Wiki - User contributions [en]2024-03-28T08:39:11ZUser contributionsMediaWiki 1.31.1https://wiki.openvz.org/index.php?title=Ploop/sparse&diff=23389Ploop/sparse2021-03-10T15:27:15Z<p>Kir: rm translate tags</p>
<hr />
<div>'''Sparse file''' is a file that contains blocks of zeroes that are not allocated on disk (see [[w:Sparse file]]). By design, ploop images can't contain such non-allocated blocks.<br />
<br />
While ploop is never creating sparse image files, they can be accidentally made so when tools such as <code>rsync --sparse</code> or <code>cp --sparse=always</code> are used to copy images. So, one should not use backup or copy tools that create sparse files out of non-sparse ones.<br />
<br />
== Kernel warning ==<br />
<br />
In case sparse file is detected by the kernel, it gives a warning in dmesg, for example:<br />
<br />
Nov 21 20:37:27 sun kernel: [43451.057489] ploop(24002): a hole in image file detected (0)<br />
<br />
In case there are no other ploop-related warnings or errors immediately after, this one is harmless ({{B|2825}}).<br />
<br />
== Userspace warnings ==<br />
<br />
You might see something like this (reported by ploop library) during container start or mount:<br />
<br />
Error in check_and_repair_sparse (check.c:542): Delta file /vz/private/1407/root.hdd/root.hdd contains uninitialized blocks (offset=135573536768 len=1323008) which are not aligned to cluster size<br />
Error in fill_hole (check.c:456): Warning: ploop image '/vz/private/1407/root.hdd/root.hdd' is sparse<br />
Reallocating sparse blocks back<br />
<br />
The last line tells that ploop library is going to fix the problem.<br />
<br />
== How to fix ==<br />
<br />
Since [[Download/ploop/1.10|ploop-1.10]], ploop images are checked for being sparse and are automatically fixed on mount, in case DiskDescriptor.xml is used. Otherwise, you can use <code>ploop check --repair-sparse</code> to check for and repair such images.<br />
<br />
Alternatively, you can just do something like this to get rid of holes. Make sure ploop file is not used!<br />
<br />
cat root.hdd > root.hdd2 && mv root.hdd2 root.hdd<br />
<br />
== See also ==<br />
<br />
<br />
* [[Ploop]]<br />
* [[w:Sparse file]]<br />
<br />
[[Category: Storage]]<br />
[[Category: Troubleshooting]]</div>Kirhttps://wiki.openvz.org/index.php?title=Ploop/Mount_helpers&diff=23388Ploop/Mount helpers2021-03-10T15:25:02Z<p>Kir: rm translate tags</p>
<hr />
<div>Despite the fact that ploop is not a file system, a trick exist<br />
to make it look and feel like so — i.e. to use usual <code>mount</code><br />
and <code>umount</code> commands rather than the {{Man|ploop|8}} tool.<br />
This article describes how it works and can be used.<br />
<br />
== Introduction ==<br />
<br />
ploop is not a filesystem per se, but a kernel [[w:loop device]] driver, providing a way<br />
to represent a ploop image (or a set of stacked images) as a<br />
[[w:Device file system#Block_devices|block device]].<br />
On top of that block device provided by ploop, an ext4 file system<br />
is created and used, for example, for storing files of a specific<br />
container.<br />
<br />
Therefore a complete ploop mount consists of two steps:<br />
# "mount" ploop image(s) to create a ploop device (/dev/ploopNNNNN)<br />
# mount a filesystem residing on this ploop device to a mount point<br />
<br />
For simplicity, these two are usually wrapped to be done together in one step (say when you use ploop mount with -m option).<br />
In reality, step 1 is kernel assembling a device out of image(s), and step 2 is the real mount.<br />
<br />
== Mounting ==<br />
<br />
You can use the following syntax to mount a ploop device and the filesystem inside it:<br />
<br />
mount -t ploop [option ...] /path/to/DiskDescriptor.xml /mount/point<br />
<br />
The following options are supported:<br />
<br />
<code>-r</code>, <code>-o ro</code><br />
: mount read-only<br />
<br />
<code>-v</code>, <code>--verbose</code><br />
: be more verbose<br />
<br />
<code>-f</code>, <code>--fake</code><br />
: do everything except for the actual mount<br />
<br />
<code>-n</code>, <code>--no-mtab</code>, <code>-s</code><br />
: these options are deliberately ignored<br />
<br />
== Unmounting ==<br />
<br />
To unmount, DiskDescriptor can be specified:<br />
<br />
umount /path/to/DiskDescriptor.xml<br />
<br />
A mount point can be used as well:<br />
<br />
umount /mount/point<br />
<br />
== Limitations ==<br />
<br />
Note that umount can only work if:<br />
# /etc/mtab is a separate file (not a symlink to /proc/mounts);<br />
# mounting was done using <code>mount</code> (not <code>ploop mount</code>).<br />
<br />
Otherwise, umount binary will not be able to find <code>ploop</code> as the "filesystem"<br />
field in /etc/mtab, and will not call <code>umount.ploop</code> helper. As a result,<br />
file system will be unmounted, but ploop device itself will stay mounted.<br />
<br />
== Alternative ==<br />
<br />
<code>ploop mount</code> and <code>ploop umount</code> commands,<br />
as described in {{Man|ploop|8}} man page.<br />
<br />
== See also ==<br />
<br />
* [[Ploop]]<br />
* {{Bug|2817}}<br />
<br />
[[Category: Storage]]</div>Kirhttps://wiki.openvz.org/index.php?title=Ploop&diff=23387Ploop2021-03-10T15:20:49Z<p>Kir: rm translate tags</p>
<hr />
<div>== Description ==<br />
<br />
Ploop is a disk loopback block device, similar to loop but with many features like dynamic resize, snapshots, backups etc. The main idea is to put container filesystem in a file.<br />
<br />
== Project resources ==<br />
<br />
The source code is [https://src.openvz.org/projects/OVZ/repos/ploop/browse on Stash] and [https://github.com/OpenVZ/ploop mirror] on GitHub.<br />
<br />
To participate in development of ploop please subscribe to the mailing list:<br />
[https://lists.openvz.org/mailman/listinfo/devel List info] | [https://lists.openvz.org/pipermail/devel List archives] | [mailto:devel-join@openvz.org Subscribe] | [mailto:devel-leave@openvz.org Unsubscribe]<br />
<br />
== See also ==<br />
<br />
* [[/Why/]] ploop is good for you<br />
* [[/Getting started/]] with ploop<br />
* [[/Limits/]] of ploop, space-wise<br />
* Ploop and [[/diskinodes/]]<br />
* [[/Backup/]] with ploop<br />
* {{pdf|Ct in a file.pdf}} Container in a file presentation<br />
* [[/readme/|README]] Low-level commands for advanced users only<br />
* ploop and [[/sparse/]] images<br />
* [[/Mount helpers/]] to use standard <code>mount</code>/<code>umount</code> commands<br />
* {{Man|ploop|8}} man page<br />
<br />
Articles about ploop in [http://openvz.livejournal.com openvz blog]:<br />
* [http://openvz.livejournal.com/40830.html Introducing container in a file aka ploop]<br />
* [http://openvz.livejournal.com/41835.html Effective live migration with ploop write tracker]<br />
* [http://openvz.livejournal.com/44508.html Ploop snapshots and backups]<br />
* [http://openvz.livejournal.com/47780.html Ploop and live migration: 2 years later]<br />
<br />
Source code and packages downloads:<br />
* [[Packages|Packages in Linux distributions]]<br />
* [[Download/ploop]]<br />
* [https://src.openvz.org/projects/OVZ/repos/ploop/browse ploop userspace git repo]<br />
* ploop [[packages]] in various Linux distributions.<br />
<br />
[[Category: Sub-projects]]<br />
[[Category: Storage]]</div>Kirhttps://wiki.openvz.org/index.php?title=Ploop/readme&diff=23386Ploop/readme2021-03-10T15:19:46Z<p>Kir: fixed some typos</p>
<hr />
<div>This document explains how to use user-space <code>ploop</code> utility for typical<br />
use-cases.<br />
<br />
{{Warning|The commands below are low-level stuff. It's better to use vzctl which has all the features in place.}}<br />
<br />
== Getting help ==<br />
<br />
All user-space ploop management operations are available via "<code>ploop</code>"<br />
utility. Run it w/o args to get help:<br />
<br />
# ploop<br />
<br />
Run with a cmd as the only arg to get cmd-specific help, e.g.:<br />
<br />
# ploop init<br />
<br />
== Load modules ==<br />
<br />
<br />
Further ploop commands assume that all necessary modules are loaded:<br />
<br />
# modprobe ploop<br />
# modprobe pfmt_ploop1<br />
# modprobe pfmt_raw<br />
# modprobe pio_direct<br />
<br />
<br />
It's not always required to load both <code>pfmt_ploop1</code> (support of ploop1 format) and<br />
<code>pfmt_raw</code> (support of raw format). If we're going to use ploop1 image file,<br />
loading <code>pfmt_raw</code> can be omitted. If we're going to use raw image file and have no<br />
plans to snapshot it, <code>pfmt_ploop1</code> can be omitted.<br />
<br />
== Initialize image file ==<br />
<br />
<br />
In-kernel ploop operates on image files of "<code>raw</code>" or "<code>ploop1</code>" format.<br />
An image file should be created and initialized (entirely in user-space)<br />
before asking in-kernel ploop to start using it.<br />
<br />
To just create and initialize a ploop image file with a GPT partition table and an ext4 filesystem inside:<br />
<br />
# ploop init -s 1g -t ext4 /ploop.image<br />
<br />
where <code>/ploop.image</code> is full path to new image file and 1g is block-device size<br />
equal to 1GB. This command succeed only if the file <code>/ploop.image</code> didn't<br />
exist at the time of running "<code>ploop init</code>".<br />
<br />
== Mount ==<br />
<br />
Assuming that previous steps were done, the following command is used to "mount"<br />
ploop device over image file.<br />
<br />
# ploop mount /ploop.image<br />
<br />
Since this point, <code>/dev/ploopXXXX</code> is operable. One can read/write any data from/to<br />
it (e.g. with "dd"), manipulate partition table on it (with <code>parted</code>, since ploop uses GUID Partition Table, or GPT), format it with <code>mkfs.ext4</code> and mount it on some mount-point. In the other words, since<br />
now <code>/dev/ploop0</code> can be used as any other ordinary block device.<br />
<br />
== Snapshot ==<br />
<br />
Let <code>/dev/ploop0</code> be a ploop device running over <code>/ploop.image</code> (i.e. step 5 was<br />
done) and <code>/ploop-delta.image</code> - some full path to non-existent file. Then the<br />
command:<br />
<br />
# ploop snapshot -d /dev/ploop0 /ploop-delta.image<br />
<br />
will create empty "ploop1" image file and register it in kernel ploop<br />
forming "snapshotted" configuration <code>top_delta → base_delta</code> where <code>base_delta</code><br />
is <code>/ploop.image</code> and <code>top_delta</code> is <code>/ploop-delta.image</code>.<br />
<br />
Since now, all i/o targeted at <code>/dev/ploop0</code> will change only <code>top_delta</code>.<br />
Actually, while performing snapshot operation in kernel, ploop re-open<br />
<code>base_delta</code> read-only. So, when "<code>ploop snapshot</code>" is completed, it's quite safe,<br />
for example, to backup <code>base_delta</code>.<br />
<br />
It's allowable to snapshot snapshotted configuration. Following example above,<br />
the command:<br />
<br />
# ploop snapshot -d /dev/ploop0 /ploop-delta1.image<br />
<br />
will form <code>top_delta → delta → base_delta</code> configuration where:<br />
<br />
top_delta := /ploop-delta1.image<br />
delta := /ploop-delta.image<br />
base_delta := /ploop.image.<br />
<br />
All deltas in snapshotted configuration are enumerated in kernel ploop in<br />
the natural order starting from 0 for <code>base_delta</code>:<br />
<br />
base_delta' number is 0<br />
delta' number is 1<br />
top_delta' number is 2.<br />
<br />
This knowledge is useful for online merge below.<br />
<br />
== Merge ==<br />
<br />
Merge operation implies copying all new data from an upper delta to a lower<br />
delta. In simplest case of delta2-->delta1 configuration, merge will copy<br />
new data from delta2 to delta1. In case of deltaN-->...-->delta1 configuration.<br />
merge will copy new data from <deltaN, ..., delta2> to delta1.<br />
<br />
There are two types of merge: offline and online. "offline" means that we have<br />
a bunch of stand-alone image files w/o kernel ploop running over them.<br />
"online" means that we have kernel ploop running over them. It's OK to perform<br />
online merge concurrently with other i/o activity (i.e. no need to stop ploop<br />
device or freeze upper-layer apps).<br />
<br />
=== Offline merge ===<br />
<br />
ploop has no heuristic about determining raw/ploop1 format of image file. So,<br />
in case of offline merge, user should specify the format of base_delta<br />
explicitly. If it's ploop1, merge command looks like:<br />
<br />
# ploop merge /ploop-delta.image /ploop.image<br />
<br />
This will merge /ploop-delta.image into /ploop.image. More than one source<br />
delta can be specified:<br />
<br />
# ploop merge /ploop-d2.image /ploop-d1.image /ploop-d.image /ploop.image<br />
<br />
<br />
This will merge /ploop-d2.image, /ploop-d1.image and /ploop-d.image into<br />
/ploop.image.<br />
<br />
<br />
When merge completed, source deltas can be deleted because all data that<br />
was present in them has been copied to destination delta.<br />
<br />
<br />
For raw format, "-f raw" should be added as option. E.g.:<br />
<br />
# ploop merge -f raw /ploop-d1.image /ploop.image<br />
<br />
=== Online merge ===<br />
<br />
In this case user should only specify ploop device and a range of deltas in the<br />
form of LEVEL1..LEVEL2 where LEVEL1 and LEVEL2 should be non-negative integers<br />
corresponding to in-kernel delta enumeration (see the end of 5th section above)<br />
and LEVEL1 must be lesser than LEVEL2. When merge completed, source deltas are<br />
deregistered from kernel ploop and can be deleted by user.<br />
<br />
Let's consider simple snapshotted configuration as example:<br />
<br />
# ploop mount -f ploop1 -d /dev/ploop0 /ploop.image<br />
# ploop snapshot -d /dev/ploop0 /ploop-delta.image<br />
# ploop snapshot -d /dev/ploop0 /ploop-delta1.image<br />
<br />
In this configuration the command:<br />
<br />
# ploop merge -d /dev/ploop0 -l 0..2<br />
<br />
will merge /ploop-delta1.image and /ploop-delta.image into /ploop.image. Here<br />
/ploop-delta1.image and /ploop-delta.image are source deltas and can be<br />
deleted.<br />
<br />
Alternatively, the command:<br />
<br />
# ploop merge -d /dev/ploop0 -l 0..1<br />
<br />
will merge /ploop-delta.image into /ploop.image. Here /ploop-delta.image is<br />
source delta and can be deleted.<br />
<br />
The last example is:<br />
<br />
# ploop merge -d /dev/ploop0 -l 1..2<br />
<br />
It will merge /ploop-delta1.image into /ploop-delta.image. Here<br />
/ploop-delta1.image is source delta and can be deleted.<br />
<br />
== Migration support ==<br />
<br />
Assuming that /dev/ploop0 is ploop device running over /ploop.image,<br />
/ploop1.image is the path to non-existent file and external_stop is some<br />
executable script or binary, the following command:<br />
<br />
# ploop copy -s /dev/ploop0 -d /ploop1.image -F external_stop<br />
<br />
will copy /home/ploop.image to /home/ploop1.image iteratively. external_stop<br />
should be an utility that completely freeze all i/o targeted at ploop device.<br />
For instance, container freeze.<br />
<br />
From user view, the command above should be equivalent to "external_stop;<br />
cp /home/ploop.image /home/ploop1.image". The benefit of "ploop copy" is<br />
minimizing duration of freezed state: it will try to copy the most part<br />
of data before calling external_stop and only some (hopefully small)<br />
amount of data after external_stop.<br />
<br />
It's also possible to split copy operation in two nodes:<br />
<br />
node01# ploop copy -d /ploop1.image<br />
node02# ploop copy -s /dev/ploop0 -F external_stop<br />
<br />
In this case "ploop copy" on node02 will write data to standard output<br />
in some special binary format and "ploop copy" on node01 will read data<br />
from standard input, parse that special format and store data in<br />
/home/ploop1.image ("-s" stands for "source", "-d" stands for "destination").<br />
This should work if standard output of node02 and standard input of node01<br />
are bound via pipe or socket connection.<br />
<br />
== Grow ploop device ==<br />
<br />
"ploop grow" command is to extend image file as necessary (offline or online)<br />
and propagate new block-device size to linux kernel (in online case).<br />
<br />
=== Offline grow ===<br />
<br />
To grow image file offline, user should specify its format explicitly. The<br />
default is "ploop1" format:<br />
<br />
# ploop grow -s 32g /ploop.image<br />
<br />
will re-arrange "ploop1" image file /ploop.image to become 32GB size long.<br />
<br />
For "raw" format, the command:<br />
<br />
# ploop grow -s 32g -f raw /ploop.image<br />
<br />
will do the same.<br />
<br />
=== Online grow ===<br />
<br />
Assuming that /dev/ploop0 is running ploop device, the command:<br />
<br />
# ploop grow -s 32g -d /dev/ploop0<br />
<br />
will re-arrange underlying image file, update internal kernel ploop structures<br />
and propagate changes to linux kernel making ploop device 32GB size long.<br />
<br />
If user had ext4 formatted and mounted on /dev/ploop0, ext4 fs can be extended<br />
online (when "ploop grow" completed):<br />
<br />
# resize2fs /dev/ploop0 32g<br />
<br />
== Ballooning ==<br />
<br />
ploop doesn't support pure shrinking block-device size due to lack of online<br />
shrink support in ext4. As a workaround, "ballooning" technique is proposed.<br />
Ballooning operation consists of inflating special balloon file in user-space<br />
(the file will be invisible for ordinary users, e.g. inside container),<br />
loading fiemap info of inflated balloon to kernel, relocating blocks of<br />
image file from the tail to the space specified by fiemap info and truncating<br />
tail of image file.<br />
<br />
Desired outcome is image file of smaller size. However, it's quite possible<br />
that inflated balloon file will span only blocks that were never touched<br />
before. They will look as "not allocated" space from kernel ploop view. In this<br />
case nothing will be relocated and nothing truncated.<br />
<br />
So, if balloon operation succeeded, it's only guaranteed that user of ploop<br />
device won't be able to consume more space than initial block device size<br />
minus size of inflated balloon. On the other hand, if user of block device<br />
used a lot of space on it, then freed significant part of used space,<br />
balloon operation will result in significant truncate of image file.<br />
<br />
To enable ballooning, ext4 residing on ploop device should be mounted<br />
with special "balloon_ino" option:<br />
<br />
# mount -t ext4 -o balloon_ino=12 /dev/ploop0 /mnt_ploop<br />
<br />
where 12 is inode number of balloon file as reported by "ls -i".<br />
(it's assumed that initially, e.g. while constructing container,<br />
someone mounted ext4 on ploop device w/o balloon_ino option, then created<br />
empty balloon file there, found out its inode number and saved it for the<br />
future use).<br />
<br />
Currently, only online ballooning is supported. The following command performs<br />
this operation:<br />
<br />
# ploop balloon change -s 1g -d /dev/ploop0 -m /mnt_ploop<br />
<br />
where 1g is desired new size of balloon file, /dev/ploop0 is ploop block<br />
device, /mnt_ploop is mount-point where ext4 residing on /dev/ploop0 is<br />
mounted to.<br />
<br />
If balloon file was empty, the command above simply inflates it to become<br />
1GB size. If it was non-empty but smaller than 1GB, that command extends it<br />
to given size (1GB). If it was non-empty but larger that 1GB, that<br />
command truncates it down to given size. If it was exactly 1GB size, the<br />
command does nothing.<br />
<br />
Along with "change" sub-command, "ploop balloon" supports a few auxiliary ones:<br />
<br />
# ploop balloon show -m /mnt_ploop<br />
<br />
will show current ploop balloon size.<br />
<br />
# ploop balloon status -d /dev/ploop0 -m /mnt_ploop<br />
<br />
will report current in-kernel status of maintenance like "merge in progress",<br />
"grow in progress", "ballooning started", etc. This is useful because on the<br />
one hand balloon operation can't be performed while merge or grow is in<br />
progress, and on the other hand previous "ploop balloon" could be killed by<br />
someone before its completion.<br />
<br />
# ploop balloon clear -d /dev/ploop0 -m /mnt_ploop<br />
<br />
will flush stale in-kernel "BALLOON" state of maintenance. This is useful if<br />
previous "ploop balloon" died early leaving in-kernel ploop locked.<br />
<br />
# ploop balloon complete -d /dev/ploop0 -m /mnt_ploop<br />
<br />
will complete previously interrupted balloon operation. An expectation is that<br />
user monitors exit status of ploop commands he/she runs in some way. If<br />
user issued "ploop balloon change" and it was killed in the middle, the user<br />
knows that it didn't complete with zero exit status. Then user should inquire<br />
current maintenance state with "ploop balloon status" command, and, if it<br />
reported "FBLOAD" or "RELOC", the user should use "ploop balloon complete"<br />
before proceeding with any other maintenance operations (snapshot, merge,<br />
grow, balloon).<br />
<br />
# ploop balloon check -d /dev/ploop0 -m /mnt_ploop<br />
<br />
will check whether existent balloon file was properly processed. This is useful<br />
if previous "ploop balloon" was interrupted, but "ploop balloon status"<br />
reports "OFF" or "BALLOON" maintenance state. In this case it's possible<br />
that balloon file was inflated but no further processing happened.<br />
<br />
"ploop balloon check" reports total number of free blocks in existent balloon<br />
file. If it's not zero, the user should use the following command to repair<br />
balloon:<br />
<br />
# ploop balloon repair -d /dev/ploop0 -m /mnt_ploop<br />
<br />
This command does essentially the same as "ploop balloon change" but w/o<br />
inflating balloon.<br />
<br />
== See also ==<br />
<br />
* [[Ploop]]<br />
* {{Man|ploop|8}}<br />
<br />
[[Category: Storage]]</div>Kirhttps://wiki.openvz.org/index.php?title=Ploop/readme&diff=23385Ploop/readme2021-03-10T15:17:59Z<p>Kir: rm translate tags</p>
<hr />
<div>This document explains how to use user-space <code>ploop</code> utility for typical<br />
use-cases.<br />
<br />
{{Warning|The commands below are low-level stuff. It's better to use vzctl which has all the features in place.}}<br />
<br />
== Getting help ==<br />
<br />
All user-space ploop management operations are available via "<code>ploop</code>"<br />
utility. Run it w/o args to get help:<br />
<br />
# ploop<br />
<br />
Run with a cmd as the only arg to get cmd-specific help, e.g.:<br />
<br />
# ploop init<br />
<br />
== Load modules ==<br />
<br />
<br />
Further ploop commands assume that all necessary modules are loaded:<br />
<br />
# modprobe ploop<br />
# modprobe pfmt_ploop1<br />
# modprobe pfmt_raw<br />
# modprobe pio_direct<br />
<br />
<br />
It's not always required to load both <code>pfmt_ploop1</code> (support of ploop1 format) and<br />
<code>pfmt_raw</code> (support of raw format). If we're going to use ploop1 image file,<br />
loading <code>pfmt_raw</code> can be omitted. If we're going to use raw image file and have no<br />
plans to snapshot it, <code>pfmt_ploop1</code> can be omitted.<br />
<br />
== Initialize image file ==<br />
<br />
<br />
In-kernel ploop operates on image files of "<code>raw</code>" or "<code>ploop1</code>" format.<br />
An image file should be created and initialized (entirely in user-space)<br />
before asking in-kernel ploop to start using it.<br />
<br />
To just create and initialize a ploop image file with a GPT partition table and an ext4 filesystem inside:<br />
<br />
# ploop init -s 1g -t ext4 /ploop.image<br />
<br />
where <code>/ploop.image</code> is full path to new image file and 1g is block-device size<br />
equal to 1GB. This command succeed only if the file <code>/ploop.image</code> didn't<br />
exist at the time of running "<code>ploop init</code>".<br />
<br />
== Mount ==<br />
<br />
Assuming that previous steps were done, the following command is used to "mount"<br />
ploop device over image file.<br />
<br />
# ploop mount /ploop.image<br />
<br />
Since this point, <code>/dev/ploopXXXX</code> is operable. One can read/write any data from/to<br />
it (e.g. with "dd"), manipulate partition table on it (with <code>parted</code>, since ploop uses GUID Partition Table, or GPT), format it with <code>mkfs.ext4</code> and mount it on some mount-point. In the other words, since<br />
now <code>/dev/ploop0</code> can be used as any other ordinary block device.<br />
<br />
== Snapshot ==<br />
<br />
Let <code>/dev/ploop0</code> be a ploop device running over <code>/ploop.image</code> (i.e. step 5 was<br />
done) and <code>/ploop-delta.image</code> - some full path to non-existent file. Then the<br />
command:<br />
<br />
# ploop snapshot -d /dev/ploop0 /ploop-delta.image<br />
<br />
will create empty "ploop1" image file and register it in kernel ploop<br />
forming "snapshotted" configuration <code>top_delta → base_delta</code> where <code>base_delta</code><br />
is <code>/ploop.image</code> and <code>top_delta</code> is <code>/ploop-delta.image</code>.<br />
<br />
Since now, all i/o targeted at <code>/dev/ploop0</code> will change only <code>top_delta</code>.<br />
Actually, while performing snapshot operation in kernel, ploop re-open<br />
<code>base_delta</code> read-only. So, when "<code>ploop snapshot</code>" is completed, it's quite safe,<br />
for example, to backup <code>base_delta</code>.<br />
<br />
It's allowable to snapshot snapshotted configuration. Following example above,<br />
the command:<br />
<br />
# ploop snapshot -d /dev/ploop0 /ploop-delta1.image<br />
<br />
will form <code>top_delta → delta → base_delta</code> configuration where:<br />
<br />
top_delta := /ploop-delta1.image<br />
delta := /ploop-delta.image<br />
base_delta := /ploop.image.<br />
<br />
All deltas in snapshotted configuration are enumerated in kernel ploop in<br />
the natural order starting from 0 for <code>base_delta</code>:<br />
<br />
base_delta' number is 0<br />
delta' number is 1<br />
top_delta' number is 2.<br />
<br />
This knowledge is useful for online merge below.<br />
<br />
== Merge ==<br />
<br />
Merge operation implies copying all new data from an upper delta to a lower<br />
delta. In simplest case of delta2-->delta1 configuration, merge will copy<br />
new data from delta2 to delta1. In case of deltaN-->...-->delta1 configuration.<br />
merge will copy new data from <deltaN, ..., delta2> to delta1.<br />
<br />
There are two types of merge: offline and online. "offline" means that we have<br />
a bunch of stand-alone image files w/o kernel ploop running over them.<br />
"online" means that we have kernel ploop running over them. It's OK to perform<br />
online merge concurrently with other i/o activity (i.e. no need to stop ploop<br />
device or freeze upper-layer apps).<br />
<br />
=== Offline merge ===<br />
<br />
ploop has no heruistic about determining raw/ploop1 format of image file. So,<br />
in case of offline merge, user should specify the format of base_delta<br />
explicitly. If it's ploop1, merge command looks like:<br />
<br />
# ploop merge /ploop-delta.image /ploop.image<br />
<br />
This will merge /ploop-delta.image into /ploop.image. More than one source<br />
delta can be specified:<br />
<br />
# ploop merge /ploop-d2.image /ploop-d1.image /ploop-d.image /ploop.image<br />
<br />
<br />
This will merge /ploop-d2.image, /ploop-d1.image and /ploop-d.image into<br />
/ploop.image.<br />
<br />
<br />
When merge completed, source deltas can be deleted because all data that<br />
was present in them has been copied to destination delta.<br />
<br />
<br />
For raw format, "-f raw" should be added as option. E.g.:<br />
<br />
# ploop merge -f raw /ploop-d1.image /ploop.image<br />
<br />
=== Online merge ===<br />
<br />
In this case user should only specify ploop device and a range of deltas in the<br />
form of LEVEL1..LEVEL2 where LEVEL1 and LEVEL2 should be non-negative integers<br />
corresponding to in-kernel delta enumeration (see the end of 5th section above)<br />
and LEVEL1 must be lesser than LEVEL2. When merge completed, source deltas are<br />
deregistered from kernel ploop and can be deleted by user.<br />
<br />
Let's consider simple snapshotted configuration as example:<br />
<br />
# ploop mount -f ploop1 -d /dev/ploop0 /ploop.image<br />
# ploop snapshot -d /dev/ploop0 /ploop-delta.image<br />
# ploop snapshot -d /dev/ploop0 /ploop-delta1.image<br />
<br />
In this configuration the command:<br />
<br />
# ploop merge -d /dev/ploop0 -l 0..2<br />
<br />
will merge /ploop-delta1.image and /ploop-delta.image into /ploop.image. Here<br />
/ploop-delta1.image and /ploop-delta.image are source deltas and can be<br />
deleted.<br />
<br />
Alternatively, the command:<br />
<br />
# ploop merge -d /dev/ploop0 -l 0..1<br />
<br />
will merge /ploop-delta.image into /ploop.image. Here /ploop-delta.image is<br />
source delta and can be deleted.<br />
<br />
The last example is:<br />
<br />
# ploop merge -d /dev/ploop0 -l 1..2<br />
<br />
It will merge /ploop-delta1.image into /ploop-delta.image. Here<br />
/ploop-delta1.image is source delta and can be deleted.<br />
<br />
== Migration support ==<br />
<br />
Assuming that /dev/ploop0 is ploop device running over /ploop.image,<br />
/ploop1.image is the path to non-existent file and external_stop is some<br />
executable script or binary, the following command:<br />
<br />
# ploop copy -s /dev/ploop0 -d /ploop1.image -F external_stop<br />
<br />
will copy /home/ploop.image to /home/ploop1.image iteratively. external_stop<br />
should be an utility that completely freeze all i/o targeted at ploop device.<br />
For instance, container freeze.<br />
<br />
From user view, the command above should be equivalent to "external_stop;<br />
cp /home/ploop.image /home/ploop1.image". The benefit of "ploop copy" is<br />
minimizing duration of freezed state: it will try to copy the most part<br />
of data before calling external_stop and only some (hopefully small)<br />
amount of data after external_stop.<br />
<br />
It's also possible to split copy operation in two nodes:<br />
<br />
node01# ploop copy -d /ploop1.image<br />
node02# ploop copy -s /dev/ploop0 -F external_stop<br />
<br />
In this case "ploop copy" on node02 will write data to standard output<br />
in some special binary format and "ploop copy" on node01 will read data<br />
from standard input, parse that special format and store data in<br />
/home/ploop1.image ("-s" stands for "source", "-d" stands for "destination").<br />
This should work if standard output of node02 and standard input of node01<br />
are bound via pipe or socket connection.<br />
<br />
== Grow ploop device ==<br />
<br />
"ploop grow" command is to extend image file as necessary (offline or online)<br />
and propagate new block-device size to linux kernel (in online case).<br />
<br />
=== Offline grow ===<br />
<br />
To grow image file offline, user should specify its format explicitly. The<br />
default is "ploop1" format:<br />
<br />
# ploop grow -s 32g /ploop.image<br />
<br />
will re-arrange "ploop1" image file /ploop.image to become 32GB size long.<br />
<br />
For "raw" format, the command:<br />
<br />
# ploop grow -s 32g -f raw /ploop.image<br />
<br />
will do the same.<br />
<br />
=== Online grow ===<br />
<br />
Assuming that /dev/ploop0 is runnung ploop device, the command:<br />
<br />
# ploop grow -s 32g -d /dev/ploop0<br />
<br />
will re-arrange underlying image file, update internal kernel ploop structures<br />
and propagate changes to linux kernel making ploop device 32GB size long.<br />
<br />
If user had ext4 formatted and mounted on /dev/ploop0, ext4 fs can be extended<br />
online (when "ploop grow" completed):<br />
<br />
# resize2fs /dev/ploop0 32g<br />
<br />
== Ballooning ==<br />
<br />
ploop doesn't support pure shrinking block-device size due to lack of online<br />
shrink support in ext4. As a workaround, "ballooning" technique is proposed.<br />
Ballooning operation consists of inflating special balloon file in user-space<br />
(the file will be invisible for ordinary users, e.g. inside container),<br />
loading fiemap info of inflated balloon to kernel, relocating blocks of<br />
image file from the tail to the space specified by fiemap info and truncating<br />
tail of image file.<br />
<br />
Desired outcome is image file of smaller size. However, it's quite possible<br />
that inflated balloon file will span only blocks that were never touched<br />
before. They will look as "not allocated" space from kernel ploop view. In this<br />
case nothing will be relocated and nothing truncated.<br />
<br />
So, if balloon operation succeeded, it's only guaranteed that user of ploop<br />
device won't be able to consume more space than initial block device size<br />
minus size of inflated balloon. On the other hand, if user of block device<br />
used a lot of space on it, then freed significant part of used space,<br />
balloon operation will result in significant truncate of image file.<br />
<br />
To enable ballooning, ext4 residing on ploop device should be mounted<br />
with special "balloon_ino" option:<br />
<br />
# mount -t ext4 -o balloon_ino=12 /dev/ploop0 /mnt_ploop<br />
<br />
where 12 is inode number of balloon file as reported by "ls -i".<br />
(it's assumed that initially, e.g. while constructing container,<br />
someone mounted ext4 on ploop device w/o balloon_ino option, then created<br />
empty balloon file there, found out its inode number and saved it for the<br />
future use).<br />
<br />
Currently, only online ballooning is supported. The following command performs<br />
this operation:<br />
<br />
# ploop balloon change -s 1g -d /dev/ploop0 -m /mnt_ploop<br />
<br />
where 1g is desired new size of balloon file, /dev/ploop0 is ploop block<br />
device, /mnt_ploop is mount-point where ext4 residing on /dev/ploop0 is<br />
mounted to.<br />
<br />
If balloon file was empty, the command above simply inflates it to become<br />
1GB size. If it was non-empty but smaller than 1GB, that command extends it<br />
to given size (1GB). If it was non-empty but larger that 1GB, that<br />
command truncates it down to given size. If it was exactly 1GB size, the<br />
command does nothing.<br />
<br />
Along with "change" sub-command, "ploop balloon" supports a few auxiliary ones:<br />
<br />
# ploop balloon show -m /mnt_ploop<br />
<br />
will show current ploop balloon size.<br />
<br />
# ploop balloon status -d /dev/ploop0 -m /mnt_ploop<br />
<br />
will report current in-kernel status of maintenance like "merge in progress",<br />
"grow in progress", "ballooning started", etc. This is useful because on the<br />
one hand balloon operation can't be performed while merge or grow is in<br />
progress, and on the other hand previous "ploop balloon" could be killed by<br />
someone before its completion.<br />
<br />
# ploop balloon clear -d /dev/ploop0 -m /mnt_ploop<br />
<br />
will flush stale in-kernel "BALLOON" state of maintenance. This is useful if<br />
previous "ploop balloon" died early leaving in-kernel ploop locked.<br />
<br />
# ploop balloon complete -d /dev/ploop0 -m /mnt_ploop<br />
<br />
will complete previously interrupted balloon operation. An expectation is that<br />
user monitors exit status of ploop commands he/she runs in some way. If<br />
user issued "ploop balloon change" and it was killed in the middle, the user<br />
knows that it didn't complete with zero exit status. Then user should inquire<br />
current maintenance state with "ploop balloon status" command, and, if it<br />
reported "FBLOAD" or "RELOC", the user should use "ploop balloon complete"<br />
before proceeding with any other maintenance operations (snapshot, merge,<br />
grow, balloon).<br />
<br />
# ploop balloon check -d /dev/ploop0 -m /mnt_ploop<br />
<br />
will check whether existent balloon file was properly processed. This is useful<br />
if previous "ploop balloon" was interrupted, but "ploop balloon status"<br />
reports "OFF" or "BALLOON" maintenance state. In this case it's possible<br />
that balloon file was inflated but no further processing happened.<br />
<br />
"ploop balloon check" reports total number of free blocks in existent balloon<br />
file. If it's not zero, the user should use the following command to repair<br />
balloon:<br />
<br />
# ploop balloon repair -d /dev/ploop0 -m /mnt_ploop<br />
<br />
This command does essentially the same as "ploop balloon change" but w/o<br />
inflating balloon.<br />
<br />
== See also ==<br />
<br />
* [[Ploop]]<br />
* {{Man|ploop|8}}<br />
<br />
[[Category: Storage]]</div>Kirhttps://wiki.openvz.org/index.php?title=Ploop/diskinodes&diff=23384Ploop/diskinodes2021-03-10T15:03:21Z<p>Kir: removed translate tags</p>
<hr />
<div>Everything you wanted to know about DISKINODES for ploop but were afraid to ask.<br />
<br />
== Limitations ==<br />
<br />
With simfs layout, vzquota is used to set limits for DISKSPACE and<br />
DISKINODES, so these limits can be changed any time.<br />
<br />
Unlike simfs, ploop contains a real file system, so amount of disk space<br />
and disk inodes are properties of the file system, determined while<br />
creating a filesystem. It is possible to resize an ext4 file system<br />
in terms of disk space, but there's no way to change the number of available<br />
inodes.<br />
<br />
{{Note|There is no way to change DISKINODES for existing ploop. This is a limitation of ext4.}}<br />
<br />
In other words, <code>vzctl set --diskinodes</code> is ignored for ploop layout -- it can only be specified on create.<br />
<br />
== Default value ==<br />
<br />
By default, ext4 allocates 1 (one) inode per each 16 KB of data; this is<br />
practically the same as to assume that the average file size will be 16KB.<br />
<br />
For example, when creating a ploop with 40GB of disk space, 2621440 inodes<br />
will be available:<br />
<br />
<math>\frac{40 * 1024 * 1024}{16} = 2621440</math><br />
<br />
== Increasing ==<br />
<br />
If the above default is too low for your usage (for example, a container<br />
has or will have too many small files), you can specify a larger value<br />
for DISKINODES '''during container creation or conversion only'''.<br />
<br />
{{Note|The feature works since vzctl 4.7.}}<br />
<br />
{{Note|You can only specify <code>--diskinodes</code> for <code>vzctl create</code> or <code>vzctl convert</code>.}}<br />
<br />
The way it works is the following. First, a file system big enough<br />
to accommodate the requested number of DISKINODES is created, and then<br />
ploop resize is performed to downsize the file system to meet the<br />
requested amount of DISKSPACE.<br />
<br />
Example:<br />
<br />
vzctl create 123 --diskspace 40G --diskinodes 5242880<br />
<br />
<br />
Here, a filesystem big enough to have 5242880 of diskinodes<br />
will be created (it's 5242880 * 16K = 80G), then downsized to 40G.<br />
<br />
== Issues ==<br />
<br />
=== Too high DISKINODES value ===<br />
<br />
Sometimes, when the amount of DISKINODES specified is too high,<br />
a very large filesystem is created, and it can not be downsized<br />
to a specified amount. In this case, the following error will be<br />
shown when converting a container from simfs to ploop:<br />
<br />
vzctl set ''CTID'' --diskspace 40G --diskinodes 1000000000 --save<br />
...<br />
vzctl convert ''CTID''<br />
...<br />
Error in ploop_resize_image (ploop.c:2477): Unable to change image size to 83877888 sectors, minimal size is 502423144<br />
Unmounting file system at /vz/private/101.ploop/root.hdd/root.hdd.mnt<br />
Unmounting device /dev/ploop37776<br />
Failed to resize image: Error in ploop_resize_image (ploop.c:2477): Unable to change image size to 83877888 sectors, minimal size is 502423144 [38]<br />
<br />
In this case, 1G inodes requirement leads to creation of 16TB filesystem<br />
(remember, 1 inode per 16K). Unfortunately, such huge FS can't be downsized<br />
to as low as 40G, the minimum seems to be around 240G (values printed in<br />
the error message are in sectors which are 512 bytes each).<br />
<br />
'''Solution 1''': please be reasonable when requesting diskinodes for ploop. <br />
<br />
'''Solution 2''': please set DISKINODES to 0 before conversion:<br />
<br />
vzctl stop ''CTID''<br />
vzctl set ''CTID'' --diskspace ''xxx''G --diskinodes 0 --save<br />
vzctl convert ''CTID''<br />
<br />
This will lead to creating a filesystem with default number of inodes.<br />
<br />
=== Too low DISKINODES value ===<br />
<br />
If DISKINODES specified during <code>create</code> or <code>convert</code> is<br />
lower than the default (1 inode per 16K of disk space), it is silently ignored.<br />
In other words, there is no way to limit DISKINODES to lower than DISKSPACE / 16384.<br />
<br />
== See also ==<br />
* {{git commit|vzctl|ef320d32a4}}<br />
* https://lists.openvz.org/pipermail/users/2014-October/005913.html<br />
<br />
[[Category: Storage]]</div>Kirhttps://wiki.openvz.org/index.php?title=Ploop/diskinodes&diff=23383Ploop/diskinodes2021-03-10T14:57:55Z<p>Kir: </p>
<hr />
<div><translate><br />
<!--T:1--><br />
Everything you wanted to know about DISKINODES for ploop but were afraid to ask.<br />
<br />
== Limitations == <!--T:2--><br />
<br />
<!--T:3--><br />
With simfs layout, vzquota is used to set limits for DISKSPACE and<br />
DISKINODES, so these limits can be changed any time.<br />
<br />
<!--T:4--><br />
Unlike simfs, ploop contains a real file system, so amount of disk space<br />
and disk inodes are properties of the file system, determined while<br />
creating a filesystem. It is possible to resize an ext4 file system<br />
in terms of disk space, but there's no way to change the number of available<br />
inodes.<br />
<br />
<!--T:5--><br />
{{Note|There is no way to change DISKINODES for existing ploop. This is a limitation of ext4.}}<br />
<br />
<!--T:6--><br />
In other words, <code>vzctl set --diskinodes</code> is ignored for ploop layout -- it can only be specified on create.<br />
<br />
== Default value == <!--T:7--><br />
<br />
<!--T:8--><br />
By default, ext4 allocates 1 (one) inode per each 16 KB of data; this is<br />
practically the same as to assume that the average file size will be 16KB.<br />
<br />
<!--T:9--><br />
For example, when creating a ploop with 40GB of disk space, 2621440 inodes<br />
will be available:<br />
<br />
<!--T:10--><br />
<math>\frac{40 * 1024 * 1024}{16} = 2621440</math><br />
<br />
== Increasing == <!--T:11--><br />
<br />
<!--T:12--><br />
If the above default is too low for your usage (for example, a container<br />
has or will have too many small files), you can specify a larger value<br />
for DISKINODES '''during container creation or conversion only'''.<br />
<br />
<!--T:13--><br />
{{Note|The feature works since vzctl 4.7.}}<br />
<br />
<!--T:14--><br />
{{Note|You can only specify <code>--diskinodes</code> for <code>vzctl create</code> or <code>vzctl convert</code>.}}<br />
<br />
<!--T:15--><br />
The way it works is the following. First, a file system big enough<br />
to accommodate the requested number of DISKINODES is created, and then<br />
ploop resize is performed to downsize the file system to meet the<br />
requested amount of DISKSPACE.<br />
<br />
<!--T:16--><br />
Example:<br />
<br />
<!--T:17--><br />
vzctl create 123 --diskspace 40G --diskinodes 5242880<br />
<br />
<!--T:18--><br />
Here, a filesystem big enough to have 5242880 of diskinodes<br />
will be created (it's 5242880 * 16K = 80G), then downsized to 40G.<br />
<br />
== Issues == <!--T:19--><br />
<br />
=== Too high DISKINODES value === <!--T:20--><br />
<br />
<!--T:21--><br />
Sometimes, when the amount of DISKINODES specified is too high,<br />
a very large filesystem is created, and it can not be downsized<br />
to a specified amount. In this case, the following error will be<br />
shown when converting a container from simfs to ploop:<br />
<br />
<!--T:22--><br />
vzctl set ''CTID'' --diskspace 40G --diskinodes 1000000000 --save<br />
...<br />
vzctl convert ''CTID''<br />
...<br />
Error in ploop_resize_image (ploop.c:2477): Unable to change image size to 83877888 sectors, minimal size is 502423144<br />
Unmounting file system at /vz/private/101.ploop/root.hdd/root.hdd.mnt<br />
Unmounting device /dev/ploop37776<br />
Failed to resize image: Error in ploop_resize_image (ploop.c:2477): Unable to change image size to 83877888 sectors, minimal size is 502423144 [38]<br />
<br />
<!--T:23--><br />
In this case, 1G inodes requirement leads to creation of 16TB filesystem<br />
(remember, 1 inode per 16K). Unfortunately, such huge FS can't be downsized<br />
to as low as 40G, the minimum seems to be around 240G (values printed in<br />
the error message are in sectors which are 512 bytes each).<br />
<br />
<!--T:24--><br />
'''Solution 1''': please be reasonable when requesting diskinodes for ploop. <br />
<br />
<!--T:25--><br />
'''Solution 2''': please set DISKINODES to 0 before conversion:<br />
<br />
<!--T:26--><br />
vzctl stop ''CTID''<br />
vzctl set ''CTID'' --diskspace ''xxx''G --diskinodes 0 --save<br />
vzctl convert ''CTID''<br />
<br />
<!--T:27--><br />
This will lead to creating a filesystem with default number of inodes.<br />
<br />
=== Too low DISKINODES value === <!--T:28--><br />
<br />
<!--T:29--><br />
If DISKINODES specified during <code>create</code> or <code>convert</code> is<br />
lower than the default (1 inode per 16K of disk space), it is silently ignored.<br />
In other words, there is no way to limit DISKINODES to lower than DISKSPACE / 16384.<br />
<br />
== See also == <!--T:30--><br />
* {{git commit|vzctl|ef320d32a4}}<br />
* https://lists.openvz.org/pipermail/users/2014-October/005913.html<br />
</translate><br />
<br />
[[Category: Storage]]</div>Kirhttps://wiki.openvz.org/index.php?title=Package_managers&diff=23377Package managers2021-02-02T22:39:36Z<p>Kir: nit: it's -> its</p>
<hr />
<div>With OpenVZ, you can run many different Linux distributions on a single box. One particular thing in which distributions differ is package management. This article summarizes how to perform various common package management tasks on a different distributions.<br />
<br />
== Commands ==<br />
{| class="wikitable"<br />
! align="center" | Action<br />
! RPM<br/><small>RHEL, Fedora, CentOS, Mandriva, SUSE, ...</small><br />
! DEB<br/><small>Debian, Knoppix, Ubuntu, ...</small><br />
! Ebuild<br/><small>Gentoo and derivatives (Sabayon, Ututo, ...)</small><br />
! Pacman<br/><small>Arch Linux</small><br />
|-<br />
! colspan="5" align="center" | <big>'''Basic queries'''</big><br />
|-<br />
! List of all installed packages<br />
|| <code>rpm -qa</code><br />
|| <code>dpkg -l</code><br />
|| <code>equery list '*'</code><br />
|| <code>pacman -Q</code><br />
|-<br />
! List of installed packages matching ''substr''<br />
|| <code>rpm -qa ''\*substr\*''</code><br />
|| <code>dpkg -l ''\*substr\*''</code><br />
|| <code>equery list ''substr''</code><br />
|| <code>pacman -Q | grep ''substr''</code><br />
|-<br />
! Basic information about an installed ''package''<br />
|| <code>rpm -qi ''package''</code><br />
|| <code>dpkg -s ''package''</code><br />
|| <code>eix ''package''</code><br />
|| <code>pacman -Qi ''package''</code><br />
|-<br />
! List of files in a given ''package''<br />
|| <code>rpm -ql ''package''</code><br />
|| <code>dpkg -L ''package''</code><br />
|| <code>equery files ''package''</code><br />
|| <code>pacman -Ql ''package''</code><br />
|-<br />
! colspan="5" align="center" | <big>'''Advanced queries'''</big><br />
|-<br />
! Which package a ''file'' belongs to?<br />
|| <code>rpm -qf ''file''</code><br />
|| <code>dpkg -S ''file''</code><br />
|| <code>equery belongs ''file''</code><br />
|| <code>pacman -Qo ''file''</code><br />
|-<br />
! Check the hash (i.e. MD5 etc.) sums of an installed package<br />
|| <code>rpm -V ''package''</code><br />
|| <code>debsums -ca ''package''</code><br />
|| <code>equery check ''package''</code><br />
||<br />
|-<br />
! Show pre/post install/uninstall scripts from a ''package''<br />
|| <code>rpm -q --scripts ''package''</code><br />
|| <code>less /var/lib/dpkg/info/''package''.{pre,post,config}*</code><br />
|| <code>cat `equery which ''package''`</code><br />
||<br />
|-<br />
! Show change log for a ''package''<br />
|| <code>rpm -q --changelog ''package''</code><br />
|| <code>zcat /usr/share/doc/''package''/changelog.Debian.gz</code><br/><code>aptitude [-t release] changelog ''package''</code><br />
|| <code>view /usr/portage/''category''/''package''/ChangeLog</code><br />
|| <code>pacman -Qc ''package''</code><br />
|-<br />
! colspan="5" align="center" | <big>'''Local package installation/upgrade/removal'''</big><br />
|-<br />
! Install a package from local ''package_file''<br />
|| <code>rpm -ihv ''package_file*.rpm''<br/>yum localinstall ''package_file*.rpm''<ref name="localinstall">In case there are unsatisfied dependencies for ''package_file'', yum will try to get and install it from known repositores.</ref></code><br />
|| <code>dpkg -i ''package_file*.deb'' <ref name="apt">Usually it is not necessary to download packages manually and install them. Use apt-cache search ''name'' to search for package in configured repositories and apt-get install ''package'' to install package and all its dependencies</ref></code><br />
|| <code>emerge --usepkg|-k ''package''<ref name="emerge-usepkg">Use a binary package if it is available from $PKGDIR, otherwise emerge from source as usual.</ref></code><br/><code>emerge --usepkgonly|-K ''package''<ref name="emerge-usepkgonly">Use a binary package if it is available from $PKGDIR, otherwise abort.</ref></code><br />
|| <code>pacman -U ''package''</code><br />
|-<br />
! Upgrade a package from local ''package_file''<br />
|| <code>rpm -Uhv ''package_file*.rpm''</code><br />
|| <code>dpkg -i ''package_file*.deb'' <ref name="apt"/></code><br />
|| <code>emerge --update --usepkg|-k ''package''<ref name="emerge-usepkg"/></code><br/><br />
<code>emerge --update --usepkgonly|-K ''package''<ref name="emerge-usepkgonly"/></code><br />
|| <code>pacman -U ''package''</code><br />
|-<br />
! Remove an installed ''package''<br />
|| <code>rpm -e ''package''</code><br/><br />
<code>yum remove|erase ''package''<ref name="yum-remove">This will also remove any packages which depend on the ''package''</ref></code><br />
|| <code>dpkg -r ''package''</code><br/><br />
<code>dpkg -P ''package''</code><br />
|| <code>emerge --unmerge ''package''</code><br/><br />
<code>emerge --prune ''package''</code><br />
|| <code>pacman -R ''package''</code><br />
|-<br />
! colspan="5" align="center" | <big>'''Package installation from repositories'''</big><br />
|-<br />
! Install a ''package''<br />
|| <code>yum install ''package''</code><br/><br />
<code>urpmi ''package''</code><br />
|| <code>apt-get update && apt-get install ''package''</code><br/><br />
<code>aptitude update && aptitude install ''package''</code><br />
|| <code>emerge -av ''package''</code><br />
|| <code>pacman -S ''package''</code><br />
|-<br />
! Install a debug information files for a ''package''<br />
|| <code>debuginfo-install ''package''</code><br />
|| <br />
|| <code>FEATURES="splitdebug installsources" emerge -av ''package''</code><br />
||<br />
|-<br />
! Only download a ''package'' from repository, do not install<br />
|| First install the yum-downloadonly plugin by running: <br/><code>yum install yum-downloadonly</code><br/> And then: <br/> <code>yum install|update ''package'' -y --downloadonly --downloaddir=/opt</code><br />
|| <code>apt-get install --download-only --reinstall ''package''</code><ref name="dpkgdir">Package will reside in /var/cache/apt/archives.</ref><br/><code>aptitude download ''package''</code><br />
|| <code>emerge -avf ''package''</code><ref name="distfiles">Package sources will reside in /usr/portage/distfiles.</ref><br />
|| <code>pacman -Sw ''package''</code><br />
|-<br />
! colspan="5" align="center" | <big>'''Get information about package interdependencies'''</big><br />
|-<br />
! What a given ''package'' provides?<br />
|| <code>rpm -q --provides ''package''</code><br />
|| <code>dpkg-query -W -f='${Provides}\n' ''package''</code><br />
|| <code>equery files ''package'' (package must be installed first)</code><br />
|| <code>pacman -Ql ''package'' (package must be installed first)</code><br />
|-<br />
! What a given ''package'' requires?<br />
|| <code>rpm -q --requires ''package''</code><br />
|| <code>dpkg-query -W -f='${Depends}\n' ''package''</code><br />
|| <code>equery depgraph --depth=1 ''package''</code><br />
|| <code>pacman -Si ''package''</code><br />
|-<br />
! Which installed package(s) provide a given ''dependency''<ref name="dep">In rpm world, a ''dependency'' can be a package name, a file, or a special atom like <code>perl(IO::Zlib)</code> for a perl module. In deb world, this can be either real or virtual package name.</ref>?<br />
|| <code>rpm -q --whatprovides ''dependency''</code><br />
|| <code>dpkg-query -W -f='${Package}: ${Provides}\n' '*' | grep ': .*''dependency''<nowiki>'</nowiki></code><br />
|| <code>equery belongs ''dependency''</code><br />
||<br />
|-<br />
! Which installed package(s) require a given ''dependency''<ref name="dep"/>?<br />
|| <code>rpm -q --whatrequires ''dependency''</code><br />
|| <code>dpkg-query -W -f='${Package}: ${Depends}\n' '*' | grep ': .*''package''<nowiki>'</nowiki></code><br><code>aptitude why ''package''</code><ref name="why">Actualy shows the whole dpendency situation that leads to install this package</ref><br />
|| <code>equery depends ''package''</code><br />
|| <code>pacman -Qi ''package'' | grep Required</code><br />
||<br />
|-<br />
! Show what prevents installation of a package<br />
|| <code>(yum/rpm tells with --verbose option -v)</code><br />
|| <code>aptitude why-not ''package''</code><br />
|| <code>emerge -pv ''package''</code><br />
||<br />
|-<br />
! Get package source files<br />
|| <code>yumdownloader --source ''package''</code><br />
|| <code>apt-get source ''package''</code><br />
|| <code>emerge -f ''package''</code><br />
|| <code>abs ''repository''/''package''</code><br />
|-<br />
! colspan="5" align="center" | <big>'''Working with package files'''</big><br />
|-<br />
! Unpack a package ''file'' to local directory<br />
|| <code>rpm2cpio ''file.rpm'' | cpio -id</code><br />
|| <code>dpkg -x / --extract ''file.deb'' .</code><br />
|| N/A<br />
|| <code>tar -xzf ''package''</code> if ''package''.pkg.tar.gz or<br/><code>tar -xJf ''package''</code> if ''package''.pkg.tar.xz<br />
|-<br />
! Check package file integrity (checksums, signatures...)<br />
|| <code>rpm -K ''file.rpm''</code><br/>(yum/rpm also checks GPG-signature and checksums automatically every time the package is installed or upgraded)<br />
|| <code>debsums ''package''</code><br />
|| <code>emerge -f ''package''</code><br />
||<br />
|-<br />
! Show package metadata<br />
|| <code>rpm -qip ''file.rpm''</code><br />
|| <code>dpkg -I / --info ''file.deb''</code><br />
|| N/A<br />
|| ??<br />
|-<br />
! Show package file list<br />
|| <code>rpm -qlvp ''file.rpm''</code><br />
|| <code>dpkg -c / --contents ''file.deb''</code><br />
|| N/A<br />
|| ??<br />
|-<br />
! colspan="5" align="center" | <big>'''Repository queries'''</big><br />
|-<br />
! Find a package in a repository which <code>/some/file</code> belongs to<br />
|| <code>yum provides ''/some/file''</code><br />
|| First run: <br/><code>apt-file update</code><br/>and then:<br/><code>apt-file search ''/some/file''</code><br />
|| N/A<br />
||<br />
|-<br />
! Find a package based on some string or part of the string descriping it<br />
|| <code>yum search ''\*substr\*''</code><br />
|| <code>apt-cache search ''\*substr\*''</code><br />
|| <code>eix -S ''substr''</code><br />
|| <code>pacman -Ss ''substr''</code><br />
|-<br />
! Shows the full description of ''package''<br />
|| <code>yum info ''package''</code><br />
|| <code>apt-cache show ''package''</code><br />
|| <code>eix ''package''</code><br />
|| <code>pacman -Si ''package''</code><br />
|}<br />
<br />
== Relevant directories and files ==<br />
<br />
=== Red Hat, Fedora, CentOS ===<br />
<br />
* yum config: <code>/etc/yum.conf</code>.<br />
* yum repos: <code>/etc/yum.repos.d/</code>.<br />
* rpm configs and macros: <code>/etc/rpm/</code>, <code>/usr/lib/rpm/</code>, <br />
* rpm DB: <code>/var/lib/rpm/</code><br />
<br />
=== Debian/Ubuntu ===<br />
<br />
* List of repositories and mirror sites: <code>/etc/apt/sources.list</code>, <code>/etc/apt/sources.list.d/</code>.<br />
<br />
=== Gentoo ===<br />
<br />
* emerge configs: <code>/etc/make.conf</code>, <code>/etc/portage/</code>.<br />
* Portage tree: <code>/usr/portage</code>.<br />
* Binary packages (FEATURES="buildpkg" enabled in make.conf): <code>/usr/portage/packages</code>.<br />
* Default directory to download sources to: <code>/usr/portage/distfiles</code>.<br />
* Default Portage working directory: <code>/var/lib/portage/</code>.<br />
<br />
== Notes==<br />
<references/><br />
<br />
== See also ==<br />
=== Debian ===<br />
* [http://www.debian.org/doc/FAQ/ch-pkgtools.en.html Debian FAQ: package management tools]<br />
* [http://www.debian.org/doc/manuals/apt-howto/ APT HOWTO]<br />
<br />
[[Category: HOWTO]]<br />
[[Category: Templates]]<br />
[[Category: Debian]]<br />
[[Category: Ubuntu]]<br />
[[Category: Gentoo]]</div>Kirhttps://wiki.openvz.org/index.php?title=Download/kernel/rhel6/042stab134.7/changes&diff=23064Download/kernel/rhel6/042stab134.7/changes2018-12-17T21:49:56Z<p>Kir: use list</p>
<hr />
<div>== Changes ==<br />
Since {{kernel link|rhel6|042stab134.3}}:<br />
<br />
* Running Ubuntu containers with systemd 229-4ubuntu21.8 could result in application failures due to /run/lock/ permission issues. (PSBM-89993)<br />
* Running Ubuntu containers with systemd 229-4ubuntu21.9 could result in services failing to start because systemd-tmpfiles was unable to validate path due to symlinking issues. (PSBM-90038) <br />
* Host with multiple ploop devices running on a debug kernel could crash in sysfs_addrm_start() on container stop. (PSBM-89413)<br />
* Ploop resize could fail and lead to access beyond the end of device. (PSBM-89687)<br />
* Ploop over Virtuozzo Storage: in rare cases, resize could lead to ploop image corruption. (PSBM-89855)<br />
<br />
=== See also ===<br />
* https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804847</div>Kirhttps://wiki.openvz.org/index.php?title=Quick_installation_(legacy)&diff=23051Quick installation (legacy)2018-11-27T02:58:53Z<p>Kir: rm translate tags</p>
<hr />
<div>{{Warning|This article describes legacy version of OpenVZ. For current version, see [[Quick installation]].}}<br />
<br />
<!--T:1--><br />
This document briefly describes the steps needed to install '''legacy''' OpenVZ on your '''RHEL 6''' (CentOS 6, Scientific Linux 6) machine.<br />
<br />
<!--T:2--><br />
For '''Debian''' based systems, please see [[Installation on Debian]].<br />
<br />
<!--T:3--><br />
{{Out|A commercial version of OpenVZ is available, which simplifies installation with a single disk as well as supports networked installation using PXE boot. To learn more about Virtuozzo and request a free trial, please see https://virtuozzo.com/openvz/}}<br />
<br />
== Requirements == <!--T:5--><br />
<br />
<!--T:6--><br />
This guide assumes you are running '''RHEL (CentOS, Scientific Linux) 6''' on your system. Currently, this is a recommended platform to run OpenVZ on.<br />
<br />
=== /vz file system === <!--T:7--><br />
<br />
<!--T:8--><br />
It is recommended to use a separate partition for containers (by default '''/vz''') and format it to '''ext4'''.<br />
<br />
=== yum pre-setup === <!--T:9--><br />
<br />
<!--T:10--><br />
Download [https://download.openvz.org/openvz.repo openvz.repo] file and put it to your <code>/etc/yum.repos.d/</code> repository:<br />
<br />
<!--T:11--><br />
<pre><nowiki>wget -P /etc/yum.repos.d/ https://download.openvz.org/openvz.repo</nowiki></pre><br />
<br />
<!--T:12--><br />
Import OpenVZ GPG key used for signing RPM packages:<br />
<br />
<!--T:13--><br />
<pre><nowiki>rpm --import http://download.openvz.org/RPM-GPG-Key-OpenVZ</nowiki></pre><br />
<br />
To make sure that you are downloading tamper free versions of the signed packages you should verify the fingerprint of the key you imported into the rpm key database as described on the [[Package signatures]] page.<br />
<br />
== Kernel installation == <!--T:14--><br />
<br />
<!--T:15--><br />
Limited OpenVZ functionality is supported when you run a recent 3.x kernel (check [[vzctl for upstream kernel]], so OpenVZ kernel installation is optional but still recommended.<br />
<br />
<!--T:16--><br />
# yum install vzkernel<br />
<br />
== System configuration == <!--T:17--><br />
<br />
<!--T:18--><br />
{{Note|With vzctl 4.4 or newer there is no need to do manual configuration. Skip to [[#Tools_installation]].}}<br />
<br />
<!--T:19--><br />
Please make sure the following steps are performed before rebooting into OpenVZ kernel.<br />
<br />
=== sysctl === <!--T:20--><br />
<br />
<!--T:21--><br />
There are a number of kernel parameters that should be set for OpenVZ to work correctly. These parameters are stored in <tt>/etc/sysctl.conf</tt> file. Here are the relevant portions of the file; please edit accordingly.<br />
<br />
<!--T:22--><br />
<pre><br />
# On Hardware Node we generally need<br />
# packet forwarding enabled and proxy arp disabled<br />
net.ipv4.ip_forward = 1<br />
net.ipv6.conf.default.forwarding = 1<br />
net.ipv6.conf.all.forwarding = 1<br />
net.ipv4.conf.default.proxy_arp = 0<br />
<br />
<!--T:23--><br />
# Enables source route verification<br />
net.ipv4.conf.all.rp_filter = 1<br />
<br />
<!--T:24--><br />
# Enables the magic-sysrq key<br />
kernel.sysrq = 1<br />
<br />
<!--T:25--><br />
# We do not want all our interfaces to send redirects<br />
net.ipv4.conf.default.send_redirects = 1<br />
net.ipv4.conf.all.send_redirects = 0<br />
</pre><br />
<br />
=== SELinux === <!--T:26--><br />
<br />
<!--T:27--><br />
SELinux should be disabled. Put <code>SELINUX=disabled</code> to <code>/etc/sysconfig/selinux</code>:<br />
<br />
<!--T:28--><br />
echo "SELINUX=disabled" > /etc/sysconfig/selinux<br />
<br />
== Tools installation == <!--T:29--><br />
<br />
<!--T:30--><br />
{{Out|Before installing tools, please read about [[vzstats]] and opt-out if you don't want to help the project.}}<br />
<br />
<!--T:31--><br />
OpenVZ needs some user-level tools installed:<br />
<br />
<!--T:32--><br />
# yum install vzctl vzquota ploop<br />
<br />
== Reboot into OpenVZ == <!--T:33--><br />
<br />
<!--T:34--><br />
Now reboot the machine and choose "OpenVZ" on the boot loader menu (it should be default choice).<br />
<br />
== Download OS templates == <!--T:35--><br />
<br />
<!--T:36--><br />
An OS template is a Linux distribution installed into a container<br />
and then packed into a gzipped tarball. Using such a cache, a new container<br />
can be created in a minute.<br />
<br />
<!--T:37--><br />
Download precreated template caches from [http://openvz.org/download/template/cache Downloads » Templates » Precreated], or directly from [http://download.openvz.org/template/precreated/ download.openvz.org/template/precreated], or from one of the [[Download mirrors|mirrors]]. Put those tarballs '''as-is (no unpacking needed)''' to the <tt>/vz/template/cache/</tt> directory.<br />
<br />
== Next steps == <!--T:38--><br />
<br />
<!--T:39--><br />
OpenVZ is now set up on your machine. Follow on to [[basic operations in OpenVZ environment]] document.<br />
<br />
[[Category: Installation]]<br />
[[Category: HOWTO]]</div>Kirhttps://wiki.openvz.org/index.php?title=Setting_up_a_mirror/ru&diff=23050Setting up a mirror/ru2018-11-27T02:58:10Z<p>Kir: rm translate tags</p>
<hr />
<div>Если Вы хотите поднять свое OpenVZ зеркало, то эта инструкция для Вас.<br />
<br />
== Требования ==<br />
<br />
{{Warning|Пожалуйста, не делайте Ваше OpenVZ зеркало публичным если:<br />
* у Вас не достаточно ресурсов (места на диске, пропускной способности сети, навыков администрирования);<br />
* если Вы не собираетесь его поддерживать хотя бы год;<br />
* Если у Вас нет автоматического мониторинга и возможности быстро восстановить работу зеркала.}}<br />
<br />
<br />
* Зеркало должно быть доступно по HTTP или FTP. Лучше если будет доступ по обоим протоколам. В дополнение Вы можете предоставлять к нему доступ по rsync.<br />
<br />
* Ваш http/ftp сервер должен возвращать корректный статус для несуществующих файлов (HTTP 404, FTP 550)<br />
<br />
* Ваше зеркало должно регулярно обновляться. Рекомендованный интервал для обновления - один раз в час.<br />
<br />
* Ваше зеркало должно быть подключено к мониторингу<br />
* Файлы должны быть доступны по всем поддерживаемым протоколам<br />
<br />
<br />
Пожалуйста, не пробуйте сделать Ваше зеркало публичным, если оно не удовлетворяет всем вышеперечисленным требованиям.<br />
<br />
== Создание зеркала ==<br />
<br />
Для начального копирования зеркала запустите:<br />
<br />
* В США: <pre>rsync -av --delete rsync://download.openvz.org/openvz-download /local/path</pre><br />
* В Европе: <pre>rsync -av --delete rsync://eu.download.openvz.org/openvz-download /local/path</pre><br />
<br />
Следующий шаг - добавить cron задание для выполнение аналогичной rsync команды хотя бы раз в час.<br />
<br />
== Настройка доступа к Вашему зеркалу ==<br />
<br />
Когда Вы будете готовы открыть Ваше зеркало, настройте HTTP/FTP доступ к нему. Лучше, если зеркало будет доступно по ссылке вида <tt><nowiki>http://openvz.yoursite.com/</nowiki></tt> или <tt><nowiki>http://mirrors.yoursite.com/openvz/</nowiki></tt> (аналогично и с ftp).<br />
<br />
== Анонс Вашего зеркала ==<br />
<br />
Последний шаг - анонсировать Ваше зеркало. Это можно сделать двумя способами:<br />
<br />
* отправить pull request в [https://src.openvz.org/projects/OVZ/repos/openvz-mirrors/browse openvz-mirrors] репозиторий и добавить vvs@ как reviewer (предпочтительный вариант)<br />
* отправить запрос по электронной почте на [mailto:mirrors@openvz.org mirrors@openvz.org]<br />
<br />
Анонс должен содежрать следующую информацию (смотрите [https://src.openvz.org/projects/OVZ/repos/openvz-mirrors/commits/c85b848e76c35b216ef157cbc6d1eb823a596d7e как пример]):<br />
<br />
* '''Site:''' - адрес сайта. Пример: hosteurope.de.<br />
* Прямые ссылки на файлы Вашего OpenVZ зеркала (http, ftp, rsync). Пример:<br />
** OVZ-https: download.openvz.org/<br />
** OVZ-ftp: download.openvz.org/<br />
** OVZ-rsync: download.openvz.org/openvz-download/<br />
* '''Maintainer''' - email администратора зеркала (по которому его будут оповещать о проблемах). Будет лучше, если это будет общий адрес (как mirroradmin@ или иной), с которого стоит перенаправление на нескольких человек.<br />
* '''Country''' (код страны по ISO 3166-1, список кодов - [http://www.staff.science.uu.nl/~penni101/mirmon/svn/trunk/countries.list])<br />
* '''Location''' - физическое расположение Вашего зеркала. Пример: Sergiev Posad, Moscow region, Russia.<br />
* '''Sponsor''' - название Вашей огранизации<br />
* '''IPv6''' - поддерживает ли Ваше зеркало IPv6 (yes, no).<br />
* '''Comment''' - дополнительная информация, как пропускная способность канала, периодичность обновления и т.п. Пример: 1GB connection, updated hourly.<br />
* '''Master site''' - в данный момент есть два master зеркала: [https://download.openvz.org download.openvz.org] (USA) и [https://eu.download.openvz.org eu.download.openvz.org] (Switzerland, Europe). Пожалуйста, настройте зеркалирование с ближайшем из них и укажите его в этом поле.<br />
<br />
Пример информации о новом зеркале:<br />
<br />
Site: eu.download.openvz.org<br />
Type: Master<br />
OVZ-https: eu.download.openvz.org/<br />
OVZ-ftp: eu.download.openvz.org/<br />
OVZ-rsync: eu.download.openvz.org/openvz-download/<br />
Maintainer: Sergey Bronnikov <sergeyb@openvz.org><br />
Country: ch<br />
Location:<br />
Sponsor: Virtuozzo<br />
IPv6: yes<br />
Comment: Master site<br />
State: Enabled<br />
<br />
== Немного статистики ==<br />
<br />
Зеркало OpenVZ занимает порядка 103 Gb (по состоянию на август 2015), исходите из этого объема при планировании требований к серверу для создания зеркала. Объём данных растёт примерно на 1.5 GB в месяц.<br />
<br />
Объём трафика для download.openvz.org равен примерно 3-15Т в месяц, но для Вашего зеркала он будет скорее всего намного ниже.<br />
<br />
== Также смотрите ==<br />
<br />
* [http://mirrors.openvz.org/ Статус доступности зеркал OpenVZ]<br />
<br />
[[Category: HOWTO]]<br />
[[Category: Infrastructure]]</div>Kirhttps://wiki.openvz.org/index.php?title=Remote_console_setup&diff=23049Remote console setup2018-11-27T02:57:36Z<p>Kir: rm translate tags</p>
<hr />
<div>In case you are experiencing a kernel crash ([[oops]]) and have already [[Hardware testing|tested your hardware]], you should report what kernel says to the console (i.e. an [[oops]] text) to [https://bugs.openvz.org/ bug tracker]. Sometimes kernel crashes so badly that <tt>syslogd</tt> is not working and what kernel says is never written to a file. If this is the case, you have to catch what kernel says. There are several ways possible.<br />
<br />
== KDump ==<br />
<br />
With RHEL6-based servers, kdump is pre-configured. See http://kb.odin.com/en/10044 to check the configuration. Dumps can be found under <code>/var/crash/</code> directory.<br />
<br />
== Manual/Photo ==<br />
If kernel backtrace is not long enough there are chances that it can fit into a single screen. In that case, you can just make a photo of the kernel crash screen and attach it to the bug report. If you do not have a camera, you still can carefully write down (using a piece of paper and a pen, that is) what you see on the screen, and later type it into the bug report.<br />
<br />
== Serial console ==<br />
Here is a description of a common routine that is necessary to set up a serial console.<br />
<br />
=== Hardware setup ===<br />
First of all you should make sure that your node has a [[w:Serial port|serial port]]. If there is no such port then<br />
unfortunately this way is not for you.<br />
<br />
Then you need to find a second machine with a serial port on it.<br />
This machine will be used to collect logs from your primary machine. Further you need to acquire<br />
so-called [[w:Serial cable|null modem cable (a.k.a. serial cable)]] and it must be long enough to connect these two machines.<br />
<br />
=== Software setup ===<br />
<br />
==== Sending side ====<br />
In your boot loader add the following kernel parameters: <br />
<pre><br />
console=ttyS0,115200 console=tty0<br />
</pre><br />
<br />
<!--T:10--><br />
{{Warning|make sure kernel command line does '''not''' contain the word '''<code>quiet</code>''', otherwise most of the kernel messages will not be printed to console.}}<br />
<br />
<!--T:11--><br />
For example, in GRUB boot loader configuration file <tt>/boot/grub/grub.conf</tt> it looks like this:<br />
<pre><br />
title Fedora Core (2.6.16-026test014.1-smp)<br />
root (hd0,0)<br />
kernel /vmlinuz-2.6.16-026test014.1-smp ro root=LABEL=/ console=ttyS0,115200 console=tty debug silencelevel=8<br />
initrd /initrd-2.6.16-026test014.1-smp.img<br />
</pre><br />
<br />
Kernel loaded with such parameters will send all kernel messages to /dev/ttyS0 (first serial port, a.k.a. COM1). If you have several ports, make sure that your null modem cable is connected to the appropriate port.<br />
<br />
==== Receiving side ==== <!--T:13--><br />
On the second node you should run any software that can log from /dev/ttyS0.<br />
<br />
<!--T:14--><br />
It can be usual<br />
<pre><br />
cat /dev/ttyS0 > /var/log/serial.log &<br />
</pre><br />
or something more sophisticated: syslogd, watchtty etc.<br />
<br />
==== Port setup ====<br />
One more important thing. 115200 in the example above is the rate of emitting port. Receiving port must also work at the same rate. For example, to tune ttyS0 rate use stty program like this:<br />
<pre><br />
stty 115200 < /dev/ttyS0<br />
</pre><br />
<br />
Some other serial port parameters, like parity, number of stop bits etc. should also be the same on both sides.<br />
<br />
== Netconsole ==<br />
<br />
=== Kernel recompilation ===<br />
If you use binary kernel from openvz.org, it already has netconsole module compiled in, so just skip to next section.<br />
<br />
If you build the kernel yourself, you might need to check if netconsole is compiled. To that effect, change to your kernel source directory and grep your kernel <tt>.config</tt> for NETCONSOLE:<br />
<pre><br />
# cd /usr/src/openvz/linux-2.6.16<br />
# grep NETCONSOLE .config<br />
</pre><br />
<br />
If you see nothing or "# CONFIG_NETCONSOLE is not set" you need to recompile the kernel.<br />
<br />
Edit your kernel configuration file <tt>.config</tt> with a text editor (<tt>nano .config</tt> or <tt>vi .config</tt>). Set netconsole to Y or M (depending on whether you want it as a module or built into the kernel; I have compiled it as a module):<br />
<br />
<pre>CONFIG_NETCONSOLE=m</pre><br />
<br />
Save the file, then recompile the kernel:<br />
<br />
# make bzImage && make modules && make modules_install<br />
<br />
Update your bootloader for the new updated kernel. In my case I use LILO so I just type lilo at the prompt.<br />
<br />
Reboot into new kernel.<br />
<br />
=== Setting up OpenVZ side ===<br />
<br />
Next you want your netconsole to send the request to somewhere. Load netconsole module, specifying the remote server parameters:<br />
<br />
# modprobe netconsole netconsole=4444@10.0.2.1/eth0,6666@10.0.2.2/00:05:5D:34:11:AF<br />
<br />
This will load the module with your settings. Replace your local IP address with where <tt>10.0.2.1</tt> is, <tt>eth0</tt> with your network interface card device, <tt>6666</tt> with the remote netconsole port (UDP), and <tt>10.0.2.2</tt> with your remote netconsole server IP. Also add in the mac address of your remote netconsole server, which in my case was 00:05:5D:34:11:AF. You can get the MAC address using arp utility:<br />
<br />
<pre><br />
# ping -c 1 10.0.2.2<br />
# /sbin/arp -n 10.0.2.2<br />
Address HWtype HWaddress Flags Mask Iface<br />
10.0.2.2 ether 00:05:5D:34:11:AF C eth0<br />
</pre><br />
<br />
If the remote netconsole server is outside of local network area, use mac address of default gateway or router on local network area and IP address of remote netconsole server (loging via WAN). Mac address of default gateway or router you can get the same way (ping to gateway/router and see mac address via arp command).<br />
<br />
Netconsole documentation is available from <tt>Documentation/networking/netconsole.txt</tt> file under your kernel source directory.<br />
<br />
=== Setting from initrd ===<br />
<br />
To log the boot process before root filesystem is mounted, network device driver and netconsole modules must be loaded from initd.<br />
<br />
<br />
RedHat 5/CentOS 5:<br />
echo 'MODULES+="<network-driver-module> netconsole "' > /etc/sysconfig/mkinitrd/netconsole<br />
chmod +x /etc/sysconfig/mkinitrd/netconsole<br />
echo 'options netconsole netconsole=<sport>@<saddr>/<dev>,<dport>@<daddr>/<dmac>' >> /etc/modprobe.conf<br />
<br />
Debian/Ubuntu:<br />
echo '<network-driver-module>' >> /etc/initramfs-tools/modules<br />
echo 'netconsole netconsole=<sport>@<saddr>/<dev>,<dport>@<daddr>/<dmac>' >> /etc/initramfs-tools/modules<br />
<br />
and rebuild initrd.<br />
<br />
=== Setting up rsyslogd ===<br />
<br />
<br />
/etc/rsyslog.d/netconsole.conf<br />
<br />
$template NetconsoleFile,"/var/log/netconsole/%FROMHOST%-%$NOW%.log"<br />
$template NetconsoleFormat,"%rawmsg%"<br />
<br />
$EscapeControlCharactersOnReceive off<br />
$DropTrailingLFOnReception off<br />
$RepeatedMsgReduction off<br />
<br />
$RuleSet NetconsoleRuleset<br />
*.* ?NetconsoleFile;NetconsoleFormat<br />
$RuleSet RSYSLOG_DefaultRuleset<br />
<br />
$ModLoad imudp<br />
$InputUDPServerBindRuleset NetconsoleRuleset<br />
$UDPServerRun 6666<br />
<br />
=== Setting up remote side ===<br />
<br />
Set up '''netcat''' ('''nc''' on some Linux distributions) on your console server to listen on port 6666 UDP:<br />
<br />
netcat -u -l -p6666<br />
<br />
or<br />
<br />
nc -lu 6666<br />
<br />
or<br />
<br />
socat udp-listen:6666,reuseaddr -<br />
<br />
When your kernel prints something on the console, the text will be also captured on this netconsole server.<br />
<br />
==== Adding to inittab ====<br />
For automatic care about capturing on console server you can use init respawn feature in this way:<br />
<br />
echo "n1:23:respawn:/bin/netcat -u -l -p 6666 >> /var/log/netconsole" >> /etc/inittab<br />
telinit q<br />
<br />
==== Adding date/time to messages ====<br />
<br />
If you want the log to contain date/time of each line, you can use '''awk''' like this:<br />
<br />
netcat -u -l -p6666 | awk '{print strftime("%d %b %Y %H:%M:%S"), $0; fflush(stdout);}' >> /var/log/netconsole<br />
<br />
See man strftime for info about how to tailor strftime() argument to your needs.<br />
<br />
Note that if you want to add this to /etc/inittab, it should be done like this:<br />
<br />
echo "netcat -u -l -p6666 | awk '{print \<br />
strftime("%d %b %Y %H:%M:%S"), \$0; fflush(stdout);}' \<br />
>> /var/log/netconsole" > /usr/local/sbin/netconsole<br />
chmod a+x /usr/local/sbin/netconsole<br />
echo "n1:23:respawn:/usr/local/sbin/netconsole" >> /etc/inittab<br />
telinit q<br />
<br />
==== Configuring logrotate ====<br />
<br />
For long term capturing you would like to do log rotating some way. With logrotate you can do it by creating config file /etc/logrotate.d/netconsole:<br />
<br />
<pre><br />
/var/log/netconsole {<br />
weekly<br />
rotate 8<br />
missingok<br />
compress<br />
copytruncate<br />
notifempty<br />
# Need to restart logger after log file move<br />
postrotate<br />
# Below line assumes netcat will be restarted by init<br />
killall -TERM netcat > /dev/null 2>&1 || true<br />
}<br />
</pre><br />
<br />
<!--T:53--><br />
For more details, see man logrotate.<br />
<br />
=== Testing netconsole ===<br />
First, check log level of console messages on OpenVZ side by:<br />
<br />
cat /proc/sys/kernel/printk<br />
<br />
First number should be 7 for testing. You can arrange it by:<br />
<br />
sysctl -w kernel.printk="7 4 1 7"<br />
<br />
After testing you can restore previous setting the same way.<br />
<br />
Load '''netconsole''' module (see above) and on the console server run netcat (nc) command. On OpenVZ side provoke any console message, for example connect any USB hardware or try command:<br />
<br />
modprobe tun<br />
<br />
If you see any console message on OpenVZ side, you should see message on console server too. If not, something is wrong. When debugging a problem, do not use tcpdump on OpenVZ side — it is not able to show netconsole packets. Instead, use tcpdump on console server. Quite a common source of problems with netconsole are firewalls.<br />
<br />
== See also ==<br />
* [[SysRq debugger]]<br />
* [[Kernel debug options]]<br />
<br />
== External links ==<br />
* [http://kb.odin.com/en/10044 How to configure kdump (kernel crash dump)]<br />
<br />
[[Category:QA]]<br />
[[Category:HOWTO]]<br />
[[Category:Kernel]]<br />
[[Category:Troubleshooting]]</div>Kirhttps://wiki.openvz.org/index.php?title=Kernel_patches&diff=23048Kernel patches2018-11-27T02:51:07Z<p>Kir: rm translate tags</p>
<hr />
<div>{{Virtuozzo}}<br />
<br />
This document describes how to contribute your patches to the OpenVZ kernel. In a nutshell, the process is similar to the one for the upstream kernel — we use git for source control and a mailing list for communication.<br />
<br />
== Source code ==<br />
<br />
Kernel source code is available from git repository at https://src.openvz.org/projects/OVZ/repos/vzkernel/browse<br />
<br />
To clone, use<br />
<br />
git clone https://src.openvz.org/scm/ovz/vzkernel.git<br />
<br />
== Editing ==<br />
<br />
As with the upstream kernel, modifications to the code should conform to the [https://www.kernel.org/doc/Documentation/CodingStyle Linux kernel coding style].<br />
<br />
== Preparing patches ==<br />
<br />
Use <code>git format-patch</code> to prepare your patches. See git documentation for more info.<br />
<br />
=== Checkpatch ===<br />
<br />
There is a tool (scripts/checkpatch.pl) that '''should''' be used to check your patches. Use<br />
<br />
./scripts/checkpatch.pl *.patch<br />
<br />
It will produce a detailed report on style problems in your patch(es). Make sure to fix all the errors (some warnings may be ignored) before sending.<br />
<br />
== Sending patches ==<br />
<br />
Please send your patches to <code>devel (AT) openvz.org</code> mailing list, preferably using <code>git send-email</code>.<br />
<br />
You need to be subscribed in order to post. The list is managed by mailman, there are two ways to subscribe:<br />
<br />
# Send an email to <code>devel-join (AT) openvz.org</code><br />
# Use a web interface at https://lists.openvz.org/mailman/listinfo/devel<br />
<br />
{{Note|You need to be subscribed first in order to be able to post.}}<br />
<br />
== See also ==<br />
* [[Contribute]]<br />
* [[Kernel build]]<br />
* [[Kernel versioning]]<br />
* [[Kernel flavors]]<br />
* [[Kernel configuration]]<br />
* [[Porting the kernel]]<br />
* [[Hardware testing]]<br />
* [[Remote console setup]]<br />
<br />
== External links ==<br />
* https://www.kernel.org/doc/Documentation/CodingStyle<br />
* http://book.git-scm.com/<br />
* http://git-scm.com/documentation<br />
<br />
[[Category:Development]]<br />
[[Category:Kernel]]<br />
[[Category:Contributions]]<br />
[[Category:Virtuozzo]]</div>Kirhttps://wiki.openvz.org/index.php?title=Download/template&diff=23047Download/template2018-11-27T02:49:34Z<p>Kir: rm translate tags</p>
<hr />
<div><br />
A '''template''' is an image of an OS (i.e. a Linux distribution) aimed for installation into a container.<br />
<br />
;[[Download/template/precreated|Precreated]]<br />
:Precreated templates of different distributions.<br />
<br />
== Unsupported ==<br />
<br />
{{Warning|The software below is unmaintained and unsupported. Do not use it, do not file bugs about it.}}<br />
<br />
;[[Download/template/utils|Utilities]]<br />
:Template utilities are programs designed to assist with template maintenance, such as the creation and update of templates and containers. Currently these consists of [[Download/vzpkg|'''vzpkg''']], [[Download/vzyum|'''vzyum''']] and several versions of the RPM utility repackaged for OpenVZ. '''All this is optional and currently only works on systems with x86 architecture and with python <= 2.4.'''<br />
;[[Download/template/metadata|Metadata]]<br />
: Template metadata is data needed to (re)create or update template cache using template utilities. Metadata for a template contains the following information: list of packages that form this template; locations of package repositories; scripts needed to be executed on various stages of template installation; public GPG key(s) needed to check signatures of packages; additional OpenVZ-specific packages.<br />
<br />
== See also ==<br />
<br />
* [[:Category:Templates]]</div>Kirhttps://wiki.openvz.org/index.php?title=Download&diff=23046Download2018-11-27T02:48:47Z<p>Kir: rm translate tags</p>
<hr />
<div><br />
OpenVZ consists of a kernel, some user-level tools, and container templates. Kernel and tools are needed to install OpenVZ, and templates are needed to create containers.<br />
<br />
For kernel and utilities installation instructions, see [[Quick installation]]. For information about templates, see [[OS template cache preparation]].<br />
<br />
== Downloads ==<br />
<br />
; [[Download/kernel|Kernel]]<br />
: Kernel is the heart of OpenVZ. This is modified Linux kernel with virtualization layer added. <br />
; [[Download/utils|Utilities]]<br />
: Set of user-level tools needed to run OpenVZ. Consists of [[Download/vzctl|'''vzctl''']] — an utility to manage containers, [[Download/ploop|'''ploop''']] — a library and a set of utilities to control ploop device, and [[Download/vzquota|'''vzquota''']] — per-container disk quota configuration tool.<br />
; [[Download/templates|Templates]]<br />
:Templates are OS images for installation into OpenVZ container. An OS template is basically a set of packages from some Linux distribution used to populate a container. With OpenVZ, different distributions can co-exist on the same hardware box, so multiple OS templates are available. Here you can find various OS templates for different distributions. <br />
; [[Download/live CD|Live CDs]]<br />
:Live CD is the best way to test drive OpenVZ without a need to install it.<br />
; Virtuozzo 7 [http://download.openvz.org/virtuozzo/releases/ installation image]<br />
[[Virtuozzo]] is a Linux distribution based on OpenVZ components.<br />
<br />
== Direct downloads and mirrors ==<br />
All the downloadable stuff is also available directly from [[download:|download.openvz.org]] and its [http://mirrors.openvz.org/ mirrors].<br />
<br />
== Yum repository ==<br />
<br />
If you are using yum, you can add openvz yum repository by putting [[download:openvz.repo]] file to the <code>/etc/yum.repos.d/</code> directory on your machine. For more info about yum and OpenVZ yum repository, see [[Yum]].<br />
<br />
== GPG signed ==<br />
<br />
Note that all RPM packages from OpenVZ project should be signed by our GPG key. See [[Package signatures]] for details.<br />
<br />
<br />
[[Category:Download]]</div>Kirhttps://wiki.openvz.org/index.php?title=Quick_installation&diff=23045Quick installation2018-11-27T02:47:00Z<p>Kir: rm translate tags</p>
<hr />
<div>{{Virtuozzo}}<br />
<br />
{{Note|See [[Quick installation (legacy)]] if you are looking to install the legacy version of OpenVZ.}}<br />
<br />
This document briefly describes the steps needed to install Virtuozzo 7 on your machine.<br />
<br />
There are a few ways to install Virtuozzo:<br />
<br />
== Bare-metal installation ==<br />
<br />
OpenVZ project builds its own Linux distribution with both hypervisor and container virtualization.<br />
It is based on our own Linux distribution, with the additions of [[Download/kernel/rhel7-testing|our custom kernel]], OpenVZ management utilities, [[QEMU]] and Virtuozzo installer. It is highly recommended to use OpenVZ containers and virtual machines with this Virtuozzo installation image. See [[Virtuozzo]].<br />
[https://download.openvz.org/virtuozzo/releases/7.0/x86_64/iso/ Download] installation ISO image.<br />
<br />
== Using Virtuozzo in the Vagrant box ==<br />
<br />
[https://www.vagrantup.com/ Vagrant] is a tool for creating reproducible and portable development environments.<br />
It is easy to run environment with Virtuozzo using Vagrant:<br />
<br />
* Download and [https://docs.vagrantup.com/v2/installation/ install Vagrant]<br />
* Download and install [https://www.virtualbox.org/wiki/Downloads Virtualbox], Parallels Desktop, VMware Fusion or VMware Workstation. Please note that you need to enable nested virtualization support in your hypervisor to run virtual machines on Virtuozzo 7. VirtualBox does not officially support nested virtualization now.<br />
* Download [https://atlas.hashicorp.com/OpenVZ/boxes/Virtuozzo-7.0 Virtuozzo box]:<br />
<br />
$ vagrant init OpenVZ/Virtuozzo-7.0<br />
<br />
* Run box:<br />
<br />
$ vagrant up --provider virtualbox<br />
<br />
and in case of VMware hypervisor:<br />
<br />
$ vagrant up --provider vmware_desktop<br />
<br />
and in case of Parallels hypervisor:<br />
<br />
$ vagrant up --provider parallels<br />
<br />
* Attach to console:<br />
<br />
$ vagrant ssh<br />
<br />
* Use ''vagrant/vagrant'' to login inside box<br />
<br />
== Using Virtuozzo in the Amazon EC2 ==<br />
<br />
Follow steps in [[Using Virtuozzo in the Amazon EC2]].<br />
<br />
== Using Virtuozzo ==<br />
<br />
Page with [[screencasts]] shows demo with a few Virtuozzo commands. Feel free to add more.<br />
<br />
== See also ==<br />
* [https://docs.openvz.org/ Official Virtuozzo documentation]<br />
<br />
[[Category: Installation]]<br />
[[Category: HOWTO]]</div>Kirhttps://wiki.openvz.org/index.php?title=FAQ&diff=23044FAQ2018-11-27T02:45:30Z<p>Kir: rm translate tags</p>
<hr />
<div>{{Virtuozzo}}<br />
<br />
== General ==<br />
<br />
===== So what is Virtuozzo? =====<br />
Virtuozzo is a Linux based virtualization platform, combining container and hypervisor virtualization, into a single product. While primarily built for service providers to run cloud services and applications, it is used by variety of businesses, including MSP, SMB and Enterprises.<br />
<br />
===== What is OpenVZ and how it compares to Virtuozzo? =====<br />
OpenVZ is a free and opensource portion of Virtuozzo. It includes core of Virtuozzo functionality, like kernel and command line management tools for creating and managing containers. Virtuozzo includes everything that OpenVZ does, plus additional features and services available with the commercial version only. <br />
<br />
===== How does Virtuozzo 7/OpenVZ pair compares to its predecessor (Virtuozzo versions 4.x and 6/OpenVZ) =====<br />
Previously, OpenVZ and Virtuozzo were built out of the same code base with some unique patches applied. That warranted the user interfaces to be similar but not identical. With Virtuozzo 7, the compatibility will be on the binary level - effectively the open source components will be the same between OpenVZ and Virtuozzo.<br />
<br />
===== How OpenVZ users will benefit from it? =====<br />
OpenVZ components will be undergoing the same testing procedures as the commercial product. Also, some new features previously available on Virtuozzo only (notably hypervisor) will become available on the product built for OpenVZ community users.<br />
<br />
===== What support options are available for Virtuozzo 7? =====<br />
For the moment, only preview (beta) versions of Virtuozzo 7 are available. They are intended for development and testing only, not for production. Virtuozzo 7 is not yet commercially supported. For supported commercial version, please refer to [http://www.odin.com/products/virtuozzo/ Virtuozzo 6].<br />
<br />
===== Why I need Virtuozzo/OpenVZ when LXC exist? =====<br />
See our [[comparison]] of different virtualization solutions.<br />
<br />
===== When OpenVZ will be in upstream kernel? =====<br />
Our kernel developers [http://openvz.org/File:Kernel_patches_stats.png work hard] to merge containers functionality into the upstream Linux kernel, making OpenVZ team the biggest contributor to Linux Containers (LXC) kernel, with features such as PID and network namespaces, memory controller, checkpoint-restore and much more.<br />
<br />
<br />
===== I want to show my appreciation to OpenVZ and put some logo to my site. Where to get it? =====<br />
:See [[Artwork]].<br />
<br />
===== What kind of documentation is available? =====<br />
<br />
:Aside from this wiki, which contains lots of information, you can check extensive [[Man|manual pages]] and [http://docs.openvz.org Virtuozzo documentation].<br />
<br />
===== Who needs OpenVZ? How it can be used? =====<br />
:See [[Use cases]].<br />
<br />
===== How scalable is OpenVZ? =====<br />
<br />
OpenVZ technology scales as well as standard Linux kernel — up to thousands of CPUs and terabytes of RAM. Read more about [[WP/Containers_density|OpenVZ containers density]] and [[performance]].<br />
<br />
== Installation and upgrade ==<br />
<br />
===== How to install OpenVZ? =====<br />
<br />
There are two versions of OpenVZ available:<br />
<br />
* [[Roadmap|stable version]]: OpenVZ legacy (based on RHEL5 and RHEL6 kernels).<br />
* [[Roadmap|development version]]: [[Virtuozzo]] Linux distribution based on RHEL7 kernel.<br />
<br />
See [[Quick installation]]<br />
<br />
===== What hardware is supported by OpenVZ kernel? =====<br />
:See [https://hardware.redhat.com/ RHEL Hardware Compatibility List].<br />
<br />
===== How existing OpenVZ users can upgrade to the [[Virtuozzo|new version]]? =====<br />
While there is no in-place upgrade, we prepared [[Upgrade_script_from_OpenVZ_to_Virtuozzo_7|upgrade script]] for OpenVZ users to move their containers to the new platform. The script allows to transfer containers from old to new OpenVZ version (or from OpenVZ to Virtuozzo).</div>Kirhttps://wiki.openvz.org/index.php?title=Contribute&diff=23043Contribute2018-11-27T02:43:56Z<p>Kir: rm translate tags</p>
<hr />
<div>OpenVZ is open source software, and if you like it, the best thing you can do is help the project. There are many ways that you can contribute. Whether you are a normal user, a geek, or a hardcore developer, the one and most important thing you can do is to actually use OpenVZ.<br />
<br />
The list below explains some of the ways that you can contribute.<br />
<br />
== Contribute code ==<br />
<br />
If you want to become an OpenVZ developer, please subscribe to the [http://openvz.org/mailman/listinfo/devel devel mailing list] and do one of the following:<br />
<br />
* Tell what you want to do to [[Contacts|community]] and suggest new [[Wishlist|features/ideas]].<br />
* Fix open [https://bugs.openvz.org/ bugs].<br />
* [[How_to_submit_patches|Send patches]] for kernel and userspace code.<br />
* Implement ideas from [[wishlist]].<br />
* Contribute to [http://criu.org/TODO CRIU] development.<br />
<br />
== Contribute quality ==<br />
<br />
* Submit [[Reporting_OpenVZ_problem|good]] [https://bugzilla.openvz.org/ bug reports].<br />
* Help us to reproduce old bugs on latest OpenVZ versions.<br />
* Participate in testing of new versions of [[:Category:Sub-projects | OpenVZ/Virtuozzo components]] and give us [[Contacts|feedback]] about changes. Information required to testing is in [[QA|QA section]].<br />
* Correct spelling and grammar mistakes in the documentation.<br />
* Take a look at [[Wishlist#Software_testing|QA wishlist]]<br />
<br />
== Contribute documentation ==<br />
<br />
* Help write good documentation.<br />
* Help [[Wiki maintenance|maintain]] the wiki.<br />
* Send us corrections/additions to the existing manuals.<br />
* Write your own guide or [[:Category:HOWTO|HOWTO]], or help to expand [[:Category:Stubs|stub articles]].<br />
* [https://www.mediawiki.org/wiki/Help:Extension:Translate/Page_translation_example Translate] the documentation into another language.<br />
* '''Proofread''' existing documentation, follow the examples, and make corrections.<br />
* Create [[screencasts]], [https://www.youtube.com/playlist?list=PL86FC0XuGZPIhm6Uva2e3XcehdHaOVMCg demo video], screenshots, and graphics for the documentation.<br />
* Expand the [[Category:Definitions|Glossary]] of technical terms (so non-geeks can understand).<br />
<br />
== Contribute publicity ==<br />
<br />
{{Out|Note: As OpenVZ gets more popular, there will be more people wanting to contribute.}}<br />
<br />
* Put an appropriate [[Artwork|banner, button]] or just some text on your site linking back to [https://openvz.org/ openvz.org].<br />
* Write '''reviews''' about [[QA_TODO_list|new OpenVZ features]].<br />
* [[Spreading the word]]<br />
* Convince people to use Vituozzo containers when possible.<br />
* Write about [[Use_cases|new ways]] of using OpenVZ.<br />
* Submit [[artwork]] (icons, backgrounds, logos).<br />
<br />
== Contribute appreciation ==<br />
<br />
* Be '''polite''' when reporting bugs or asking for new features; after all, the developers have no obligation to do it.<br />
* Express your appreciation to developers (through e-mail, bug reports, and IRC).<br />
* [[Donate|Give the project or a developer a donation/gift]] (many of us have wish lists for this).<br />
<br />
== Contribute support ==<br />
<br />
* Participate in the [[mailing lists]], [[IRC|IRC channel]], [http://forum.openvz.org/ forums], if you know some the answer to a question asked, feel free to share it with others.<br />
* Contribute to (or start) an online support group.<br />
* Write '''HOWTOs''' and post them in the [[:Category:HOWTO|Tutorials and Howtos]] or your own blog.<br />
* [[Setting up a mirror|Setup]] a [http://mirrors.openvz.org/ public OpenVZ mirror].<br />
* Contribute new [[How to create OS template|OS templates]].<br />
<br />
== Contribute code of infrastructure (DevOps) ==<br />
<br />
* Automate [[Wishlist#DevOps|all the things]]<br />
* Make [[packages]] with OpenVZ components<br />
<br />
== Contribute creativity ==<br />
<br />
* Web design for [[OpenVZ_infrastructure|OpenVZ services]]. See [[design tasks]].<br />
* OpenVZ [http://store.openvz.org T-shirt] prints: [[T-Shirt ideas|new ideas]]<br />
* [[Artwork]]: update OpenVZ logo (may be material design?)<br />
<br />
== See also ==<br />
<br />
* [[Development portal]]<br />
* [[Membership]]<br />
<br />
[[Category: Infrastructure]]<br />
[[Category: Development]]<br />
[[Category: Contributions]]</div>Kirhttps://wiki.openvz.org/index.php?title=Main_Page&diff=23042Main Page2018-11-27T02:42:21Z<p>Kir: rm translate tags</p>
<hr />
<div>__NOTOC__ __NOEDITSECTION__<br />
{{Main page announce}}<br />
{{News sidebar}}<br />
<br />
'''OpenVZ''' is a container-based virtualization for Linux. OpenVZ creates multiple secure, isolated Linux containers (otherwise known as VEs or VPSs) on a single physical server enabling better server utilization and ensuring that applications do not conflict. Each container performs and executes exactly like a stand-alone server; a container can be rebooted independently and have root access, users, IP addresses, memory, processes, files, applications, system libraries and configuration files. <br />
<br />
OpenVZ is free open source software, available under GNU GPL.<br />
<br />
OpenVZ is the basis of [[Virtuozzo]], a virtualization solution offered by [http://www.virtuozzo.com/ Virtuozzo] company. Virtuozzo is optimized for hosters and offers hypervisor (VMs in addition to containers), [[Virtuozzo_Storage|distributed cloud storage]], dedicated support, management tools, and easy installation.<br />
<br />
== Installation and usage ==<br />
<br />
OpenVZ is easy to install if you already have Linux installed on your machine. See [[quick installation]] for installation info. Alternatively, you can try a [[Download live CD|live CD]] to test drive the technology without a need to install anything.<br />
<br />
A comprehensive (although somewhat old) {{PDFlink|[[download:doc/OpenVZ-Users-Guide.pdf|doc/OpenVZ-Users-Guide.pdf]]| 1.3&nbsp;MB}} is a good start. This wiki also has a lot of information (use search function, see [[Special:Categories|list of all categories]] or [[Special:Allpages|list of all pages]].<br />
<br />
== Support ==<br />
<br />
The supported version of OpenVZ is [https://virtuozzo.com/openvz Virtuozzo].<br />
<br />
=== Free support === <br />
<br />
Please read the documentation before asking questions. Check the [[FAQ]], use [[google:openvz|Google]], search both this wiki and the [http://forum.openvz.org/index.php?t=search forum]. If this doesn't help, ask on either [[forum:|forum]] or a [[mailing list]]. Please report all bugs to [https://bugs.openvz.org/ OpenVZ bug tracker].<br />
<br />
== This wiki ==<br />
<br />
This site is a wiki — the place to gain and share your OpenVZ knowledge. Wiki is a documentation portal, a knowledge base, a collaboration tool. Everyone (you!) can create or edit content, it's really easy. For information about wiki syntax and wiki editing, see [[meta:Help:Editing]].<br />
<br />
Below are a few links you can start from. In addition, you might want to take a look at the list of [[Special:Categories|all categories]] or [[Special:Allpages|all pages]].<br />
<br />
;[[:Category: Concepts|Concepts]]<br />
: OpenVZ and virtualization concepts<br />
;[[:Category: Technology|Technology]]<br />
: Description of OpenVZ technologies<br />
;[[:Category: Installation|Installation]]<br />
: How to install OpenVZ<br />
;[[:Category: Templates|Templates]]<br />
: Everything about OpenVZ templates<br />
;[[:Category: Kernel|Kernel]]<br />
: Articles concerning OpenVZ kernel<br />
;[[:Category:Troubleshooting|Troubleshooting]]<br />
: What to do if something fails<br />
;[[:Category:Networking|Networking]]<br />
: Networking-related articles<br />
;[[:Category:Storage|Storage]]<br />
: Storage-related articles (mostly [[ploop]] and [[pstorage]])<br />
;[[:Category:HOWTO|HOWTOs]]<br />
: How to do something<br />
;[[FAQ]]<br />
: Frequently Asked Questions<br />
;[[Artwork]]<br />
: Show your appreciation of OpenVZ on your site using these images<br />
;[[:Category:Definitions|Definitions]]<br />
: Short definitions of various terms used in OpenVZ<br />
;[[History]]<br />
: list of major project milestones<br />
;[[Interviews]] <br />
: public conversations with OpenVZ developers<br />
;[[Comparison]]<br />
: to other container solutions<br />
;[[Roadmap]]<br />
: past and future releases of OpenVZ and its components<br />
<br />
== External links ==<br />
* [[wikipedia:OpenVZ]]<br />
* [http://criu.org criu.org]<br />
* [[meta:Help:Editing]]</div>Kirhttps://wiki.openvz.org/index.php?title=Download/vzctl/4.11.1/changes&diff=23024Download/vzctl/4.11.1/changes2018-09-18T00:55:15Z<p>Kir: +vertical space</p>
<hr />
<div>== Changes ==<br />
Since {{dlink|vzctl|4.9.4}}:<br />
<br />
Fixes:<br />
* quotacheck failure on ploop-based CentOS 7.5 containers<br />
* postcreate.sh: support for Debian 8/Ubuntu 15.04+ xattrs<br />
* vzctl create: add pigz support (if available)<br />
* vzlist: add netfilter, capability output fields<br />
* compilation fixes for Alpine Linux / musl libc<br />
* vzctl destroy: handle the semi-mounted ploop<br />
* vzubc: allow for more than 999%<br />
<br />
{{git log|vzctl|vzctl-4.11.1|}}<br />
<br />
=== Thanks ===<br />
<br />
OpenVZ project would like to thank the following people who contributed patches<br />
and/or provided bug reports for this vzctl release (in no particular order):<br />
<br />
* Sergei A Mamonov<br />
* Dennis Przytarski<br />
* Fusl Dash</div>Kirhttps://wiki.openvz.org/index.php?title=Download/vzctl/4.11.1/changes&diff=23023Download/vzctl/4.11.1/changes2018-09-18T00:54:26Z<p>Kir: minor rewording</p>
<hr />
<div>== Changes ==<br />
Since {{dlink|vzctl|4.9.4}}:<br />
Fixes:<br />
* quotacheck failure on ploop-based CentOS 7.5 containers<br />
* postcreate.sh: support for Debian 8/Ubuntu 15.04+ xattrs<br />
* vzctl create: add pigz support (if available)<br />
* vzlist: add netfilter, capability output fields<br />
* compilation fixes for Alpine Linux / musl libc<br />
* vzctl destroy: handle the semi-mounted ploop<br />
* vzubc: allow for more than 999%<br />
<br />
{{git log|vzctl|vzctl-4.11.1|}}<br />
<br />
=== Thanks ===<br />
<br />
OpenVZ project would like to thank the following people who contributed patches<br />
and/or provided bug reports for this vzctl release (in no particular order):<br />
<br />
* Sergei A Mamonov<br />
* Dennis Przytarski<br />
* Fusl Dash</div>Kirhttps://wiki.openvz.org/index.php?title=User:Flip101&diff=22942User:Flip1012018-05-17T16:43:55Z<p>Kir: Creating user page for new user.</p>
<hr />
<div>nothing here yet, perhaps later. I am just making a tiny change here and do not want to disclose my bio</div>Kirhttps://wiki.openvz.org/index.php?title=Download/vzstats/0.5.5/changes&diff=22757Download/vzstats/0.5.5/changes2017-07-17T20:32:23Z<p>Kir: fix wording</p>
<hr />
<div>== Changes ==<br />
Since version {{dlink|vzstats|0.5.3}}:<br />
* removed obsoleted CA bundle that was blocking upload to vzstats.openvz.org ({{OVZ|6913}})<br />
<br />
{{git log|vzstats|vzstats-0.5.5|}}</div>Kirhttps://wiki.openvz.org/index.php?title=Package_managers&diff=22659Package managers2017-06-20T20:55:15Z<p>Kir: fix dpkg -s</p>
<hr />
<div>With OpenVZ, you can run many different Linux distributions on a single box. One particular thing in which distributions differ is package management. This article summarizes how to perform various common package management tasks on a different distributions.<br />
<br />
== Commands ==<br />
{| class="wikitable"<br />
! align="center" | Action<br />
! RPM<br/><small>RHEL, Fedora, CentOS, Mandriva, SUSE, ...</small><br />
! DEB<br/><small>Debian, Knoppix, Ubuntu, ...</small><br />
! Ebuild<br/><small>Gentoo and derivatives (Sabayon, Ututo, ...)</small><br />
! Pacman<br/><small>Arch Linux</small><br />
|-<br />
! colspan="5" align="center" | <big>'''Basic queries'''</big><br />
|-<br />
! List of all installed packages<br />
|| <code>rpm -qa</code><br />
|| <code>dpkg -l</code><br />
|| <code>equery list '*'</code><br />
|| <code>pacman -Q</code><br />
|-<br />
! List of installed packages matching ''substr''<br />
|| <code>rpm -qa ''\*substr\*''</code><br />
|| <code>dpkg -l ''\*substr\*''</code><br />
|| <code>equery list ''substr''</code><br />
|| <code>pacman -Q | grep ''substr''</code><br />
|-<br />
! Basic information about an installed ''package''<br />
|| <code>rpm -qi ''package''</code><br />
|| <code>dpkg -s ''package''</code><br />
|| <code>eix ''package''</code><br />
|| <code>pacman -Qi ''package''</code><br />
|-<br />
! List of files in a given ''package''<br />
|| <code>rpm -ql ''package''</code><br />
|| <code>dpkg -L ''package''</code><br />
|| <code>equery files ''package''</code><br />
|| <code>pacman -Ql ''package''</code><br />
|-<br />
! colspan="5" align="center" | <big>'''Advanced queries'''</big><br />
|-<br />
! Which package a ''file'' belongs to?<br />
|| <code>rpm -qf ''file''</code><br />
|| <code>dpkg -S ''file''</code><br />
|| <code>equery belongs ''file''</code><br />
|| <code>pacman -Qo ''file''</code><br />
|-<br />
! Check the hash (i.e. MD5 etc.) sums of an installed package<br />
|| <code>rpm -V ''package''</code><br />
|| <code>debsums -ca ''package''</code><br />
|| <code>equery check ''package''</code><br />
||<br />
|-<br />
! Show pre/post install/uninstall scripts from a ''package''<br />
|| <code>rpm -q --scripts ''package''</code><br />
|| <code>less /var/lib/dpkg/info/''package''.{pre,post,config}*</code><br />
|| <code>cat `equery which ''package''`</code><br />
||<br />
|-<br />
! Show change log for a ''package''<br />
|| <code>rpm -q --changelog ''package''</code><br />
|| <code>zcat /usr/share/doc/''package''/changelog.Debian.gz</code><br/><code>aptitude [-t release] changelog ''package''</code><br />
|| <code>view /usr/portage/''category''/''package''/ChangeLog</code><br />
|| <code>pacman -Qc ''package''</code><br />
|-<br />
! colspan="5" align="center" | <big>'''Local package installation/upgrade/removal'''</big><br />
|-<br />
! Install a package from local ''package_file''<br />
|| <code>rpm -ihv ''package_file*.rpm''<br/>yum localinstall ''package_file*.rpm''<ref name="localinstall">In case there are unsatisfied dependencies for ''package_file'', yum will try to get and install it from known repositores.</ref></code><br />
|| <code>dpkg -i ''package_file*.deb'' <ref name="apt">Usually it is not necessary to download packages manually and install them. Use apt-cache search ''name'' to search for package in configured repositories and apt-get install ''package'' to install package and all it's dependencies</ref></code><br />
|| <code>emerge --usepkg|-k ''package''<ref name="emerge-usepkg">Use a binary package if it is available from $PKGDIR, otherwise emerge from source as usual.</ref></code><br/><code>emerge --usepkgonly|-K ''package''<ref name="emerge-usepkgonly">Use a binary package if it is available from $PKGDIR, otherwise abort.</ref></code><br />
|| <code>pacman -U ''package''</code><br />
|-<br />
! Upgrade a package from local ''package_file''<br />
|| <code>rpm -Uhv ''package_file*.rpm''</code><br />
|| <code>dpkg -i ''package_file*.deb'' <ref name="apt"/></code><br />
|| <code>emerge --update --usepkg|-k ''package''<ref name="emerge-usepkg"/></code><br/><br />
<code>emerge --update --usepkgonly|-K ''package''<ref name="emerge-usepkgonly"/></code><br />
|| <code>pacman -U ''package''</code><br />
|-<br />
! Remove an installed ''package''<br />
|| <code>rpm -e ''package''</code><br/><br />
<code>yum remove|erase ''package''<ref name="yum-remove">This will also remove any packages which depend on the ''package''</ref></code><br />
|| <code>dpkg -r ''package''</code><br/><br />
<code>dpkg -P ''package''</code><br />
|| <code>emerge --unmerge ''package''</code><br/><br />
<code>emerge --prune ''package''</code><br />
|| <code>pacman -R ''package''</code><br />
|-<br />
! colspan="5" align="center" | <big>'''Package installation from repositories'''</big><br />
|-<br />
! Install a ''package''<br />
|| <code>yum install ''package''</code><br/><br />
<code>urpmi ''package''</code><br />
|| <code>apt-get update && apt-get install ''package''</code><br/><br />
<code>aptitude update && aptitude install ''package''</code><br />
|| <code>emerge -av ''package''</code><br />
|| <code>pacman -S ''package''</code><br />
|-<br />
! Install a debug information files for a ''package''<br />
|| <code>debuginfo-install ''package''</code><br />
|| <br />
|| <code>FEATURES="splitdebug installsources" emerge -av ''package''</code><br />
||<br />
|-<br />
! Only download a ''package'' from repository, do not install<br />
|| First install the yum-downloadonly plugin by running: <br/><code>yum install yum-downloadonly</code><br/> And then: <br/> <code>yum install|update ''package'' -y --downloadonly --downloaddir=/opt</code><br />
|| <code>apt-get install --download-only --reinstall ''package''</code><ref name="dpkgdir">Package will reside in /var/cache/apt/archives.</ref><br/><code>aptitude download ''package''</code><br />
|| <code>emerge -avf ''package''</code><ref name="distfiles">Package sources will reside in /usr/portage/distfiles.</ref><br />
|| <code>pacman -Sw ''package''</code><br />
|-<br />
! colspan="5" align="center" | <big>'''Get information about package interdependencies'''</big><br />
|-<br />
! What a given ''package'' provides?<br />
|| <code>rpm -q --provides ''package''</code><br />
|| <code>dpkg-query -W -f='${Provides}\n' ''package''</code><br />
|| <code>equery files ''package'' (package must be installed first)</code><br />
|| <code>pacman -Ql ''package'' (package must be installed first)</code><br />
|-<br />
! What a given ''package'' requires?<br />
|| <code>rpm -q --requires ''package''</code><br />
|| <code>dpkg-query -W -f='${Depends}\n' ''package''</code><br />
|| <code>equery depgraph --depth=1 ''package''</code><br />
|| <code>pacman -Si ''package''</code><br />
|-<br />
! Which installed package(s) provide a given ''dependency''<ref name="dep">In rpm world, a ''dependency'' can be a package name, a file, or a special atom like <code>perl(IO::Zlib)</code> for a perl module. In deb world, this can be either real or virtual package name.</ref>?<br />
|| <code>rpm -q --whatprovides ''dependency''</code><br />
|| <code>dpkg-query -W -f='${Package}: ${Provides}\n' '*' | grep ': .*''dependency''<nowiki>'</nowiki></code><br />
|| <code>equery belongs ''dependency''</code><br />
||<br />
|-<br />
! Which installed package(s) require a given ''dependency''<ref name="dep"/>?<br />
|| <code>rpm -q --whatrequires ''dependency''</code><br />
|| <code>dpkg-query -W -f='${Package}: ${Depends}\n' '*' | grep ': .*''package''<nowiki>'</nowiki></code><br><code>aptitude why ''package''</code><ref name="why">Actualy shows the whole dpendency situation that leads to install this package</ref><br />
|| <code>equery depends ''package''</code><br />
|| <code>pacman -Qi ''package'' | grep Required</code><br />
||<br />
|-<br />
! Show what prevents installation of a package<br />
|| <code>(yum/rpm tells with --verbose option -v)</code><br />
|| <code>aptitude why-not ''package''</code><br />
|| <code>emerge -pv ''package''</code><br />
||<br />
|-<br />
! Get package source files<br />
|| <code>yumdownloader --source ''package''</code><br />
|| <code>apt-get source ''package''</code><br />
|| <code>emerge -f ''package''</code><br />
|| <code>abs ''repository''/''package''</code><br />
|-<br />
! colspan="5" align="center" | <big>'''Working with package files'''</big><br />
|-<br />
! Unpack a package ''file'' to local directory<br />
|| <code>rpm2cpio ''file.rpm'' | cpio -id</code><br />
|| <code>dpkg -x / --extract ''file.deb'' .</code><br />
|| N/A<br />
|| <code>tar -xzf ''package''</code> if ''package''.pkg.tar.gz or<br/><code>tar -xJf ''package''</code> if ''package''.pkg.tar.xz<br />
|-<br />
! Check package file integrity (checksums, signatures...)<br />
|| <code>rpm -K ''file.rpm''</code><br/>(yum/rpm also checks GPG-signature and checksums automatically every time the package is installed or upgraded)<br />
|| <code>debsums ''package''</code><br />
|| <code>emerge -f ''package''</code><br />
||<br />
|-<br />
! Show package metadata<br />
|| <code>rpm -qip ''file.rpm''</code><br />
|| <code>dpkg -I / --info ''file.deb''</code><br />
|| N/A<br />
|| ??<br />
|-<br />
! Show package file list<br />
|| <code>rpm -qlvp ''file.rpm''</code><br />
|| <code>dpkg -c / --contents ''file.deb''</code><br />
|| N/A<br />
|| ??<br />
|-<br />
! colspan="5" align="center" | <big>'''Repository queries'''</big><br />
|-<br />
! Find a package in a repository which <code>/some/file</code> belongs to<br />
|| <code>yum provides ''/some/file''</code><br />
|| First run: <br/><code>apt-file update</code><br/>and then:<br/><code>apt-file search ''/some/file''</code><br />
|| N/A<br />
||<br />
|-<br />
! Find a package based on some string or part of the string descriping it<br />
|| <code>yum search ''\*substr\*''</code><br />
|| <code>apt-cache search ''\*substr\*''</code><br />
|| <code>eix -S ''substr''</code><br />
|| <code>pacman -Ss ''substr''</code><br />
|-<br />
! Shows the full description of ''package''<br />
|| <code>yum info ''package''</code><br />
|| <code>apt-cache show ''package''</code><br />
|| <code>eix ''package''</code><br />
|| <code>pacman -Si ''package''</code><br />
|}<br />
<br />
== Relevant directories and files ==<br />
<br />
=== Red Hat, Fedora, CentOS ===<br />
<br />
* yum config: <code>/etc/yum.conf</code>.<br />
* yum repos: <code>/etc/yum.repos.d/</code>.<br />
* rpm configs and macros: <code>/etc/rpm/</code>, <code>/usr/lib/rpm/</code>, <br />
* rpm DB: <code>/var/lib/rpm/</code><br />
<br />
=== Debian/Ubuntu ===<br />
<br />
* List of repositories and mirror sites: <code>/etc/apt/sources.list</code>, <code>/etc/apt/sources.list.d/</code>.<br />
<br />
=== Gentoo ===<br />
<br />
* emerge configs: <code>/etc/make.conf</code>, <code>/etc/portage/</code>.<br />
* Portage tree: <code>/usr/portage</code>.<br />
* Binary packages (FEATURES="buildpkg" enabled in make.conf): <code>/usr/portage/packages</code>.<br />
* Default directory to download sources to: <code>/usr/portage/distfiles</code>.<br />
* Default Portage working directory: <code>/var/lib/portage/</code>.<br />
<br />
== Notes==<br />
<references/><br />
<br />
== See also ==<br />
=== Debian ===<br />
* [http://www.debian.org/doc/FAQ/ch-pkgtools.en.html Debian FAQ: package management tools]<br />
* [http://www.debian.org/doc/manuals/apt-howto/ APT HOWTO]<br />
<br />
[[Category: HOWTO]]<br />
[[Category: Templates]]<br />
[[Category: Debian]]<br />
[[Category: Ubuntu]]<br />
[[Category: Gentoo]]</div>Kirhttps://wiki.openvz.org/index.php?title=VPS_vs_Dedicated&diff=22654VPS vs Dedicated2017-06-06T20:59:30Z<p>Kir: Protected "VPS vs Dedicated" ([Edit=Allow only autoconfirmed users] (indefinite) [Move=Allow only autoconfirmed users] (indefinite))</p>
<hr />
<div>Although I am somewhat of a new user to the container world I thought I'd write a short article giving an overview of why use container instead of dedicated servers for those of you who are involved in the hosting business or people thinking about leasing a container server. Here I will address misconceptions I had about container and talk about how my perspective on container is changing.<br />
<br />
Who am I? This article originally written by [http://www.perkel.com Marc Perkel] - a new container user - expressing my overview of OpenVZ from my perspective as a new user talking to other new users about my experience in learning this new environment. I am not an OpenVZ expert and I want to write this while I'm still new to OpenVZ so I can express my view from a new user's perspective. If you are just reading about container for the first time I am not that far ahead of you. This article is an attempt by me to give back a little to those who created this free software and give you new people an overview of the big picture as I learn this myself.<br />
<br />
== Why use Virtual Private Servers instead of Dedicated Servers ==<br />
<br />
Like many of you when I first heard of the idea of container I pictured it as some small lame server that is sold to 12 year olds trying to start hosting companies on the cheap. It had never quite caught my attention until I decided I needed a remote name server and all I needed was enough of a server to run bind, but didn't want to buy a dedicated box just to do that. So I got a container based on Virtuozzo for $80/year and it worked great.<br />
<br />
In the process however I started understanding the container concept and it became apparent that this is more than just a tool to create little servers. The way I see it container can replace dedicated servers in many situations in a data center and do a better job than dedicated. You can actually give the customer more horsepower and better hosting than selling them a small dedicated box. (Of course big customers will still need their own server.)<br />
<br />
I don't own a data center business myself but I have a friend who does and I colo several servers there. He has several racks of some old Celeron boxes with 512 Megs of RAM and one or two 80 Gig drives depending on if the customer has any concept of backups, which most of them don't. I'm looking at the racks of Celerons and P4s thinking that each rack could be consolidated into a single modern server and that the customers would actually have a better server than the one they are on now. And the cost savings would be tremendous.<br />
<br />
== Advantages of container ==<br />
<br />
Most small dedicated servers are a waste of resources. People buy bigger servers than they need and the excess capacity is wasted. These servers take both space and power which is expensive in a data center and you have hardware costs associated with each server that you have to recoup. People often don't do any backups so after several years the hard drive fails and they lose everything. And it's your fault for not backing them up in the first place.<br />
<br />
Imagine a rack of 16 Celeron boxes with 80 gig drives being replaced by a Dual Core Athlox X2 with 8 gigs of ram and 4 500gb SATA 2 drives running in a raid 10 configuration. (Writing this in Feb of 2007 for future historians who will read this and laugh at the old days when computers had just gigabytes.) The above server would cost about $2000 to build and only take 2U of space and use far less power than the 16 machines that are being replaced.<br />
<br />
Note that I'm suggesting in this example only a 16 to 1 consolidation. Everyone has the same amount of ram. In reality the consolidation is many times higher because most of those using the Celerons are not using all the memory. Many are using only 1/5 of what they have and a lot of that is used by the individual kernels running. In OpenVZ there is one kernel for everyone.<br />
<br />
Note also that many of these servers have idle time where the processor is doing nothing and they have lots of extra hard drive space that isn't being used. By consolidating these systems the free resources are combined allowing you to run many more logical servers that each have more resources than the individual servers.<br />
<br />
On a dedicated computer the user is stuck with an old slow 32 bit processor, a limited amount of ram, and an old slow hard drive with no backups. In a container that same user is running on a shared dual core 64 bit CPU sharing 8 gigs of ram with fast modern large hard drives with raid backup. That is a significant improvement over having their own dedicated box. So this is a better deal for the customer.<br />
<br />
=== Administration Advantages ===<br />
<br />
If a customer needs you to fix something on their dedicated server you have to either know the root password or take the server down and boot from a rescue CD to get in and fix it. You also can't access the customer's files without logging in to their server as root. In a container you as host can enter their server at any time without a password. (Keeping the host environment very secure of course.) That allows you to do maintenance without having to look up the person's root password.<br />
<br />
=== Ease of Setup ===<br />
<br />
Setup couldn't be easier as compared to building a dedicated server. All you have to do is type a few commands and the new virtual server is ready to go. You can have the customer running while you are still on the phone taking the order. A dedicated box requires setup, installation, and often has to be scheduled. This involves cost and time. container is ready instantly and easily. Any distro you want with all the latest updates installed. When a customer places an order they want it now. With container you can deliver it now.<br />
<br />
=== Backup Advantages ===<br />
<br />
Additionally you can access the customers files directly from the host environment. This allows you to run rsync scripts to back up all the virtual servers to external storage or backup servers without the customer being aware that you are doing sophisticated backups. Then when the customer calls you up in a panic and says, "I totally screwed up my server and deleted a bunch of files by accident. Can you get it back?" You can magically restore their lost data and you are forever their hero.<br />
<br />
=== IP Allocation Advantages ===<br />
<br />
Tired of allocating 4 IP addresses just to give the customer 1 usable? Or giving them 8 so they have 5 usable and most of them only use one? How inefficient is that? With OpenVZ you can allocate IP addresses individually so that if a customer only needs one IP then they get only 1 IP. But if they need 9 IP addresses you can give them exactly 9 of them. They can call you up and say I need one more IP and you can give it to them in seconds. On a dedicated server if you gave them a /29 vlan and they are using all 5 IPs and they need another one - that is a huge hassle.<br />
<br />
=== Disk Space Allocation ===<br />
<br />
On dedicated servers you have to install a big hard drive that is mostly wasted. If the customer wants backups then it's two hard drives. In OpenVZ you just allocate space in the raid array based on what the customer actually needs and they only use the space that they use rather than what's allocated. The "allocation" is really just a software limit and that is a line in a text file that you can instantly change the moment the customer needs more space. On a dedicatd box if the customer needs a bigger drive then it's a trip to the data center with a new drive and a few hours time to copy everything over and replacing the drive, not to mention the down time.<br />
<br />
=== Memory Upgrades ===<br />
<br />
Memory upgrades are as easy as hard drive upgrades. Just one command than the user has more ram. But what if the server is full and you don't have any more ram? No problem. Just copy the user's container (virtual environment) over to another physical server with rsync and start them up there. In only a few minutes you've migrated them to a new box and they are up and running.<br />
<br />
=== Migration ===<br />
<br />
Suppose a customer just needs a bigger server. Migration is easy in the container environment because the container is consistent between servers. You just copy over the files and start it up. You don't have to build a new server, install an OS, copy it all over, and then mess with it for an hour getting everything to work.<br />
<br />
=== Emergency Procedures ===<br />
<br />
Let's say that a server fries. With container and good backups you have more options. You can copy the backup of the container onto another server and restore it as of the last (nightly) backup. (I'm a backup freak - but it pays.) That gets the customers up instantly if they need that while a tech can go down there and fix the server with less pressure. This give you more options when bad things happen.<br />
<br />
=== Load Balancing ===<br />
<br />
OpenVZ allows you to migrate servers live from one physical server to another. I haven't yet done that but I have done a shutdown, copy, and restart of the container on another server and it's so easy to do that. So suppose you have a server that's a little crowded and some user starts hogging some resources. No problem. You just move a few users to another box and problem solved. This could probably be done automatically with some well configured cluster and I would love it if someone wrote a wiki page telling us how to do it.<br />
<br />
=== Protecting your Customers ===<br />
<br />
Since you are managing the host system you can create IP filters and port blocking policies that help keep users from exploiting you or keep hackers from exploiting your users. Instead of a separate box that is all theirs you have them in a more managed shell allowing you to keep the inexperienced out of trouble. This provides them with a service that watched it more closely allowing them to do their own thing, but keeping you closer by to keep them out of trouble.<br />
<br />
== Cost ==<br />
<br />
The cost savings are rather obvious. An entire rack compressed into one or two computers. Picture the space and power savings. The greenhouse gas not being generated by the power you're not using. The number of computers that you are not buying. The hours you are saving in setup time and administrative time. When it comes to saving money this is definitely a winner. You can take that extra money and pass some on to customers and keep some extra for yourself.<br />
<br />
== The Down Side ==<br />
<br />
Any time you add another layer then you have another layer of things that can go wrong. It takes some learning to understand the process and there is the possibility that one person can screw up the system for everyone. As virtualization develops it will get better. OpenVZ is very stable in that it is far less intrusive than other virtualization methods. It is limited to Linux only so BSD and Windows users will have to do something else.<br />
<br />
== Conclusion ==<br />
<br />
I believe that container represents the future of computing. The space, power, and cost savings are too great to ignore. I see data centers that are massive clusters running tens of thousands of logical servers that transparently migrate around the physical resources and are up 100% of the time. Customers no longer will have to deal with issues of backups the way they have to now, and it will simplify the hosting process. I think that every data center should be looking into virtualization technology now with the idea that you are going to be doing this and it's time to at least start thinking about it and exploring it with an eye towards the future.<br />
<br />
I have to say that my view of container has radically changed and that I now see this as a solution not just for people wanting little servers but for most everyone who is looking for dedicated service. container is a different way of looking at the computing world and it takes some significant mental adjustment and education to grasp the big picture.<br />
<br />
[[Category: Technology]]<br />
[[Category: Concepts]]</div>Kirhttps://wiki.openvz.org/index.php?title=VPS_vs_Dedicated&diff=22653VPS vs Dedicated2017-06-06T20:58:56Z<p>Kir: spam removed</p>
<hr />
<div>Although I am somewhat of a new user to the container world I thought I'd write a short article giving an overview of why use container instead of dedicated servers for those of you who are involved in the hosting business or people thinking about leasing a container server. Here I will address misconceptions I had about container and talk about how my perspective on container is changing.<br />
<br />
Who am I? This article originally written by [http://www.perkel.com Marc Perkel] - a new container user - expressing my overview of OpenVZ from my perspective as a new user talking to other new users about my experience in learning this new environment. I am not an OpenVZ expert and I want to write this while I'm still new to OpenVZ so I can express my view from a new user's perspective. If you are just reading about container for the first time I am not that far ahead of you. This article is an attempt by me to give back a little to those who created this free software and give you new people an overview of the big picture as I learn this myself.<br />
<br />
== Why use Virtual Private Servers instead of Dedicated Servers ==<br />
<br />
Like many of you when I first heard of the idea of container I pictured it as some small lame server that is sold to 12 year olds trying to start hosting companies on the cheap. It had never quite caught my attention until I decided I needed a remote name server and all I needed was enough of a server to run bind, but didn't want to buy a dedicated box just to do that. So I got a container based on Virtuozzo for $80/year and it worked great.<br />
<br />
In the process however I started understanding the container concept and it became apparent that this is more than just a tool to create little servers. The way I see it container can replace dedicated servers in many situations in a data center and do a better job than dedicated. You can actually give the customer more horsepower and better hosting than selling them a small dedicated box. (Of course big customers will still need their own server.)<br />
<br />
I don't own a data center business myself but I have a friend who does and I colo several servers there. He has several racks of some old Celeron boxes with 512 Megs of RAM and one or two 80 Gig drives depending on if the customer has any concept of backups, which most of them don't. I'm looking at the racks of Celerons and P4s thinking that each rack could be consolidated into a single modern server and that the customers would actually have a better server than the one they are on now. And the cost savings would be tremendous.<br />
<br />
== Advantages of container ==<br />
<br />
Most small dedicated servers are a waste of resources. People buy bigger servers than they need and the excess capacity is wasted. These servers take both space and power which is expensive in a data center and you have hardware costs associated with each server that you have to recoup. People often don't do any backups so after several years the hard drive fails and they lose everything. And it's your fault for not backing them up in the first place.<br />
<br />
Imagine a rack of 16 Celeron boxes with 80 gig drives being replaced by a Dual Core Athlox X2 with 8 gigs of ram and 4 500gb SATA 2 drives running in a raid 10 configuration. (Writing this in Feb of 2007 for future historians who will read this and laugh at the old days when computers had just gigabytes.) The above server would cost about $2000 to build and only take 2U of space and use far less power than the 16 machines that are being replaced.<br />
<br />
Note that I'm suggesting in this example only a 16 to 1 consolidation. Everyone has the same amount of ram. In reality the consolidation is many times higher because most of those using the Celerons are not using all the memory. Many are using only 1/5 of what they have and a lot of that is used by the individual kernels running. In OpenVZ there is one kernel for everyone.<br />
<br />
Note also that many of these servers have idle time where the processor is doing nothing and they have lots of extra hard drive space that isn't being used. By consolidating these systems the free resources are combined allowing you to run many more logical servers that each have more resources than the individual servers.<br />
<br />
On a dedicated computer the user is stuck with an old slow 32 bit processor, a limited amount of ram, and an old slow hard drive with no backups. In a container that same user is running on a shared dual core 64 bit CPU sharing 8 gigs of ram with fast modern large hard drives with raid backup. That is a significant improvement over having their own dedicated box. So this is a better deal for the customer.<br />
<br />
=== Administration Advantages ===<br />
<br />
If a customer needs you to fix something on their dedicated server you have to either know the root password or take the server down and boot from a rescue CD to get in and fix it. You also can't access the customer's files without logging in to their server as root. In a container you as host can enter their server at any time without a password. (Keeping the host environment very secure of course.) That allows you to do maintenance without having to look up the person's root password.<br />
<br />
=== Ease of Setup ===<br />
<br />
Setup couldn't be easier as compared to building a dedicated server. All you have to do is type a few commands and the new virtual server is ready to go. You can have the customer running while you are still on the phone taking the order. A dedicated box requires setup, installation, and often has to be scheduled. This involves cost and time. container is ready instantly and easily. Any distro you want with all the latest updates installed. When a customer places an order they want it now. With container you can deliver it now.<br />
<br />
=== Backup Advantages ===<br />
<br />
Additionally you can access the customers files directly from the host environment. This allows you to run rsync scripts to back up all the virtual servers to external storage or backup servers without the customer being aware that you are doing sophisticated backups. Then when the customer calls you up in a panic and says, "I totally screwed up my server and deleted a bunch of files by accident. Can you get it back?" You can magically restore their lost data and you are forever their hero.<br />
<br />
=== IP Allocation Advantages ===<br />
<br />
Tired of allocating 4 IP addresses just to give the customer 1 usable? Or giving them 8 so they have 5 usable and most of them only use one? How inefficient is that? With OpenVZ you can allocate IP addresses individually so that if a customer only needs one IP then they get only 1 IP. But if they need 9 IP addresses you can give them exactly 9 of them. They can call you up and say I need one more IP and you can give it to them in seconds. On a dedicated server if you gave them a /29 vlan and they are using all 5 IPs and they need another one - that is a huge hassle.<br />
<br />
=== Disk Space Allocation ===<br />
<br />
On dedicated servers you have to install a big hard drive that is mostly wasted. If the customer wants backups then it's two hard drives. In OpenVZ you just allocate space in the raid array based on what the customer actually needs and they only use the space that they use rather than what's allocated. The "allocation" is really just a software limit and that is a line in a text file that you can instantly change the moment the customer needs more space. On a dedicatd box if the customer needs a bigger drive then it's a trip to the data center with a new drive and a few hours time to copy everything over and replacing the drive, not to mention the down time.<br />
<br />
=== Memory Upgrades ===<br />
<br />
Memory upgrades are as easy as hard drive upgrades. Just one command than the user has more ram. But what if the server is full and you don't have any more ram? No problem. Just copy the user's container (virtual environment) over to another physical server with rsync and start them up there. In only a few minutes you've migrated them to a new box and they are up and running.<br />
<br />
=== Migration ===<br />
<br />
Suppose a customer just needs a bigger server. Migration is easy in the container environment because the container is consistent between servers. You just copy over the files and start it up. You don't have to build a new server, install an OS, copy it all over, and then mess with it for an hour getting everything to work.<br />
<br />
=== Emergency Procedures ===<br />
<br />
Let's say that a server fries. With container and good backups you have more options. You can copy the backup of the container onto another server and restore it as of the last (nightly) backup. (I'm a backup freak - but it pays.) That gets the customers up instantly if they need that while a tech can go down there and fix the server with less pressure. This give you more options when bad things happen.<br />
<br />
=== Load Balancing ===<br />
<br />
OpenVZ allows you to migrate servers live from one physical server to another. I haven't yet done that but I have done a shutdown, copy, and restart of the container on another server and it's so easy to do that. So suppose you have a server that's a little crowded and some user starts hogging some resources. No problem. You just move a few users to another box and problem solved. This could probably be done automatically with some well configured cluster and I would love it if someone wrote a wiki page telling us how to do it.<br />
<br />
=== Protecting your Customers ===<br />
<br />
Since you are managing the host system you can create IP filters and port blocking policies that help keep users from exploiting you or keep hackers from exploiting your users. Instead of a separate box that is all theirs you have them in a more managed shell allowing you to keep the inexperienced out of trouble. This provides them with a service that watched it more closely allowing them to do their own thing, but keeping you closer by to keep them out of trouble.<br />
<br />
== Cost ==<br />
<br />
The cost savings are rather obvious. An entire rack compressed into one or two computers. Picture the space and power savings. The greenhouse gas not being generated by the power you're not using. The number of computers that you are not buying. The hours you are saving in setup time and administrative time. When it comes to saving money this is definitely a winner. You can take that extra money and pass some on to customers and keep some extra for yourself.<br />
<br />
== The Down Side ==<br />
<br />
Any time you add another layer then you have another layer of things that can go wrong. It takes some learning to understand the process and there is the possibility that one person can screw up the system for everyone. As virtualization develops it will get better. OpenVZ is very stable in that it is far less intrusive than other virtualization methods. It is limited to Linux only so BSD and Windows users will have to do something else.<br />
<br />
== Conclusion ==<br />
<br />
I believe that container represents the future of computing. The space, power, and cost savings are too great to ignore. I see data centers that are massive clusters running tens of thousands of logical servers that transparently migrate around the physical resources and are up 100% of the time. Customers no longer will have to deal with issues of backups the way they have to now, and it will simplify the hosting process. I think that every data center should be looking into virtualization technology now with the idea that you are going to be doing this and it's time to at least start thinking about it and exploring it with an eye towards the future.<br />
<br />
I have to say that my view of container has radically changed and that I now see this as a solution not just for people wanting little servers but for most everyone who is looking for dedicated service. container is a different way of looking at the computing world and it takes some significant mental adjustment and education to grasp the big picture.<br />
<br />
[[Category: Technology]]<br />
[[Category: Concepts]]</div>Kirhttps://wiki.openvz.org/index.php?title=Contribute&diff=22652Contribute2017-06-06T20:50:31Z<p>Kir: Reverted edits by 24.39.1.139 (talk) to last revision by Sergey Bronnikov</p>
<hr />
<div><languages /><br />
<br />
<translate><!--T:1--><br />
OpenVZ is open source software, and if you like it, the best thing you can do is help the project. There are many ways that you can contribute. Whether you are a normal user, a geek, or a hardcore developer, the one and most important thing you can do is to actually use OpenVZ.<br />
<br />
<!--T:2--><br />
The list below explains some of the ways that you can contribute.<br />
<br />
== Contribute code == <!--T:3--><br />
<br />
<!--T:4--><br />
If you want to become an OpenVZ developer, please subscribe to the [http://openvz.org/mailman/listinfo/devel devel mailing list] and do one of the following:<br />
<br />
<!--T:5--><br />
* Tell what you want to do to [[Contacts|community]] and suggest new [[Wishlist|features/ideas]].<br />
* Fix open [https://bugs.openvz.org/ bugs].<br />
* [[How_to_submit_patches|Send patches]] for kernel and userspace code.<br />
* Implement ideas from [[wishlist]].<br />
* Contribute to [http://criu.org/TODO CRIU] development.<br />
<br />
== Contribute quality == <!--T:6--><br />
<br />
<!--T:7--><br />
* Submit [[Reporting_OpenVZ_problem|good]] [https://bugzilla.openvz.org/ bug reports].<br />
* Help us to reproduce old bugs on latest OpenVZ versions.<br />
* Participate in testing of new versions of [[:Category:Sub-projects | OpenVZ/Virtuozzo components]] and give us [[Contacts|feedback]] about changes. Information required to testing is in [[QA|QA section]].<br />
* Correct spelling and grammar mistakes in the documentation.<br />
* Take a look at [[Wishlist#Software_testing|QA wishlist]]<br />
<br />
== Contribute documentation == <!--T:8--><br />
<br />
<!--T:9--><br />
* Help write good documentation.<br />
* Help [[Wiki maintenance|maintain]] the wiki.<br />
* Send us corrections/additions to the existing manuals.<br />
* Write your own guide or [[:Category:HOWTO|HOWTO]], or help to expand [[:Category:Stubs|stub articles]].<br />
* [https://www.mediawiki.org/wiki/Help:Extension:Translate/Page_translation_example Translate] the documentation into another language.<br />
* '''Proofread''' existing documentation, follow the examples, and make corrections.<br />
* Create [[screencasts]], [https://www.youtube.com/playlist?list=PL86FC0XuGZPIhm6Uva2e3XcehdHaOVMCg demo video], screenshots, and graphics for the documentation.<br />
* Expand the [[Category:Definitions|Glossary]] of technical terms (so non-geeks can understand).<br />
<br />
== Contribute publicity == <!--T:10--><br />
<br />
<!--T:11--><br />
{{Out|Note: As OpenVZ gets more popular, there will be more people wanting to contribute.}}<br />
<br />
<!--T:12--><br />
* Put an appropriate [[Artwork|banner, button]] or just some text on your site linking back to [https://openvz.org/ openvz.org].<br />
* Write '''reviews''' about [[QA_TODO_list|new OpenVZ features]].<br />
* [[Spreading the word]]<br />
* Convince people to use Vituozzo containers when possible.<br />
* Write about [[Use_cases|new ways]] of using OpenVZ.<br />
* Submit [[artwork]] (icons, backgrounds, logos).<br />
<br />
== Contribute appreciation == <!--T:13--><br />
<br />
<!--T:14--><br />
* Be '''polite''' when reporting bugs or asking for new features; after all, the developers have no obligation to do it.<br />
* Express your appreciation to developers (through e-mail, bug reports, and IRC).<br />
* [[Donate|Give the project or a developer a donation/gift]] (many of us have wish lists for this).<br />
<br />
== Contribute support == <!--T:15--><br />
<br />
<!--T:16--><br />
* Participate in the [[mailing lists]], [[IRC|IRC channel]], [http://forum.openvz.org/ forums], if you know some the answer to a question asked, feel free to share it with others.<br />
* Contribute to (or start) an online support group.<br />
* Write '''HOWTOs''' and post them in the [[:Category:HOWTO|Tutorials and Howtos]] or your own blog.<br />
* [[Setting up a mirror|Setup]] a [http://mirrors.openvz.org/ public OpenVZ mirror].<br />
* Contribute new [[How to create OS template|OS templates]].<br />
<br />
== Contribute code of infrastructure (DevOps) == <!--T:17--><br />
<br />
<!--T:18--><br />
* Automate [[Wishlist#DevOps|all the things]]<br />
* Make [[packages]] with OpenVZ components<br />
<br />
== Contribute creativity == <!--T:19--><br />
<br />
<!--T:20--><br />
* Web design for [[OpenVZ_infrastructure|OpenVZ services]]. See [[design tasks]].<br />
* OpenVZ [http://store.openvz.org T-shirt] prints: [[T-Shirt ideas|new ideas]]<br />
* [[Artwork]]: update OpenVZ logo (may be material design?)<br />
<br />
== See also == <!--T:21--><br />
<br />
<!--T:22--><br />
* [[Development portal]]<br />
* [[Membership]]<br />
</translate><br />
<br />
[[Category: Infrastructure]]<br />
[[Category: Development]]<br />
[[Category: Contributions]]</div>Kirhttps://wiki.openvz.org/index.php?title=FAQ&diff=22651FAQ2017-06-06T20:50:20Z<p>Kir: Reverted edits by 24.39.1.139 (talk) to last revision by Byrner</p>
<hr />
<div>{{Virtuozzo}}<br />
<br />
<translate><br />
== General == <!--T:1--><br />
<br />
===== So what is Virtuozzo? ===== <!--T:2--><br />
Virtuozzo is a Linux based virtualization platform, combining container and hypervisor virtualization, into a single product. While primarily built for service providers to run cloud services and applications, it is used by variety of businesses, including MSP, SMB and Enterprises.<br />
<br />
===== What is OpenVZ and how it compares to Virtuozzo? ===== <!--T:3--><br />
OpenVZ is a free and opensource portion of Virtuozzo. It includes core of Virtuozzo functionality, like kernel and command line management tools for creating and managing containers. Virtuozzo includes everything that OpenVZ does, plus additional features and services available with the commercial version only. <br />
<br />
===== How does Virtuozzo 7/OpenVZ pair compares to its predecessor (Virtuozzo versions 4.x and 6/OpenVZ) ===== <!--T:4--><br />
Previously, OpenVZ and Virtuozzo were built out of the same code base with some unique patches applied. That warranted the user interfaces to be similar but not identical. With Virtuozzo 7, the compatibility will be on the binary level - effectively the open source components will be the same between OpenVZ and Virtuozzo.<br />
<br />
===== How OpenVZ users will benefit from it? ===== <!--T:5--><br />
OpenVZ components will be undergoing the same testing procedures as the commercial product. Also, some new features previously available on Virtuozzo only (notably hypervisor) will become available on the product built for OpenVZ community users.<br />
<br />
===== What support options are available for Virtuozzo 7? ===== <!--T:6--><br />
For the moment, only preview (beta) versions of Virtuozzo 7 are available. They are intended for development and testing only, not for production. Virtuozzo 7 is not yet commercially supported. For supported commercial version, please refer to [http://www.odin.com/products/virtuozzo/ Virtuozzo 6].<br />
<br />
===== Why I need Virtuozzo/OpenVZ when LXC exist? ===== <!--T:7--><br />
See our [[comparison]] of different virtualization solutions.<br />
<br />
===== When OpenVZ will be in upstream kernel? ===== <!--T:8--><br />
Our kernel developers [http://openvz.org/File:Kernel_patches_stats.png work hard] to merge containers functionality into the upstream Linux kernel, making OpenVZ team the biggest contributor to Linux Containers (LXC) kernel, with features such as PID and network namespaces, memory controller, checkpoint-restore and much more.<br />
<br />
<br />
===== I want to show my appreciation to OpenVZ and put some logo to my site. Where to get it? ===== <!--T:9--><br />
:See [[Artwork]].<br />
<br />
===== What kind of documentation is available? ===== <!--T:10--><br />
<br />
<!--T:11--><br />
:Aside from this wiki, which contains lots of information, you can check extensive [[Man|manual pages]] and [http://docs.openvz.org Virtuozzo documentation].<br />
<br />
===== Who needs OpenVZ? How it can be used? ===== <!--T:12--><br />
:See [[Use cases]].<br />
<br />
===== How scalable is OpenVZ? ===== <!--T:13--><br />
<br />
<!--T:14--><br />
OpenVZ technology scales as well as standard Linux kernel — up to thousands of CPUs and terabytes of RAM. Read more about [[WP/Containers_density|OpenVZ containers density]] and [[performance]].<br />
<br />
== Installation and upgrade == <!--T:15--><br />
<br />
===== How to install OpenVZ? ===== <!--T:16--><br />
<br />
<!--T:17--><br />
There are two versions of OpenVZ available:<br />
<br />
<!--T:18--><br />
* [[Roadmap|stable version]]: OpenVZ legacy (based on RHEL5 and RHEL6 kernels).<br />
* [[Roadmap|development version]]: [[Virtuozzo]] Linux distribution based on RHEL7 kernel.<br />
<br />
<!--T:19--><br />
See [[Quick installation]]<br />
<br />
===== What hardware is supported by OpenVZ kernel? ===== <!--T:20--><br />
:See [https://hardware.redhat.com/ RHEL Hardware Compatibility List].<br />
<br />
===== How existing OpenVZ users can upgrade to the [[Virtuozzo|new version]]? ===== <!--T:21--><br />
While there is no in-place upgrade, we prepared [[Upgrade_script_from_OpenVZ_to_Virtuozzo_7|upgrade script]] for OpenVZ users to move their containers to the new platform. The script allows to transfer containers from old to new OpenVZ version (or from OpenVZ to Virtuozzo).<br />
</translate></div>Kirhttps://wiki.openvz.org/index.php?title=News/events/past&diff=22650News/events/past2017-06-06T20:48:23Z<p>Kir: add SCALE15x</p>
<hr />
<div>{{Note|this page lists events that has happened already, kept here just for historical reasons. For future events, see [[News/events]].}}<br />
__TOC__<br />
<br />
== SCALE 15x ==<br />
[[Image:scale 15x logo.png|left|100px|link=]]<br />
<br />
'''March 2-5, 2017, Pasadena, CA, USA'''<br />
<br />
Kir Kolyshkin will tell about [http://www.socallinuxexpo.org/scale/15x/presentations/weird-ways-use-application-checkpointrestore some uncommon ways to use CRIU].<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 20:42, 13 February 2017 (UTC)<br />
<br clear="both"/><br />
<br />
== Virtuozzo Webinar: Cloud Security: Should You Be Worried? ==<br />
'''February 22, 2017'''<br />
<br />
Still wondering if your container data is secure? <br />
<br />
We’ll discuss security risks and data protection threats faced by service providers and their customers today – and what you can do to overcome them. You’ll learn best practices for securing container data, and all about new technologies to keep your data more secure. [https://attendee.gotowebinar.com/recording/288690352883640845 View Recording].<br />
<br />
--[[User:MaryMarks|MaryMarks]] ([[User talk:Mary|talk]]) 10:28, 15 February 2017 (UTC)<br />
<br clear="both"/><br />
<br />
== Presentation DevConf.cz - Painless Userspace Live Patching ==<br />
'''January 29, 2017'''<br />
<br />
Virtuozzo expert Stanislav Kinsburskiy will be discussing “Painless Userspace Live Patching" at DevConf.cz. His talk will touch on technologies like binary analysis, stack unwinding, process manipulation via new library "libcompel", and more.<br />
<br />
[https://devconf.cz/index.html#about DevConf.cz Jan 27-29 Brno, Czech Republic]<br />
<br />
--[[User:Marymarks|Marymarks]] ([[User talk:Marymarks|talk]]) 21:35, 24 January 2017 (UTC)<br />
<br />
== Presentation DevConf.cz - Decreasing container downtime during migration ==<br />
'''January 29, 2017'''<br />
<br />
Adrian Weber, Red Hat Software Developer, will be discussing how CRIU can reduce migration downtime.<br />
<br />
[https://devconf.cz/index.html#about DevConf.cz Jan 27-29 Brno, Czech Republic]<br />
<br />
--[[User:Marymarks|Marymarks]] ([[User talk:Marymarks|talk]]) 21:35, 24 January 2017 (UTC)<br />
<br />
== Presentation FOSDEM.org - OpenVZ containers, how they work and look ==<br />
'''February 4, 2017'''<br />
<br />
Virtuozzo expert Alexander Stefanov will be discussing OpenVZ containers and how Virtuozzo Linux can create lightweight virtual environments.<br />
<br />
[https://fosdem.org/2017/ FOSDEM.org Feb 4-5 Brussels, Belgium]<br />
<br />
--[[User:Marymarks|Marymarks]] ([[User talk:Marymarks|talk]]) 21:35, 24 January 2017 (UTC)<br />
<br />
== Webinar: Getting to Virtuozzo 7 ==<br />
'''December 14, 2016'''<br />
<br />
Learn how to move to the most recent Virtuozzo version and get all the benefits of its new features. This webinar will cover all the possible upgrade options in great technical details. You will also have an opportunity to ask any technical questions you may have. [https://attendee.gotowebinar.com/recording/2531794127555599371 Recording]<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 23:06, 30 November 2016 (UTC)<br />
<br />
== Webinar: What's new in Virtuozzo 7 ==<br />
'''December 7, 2016'''<br />
<br />
Cover the changes and new features of Virtuozzo 7 in great technical details. [https://attendee.gotowebinar.com/recording/1407907426348600067 Recording]<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 23:06, 30 November 2016 (UTC)<br />
<br />
<br />
== SeaGL 2016 ==<br />
[[File:SeaGL.png|left|100px]]<br />
'''Nov 11-12, 2016, Seattle, WA'''<br />
<br />
Kir Kolyshkin will talk about [https://osem.seagl.org/conference/seagl2016/program/proposal/236 Linux containers history].<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 22:08, 23 September 2016 (UTC)<br />
<br clear="both"><br />
== Linux Piter ==<br />
[[File:Linuxpiter.png|left|100px]]<br />
<br />
'''Nov 11-12, 2016, St.Petersburg'''<br />
<br />
Pavel Emelyanov will talk about [http://www.it-events.com/ru/events/6997#tabs-programm containers],<br />
and Tycho Andresen will talk about how LXC/LXD uses CRIU.<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 06:45, 13 October 2016 (UTC)<br />
<br clear="both"><br />
<br />
== Linux Plumbers Conference 2016 ==<br />
[[File:LinuxPlumbers.png|left|100px]]<br />
'''Nov 2-4, 2016, Santa Fe, NM'''<br />
<br />
[https://linuxplumbersconf.org/2016/ocw/events/LPC2016/tracks/519 Containers] and <br />
[https://linuxplumbersconf.org/2016/ocw/events/LPC2016/tracks/567 Checkpoint/restore]<br />
micro-conferences are both part of the Linux Plumbers event.<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 21:59, 23 September 2016 (UTC)<br />
<br clear="both"><br />
<br />
== LinuxCon + ContainerCon North America 2016 ==<br />
[[Image:Linuxcon.png|left|100px]]<br />
<br />
'''August 22-24 2016, Toronto, Canada'''<br />
<br />
Kir Kolyshkin and Andrey Vagin will talk about [http://lcccna2016.sched.org/event/7JWS/time-to-rethink-proc-kirill-kolyshkin-open-vzvirtuozzo?iframe=no&w=&sidebar=yes&bg=no Time to rethink /proc].<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 10:25, 15 June 2016 (EDT)<br />
<br />
<br clear=all><br />
== nginx.conf 2016 ==<br />
[[Image:Nginx-conf-16-logo.png|left|100px]]<br />
<br />
'''September 07-09, 2016, Austin, TX'''<br />
<br />
Pavel Emelyanov will have a [https://www.nginx.com/nginxconf/program/#572353576a0fe82a1a000144 NGINX + Virtuozzo = Love AND Performance].<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 04:57, 23 June 2016 (EDT)<br />
<br />
<br clear=all><br />
== OSDN conference 2016 ==<br />
[[Image:Osdn-logo.png|left|100px]]<br />
<br />
'''Sep 17 2016, Kyiv, Ukraine'''<br />
<br />
Pavel Emelyanov and Sergey Bronnikov will [http://osdn.org.ua/manual/#speakers present] two talks: "Что нового в OpenVZ?" and "Дались вам эти контейнеры!".<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 11:21, 28 July 2016 (EDT)<br />
<br />
<br clear=all><br />
== Texas Linux Fest 2016 ==<br />
[[Image:2016-06-15 13-47-25.png|left|100px]]<br />
<br />
'''July 08-09, 2016, Austin, TX'''<br />
<br />
Kir Kolyshkin will talk about [http://2016.texaslinuxfest.org/node/101 Time to rethink /proc].<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 06:50, 15 June 2016 (EDT)<br />
<br />
<br clear=all><br />
== DockerCon 2016 ==<br />
[[Image:Dockercon16.png|left|100px]]<br />
<br />
'''June 19-21, 2016, Seattle, WA'''<br />
<br />
We will have a booth (S28) there.<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 06:49, 15 June 2016 (EDT)<br />
<br />
<br clear=all><br />
== QA: Conference 2016 ==<br />
[[Image:Qac black.png|left|100px]]<br />
<br />
'''23 Apr 2016, Moscow, Russia'''<br />
<br />
[http://qaconf.ru/speakers.html Continuous Integration in OpenStack development] -- Evgenii Antyshev<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 07:56, 4 March 2016 (EST)<br />
<br />
<br clear=all><br />
== The Linux Storage, Filesystem & Memory Management Summit 2016 ==<br />
[[Image:Lsfmm logo.png|left|100px]]<br />
<br />
'''18-19 April 2016, Raleigh, NC'''<br />
<br />
Attendees from OpenVZ project: Dmitry Monakhov and Vladimir Davydov. See [http://events.linuxfoundation.org/events/linux-storage-filesystem-and-mm-summit program].<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 04:02, 4 March 2016 (EST)<br />
<br />
<br clear=all><br />
== DevConf.cz 2016 ==<br />
[[Image:Devconf.cz-logo.png|left|100px]]<br />
<br />
'''5-7 Feb 2016, Brno, Czech Republic'''<br />
<br />
[https://devconfcz2016.sched.org/event/5lzL/live-migrating-a-container-pros-cons-and-gotchas Live migrating a container: pros, cons and gotchas] -- Pavel Emelyanov<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 13:34, 11 January 2016 (EST)<br />
<br />
<br clear=all><br />
== FOSDEM 2016 ==<br />
[[Image:fosdem-logo.png|left|80px]]<br />
<br />
'''30-31 Jan 2016, Brussels, Belgium'''<br />
<br />
Containers and Process Isolation devroom ([https://www.fosdem.org/2016/schedule/track/containers_and_process_isolation/ schedule])<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 09:41, 21 December 2015 (EST)<br />
<br />
<br clear=all><br />
== Linux Piter 2015 ==<br />
[[Image:Tux.png|left|80px]]<br />
<br />
'''November 21, 2015, Saint Petersburg, Russia'''<br />
<br />
[http://www.it-sobytie.ru/events/4868 Живая миграция контейнеров: плюсы, минусы, подводные камни] -- Pavel Emelyanov<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 17:43, 27 August 2015 (EDT)<br />
<br />
<br clear=all><br />
== ContainerDays NYC 2015 ==<br />
[[Image:2015-nyc-logo.png|left|100px]]<br />
<br />
'''October 30, 2015, New York, U.S.A.'''<br />
<br />
[http://dynamicinfradays.org/events/2015-nyc/programme.html#criu CRIU: Time and Space Travel for Linux Containers] -- by Kirill Kolyshkin<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 00:50, 14 September 2015 (EDT)<br />
<br />
<br clear=all><br />
== OpenStack Summit ==<br />
[[Image:Openstack-summit-logo.svg|left|120px]]<br />
<br />
'''October 27-30, 2015, Tokyo, Japan'''<br />
<br />
Part of OpenVZ Team will attend in [https://www.openstack.org/summit/tokyo-2015/ OpenStack Tokyo]:<br />
Sergey Bronnikov, Dmitry Guryanov (LibVirt, integration with OpenStack), Maxim Nestratov (LibVirt, integration with OpenStack).<br />
You are welcome to contact with us!<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 05:29, 9 September 2015 (EDT)<br />
<br />
== SECR 2015 ==<br />
[[Image:Secr 2015 logo-site.png|left|100px]]<br />
<br />
'''October 22–24 2015, Moscow, Russia'''<br />
<br />
[http://2015.secr.ru/lang/ru/program/submitted-presentations/testing-of-software-based-on-third-party-components-by-the-linux-distribution-example Testing of software based on third party components by the linux distribution example] -- Denis Silakov<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 12:55, 23 September 2015 (EDT)<br />
<br />
== The 12th conference of developers of free software ==<br />
[[Image:Altlinux-logo.gif|left|100px]]<br />
<br />
'''October 16-18, 2015, Kaluga, Russia'''<br />
<br />
[http://www.altlinux.ru/news/archive/2015/08/item/743/ Двенадцатая конференция разработчиков свободных программ]<br />
<br />
Живая миграция контейнеров: плюсы, минусы, подводные камни -- ''Pavel Emelyanov''<br />
<br />
Когда уже OpenVZ будет в основном Linux ядре? -- ''Sergey Bronnikov''<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 08:46, 1 October 2015 (EDT)<br />
<br />
== OpenVZ meetup ==<br />
[[Image:Yandex.png|left|80px]]<br />
<br />
'''September 19, 2015, Moscow, Russia'''<br />
<br />
[https://events.yandex.ru/events/yagosti/19-september-2015-linux/ Встреча разработчиков Linux-контейнеров]<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 06:19, 28 August 2015 (EDT)<br />
<br />
== Linux Plumbers Conference ==<br />
[[Image:LinuxPlumbers.png|left|100px]]<br />
<br />
'''Seattle, WA, USA, August 19-21 2015'''<br />
<br />
Check [https://linuxplumbersconf.org/2015/ocw/events/LPC2015/schedule/ Linux Plumbers Conference] website for more details.<br />
<br clear="both"/><br />
* CGroups kernel memory manager (containers MC), ''by Pavel Emelyanov''<br />
* P.Haul: live migration with CRIU (C/R MC), ''by Pavel Emelyanov''<br />
* Containers in the upstream kernel (containers MC), ''by Kir Kolyshkin''<br />
* C/R status update (containers MC), ''by Andrey Vagin''<br />
* Running Docker inside VZ containers (Plumbers, Containers MC), ''by Maxim Patlasov''<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 11:16, 22 August 2015 (EDT)<br />
<br />
== ContainerCon ==<br />
[[Image:Logo_containercon.png|left|100px]]<br />
'''Seattle, WA, USA, August 17-19 2015'''<br />
<br />
The Linux Foundation is launching a new conference called ContainerCon to bring together leading contributors in Linux containers, the Linux kernel, and related projects to forge a path to continued innovation and education.<br />
<br />
Check [http://events.linuxfoundation.org/events/containercon ContainerCon event page] for more details.<br />
<br />
* Denser containers with PFcache, ''by Pavel Emelyanov''<br />
* A brief history of containers, ''by Kir Kolyshkin''<br />
* Libcontainer: one lib to rule them all, ''by Andrey Vagin''<br />
* Private Cloud is Dead, Long Live Public Cloud, ''by James Bottomley''<br />
* Taking Containers to the Next Level, ''by James Bottomley''<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 01:41, 11 August 2015 (EDT)<br />
<br />
== LVEE 2015 ==<br />
[[File:Lvee_logo_180x174.png|left|100px]]<br />
<br />
'''25-28 June 2015, Grodno, Belarus'''<br />
<br />
[http://lvee.org/ru/conference_registrations/LVEE%202015 "Мифы и легенды о проекте OpenVZ"]<br />
<br />
Sergey Bronnikov will talk about myths around OpenVZ project (in Russian).<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 16:59, 6 June 2015 (EDT)<br />
<br />
== OSday 2015 ==<br />
[[Image:800px-Os-day-logo.png|left|150px]]<br />
<br />
'''Kazan, Russia, June 9-10 2015'''<br />
<br />
[http://osday.org/bronnikov.html#speaker Семь проблем Linux контейнеров]<br />
<br />
Sergey Bronnikov will talk about problems in Linux containers (in Russian).<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 14:23, 19 May 2015 (EDT)<br />
<br clear="both"/><br />
<br />
== ContainerDays 2015 ==<br />
[[Image:Logo-ContainerDays.png|left|150px]]<br />
<br />
'''Boston, MA, USA, June 5-6 2015'''<br />
<br />
ContainerDays Boston is a community (un)conference to encourage discussion and learning on the subject of containers and dynamic infrastructure generally. The programme is a mix of OpenSpaces sessions and talks from users, contributors and extenders from all corners of the space.<br />
<br />
Kir Kolyshkin from OpenVZ project will give a talk [http://dynamicinfradays.org/events/2015-boston/programme.html#nproblems "N Problems of Linux Containers...and Some Solutions"].<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 05:26, 12 May 2015 (EDT)<br />
<br clear="both"/><br />
<br />
== LinuxFest Northwest 2015 ==<br />
[[Image:Linuxfestnorthwest.jpg|left|100px]]<br />
'''Bellingham, WA, USA, April 25-26 2015'''<br />
<br />
Kir Kolyshkin is signed up to give a [http://linuxfestnorthwest.org/2015/sessions/openvz-virtuozzo-core-and-docker presentation on OpenVZ, Virtuozzo Core and Docker].<br />
<br />
Check [http://linuxfestnorthwest.org/ linuxfestnorthwest.org] for more details.<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 19:25, 22 March 2015 (EDT)<br />
<br />
<br clear="both"/><br />
== Linux Plumbers ==<br />
[[Image:LinuxPlumbers.png|left|100px]]<br />
<br />
'''October 15-17, 2014, Dusseldorf, Germany'''<br />
<br />
Slides [http://www.linuxplumbersconf.org/2014/ocw/proposals/1959 Are containers that we have now secure enough?]<br />
<br />
[http://www.linuxplumbersconf.org/2014/an-in-depth-look-containers-microconference/ Containers mini-conf ] -- Pavel Emelyanov, Kir Kolyshkin<noinclude><br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 11:58, 6 June 2014 (EDT)<br />
<br />
<br clear="both"/><br />
== LinuxCon ==<br />
[[Image:Linuxcon.png|left|100px]]<br />
<br />
'''August 20 - 22, 2014, Chicago, IL, USA'''<br />
<br />
[http://sched.co/1r2OMI2 Containers in Linux: Current State and Where We're Going] - James Bottomley<noinclude><br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 13:50, 15 August 2014 (EDT)<br />
<br />
<br clear="both"/><br />
== Open WG talk ==<br />
[[Image:WGtalk.png|left|100px]]<br />
<br />
'''Friday, July 18, 2014, Minsk, Belarus'''<br />
<br />
[https://www.eventbrite.com/e/open-wg-talk-2-linux-container-virtualization-tickets-12189971533?fb_action_ids=705517169505083&fb_action_types=og.likes&fb_source=feed_opengraph&action_object_map=%7B%22705517169505083%22%3A753726634669877%7D&action_type_map=%7B%22705517169505083%22%3A%22og.likes%22%7D&action_ref_map=%5B%5D Open WG Talk -- Linux container virtualization] -- Andrey Vagin, Konstantin Khorenko<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 14:47, 9 July 2014 (EDT)<br />
<br />
<br clear="both"><br />
== Texas Linux Fest ==<br />
[[Image:Txlf2014.png|left|100px]]<br />
<br />
'''June 13-14, 2014, Austin, Texas, US'''<br />
<br />
[https://2014.texaslinuxfest.org/content/criu-time-and-space-travel-service-linux-apps.html CRIU: time and space travel service for Linux apps] -- Kir Kolyshkin<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 11:56, 6 June 2014 (EDT)<br />
<br />
<br clear="both"><br />
<br />
== OpenVZ talk at SCALE12x ==<br />
[[Image:Scale-12x.png|left|120px|link=http://www.socallinuxexpo.org/scale12x]]<br />
<br />
'''21-23 February, 2014. Los Angeles, CA, USA'''<br />
<br />
[https://www.socallinuxexpo.org/scale12x/presentations/seven-problems-linux-containers Seven Problems of Linux Containers], Feb 23, 13:30 to 14:30.<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 14:05, 24 January 2014 (EST)<br />
<br />
<br clear="both"><br />
== CRIU talk at SCALE11x ==<br />
[[Image:Scale-11x.png|left|link=http://www.socallinuxexpo.org/scale11x]]<br />
'''22-24 February, 2013. Los Angeles, CA, USA'''<br />
<br />
[http://www.socallinuxexpo.org/scale11x/presentations/checkpoint-restore-live-migration-and-beyond Checkpoint, Restore, Live Migration and Beyond - Kir Kolyshkin]<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 12:10, 23 January 2013 (EST)<br />
<br />
<br clear="both"><br />
== CRIU talk at linux.conf.au ==<br />
[[Image:Linux-conf-au-2013.jpg|left|link=https://lca2013.linux.org.au/]]<br />
'''28 January to 2 February, 2013. Canberra, Australia'''<br />
<br />
[https://lca2013.linux.org.au/schedule/30116/view_talk?day=thursday Checkpoint and Restore: Are We There Yet? - Pavel Emelyanov]<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 14:31, 17 December 2012 (EST)<br />
<br />
<br clear="both"><br />
== CRIU talk at FOSDEM ==<br />
[[Image:Fosdem-2013.png|left|link=https://fosdem.org/2013/]]<br />
'''2 and 3 February, 2013. Brussels, Belgium'''<br />
<br />
[https://fosdem.org/2013/schedule/event/criu_ckeckpoint_restore/ CRIU: Checkpoint and Restore (mostly) In Userspace - Andrey Vagin]<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 20:57, 22 January 2013 (EST)<br />
<br clear="both"><br />
<br />
<br />
== CRIU talk at YAC 2012 ==<br />
<br />
1 Oct 2012, Moscow, Russia || [http://events.yandex.ru/events/yac/2012/ YAC 2012]<br />
<br />
Kir Kolyshkin and Pavel Emelyanov will talk about CRIU project. CRIU is an implementation of checkpoint/restore mechanism for Linux which<br />
is mostly performed in userspace. An in-kernel OpenVZ implementation of checkpoint/restore will eventually be replaced by CRIU.<br />
<br clear="both"/><br />
== Container mini-summit at Linux Plumbers ==<br />
[[File:LinuxPlumbers.png|left|80px]]<br />
''San Diego, CA, USA, 29 Aug 2012''<br />
<br />
Discussed various topics on containers and resource management. See more at [http://summit.linuxplumbersconf.org/lpc-2012/meeting/116/lpc2012-cont-cgroups/].<br />
<br />
<br clear="both"/><br />
== Southern California Linux Expo ==<br />
[[File:Scale 10x 1.gif|left]]<br />
''Los Angeles, CA, 20-23 Jan 2012''<br />
<br />
OpenVZ will present itself at booth #54. Also, Kir Kolyshkin and Andrey Vagin will deliver a talk titled "Reinventing Linux loopback device" dedicated to a new ploop technology currently being developed. See more at [http://www.socallinuxexpo.org/scale10x/openvz] and [http://www.socallinuxexpo.org/scale10x/presentations/reinventing-linux-loopback-device-clouds].<br />
<br clear="both"/><br />
<br />
== FOSDEM 2012 ==<br />
[[File:Fosdem.png|left]]<br />
''Brussels, Belgium, 4-5 Feb 2012''<br />
<br />
OpenVZ will present a talk titled "Linux Containers and OpenVZ", see more at [http://fosdem.org/2012/schedule/event/hypervisors_openvz].<br />
<br clear="both"/><br />
<br />
== LinuxCon Europe 2011 ==<br />
[[File:Linuxcon.png|left]]<br />
''Prague, Czech, Oct 23 - 25, 2011''<br />
<br />
OpenVZ project manager, kernel team leader, and three kernel developers will be at LinuxCon. Two talks -- "Container in a file" about a new loop-like file system to store containers (Wed 11:45), and "OpenVZ and Linux Kernel testing" about our QA experience (Fri 16:45)-- will be presented. See more at the [http://events.linuxfoundation.org/events/linuxcon-europe Linux Con Europe site]. <br />
<br clear="both"/><br />
<br />
== Linux Plumbers Conference 2011 == <br />
[[File:LinuxPlumbers.png|left|80px]]<br />
''Santa Rosa, CA, USA, September 7-9, 2011''<br />
<br />
The conference includes Containers and CGroups mini-summit, during which we want to discuss a few interesting topics. See more at [http://blog.openvz.org/38447.html openvz blog].<br />
<br clear="both"/><br />
== LinuxSymposium 2010 ==<br />
''Ottawa, Canada, 13-16 July 2010''<br />
<br />
Kir Kolyshkin presented a two-hour tutorial about using OpenVZ.<br />
<br />
== LinuxTag 2010 ==<br />
[[File:LinuxTag.gif|left]]<br />
''Berlin, Germany, 9-12 June 2010''<br />
<br />
OpenVZ had a booth.<br />
<br />
<br clear="both"/><br />
== Linux Foundation Collaboration Summit ==<br />
[[File:Linux foundation collaboration summit-logo.png|left]]<br />
''San Francisco, CA, Apr 14-16 2010''<br/><br />
<br />
Kir Kolyshkin will deliver a talk titled "Containers and Namespaces in the Linux Kernel" during the Virtualization track.<br />
<br />
<br clear="both"/><br />
== Southern California Linux Expo aka SCALE 8x ==<br />
''Los Angeles, CA, Feb 19-21 2010''<br/><br />
[[File:SCALE8x.gif|left]]<br />
<br />
Kir Kolyshkin will be there presenting an OpenVZ booth.<br />
<br />
<br clear="both"/><br />
<br />
== Utah Open Source Conference 2009 ==<br />
''Sandy, Utah, USA, 8-10 Oct, 2009''<br/><br />
[[Image:UTOCS2009.png|left]]<br />
Scott Dowdle will host an OpenVZ booth, plus will also be giving a presentation entitled [http://2009.utosc.com/presentation/52/ Introduction to OS Virtualization, Containers, and OpenVZ].<br />
<br />
<br clear="both"/><br />
== LinuxTag 2009 ==<br />
''Berlin, Germany, June 24-27, 2009''<br/><br />
[[Image:LinuxTag.gif|left]]<br />
OpenVZ project will have a booth at this year's LinuxTag -- one of the biggest and greatest Linux shows in Germany.<br />
<br />
<br clear="both"/><br />
== Linux Symposium 2009 ==<br />
''Montreal, Canada, July 13-17 2009''<br/><br />
[[Image:Linux symposium 09.png|left]]<br />
It's a third time OpenVZ takes part in Linux Symposium, and a first time it's being held in Montreal! The project will present a [http://www.linuxsymposium.org/2009/view_abstract.php?content_key=31 tutorial on installing/using OpenVZ], and [http://www.linuxsymposium.org/2009/view_abstract.php?content_key=32 a BoF for OpenVZ users and developers].<br />
<br clear="both"/><br />
<hr color="#ddcef2"/><br />
<br />
== Southern California Linux Expo 2008 ==<br />
[[Image:Scale7x.gif|left]]<br />
''Los Angeles, USA, February 20-22, 2009''<br />
<br />
OpenVZ project will have a booth, plus Kir Kolyshkin will deliver [http://scale7x.socallinuxexpo.org/conference-info/speakers/kir-kolyshkin a talk] titled "Recent Advances in the Linux Kernel Resource Management"<br />
<br clear="both"/><br />
<hr color="#ddcef2"/><br />
<br />
[[Image:LinuxWorld logo.gif|left|180px]]<br />
== LinuxWorld Expo ==<br />
''San Francisco, California, USA, August 5-7, 2008''<br />
<br />
OpenVZ project will have a booth at the .org Pavilion at the upcoming [http://www.linuxworldexpo.com/live/12 LinuxWorld Conference and Expo 2008]. Plus, project leader Kir Kolyshkin will deliver [http://www.linuxworldexpo.com/live/12/conference//tracks/tracksessions/Virtualization/QMONYB00BHXK a talk titled "Containers, Virtualization, and Live Migration"].<br />
<br clear="both"/><br />
<hr color="#ddcef2"/><br />
<br />
[[Image: Scale6x.gif|left|100px]]<br />
== Southern California Linux Expo ==<br />
''Los Angeles, USA, February 8-10, 2008''<br />
<br />
OpenVZ will have a booth at the show, plus Kir Kolyshkin and Andrey Mirkin will present a talk titled "Containers Checkpointing and Live Migration".<br />
<br />
For more details, check [http://socallinuxexpo.com/ socallinuxexpo.com].<br />
<br clear="both"/><br />
<hr color="#ddcef2"/><br />
<br />
[[Image:FLoridaLinuxshow2.jpg|left|100px]]<br />
== Florida Linux Show ==<br />
''Jacksonville, FL, USA, February 11, 2008''<br />
<br />
Kir Kolyshkin will present an introductory talk about OpenVZ.<br />
<br />
For more details, check [http://www.floridalinuxshow.com/ floridalinuxshow.com].<br />
<br clear="both"/><br />
<hr color="#ddcef2"/><br />
<br />
[[Image:Linuxfestnorthwest.jpg|left|100px]]<br />
== LinuxFest Northwest ==<br />
'' Bellingham, WA, USA, April 26 and 27, 2008''<br />
<br />
Scott Dowdle is signed up to give a presentation on OpenVZ and OS virtualization.<br />
<br />
Check [http://linuxfestnorthwest.org/ linuxfestnorthwest.org] for more details.<br />
<br clear="both"/><br />
<hr color="#ddcef2"/><br />
<br />
[[Image:Linux Symposium 2008.gif|left|180px]]<br />
== Linux Symposium and Containers mini-summit==<br />
''Ottawa, Canada, July 23-26, 2008''<br />
<br />
[[Containers/Mini-summit 2008|Containers mini-summit]] will take place 22nd of July 2008, just before the conference. See [[Containers/Mini-summit 2008]] for more info.<br />
<br />
At the Linux Symposium, our kernel developer [http://www.linuxsymposium.org/2008/view_bio.php?id=3175 Andrey Mirkin] will present [http://www.linuxsymposium.org/2008/view_abstract.php?content_key=17 a talk titled "Containers Checkpointing and Live Migration"].<br />
<br clear="both"/><br />
<hr color="#ddcef2"/><br />
<br />
[[Image:LinuxWorld logo.gif|left|180px]]<br />
== LinuxWorld Expo ==<br />
''San Francisco, California, USA, August 5-7, 2008''<br />
<br />
OpenVZ project will have a booth at the .org Pavilion at the upcoming [http://www.linuxworldexpo.com/live/12 LinuxWorld Conference and Expo 2008]. Plus, project leader Kir Kolyshkin will deliver [http://www.linuxworldexpo.com/live/12/conference//tracks/tracksessions/Virtualization/QMONYB00BHXK a talk titled "Containers, Virtualization, and Live Migration"].<br />
<br />
[[Category:Events]]</div>Kirhttps://wiki.openvz.org/index.php?title=News/events&diff=22649News/events2017-06-06T20:48:14Z<p>Kir: moved to past</p>
<hr />
<div><noinclude> __NOTOC__<br />
<!--<br />
This page is<br />
1. used directly (i.e. one can view it);<br />
2. included into some other pages (such as [[Template:News block 2]]);<br />
3. exported via RSS.<br />
Because of that, extreme care should be taken when modifying it. --~~~~<br />
<br />
>>> PLEASE MAKE SURE MOST RECENT EVENTS GO FIRST <<<<br />
<br />
--><br />
<startFeed/><br />
</noinclude><br />
<br />
<noinclude><br />
<endFeed/><br />
<br />
== See also ==<br />
* [[/past|Past events]]<br />
<br />
[[Category:Events]]<br />
</noinclude></div>Kirhttps://wiki.openvz.org/index.php?title=MediaWiki:Sitenotice&diff=22607MediaWiki:Sitenotice2017-04-12T03:24:29Z<p>Kir: kill the banner</p>
<hr />
<div></div>Kirhttps://wiki.openvz.org/index.php?title=User:Chl&diff=22572User:Chl2017-03-18T17:18:23Z<p>Kir: Creating user page for new user.</p>
<hr />
<div>Simple OpenVZ & Container enthusiast (hum, that should count as 4-5 words, I need something to fill the "at least 20 words" biography in order to complete my account request. Well... Dolor sit amet)</div>Kirhttps://wiki.openvz.org/index.php?title=User:Kae&diff=22567User:Kae2017-03-07T20:37:16Z<p>Kir: Creating user page for new user.</p>
<hr />
<div>BigData, virtuoso, open stack, Bitname, das sind die Themen.<br />
DB Mongo, Cassandra, OrientDB das sind die DB's<br />
SMACK, Ansible, DC/OS, MAAS, das sind BS</div>Kirhttps://wiki.openvz.org/index.php?title=News/events&diff=22558News/events2017-03-03T20:11:32Z<p>Kir: rm extra empty line</p>
<hr />
<div><noinclude> __NOTOC__<br />
<!--<br />
This page is<br />
1. used directly (i.e. one can view it);<br />
2. included into some other pages (such as [[Template:News block 2]]);<br />
3. exported via RSS.<br />
Because of that, extreme care should be taken when modifying it. --~~~~<br />
<br />
>>> PLEASE MAKE SURE MOST RECENT EVENTS GO FIRST <<<<br />
<br />
--><br />
<startFeed/><br />
</noinclude><br />
== SCALE 15x ==<br />
[[Image:scale 15x logo.png|left|100px|link=]]<br />
<br />
'''March 2-5, 2017, Pasadena, CA, USA'''<br />
<br />
Kir Kolyshkin will tell about [http://www.socallinuxexpo.org/scale/15x/presentations/weird-ways-use-application-checkpointrestore some uncommon ways to use CRIU].<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 20:42, 13 February 2017 (UTC)<br />
<br clear="both"/><br />
<noinclude><br />
<endFeed/><br />
<br />
== See also ==<br />
* [[/past|Past events]]<br />
<br />
[[Category:Events]]<br />
</noinclude></div>Kirhttps://wiki.openvz.org/index.php?title=News/events&diff=22557News/events2017-03-03T20:10:16Z<p>Kir: moved event to past</p>
<hr />
<div><noinclude> __NOTOC__<br />
<!--<br />
This page is<br />
1. used directly (i.e. one can view it);<br />
2. included into some other pages (such as [[Template:News block 2]]);<br />
3. exported via RSS.<br />
Because of that, extreme care should be taken when modifying it. --~~~~<br />
<br />
>>> PLEASE MAKE SURE MOST RECENT EVENTS GO FIRST <<<<br />
<br />
--><br />
<startFeed/><br />
</noinclude><br />
<br />
== SCALE 15x ==<br />
[[Image:scale 15x logo.png|left|100px|link=]]<br />
<br />
'''March 2-5, 2017, Pasadena, CA, USA'''<br />
<br />
Kir Kolyshkin will tell about [http://www.socallinuxexpo.org/scale/15x/presentations/weird-ways-use-application-checkpointrestore some uncommon ways to use CRIU].<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 20:42, 13 February 2017 (UTC)<br />
<br clear="both"/><br />
<noinclude><br />
<endFeed/><br />
<br />
== See also ==<br />
* [[/past|Past events]]<br />
<br />
[[Category:Events]]<br />
</noinclude></div>Kirhttps://wiki.openvz.org/index.php?title=News/events/past&diff=22556News/events/past2017-03-03T20:10:07Z<p>Kir: moved past event</p>
<hr />
<div>{{Note|this page lists events that has happened already, kept here just for historical reasons. For future events, see [[News/events]].}}<br />
__TOC__<br />
<br />
== Virtuozzo Webinar: Cloud Security: Should You Be Worried? ==<br />
'''February 22, 2017'''<br />
<br />
Still wondering if your container data is secure? <br />
<br />
We’ll discuss security risks and data protection threats faced by service providers and their customers today – and what you can do to overcome them. You’ll learn best practices for securing container data, and all about new technologies to keep your data more secure. [https://attendee.gotowebinar.com/recording/288690352883640845 View Recording].<br />
<br />
--[[User:MaryMarks|MaryMarks]] ([[User talk:Mary|talk]]) 10:28, 15 February 2017 (UTC)<br />
<br clear="both"/><br />
<br />
== Presentation DevConf.cz - Painless Userspace Live Patching ==<br />
'''January 29, 2017'''<br />
<br />
Virtuozzo expert Stanislav Kinsburskiy will be discussing “Painless Userspace Live Patching" at DevConf.cz. His talk will touch on technologies like binary analysis, stack unwinding, process manipulation via new library "libcompel", and more.<br />
<br />
[https://devconf.cz/index.html#about DevConf.cz Jan 27-29 Brno, Czech Republic]<br />
<br />
--[[User:Marymarks|Marymarks]] ([[User talk:Marymarks|talk]]) 21:35, 24 January 2017 (UTC)<br />
<br />
== Presentation DevConf.cz - Decreasing container downtime during migration ==<br />
'''January 29, 2017'''<br />
<br />
Adrian Weber, Red Hat Software Developer, will be discussing how CRIU can reduce migration downtime.<br />
<br />
[https://devconf.cz/index.html#about DevConf.cz Jan 27-29 Brno, Czech Republic]<br />
<br />
--[[User:Marymarks|Marymarks]] ([[User talk:Marymarks|talk]]) 21:35, 24 January 2017 (UTC)<br />
<br />
== Presentation FOSDEM.org - OpenVZ containers, how they work and look ==<br />
'''February 4, 2017'''<br />
<br />
Virtuozzo expert Alexander Stefanov will be discussing OpenVZ containers and how Virtuozzo Linux can create lightweight virtual environments.<br />
<br />
[https://fosdem.org/2017/ FOSDEM.org Feb 4-5 Brussels, Belgium]<br />
<br />
--[[User:Marymarks|Marymarks]] ([[User talk:Marymarks|talk]]) 21:35, 24 January 2017 (UTC)<br />
<br />
== Webinar: Getting to Virtuozzo 7 ==<br />
'''December 14, 2016'''<br />
<br />
Learn how to move to the most recent Virtuozzo version and get all the benefits of its new features. This webinar will cover all the possible upgrade options in great technical details. You will also have an opportunity to ask any technical questions you may have. [https://attendee.gotowebinar.com/recording/2531794127555599371 Recording]<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 23:06, 30 November 2016 (UTC)<br />
<br />
== Webinar: What's new in Virtuozzo 7 ==<br />
'''December 7, 2016'''<br />
<br />
Cover the changes and new features of Virtuozzo 7 in great technical details. [https://attendee.gotowebinar.com/recording/1407907426348600067 Recording]<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 23:06, 30 November 2016 (UTC)<br />
<br />
<br />
== SeaGL 2016 ==<br />
[[File:SeaGL.png|left|100px]]<br />
'''Nov 11-12, 2016, Seattle, WA'''<br />
<br />
Kir Kolyshkin will talk about [https://osem.seagl.org/conference/seagl2016/program/proposal/236 Linux containers history].<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 22:08, 23 September 2016 (UTC)<br />
<br clear="both"><br />
== Linux Piter ==<br />
[[File:Linuxpiter.png|left|100px]]<br />
<br />
'''Nov 11-12, 2016, St.Petersburg'''<br />
<br />
Pavel Emelyanov will talk about [http://www.it-events.com/ru/events/6997#tabs-programm containers],<br />
and Tycho Andresen will talk about how LXC/LXD uses CRIU.<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 06:45, 13 October 2016 (UTC)<br />
<br clear="both"><br />
<br />
== Linux Plumbers Conference 2016 ==<br />
[[File:LinuxPlumbers.png|left|100px]]<br />
'''Nov 2-4, 2016, Santa Fe, NM'''<br />
<br />
[https://linuxplumbersconf.org/2016/ocw/events/LPC2016/tracks/519 Containers] and <br />
[https://linuxplumbersconf.org/2016/ocw/events/LPC2016/tracks/567 Checkpoint/restore]<br />
micro-conferences are both part of the Linux Plumbers event.<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 21:59, 23 September 2016 (UTC)<br />
<br clear="both"><br />
<br />
== LinuxCon + ContainerCon North America 2016 ==<br />
[[Image:Linuxcon.png|left|100px]]<br />
<br />
'''August 22-24 2016, Toronto, Canada'''<br />
<br />
Kir Kolyshkin and Andrey Vagin will talk about [http://lcccna2016.sched.org/event/7JWS/time-to-rethink-proc-kirill-kolyshkin-open-vzvirtuozzo?iframe=no&w=&sidebar=yes&bg=no Time to rethink /proc].<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 10:25, 15 June 2016 (EDT)<br />
<br />
<br clear=all><br />
== nginx.conf 2016 ==<br />
[[Image:Nginx-conf-16-logo.png|left|100px]]<br />
<br />
'''September 07-09, 2016, Austin, TX'''<br />
<br />
Pavel Emelyanov will have a [https://www.nginx.com/nginxconf/program/#572353576a0fe82a1a000144 NGINX + Virtuozzo = Love AND Performance].<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 04:57, 23 June 2016 (EDT)<br />
<br />
<br clear=all><br />
== OSDN conference 2016 ==<br />
[[Image:Osdn-logo.png|left|100px]]<br />
<br />
'''Sep 17 2016, Kyiv, Ukraine'''<br />
<br />
Pavel Emelyanov and Sergey Bronnikov will [http://osdn.org.ua/manual/#speakers present] two talks: "Что нового в OpenVZ?" and "Дались вам эти контейнеры!".<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 11:21, 28 July 2016 (EDT)<br />
<br />
<br clear=all><br />
== Texas Linux Fest 2016 ==<br />
[[Image:2016-06-15 13-47-25.png|left|100px]]<br />
<br />
'''July 08-09, 2016, Austin, TX'''<br />
<br />
Kir Kolyshkin will talk about [http://2016.texaslinuxfest.org/node/101 Time to rethink /proc].<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 06:50, 15 June 2016 (EDT)<br />
<br />
<br clear=all><br />
== DockerCon 2016 ==<br />
[[Image:Dockercon16.png|left|100px]]<br />
<br />
'''June 19-21, 2016, Seattle, WA'''<br />
<br />
We will have a booth (S28) there.<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 06:49, 15 June 2016 (EDT)<br />
<br />
<br clear=all><br />
== QA: Conference 2016 ==<br />
[[Image:Qac black.png|left|100px]]<br />
<br />
'''23 Apr 2016, Moscow, Russia'''<br />
<br />
[http://qaconf.ru/speakers.html Continuous Integration in OpenStack development] -- Evgenii Antyshev<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 07:56, 4 March 2016 (EST)<br />
<br />
<br clear=all><br />
== The Linux Storage, Filesystem & Memory Management Summit 2016 ==<br />
[[Image:Lsfmm logo.png|left|100px]]<br />
<br />
'''18-19 April 2016, Raleigh, NC'''<br />
<br />
Attendees from OpenVZ project: Dmitry Monakhov and Vladimir Davydov. See [http://events.linuxfoundation.org/events/linux-storage-filesystem-and-mm-summit program].<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 04:02, 4 March 2016 (EST)<br />
<br />
<br clear=all><br />
== DevConf.cz 2016 ==<br />
[[Image:Devconf.cz-logo.png|left|100px]]<br />
<br />
'''5-7 Feb 2016, Brno, Czech Republic'''<br />
<br />
[https://devconfcz2016.sched.org/event/5lzL/live-migrating-a-container-pros-cons-and-gotchas Live migrating a container: pros, cons and gotchas] -- Pavel Emelyanov<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 13:34, 11 January 2016 (EST)<br />
<br />
<br clear=all><br />
== FOSDEM 2016 ==<br />
[[Image:fosdem-logo.png|left|80px]]<br />
<br />
'''30-31 Jan 2016, Brussels, Belgium'''<br />
<br />
Containers and Process Isolation devroom ([https://www.fosdem.org/2016/schedule/track/containers_and_process_isolation/ schedule])<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 09:41, 21 December 2015 (EST)<br />
<br />
<br clear=all><br />
== Linux Piter 2015 ==<br />
[[Image:Tux.png|left|80px]]<br />
<br />
'''November 21, 2015, Saint Petersburg, Russia'''<br />
<br />
[http://www.it-sobytie.ru/events/4868 Живая миграция контейнеров: плюсы, минусы, подводные камни] -- Pavel Emelyanov<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 17:43, 27 August 2015 (EDT)<br />
<br />
<br clear=all><br />
== ContainerDays NYC 2015 ==<br />
[[Image:2015-nyc-logo.png|left|100px]]<br />
<br />
'''October 30, 2015, New York, U.S.A.'''<br />
<br />
[http://dynamicinfradays.org/events/2015-nyc/programme.html#criu CRIU: Time and Space Travel for Linux Containers] -- by Kirill Kolyshkin<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 00:50, 14 September 2015 (EDT)<br />
<br />
<br clear=all><br />
== OpenStack Summit ==<br />
[[Image:Openstack-summit-logo.svg|left|120px]]<br />
<br />
'''October 27-30, 2015, Tokyo, Japan'''<br />
<br />
Part of OpenVZ Team will attend in [https://www.openstack.org/summit/tokyo-2015/ OpenStack Tokyo]:<br />
Sergey Bronnikov, Dmitry Guryanov (LibVirt, integration with OpenStack), Maxim Nestratov (LibVirt, integration with OpenStack).<br />
You are welcome to contact with us!<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 05:29, 9 September 2015 (EDT)<br />
<br />
== SECR 2015 ==<br />
[[Image:Secr 2015 logo-site.png|left|100px]]<br />
<br />
'''October 22–24 2015, Moscow, Russia'''<br />
<br />
[http://2015.secr.ru/lang/ru/program/submitted-presentations/testing-of-software-based-on-third-party-components-by-the-linux-distribution-example Testing of software based on third party components by the linux distribution example] -- Denis Silakov<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 12:55, 23 September 2015 (EDT)<br />
<br />
== The 12th conference of developers of free software ==<br />
[[Image:Altlinux-logo.gif|left|100px]]<br />
<br />
'''October 16-18, 2015, Kaluga, Russia'''<br />
<br />
[http://www.altlinux.ru/news/archive/2015/08/item/743/ Двенадцатая конференция разработчиков свободных программ]<br />
<br />
Живая миграция контейнеров: плюсы, минусы, подводные камни -- ''Pavel Emelyanov''<br />
<br />
Когда уже OpenVZ будет в основном Linux ядре? -- ''Sergey Bronnikov''<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 08:46, 1 October 2015 (EDT)<br />
<br />
== OpenVZ meetup ==<br />
[[Image:Yandex.png|left|80px]]<br />
<br />
'''September 19, 2015, Moscow, Russia'''<br />
<br />
[https://events.yandex.ru/events/yagosti/19-september-2015-linux/ Встреча разработчиков Linux-контейнеров]<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 06:19, 28 August 2015 (EDT)<br />
<br />
== Linux Plumbers Conference ==<br />
[[Image:LinuxPlumbers.png|left|100px]]<br />
<br />
'''Seattle, WA, USA, August 19-21 2015'''<br />
<br />
Check [https://linuxplumbersconf.org/2015/ocw/events/LPC2015/schedule/ Linux Plumbers Conference] website for more details.<br />
<br clear="both"/><br />
* CGroups kernel memory manager (containers MC), ''by Pavel Emelyanov''<br />
* P.Haul: live migration with CRIU (C/R MC), ''by Pavel Emelyanov''<br />
* Containers in the upstream kernel (containers MC), ''by Kir Kolyshkin''<br />
* C/R status update (containers MC), ''by Andrey Vagin''<br />
* Running Docker inside VZ containers (Plumbers, Containers MC), ''by Maxim Patlasov''<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 11:16, 22 August 2015 (EDT)<br />
<br />
== ContainerCon ==<br />
[[Image:Logo_containercon.png|left|100px]]<br />
'''Seattle, WA, USA, August 17-19 2015'''<br />
<br />
The Linux Foundation is launching a new conference called ContainerCon to bring together leading contributors in Linux containers, the Linux kernel, and related projects to forge a path to continued innovation and education.<br />
<br />
Check [http://events.linuxfoundation.org/events/containercon ContainerCon event page] for more details.<br />
<br />
* Denser containers with PFcache, ''by Pavel Emelyanov''<br />
* A brief history of containers, ''by Kir Kolyshkin''<br />
* Libcontainer: one lib to rule them all, ''by Andrey Vagin''<br />
* Private Cloud is Dead, Long Live Public Cloud, ''by James Bottomley''<br />
* Taking Containers to the Next Level, ''by James Bottomley''<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 01:41, 11 August 2015 (EDT)<br />
<br />
== LVEE 2015 ==<br />
[[File:Lvee_logo_180x174.png|left|100px]]<br />
<br />
'''25-28 June 2015, Grodno, Belarus'''<br />
<br />
[http://lvee.org/ru/conference_registrations/LVEE%202015 "Мифы и легенды о проекте OpenVZ"]<br />
<br />
Sergey Bronnikov will talk about myths around OpenVZ project (in Russian).<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 16:59, 6 June 2015 (EDT)<br />
<br />
== OSday 2015 ==<br />
[[Image:800px-Os-day-logo.png|left|150px]]<br />
<br />
'''Kazan, Russia, June 9-10 2015'''<br />
<br />
[http://osday.org/bronnikov.html#speaker Семь проблем Linux контейнеров]<br />
<br />
Sergey Bronnikov will talk about problems in Linux containers (in Russian).<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 14:23, 19 May 2015 (EDT)<br />
<br clear="both"/><br />
<br />
== ContainerDays 2015 ==<br />
[[Image:Logo-ContainerDays.png|left|150px]]<br />
<br />
'''Boston, MA, USA, June 5-6 2015'''<br />
<br />
ContainerDays Boston is a community (un)conference to encourage discussion and learning on the subject of containers and dynamic infrastructure generally. The programme is a mix of OpenSpaces sessions and talks from users, contributors and extenders from all corners of the space.<br />
<br />
Kir Kolyshkin from OpenVZ project will give a talk [http://dynamicinfradays.org/events/2015-boston/programme.html#nproblems "N Problems of Linux Containers...and Some Solutions"].<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 05:26, 12 May 2015 (EDT)<br />
<br clear="both"/><br />
<br />
== LinuxFest Northwest 2015 ==<br />
[[Image:Linuxfestnorthwest.jpg|left|100px]]<br />
'''Bellingham, WA, USA, April 25-26 2015'''<br />
<br />
Kir Kolyshkin is signed up to give a [http://linuxfestnorthwest.org/2015/sessions/openvz-virtuozzo-core-and-docker presentation on OpenVZ, Virtuozzo Core and Docker].<br />
<br />
Check [http://linuxfestnorthwest.org/ linuxfestnorthwest.org] for more details.<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 19:25, 22 March 2015 (EDT)<br />
<br />
<br clear="both"/><br />
== Linux Plumbers ==<br />
[[Image:LinuxPlumbers.png|left|100px]]<br />
<br />
'''October 15-17, 2014, Dusseldorf, Germany'''<br />
<br />
Slides [http://www.linuxplumbersconf.org/2014/ocw/proposals/1959 Are containers that we have now secure enough?]<br />
<br />
[http://www.linuxplumbersconf.org/2014/an-in-depth-look-containers-microconference/ Containers mini-conf ] -- Pavel Emelyanov, Kir Kolyshkin<noinclude><br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 11:58, 6 June 2014 (EDT)<br />
<br />
<br clear="both"/><br />
== LinuxCon ==<br />
[[Image:Linuxcon.png|left|100px]]<br />
<br />
'''August 20 - 22, 2014, Chicago, IL, USA'''<br />
<br />
[http://sched.co/1r2OMI2 Containers in Linux: Current State and Where We're Going] - James Bottomley<noinclude><br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 13:50, 15 August 2014 (EDT)<br />
<br />
<br clear="both"/><br />
== Open WG talk ==<br />
[[Image:WGtalk.png|left|100px]]<br />
<br />
'''Friday, July 18, 2014, Minsk, Belarus'''<br />
<br />
[https://www.eventbrite.com/e/open-wg-talk-2-linux-container-virtualization-tickets-12189971533?fb_action_ids=705517169505083&fb_action_types=og.likes&fb_source=feed_opengraph&action_object_map=%7B%22705517169505083%22%3A753726634669877%7D&action_type_map=%7B%22705517169505083%22%3A%22og.likes%22%7D&action_ref_map=%5B%5D Open WG Talk -- Linux container virtualization] -- Andrey Vagin, Konstantin Khorenko<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 14:47, 9 July 2014 (EDT)<br />
<br />
<br clear="both"><br />
== Texas Linux Fest ==<br />
[[Image:Txlf2014.png|left|100px]]<br />
<br />
'''June 13-14, 2014, Austin, Texas, US'''<br />
<br />
[https://2014.texaslinuxfest.org/content/criu-time-and-space-travel-service-linux-apps.html CRIU: time and space travel service for Linux apps] -- Kir Kolyshkin<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 11:56, 6 June 2014 (EDT)<br />
<br />
<br clear="both"><br />
<br />
== OpenVZ talk at SCALE12x ==<br />
[[Image:Scale-12x.png|left|120px|link=http://www.socallinuxexpo.org/scale12x]]<br />
<br />
'''21-23 February, 2014. Los Angeles, CA, USA'''<br />
<br />
[https://www.socallinuxexpo.org/scale12x/presentations/seven-problems-linux-containers Seven Problems of Linux Containers], Feb 23, 13:30 to 14:30.<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 14:05, 24 January 2014 (EST)<br />
<br />
<br clear="both"><br />
== CRIU talk at SCALE11x ==<br />
[[Image:Scale-11x.png|left|link=http://www.socallinuxexpo.org/scale11x]]<br />
'''22-24 February, 2013. Los Angeles, CA, USA'''<br />
<br />
[http://www.socallinuxexpo.org/scale11x/presentations/checkpoint-restore-live-migration-and-beyond Checkpoint, Restore, Live Migration and Beyond - Kir Kolyshkin]<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 12:10, 23 January 2013 (EST)<br />
<br />
<br clear="both"><br />
== CRIU talk at linux.conf.au ==<br />
[[Image:Linux-conf-au-2013.jpg|left|link=https://lca2013.linux.org.au/]]<br />
'''28 January to 2 February, 2013. Canberra, Australia'''<br />
<br />
[https://lca2013.linux.org.au/schedule/30116/view_talk?day=thursday Checkpoint and Restore: Are We There Yet? - Pavel Emelyanov]<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 14:31, 17 December 2012 (EST)<br />
<br />
<br clear="both"><br />
== CRIU talk at FOSDEM ==<br />
[[Image:Fosdem-2013.png|left|link=https://fosdem.org/2013/]]<br />
'''2 and 3 February, 2013. Brussels, Belgium'''<br />
<br />
[https://fosdem.org/2013/schedule/event/criu_ckeckpoint_restore/ CRIU: Checkpoint and Restore (mostly) In Userspace - Andrey Vagin]<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 20:57, 22 January 2013 (EST)<br />
<br clear="both"><br />
<br />
<br />
== CRIU talk at YAC 2012 ==<br />
<br />
1 Oct 2012, Moscow, Russia || [http://events.yandex.ru/events/yac/2012/ YAC 2012]<br />
<br />
Kir Kolyshkin and Pavel Emelyanov will talk about CRIU project. CRIU is an implementation of checkpoint/restore mechanism for Linux which<br />
is mostly performed in userspace. An in-kernel OpenVZ implementation of checkpoint/restore will eventually be replaced by CRIU.<br />
<br clear="both"/><br />
== Container mini-summit at Linux Plumbers ==<br />
[[File:LinuxPlumbers.png|left|80px]]<br />
''San Diego, CA, USA, 29 Aug 2012''<br />
<br />
Discussed various topics on containers and resource management. See more at [http://summit.linuxplumbersconf.org/lpc-2012/meeting/116/lpc2012-cont-cgroups/].<br />
<br />
<br clear="both"/><br />
== Southern California Linux Expo ==<br />
[[File:Scale 10x 1.gif|left]]<br />
''Los Angeles, CA, 20-23 Jan 2012''<br />
<br />
OpenVZ will present itself at booth #54. Also, Kir Kolyshkin and Andrey Vagin will deliver a talk titled "Reinventing Linux loopback device" dedicated to a new ploop technology currently being developed. See more at [http://www.socallinuxexpo.org/scale10x/openvz] and [http://www.socallinuxexpo.org/scale10x/presentations/reinventing-linux-loopback-device-clouds].<br />
<br clear="both"/><br />
<br />
== FOSDEM 2012 ==<br />
[[File:Fosdem.png|left]]<br />
''Brussels, Belgium, 4-5 Feb 2012''<br />
<br />
OpenVZ will present a talk titled "Linux Containers and OpenVZ", see more at [http://fosdem.org/2012/schedule/event/hypervisors_openvz].<br />
<br clear="both"/><br />
<br />
== LinuxCon Europe 2011 ==<br />
[[File:Linuxcon.png|left]]<br />
''Prague, Czech, Oct 23 - 25, 2011''<br />
<br />
OpenVZ project manager, kernel team leader, and three kernel developers will be at LinuxCon. Two talks -- "Container in a file" about a new loop-like file system to store containers (Wed 11:45), and "OpenVZ and Linux Kernel testing" about our QA experience (Fri 16:45)-- will be presented. See more at the [http://events.linuxfoundation.org/events/linuxcon-europe Linux Con Europe site]. <br />
<br clear="both"/><br />
<br />
== Linux Plumbers Conference 2011 == <br />
[[File:LinuxPlumbers.png|left|80px]]<br />
''Santa Rosa, CA, USA, September 7-9, 2011''<br />
<br />
The conference includes Containers and CGroups mini-summit, during which we want to discuss a few interesting topics. See more at [http://blog.openvz.org/38447.html openvz blog].<br />
<br clear="both"/><br />
== LinuxSymposium 2010 ==<br />
''Ottawa, Canada, 13-16 July 2010''<br />
<br />
Kir Kolyshkin presented a two-hour tutorial about using OpenVZ.<br />
<br />
== LinuxTag 2010 ==<br />
[[File:LinuxTag.gif|left]]<br />
''Berlin, Germany, 9-12 June 2010''<br />
<br />
OpenVZ had a booth.<br />
<br />
<br clear="both"/><br />
== Linux Foundation Collaboration Summit ==<br />
[[File:Linux foundation collaboration summit-logo.png|left]]<br />
''San Francisco, CA, Apr 14-16 2010''<br/><br />
<br />
Kir Kolyshkin will deliver a talk titled "Containers and Namespaces in the Linux Kernel" during the Virtualization track.<br />
<br />
<br clear="both"/><br />
== Southern California Linux Expo aka SCALE 8x ==<br />
''Los Angeles, CA, Feb 19-21 2010''<br/><br />
[[File:SCALE8x.gif|left]]<br />
<br />
Kir Kolyshkin will be there presenting an OpenVZ booth.<br />
<br />
<br clear="both"/><br />
<br />
== Utah Open Source Conference 2009 ==<br />
''Sandy, Utah, USA, 8-10 Oct, 2009''<br/><br />
[[Image:UTOCS2009.png|left]]<br />
Scott Dowdle will host an OpenVZ booth, plus will also be giving a presentation entitled [http://2009.utosc.com/presentation/52/ Introduction to OS Virtualization, Containers, and OpenVZ].<br />
<br />
<br clear="both"/><br />
== LinuxTag 2009 ==<br />
''Berlin, Germany, June 24-27, 2009''<br/><br />
[[Image:LinuxTag.gif|left]]<br />
OpenVZ project will have a booth at this year's LinuxTag -- one of the biggest and greatest Linux shows in Germany.<br />
<br />
<br clear="both"/><br />
== Linux Symposium 2009 ==<br />
''Montreal, Canada, July 13-17 2009''<br/><br />
[[Image:Linux symposium 09.png|left]]<br />
It's a third time OpenVZ takes part in Linux Symposium, and a first time it's being held in Montreal! The project will present a [http://www.linuxsymposium.org/2009/view_abstract.php?content_key=31 tutorial on installing/using OpenVZ], and [http://www.linuxsymposium.org/2009/view_abstract.php?content_key=32 a BoF for OpenVZ users and developers].<br />
<br clear="both"/><br />
<hr color="#ddcef2"/><br />
<br />
== Southern California Linux Expo 2008 ==<br />
[[Image:Scale7x.gif|left]]<br />
''Los Angeles, USA, February 20-22, 2009''<br />
<br />
OpenVZ project will have a booth, plus Kir Kolyshkin will deliver [http://scale7x.socallinuxexpo.org/conference-info/speakers/kir-kolyshkin a talk] titled "Recent Advances in the Linux Kernel Resource Management"<br />
<br clear="both"/><br />
<hr color="#ddcef2"/><br />
<br />
[[Image:LinuxWorld logo.gif|left|180px]]<br />
== LinuxWorld Expo ==<br />
''San Francisco, California, USA, August 5-7, 2008''<br />
<br />
OpenVZ project will have a booth at the .org Pavilion at the upcoming [http://www.linuxworldexpo.com/live/12 LinuxWorld Conference and Expo 2008]. Plus, project leader Kir Kolyshkin will deliver [http://www.linuxworldexpo.com/live/12/conference//tracks/tracksessions/Virtualization/QMONYB00BHXK a talk titled "Containers, Virtualization, and Live Migration"].<br />
<br clear="both"/><br />
<hr color="#ddcef2"/><br />
<br />
[[Image: Scale6x.gif|left|100px]]<br />
== Southern California Linux Expo ==<br />
''Los Angeles, USA, February 8-10, 2008''<br />
<br />
OpenVZ will have a booth at the show, plus Kir Kolyshkin and Andrey Mirkin will present a talk titled "Containers Checkpointing and Live Migration".<br />
<br />
For more details, check [http://socallinuxexpo.com/ socallinuxexpo.com].<br />
<br clear="both"/><br />
<hr color="#ddcef2"/><br />
<br />
[[Image:FLoridaLinuxshow2.jpg|left|100px]]<br />
== Florida Linux Show ==<br />
''Jacksonville, FL, USA, February 11, 2008''<br />
<br />
Kir Kolyshkin will present an introductory talk about OpenVZ.<br />
<br />
For more details, check [http://www.floridalinuxshow.com/ floridalinuxshow.com].<br />
<br clear="both"/><br />
<hr color="#ddcef2"/><br />
<br />
[[Image:Linuxfestnorthwest.jpg|left|100px]]<br />
== LinuxFest Northwest ==<br />
'' Bellingham, WA, USA, April 26 and 27, 2008''<br />
<br />
Scott Dowdle is signed up to give a presentation on OpenVZ and OS virtualization.<br />
<br />
Check [http://linuxfestnorthwest.org/ linuxfestnorthwest.org] for more details.<br />
<br clear="both"/><br />
<hr color="#ddcef2"/><br />
<br />
[[Image:Linux Symposium 2008.gif|left|180px]]<br />
== Linux Symposium and Containers mini-summit==<br />
''Ottawa, Canada, July 23-26, 2008''<br />
<br />
[[Containers/Mini-summit 2008|Containers mini-summit]] will take place 22nd of July 2008, just before the conference. See [[Containers/Mini-summit 2008]] for more info.<br />
<br />
At the Linux Symposium, our kernel developer [http://www.linuxsymposium.org/2008/view_bio.php?id=3175 Andrey Mirkin] will present [http://www.linuxsymposium.org/2008/view_abstract.php?content_key=17 a talk titled "Containers Checkpointing and Live Migration"].<br />
<br clear="both"/><br />
<hr color="#ddcef2"/><br />
<br />
[[Image:LinuxWorld logo.gif|left|180px]]<br />
== LinuxWorld Expo ==<br />
''San Francisco, California, USA, August 5-7, 2008''<br />
<br />
OpenVZ project will have a booth at the .org Pavilion at the upcoming [http://www.linuxworldexpo.com/live/12 LinuxWorld Conference and Expo 2008]. Plus, project leader Kir Kolyshkin will deliver [http://www.linuxworldexpo.com/live/12/conference//tracks/tracksessions/Virtualization/QMONYB00BHXK a talk titled "Containers, Virtualization, and Live Migration"].<br />
<br />
[[Category:Events]]</div>Kirhttps://wiki.openvz.org/index.php?title=News/events&diff=22541News/events2017-02-15T18:46:03Z<p>Kir: vz webinar, make it shorter</p>
<hr />
<div><noinclude> __NOTOC__<br />
<!--<br />
This page is<br />
1. used directly (i.e. one can view it);<br />
2. included into some other pages (such as [[Template:News block 2]]);<br />
3. exported via RSS.<br />
Because of that, extreme care should be taken when modifying it. --~~~~<br />
<br />
>>> PLEASE MAKE SURE MOST RECENT EVENTS GO FIRST <<<<br />
<br />
--><br />
<startFeed/><br />
</noinclude><br />
== Virtuozzo Webinar: Cloud Security: Should You Be Worried? ==<br />
<br />
'''Feb 22, 2017 11:00am ET|8:00am PT'''<br />
<br />
We will discuss security risks and data protection threats faced by service providers today – and what you can do to overcome them. You’ll learn best practices for securing container data, and we’ll take a close look at some new technologies to keep your data more secure. [https://attendee.gotowebinar.com/register/7351790321802848771 Register here].<br />
<br />
--[[User:MaryMarks|MaryMarks]] ([[User talk:Mary|talk]]) 10:28, 15 February 2017 (UTC)<br />
<br clear="both"/><br />
<br />
== SCALE 15x ==<br />
[[Image:scale 15x logo.png|left|100px|link=]]<br />
<br />
'''March 2-5, 2017, Pasadena, CA, USA'''<br />
<br />
Kir Kolyshkin will tell about [http://www.socallinuxexpo.org/scale/15x/presentations/weird-ways-use-application-checkpointrestore some uncommon ways to use CRIU].<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 20:42, 13 February 2017 (UTC)<br />
<br clear="both"/><br />
<noinclude><br />
<endFeed/><br />
<br />
== See also ==<br />
* [[/past|Past events]]<br />
<br />
[[Category:Events]]<br />
</noinclude></div>Kirhttps://wiki.openvz.org/index.php?title=News/events&diff=22534News/events2017-02-13T21:23:54Z<p>Kir: rm extra empty line</p>
<hr />
<div><noinclude> __NOTOC__<br />
<!--<br />
This page is<br />
1. used directly (i.e. one can view it);<br />
2. included into some other pages (such as [[Template:News block 2]]);<br />
3. exported via RSS.<br />
Because of that, extreme care should be taken when modifying it. --~~~~<br />
<br />
>>> PLEASE MAKE SURE MOST RECENT EVENTS GO FIRST <<<<br />
<br />
--><br />
<startFeed/><br />
</noinclude><br />
== SCALE 15x ==<br />
[[Image:scale 15x logo.png|left|100px|link=]]<br />
<br />
'''March 2-5, 2017, Pasadena, CA, USA'''<br />
<br />
Kir Kolyshkin will tell about [http://www.socallinuxexpo.org/scale/15x/presentations/weird-ways-use-application-checkpointrestore some uncommon ways to use CRIU].<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 20:42, 13 February 2017 (UTC)<br />
<br clear="both"/><br />
<noinclude><br />
<endFeed/><br />
<br />
== See also ==<br />
* [[/past|Past events]]<br />
<br />
[[Category:Events]]<br />
</noinclude></div>Kirhttps://wiki.openvz.org/index.php?title=File:Scale_15x_logo.png&diff=22533File:Scale 15x logo.png2017-02-13T21:23:11Z<p>Kir: </p>
<hr />
<div></div>Kirhttps://wiki.openvz.org/index.php?title=News/events&diff=22532News/events2017-02-13T21:22:56Z<p>Kir: /* SCALE 15x */ add image and dates</p>
<hr />
<div><noinclude> __NOTOC__<br />
<!--<br />
This page is<br />
1. used directly (i.e. one can view it);<br />
2. included into some other pages (such as [[Template:News block 2]]);<br />
3. exported via RSS.<br />
Because of that, extreme care should be taken when modifying it. --~~~~<br />
<br />
>>> PLEASE MAKE SURE MOST RECENT EVENTS GO FIRST <<<<br />
<br />
--><br />
<startFeed/><br />
</noinclude><br />
<br />
== SCALE 15x ==<br />
[[Image:scale 15x logo.png|left|100px|link=]]<br />
<br />
'''March 2-5, 2017, Pasadena, CA, USA'''<br />
<br />
Kir Kolyshkin will tell about [http://www.socallinuxexpo.org/scale/15x/presentations/weird-ways-use-application-checkpointrestore some uncommon ways to use CRIU].<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 20:42, 13 February 2017 (UTC)<br />
<br clear="both"/><br />
<noinclude><br />
<endFeed/><br />
<br />
== See also ==<br />
* [[/past|Past events]]<br />
<br />
[[Category:Events]]<br />
</noinclude></div>Kirhttps://wiki.openvz.org/index.php?title=News/events&diff=22531News/events2017-02-13T20:42:16Z<p>Kir: scale15x</p>
<hr />
<div><noinclude> __NOTOC__<br />
<!--<br />
This page is<br />
1. used directly (i.e. one can view it);<br />
2. included into some other pages (such as [[Template:News block 2]]);<br />
3. exported via RSS.<br />
Because of that, extreme care should be taken when modifying it. --~~~~<br />
<br />
>>> PLEASE MAKE SURE MOST RECENT EVENTS GO FIRST <<<<br />
<br />
--><br />
<startFeed/><br />
</noinclude><br />
<br />
== SCALE 15x ==<br />
<br />
Kir Kolyshkin will tell about [http://www.socallinuxexpo.org/scale/15x/presentations/weird-ways-use-application-checkpointrestore some uncommon ways to use CRIU].<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 20:42, 13 February 2017 (UTC)<br />
<br />
<noinclude><br />
<endFeed/><br />
== See also ==<br />
* [[/past|Past events]]<br />
<br />
[[Category:Events]]<br />
</noinclude></div>Kirhttps://wiki.openvz.org/index.php?title=News/events/past&diff=22530News/events/past2017-02-13T20:39:49Z<p>Kir: moved past events</p>
<hr />
<div>{{Note|this page lists events that has happened already, kept here just for historical reasons. For future events, see [[News/events]].}}<br />
__TOC__<br />
<br />
== Presentation DevConf.cz - Painless Userspace Live Patching ==<br />
'''January 29, 2017'''<br />
<br />
Virtuozzo expert Stanislav Kinsburskiy will be discussing “Painless Userspace Live Patching" at DevConf.cz. His talk will touch on technologies like binary analysis, stack unwinding, process manipulation via new library "libcompel", and more.<br />
<br />
[https://devconf.cz/index.html#about DevConf.cz Jan 27-29 Brno, Czech Republic]<br />
<br />
--[[User:Marymarks|Marymarks]] ([[User talk:Marymarks|talk]]) 21:35, 24 January 2017 (UTC)<br />
<br />
== Presentation DevConf.cz - Decreasing container downtime during migration ==<br />
'''January 29, 2017'''<br />
<br />
Adrian Weber, Red Hat Software Developer, will be discussing how CRIU can reduce migration downtime.<br />
<br />
[https://devconf.cz/index.html#about DevConf.cz Jan 27-29 Brno, Czech Republic]<br />
<br />
--[[User:Marymarks|Marymarks]] ([[User talk:Marymarks|talk]]) 21:35, 24 January 2017 (UTC)<br />
<br />
== Presentation FOSDEM.org - OpenVZ containers, how they work and look ==<br />
'''February 4, 2017'''<br />
<br />
Virtuozzo expert Alexander Stefanov will be discussing OpenVZ containers and how Virtuozzo Linux can create lightweight virtual environments.<br />
<br />
[https://fosdem.org/2017/ FOSDEM.org Feb 4-5 Brussels, Belgium]<br />
<br />
--[[User:Marymarks|Marymarks]] ([[User talk:Marymarks|talk]]) 21:35, 24 January 2017 (UTC)<br />
<br />
== Webinar: Getting to Virtuozzo 7 ==<br />
'''December 14, 2016'''<br />
<br />
Learn how to move to the most recent Virtuozzo version and get all the benefits of its new features. This webinar will cover all the possible upgrade options in great technical details. You will also have an opportunity to ask any technical questions you may have. [https://attendee.gotowebinar.com/recording/2531794127555599371 Recording]<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 23:06, 30 November 2016 (UTC)<br />
<br />
== Webinar: What's new in Virtuozzo 7 ==<br />
'''December 7, 2016'''<br />
<br />
Cover the changes and new features of Virtuozzo 7 in great technical details. [https://attendee.gotowebinar.com/recording/1407907426348600067 Recording]<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 23:06, 30 November 2016 (UTC)<br />
<br />
<br />
== SeaGL 2016 ==<br />
[[File:SeaGL.png|left|100px]]<br />
'''Nov 11-12, 2016, Seattle, WA'''<br />
<br />
Kir Kolyshkin will talk about [https://osem.seagl.org/conference/seagl2016/program/proposal/236 Linux containers history].<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 22:08, 23 September 2016 (UTC)<br />
<br clear="both"><br />
== Linux Piter ==<br />
[[File:Linuxpiter.png|left|100px]]<br />
<br />
'''Nov 11-12, 2016, St.Petersburg'''<br />
<br />
Pavel Emelyanov will talk about [http://www.it-events.com/ru/events/6997#tabs-programm containers],<br />
and Tycho Andresen will talk about how LXC/LXD uses CRIU.<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 06:45, 13 October 2016 (UTC)<br />
<br clear="both"><br />
<br />
== Linux Plumbers Conference 2016 ==<br />
[[File:LinuxPlumbers.png|left|100px]]<br />
'''Nov 2-4, 2016, Santa Fe, NM'''<br />
<br />
[https://linuxplumbersconf.org/2016/ocw/events/LPC2016/tracks/519 Containers] and <br />
[https://linuxplumbersconf.org/2016/ocw/events/LPC2016/tracks/567 Checkpoint/restore]<br />
micro-conferences are both part of the Linux Plumbers event.<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 21:59, 23 September 2016 (UTC)<br />
<br clear="both"><br />
<br />
== LinuxCon + ContainerCon North America 2016 ==<br />
[[Image:Linuxcon.png|left|100px]]<br />
<br />
'''August 22-24 2016, Toronto, Canada'''<br />
<br />
Kir Kolyshkin and Andrey Vagin will talk about [http://lcccna2016.sched.org/event/7JWS/time-to-rethink-proc-kirill-kolyshkin-open-vzvirtuozzo?iframe=no&w=&sidebar=yes&bg=no Time to rethink /proc].<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 10:25, 15 June 2016 (EDT)<br />
<br />
<br clear=all><br />
== nginx.conf 2016 ==<br />
[[Image:Nginx-conf-16-logo.png|left|100px]]<br />
<br />
'''September 07-09, 2016, Austin, TX'''<br />
<br />
Pavel Emelyanov will have a [https://www.nginx.com/nginxconf/program/#572353576a0fe82a1a000144 NGINX + Virtuozzo = Love AND Performance].<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 04:57, 23 June 2016 (EDT)<br />
<br />
<br clear=all><br />
== OSDN conference 2016 ==<br />
[[Image:Osdn-logo.png|left|100px]]<br />
<br />
'''Sep 17 2016, Kyiv, Ukraine'''<br />
<br />
Pavel Emelyanov and Sergey Bronnikov will [http://osdn.org.ua/manual/#speakers present] two talks: "Что нового в OpenVZ?" and "Дались вам эти контейнеры!".<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 11:21, 28 July 2016 (EDT)<br />
<br />
<br clear=all><br />
== Texas Linux Fest 2016 ==<br />
[[Image:2016-06-15 13-47-25.png|left|100px]]<br />
<br />
'''July 08-09, 2016, Austin, TX'''<br />
<br />
Kir Kolyshkin will talk about [http://2016.texaslinuxfest.org/node/101 Time to rethink /proc].<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 06:50, 15 June 2016 (EDT)<br />
<br />
<br clear=all><br />
== DockerCon 2016 ==<br />
[[Image:Dockercon16.png|left|100px]]<br />
<br />
'''June 19-21, 2016, Seattle, WA'''<br />
<br />
We will have a booth (S28) there.<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 06:49, 15 June 2016 (EDT)<br />
<br />
<br clear=all><br />
== QA: Conference 2016 ==<br />
[[Image:Qac black.png|left|100px]]<br />
<br />
'''23 Apr 2016, Moscow, Russia'''<br />
<br />
[http://qaconf.ru/speakers.html Continuous Integration in OpenStack development] -- Evgenii Antyshev<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 07:56, 4 March 2016 (EST)<br />
<br />
<br clear=all><br />
== The Linux Storage, Filesystem & Memory Management Summit 2016 ==<br />
[[Image:Lsfmm logo.png|left|100px]]<br />
<br />
'''18-19 April 2016, Raleigh, NC'''<br />
<br />
Attendees from OpenVZ project: Dmitry Monakhov and Vladimir Davydov. See [http://events.linuxfoundation.org/events/linux-storage-filesystem-and-mm-summit program].<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 04:02, 4 March 2016 (EST)<br />
<br />
<br clear=all><br />
== DevConf.cz 2016 ==<br />
[[Image:Devconf.cz-logo.png|left|100px]]<br />
<br />
'''5-7 Feb 2016, Brno, Czech Republic'''<br />
<br />
[https://devconfcz2016.sched.org/event/5lzL/live-migrating-a-container-pros-cons-and-gotchas Live migrating a container: pros, cons and gotchas] -- Pavel Emelyanov<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 13:34, 11 January 2016 (EST)<br />
<br />
<br clear=all><br />
== FOSDEM 2016 ==<br />
[[Image:fosdem-logo.png|left|80px]]<br />
<br />
'''30-31 Jan 2016, Brussels, Belgium'''<br />
<br />
Containers and Process Isolation devroom ([https://www.fosdem.org/2016/schedule/track/containers_and_process_isolation/ schedule])<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 09:41, 21 December 2015 (EST)<br />
<br />
<br clear=all><br />
== Linux Piter 2015 ==<br />
[[Image:Tux.png|left|80px]]<br />
<br />
'''November 21, 2015, Saint Petersburg, Russia'''<br />
<br />
[http://www.it-sobytie.ru/events/4868 Живая миграция контейнеров: плюсы, минусы, подводные камни] -- Pavel Emelyanov<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 17:43, 27 August 2015 (EDT)<br />
<br />
<br clear=all><br />
== ContainerDays NYC 2015 ==<br />
[[Image:2015-nyc-logo.png|left|100px]]<br />
<br />
'''October 30, 2015, New York, U.S.A.'''<br />
<br />
[http://dynamicinfradays.org/events/2015-nyc/programme.html#criu CRIU: Time and Space Travel for Linux Containers] -- by Kirill Kolyshkin<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 00:50, 14 September 2015 (EDT)<br />
<br />
<br clear=all><br />
== OpenStack Summit ==<br />
[[Image:Openstack-summit-logo.svg|left|120px]]<br />
<br />
'''October 27-30, 2015, Tokyo, Japan'''<br />
<br />
Part of OpenVZ Team will attend in [https://www.openstack.org/summit/tokyo-2015/ OpenStack Tokyo]:<br />
Sergey Bronnikov, Dmitry Guryanov (LibVirt, integration with OpenStack), Maxim Nestratov (LibVirt, integration with OpenStack).<br />
You are welcome to contact with us!<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 05:29, 9 September 2015 (EDT)<br />
<br />
== SECR 2015 ==<br />
[[Image:Secr 2015 logo-site.png|left|100px]]<br />
<br />
'''October 22–24 2015, Moscow, Russia'''<br />
<br />
[http://2015.secr.ru/lang/ru/program/submitted-presentations/testing-of-software-based-on-third-party-components-by-the-linux-distribution-example Testing of software based on third party components by the linux distribution example] -- Denis Silakov<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 12:55, 23 September 2015 (EDT)<br />
<br />
== The 12th conference of developers of free software ==<br />
[[Image:Altlinux-logo.gif|left|100px]]<br />
<br />
'''October 16-18, 2015, Kaluga, Russia'''<br />
<br />
[http://www.altlinux.ru/news/archive/2015/08/item/743/ Двенадцатая конференция разработчиков свободных программ]<br />
<br />
Живая миграция контейнеров: плюсы, минусы, подводные камни -- ''Pavel Emelyanov''<br />
<br />
Когда уже OpenVZ будет в основном Linux ядре? -- ''Sergey Bronnikov''<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 08:46, 1 October 2015 (EDT)<br />
<br />
== OpenVZ meetup ==<br />
[[Image:Yandex.png|left|80px]]<br />
<br />
'''September 19, 2015, Moscow, Russia'''<br />
<br />
[https://events.yandex.ru/events/yagosti/19-september-2015-linux/ Встреча разработчиков Linux-контейнеров]<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 06:19, 28 August 2015 (EDT)<br />
<br />
== Linux Plumbers Conference ==<br />
[[Image:LinuxPlumbers.png|left|100px]]<br />
<br />
'''Seattle, WA, USA, August 19-21 2015'''<br />
<br />
Check [https://linuxplumbersconf.org/2015/ocw/events/LPC2015/schedule/ Linux Plumbers Conference] website for more details.<br />
<br clear="both"/><br />
* CGroups kernel memory manager (containers MC), ''by Pavel Emelyanov''<br />
* P.Haul: live migration with CRIU (C/R MC), ''by Pavel Emelyanov''<br />
* Containers in the upstream kernel (containers MC), ''by Kir Kolyshkin''<br />
* C/R status update (containers MC), ''by Andrey Vagin''<br />
* Running Docker inside VZ containers (Plumbers, Containers MC), ''by Maxim Patlasov''<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 11:16, 22 August 2015 (EDT)<br />
<br />
== ContainerCon ==<br />
[[Image:Logo_containercon.png|left|100px]]<br />
'''Seattle, WA, USA, August 17-19 2015'''<br />
<br />
The Linux Foundation is launching a new conference called ContainerCon to bring together leading contributors in Linux containers, the Linux kernel, and related projects to forge a path to continued innovation and education.<br />
<br />
Check [http://events.linuxfoundation.org/events/containercon ContainerCon event page] for more details.<br />
<br />
* Denser containers with PFcache, ''by Pavel Emelyanov''<br />
* A brief history of containers, ''by Kir Kolyshkin''<br />
* Libcontainer: one lib to rule them all, ''by Andrey Vagin''<br />
* Private Cloud is Dead, Long Live Public Cloud, ''by James Bottomley''<br />
* Taking Containers to the Next Level, ''by James Bottomley''<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 01:41, 11 August 2015 (EDT)<br />
<br />
== LVEE 2015 ==<br />
[[File:Lvee_logo_180x174.png|left|100px]]<br />
<br />
'''25-28 June 2015, Grodno, Belarus'''<br />
<br />
[http://lvee.org/ru/conference_registrations/LVEE%202015 "Мифы и легенды о проекте OpenVZ"]<br />
<br />
Sergey Bronnikov will talk about myths around OpenVZ project (in Russian).<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 16:59, 6 June 2015 (EDT)<br />
<br />
== OSday 2015 ==<br />
[[Image:800px-Os-day-logo.png|left|150px]]<br />
<br />
'''Kazan, Russia, June 9-10 2015'''<br />
<br />
[http://osday.org/bronnikov.html#speaker Семь проблем Linux контейнеров]<br />
<br />
Sergey Bronnikov will talk about problems in Linux containers (in Russian).<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 14:23, 19 May 2015 (EDT)<br />
<br clear="both"/><br />
<br />
== ContainerDays 2015 ==<br />
[[Image:Logo-ContainerDays.png|left|150px]]<br />
<br />
'''Boston, MA, USA, June 5-6 2015'''<br />
<br />
ContainerDays Boston is a community (un)conference to encourage discussion and learning on the subject of containers and dynamic infrastructure generally. The programme is a mix of OpenSpaces sessions and talks from users, contributors and extenders from all corners of the space.<br />
<br />
Kir Kolyshkin from OpenVZ project will give a talk [http://dynamicinfradays.org/events/2015-boston/programme.html#nproblems "N Problems of Linux Containers...and Some Solutions"].<br />
<br />
--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 05:26, 12 May 2015 (EDT)<br />
<br clear="both"/><br />
<br />
== LinuxFest Northwest 2015 ==<br />
[[Image:Linuxfestnorthwest.jpg|left|100px]]<br />
'''Bellingham, WA, USA, April 25-26 2015'''<br />
<br />
Kir Kolyshkin is signed up to give a [http://linuxfestnorthwest.org/2015/sessions/openvz-virtuozzo-core-and-docker presentation on OpenVZ, Virtuozzo Core and Docker].<br />
<br />
Check [http://linuxfestnorthwest.org/ linuxfestnorthwest.org] for more details.<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 19:25, 22 March 2015 (EDT)<br />
<br />
<br clear="both"/><br />
== Linux Plumbers ==<br />
[[Image:LinuxPlumbers.png|left|100px]]<br />
<br />
'''October 15-17, 2014, Dusseldorf, Germany'''<br />
<br />
Slides [http://www.linuxplumbersconf.org/2014/ocw/proposals/1959 Are containers that we have now secure enough?]<br />
<br />
[http://www.linuxplumbersconf.org/2014/an-in-depth-look-containers-microconference/ Containers mini-conf ] -- Pavel Emelyanov, Kir Kolyshkin<noinclude><br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 11:58, 6 June 2014 (EDT)<br />
<br />
<br clear="both"/><br />
== LinuxCon ==<br />
[[Image:Linuxcon.png|left|100px]]<br />
<br />
'''August 20 - 22, 2014, Chicago, IL, USA'''<br />
<br />
[http://sched.co/1r2OMI2 Containers in Linux: Current State and Where We're Going] - James Bottomley<noinclude><br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 13:50, 15 August 2014 (EDT)<br />
<br />
<br clear="both"/><br />
== Open WG talk ==<br />
[[Image:WGtalk.png|left|100px]]<br />
<br />
'''Friday, July 18, 2014, Minsk, Belarus'''<br />
<br />
[https://www.eventbrite.com/e/open-wg-talk-2-linux-container-virtualization-tickets-12189971533?fb_action_ids=705517169505083&fb_action_types=og.likes&fb_source=feed_opengraph&action_object_map=%7B%22705517169505083%22%3A753726634669877%7D&action_type_map=%7B%22705517169505083%22%3A%22og.likes%22%7D&action_ref_map=%5B%5D Open WG Talk -- Linux container virtualization] -- Andrey Vagin, Konstantin Khorenko<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 14:47, 9 July 2014 (EDT)<br />
<br />
<br clear="both"><br />
== Texas Linux Fest ==<br />
[[Image:Txlf2014.png|left|100px]]<br />
<br />
'''June 13-14, 2014, Austin, Texas, US'''<br />
<br />
[https://2014.texaslinuxfest.org/content/criu-time-and-space-travel-service-linux-apps.html CRIU: time and space travel service for Linux apps] -- Kir Kolyshkin<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 11:56, 6 June 2014 (EDT)<br />
<br />
<br clear="both"><br />
<br />
== OpenVZ talk at SCALE12x ==<br />
[[Image:Scale-12x.png|left|120px|link=http://www.socallinuxexpo.org/scale12x]]<br />
<br />
'''21-23 February, 2014. Los Angeles, CA, USA'''<br />
<br />
[https://www.socallinuxexpo.org/scale12x/presentations/seven-problems-linux-containers Seven Problems of Linux Containers], Feb 23, 13:30 to 14:30.<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 14:05, 24 January 2014 (EST)<br />
<br />
<br clear="both"><br />
== CRIU talk at SCALE11x ==<br />
[[Image:Scale-11x.png|left|link=http://www.socallinuxexpo.org/scale11x]]<br />
'''22-24 February, 2013. Los Angeles, CA, USA'''<br />
<br />
[http://www.socallinuxexpo.org/scale11x/presentations/checkpoint-restore-live-migration-and-beyond Checkpoint, Restore, Live Migration and Beyond - Kir Kolyshkin]<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 12:10, 23 January 2013 (EST)<br />
<br />
<br clear="both"><br />
== CRIU talk at linux.conf.au ==<br />
[[Image:Linux-conf-au-2013.jpg|left|link=https://lca2013.linux.org.au/]]<br />
'''28 January to 2 February, 2013. Canberra, Australia'''<br />
<br />
[https://lca2013.linux.org.au/schedule/30116/view_talk?day=thursday Checkpoint and Restore: Are We There Yet? - Pavel Emelyanov]<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 14:31, 17 December 2012 (EST)<br />
<br />
<br clear="both"><br />
== CRIU talk at FOSDEM ==<br />
[[Image:Fosdem-2013.png|left|link=https://fosdem.org/2013/]]<br />
'''2 and 3 February, 2013. Brussels, Belgium'''<br />
<br />
[https://fosdem.org/2013/schedule/event/criu_ckeckpoint_restore/ CRIU: Checkpoint and Restore (mostly) In Userspace - Andrey Vagin]<br />
<br />
--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 20:57, 22 January 2013 (EST)<br />
<br clear="both"><br />
<br />
<br />
== CRIU talk at YAC 2012 ==<br />
<br />
1 Oct 2012, Moscow, Russia || [http://events.yandex.ru/events/yac/2012/ YAC 2012]<br />
<br />
Kir Kolyshkin and Pavel Emelyanov will talk about CRIU project. CRIU is an implementation of checkpoint/restore mechanism for Linux which<br />
is mostly performed in userspace. An in-kernel OpenVZ implementation of checkpoint/restore will eventually be replaced by CRIU.<br />
<br clear="both"/><br />
== Container mini-summit at Linux Plumbers ==<br />
[[File:LinuxPlumbers.png|left|80px]]<br />
''San Diego, CA, USA, 29 Aug 2012''<br />
<br />
Discussed various topics on containers and resource management. See more at [http://summit.linuxplumbersconf.org/lpc-2012/meeting/116/lpc2012-cont-cgroups/].<br />
<br />
<br clear="both"/><br />
== Southern California Linux Expo ==<br />
[[File:Scale 10x 1.gif|left]]<br />
''Los Angeles, CA, 20-23 Jan 2012''<br />
<br />
OpenVZ will present itself at booth #54. Also, Kir Kolyshkin and Andrey Vagin will deliver a talk titled "Reinventing Linux loopback device" dedicated to a new ploop technology currently being developed. See more at [http://www.socallinuxexpo.org/scale10x/openvz] and [http://www.socallinuxexpo.org/scale10x/presentations/reinventing-linux-loopback-device-clouds].<br />
<br clear="both"/><br />
<br />
== FOSDEM 2012 ==<br />
[[File:Fosdem.png|left]]<br />
''Brussels, Belgium, 4-5 Feb 2012''<br />
<br />
OpenVZ will present a talk titled "Linux Containers and OpenVZ", see more at [http://fosdem.org/2012/schedule/event/hypervisors_openvz].<br />
<br clear="both"/><br />
<br />
== LinuxCon Europe 2011 ==<br />
[[File:Linuxcon.png|left]]<br />
''Prague, Czech, Oct 23 - 25, 2011''<br />
<br />
OpenVZ project manager, kernel team leader, and three kernel developers will be at LinuxCon. Two talks -- "Container in a file" about a new loop-like file system to store containers (Wed 11:45), and "OpenVZ and Linux Kernel testing" about our QA experience (Fri 16:45)-- will be presented. See more at the [http://events.linuxfoundation.org/events/linuxcon-europe Linux Con Europe site]. <br />
<br clear="both"/><br />
<br />
== Linux Plumbers Conference 2011 == <br />
[[File:LinuxPlumbers.png|left|80px]]<br />
''Santa Rosa, CA, USA, September 7-9, 2011''<br />
<br />
The conference includes Containers and CGroups mini-summit, during which we want to discuss a few interesting topics. See more at [http://blog.openvz.org/38447.html openvz blog].<br />
<br clear="both"/><br />
== LinuxSymposium 2010 ==<br />
''Ottawa, Canada, 13-16 July 2010''<br />
<br />
Kir Kolyshkin presented a two-hour tutorial about using OpenVZ.<br />
<br />
== LinuxTag 2010 ==<br />
[[File:LinuxTag.gif|left]]<br />
''Berlin, Germany, 9-12 June 2010''<br />
<br />
OpenVZ had a booth.<br />
<br />
<br clear="both"/><br />
== Linux Foundation Collaboration Summit ==<br />
[[File:Linux foundation collaboration summit-logo.png|left]]<br />
''San Francisco, CA, Apr 14-16 2010''<br/><br />
<br />
Kir Kolyshkin will deliver a talk titled "Containers and Namespaces in the Linux Kernel" during the Virtualization track.<br />
<br />
<br clear="both"/><br />
== Southern California Linux Expo aka SCALE 8x ==<br />
''Los Angeles, CA, Feb 19-21 2010''<br/><br />
[[File:SCALE8x.gif|left]]<br />
<br />
Kir Kolyshkin will be there presenting an OpenVZ booth.<br />
<br />
<br clear="both"/><br />
<br />
== Utah Open Source Conference 2009 ==<br />
''Sandy, Utah, USA, 8-10 Oct, 2009''<br/><br />
[[Image:UTOCS2009.png|left]]<br />
Scott Dowdle will host an OpenVZ booth, plus will also be giving a presentation entitled [http://2009.utosc.com/presentation/52/ Introduction to OS Virtualization, Containers, and OpenVZ].<br />
<br />
<br clear="both"/><br />
== LinuxTag 2009 ==<br />
''Berlin, Germany, June 24-27, 2009''<br/><br />
[[Image:LinuxTag.gif|left]]<br />
OpenVZ project will have a booth at this year's LinuxTag -- one of the biggest and greatest Linux shows in Germany.<br />
<br />
<br clear="both"/><br />
== Linux Symposium 2009 ==<br />
''Montreal, Canada, July 13-17 2009''<br/><br />
[[Image:Linux symposium 09.png|left]]<br />
It's a third time OpenVZ takes part in Linux Symposium, and a first time it's being held in Montreal! The project will present a [http://www.linuxsymposium.org/2009/view_abstract.php?content_key=31 tutorial on installing/using OpenVZ], and [http://www.linuxsymposium.org/2009/view_abstract.php?content_key=32 a BoF for OpenVZ users and developers].<br />
<br clear="both"/><br />
<hr color="#ddcef2"/><br />
<br />
== Southern California Linux Expo 2008 ==<br />
[[Image:Scale7x.gif|left]]<br />
''Los Angeles, USA, February 20-22, 2009''<br />
<br />
OpenVZ project will have a booth, plus Kir Kolyshkin will deliver [http://scale7x.socallinuxexpo.org/conference-info/speakers/kir-kolyshkin a talk] titled "Recent Advances in the Linux Kernel Resource Management"<br />
<br clear="both"/><br />
<hr color="#ddcef2"/><br />
<br />
[[Image:LinuxWorld logo.gif|left|180px]]<br />
== LinuxWorld Expo ==<br />
''San Francisco, California, USA, August 5-7, 2008''<br />
<br />
OpenVZ project will have a booth at the .org Pavilion at the upcoming [http://www.linuxworldexpo.com/live/12 LinuxWorld Conference and Expo 2008]. Plus, project leader Kir Kolyshkin will deliver [http://www.linuxworldexpo.com/live/12/conference//tracks/tracksessions/Virtualization/QMONYB00BHXK a talk titled "Containers, Virtualization, and Live Migration"].<br />
<br clear="both"/><br />
<hr color="#ddcef2"/><br />
<br />
[[Image: Scale6x.gif|left|100px]]<br />
== Southern California Linux Expo ==<br />
''Los Angeles, USA, February 8-10, 2008''<br />
<br />
OpenVZ will have a booth at the show, plus Kir Kolyshkin and Andrey Mirkin will present a talk titled "Containers Checkpointing and Live Migration".<br />
<br />
For more details, check [http://socallinuxexpo.com/ socallinuxexpo.com].<br />
<br clear="both"/><br />
<hr color="#ddcef2"/><br />
<br />
[[Image:FLoridaLinuxshow2.jpg|left|100px]]<br />
== Florida Linux Show ==<br />
''Jacksonville, FL, USA, February 11, 2008''<br />
<br />
Kir Kolyshkin will present an introductory talk about OpenVZ.<br />
<br />
For more details, check [http://www.floridalinuxshow.com/ floridalinuxshow.com].<br />
<br clear="both"/><br />
<hr color="#ddcef2"/><br />
<br />
[[Image:Linuxfestnorthwest.jpg|left|100px]]<br />
== LinuxFest Northwest ==<br />
'' Bellingham, WA, USA, April 26 and 27, 2008''<br />
<br />
Scott Dowdle is signed up to give a presentation on OpenVZ and OS virtualization.<br />
<br />
Check [http://linuxfestnorthwest.org/ linuxfestnorthwest.org] for more details.<br />
<br clear="both"/><br />
<hr color="#ddcef2"/><br />
<br />
[[Image:Linux Symposium 2008.gif|left|180px]]<br />
== Linux Symposium and Containers mini-summit==<br />
''Ottawa, Canada, July 23-26, 2008''<br />
<br />
[[Containers/Mini-summit 2008|Containers mini-summit]] will take place 22nd of July 2008, just before the conference. See [[Containers/Mini-summit 2008]] for more info.<br />
<br />
At the Linux Symposium, our kernel developer [http://www.linuxsymposium.org/2008/view_bio.php?id=3175 Andrey Mirkin] will present [http://www.linuxsymposium.org/2008/view_abstract.php?content_key=17 a talk titled "Containers Checkpointing and Live Migration"].<br />
<br clear="both"/><br />
<hr color="#ddcef2"/><br />
<br />
[[Image:LinuxWorld logo.gif|left|180px]]<br />
== LinuxWorld Expo ==<br />
''San Francisco, California, USA, August 5-7, 2008''<br />
<br />
OpenVZ project will have a booth at the .org Pavilion at the upcoming [http://www.linuxworldexpo.com/live/12 LinuxWorld Conference and Expo 2008]. Plus, project leader Kir Kolyshkin will deliver [http://www.linuxworldexpo.com/live/12/conference//tracks/tracksessions/Virtualization/QMONYB00BHXK a talk titled "Containers, Virtualization, and Live Migration"].<br />
<br />
[[Category:Events]]</div>Kirhttps://wiki.openvz.org/index.php?title=User:Byrner&diff=22529User:Byrner2017-02-13T20:38:00Z<p>Kir: Creating user page for new user.</p>
<hr />
<div>My name is Mike, I am a big fan of the OpenVZ project and hope to continue to watch it grow over the coming months and years. I would love the opportunity to play a small role in that growth by helping fill in these pages. I am happy to provide any additional information you may require from me.<br />
<br />
Thank you for the opportunity.</div>Kirhttps://wiki.openvz.org/index.php?title=User:Onliveserver&diff=22512User:Onliveserver2017-02-03T20:03:02Z<p>Kir: Creating user page for new user.</p>
<hr />
<div>Onlive Server Technology LLP is an established Server Administration, Cloud VPS, IT Support Services and Web Hosting since 2008. Carefully studying its customers needs, Onlive Server Technology is consistently improving the quality of its services, which results in numerous loyal customers we have been cooperating with since the very foundation of the company.<br />
<br />
I am working on platforms like Windows Servers, Linux Servers, Vmware, Hyper-VM, Solus VM, KVM, XEN and storage server 2012, Centos, Ubuntu, Debian, Fedora, Suse, Scientific, WHM/Cpanel, Webmin, Plesk and Postfix.<br />
<br />
Service Description:<br />
<br />
- Microsoft Exchange hosted Solutions<br />
- Network Management<br />
- Server Setup & Management<br />
- Data center Management<br />
- Virtualization Solutions<br />
- Migration Services<br />
- Linux and Windows Hosting</div>Kirhttps://wiki.openvz.org/index.php?title=News/events&diff=22509News/events2017-01-25T06:06:43Z<p>Kir: fix extra tags, minor whitespace cleanup</p>
<hr />
<div><noinclude> __NOTOC__<br />
<!--<br />
This page is<br />
1. used directly (i.e. one can view it);<br />
2. included into some other pages (such as [[Template:News block 2]]);<br />
3. exported via RSS.<br />
Because of that, extreme care should be taken when modifying it. --~~~~<br />
<br />
>>> PLEASE MAKE SURE MOST RECENT EVENTS GO FIRST <<<<br />
<br />
--><br />
<startFeed/><br />
</noinclude><br />
== Presentation DevConf.cz - Painless Userspace Live Patching ==<br />
'''January 29, 2017'''<br />
<br />
Virtuozzo expert Stanislav Kinsburskiy will be discussing “Painless Userspace Live Patching" at DevConf.cz. His talk will touch on technologies like binary analysis, stack unwinding, process manipulation via new library "libcompel", and more.<br />
<br />
[https://devconf.cz/index.html#about DevConf.cz Jan 27-29 Brno, Czech Republic]<br />
<br />
--[[User:Marymarks|Marymarks]] ([[User talk:Marymarks|talk]]) 21:35, 24 January 2017 (UTC)<br />
<br />
== Presentation DevConf.cz - Decreasing container downtime during migration ==<br />
'''January 29, 2017'''<br />
<br />
Adrian Weber, Red Hat Software Developer, will be discussing how CRIU can reduce migration downtime.<br />
<br />
[https://devconf.cz/index.html#about DevConf.cz Jan 27-29 Brno, Czech Republic]<br />
<br />
--[[User:Marymarks|Marymarks]] ([[User talk:Marymarks|talk]]) 21:35, 24 January 2017 (UTC)<br />
<br />
== Presentation FOSDEM.org - OpenVZ containers, how they work and look ==<br />
'''February 4, 2017'''<br />
<br />
Virtuozzo expert Alexander Stefanov will be discussing OpenVZ containers and how Virtuozzo Linux can create lightweight virtual environments.<br />
<br />
[https://fosdem.org/2017/ FOSDEM.org Feb 4-5 Brussels, Belgium]<br />
<br />
--[[User:Marymarks|Marymarks]] ([[User talk:Marymarks|talk]]) 21:35, 24 January 2017 (UTC)<br />
<br />
<noinclude><br />
<endFeed/><br />
== See also ==<br />
* [[/past|Past events]]<br />
<br />
[[Category:Events]]<br />
</noinclude></div>Kirhttps://wiki.openvz.org/index.php?title=User:Vpsfast&diff=22506User:Vpsfast2017-01-23T21:30:23Z<p>Kir: Creating user page for new user.</p>
<hr />
<div>VPSFast is dedicated to provide cheap and reliable VPS Hosting. Our VPS is ideal and cost-effective hosting platform for customers looking for high performance, redundancy and scalability at economical price.</div>Kirhttps://wiki.openvz.org/index.php?title=User:StasFomin&diff=22505User:StasFomin2017-01-23T21:29:28Z<p>Kir: Creating user page for new user.</p>
<hr />
<div>* http://discopal.ispras.ru/User:StasFomin/CV<br />
* https://ru.wikipedia.org/wiki/User:Stas<br />
* http://0x1.tv/User:StasFomin<br />
* http://wiki.4intra.net/User:StasFomin<br />
* https://habrahabr.ru/users/belonesox/<br />
* https://linkedin.com/in/stasfomin<br />
* http://belonesox.moikrug.ru<br />
* http://facebook.com/stas.fomin</div>Kirhttps://wiki.openvz.org/index.php?title=MediaWiki:Sitenotice&diff=22504MediaWiki:Sitenotice2017-01-23T19:16:23Z<p>Kir: new banner</p>
<hr />
<div><div class="plainlinks" align="center">[https://virtuozzo.com/openvz/?utm_source=Openvz.org&utm_medium=banner1&utm_campaign=OpenVZ https://openvz.org/i/vz-banner-b.png]</div></div>Kirhttps://wiki.openvz.org/index.php?title=User:Marymarks&diff=22503User:Marymarks2017-01-23T19:06:34Z<p>Kir: Creating user page for new user.</p>
<hr />
<div>This is Mary Marks, Partner Marketing Manager, Virtuozzo. I joined the Marketing team at Virtuozzo in October 2016 and support partners and OpenVZ.</div>Kirhttps://wiki.openvz.org/index.php?title=User:Ykargin&diff=22471User:Ykargin2016-12-15T09:55:57Z<p>Kir: Creating user page for new user.</p>
<hr />
<div>SDET in Virtuozzo since 2012. <br />
For urgent questions please feel free to contact me directly by email. <br />
<br />
Best regards, <br />
Y. Kargin</div>Kir