Return-Path: X-Original-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5DC8CE471 for ; Mon, 7 Jan 2013 21:23:53 +0000 (UTC) Received: (qmail 23888 invoked by uid 500); 7 Jan 2013 21:23:53 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 23857 invoked by uid 500); 7 Jan 2013 21:23:52 -0000 Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-dev@incubator.apache.org Delivered-To: mailing list cloudstack-dev@incubator.apache.org Received: (qmail 23845 invoked by uid 99); 7 Jan 2013 21:23:52 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Jan 2013 21:23:52 +0000 X-ASF-Spam-Status: No, hits=-1.6 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [74.125.149.83] (HELO na3sys009aog134.obsmtp.com) (74.125.149.83) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Jan 2013 21:23:45 +0000 Received: from mail-we0-f199.google.com ([74.125.82.199]) (using TLSv1) by na3sys009aob134.postini.com ([74.125.148.12]) with SMTP ID DSNKUOs8y4hGHuNiTKnRVXBSzH2vp9ec7kab@postini.com; Mon, 07 Jan 2013 13:23:25 PST Received: by mail-we0-f199.google.com with SMTP id t57so17165316wey.6 for ; Mon, 07 Jan 2013 13:23:22 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:date:message-id :subject:from:to:content-type:x-gm-message-state; bh=2vB+2XGazSrOmY5LuuOLsl0As2xWmgCmwXBIXSprOz0=; b=k/EyW16zmy3zKDnKgTR0iKfZAvRMVM3Kwv1d4RWNrpU9o+PtEc11UVveuGOBh/kqC5 nkmBNCece7ZprQFLPHhjMQF//d2SiqFpHWl0LZb8lo7N4yh9wwOxsWLFXp0iQMwXCQ7O 05sGe08oiCMvrgShA1lCb72vda0U3PxWnqdUxoaTrgyz7Ed4yNMXWVQ75zhjiaLOF0wB GtIt6zjG062LkWKttG9SfPHtXayCMx0fxDIPDNbt0evVy5i/AehGAccX7GmUw92xjkON SS5qRMQM1TrB+seFTRqnAGFZwvOeUf8mzoy5S06Sz2pge+nMO52AJQygzf+YeH9dnSvN O+/w== X-Received: by 10.194.23.37 with SMTP id j5mr97843821wjf.28.1357593802452; Mon, 07 Jan 2013 13:23:22 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.23.37 with SMTP id j5mr97843813wjf.28.1357593802369; Mon, 07 Jan 2013 13:23:22 -0800 (PST) Received: by 10.194.37.68 with HTTP; Mon, 7 Jan 2013 13:23:22 -0800 (PST) In-Reply-To: References: Date: Mon, 7 Jan 2013 16:23:22 -0500 Message-ID: Subject: Re: Adding LXC support to Cloudstack From: Chip Childers To: "cloudstack-dev@incubator.apache.org" Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQkdKsYjO6r5t3ge1ZL6ZwHqUK6XYynXKKwddOWUuGy4zuQEQIOslqZ5iTnccxcsL7OZoiYLruzwJAIzWtAONlqPoPxmezU4EzgdX4+3lMtuvJ1xbxKdEWaZmQx8/ExaZKp5dgMkO6lM+IWtVfandgNPkegKinpQGiY4yT5I2/ZFZJuXcgPLm4gRiZqUXN6u6g9b1b2F X-Virus-Checked: Checked by ClamAV on apache.org On Mon, Jan 7, 2013 at 4:15 PM, Alex Karasulu wrote: > On Mon, Jan 7, 2013 at 11:13 PM, Alex Karasulu wrote: > >> Hi Phong, >> >> On Mon, Jan 7, 2013 at 10:02 PM, Phong Nguyen wrote: >> >>> Hi, >>> >>> We are interested in adding LXC support to Cloudstack. >> >> >> I've also been interested in Cloudstack support for LXC. I checked a few >> days ago for it and was disappointed when I could not find it but found >> support for it in OpenStack instead :P. I wanted to inquire about adding >> LXC support thinking this might be a good starting point for my getting >> involved in the code. At this point, I have nothing further to contribute >> besides the link you already found, but I thought if others saw more people >> interested then LXC support might be considered. >> >> > Here's a bit more chatter on this topic but as we see it's not been > implemented. Rip for the picking ... > > http://goo.gl/x60At > I'll echo what Kevin said on that thread. If you're interested in building it, I'm interested in having it! We're still learning how to do our feature proposal process as a community, but generally we are following the process here: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Adding+new+features+and+design+documents If we have a consensus around adding support for LXC, then the next step would be to propose it via a functional spec. Purely from a release planning point of view, I'd suggest that you add the spec as a child page of our "uncommitted" design page: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Design+Documents+Not+Committed+to+a+Release Also one other thing to note: the community has two major refactoring merge activities that we expect to happen this week / early next week (first, the api_refactoring branch, then the javelin branch). You should be aware of this, but I doubt it would impact the design much. If either of you decide to take this on (and perhaps collaboration would be in order), please do share your thoughts, questions, concerns with the list! We're happy to help with the architecture and our community processes. -chip > >> I've searched around >>> for container support for Cloudstack and was able to find one posting >>> related to OpenVZ (over a year ago): >>> >>> http://sourceforge.net/mailarchive/message.php?msg_id=28030821 >>> >> >> BTW OpenVZ is great stuff but I've found the fact that you need a custom >> Kernel a bit of a problem. LXC is much better in this sense since it's >> already present in every kernel past 2.6.26 (or 2.6.29?) but that's besides >> the point of this thread. Sorry for digressing. >> >> Is there any current, on-going, or future work planned in this area? Are >>> there any architectural changes since then that would affect the >>> suggestions in this posting? Any other suggestions greatly appreciated. >>> >>> >> I too am interested in these details. >> >> Thanks, >> Alex >> >> > > > -- > Best Regards, > -- Alex