ALT Linux Team development discussions
 help / color / mirror / Atom feed
From: Gleb Fotengauer-Malinovskiy <glebfm@altlinux.org>
To: "Павел Исопенко" <master@pauli.ru>,
	"Евгений Терешков" <evg-krsk@yandex.ru>
Cc: ALT Linux Team development discussions <devel@lists.altlinux.org>
Subject: Re: [devel] Parallels Virtuozzo
Date: Thu, 7 May 2015 16:59:21 +0300
Message-ID: <20150507135920.GG3470@glebfm.cloud.tilaa.com> (raw)
In-Reply-To: <554B6B1A.9000106@pauli.ru>

[-- Attachment #1: Type: text/plain, Size: 1590 bytes --]

Hi,

On Thu, May 07, 2015 at 04:39:38PM +0300, Павел Исопенко wrote:
> Прошла информация об открытии Parallels Virtuozzo.
> Какие будут соображения? Или кто-то из наших уже занимается?

К сожалению, это пока только ядро.
Могу отправить в Сизиф, если надо. Сейчас лежит в сторонке готовый пакет.

> Ищу заинтересованных в теме. Имею потенциального клиента.
> Ковыряться в одиночку смысла не вижу, другое дело если в компании.

На сколько я понимаю, vzctl для этого ядра пока не был опубликован:

http://lists.openvz.org/pipermail/announce/2015-April/000579.html
 On Mon, Apr 27, 2015 at 01:05:29PM +0300, Sergey Bronnikov wrote:
 > IMPORTANT: The work on the new kernel is still in progress, in particular, we're
 > still changing the Container management API. At the same time, we haven't yet
 > finished implementing support for the old kernel API, so you can't manage
 > Containers with the existing OpenVZ vzctl utility. This might be a good task to
 > start with if you're willing to contribute: implement into the new kernel the
 > compatibility with the old kernel API to make the current vzctl work.  New
 > userspace utilities, including new vzctl, which will work via the new kernel
 > API, will be published later.

-- 
glebfm

[-- Attachment #2: Type: application/pgp-signature, Size: 181 bytes --]

      parent reply	other threads:[~2015-05-07 13:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-07 13:47 ` Евгений Терешков
2015-05-07 13:59 ` Gleb Fotengauer-Malinovskiy [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150507135920.GG3470@glebfm.cloud.tilaa.com \
    --to=glebfm@altlinux.org \
    --cc=devel@lists.altlinux.org \
    --cc=evg-krsk@yandex.ru \
    --cc=master@pauli.ru \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

ALT Linux Team development discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
		devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
	public-inbox-index devel

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git