Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 26A77D2B0 for ; Tue, 21 May 2013 21:14:17 +0000 (UTC) Received: (qmail 1710 invoked by uid 500); 21 May 2013 21:14:17 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 1672 invoked by uid 500); 21 May 2013 21:14:16 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 1664 invoked by uid 99); 21 May 2013 21:14:16 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 May 2013 21:14:16 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW X-Spam-Check-By: apache.org Received-SPF: unknown (nike.apache.org: error in processing during lookup of fgaudreault@cloudops.com) Received: from [209.85.160.172] (HELO mail-gh0-f172.google.com) (209.85.160.172) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 May 2013 21:14:11 +0000 Received: by mail-gh0-f172.google.com with SMTP id r18so381757ghr.17 for ; Tue, 21 May 2013 14:13:50 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=slNfrWFuSt8r3wOwM685uUGOWNu8GWpQMLga5l3EE3A=; b=QtYsX2p1uhy7KdEQKbHrav9P/XtP/gH/D3ZoaVQ1rqBehKGX6UsUvSqlLI+iQt4rZR /tro8/hU7U6QqSp9CcvaoxAF7mmYWfvXshbErRkFAh8c+E3UoaTTv+HEuTL5bAWE5crU YlFfiNC4PFMLKWxoNu6rPsnQ6nkoOxG2TFZgrWt8QGn9uocX36Z1+LhMa1LKzEGx/YWI 7Njkt7Anwz2TkKFBYc0kTHa2dokq/b1fWjUoFppNtMF1xe6F+nk62ZyRiS0qvvzOuUhw 3aHds5PdLu3UNyLJAa6g9HDOrEjdNZfTpfiAeT7f8+2olKsts2Cj+s8HnUNjCRLHJC0p vAmA== X-Received: by 10.236.29.202 with SMTP id i50mr3214306yha.82.1369170830090; Tue, 21 May 2013 14:13:50 -0700 (PDT) Received: from Francoiss-MacBook-Pro-3.local ([38.108.74.28]) by mx.google.com with ESMTPSA id t41sm6383713yhh.11.2013.05.21.14.13.48 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 21 May 2013 14:13:49 -0700 (PDT) Message-ID: <519BE38B.3070806@cloudops.com> Date: Tue, 21 May 2013 17:13:47 -0400 From: Francois Gaudreault Reply-To: fgaudreault@cloudops.com User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: dev@cloudstack.apache.org CC: Chip Childers Subject: Re: [VOTE] Move forward with 4.1 without a Xen-specific fix for CLOUDSTACK-2492? References: <20130520201514.GP56667@USLT-205755.sungardas.corp> <20130521202056.GG56667@USLT-205755.sungardas.corp> In-Reply-To: <20130521202056.GG56667@USLT-205755.sungardas.corp> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Gm-Message-State: ALoCoQmVVRMhnlglhCAxoLAhsdYZP1zUedzSQr+iA5tDt8lgqMytnrssTaH9Zm74Tom9mY0PAbTw X-Virus-Checked: Checked by ClamAV on apache.org I am not sure if I am allowed to vote here but... I guess the SSVM has been built using HVM instead of PV? If the SSVM is PV, it should sync domU -> dom0. It might also require some hotfixes on the XenServer side if you are using XS 6.0.2 (hotfix 18) that addresses some clock drift issues. Because of the potential impact on other APIs (swift?), I would say: -1. On 2013-05-21 4:20 PM, Chip Childers wrote: > On Mon, May 20, 2013 at 04:15:14PM -0400, Chip Childers wrote: >> All, >> >> As discussed on another thread [1], we identified a bug >> (CLOUDSTACK-2492) in the current 3.x system VMs, where the System VMs >> are not configured to sync their time with either the host HV or an NTP >> service. That bug affects the system VMs for all three primary HVs (KVM, >> Xen and vSphere). Patches have been committed addressing vSphere and >> KVM. It appears that a correction for Xen would require the re-build of >> a system VM image and a full round of regression testing that image. >> >> Given that the discussion thread has not resulted in a consensus on this >> issue, I unfortunately believe that the only path forward is to call for >> a formal VOTE. >> >> Please respond with one of the following: >> >> +1: proceed with 4.1 without the Xen portion of CLOUDSTACK-2492 being resolved >> +0: don't care one way or the other >> -1: do *not* proceed with any further 4.1 release candidates until CLOUDSTACK-2492 has been fully resolved >> >> -chip >> >> [1] http://markmail.org/message/rw7vciq3r33biasb > We need more people to voice their opinions here please. > > -- Francois Gaudreault Architecte de Solution Cloud | Cloud Solutions Architect fgaudreault@cloudops.com 514-629-6775 - - - CloudOps 420 rue Guy Montr�al QC H3J 1S6 www.cloudops.com @CloudOps_