Return-Path: X-Original-To: apmail-cloudstack-users-archive@www.apache.org Delivered-To: apmail-cloudstack-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4D659C231 for ; Thu, 18 Jul 2013 15:47:32 +0000 (UTC) Received: (qmail 98999 invoked by uid 500); 18 Jul 2013 15:47:31 -0000 Delivered-To: apmail-cloudstack-users-archive@cloudstack.apache.org Received: (qmail 98645 invoked by uid 500); 18 Jul 2013 15:47:30 -0000 Mailing-List: contact users-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@cloudstack.apache.org Delivered-To: mailing list users@cloudstack.apache.org Received: (qmail 98636 invoked by uid 99); 18 Jul 2013 15:47:30 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Jul 2013 15:47:30 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED X-Spam-Check-By: apache.org Received-SPF: error (athena.apache.org: local policy) Received: from [74.125.149.153] (HELO na3sys009aog125.obsmtp.com) (74.125.149.153) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Jul 2013 15:47:24 +0000 Received: from mail-gg0-f169.google.com ([209.85.161.169]) (using TLSv1) by na3sys009aob125.postini.com ([74.125.148.12]) with SMTP ID DSNKUegN49PFPCc+pROet1JZc0DvY3nk8Smz@postini.com; Thu, 18 Jul 2013 08:47:04 PDT Received: by mail-gg0-f169.google.com with SMTP id b1so968697ggn.28 for ; Thu, 18 Jul 2013 08:46:43 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=date:from:to:subject:message-id:references:mime-version :content-type:content-disposition:content-transfer-encoding :in-reply-to:user-agent:x-gm-message-state; bh=Ogb2bUUuxjPB6VP/NRTG0FIkZBjL37Vs7jcPMHT4uk0=; b=aqIGvyuGfd+yw7IKd+BWw9Q/49nRtCGcm3BJ+3jLfjZ3LvO69jd1zmP4VycQgy+izM Oh1uD/WnEmyIS68Rd2KXGdUsr+tpLdbh5YY/Q+DfOlvbtRDeMc2XrTvsbTSkqrHfE+dM ItdBjz0hVD/cenYIjOU8800HxSudSYCU6gOAFwUJagR2jmvpQZG0YRY1GKGy0LYPl2i6 qyHPwG1g5lJ+WskUIeJqM2rHi0rgZumo04NJrZwof11RGHaiXM5LhkjQM3xMCemrohp3 FimC1Ia3uwNzuSLHlcYgOoY44PU3dM81M2N+aQvVZabFt+xzBnqbLJrFf9Sd302M01MG 3Jxw== X-Received: by 10.236.85.45 with SMTP id t33mr6020141yhe.211.1374162403025; Thu, 18 Jul 2013 08:46:43 -0700 (PDT) X-Received: by 10.236.85.45 with SMTP id t33mr6020130yhe.211.1374162402902; Thu, 18 Jul 2013 08:46:42 -0700 (PDT) Received: from localhost ([216.203.6.11]) by mx.google.com with ESMTPSA id e69sm15410794yhl.3.2013.07.18.08.46.41 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Thu, 18 Jul 2013 08:46:42 -0700 (PDT) Date: Thu, 18 Jul 2013 11:46:39 -0400 From: Chip Childers To: users@cloudstack.apache.org Subject: Re: Ceph RBD With Xen Server Message-ID: <20130718154639.GF50818@USLT-205755.sungardas.corp> References: <22dafc1f30187924a1fc573bb53c3138@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <22dafc1f30187924a1fc573bb53c3138@mail.gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Gm-Message-State: ALoCoQlzv22nAHZEt2Nlq6MttwtK5Uq/L4pNfA6O6dS4PfrO+dkIQT5mAMLh7PKztXVtAcOJ8nLkeBPL/wtneTxkHUgyJg2V/b5u2Ldb2oJogwcSqbdPMvMy1lB1EEYSIbI02eXrwpEYBN+JEYvMGgclU9dA77hr2dpaLtM6xtsAfe/YAgbzdp4= X-Virus-Checked: Checked by ClamAV on apache.org On Thu, Jul 18, 2013 at 03:49:48PM +0100, Adrian Lewis wrote: > Hi, > > > > First post and only just subscribed so not sure if this will connect up > with the existing thread but I’m very interested in XenServer and Ceph/RBD. > I understand that Wido has informally committed to building the > Xenserver/RBD glue when it is supported on XenServer (think this was in a > video I saw on youtube). With this in mind, I’m wondering if this is > something that could still be added to 4.2 based on the info in > http://xenserver.org/blog/entry/tech-preview-of-xenserver-libvirt-ceph.html. > I realise that it’s not ready yet on the XenServer side but is this > something that might make it to 4.2 in advance of the XenServer development > as opposed to waiting for 4.3? Can the Cloudstack side of things be > developed in advance of the Xenserver elements? I'll only answer with regard to the status of new features and 4.2. We have hit feature freeze for that release now, so if it's technically possible to build the feature ahead of XenServer it would end up in the next feature release of CloudStack (assuming that someone builds it).