All of lore.kernel.org
 help / color / mirror / Atom feed
From: Whit Blauvelt <whit-M6G8SDWvnhfby3iVrkZq2A@public.gmane.org>
To: Matt Helsley <matthltc-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org,
	Enrico Weigelt <weigelt-EU+a56NjgY8@public.gmane.org>
Subject: Re: Containers vs. OpenVZ
Date: Tue, 17 Aug 2010 20:56:56 -0400	[thread overview]
Message-ID: <20100818005656.GA2070@transpect.com> (raw)
In-Reply-To: <20100818002416.GG3648-52DBMbEzqgQ/wnmkkaCWp/UQ3DHhIser@public.gmane.org>

As someone who's not running either, but was sampling both about a month
back, my experience was (1) the current and next-to-latest openvz patches
produced kernels which couldn't really run openvz - it crashed - and it took
a couple of weeks to get a response to my bug report on that, while (2) lxc
has a very responsive development team, when I hit bugs there too, but it's
maybe 6 months out of being mature enough to really pay off for a sysadmin
of mid-level skills like me. If you're an ace, I'm sure you can get good use
now.

For what little my short-acquaintance comparison's worth, the openvz bugs
I hit were a lot more serious. It's doubtless presently more
feature-complete, when it works. But there's a lot more momentum in lxc,
plus it's mainline in the kernel so it's future's brighter.

Meanwhile I've settled on kvm, but can see some real uses for lxc in the
not-far future.

Whit

  parent reply	other threads:[~2010-08-18  0:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-17 10:33 Containers vs. OpenVZ Enrico Weigelt
     [not found] ` <20100817103339.GA8495-q9I3ByPDOfiE+EvaaNYduQ@public.gmane.org>
2010-08-18  0:24   ` Matt Helsley
     [not found]     ` <20100818002416.GG3648-52DBMbEzqgQ/wnmkkaCWp/UQ3DHhIser@public.gmane.org>
2010-08-18  0:56       ` Whit Blauvelt [this message]
2010-08-18  0:59       ` Oren Laadan
     [not found]         ` <4C6B3082.2070802-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2010-08-18 10:42           ` Marc Aymerich
     [not found]             ` <AANLkTinLMVV21pW_icDriWbrZ1U8NgfKYWMhFLBD5XS--JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-08-18 10:48               ` Marc Aymerich
     [not found]                 ` <AANLkTimHdaZnB-q6_XgoAwxKAwQKgAMtz0_J78MBDBbp-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-08-18 16:00                   ` Oren Laadan
2010-08-18 17:02               ` Matt Helsley
     [not found]                 ` <20100818170256.GA3642-52DBMbEzqgQ/wnmkkaCWp/UQ3DHhIser@public.gmane.org>
2010-08-23  7:44                   ` Pavel Emelyanov
     [not found]                     ` <4C7226EA.5020600-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2010-08-23  9:08                       ` [Devel] " Peter Volkov
2010-08-23  9:38                         ` Pavel Emelyanov

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=20100818005656.GA2070@transpect.com \
    --to=whit-m6g8sdwvnhfby3ivrkzq2a@public.gmane.org \
    --cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
    --cc=matthltc-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
    --cc=weigelt-EU+a56NjgY8@public.gmane.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.