From xen-api-bounces@lists.xen.org Tue Jul 01 09:53:42 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 01 Jul 2014 09:53:42 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X1uko-00070r-24; Tue, 01 Jul 2014 09:53:34 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <lars.kurth.xen@gmail.com>)
	id 1X1ukm-00070d-NQ; Tue, 01 Jul 2014 09:53:32 +0000
Received: from [85.158.137.68:50325] by server-9.bemta-3.messagelabs.com id
	FF/49-09496-B1582B35; Tue, 01 Jul 2014 09:53:31 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-3.tower-31.messagelabs.com!1404208410!13350730!1
X-Originating-IP: [209.85.212.181]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 13701 invoked from network); 1 Jul 2014 09:53:31 -0000
Received: from mail-wi0-f181.google.com (HELO mail-wi0-f181.google.com)
	(209.85.212.181)
	by server-3.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	1 Jul 2014 09:53:31 -0000
Received: by mail-wi0-f181.google.com with SMTP id n3so7445683wiv.14
	for <multiple recipients>; Tue, 01 Jul 2014 02:53:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=sender:message-id:date:from:reply-to:user-agent:mime-version:to
	:subject:content-type:content-transfer-encoding;
	bh=wvxthEZHCC7qwYjAoi/vOC6owbXT/mi8i/fiyzoSUzc=;
	b=GlgbDoM3SRHMPQAscVykqDO7zXU6qxaOZSzNNLLzR9FUfSTW7f7bKqaprmq75r8U0Z
	vGRUOIYv07HzA0WeRzfQQNswXMRsOsBMd4QkNT0Ii2dCP/wGasu6zvfbQaQWrNYdz+Kk
	wNnJkJMHVqGxP3T+rHD8FPoOWIw5CK0ruKnxpZiIvSjDrxyTWhQUV6AjI3PM4GyDwzrc
	YdQkbQO98uk9F1JhfoqvJ50mEuRVbgXAk5XI86TBn2xEpQgPyU+rdDkO40Nwr8I/D6I5
	ZRfWME6TcnBn9P+LZC1Clk8ugyEa8E0dOSdIgf6Z0cSxVrna08ozWVutcXalAlChb+OQ
	Cmhw==
X-Received: by 10.180.96.97 with SMTP id dr1mr35726113wib.19.1404208410804;
	Tue, 01 Jul 2014 02:53:30 -0700 (PDT)
Received: from [172.16.25.10] (97e5a5cd.skybroadband.com. [151.229.165.205])
	by mx.google.com with ESMTPSA id d12sm13549256wjx.0.2014.07.01.02.53.28
	for <multiple recipients>
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Tue, 01 Jul 2014 02:53:30 -0700 (PDT)
Message-ID: <53B28517.9020807@xen.org>
Date: Tue, 01 Jul 2014 10:53:27 +0100
From: Lars Kurth <lars.kurth@xen.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>, 
	"mirageos-devel@lists.xenproject.org"
	<mirageos-devel@lists.xenproject.org>, 
	"xen-api@lists.xen.org" <xen-api@lists.xen.org>, 
	Alex Agizim <alex.agizim@globallogic.com>,
	Artem Mygaiev <artem.mygaiev@globallogic.com>
Subject: [Xen-API] [For Community Review] Embedded and Automotive PV Drivers
 Sub-Project Proposal (deadline July 11th)
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

Hi all,

the "Embedded and Automotive PV Drivers Sub-Project Proposal" (see 
http://wiki.xenproject.org/wiki/Embedded_and_Automotive_PV_Drivers_Project_Proposal) 
is now open for community review. Please provide feedback by replying to 
this thread or using the Comment feature (see 
http://wiki.xenproject.org/wiki/Template:Comment) using 
"{{comment|~~~~}} My comment" on the relevant section of the wiki page.

I extended the deadline by a few days, to account for the 4th of July 
holidays/vacation in the USA

Best Regards
Lars

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

From xen-api-bounces@lists.xen.org Tue Jul 01 09:53:42 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 01 Jul 2014 09:53:42 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X1uko-00070r-24; Tue, 01 Jul 2014 09:53:34 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <lars.kurth.xen@gmail.com>)
	id 1X1ukm-00070d-NQ; Tue, 01 Jul 2014 09:53:32 +0000
Received: from [85.158.137.68:50325] by server-9.bemta-3.messagelabs.com id
	FF/49-09496-B1582B35; Tue, 01 Jul 2014 09:53:31 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-3.tower-31.messagelabs.com!1404208410!13350730!1
X-Originating-IP: [209.85.212.181]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 13701 invoked from network); 1 Jul 2014 09:53:31 -0000
Received: from mail-wi0-f181.google.com (HELO mail-wi0-f181.google.com)
	(209.85.212.181)
	by server-3.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	1 Jul 2014 09:53:31 -0000
Received: by mail-wi0-f181.google.com with SMTP id n3so7445683wiv.14
	for <multiple recipients>; Tue, 01 Jul 2014 02:53:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=sender:message-id:date:from:reply-to:user-agent:mime-version:to
	:subject:content-type:content-transfer-encoding;
	bh=wvxthEZHCC7qwYjAoi/vOC6owbXT/mi8i/fiyzoSUzc=;
	b=GlgbDoM3SRHMPQAscVykqDO7zXU6qxaOZSzNNLLzR9FUfSTW7f7bKqaprmq75r8U0Z
	vGRUOIYv07HzA0WeRzfQQNswXMRsOsBMd4QkNT0Ii2dCP/wGasu6zvfbQaQWrNYdz+Kk
	wNnJkJMHVqGxP3T+rHD8FPoOWIw5CK0ruKnxpZiIvSjDrxyTWhQUV6AjI3PM4GyDwzrc
	YdQkbQO98uk9F1JhfoqvJ50mEuRVbgXAk5XI86TBn2xEpQgPyU+rdDkO40Nwr8I/D6I5
	ZRfWME6TcnBn9P+LZC1Clk8ugyEa8E0dOSdIgf6Z0cSxVrna08ozWVutcXalAlChb+OQ
	Cmhw==
X-Received: by 10.180.96.97 with SMTP id dr1mr35726113wib.19.1404208410804;
	Tue, 01 Jul 2014 02:53:30 -0700 (PDT)
Received: from [172.16.25.10] (97e5a5cd.skybroadband.com. [151.229.165.205])
	by mx.google.com with ESMTPSA id d12sm13549256wjx.0.2014.07.01.02.53.28
	for <multiple recipients>
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Tue, 01 Jul 2014 02:53:30 -0700 (PDT)
Message-ID: <53B28517.9020807@xen.org>
Date: Tue, 01 Jul 2014 10:53:27 +0100
From: Lars Kurth <lars.kurth@xen.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>, 
	"mirageos-devel@lists.xenproject.org"
	<mirageos-devel@lists.xenproject.org>, 
	"xen-api@lists.xen.org" <xen-api@lists.xen.org>, 
	Alex Agizim <alex.agizim@globallogic.com>,
	Artem Mygaiev <artem.mygaiev@globallogic.com>
Subject: [Xen-API] [For Community Review] Embedded and Automotive PV Drivers
 Sub-Project Proposal (deadline July 11th)
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

Hi all,

the "Embedded and Automotive PV Drivers Sub-Project Proposal" (see 
http://wiki.xenproject.org/wiki/Embedded_and_Automotive_PV_Drivers_Project_Proposal) 
is now open for community review. Please provide feedback by replying to 
this thread or using the Comment feature (see 
http://wiki.xenproject.org/wiki/Template:Comment) using 
"{{comment|~~~~}} My comment" on the relevant section of the wiki page.

I extended the deadline by a few days, to account for the 4th of July 
holidays/vacation in the USA

Best Regards
Lars

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

From xen-api-bounces@lists.xen.org Tue Jul 01 13:57:15 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 01 Jul 2014 13:57:15 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X1yYU-00036M-Sg; Tue, 01 Jul 2014 13:57:06 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <anil@recoil.org>) id 1X1yYO-00035x-7H
	for xen-api@lists.xen.org; Tue, 01 Jul 2014 13:57:00 +0000
Received: from [85.158.139.211:50809] by server-15.bemta-5.messagelabs.com id
	DD/39-19516-B2EB2B35; Tue, 01 Jul 2014 13:56:59 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-13.tower-206.messagelabs.com!1404223018!13018992!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 24754 invoked from network); 1 Jul 2014 13:56:58 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-13.tower-206.messagelabs.com with SMTP;
	1 Jul 2014 13:56:58 -0000
Received: (qmail 5180 invoked by uid 634); 1 Jul 2014 13:56:57 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from athedsl-297430.home.otenet.gr (HELO [10.100.22.69])
	(85.73.209.116)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Tue, 01 Jul 2014 14:56:57 +0100
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: Anil Madhavapeddy <anil@recoil.org>
In-Reply-To: <53B28517.9020807@xen.org>
Date: Tue, 1 Jul 2014 16:56:40 +0300
Message-Id: <75D6B875-6AF4-4176-B530-447D47B2A18A@recoil.org>
References: <53B28517.9020807@xen.org>
To: lars.kurth@xen.org
X-Mailer: Apple Mail (2.1878.2)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: "xen-api@lists.xen.org" <xen-api@lists.xen.org>,
	Artem Mygaiev <artem.mygaiev@globallogic.com>,
	Alex Agizim <alex.agizim@globallogic.com>,
	"mirageos-devel@lists.xenproject.org"
	<mirageos-devel@lists.xenproject.org>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [Xen-API] [Xen-devel] [For Community Review] Embedded and
	Automotive PV Drivers Sub-Project Proposal (deadline July 11th)
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org


On 1 Jul 2014, at 12:53, Lars Kurth <lars.kurth@xen.org> wrote:
> Hi all,
> 
> the "Embedded and Automotive PV Drivers Sub-Project Proposal" (see http://wiki.xenproject.org/wiki/Embedded_and_Automotive_PV_Drivers_Project_Proposal) is now open for community review. Please provide feedback by replying to this thread or using the Comment feature (see http://wiki.xenproject.org/wiki/Template:Comment) using "{{comment|~~~~}} My comment" on the relevant section of the wiki page.

Looks great! A few comments:

- "pv_fb driver provide audio driver back- " => audio should be "framebuffer"

- Several of the drivers overlap with existing front/back drivers (for example, the pv_usb one).  Is there a plan to merge these, or at least document the differences between QNX and the Linux/BSD versions of the relevant ring protocols?

- Not sure why the pv_gpu drivers has a "lnx-alsa-be/" entry in the drivers. Might be a c&p error.

cheers,
ANil

> 
> I extended the deadline by a few days, to account for the 4th of July holidays/vacation in the USA
> 
> Best Regards
> Lars
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
> 


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

From xen-api-bounces@lists.xen.org Tue Jul 01 13:57:15 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 01 Jul 2014 13:57:15 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X1yYU-00036M-Sg; Tue, 01 Jul 2014 13:57:06 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <anil@recoil.org>) id 1X1yYO-00035x-7H
	for xen-api@lists.xen.org; Tue, 01 Jul 2014 13:57:00 +0000
Received: from [85.158.139.211:50809] by server-15.bemta-5.messagelabs.com id
	DD/39-19516-B2EB2B35; Tue, 01 Jul 2014 13:56:59 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-13.tower-206.messagelabs.com!1404223018!13018992!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 24754 invoked from network); 1 Jul 2014 13:56:58 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-13.tower-206.messagelabs.com with SMTP;
	1 Jul 2014 13:56:58 -0000
Received: (qmail 5180 invoked by uid 634); 1 Jul 2014 13:56:57 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from athedsl-297430.home.otenet.gr (HELO [10.100.22.69])
	(85.73.209.116)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Tue, 01 Jul 2014 14:56:57 +0100
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: Anil Madhavapeddy <anil@recoil.org>
In-Reply-To: <53B28517.9020807@xen.org>
Date: Tue, 1 Jul 2014 16:56:40 +0300
Message-Id: <75D6B875-6AF4-4176-B530-447D47B2A18A@recoil.org>
References: <53B28517.9020807@xen.org>
To: lars.kurth@xen.org
X-Mailer: Apple Mail (2.1878.2)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: "xen-api@lists.xen.org" <xen-api@lists.xen.org>,
	Artem Mygaiev <artem.mygaiev@globallogic.com>,
	Alex Agizim <alex.agizim@globallogic.com>,
	"mirageos-devel@lists.xenproject.org"
	<mirageos-devel@lists.xenproject.org>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [Xen-API] [Xen-devel] [For Community Review] Embedded and
	Automotive PV Drivers Sub-Project Proposal (deadline July 11th)
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org


On 1 Jul 2014, at 12:53, Lars Kurth <lars.kurth@xen.org> wrote:
> Hi all,
> 
> the "Embedded and Automotive PV Drivers Sub-Project Proposal" (see http://wiki.xenproject.org/wiki/Embedded_and_Automotive_PV_Drivers_Project_Proposal) is now open for community review. Please provide feedback by replying to this thread or using the Comment feature (see http://wiki.xenproject.org/wiki/Template:Comment) using "{{comment|~~~~}} My comment" on the relevant section of the wiki page.

Looks great! A few comments:

- "pv_fb driver provide audio driver back- " => audio should be "framebuffer"

- Several of the drivers overlap with existing front/back drivers (for example, the pv_usb one).  Is there a plan to merge these, or at least document the differences between QNX and the Linux/BSD versions of the relevant ring protocols?

- Not sure why the pv_gpu drivers has a "lnx-alsa-be/" entry in the drivers. Might be a c&p error.

cheers,
ANil

> 
> I extended the deadline by a few days, to account for the 4th of July holidays/vacation in the USA
> 
> Best Regards
> Lars
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
> 


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

From xen-api-bounces@lists.xen.org Tue Jul 01 15:21:13 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 01 Jul 2014 15:21:13 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X1zrk-0002yI-5Z; Tue, 01 Jul 2014 15:21:04 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <anil@recoil.org>) id 1X1zrg-0002y2-Ic
	for xen-api@lists.xen.org; Tue, 01 Jul 2014 15:21:00 +0000
Received: from [85.158.137.68:18665] by server-9.bemta-3.messagelabs.com id
	3F/9B-09496-BD1D2B35; Tue, 01 Jul 2014 15:20:59 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-14.tower-31.messagelabs.com!1404228058!10943488!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 25333 invoked from network); 1 Jul 2014 15:20:58 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-14.tower-31.messagelabs.com with SMTP;
	1 Jul 2014 15:20:58 -0000
Received: (qmail 1842 invoked by uid 634); 1 Jul 2014 15:20:58 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from athedsl-297430.home.otenet.gr (HELO [10.100.22.69])
	(85.73.209.116)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Tue, 01 Jul 2014 16:20:58 +0100
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: Anil Madhavapeddy <anil@recoil.org>
In-Reply-To: <0CF8E334-9DB6-44A8-B327-3644C14D92EA@cam.ac.uk>
Date: Tue, 1 Jul 2014 18:20:51 +0300
Message-Id: <0521ACDC-1E09-4506-B054-588DD4E17D70@recoil.org>
References: <5396D482.6000706@eu.citrix.com>
	<0CF8E334-9DB6-44A8-B327-3644C14D92EA@cam.ac.uk>
To: Amir M Chaudhry <amc79@cam.ac.uk>
X-Mailer: Apple Mail (2.1878.2)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: Lars Kurth <lars.kurth@citrix.com>, David Scott <Dave.Scott@citrix.com>,
	"mirageos-devel@lists.xenproject.org"
	<mirageos-devel@lists.xenproject.org>, xen-api@lists.xen.org
Subject: Re: [Xen-API] [MirageOS-devel] Xapi project repositories
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

On 1 Jul 2014, at 14:08, Amir Chaudhry <amc79@cam.ac.uk> wrote:

> Dave, could we please move the three remaining libraries to the Mirage org as soon as possible please?
> It's a fairly trivial process and is transparent to end users.  I've even included links that should take you to the exact page where you can click the transfer button. :)
> If there's some blocker to this, please let me know.

I believe what's blocking the xenstore transfer is a refactoring to separate out the bits intended for xen upstream to the core libraries used by Mirage/xapi/etc.  From the Mirage perspective, I'm happy for this split to be done 'in-tree', but Dave has the final call on this since he's actually doing the hard work :-) 

-anil
_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

From xen-api-bounces@lists.xen.org Tue Jul 01 15:21:13 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 01 Jul 2014 15:21:13 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X1zrk-0002yI-5Z; Tue, 01 Jul 2014 15:21:04 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <anil@recoil.org>) id 1X1zrg-0002y2-Ic
	for xen-api@lists.xen.org; Tue, 01 Jul 2014 15:21:00 +0000
Received: from [85.158.137.68:18665] by server-9.bemta-3.messagelabs.com id
	3F/9B-09496-BD1D2B35; Tue, 01 Jul 2014 15:20:59 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-14.tower-31.messagelabs.com!1404228058!10943488!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 25333 invoked from network); 1 Jul 2014 15:20:58 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-14.tower-31.messagelabs.com with SMTP;
	1 Jul 2014 15:20:58 -0000
Received: (qmail 1842 invoked by uid 634); 1 Jul 2014 15:20:58 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from athedsl-297430.home.otenet.gr (HELO [10.100.22.69])
	(85.73.209.116)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Tue, 01 Jul 2014 16:20:58 +0100
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: Anil Madhavapeddy <anil@recoil.org>
In-Reply-To: <0CF8E334-9DB6-44A8-B327-3644C14D92EA@cam.ac.uk>
Date: Tue, 1 Jul 2014 18:20:51 +0300
Message-Id: <0521ACDC-1E09-4506-B054-588DD4E17D70@recoil.org>
References: <5396D482.6000706@eu.citrix.com>
	<0CF8E334-9DB6-44A8-B327-3644C14D92EA@cam.ac.uk>
To: Amir M Chaudhry <amc79@cam.ac.uk>
X-Mailer: Apple Mail (2.1878.2)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: Lars Kurth <lars.kurth@citrix.com>, David Scott <Dave.Scott@citrix.com>,
	"mirageos-devel@lists.xenproject.org"
	<mirageos-devel@lists.xenproject.org>, xen-api@lists.xen.org
Subject: Re: [Xen-API] [MirageOS-devel] Xapi project repositories
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

On 1 Jul 2014, at 14:08, Amir Chaudhry <amc79@cam.ac.uk> wrote:

> Dave, could we please move the three remaining libraries to the Mirage org as soon as possible please?
> It's a fairly trivial process and is transparent to end users.  I've even included links that should take you to the exact page where you can click the transfer button. :)
> If there's some blocker to this, please let me know.

I believe what's blocking the xenstore transfer is a refactoring to separate out the bits intended for xen upstream to the core libraries used by Mirage/xapi/etc.  From the Mirage perspective, I'm happy for this split to be done 'in-tree', but Dave has the final call on this since he's actually doing the hard work :-) 

-anil
_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

From xen-api-bounces@lists.xen.org Tue Jul 01 15:45:37 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 01 Jul 2014 15:45:37 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X20FQ-0004VS-8q; Tue, 01 Jul 2014 15:45:32 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <amc79@cam.ac.uk>) id 1X1vvA-0002CT-2G
	for xen-api@lists.xen.org; Tue, 01 Jul 2014 11:08:20 +0000
Received: from [85.158.139.211:28224] by server-16.bemta-5.messagelabs.com id
	2F/11-18862-3A692B35; Tue, 01 Jul 2014 11:08:19 +0000
X-Env-Sender: amc79@cam.ac.uk
X-Msg-Ref: server-9.tower-206.messagelabs.com!1404212898!12952955!1
X-Originating-IP: [131.111.8.152]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MiA9PiA4MDU1Mw==\n
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 26803 invoked from network); 1 Jul 2014 11:08:18 -0000
Received: from ppsw-52.csi.cam.ac.uk (HELO ppsw-52.csi.cam.ac.uk)
	(131.111.8.152)
	by server-9.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 1 Jul 2014 11:08:18 -0000
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from m.cb1.com ([217.155.139.150]:65182 helo=[192.168.1.187])
	by ppsw-52.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:587)
	with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128)
	id 1X1vv7-0008As-EV (Exim 4.82_3-c0e5623)
	(return-path <amc79@cam.ac.uk>); Tue, 01 Jul 2014 12:08:17 +0100
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Amir Chaudhry <amc79@cam.ac.uk>
In-Reply-To: <5396D482.6000706@eu.citrix.com>
Date: Tue, 1 Jul 2014 12:08:17 +0100
Message-Id: <0CF8E334-9DB6-44A8-B327-3644C14D92EA@cam.ac.uk>
References: <5396D482.6000706@eu.citrix.com>
To: Jon Ludlam <jonathan.ludlam@eu.citrix.com>, xen-api@lists.xen.org,
	David Scott <Dave.Scott@citrix.com>, "mirageos-devel@lists.xenproject.org"
	<mirageos-devel@lists.xenproject.org>, Lars Kurth <lars.kurth@citrix.com>
X-Mailer: Apple Mail (2.1510)
X-Mailman-Approved-At: Tue, 01 Jul 2014 15:45:31 +0000
Subject: Re: [Xen-API] [MirageOS-devel] Xapi project repositories
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

Hi folks,

Since the Mirage release is fast approaching, I'd like to get the repo transfers in order.
Extracting from Jon's email below, here is where things stand with respect to the Mirage libs.

    *ocaml-xenstore*
    xapi-project is the current root
    An admin must initiate transfer to the Mirage org
    https://github.com/xapi-project/ocaml-xenstore/settings

    *ocaml-xenstore-xen*
    xapi-project is the current root
    An admin must initiate transfer to the Mirage org
    https://github.com/xapi-project/ocaml-xenstore-xen/settings

    *ocaml-xenstore-clients*
    djs55 is the current root
    Dave to transfer his personal repo to the Mirage org
    https://github.com/djs55/ocaml-xenstore-clients/settings

    *ocaml-gnt*
    Already transferred

    *ocaml-evtchn*
    Already transferred

Dave, could we please move the three remaining libraries to the Mirage org as soon as possible please?
It's a fairly trivial process and is transparent to end users.  I've even included links that should take you to the exact page where you can click the transfer button. :)
If there's some blocker to this, please let me know.

Best wishes,
Amir


On 10 Jun 2014, at 10:48, Jon Ludlam <jonathan.ludlam@eu.citrix.com> wrote:

> Hi all,
> 
> In preparing for the 2.0 release, it's become increasingly obvious that
> we really need to tidy up the xapi-project org on github. There are many
> repositories that are in the org that aren't a part of the Xapi Project.
> I started making a list, and realised that there are a few other
> inconsistencies that we ought to clean up at the same time, for example,
> many repositories are marked as forks of personal repos where that
> relationship ought to be reversed.
> 
> 
> 
> First, there are some repositories that should just be deleted:
> 
> - opam
> A fork of github.com/ocaml/opam. I don't know why we have this, it
> doesn't appear to have any commits from us.
> 
> - opam-repository
> Same as opam.
> 
> - xcp-fhs
> This is unused by anyone, as far as I know.
> 
> - xen-unstable-mirror
> Just a mirror of the xen project repository.
> 
> - xcp-storage-managers
> An old fork. sm.git should be used instead.
> 
> - ocaml-sha
> A fork of upstream, no additional changesets from us.
> 
> - ocaml-tar
> A fork of upstream, no additional changesets from us
> 
> - ocaml-vhd
> A fork of upstream, no additional changesets from us
> 
> 
> 
> Secondly, I believe some of the repositories should be transferred to
> the 'xenserver' organisation, which I think probably needs approval, as
> the xenserver org is not a part of the Linux Foundation. These are:
> 
> - filesystem-summarise
> A tool to check for filesystem changes. Useful on XenServer for
> detecting when changes have been made to configuration files and so on.
> Not useful for general installations of the xapi project.
> 
> - jiralib
> An old python library for talking to jira. Superseded by jira-python
> package.
> 
> - mirrortest
> A test repository for checking Citrix's internal mirrors of the github
> repositories.
> 
> - PRDup
> 'Pull Request Duplicator', a tool for helping to backport pull requests
> to different branches.
> 
> - pull-request-manager
> Uses Citrix's internal build system to test pull requests - no longer used.
> 
> - xs-pull-request-build-scripts
> Replacement for pull-request-manager - uses Citrix's internal build
> system to test pull requests, this time using jenkins.
> 
> - xen-api-libs-specs
> Spec files used for building a lot of the xapi-project components for
> XenServer. There is large overlap with github.com/xenserver/buildroot -
> these should probably merge (or become more closely related).
> 
> - xen-api-backports
> Similar to xen-api-libs-specs, but for Citrix's internal 'old
> buildsystem' as opposed to Citrix's internal 'newer buildsystem'.
> 
> I don't think any of these is actually contentious - they probably
> should never have been part of the Linux Foundation, and have been there
> since we only had the one place on github to put things!
> 
> 
> 
> Third, we have some libraries that are actually mirage core libraries.
> These should transfer over to the mirage organisation (remaining in LF,
> as mirage is a Xen Project subproject like xapi):
> 
> - ocaml-gnt
> OCaml grant table manipulation. This code originated in the mirage
> project and was put here when it was split out of mirage-platform (see
> here:
> https://github.com/mirage/mirage-platform/commit/f532fc79af41e0e39b624a8e63dffc900bf1b7e4).
> 
> - ocaml-xenstore
> This is the mirage implementation of a xenstore client library. Required
> for running mirage kernels on xen. We use the unix-flavour of this
> library. It also contains a WIP new version of the guts of a xenstore
> daemon, which will be a mirage-style unix process _or_ unikernel
> (xenstore stub-domain!) that should eventually be upstreamed into xen.
> 
> - ocaml-xenstore-clients
> Slightly oddly named library that defines the unix transport mechanisms
> (unix-domain sockets) for using the ocaml-xenstore library. This is the
> unix counterpart to the internal shared-page mechanism used by mirage
> unikernels.
> 
> - ocaml-evtchn
> Similar to ocaml-gnt - split from the main mirage code at around the
> same time as ocaml-gnt.
> 
> - ocaml-xenstore-xen
> Unused by xapi-project. I believe in here lives the code that turns the
> xenstore daemon library from ocaml-xenstore into the actual xenstored
> stubdomain or process.
> 
> 
> 
> We have a few repositories that are forks of upstream repos with some of
> our own changes in. We should get these changes upstreamed at some
> point, but for now we should leave them there, but recognise that these
> aren't necessarily part of the official Xapi Project (excepting where
> they are, e.g. ocaml-xen-lowlevel-libs, which is a staging area for
> upstreaming back into xen.git!)
> - oclock
> - ocamltest
> - ocaml-xen-lowlevel-libs
> - python-github2
> 
> 
> 
> Then there are generic ocaml libraries which could be used by other
> ocaml programs. I think these can live on in the xapi project
> organisation for now, but I wouldn't class them as 'core' xapi-project
> repos.
> 
> - cdrom
> - netdev
> - ocamldoc-json
> - ocaml-encodings
> - ocaml-crc
> - ocaml-fd-send-recv
> - ocaml-netlink
> - ocaml-opasswd
> - ocaml-pci-db
> - ocaml-qmp
> - stdext
> - stunnel
> - nbd
> 
> 
> 
> 
> Which leaves us with the 'core' xapi project repositories:
> 
> - blktap
> - blktap-dkms
> - example-ocaml-daemon
> - ffs
> - forkexecd
> - libvhd
> - message-switch
> - ocaml-rrdd-plugins
> - opam-repo-dev
> - rrd-transport
> - rrdd-plugin-legacy
> - rrddump
> - sm
> - sm-cli
> - squeezed
> - tapctl
> - vhd-tool
> - vncproxy
> - vncterm
> - vxs
> - wsproxy
> - xapi-codegen
> - xapi-libvirt-storage
> - xapi-project
> - xcp-eliloader
> - xcp-guest-templates
> - xcp-idl
> - xcp-inventory
> - xcp-networkd
> - xcp-rrd
> - xcp-rrdd
> - xen-api
> - xen-api-client
> - xen-api-libs
> - xen-api-libs-transitional
> - xen-api-sdk
> - xenops
> - xenops-cli
> - xenopsd
> 
> Of the above lists that will remain in the xapi project, these
> repositories have incorrect forking status (they are marked as forks of
> someone here at Citrix, but shouldn't be):
> 
> Forked from me (jonludlam on github):
> xen-api-libs-transitional
> xen-api-client
> xcp-guest-templates
> xcp-eliloader
> wsproxy
> tapctl
> libvhd
> blktap-dkms
> netdev
> nbd
> cdrom
> 
> Forked from Dave Scott (djs55)
> xcp-idl
> vhd-tool
> ffs
> ocaml-vhd
> ocaml-tar
> ocaml-fd-send-recv
> 
> Forked from Simon Beaumont (simonjbeaumont):
> ocaml-pci-db
> 
> Forked from Mike McClurg (mcclurmc):
> ocaml-opasswd
> 
> These forking relationship problems need to be fixed by the people who
> own the upstream repo. I don't think it's quite as simple as clicking
> the 'transfer repository' button. If anyone knows the exact procedure
> for doing this, could they please reply?
> 
> 
> In summary, I believe we need to:
> 1) delete some repositories
> 2) move some repositories to xenserver
> 3) move some repositories to mirage-project
> 4) transfer ownership of some repositories (just flip around the
> direction of the fork).
> 5) document all of this on the wiki!
> 
> Any comments?
> 
> Jon
> 
> 
> 
> 
> 
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

From xen-api-bounces@lists.xen.org Tue Jul 01 15:45:37 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 01 Jul 2014 15:45:37 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X20FQ-0004VS-8q; Tue, 01 Jul 2014 15:45:32 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <amc79@cam.ac.uk>) id 1X1vvA-0002CT-2G
	for xen-api@lists.xen.org; Tue, 01 Jul 2014 11:08:20 +0000
Received: from [85.158.139.211:28224] by server-16.bemta-5.messagelabs.com id
	2F/11-18862-3A692B35; Tue, 01 Jul 2014 11:08:19 +0000
X-Env-Sender: amc79@cam.ac.uk
X-Msg-Ref: server-9.tower-206.messagelabs.com!1404212898!12952955!1
X-Originating-IP: [131.111.8.152]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MiA9PiA4MDU1Mw==\n
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 26803 invoked from network); 1 Jul 2014 11:08:18 -0000
Received: from ppsw-52.csi.cam.ac.uk (HELO ppsw-52.csi.cam.ac.uk)
	(131.111.8.152)
	by server-9.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted
	SMTP; 1 Jul 2014 11:08:18 -0000
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from m.cb1.com ([217.155.139.150]:65182 helo=[192.168.1.187])
	by ppsw-52.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:587)
	with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128)
	id 1X1vv7-0008As-EV (Exim 4.82_3-c0e5623)
	(return-path <amc79@cam.ac.uk>); Tue, 01 Jul 2014 12:08:17 +0100
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Amir Chaudhry <amc79@cam.ac.uk>
In-Reply-To: <5396D482.6000706@eu.citrix.com>
Date: Tue, 1 Jul 2014 12:08:17 +0100
Message-Id: <0CF8E334-9DB6-44A8-B327-3644C14D92EA@cam.ac.uk>
References: <5396D482.6000706@eu.citrix.com>
To: Jon Ludlam <jonathan.ludlam@eu.citrix.com>, xen-api@lists.xen.org,
	David Scott <Dave.Scott@citrix.com>, "mirageos-devel@lists.xenproject.org"
	<mirageos-devel@lists.xenproject.org>, Lars Kurth <lars.kurth@citrix.com>
X-Mailer: Apple Mail (2.1510)
X-Mailman-Approved-At: Tue, 01 Jul 2014 15:45:31 +0000
Subject: Re: [Xen-API] [MirageOS-devel] Xapi project repositories
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

Hi folks,

Since the Mirage release is fast approaching, I'd like to get the repo transfers in order.
Extracting from Jon's email below, here is where things stand with respect to the Mirage libs.

    *ocaml-xenstore*
    xapi-project is the current root
    An admin must initiate transfer to the Mirage org
    https://github.com/xapi-project/ocaml-xenstore/settings

    *ocaml-xenstore-xen*
    xapi-project is the current root
    An admin must initiate transfer to the Mirage org
    https://github.com/xapi-project/ocaml-xenstore-xen/settings

    *ocaml-xenstore-clients*
    djs55 is the current root
    Dave to transfer his personal repo to the Mirage org
    https://github.com/djs55/ocaml-xenstore-clients/settings

    *ocaml-gnt*
    Already transferred

    *ocaml-evtchn*
    Already transferred

Dave, could we please move the three remaining libraries to the Mirage org as soon as possible please?
It's a fairly trivial process and is transparent to end users.  I've even included links that should take you to the exact page where you can click the transfer button. :)
If there's some blocker to this, please let me know.

Best wishes,
Amir


On 10 Jun 2014, at 10:48, Jon Ludlam <jonathan.ludlam@eu.citrix.com> wrote:

> Hi all,
> 
> In preparing for the 2.0 release, it's become increasingly obvious that
> we really need to tidy up the xapi-project org on github. There are many
> repositories that are in the org that aren't a part of the Xapi Project.
> I started making a list, and realised that there are a few other
> inconsistencies that we ought to clean up at the same time, for example,
> many repositories are marked as forks of personal repos where that
> relationship ought to be reversed.
> 
> 
> 
> First, there are some repositories that should just be deleted:
> 
> - opam
> A fork of github.com/ocaml/opam. I don't know why we have this, it
> doesn't appear to have any commits from us.
> 
> - opam-repository
> Same as opam.
> 
> - xcp-fhs
> This is unused by anyone, as far as I know.
> 
> - xen-unstable-mirror
> Just a mirror of the xen project repository.
> 
> - xcp-storage-managers
> An old fork. sm.git should be used instead.
> 
> - ocaml-sha
> A fork of upstream, no additional changesets from us.
> 
> - ocaml-tar
> A fork of upstream, no additional changesets from us
> 
> - ocaml-vhd
> A fork of upstream, no additional changesets from us
> 
> 
> 
> Secondly, I believe some of the repositories should be transferred to
> the 'xenserver' organisation, which I think probably needs approval, as
> the xenserver org is not a part of the Linux Foundation. These are:
> 
> - filesystem-summarise
> A tool to check for filesystem changes. Useful on XenServer for
> detecting when changes have been made to configuration files and so on.
> Not useful for general installations of the xapi project.
> 
> - jiralib
> An old python library for talking to jira. Superseded by jira-python
> package.
> 
> - mirrortest
> A test repository for checking Citrix's internal mirrors of the github
> repositories.
> 
> - PRDup
> 'Pull Request Duplicator', a tool for helping to backport pull requests
> to different branches.
> 
> - pull-request-manager
> Uses Citrix's internal build system to test pull requests - no longer used.
> 
> - xs-pull-request-build-scripts
> Replacement for pull-request-manager - uses Citrix's internal build
> system to test pull requests, this time using jenkins.
> 
> - xen-api-libs-specs
> Spec files used for building a lot of the xapi-project components for
> XenServer. There is large overlap with github.com/xenserver/buildroot -
> these should probably merge (or become more closely related).
> 
> - xen-api-backports
> Similar to xen-api-libs-specs, but for Citrix's internal 'old
> buildsystem' as opposed to Citrix's internal 'newer buildsystem'.
> 
> I don't think any of these is actually contentious - they probably
> should never have been part of the Linux Foundation, and have been there
> since we only had the one place on github to put things!
> 
> 
> 
> Third, we have some libraries that are actually mirage core libraries.
> These should transfer over to the mirage organisation (remaining in LF,
> as mirage is a Xen Project subproject like xapi):
> 
> - ocaml-gnt
> OCaml grant table manipulation. This code originated in the mirage
> project and was put here when it was split out of mirage-platform (see
> here:
> https://github.com/mirage/mirage-platform/commit/f532fc79af41e0e39b624a8e63dffc900bf1b7e4).
> 
> - ocaml-xenstore
> This is the mirage implementation of a xenstore client library. Required
> for running mirage kernels on xen. We use the unix-flavour of this
> library. It also contains a WIP new version of the guts of a xenstore
> daemon, which will be a mirage-style unix process _or_ unikernel
> (xenstore stub-domain!) that should eventually be upstreamed into xen.
> 
> - ocaml-xenstore-clients
> Slightly oddly named library that defines the unix transport mechanisms
> (unix-domain sockets) for using the ocaml-xenstore library. This is the
> unix counterpart to the internal shared-page mechanism used by mirage
> unikernels.
> 
> - ocaml-evtchn
> Similar to ocaml-gnt - split from the main mirage code at around the
> same time as ocaml-gnt.
> 
> - ocaml-xenstore-xen
> Unused by xapi-project. I believe in here lives the code that turns the
> xenstore daemon library from ocaml-xenstore into the actual xenstored
> stubdomain or process.
> 
> 
> 
> We have a few repositories that are forks of upstream repos with some of
> our own changes in. We should get these changes upstreamed at some
> point, but for now we should leave them there, but recognise that these
> aren't necessarily part of the official Xapi Project (excepting where
> they are, e.g. ocaml-xen-lowlevel-libs, which is a staging area for
> upstreaming back into xen.git!)
> - oclock
> - ocamltest
> - ocaml-xen-lowlevel-libs
> - python-github2
> 
> 
> 
> Then there are generic ocaml libraries which could be used by other
> ocaml programs. I think these can live on in the xapi project
> organisation for now, but I wouldn't class them as 'core' xapi-project
> repos.
> 
> - cdrom
> - netdev
> - ocamldoc-json
> - ocaml-encodings
> - ocaml-crc
> - ocaml-fd-send-recv
> - ocaml-netlink
> - ocaml-opasswd
> - ocaml-pci-db
> - ocaml-qmp
> - stdext
> - stunnel
> - nbd
> 
> 
> 
> 
> Which leaves us with the 'core' xapi project repositories:
> 
> - blktap
> - blktap-dkms
> - example-ocaml-daemon
> - ffs
> - forkexecd
> - libvhd
> - message-switch
> - ocaml-rrdd-plugins
> - opam-repo-dev
> - rrd-transport
> - rrdd-plugin-legacy
> - rrddump
> - sm
> - sm-cli
> - squeezed
> - tapctl
> - vhd-tool
> - vncproxy
> - vncterm
> - vxs
> - wsproxy
> - xapi-codegen
> - xapi-libvirt-storage
> - xapi-project
> - xcp-eliloader
> - xcp-guest-templates
> - xcp-idl
> - xcp-inventory
> - xcp-networkd
> - xcp-rrd
> - xcp-rrdd
> - xen-api
> - xen-api-client
> - xen-api-libs
> - xen-api-libs-transitional
> - xen-api-sdk
> - xenops
> - xenops-cli
> - xenopsd
> 
> Of the above lists that will remain in the xapi project, these
> repositories have incorrect forking status (they are marked as forks of
> someone here at Citrix, but shouldn't be):
> 
> Forked from me (jonludlam on github):
> xen-api-libs-transitional
> xen-api-client
> xcp-guest-templates
> xcp-eliloader
> wsproxy
> tapctl
> libvhd
> blktap-dkms
> netdev
> nbd
> cdrom
> 
> Forked from Dave Scott (djs55)
> xcp-idl
> vhd-tool
> ffs
> ocaml-vhd
> ocaml-tar
> ocaml-fd-send-recv
> 
> Forked from Simon Beaumont (simonjbeaumont):
> ocaml-pci-db
> 
> Forked from Mike McClurg (mcclurmc):
> ocaml-opasswd
> 
> These forking relationship problems need to be fixed by the people who
> own the upstream repo. I don't think it's quite as simple as clicking
> the 'transfer repository' button. If anyone knows the exact procedure
> for doing this, could they please reply?
> 
> 
> In summary, I believe we need to:
> 1) delete some repositories
> 2) move some repositories to xenserver
> 3) move some repositories to mirage-project
> 4) transfer ownership of some repositories (just flip around the
> direction of the fork).
> 5) document all of this on the wiki!
> 
> Any comments?
> 
> Jon
> 
> 
> 
> 
> 
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

From xen-api-bounces@lists.xen.org Thu Jul 03 10:14:21 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 03 Jul 2014 10:14:21 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X2e1q-0001M3-NP; Thu, 03 Jul 2014 10:14:10 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <Koksharov.P@amngr.ru>) id 1X2aeM-00047E-Hq
	for xen-api@lists.xenproject.org; Thu, 03 Jul 2014 06:37:42 +0000
Received: from [85.158.139.211:26565] by server-1.bemta-5.messagelabs.com id
	1C/7C-30932-53AF4B35; Thu, 03 Jul 2014 06:37:41 +0000
X-Env-Sender: Koksharov.P@amngr.ru
X-Msg-Ref: server-6.tower-206.messagelabs.com!1404369460!13368737!1
X-Originating-IP: [213.142.193.171]
X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 31238 invoked from network); 3 Jul 2014 06:37:41 -0000
Received: from undina.amngr.ru (HELO undina.amngr.ru) (213.142.193.171)
	by server-6.tower-206.messagelabs.com with SMTP;
	3 Jul 2014 06:37:41 -0000
Received: from localhost (localhost [127.0.0.1])
	by undina.amngr.ru (Postfix) with ESMTP id 1BAE31158
	for <xen-api@lists.xenproject.org>;
	Thu,  3 Jul 2014 10:32:58 +0400 (MSK)
X-Virus-Scanned: amavisd-new at amngr.ru
Received: from undina.amngr.ru ([127.0.0.1])
	by localhost (undina.amngr.ru [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id IFTfjZvN_8aV for <xen-api@lists.xenproject.org>;
	Thu,  3 Jul 2014 10:32:57 +0400 (MSK)
Received: from TEGAMI.amngr.ru (tegami [20.12.0.11])
	by undina.amngr.ru (Postfix) with ESMTP id BD880108F
	for <xen-api@lists.xenproject.org>;
	Thu,  3 Jul 2014 10:32:57 +0400 (MSK)
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Thu, 3 Jul 2014 10:37:23 +0400
Message-ID: <F2FD278AB7BACA40A86B799AE6B3CB1B0135E9A7@TEGAMI.amngr.ru>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: LICENSE_EXPIRES_SOON
Thread-Index: Ac+WiT7mZVNL4kHMR9+5tSz7Kr2Ssg==
From: =?koi8-r?B?68/L28HSz9cg8MHXxcwg88XSx8XF18ne?= <Koksharov.P@amngr.ru>
To: <xen-api@lists.xenproject.org>
X-Mailman-Approved-At: Thu, 03 Jul 2014 10:14:09 +0000
Subject: [Xen-API] LICENSE_EXPIRES_SOON
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============6364846965586162231=="
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

This is a multi-part message in MIME format.

--===============6364846965586162231==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01CF9689.3F73C8C9"

This is a multi-part message in MIME format.

------_=_NextPart_001_01CF9689.3F73C8C9
Content-Type: text/plain;
	charset="koi8-r"
Content-Transfer-Encoding: quoted-printable

Hello gentlemen.

I've got a serious problem. I'm desperate to say more precisely. My =
hosts are running XCP 1.6.After upgrade from 1.1 some of my VMs still =
running MS Server 2003 started to lock up in the state of so called gray =
screen of death. After a bit of googling i discovered that it's a bug =
and Citrix released hotfixes against this disease. So i installed them. =
Everything went fine until recently, when everyday my hosts started to =
send emails stating that license is going to expire. Here's an example:

Field Value
----- -----
Name: LICENSE_EXPIRES_SOON
Priority: 10
Class: Host
Object UUID: 40aa0b58-d489-4009-a55a-95c5b151c0ce
Timestamp: 20140703T00:02:01Z
Message UUID: 58fcfb3d-e46c-18d3-700d-4c1080f4d13e
Pool name: zen
Body: Your license will expire in 27 days

I suppose it's because of an updated xapi from Citrix. My question is - =
what can i do with this, because i suppose when the counter reaches zero =
my servers could just lock up as with ordinary Xenserver. And what's =
worse, i'm not even in the office to physically reach the servers, have =
network access though. Please, i'd appreciate any help.


------_=_NextPart_001_01CF9689.3F73C8C9
Content-Type: text/html;
	charset="koi8-r"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dkoi8-r"><meta =
name=3DGenerator content=3D"Microsoft Word 14 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Gisha;
	panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:2.0cm 42.5pt 2.0cm 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DRU link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:9.0pt;font-family:"Gisha","sans-serif";color:#333333;b=
ackground:white'>Hello gentlemen.</span><span lang=3DEN-US =
style=3D'font-size:9.0pt;font-family:"Gisha","sans-serif";color:#333333'>=
<br><br><span style=3D'background:white'>I've got a serious problem. I'm =
desperate to say more precisely. My hosts are running XCP 1.6.After =
upgrade from 1.1 some of my VMs still running MS Server 2003 started to =
lock up in the state of so called gray screen of death. After a bit of =
googling i discovered that it's a bug and Citrix released hotfixes =
against this disease. So i installed them. Everything went fine until =
recently, when everyday my hosts started to send emails stating that =
license is going to expire. Here's an example:</span><br><br><span =
style=3D'background:white'>Field Value</span><br><span =
style=3D'background:white'>----- -----</span><br><span =
style=3D'background:white'>Name: LICENSE_EXPIRES_SOON</span><br><span =
style=3D'background:white'>Priority: 10</span><br><span =
style=3D'background:white'>Class: Host</span><br><span =
style=3D'background:white'>Object UUID: =
40aa0b58-d489-4009-a55a-95c5b151c0ce</span><br><span =
style=3D'background:white'>Timestamp: 20140703T00:02:01Z</span><br><span =
style=3D'background:white'>Message UUID: =
58fcfb3d-e46c-18d3-700d-4c1080f4d13e</span><br><span =
style=3D'background:white'>Pool name: zen</span><br><span =
style=3D'background:white'>Body: Your license will expire in =
</span></span><span lang=3DEN-US =
style=3D'font-size:9.0pt;color:#333333;background:white'>27</span><span =
lang=3DEN-US =
style=3D'font-size:9.0pt;font-family:"Gisha","sans-serif";color:#333333;b=
ackground:white'> days</span><span lang=3DEN-US =
style=3D'font-size:9.0pt;font-family:"Gisha","sans-serif";color:#333333'>=
<br><br><span style=3D'background:white'>I suppose it's because of an =
updated xapi from Citrix. My question is - what can i do with this, =
because i suppose when the counter reaches zero my servers could just =
lock up as with ordinary Xenserver. And what's worse, i'm not even in =
the office to physically reach the servers, have network access though. =
</span></span><span =
style=3D'font-size:9.0pt;font-family:"Gisha","sans-serif";color:#333333;b=
ackground:white'>Please, i'd appreciate any =
help.</span><o:p></o:p></p></div></body></html>
------_=_NextPart_001_01CF9689.3F73C8C9--


--===============6364846965586162231==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--===============6364846965586162231==--


From xen-api-bounces@lists.xen.org Thu Jul 03 10:14:21 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 03 Jul 2014 10:14:21 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X2e1q-0001M3-NP; Thu, 03 Jul 2014 10:14:10 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <Koksharov.P@amngr.ru>) id 1X2aeM-00047E-Hq
	for xen-api@lists.xenproject.org; Thu, 03 Jul 2014 06:37:42 +0000
Received: from [85.158.139.211:26565] by server-1.bemta-5.messagelabs.com id
	1C/7C-30932-53AF4B35; Thu, 03 Jul 2014 06:37:41 +0000
X-Env-Sender: Koksharov.P@amngr.ru
X-Msg-Ref: server-6.tower-206.messagelabs.com!1404369460!13368737!1
X-Originating-IP: [213.142.193.171]
X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 31238 invoked from network); 3 Jul 2014 06:37:41 -0000
Received: from undina.amngr.ru (HELO undina.amngr.ru) (213.142.193.171)
	by server-6.tower-206.messagelabs.com with SMTP;
	3 Jul 2014 06:37:41 -0000
Received: from localhost (localhost [127.0.0.1])
	by undina.amngr.ru (Postfix) with ESMTP id 1BAE31158
	for <xen-api@lists.xenproject.org>;
	Thu,  3 Jul 2014 10:32:58 +0400 (MSK)
X-Virus-Scanned: amavisd-new at amngr.ru
Received: from undina.amngr.ru ([127.0.0.1])
	by localhost (undina.amngr.ru [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id IFTfjZvN_8aV for <xen-api@lists.xenproject.org>;
	Thu,  3 Jul 2014 10:32:57 +0400 (MSK)
Received: from TEGAMI.amngr.ru (tegami [20.12.0.11])
	by undina.amngr.ru (Postfix) with ESMTP id BD880108F
	for <xen-api@lists.xenproject.org>;
	Thu,  3 Jul 2014 10:32:57 +0400 (MSK)
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Thu, 3 Jul 2014 10:37:23 +0400
Message-ID: <F2FD278AB7BACA40A86B799AE6B3CB1B0135E9A7@TEGAMI.amngr.ru>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: LICENSE_EXPIRES_SOON
Thread-Index: Ac+WiT7mZVNL4kHMR9+5tSz7Kr2Ssg==
From: =?koi8-r?B?68/L28HSz9cg8MHXxcwg88XSx8XF18ne?= <Koksharov.P@amngr.ru>
To: <xen-api@lists.xenproject.org>
X-Mailman-Approved-At: Thu, 03 Jul 2014 10:14:09 +0000
Subject: [Xen-API] LICENSE_EXPIRES_SOON
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============6364846965586162231=="
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

This is a multi-part message in MIME format.

--===============6364846965586162231==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01CF9689.3F73C8C9"

This is a multi-part message in MIME format.

------_=_NextPart_001_01CF9689.3F73C8C9
Content-Type: text/plain;
	charset="koi8-r"
Content-Transfer-Encoding: quoted-printable

Hello gentlemen.

I've got a serious problem. I'm desperate to say more precisely. My =
hosts are running XCP 1.6.After upgrade from 1.1 some of my VMs still =
running MS Server 2003 started to lock up in the state of so called gray =
screen of death. After a bit of googling i discovered that it's a bug =
and Citrix released hotfixes against this disease. So i installed them. =
Everything went fine until recently, when everyday my hosts started to =
send emails stating that license is going to expire. Here's an example:

Field Value
----- -----
Name: LICENSE_EXPIRES_SOON
Priority: 10
Class: Host
Object UUID: 40aa0b58-d489-4009-a55a-95c5b151c0ce
Timestamp: 20140703T00:02:01Z
Message UUID: 58fcfb3d-e46c-18d3-700d-4c1080f4d13e
Pool name: zen
Body: Your license will expire in 27 days

I suppose it's because of an updated xapi from Citrix. My question is - =
what can i do with this, because i suppose when the counter reaches zero =
my servers could just lock up as with ordinary Xenserver. And what's =
worse, i'm not even in the office to physically reach the servers, have =
network access though. Please, i'd appreciate any help.


------_=_NextPart_001_01CF9689.3F73C8C9
Content-Type: text/html;
	charset="koi8-r"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dkoi8-r"><meta =
name=3DGenerator content=3D"Microsoft Word 14 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Gisha;
	panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:2.0cm 42.5pt 2.0cm 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DRU link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:9.0pt;font-family:"Gisha","sans-serif";color:#333333;b=
ackground:white'>Hello gentlemen.</span><span lang=3DEN-US =
style=3D'font-size:9.0pt;font-family:"Gisha","sans-serif";color:#333333'>=
<br><br><span style=3D'background:white'>I've got a serious problem. I'm =
desperate to say more precisely. My hosts are running XCP 1.6.After =
upgrade from 1.1 some of my VMs still running MS Server 2003 started to =
lock up in the state of so called gray screen of death. After a bit of =
googling i discovered that it's a bug and Citrix released hotfixes =
against this disease. So i installed them. Everything went fine until =
recently, when everyday my hosts started to send emails stating that =
license is going to expire. Here's an example:</span><br><br><span =
style=3D'background:white'>Field Value</span><br><span =
style=3D'background:white'>----- -----</span><br><span =
style=3D'background:white'>Name: LICENSE_EXPIRES_SOON</span><br><span =
style=3D'background:white'>Priority: 10</span><br><span =
style=3D'background:white'>Class: Host</span><br><span =
style=3D'background:white'>Object UUID: =
40aa0b58-d489-4009-a55a-95c5b151c0ce</span><br><span =
style=3D'background:white'>Timestamp: 20140703T00:02:01Z</span><br><span =
style=3D'background:white'>Message UUID: =
58fcfb3d-e46c-18d3-700d-4c1080f4d13e</span><br><span =
style=3D'background:white'>Pool name: zen</span><br><span =
style=3D'background:white'>Body: Your license will expire in =
</span></span><span lang=3DEN-US =
style=3D'font-size:9.0pt;color:#333333;background:white'>27</span><span =
lang=3DEN-US =
style=3D'font-size:9.0pt;font-family:"Gisha","sans-serif";color:#333333;b=
ackground:white'> days</span><span lang=3DEN-US =
style=3D'font-size:9.0pt;font-family:"Gisha","sans-serif";color:#333333'>=
<br><br><span style=3D'background:white'>I suppose it's because of an =
updated xapi from Citrix. My question is - what can i do with this, =
because i suppose when the counter reaches zero my servers could just =
lock up as with ordinary Xenserver. And what's worse, i'm not even in =
the office to physically reach the servers, have network access though. =
</span></span><span =
style=3D'font-size:9.0pt;font-family:"Gisha","sans-serif";color:#333333;b=
ackground:white'>Please, i'd appreciate any =
help.</span><o:p></o:p></p></div></body></html>
------_=_NextPart_001_01CF9689.3F73C8C9--


--===============6364846965586162231==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--===============6364846965586162231==--


From xen-api-bounces@lists.xen.org Thu Jul 03 10:32:37 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 03 Jul 2014 10:32:37 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X2eJd-0003D7-Q8; Thu, 03 Jul 2014 10:32:33 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <Rob.Hoes@citrix.com>) id 1X2eJb-0003Cn-QC
	for xen-api@lists.xenproject.org; Thu, 03 Jul 2014 10:32:32 +0000
Received: from [85.158.139.211:46762] by server-7.bemta-5.messagelabs.com id
	DF/41-03657-F3135B35; Thu, 03 Jul 2014 10:32:31 +0000
X-Env-Sender: Rob.Hoes@citrix.com
X-Msg-Ref: server-13.tower-206.messagelabs.com!1404383550!13455123!1
X-Originating-IP: [185.25.65.24]
X-SpamReason: No, hits=1.1 required=7.0 tests=HTML_MESSAGE,SUBJ_ALL_CAPS
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 7056 invoked from network); 3 Jul 2014 10:32:30 -0000
Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24)
	by server-13.tower-206.messagelabs.com with SMTP;
	3 Jul 2014 10:32:30 -0000
X-IronPort-AV: E=Sophos;i="5.01,594,1400025600"; d="scan'208,217";a="22821349"
Received: from unknown (HELO AMSPEX01CL01.citrite.net) ([10.69.60.9])
	by AMSPIP01.EU.Citrix.com with ESMTP; 03 Jul 2014 10:32:30 +0000
Received: from AMSPEX01CL03.citrite.net ([169.254.8.89]) by
	AMSPEX01CL01.citrite.net ([169.254.6.105]) with mapi id 14.03.0181.006;
	Thu, 3 Jul 2014 12:32:29 +0200
From: Rob Hoes <Rob.Hoes@citrix.com>
To: "'Koksharov.P@amngr.ru'" <Koksharov.P@amngr.ru>,
	"xen-api@lists.xenproject.org" <xen-api@lists.xenproject.org>
Thread-Topic: LICENSE_EXPIRES_SOON
Thread-Index: Ac+WiT7mZVNL4kHMR9+5tSz7Kr2SsgAIAnWw
Date: Thu, 3 Jul 2014 10:32:29 +0000
Message-ID: <360717C0B01E6345BCBE64B758E22C2D3DF58C@AMSPEX01CL03.citrite.net>
References: <F2FD278AB7BACA40A86B799AE6B3CB1B0135E9A7@TEGAMI.amngr.ru>
In-Reply-To: <F2FD278AB7BACA40A86B799AE6B3CB1B0135E9A7@TEGAMI.amngr.ru>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.69.129.154]
MIME-Version: 1.0
X-DLP: AMS1
Subject: Re: [Xen-API] LICENSE_EXPIRES_SOON
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============8842397404249705928=="
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

--===============8842397404249705928==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_360717C0B01E6345BCBE64B758E22C2D3DF58CAMSPEX01CL03citri_"

--_000_360717C0B01E6345BCBE64B758E22C2D3DF58CAMSPEX01CL03citri_
Content-Type: text/plain; charset="koi8-r"
Content-Transfer-Encoding: quoted-printable

Hello,

When a license expires in XenServer, any running VMs will continue to run, =
they won't lock up.

I can't remember from the top of my head what the situation was for XCP 1.6=
, but it may be that nothing at all would happen when the "license" expires=
, because the code to do that was switched off. I do remember that we had m=
ade a mistake in this area in the first release, and then released an updat=
e.

I guess it depends on what exactly you have installed: what exactly is the =
hotfix that you have got?

Cheers,
Rob

From: xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org] =
On Behalf Of ???????? ????? ?????????
Sent: 03 July 2014 7:37 AM
To: xen-api@lists.xenproject.org
Subject: [Xen-API] LICENSE_EXPIRES_SOON

Hello gentlemen.

I've got a serious problem. I'm desperate to say more precisely. My hosts a=
re running XCP 1.6.After upgrade from 1.1 some of my VMs still running MS S=
erver 2003 started to lock up in the state of so called gray screen of deat=
h. After a bit of googling i discovered that it's a bug and Citrix released=
 hotfixes against this disease. So i installed them. Everything went fine u=
ntil recently, when everyday my hosts started to send emails stating that l=
icense is going to expire. Here's an example:

Field Value
----- -----
Name: LICENSE_EXPIRES_SOON
Priority: 10
Class: Host
Object UUID: 40aa0b58-d489-4009-a55a-95c5b151c0ce
Timestamp: 20140703T00:02:01Z
Message UUID: 58fcfb3d-e46c-18d3-700d-4c1080f4d13e
Pool name: zen
Body: Your license will expire in 27 days

I suppose it's because of an updated xapi from Citrix. My question is - wha=
t can i do with this, because i suppose when the counter reaches zero my se=
rvers could just lock up as with ordinary Xenserver. And what's worse, i'm =
not even in the office to physically reach the servers, have network access=
 though. Please, i'd appreciate any help.

--_000_360717C0B01E6345BCBE64B758E22C2D3DF58CAMSPEX01CL03citri_
Content-Type: text/html; charset="koi8-r"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dkoi8-r">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:Gisha;
	panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:2.0cm 42.5pt 2.0cm 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hello,<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">When a license expires=
 in XenServer, any running VMs will continue to run, they won&#8217;t lock =
up.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I can&#8217;t remember=
 from the top of my head what the situation was for XCP 1.6, but it may be =
that nothing at all would happen when the &#8220;license&#8221; expires, be=
cause the code to do that was switched off. I do remember
 that we had made a mistake in this area in the first release, and then rel=
eased an update.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I guess it depends on =
what exactly you have installed: what exactly is the hotfix that you have g=
ot?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Cheers,<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Rob<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;mso-fareast-language:ZH=
-CN">From:</span></b><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-fa=
mily:&quot;Tahoma&quot;,&quot;sans-serif&quot;;mso-fareast-language:ZH-CN">=
 xen-api-bounces@lists.xen.org
 [mailto:xen-api-bounces@lists.xen.org] <b>On Behalf Of </b>???????? ????? =
?????????<br>
<b>Sent:</b> 03 July 2014 7:37 AM<br>
<b>To:</b> xen-api@lists.xenproject.org<br>
<b>Subject:</b> [Xen-API] LICENSE_EXPIRES_SOON<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:9.0pt;font-f=
amily:&quot;Gisha&quot;,&quot;sans-serif&quot;;color:#333333;background:whi=
te">Hello gentlemen.</span><span lang=3D"EN-US" style=3D"font-size:9.0pt;fo=
nt-family:&quot;Gisha&quot;,&quot;sans-serif&quot;;color:#333333"><br>
<br>
<span style=3D"background:white">I've got a serious problem. I'm desperate =
to say more precisely. My hosts are running XCP 1.6.After upgrade from 1.1 =
some of my VMs still running MS Server 2003 started to lock up in the state=
 of so called gray screen of death.
 After a bit of googling i discovered that it's a bug and Citrix released h=
otfixes against this disease. So i installed them. Everything went fine unt=
il recently, when everyday my hosts started to send emails stating that lic=
ense is going to expire. Here's
 an example:</span><br>
<br>
<span style=3D"background:white">Field Value</span><br>
<span style=3D"background:white">----- -----</span><br>
<span style=3D"background:white">Name: LICENSE_EXPIRES_SOON</span><br>
<span style=3D"background:white">Priority: 10</span><br>
<span style=3D"background:white">Class: Host</span><br>
<span style=3D"background:white">Object UUID: 40aa0b58-d489-4009-a55a-95c5b=
151c0ce</span><br>
<span style=3D"background:white">Timestamp: 20140703T00:02:01Z</span><br>
<span style=3D"background:white">Message UUID: 58fcfb3d-e46c-18d3-700d-4c10=
80f4d13e</span><br>
<span style=3D"background:white">Pool name: zen</span><br>
<span style=3D"background:white">Body: Your license will expire in </span><=
/span><span lang=3D"EN-US" style=3D"font-size:9.0pt;color:#333333;backgroun=
d:white">27</span><span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family=
:&quot;Gisha&quot;,&quot;sans-serif&quot;;color:#333333;background:white">
 days</span><span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot=
;Gisha&quot;,&quot;sans-serif&quot;;color:#333333"><br>
<br>
<span style=3D"background:white">I suppose it's because of an updated xapi =
from Citrix. My question is - what can i do with this, because i suppose wh=
en the counter reaches zero my servers could just lock up as with ordinary =
Xenserver. And what's worse, i'm not
 even in the office to physically reach the servers, have network access th=
ough. </span>
</span><span lang=3D"RU" style=3D"font-size:9.0pt;font-family:&quot;Gisha&q=
uot;,&quot;sans-serif&quot;;color:#333333;background:white">Please, i'd app=
reciate any help.</span><span lang=3D"RU"><o:p></o:p></span></p>
</div>
</div>
</body>
</html>

--_000_360717C0B01E6345BCBE64B758E22C2D3DF58CAMSPEX01CL03citri_--


--===============8842397404249705928==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--===============8842397404249705928==--


From xen-api-bounces@lists.xen.org Thu Jul 03 10:32:37 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 03 Jul 2014 10:32:37 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X2eJd-0003D7-Q8; Thu, 03 Jul 2014 10:32:33 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <Rob.Hoes@citrix.com>) id 1X2eJb-0003Cn-QC
	for xen-api@lists.xenproject.org; Thu, 03 Jul 2014 10:32:32 +0000
Received: from [85.158.139.211:46762] by server-7.bemta-5.messagelabs.com id
	DF/41-03657-F3135B35; Thu, 03 Jul 2014 10:32:31 +0000
X-Env-Sender: Rob.Hoes@citrix.com
X-Msg-Ref: server-13.tower-206.messagelabs.com!1404383550!13455123!1
X-Originating-IP: [185.25.65.24]
X-SpamReason: No, hits=1.1 required=7.0 tests=HTML_MESSAGE,SUBJ_ALL_CAPS
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 7056 invoked from network); 3 Jul 2014 10:32:30 -0000
Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24)
	by server-13.tower-206.messagelabs.com with SMTP;
	3 Jul 2014 10:32:30 -0000
X-IronPort-AV: E=Sophos;i="5.01,594,1400025600"; d="scan'208,217";a="22821349"
Received: from unknown (HELO AMSPEX01CL01.citrite.net) ([10.69.60.9])
	by AMSPIP01.EU.Citrix.com with ESMTP; 03 Jul 2014 10:32:30 +0000
Received: from AMSPEX01CL03.citrite.net ([169.254.8.89]) by
	AMSPEX01CL01.citrite.net ([169.254.6.105]) with mapi id 14.03.0181.006;
	Thu, 3 Jul 2014 12:32:29 +0200
From: Rob Hoes <Rob.Hoes@citrix.com>
To: "'Koksharov.P@amngr.ru'" <Koksharov.P@amngr.ru>,
	"xen-api@lists.xenproject.org" <xen-api@lists.xenproject.org>
Thread-Topic: LICENSE_EXPIRES_SOON
Thread-Index: Ac+WiT7mZVNL4kHMR9+5tSz7Kr2SsgAIAnWw
Date: Thu, 3 Jul 2014 10:32:29 +0000
Message-ID: <360717C0B01E6345BCBE64B758E22C2D3DF58C@AMSPEX01CL03.citrite.net>
References: <F2FD278AB7BACA40A86B799AE6B3CB1B0135E9A7@TEGAMI.amngr.ru>
In-Reply-To: <F2FD278AB7BACA40A86B799AE6B3CB1B0135E9A7@TEGAMI.amngr.ru>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.69.129.154]
MIME-Version: 1.0
X-DLP: AMS1
Subject: Re: [Xen-API] LICENSE_EXPIRES_SOON
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============8842397404249705928=="
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

--===============8842397404249705928==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_360717C0B01E6345BCBE64B758E22C2D3DF58CAMSPEX01CL03citri_"

--_000_360717C0B01E6345BCBE64B758E22C2D3DF58CAMSPEX01CL03citri_
Content-Type: text/plain; charset="koi8-r"
Content-Transfer-Encoding: quoted-printable

Hello,

When a license expires in XenServer, any running VMs will continue to run, =
they won't lock up.

I can't remember from the top of my head what the situation was for XCP 1.6=
, but it may be that nothing at all would happen when the "license" expires=
, because the code to do that was switched off. I do remember that we had m=
ade a mistake in this area in the first release, and then released an updat=
e.

I guess it depends on what exactly you have installed: what exactly is the =
hotfix that you have got?

Cheers,
Rob

From: xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org] =
On Behalf Of ???????? ????? ?????????
Sent: 03 July 2014 7:37 AM
To: xen-api@lists.xenproject.org
Subject: [Xen-API] LICENSE_EXPIRES_SOON

Hello gentlemen.

I've got a serious problem. I'm desperate to say more precisely. My hosts a=
re running XCP 1.6.After upgrade from 1.1 some of my VMs still running MS S=
erver 2003 started to lock up in the state of so called gray screen of deat=
h. After a bit of googling i discovered that it's a bug and Citrix released=
 hotfixes against this disease. So i installed them. Everything went fine u=
ntil recently, when everyday my hosts started to send emails stating that l=
icense is going to expire. Here's an example:

Field Value
----- -----
Name: LICENSE_EXPIRES_SOON
Priority: 10
Class: Host
Object UUID: 40aa0b58-d489-4009-a55a-95c5b151c0ce
Timestamp: 20140703T00:02:01Z
Message UUID: 58fcfb3d-e46c-18d3-700d-4c1080f4d13e
Pool name: zen
Body: Your license will expire in 27 days

I suppose it's because of an updated xapi from Citrix. My question is - wha=
t can i do with this, because i suppose when the counter reaches zero my se=
rvers could just lock up as with ordinary Xenserver. And what's worse, i'm =
not even in the office to physically reach the servers, have network access=
 though. Please, i'd appreciate any help.

--_000_360717C0B01E6345BCBE64B758E22C2D3DF58CAMSPEX01CL03citri_
Content-Type: text/html; charset="koi8-r"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dkoi8-r">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:Gisha;
	panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:2.0cm 42.5pt 2.0cm 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hello,<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">When a license expires=
 in XenServer, any running VMs will continue to run, they won&#8217;t lock =
up.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I can&#8217;t remember=
 from the top of my head what the situation was for XCP 1.6, but it may be =
that nothing at all would happen when the &#8220;license&#8221; expires, be=
cause the code to do that was switched off. I do remember
 that we had made a mistake in this area in the first release, and then rel=
eased an update.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I guess it depends on =
what exactly you have installed: what exactly is the hotfix that you have g=
ot?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Cheers,<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Rob<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;mso-fareast-language:ZH=
-CN">From:</span></b><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-fa=
mily:&quot;Tahoma&quot;,&quot;sans-serif&quot;;mso-fareast-language:ZH-CN">=
 xen-api-bounces@lists.xen.org
 [mailto:xen-api-bounces@lists.xen.org] <b>On Behalf Of </b>???????? ????? =
?????????<br>
<b>Sent:</b> 03 July 2014 7:37 AM<br>
<b>To:</b> xen-api@lists.xenproject.org<br>
<b>Subject:</b> [Xen-API] LICENSE_EXPIRES_SOON<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:9.0pt;font-f=
amily:&quot;Gisha&quot;,&quot;sans-serif&quot;;color:#333333;background:whi=
te">Hello gentlemen.</span><span lang=3D"EN-US" style=3D"font-size:9.0pt;fo=
nt-family:&quot;Gisha&quot;,&quot;sans-serif&quot;;color:#333333"><br>
<br>
<span style=3D"background:white">I've got a serious problem. I'm desperate =
to say more precisely. My hosts are running XCP 1.6.After upgrade from 1.1 =
some of my VMs still running MS Server 2003 started to lock up in the state=
 of so called gray screen of death.
 After a bit of googling i discovered that it's a bug and Citrix released h=
otfixes against this disease. So i installed them. Everything went fine unt=
il recently, when everyday my hosts started to send emails stating that lic=
ense is going to expire. Here's
 an example:</span><br>
<br>
<span style=3D"background:white">Field Value</span><br>
<span style=3D"background:white">----- -----</span><br>
<span style=3D"background:white">Name: LICENSE_EXPIRES_SOON</span><br>
<span style=3D"background:white">Priority: 10</span><br>
<span style=3D"background:white">Class: Host</span><br>
<span style=3D"background:white">Object UUID: 40aa0b58-d489-4009-a55a-95c5b=
151c0ce</span><br>
<span style=3D"background:white">Timestamp: 20140703T00:02:01Z</span><br>
<span style=3D"background:white">Message UUID: 58fcfb3d-e46c-18d3-700d-4c10=
80f4d13e</span><br>
<span style=3D"background:white">Pool name: zen</span><br>
<span style=3D"background:white">Body: Your license will expire in </span><=
/span><span lang=3D"EN-US" style=3D"font-size:9.0pt;color:#333333;backgroun=
d:white">27</span><span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family=
:&quot;Gisha&quot;,&quot;sans-serif&quot;;color:#333333;background:white">
 days</span><span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot=
;Gisha&quot;,&quot;sans-serif&quot;;color:#333333"><br>
<br>
<span style=3D"background:white">I suppose it's because of an updated xapi =
from Citrix. My question is - what can i do with this, because i suppose wh=
en the counter reaches zero my servers could just lock up as with ordinary =
Xenserver. And what's worse, i'm not
 even in the office to physically reach the servers, have network access th=
ough. </span>
</span><span lang=3D"RU" style=3D"font-size:9.0pt;font-family:&quot;Gisha&q=
uot;,&quot;sans-serif&quot;;color:#333333;background:white">Please, i'd app=
reciate any help.</span><span lang=3D"RU"><o:p></o:p></span></p>
</div>
</div>
</body>
</html>

--_000_360717C0B01E6345BCBE64B758E22C2D3DF58CAMSPEX01CL03citri_--


--===============8842397404249705928==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--===============8842397404249705928==--


From xen-api-bounces@lists.xen.org Thu Jul 03 13:54:25 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 03 Jul 2014 13:54:25 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X2hSr-0002oB-09; Thu, 03 Jul 2014 13:54:17 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <Rob.Hoes@citrix.com>) id 1X2hSp-0002o2-Nu
	for xen-api@lists.xenproject.org; Thu, 03 Jul 2014 13:54:16 +0000
Received: from [85.158.143.35:3020] by server-1.bemta-4.messagelabs.com id
	D6/A6-09496-78065B35; Thu, 03 Jul 2014 13:54:15 +0000
X-Env-Sender: Rob.Hoes@citrix.com
X-Msg-Ref: server-4.tower-21.messagelabs.com!1404395653!15619903!1
X-Originating-IP: [185.25.65.24]
X-SpamReason: No, hits=1.1 required=7.0 tests=HTML_MESSAGE,SUBJ_ALL_CAPS
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 6840 invoked from network); 3 Jul 2014 13:54:13 -0000
Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24)
	by server-4.tower-21.messagelabs.com with SMTP;
	3 Jul 2014 13:54:13 -0000
X-IronPort-AV: E=Sophos;i="5.01,595,1400025600"; d="scan'208,217";a="22826839"
Received: from unknown (HELO AMSPEX01CL01.citrite.net) ([10.69.60.9])
	by AMSPIP01.EU.Citrix.com with ESMTP; 03 Jul 2014 13:54:13 +0000
Received: from AMSPEX01CL03.citrite.net ([169.254.8.89]) by
	AMSPEX01CL01.citrite.net ([169.254.6.105]) with mapi id 14.03.0181.006;
	Thu, 3 Jul 2014 15:54:13 +0200
From: Rob Hoes <Rob.Hoes@citrix.com>
To: "'Koksharov.P@amngr.ru'" <Koksharov.P@amngr.ru>
Thread-Topic: LICENSE_EXPIRES_SOON
Thread-Index: Ac+WiT7mZVNL4kHMR9+5tSz7Kr2SsgAIAnWwAANBjuAAA3RTMA==
Date: Thu, 3 Jul 2014 13:54:11 +0000
Message-ID: <360717C0B01E6345BCBE64B758E22C2D3DF8AA@AMSPEX01CL03.citrite.net>
References: <F2FD278AB7BACA40A86B799AE6B3CB1B0135E9A7@TEGAMI.amngr.ru>
	<360717C0B01E6345BCBE64B758E22C2D3DF58C@AMSPEX01CL03.citrite.net>
	<F2FD278AB7BACA40A86B799AE6B3CB1B0135EAC1@TEGAMI.amngr.ru>
In-Reply-To: <F2FD278AB7BACA40A86B799AE6B3CB1B0135EAC1@TEGAMI.amngr.ru>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.69.129.154]
MIME-Version: 1.0
X-DLP: AMS1
Cc: "xen-api@lists.xenproject.org" <xen-api@lists.xenproject.org>,
	Tim Mackey <Timothy.Mackey@citrix.com>
Subject: Re: [Xen-API] LICENSE_EXPIRES_SOON
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============5207051324545329962=="
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

--===============5207051324545329962==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_360717C0B01E6345BCBE64B758E22C2D3DF8AAAMSPEX01CL03citri_"

--_000_360717C0B01E6345BCBE64B758E22C2D3DF8AAAMSPEX01CL03citri_
Content-Type: text/plain; charset="koi8-r"
Content-Transfer-Encoding: quoted-printable

I see that Tim Mackey has meanwhile answered on the Q&A page you link to be=
low.

I understand now that you have indeed applied an actual XenServer hotfix pa=
ckage to an XCP server. Unfortunately, XenServer hotfixes are not usually c=
ompatible with XCP (it is definitely not tested this way). What this means =
for licensing, is that the hotfix you have installed must have contained a =
new xapi binary with the licensing checks enabled (as in XenServer).

I think that the options are:

1.       Tim to give you a 12-month "XenServer Free Edition" license file. =
This may be the easiest way forward in the short term.

2.       Reinstall the original xapi RPM package from XCP 1.6, which you sh=
ould be able to find on the XCP install ISO. This would remove the licensin=
g checks again, but would also undo any xapi fixes that were present in you=
r hotfix, and would move you even further away from a tested system...

3.       Upgrade to XenServer 6.2, which is as free as XCP, and to which yo=
u can safely apply further hotfixes from Citrix.

Cheers,
Rob

From: =EB=CF=CB=DB=C1=D2=CF=D7 =F0=C1=D7=C5=CC =F3=C5=D2=C7=C5=C5=D7=C9=DE =
[mailto:Koksharov.P@amngr.ru]
Sent: 03 July 2014 1:04 PM
To: Rob Hoes
Subject: RE: LICENSE_EXPIRES_SOON

Here http://www.xenproject.org/questions-and-answers/please-help-xcp-1-6-wi=
th-citrix-hotfixes-resulted-in-license-problem-urgent.html , are the same s=
erver. "Alexander" my former colleague, but lost contact with him. I don `t=
 know how he solved the problem. With servers did not do anything, do not p=
ut hot fixes. They both began to send e-mail messages on the end of the lic=
ense. How to be in this situation? Thanks for the help!

From: Rob Hoes [mailto:Rob.Hoes@citrix.com]
Sent: Thursday, July 03, 2014 2:32 PM
To: =EB=CF=CB=DB=C1=D2=CF=D7 =F0=C1=D7=C5=CC =F3=C5=D2=C7=C5=C5=D7=C9=DE; x=
en-api@lists.xenproject.org<mailto:xen-api@lists.xenproject.org>
Subject: RE: LICENSE_EXPIRES_SOON

Hello,

When a license expires in XenServer, any running VMs will continue to run, =
they won't lock up.

I can't remember from the top of my head what the situation was for XCP 1.6=
, but it may be that nothing at all would happen when the "license" expires=
, because the code to do that was switched off. I do remember that we had m=
ade a mistake in this area in the first release, and then released an updat=
e.

I guess it depends on what exactly you have installed: what exactly is the =
hotfix that you have got?

Cheers,
Rob

From: xen-api-bounces@lists.xen.org<mailto:xen-api-bounces@lists.xen.org> [=
mailto:xen-api-bounces@lists.xen.org] On Behalf Of ???????? ????? ?????????
Sent: 03 July 2014 7:37 AM
To: xen-api@lists.xenproject.org<mailto:xen-api@lists.xenproject.org>
Subject: [Xen-API] LICENSE_EXPIRES_SOON

Hello gentlemen.

I've got a serious problem. I'm desperate to say more precisely. My hosts a=
re running XCP 1.6.After upgrade from 1.1 some of my VMs still running MS S=
erver 2003 started to lock up in the state of so called gray screen of deat=
h. After a bit of googling i discovered that it's a bug and Citrix released=
 hotfixes against this disease. So i installed them. Everything went fine u=
ntil recently, when everyday my hosts started to send emails stating that l=
icense is going to expire. Here's an example:

Field Value
----- -----
Name: LICENSE_EXPIRES_SOON
Priority: 10
Class: Host
Object UUID: 40aa0b58-d489-4009-a55a-95c5b151c0ce
Timestamp: 20140703T00:02:01Z
Message UUID: 58fcfb3d-e46c-18d3-700d-4c1080f4d13e
Pool name: zen
Body: Your license will expire in 27 days

I suppose it's because of an updated xapi from Citrix. My question is - wha=
t can i do with this, because i suppose when the counter reaches zero my se=
rvers could just lock up as with ordinary Xenserver. And what's worse, i'm =
not even in the office to physically reach the servers, have network access=
 though. Please, i'd appreciate any help.

--_000_360717C0B01E6345BCBE64B758E22C2D3DF8AAAMSPEX01CL03citri_
Content-Type: text/html; charset="koi8-r"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dkoi8-r">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:Gisha;
	panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";
	mso-fareast-language:EN-US;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";
	mso-fareast-language:EN-US;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
p.a, li.a, div.a
	{mso-style-name:"\0422\0435\043A\0441\0442 \0432\044B\043D\043E\0441\043A\=
0438";
	mso-style-link:"\0422\0435\043A\0441\0442 \0432\044B\043D\043E\0441\043A\0=
438 \0417\043D\0430\043A";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
span.a0
	{mso-style-name:"\0422\0435\043A\0441\0442 \0432\044B\043D\043E\0441\043A\=
0438 \0417\043D\0430\043A";
	mso-style-priority:99;
	mso-style-link:"\0422\0435\043A\0441\0442 \0432\044B\043D\043E\0441\043A\0=
438";
	font-family:"Tahoma","sans-serif";
	mso-fareast-language:EN-US;}
span.EmailStyle24
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:2.0cm 42.5pt 2.0cm 3.0cm;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1780298690;
	mso-list-type:hybrid;
	mso-list-template-ids:728130932 134807567 134807577 134807579 134807567 13=
4807577 134807579 134807567 134807577 134807579;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I see that Tim Mackey =
has meanwhile answered on the Q&amp;A page you link to below.<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I understand now that =
you have indeed applied an actual XenServer hotfix package to an XCP server=
. Unfortunately, XenServer hotfixes are not usually compatible with XCP (it=
 is definitely not tested this way).
 What this means for licensing, is that the hotfix you have installed must =
have contained a new xapi binary with the licensing checks enabled (as in X=
enServer).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I think that the optio=
ns are:<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 lfo1"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"=
mso-list:Ignore">1.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"colo=
r:#1F497D">Tim to give you a 12-month &#8220;XenServer Free Edition&#8221; =
license file. This may be the easiest way forward in the short term.<o:p></=
o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 lfo1"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"=
mso-list:Ignore">2.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"colo=
r:#1F497D">Reinstall the original xapi RPM package from XCP 1.6, which you =
should be able to find on the XCP install ISO. This would remove the licens=
ing checks again, but would also undo
 any xapi fixes that were present in your hotfix, and would move you even f=
urther away from a tested system&#8230;<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 lfo1"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"=
mso-list:Ignore">3.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"colo=
r:#1F497D">Upgrade to XenServer 6.2, which is as free as XCP, and to which =
you can safely apply further hotfixes from Citrix.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Cheers,<br>
Rob<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;mso-fareast-language:ZH=
-CN">From:</span></b><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-fa=
mily:&quot;Tahoma&quot;,&quot;sans-serif&quot;;mso-fareast-language:ZH-CN">=
 =EB=CF=CB=DB=C1=D2=CF=D7
 =F0=C1=D7=C5=CC =F3=C5=D2=C7=C5=C5=D7=C9=DE [mailto:Koksharov.P@amngr.ru] =
<br>
<b>Sent:</b> 03 July 2014 1:04 PM<br>
<b>To:</b> Rob Hoes<br>
<b>Subject:</b> RE: LICENSE_EXPIRES_SOON<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Here <a=
 href=3D"http://www.xenproject.org/questions-and-answers/please-help-xcp-1-=
6-with-citrix-hotfixes-resulted-in-license-problem-urgent.html">
http://www.xenproject.org/questions-and-answers/please-help-xcp-1-6-with-ci=
trix-hotfixes-resulted-in-license-problem-urgent.html</a> , are the same se=
rver. &quot;Alexander&quot; my former colleague, but lost contact with him.=
 I don `t know how he solved the problem.
 With servers did not do anything, do not put hot fixes. They both began to=
 send e-mail messages on the end of the license. How to be in this situatio=
n? Thanks for the help!<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"RU" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;mso-fareast-language:RU">F=
rom:</span></b><span lang=3D"RU" style=3D"font-size:10.0pt;font-family:&quo=
t;Tahoma&quot;,&quot;sans-serif&quot;;mso-fareast-language:RU"> Rob Hoes [<=
a href=3D"mailto:Rob.Hoes@citrix.com">mailto:Rob.Hoes@citrix.com</a>]
<br>
<b>Sent:</b> Thursday, July 03, 2014 2:32 PM<br>
<b>To:</b> =EB=CF=CB=DB=C1=D2=CF=D7 =F0=C1=D7=C5=CC =F3=C5=D2=C7=C5=C5=D7=
=C9=DE; <a href=3D"mailto:xen-api@lists.xenproject.org">
xen-api@lists.xenproject.org</a><br>
<b>Subject:</b> RE: LICENSE_EXPIRES_SOON<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"RU"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hello,<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">When a license expires=
 in XenServer, any running VMs will continue to run, they won&#8217;t lock =
up.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I can&#8217;t remember=
 from the top of my head what the situation was for XCP 1.6, but it may be =
that nothing at all would happen when the &#8220;license&#8221; expires, be=
cause the code to do that was switched off. I do remember
 that we had made a mistake in this area in the first release, and then rel=
eased an update.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I guess it depends on =
what exactly you have installed: what exactly is the hotfix that you have g=
ot?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Cheers,<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Rob<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;mso-fareast-language:ZH=
-CN">From:</span></b><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-fa=
mily:&quot;Tahoma&quot;,&quot;sans-serif&quot;;mso-fareast-language:ZH-CN">
<a href=3D"mailto:xen-api-bounces@lists.xen.org">xen-api-bounces@lists.xen.=
org</a> [<a href=3D"mailto:xen-api-bounces@lists.xen.org">mailto:xen-api-bo=
unces@lists.xen.org</a>]
<b>On Behalf Of </b>???????? ????? ?????????<br>
<b>Sent:</b> 03 July 2014 7:37 AM<br>
<b>To:</b> <a href=3D"mailto:xen-api@lists.xenproject.org">xen-api@lists.xe=
nproject.org</a><br>
<b>Subject:</b> [Xen-API] LICENSE_EXPIRES_SOON<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:9.0pt;font-f=
amily:&quot;Gisha&quot;,&quot;sans-serif&quot;;color:#333333;background:whi=
te">Hello gentlemen.</span><span lang=3D"EN-US" style=3D"font-size:9.0pt;fo=
nt-family:&quot;Gisha&quot;,&quot;sans-serif&quot;;color:#333333"><br>
<br>
<span style=3D"background:white">I've got a serious problem. I'm desperate =
to say more precisely. My hosts are running XCP 1.6.After upgrade from 1.1 =
some of my VMs still running MS Server 2003 started to lock up in the state=
 of so called gray screen of death.
 After a bit of googling i discovered that it's a bug and Citrix released h=
otfixes against this disease. So i installed them. Everything went fine unt=
il recently, when everyday my hosts started to send emails stating that lic=
ense is going to expire. Here's
 an example:</span><br>
<br>
<span style=3D"background:white">Field Value</span><br>
<span style=3D"background:white">----- -----</span><br>
<span style=3D"background:white">Name: LICENSE_EXPIRES_SOON</span><br>
<span style=3D"background:white">Priority: 10</span><br>
<span style=3D"background:white">Class: Host</span><br>
<span style=3D"background:white">Object UUID: 40aa0b58-d489-4009-a55a-95c5b=
151c0ce</span><br>
<span style=3D"background:white">Timestamp: 20140703T00:02:01Z</span><br>
<span style=3D"background:white">Message UUID: 58fcfb3d-e46c-18d3-700d-4c10=
80f4d13e</span><br>
<span style=3D"background:white">Pool name: zen</span><br>
<span style=3D"background:white">Body: Your license will expire in </span><=
/span><span lang=3D"EN-US" style=3D"font-size:9.0pt;color:#333333;backgroun=
d:white">27</span><span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family=
:&quot;Gisha&quot;,&quot;sans-serif&quot;;color:#333333;background:white">
 days</span><span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot=
;Gisha&quot;,&quot;sans-serif&quot;;color:#333333"><br>
<br>
<span style=3D"background:white">I suppose it's because of an updated xapi =
from Citrix. My question is - what can i do with this, because i suppose wh=
en the counter reaches zero my servers could just lock up as with ordinary =
Xenserver. And what's worse, i'm not
 even in the office to physically reach the servers, have network access th=
ough. </span>
</span><span lang=3D"RU" style=3D"font-size:9.0pt;font-family:&quot;Gisha&q=
uot;,&quot;sans-serif&quot;;color:#333333;background:white">Please, i'd app=
reciate any help.</span><span lang=3D"RU"><o:p></o:p></span></p>
</div>
</div>
</div>
</body>
</html>

--_000_360717C0B01E6345BCBE64B758E22C2D3DF8AAAMSPEX01CL03citri_--


--===============5207051324545329962==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--===============5207051324545329962==--


From xen-api-bounces@lists.xen.org Thu Jul 03 13:54:25 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 03 Jul 2014 13:54:25 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X2hSr-0002oB-09; Thu, 03 Jul 2014 13:54:17 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <Rob.Hoes@citrix.com>) id 1X2hSp-0002o2-Nu
	for xen-api@lists.xenproject.org; Thu, 03 Jul 2014 13:54:16 +0000
Received: from [85.158.143.35:3020] by server-1.bemta-4.messagelabs.com id
	D6/A6-09496-78065B35; Thu, 03 Jul 2014 13:54:15 +0000
X-Env-Sender: Rob.Hoes@citrix.com
X-Msg-Ref: server-4.tower-21.messagelabs.com!1404395653!15619903!1
X-Originating-IP: [185.25.65.24]
X-SpamReason: No, hits=1.1 required=7.0 tests=HTML_MESSAGE,SUBJ_ALL_CAPS
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 6840 invoked from network); 3 Jul 2014 13:54:13 -0000
Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24)
	by server-4.tower-21.messagelabs.com with SMTP;
	3 Jul 2014 13:54:13 -0000
X-IronPort-AV: E=Sophos;i="5.01,595,1400025600"; d="scan'208,217";a="22826839"
Received: from unknown (HELO AMSPEX01CL01.citrite.net) ([10.69.60.9])
	by AMSPIP01.EU.Citrix.com with ESMTP; 03 Jul 2014 13:54:13 +0000
Received: from AMSPEX01CL03.citrite.net ([169.254.8.89]) by
	AMSPEX01CL01.citrite.net ([169.254.6.105]) with mapi id 14.03.0181.006;
	Thu, 3 Jul 2014 15:54:13 +0200
From: Rob Hoes <Rob.Hoes@citrix.com>
To: "'Koksharov.P@amngr.ru'" <Koksharov.P@amngr.ru>
Thread-Topic: LICENSE_EXPIRES_SOON
Thread-Index: Ac+WiT7mZVNL4kHMR9+5tSz7Kr2SsgAIAnWwAANBjuAAA3RTMA==
Date: Thu, 3 Jul 2014 13:54:11 +0000
Message-ID: <360717C0B01E6345BCBE64B758E22C2D3DF8AA@AMSPEX01CL03.citrite.net>
References: <F2FD278AB7BACA40A86B799AE6B3CB1B0135E9A7@TEGAMI.amngr.ru>
	<360717C0B01E6345BCBE64B758E22C2D3DF58C@AMSPEX01CL03.citrite.net>
	<F2FD278AB7BACA40A86B799AE6B3CB1B0135EAC1@TEGAMI.amngr.ru>
In-Reply-To: <F2FD278AB7BACA40A86B799AE6B3CB1B0135EAC1@TEGAMI.amngr.ru>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.69.129.154]
MIME-Version: 1.0
X-DLP: AMS1
Cc: "xen-api@lists.xenproject.org" <xen-api@lists.xenproject.org>,
	Tim Mackey <Timothy.Mackey@citrix.com>
Subject: Re: [Xen-API] LICENSE_EXPIRES_SOON
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============5207051324545329962=="
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

--===============5207051324545329962==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_360717C0B01E6345BCBE64B758E22C2D3DF8AAAMSPEX01CL03citri_"

--_000_360717C0B01E6345BCBE64B758E22C2D3DF8AAAMSPEX01CL03citri_
Content-Type: text/plain; charset="koi8-r"
Content-Transfer-Encoding: quoted-printable

I see that Tim Mackey has meanwhile answered on the Q&A page you link to be=
low.

I understand now that you have indeed applied an actual XenServer hotfix pa=
ckage to an XCP server. Unfortunately, XenServer hotfixes are not usually c=
ompatible with XCP (it is definitely not tested this way). What this means =
for licensing, is that the hotfix you have installed must have contained a =
new xapi binary with the licensing checks enabled (as in XenServer).

I think that the options are:

1.       Tim to give you a 12-month "XenServer Free Edition" license file. =
This may be the easiest way forward in the short term.

2.       Reinstall the original xapi RPM package from XCP 1.6, which you sh=
ould be able to find on the XCP install ISO. This would remove the licensin=
g checks again, but would also undo any xapi fixes that were present in you=
r hotfix, and would move you even further away from a tested system...

3.       Upgrade to XenServer 6.2, which is as free as XCP, and to which yo=
u can safely apply further hotfixes from Citrix.

Cheers,
Rob

From: =EB=CF=CB=DB=C1=D2=CF=D7 =F0=C1=D7=C5=CC =F3=C5=D2=C7=C5=C5=D7=C9=DE =
[mailto:Koksharov.P@amngr.ru]
Sent: 03 July 2014 1:04 PM
To: Rob Hoes
Subject: RE: LICENSE_EXPIRES_SOON

Here http://www.xenproject.org/questions-and-answers/please-help-xcp-1-6-wi=
th-citrix-hotfixes-resulted-in-license-problem-urgent.html , are the same s=
erver. "Alexander" my former colleague, but lost contact with him. I don `t=
 know how he solved the problem. With servers did not do anything, do not p=
ut hot fixes. They both began to send e-mail messages on the end of the lic=
ense. How to be in this situation? Thanks for the help!

From: Rob Hoes [mailto:Rob.Hoes@citrix.com]
Sent: Thursday, July 03, 2014 2:32 PM
To: =EB=CF=CB=DB=C1=D2=CF=D7 =F0=C1=D7=C5=CC =F3=C5=D2=C7=C5=C5=D7=C9=DE; x=
en-api@lists.xenproject.org<mailto:xen-api@lists.xenproject.org>
Subject: RE: LICENSE_EXPIRES_SOON

Hello,

When a license expires in XenServer, any running VMs will continue to run, =
they won't lock up.

I can't remember from the top of my head what the situation was for XCP 1.6=
, but it may be that nothing at all would happen when the "license" expires=
, because the code to do that was switched off. I do remember that we had m=
ade a mistake in this area in the first release, and then released an updat=
e.

I guess it depends on what exactly you have installed: what exactly is the =
hotfix that you have got?

Cheers,
Rob

From: xen-api-bounces@lists.xen.org<mailto:xen-api-bounces@lists.xen.org> [=
mailto:xen-api-bounces@lists.xen.org] On Behalf Of ???????? ????? ?????????
Sent: 03 July 2014 7:37 AM
To: xen-api@lists.xenproject.org<mailto:xen-api@lists.xenproject.org>
Subject: [Xen-API] LICENSE_EXPIRES_SOON

Hello gentlemen.

I've got a serious problem. I'm desperate to say more precisely. My hosts a=
re running XCP 1.6.After upgrade from 1.1 some of my VMs still running MS S=
erver 2003 started to lock up in the state of so called gray screen of deat=
h. After a bit of googling i discovered that it's a bug and Citrix released=
 hotfixes against this disease. So i installed them. Everything went fine u=
ntil recently, when everyday my hosts started to send emails stating that l=
icense is going to expire. Here's an example:

Field Value
----- -----
Name: LICENSE_EXPIRES_SOON
Priority: 10
Class: Host
Object UUID: 40aa0b58-d489-4009-a55a-95c5b151c0ce
Timestamp: 20140703T00:02:01Z
Message UUID: 58fcfb3d-e46c-18d3-700d-4c1080f4d13e
Pool name: zen
Body: Your license will expire in 27 days

I suppose it's because of an updated xapi from Citrix. My question is - wha=
t can i do with this, because i suppose when the counter reaches zero my se=
rvers could just lock up as with ordinary Xenserver. And what's worse, i'm =
not even in the office to physically reach the servers, have network access=
 though. Please, i'd appreciate any help.

--_000_360717C0B01E6345BCBE64B758E22C2D3DF8AAAMSPEX01CL03citri_
Content-Type: text/html; charset="koi8-r"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dkoi8-r">
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:Gisha;
	panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";
	mso-fareast-language:EN-US;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";
	mso-fareast-language:EN-US;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
p.a, li.a, div.a
	{mso-style-name:"\0422\0435\043A\0441\0442 \0432\044B\043D\043E\0441\043A\=
0438";
	mso-style-link:"\0422\0435\043A\0441\0442 \0432\044B\043D\043E\0441\043A\0=
438 \0417\043D\0430\043A";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
span.a0
	{mso-style-name:"\0422\0435\043A\0441\0442 \0432\044B\043D\043E\0441\043A\=
0438 \0417\043D\0430\043A";
	mso-style-priority:99;
	mso-style-link:"\0422\0435\043A\0441\0442 \0432\044B\043D\043E\0441\043A\0=
438";
	font-family:"Tahoma","sans-serif";
	mso-fareast-language:EN-US;}
span.EmailStyle24
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:2.0cm 42.5pt 2.0cm 3.0cm;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1780298690;
	mso-list-type:hybrid;
	mso-list-template-ids:728130932 134807567 134807577 134807579 134807567 13=
4807577 134807579 134807567 134807577 134807579;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I see that Tim Mackey =
has meanwhile answered on the Q&amp;A page you link to below.<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I understand now that =
you have indeed applied an actual XenServer hotfix package to an XCP server=
. Unfortunately, XenServer hotfixes are not usually compatible with XCP (it=
 is definitely not tested this way).
 What this means for licensing, is that the hotfix you have installed must =
have contained a new xapi binary with the licensing checks enabled (as in X=
enServer).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I think that the optio=
ns are:<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 lfo1"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"=
mso-list:Ignore">1.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"colo=
r:#1F497D">Tim to give you a 12-month &#8220;XenServer Free Edition&#8221; =
license file. This may be the easiest way forward in the short term.<o:p></=
o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 lfo1"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"=
mso-list:Ignore">2.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"colo=
r:#1F497D">Reinstall the original xapi RPM package from XCP 1.6, which you =
should be able to find on the XCP install ISO. This would remove the licens=
ing checks again, but would also undo
 any xapi fixes that were present in your hotfix, and would move you even f=
urther away from a tested system&#8230;<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 lfo1"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"=
mso-list:Ignore">3.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span dir=3D"LTR"></span><span style=3D"colo=
r:#1F497D">Upgrade to XenServer 6.2, which is as free as XCP, and to which =
you can safely apply further hotfixes from Citrix.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Cheers,<br>
Rob<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;mso-fareast-language:ZH=
-CN">From:</span></b><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-fa=
mily:&quot;Tahoma&quot;,&quot;sans-serif&quot;;mso-fareast-language:ZH-CN">=
 =EB=CF=CB=DB=C1=D2=CF=D7
 =F0=C1=D7=C5=CC =F3=C5=D2=C7=C5=C5=D7=C9=DE [mailto:Koksharov.P@amngr.ru] =
<br>
<b>Sent:</b> 03 July 2014 1:04 PM<br>
<b>To:</b> Rob Hoes<br>
<b>Subject:</b> RE: LICENSE_EXPIRES_SOON<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Here <a=
 href=3D"http://www.xenproject.org/questions-and-answers/please-help-xcp-1-=
6-with-citrix-hotfixes-resulted-in-license-problem-urgent.html">
http://www.xenproject.org/questions-and-answers/please-help-xcp-1-6-with-ci=
trix-hotfixes-resulted-in-license-problem-urgent.html</a> , are the same se=
rver. &quot;Alexander&quot; my former colleague, but lost contact with him.=
 I don `t know how he solved the problem.
 With servers did not do anything, do not put hot fixes. They both began to=
 send e-mail messages on the end of the license. How to be in this situatio=
n? Thanks for the help!<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"RU" style=3D"font-size:10.0pt;font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;mso-fareast-language:RU">F=
rom:</span></b><span lang=3D"RU" style=3D"font-size:10.0pt;font-family:&quo=
t;Tahoma&quot;,&quot;sans-serif&quot;;mso-fareast-language:RU"> Rob Hoes [<=
a href=3D"mailto:Rob.Hoes@citrix.com">mailto:Rob.Hoes@citrix.com</a>]
<br>
<b>Sent:</b> Thursday, July 03, 2014 2:32 PM<br>
<b>To:</b> =EB=CF=CB=DB=C1=D2=CF=D7 =F0=C1=D7=C5=CC =F3=C5=D2=C7=C5=C5=D7=
=C9=DE; <a href=3D"mailto:xen-api@lists.xenproject.org">
xen-api@lists.xenproject.org</a><br>
<b>Subject:</b> RE: LICENSE_EXPIRES_SOON<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"RU"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hello,<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">When a license expires=
 in XenServer, any running VMs will continue to run, they won&#8217;t lock =
up.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I can&#8217;t remember=
 from the top of my head what the situation was for XCP 1.6, but it may be =
that nothing at all would happen when the &#8220;license&#8221; expires, be=
cause the code to do that was switched off. I do remember
 that we had made a mistake in this area in the first release, and then rel=
eased an update.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I guess it depends on =
what exactly you have installed: what exactly is the hotfix that you have g=
ot?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Cheers,<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Rob<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;mso-fareast-language:ZH=
-CN">From:</span></b><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-fa=
mily:&quot;Tahoma&quot;,&quot;sans-serif&quot;;mso-fareast-language:ZH-CN">
<a href=3D"mailto:xen-api-bounces@lists.xen.org">xen-api-bounces@lists.xen.=
org</a> [<a href=3D"mailto:xen-api-bounces@lists.xen.org">mailto:xen-api-bo=
unces@lists.xen.org</a>]
<b>On Behalf Of </b>???????? ????? ?????????<br>
<b>Sent:</b> 03 July 2014 7:37 AM<br>
<b>To:</b> <a href=3D"mailto:xen-api@lists.xenproject.org">xen-api@lists.xe=
nproject.org</a><br>
<b>Subject:</b> [Xen-API] LICENSE_EXPIRES_SOON<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:9.0pt;font-f=
amily:&quot;Gisha&quot;,&quot;sans-serif&quot;;color:#333333;background:whi=
te">Hello gentlemen.</span><span lang=3D"EN-US" style=3D"font-size:9.0pt;fo=
nt-family:&quot;Gisha&quot;,&quot;sans-serif&quot;;color:#333333"><br>
<br>
<span style=3D"background:white">I've got a serious problem. I'm desperate =
to say more precisely. My hosts are running XCP 1.6.After upgrade from 1.1 =
some of my VMs still running MS Server 2003 started to lock up in the state=
 of so called gray screen of death.
 After a bit of googling i discovered that it's a bug and Citrix released h=
otfixes against this disease. So i installed them. Everything went fine unt=
il recently, when everyday my hosts started to send emails stating that lic=
ense is going to expire. Here's
 an example:</span><br>
<br>
<span style=3D"background:white">Field Value</span><br>
<span style=3D"background:white">----- -----</span><br>
<span style=3D"background:white">Name: LICENSE_EXPIRES_SOON</span><br>
<span style=3D"background:white">Priority: 10</span><br>
<span style=3D"background:white">Class: Host</span><br>
<span style=3D"background:white">Object UUID: 40aa0b58-d489-4009-a55a-95c5b=
151c0ce</span><br>
<span style=3D"background:white">Timestamp: 20140703T00:02:01Z</span><br>
<span style=3D"background:white">Message UUID: 58fcfb3d-e46c-18d3-700d-4c10=
80f4d13e</span><br>
<span style=3D"background:white">Pool name: zen</span><br>
<span style=3D"background:white">Body: Your license will expire in </span><=
/span><span lang=3D"EN-US" style=3D"font-size:9.0pt;color:#333333;backgroun=
d:white">27</span><span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family=
:&quot;Gisha&quot;,&quot;sans-serif&quot;;color:#333333;background:white">
 days</span><span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot=
;Gisha&quot;,&quot;sans-serif&quot;;color:#333333"><br>
<br>
<span style=3D"background:white">I suppose it's because of an updated xapi =
from Citrix. My question is - what can i do with this, because i suppose wh=
en the counter reaches zero my servers could just lock up as with ordinary =
Xenserver. And what's worse, i'm not
 even in the office to physically reach the servers, have network access th=
ough. </span>
</span><span lang=3D"RU" style=3D"font-size:9.0pt;font-family:&quot;Gisha&q=
uot;,&quot;sans-serif&quot;;color:#333333;background:white">Please, i'd app=
reciate any help.</span><span lang=3D"RU"><o:p></o:p></span></p>
</div>
</div>
</div>
</body>
</html>

--_000_360717C0B01E6345BCBE64B758E22C2D3DF8AAAMSPEX01CL03citri_--


--===============5207051324545329962==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--===============5207051324545329962==--


From xen-api-bounces@lists.xen.org Sat Jul 05 14:51:34 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Sat, 05 Jul 2014 14:51:34 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X3RJD-0007dZ-I7; Sat, 05 Jul 2014 14:51:23 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <dobropalka@gmail.com>) id 1X3RJB-0007dU-H8
	for xen-api@lists.xen.org; Sat, 05 Jul 2014 14:51:21 +0000
Received: from [85.158.137.68:22992] by server-9.bemta-3.messagelabs.com id
	A5/2E-09496-8E018B35; Sat, 05 Jul 2014 14:51:20 +0000
X-Env-Sender: dobropalka@gmail.com
X-Msg-Ref: server-5.tower-31.messagelabs.com!1404571878!14246769!1
X-Originating-IP: [209.85.217.171]
X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_30_40,HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_14,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 29665 invoked from network); 5 Jul 2014 14:51:18 -0000
Received: from mail-lb0-f171.google.com (HELO mail-lb0-f171.google.com)
	(209.85.217.171)
	by server-5.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	5 Jul 2014 14:51:18 -0000
Received: by mail-lb0-f171.google.com with SMTP id s7so1775821lbd.2
	for <xen-api@lists.xen.org>; Sat, 05 Jul 2014 07:51:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=from:to:subject:date:message-id:mime-version:content-type
	:thread-index:content-language;
	bh=8lYmYVIs3LijugwN5HzQqsXlysnT7yEd5vAQDx/CiVI=;
	b=we6yLBwWbAZC5JMW4ETBa8GFESDhle4bnpBPpXg9qRJ42JLcLvRMoLElGCsgGk9DTM
	pESPg+v7RHDGVz0nIKv6Pl1MvuJ7XSN2u+YJ8E9365eqlUv6+JnXOMgXv4GUGLcD7Vcs
	Z7IkWq1qs6M7Ppf541+lHm6Wv5rpz1VFtYRlgHBIUhyuiem3EFOcydONyJSlAEvqzXkn
	oRorKqHMV/JiC0QCwaz3+WPenH4y3EBDrPQzJ2ArHaR2fLUqdTq0OIBtwrqhmlR66Pdc
	T+TdQpaO6ayEHmShD3RxAZsQkhuBF0NKcLQ+JdL3peC6Nq4WEh8kmVOLG8524BebqGUj
	8HfQ==
X-Received: by 10.152.116.67 with SMTP id ju3mr13336962lab.38.1404571878068;
	Sat, 05 Jul 2014 07:51:18 -0700 (PDT)
Received: from RUIT06 ([217.23.88.19]) by mx.google.com with ESMTPSA id
	xx9sm10859219lbb.30.2014.07.05.07.51.17 for <xen-api@lists.xen.org>
	(version=TLSv1.2 cipher=ECDHE-RSA-AES128-SHA bits=128/128);
	Sat, 05 Jul 2014 07:51:17 -0700 (PDT)
From: "dobropalka" <dobropalka@gmail.com>
To: <xen-api@lists.xen.org>
Date: Sat, 5 Jul 2014 18:51:16 +0400
Message-ID: <01e901cf9860$935928d0$ba0b7a70$@gmail.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 15.0
Thread-Index: Ac+YYC92YgqTlRQGT7C9IFkmVI8m3A==
Content-Language: ru
Subject: [Xen-API] connection to pool master is buggy
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0235527498685828038=="
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

This is a multipart message in MIME format.

--===============0235527498685828038==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_01EA_01CF9882.1A6C4F70"
Content-Language: ru

This is a multipart message in MIME format.

------=_NextPart_000_01EA_01CF9882.1A6C4F70
Content-Type: text/plain;
	charset="koi8-r"
Content-Transfer-Encoding: 7bit

Hello, guys!



We got a little pool of 4 xenservers. Everything seems to work fine, but all
my xensource logs are full of these debug messages:

 

Jul  4 08:09:56 cloudstack22 xapi: [ info|cloudstack22|221070 UNIX
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|xapi]
Session.create trackid=d99439bce7424c057acf8204cea45f24 pool=false
uname=root is_local_superuser=true auth_user_sid=
parent=trackid=9834f5af41c964e225f24279aefe4e49

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|mscgen] xapi=>xapi
[label="(XML)"];

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|stunnel]
check_reusable: caught exception Unix.Unix_error(31, "write", ""); assuming
not reusable

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|stunnel]
get_reusable_stunnel: Found non-reusable stunnel in the cache. disconnecting
from 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|stunnel]
get_reusable_stunnel: stunnel cache is empty; creating a fresh connection to
10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [ info|cloudstack22|214513 INET
0.0.0.0:80|sm_exec D:176fe384092b|xapi] Session.destroy
trackid=667f0d1664f406698854c89fe03aca7c

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|xmlrpc_client]
stunnel pid: 26281 (cached = true) connected to 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|xmlrpc_client]
with_recorded_stunnelpid task_opt=None s_pid=26281

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|xmlrpc_client]
stunnel pid: 26281 (cached = true) returned stunnel to cache

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221071 UNIX
/var/xapi/xapi||mscgen] xapi=>xapi [label="(XML)"];

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221071 UNIX
/var/xapi/xapi||xmlrpc_client] stunnel pid: 26281 (cached = true) connected
to 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221071 UNIX
/var/xapi/xapi||xmlrpc_client] with_recorded_stunnelpid task_opt=None
s_pid=26281

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221071 UNIX
/var/xapi/xapi||xmlrpc_client] stunnel pid: 26281 (cached = true) returned
stunnel to cache

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX
/var/xapi/xapi||mscgen] xapi=>xapi [label="(XML)"];

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX
/var/xapi/xapi||stunnel] check_reusable: caught exception
Unix.Unix_error(31, "write", ""); assuming not reusable

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX
/var/xapi/xapi||stunnel] get_reusable_stunnel: Found non-reusable stunnel in
the cache. disconnecting from 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX
/var/xapi/xapi||stunnel] get_reusable_stunnel: stunnel cache is empty;
creating a fresh connection to 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX
/var/xapi/xapi||xmlrpc_client] stunnel pid: 26287 (cached = true) connected
to 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX
/var/xapi/xapi||xmlrpc_client] with_recorded_stunnelpid task_opt=None
s_pid=26287

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX
/var/xapi/xapi||xmlrpc_client] stunnel pid: 26287 (cached = true) returned
stunnel to cache

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX
/var/xapi/xapi||mscgen] xapi=>xapi [label="(XML)"];

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX
/var/xapi/xapi||stunnel] check_reusable: caught exception
Unix.Unix_error(31, "write", ""); assuming not reusable

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX
/var/xapi/xapi||stunnel] get_reusable_stunnel: Found non-reusable stunnel in
the cache. disconnecting from 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX
/var/xapi/xapi||stunnel] get_reusable_stunnel: stunnel cache is empty;
creating a fresh connection to 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|214513 INET
0.0.0.0:80|SR.scan R:eb94a1324f62|taskhelper] forwarded task destroyed

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX
/var/xapi/xapi||xmlrpc_client] stunnel pid: 26292 (cached = true) connected
to 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX
/var/xapi/xapi||xmlrpc_client] with_recorded_stunnelpid task_opt=None
s_pid=26292

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX
/var/xapi/xapi||xmlrpc_client] stunnel pid: 26292 (cached = true) returned
stunnel to cache

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX
/var/xapi/xapi||mscgen] xapi=>xapi [label="(XML)"];

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX
/var/xapi/xapi||stunnel] check_reusable: caught exception
Unix.Unix_error(31, "write", ""); assuming not reusable

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX
/var/xapi/xapi||stunnel] get_reusable_stunnel: Found non-reusable stunnel in
the cache. disconnecting from 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX
/var/xapi/xapi||stunnel] get_reusable_stunnel: stunnel cache is empty;
creating a fresh connection to 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX
/var/xapi/xapi||xmlrpc_client] stunnel pid: 26297 (cached = true) connected
to 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX
/var/xapi/xapi||xmlrpc_client] with_recorded_stunnelpid task_opt=None
s_pid=26297

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX
/var/xapi/xapi||xmlrpc_client] stunnel pid: 26297 (cached = true) returned
stunnel to cache

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX
/var/xapi/xapi||mscgen] xapi=>xapi [label="(XML)"];

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX
/var/xapi/xapi||stunnel] check_reusable: caught exception
Unix.Unix_error(31, "write", ""); assuming not reusable

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX
/var/xapi/xapi||stunnel] get_reusable_stunnel: Found non-reusable stunnel in
the cache. disconnecting from 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX
/var/xapi/xapi||stunnel] get_reusable_stunnel: stunnel cache is empty;
creating a fresh connection to 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX
/var/xapi/xapi||xmlrpc_client] stunnel pid: 26302 (cached = true) connected
to 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX
/var/xapi/xapi||xmlrpc_client] with_recorded_stunnelpid task_opt=None
s_pid=26302

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX
/var/xapi/xapi||xmlrpc_client] stunnel pid: 26302 (cached = true) returned
stunnel to cache

 

The only mention I found in internet didn't give me a clue.

Still, cluster works fine, I'm just worried if there's a bug somewhere
deeper then I see and it can cause some problems

 

Regards, 

Ivan Derbenev

 


------=_NextPart_000_01EA_01CF9882.1A6C4F70
Content-Type: text/html;
	charset="koi8-r"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dkoi8-r"><meta =
name=3DGenerator content=3D"Microsoft Word 15 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:2.0cm 42.5pt 2.0cm 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DRU =
link=3D"#0563C1" vlink=3D"#954F72"><div class=3DWordSection1><p =
class=3DMsoNormal><span lang=3DEN-US>Hello, =
guys!<br><br><o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>We got a little pool of 4 xenservers. Everything seems to =
work fine, but all my xensource logs are full of these debug =
messages:<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 xapi: [ =
info|cloudstack22|221070 UNIX /var/xapi/xapi|session.login_with_password =
D:9579fb00c72a|xapi] Session.create =
trackid=3Dd99439bce7424c057acf8204cea45f24 pool=3Dfalse uname=3Droot =
is_local_superuser=3Dtrue auth_user_sid=3D =
parent=3Dtrackid=3D9834f5af41c964e225f24279aefe4e49<o:p></o:p></span></p>=
<p class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221070 UNIX =
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|mscgen] =
xapi=3D&gt;xapi [label=3D&quot;(XML)&quot;];<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221070 UNIX =
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|stunnel] =
check_reusable: caught exception Unix.Unix_error(31, &quot;write&quot;, =
&quot;&quot;); assuming not reusable<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221070 UNIX =
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|stunnel] =
get_reusable_stunnel: Found non-reusable stunnel in the cache. =
disconnecting from 10.50.128.21:443<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221070 UNIX =
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|stunnel] =
get_reusable_stunnel: stunnel cache is empty; creating a fresh =
connection to 10.50.128.21:443<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [ info|cloudstack22|214513 INET 0.0.0.0:80|sm_exec =
D:176fe384092b|xapi] Session.destroy =
trackid=3D667f0d1664f406698854c89fe03aca7c<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221070 UNIX =
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|xmlrpc_client] =
stunnel pid: 26281 (cached =3D true) connected to =
10.50.128.21:443<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221070 UNIX =
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|xmlrpc_client] =
with_recorded_stunnelpid task_opt=3DNone =
s_pid=3D26281<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221070 UNIX =
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|xmlrpc_client] =
stunnel pid: 26281 (cached =3D true) returned stunnel to =
cache<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221071 UNIX /var/xapi/xapi||mscgen] xapi=3D&gt;xapi =
[label=3D&quot;(XML)&quot;];<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221071 UNIX /var/xapi/xapi||xmlrpc_client] =
stunnel pid: 26281 (cached =3D true) connected to =
10.50.128.21:443<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221071 UNIX /var/xapi/xapi||xmlrpc_client] =
with_recorded_stunnelpid task_opt=3DNone =
s_pid=3D26281<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221071 UNIX /var/xapi/xapi||xmlrpc_client] stunnel =
pid: 26281 (cached =3D true) returned stunnel to =
cache<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221072 UNIX /var/xapi/xapi||mscgen] xapi=3D&gt;xapi =
[label=3D&quot;(XML)&quot;];<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221072 UNIX /var/xapi/xapi||stunnel] =
check_reusable: caught exception Unix.Unix_error(31, &quot;write&quot;, =
&quot;&quot;); assuming not reusable<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221072 UNIX /var/xapi/xapi||stunnel] =
get_reusable_stunnel: Found non-reusable stunnel in the cache. =
disconnecting from 10.50.128.21:443<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221072 UNIX /var/xapi/xapi||stunnel] =
get_reusable_stunnel: stunnel cache is empty; creating a fresh =
connection to 10.50.128.21:443<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221072 UNIX /var/xapi/xapi||xmlrpc_client] =
stunnel pid: 26287 (cached =3D true) connected to =
10.50.128.21:443<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221072 UNIX /var/xapi/xapi||xmlrpc_client] =
with_recorded_stunnelpid task_opt=3DNone =
s_pid=3D26287<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221072 UNIX /var/xapi/xapi||xmlrpc_client] stunnel =
pid: 26287 (cached =3D true) returned stunnel to =
cache<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221073 UNIX /var/xapi/xapi||mscgen] xapi=3D&gt;xapi =
[label=3D&quot;(XML)&quot;];<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221073 UNIX /var/xapi/xapi||stunnel] =
check_reusable: caught exception Unix.Unix_error(31, &quot;write&quot;, =
&quot;&quot;); assuming not reusable<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221073 UNIX /var/xapi/xapi||stunnel] =
get_reusable_stunnel: Found non-reusable stunnel in the cache. =
disconnecting from 10.50.128.21:443<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221073 UNIX /var/xapi/xapi||stunnel] =
get_reusable_stunnel: stunnel cache is empty; creating a fresh =
connection to 10.50.128.21:443<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|214513 INET 0.0.0.0:80|SR.scan =
R:eb94a1324f62|taskhelper] forwarded task =
destroyed<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221073 UNIX /var/xapi/xapi||xmlrpc_client] stunnel =
pid: 26292 (cached =3D true) connected to =
10.50.128.21:443<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221073 UNIX /var/xapi/xapi||xmlrpc_client] =
with_recorded_stunnelpid task_opt=3DNone =
s_pid=3D26292<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221073 UNIX /var/xapi/xapi||xmlrpc_client] stunnel =
pid: 26292 (cached =3D true) returned stunnel to =
cache<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221074 UNIX /var/xapi/xapi||mscgen] xapi=3D&gt;xapi =
[label=3D&quot;(XML)&quot;];<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221074 UNIX /var/xapi/xapi||stunnel] =
check_reusable: caught exception Unix.Unix_error(31, &quot;write&quot;, =
&quot;&quot;); assuming not reusable<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221074 UNIX /var/xapi/xapi||stunnel] =
get_reusable_stunnel: Found non-reusable stunnel in the cache. =
disconnecting from 10.50.128.21:443<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221074 UNIX /var/xapi/xapi||stunnel] =
get_reusable_stunnel: stunnel cache is empty; creating a fresh =
connection to 10.50.128.21:443<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221074 UNIX /var/xapi/xapi||xmlrpc_client] =
stunnel pid: 26297 (cached =3D true) connected to =
10.50.128.21:443<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221074 UNIX /var/xapi/xapi||xmlrpc_client] =
with_recorded_stunnelpid task_opt=3DNone =
s_pid=3D26297<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221074 UNIX /var/xapi/xapi||xmlrpc_client] stunnel =
pid: 26297 (cached =3D true) returned stunnel to =
cache<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221075 UNIX /var/xapi/xapi||mscgen] xapi=3D&gt;xapi =
[label=3D&quot;(XML)&quot;];<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221075 UNIX /var/xapi/xapi||stunnel] =
check_reusable: caught exception Unix.Unix_error(31, &quot;write&quot;, =
&quot;&quot;); assuming not reusable<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221075 UNIX /var/xapi/xapi||stunnel] =
get_reusable_stunnel: Found non-reusable stunnel in the cache. =
disconnecting from 10.50.128.21:443<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221075 UNIX /var/xapi/xapi||stunnel] =
get_reusable_stunnel: stunnel cache is empty; creating a fresh =
connection to 10.50.128.21:443<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221075 UNIX /var/xapi/xapi||xmlrpc_client] =
stunnel pid: 26302 (cached =3D true) connected to =
10.50.128.21:443<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221075 UNIX /var/xapi/xapi||xmlrpc_client] =
with_recorded_stunnelpid task_opt=3DNone =
s_pid=3D26302<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221075 UNIX /var/xapi/xapi||xmlrpc_client] stunnel =
pid: 26302 (cached =3D true) returned stunnel to =
cache<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>The only mention I found in internet didn&#8217;t give me a =
clue.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Still, cluster works fine, I&#8217;m just worried if =
there&#8217;s a bug somewhere deeper then I see and it can cause some =
problems<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'mso-fareast-language:RU'>Regards, =
<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:RU'>Ivan Derbenev<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_01EA_01CF9882.1A6C4F70--



--===============0235527498685828038==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--===============0235527498685828038==--



From xen-api-bounces@lists.xen.org Sat Jul 05 14:51:34 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Sat, 05 Jul 2014 14:51:34 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X3RJD-0007dZ-I7; Sat, 05 Jul 2014 14:51:23 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <dobropalka@gmail.com>) id 1X3RJB-0007dU-H8
	for xen-api@lists.xen.org; Sat, 05 Jul 2014 14:51:21 +0000
Received: from [85.158.137.68:22992] by server-9.bemta-3.messagelabs.com id
	A5/2E-09496-8E018B35; Sat, 05 Jul 2014 14:51:20 +0000
X-Env-Sender: dobropalka@gmail.com
X-Msg-Ref: server-5.tower-31.messagelabs.com!1404571878!14246769!1
X-Originating-IP: [209.85.217.171]
X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_30_40,HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_14,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 29665 invoked from network); 5 Jul 2014 14:51:18 -0000
Received: from mail-lb0-f171.google.com (HELO mail-lb0-f171.google.com)
	(209.85.217.171)
	by server-5.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	5 Jul 2014 14:51:18 -0000
Received: by mail-lb0-f171.google.com with SMTP id s7so1775821lbd.2
	for <xen-api@lists.xen.org>; Sat, 05 Jul 2014 07:51:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=from:to:subject:date:message-id:mime-version:content-type
	:thread-index:content-language;
	bh=8lYmYVIs3LijugwN5HzQqsXlysnT7yEd5vAQDx/CiVI=;
	b=we6yLBwWbAZC5JMW4ETBa8GFESDhle4bnpBPpXg9qRJ42JLcLvRMoLElGCsgGk9DTM
	pESPg+v7RHDGVz0nIKv6Pl1MvuJ7XSN2u+YJ8E9365eqlUv6+JnXOMgXv4GUGLcD7Vcs
	Z7IkWq1qs6M7Ppf541+lHm6Wv5rpz1VFtYRlgHBIUhyuiem3EFOcydONyJSlAEvqzXkn
	oRorKqHMV/JiC0QCwaz3+WPenH4y3EBDrPQzJ2ArHaR2fLUqdTq0OIBtwrqhmlR66Pdc
	T+TdQpaO6ayEHmShD3RxAZsQkhuBF0NKcLQ+JdL3peC6Nq4WEh8kmVOLG8524BebqGUj
	8HfQ==
X-Received: by 10.152.116.67 with SMTP id ju3mr13336962lab.38.1404571878068;
	Sat, 05 Jul 2014 07:51:18 -0700 (PDT)
Received: from RUIT06 ([217.23.88.19]) by mx.google.com with ESMTPSA id
	xx9sm10859219lbb.30.2014.07.05.07.51.17 for <xen-api@lists.xen.org>
	(version=TLSv1.2 cipher=ECDHE-RSA-AES128-SHA bits=128/128);
	Sat, 05 Jul 2014 07:51:17 -0700 (PDT)
From: "dobropalka" <dobropalka@gmail.com>
To: <xen-api@lists.xen.org>
Date: Sat, 5 Jul 2014 18:51:16 +0400
Message-ID: <01e901cf9860$935928d0$ba0b7a70$@gmail.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 15.0
Thread-Index: Ac+YYC92YgqTlRQGT7C9IFkmVI8m3A==
Content-Language: ru
Subject: [Xen-API] connection to pool master is buggy
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0235527498685828038=="
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

This is a multipart message in MIME format.

--===============0235527498685828038==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_01EA_01CF9882.1A6C4F70"
Content-Language: ru

This is a multipart message in MIME format.

------=_NextPart_000_01EA_01CF9882.1A6C4F70
Content-Type: text/plain;
	charset="koi8-r"
Content-Transfer-Encoding: 7bit

Hello, guys!



We got a little pool of 4 xenservers. Everything seems to work fine, but all
my xensource logs are full of these debug messages:

 

Jul  4 08:09:56 cloudstack22 xapi: [ info|cloudstack22|221070 UNIX
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|xapi]
Session.create trackid=d99439bce7424c057acf8204cea45f24 pool=false
uname=root is_local_superuser=true auth_user_sid=
parent=trackid=9834f5af41c964e225f24279aefe4e49

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|mscgen] xapi=>xapi
[label="(XML)"];

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|stunnel]
check_reusable: caught exception Unix.Unix_error(31, "write", ""); assuming
not reusable

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|stunnel]
get_reusable_stunnel: Found non-reusable stunnel in the cache. disconnecting
from 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|stunnel]
get_reusable_stunnel: stunnel cache is empty; creating a fresh connection to
10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [ info|cloudstack22|214513 INET
0.0.0.0:80|sm_exec D:176fe384092b|xapi] Session.destroy
trackid=667f0d1664f406698854c89fe03aca7c

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|xmlrpc_client]
stunnel pid: 26281 (cached = true) connected to 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|xmlrpc_client]
with_recorded_stunnelpid task_opt=None s_pid=26281

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|xmlrpc_client]
stunnel pid: 26281 (cached = true) returned stunnel to cache

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221071 UNIX
/var/xapi/xapi||mscgen] xapi=>xapi [label="(XML)"];

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221071 UNIX
/var/xapi/xapi||xmlrpc_client] stunnel pid: 26281 (cached = true) connected
to 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221071 UNIX
/var/xapi/xapi||xmlrpc_client] with_recorded_stunnelpid task_opt=None
s_pid=26281

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221071 UNIX
/var/xapi/xapi||xmlrpc_client] stunnel pid: 26281 (cached = true) returned
stunnel to cache

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX
/var/xapi/xapi||mscgen] xapi=>xapi [label="(XML)"];

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX
/var/xapi/xapi||stunnel] check_reusable: caught exception
Unix.Unix_error(31, "write", ""); assuming not reusable

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX
/var/xapi/xapi||stunnel] get_reusable_stunnel: Found non-reusable stunnel in
the cache. disconnecting from 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX
/var/xapi/xapi||stunnel] get_reusable_stunnel: stunnel cache is empty;
creating a fresh connection to 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX
/var/xapi/xapi||xmlrpc_client] stunnel pid: 26287 (cached = true) connected
to 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX
/var/xapi/xapi||xmlrpc_client] with_recorded_stunnelpid task_opt=None
s_pid=26287

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX
/var/xapi/xapi||xmlrpc_client] stunnel pid: 26287 (cached = true) returned
stunnel to cache

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX
/var/xapi/xapi||mscgen] xapi=>xapi [label="(XML)"];

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX
/var/xapi/xapi||stunnel] check_reusable: caught exception
Unix.Unix_error(31, "write", ""); assuming not reusable

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX
/var/xapi/xapi||stunnel] get_reusable_stunnel: Found non-reusable stunnel in
the cache. disconnecting from 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX
/var/xapi/xapi||stunnel] get_reusable_stunnel: stunnel cache is empty;
creating a fresh connection to 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|214513 INET
0.0.0.0:80|SR.scan R:eb94a1324f62|taskhelper] forwarded task destroyed

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX
/var/xapi/xapi||xmlrpc_client] stunnel pid: 26292 (cached = true) connected
to 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX
/var/xapi/xapi||xmlrpc_client] with_recorded_stunnelpid task_opt=None
s_pid=26292

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX
/var/xapi/xapi||xmlrpc_client] stunnel pid: 26292 (cached = true) returned
stunnel to cache

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX
/var/xapi/xapi||mscgen] xapi=>xapi [label="(XML)"];

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX
/var/xapi/xapi||stunnel] check_reusable: caught exception
Unix.Unix_error(31, "write", ""); assuming not reusable

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX
/var/xapi/xapi||stunnel] get_reusable_stunnel: Found non-reusable stunnel in
the cache. disconnecting from 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX
/var/xapi/xapi||stunnel] get_reusable_stunnel: stunnel cache is empty;
creating a fresh connection to 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX
/var/xapi/xapi||xmlrpc_client] stunnel pid: 26297 (cached = true) connected
to 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX
/var/xapi/xapi||xmlrpc_client] with_recorded_stunnelpid task_opt=None
s_pid=26297

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX
/var/xapi/xapi||xmlrpc_client] stunnel pid: 26297 (cached = true) returned
stunnel to cache

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX
/var/xapi/xapi||mscgen] xapi=>xapi [label="(XML)"];

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX
/var/xapi/xapi||stunnel] check_reusable: caught exception
Unix.Unix_error(31, "write", ""); assuming not reusable

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX
/var/xapi/xapi||stunnel] get_reusable_stunnel: Found non-reusable stunnel in
the cache. disconnecting from 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX
/var/xapi/xapi||stunnel] get_reusable_stunnel: stunnel cache is empty;
creating a fresh connection to 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX
/var/xapi/xapi||xmlrpc_client] stunnel pid: 26302 (cached = true) connected
to 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX
/var/xapi/xapi||xmlrpc_client] with_recorded_stunnelpid task_opt=None
s_pid=26302

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX
/var/xapi/xapi||xmlrpc_client] stunnel pid: 26302 (cached = true) returned
stunnel to cache

 

The only mention I found in internet didn't give me a clue.

Still, cluster works fine, I'm just worried if there's a bug somewhere
deeper then I see and it can cause some problems

 

Regards, 

Ivan Derbenev

 


------=_NextPart_000_01EA_01CF9882.1A6C4F70
Content-Type: text/html;
	charset="koi8-r"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dkoi8-r"><meta =
name=3DGenerator content=3D"Microsoft Word 15 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:2.0cm 42.5pt 2.0cm 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DRU =
link=3D"#0563C1" vlink=3D"#954F72"><div class=3DWordSection1><p =
class=3DMsoNormal><span lang=3DEN-US>Hello, =
guys!<br><br><o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>We got a little pool of 4 xenservers. Everything seems to =
work fine, but all my xensource logs are full of these debug =
messages:<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 xapi: [ =
info|cloudstack22|221070 UNIX /var/xapi/xapi|session.login_with_password =
D:9579fb00c72a|xapi] Session.create =
trackid=3Dd99439bce7424c057acf8204cea45f24 pool=3Dfalse uname=3Droot =
is_local_superuser=3Dtrue auth_user_sid=3D =
parent=3Dtrackid=3D9834f5af41c964e225f24279aefe4e49<o:p></o:p></span></p>=
<p class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221070 UNIX =
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|mscgen] =
xapi=3D&gt;xapi [label=3D&quot;(XML)&quot;];<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221070 UNIX =
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|stunnel] =
check_reusable: caught exception Unix.Unix_error(31, &quot;write&quot;, =
&quot;&quot;); assuming not reusable<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221070 UNIX =
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|stunnel] =
get_reusable_stunnel: Found non-reusable stunnel in the cache. =
disconnecting from 10.50.128.21:443<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221070 UNIX =
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|stunnel] =
get_reusable_stunnel: stunnel cache is empty; creating a fresh =
connection to 10.50.128.21:443<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [ info|cloudstack22|214513 INET 0.0.0.0:80|sm_exec =
D:176fe384092b|xapi] Session.destroy =
trackid=3D667f0d1664f406698854c89fe03aca7c<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221070 UNIX =
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|xmlrpc_client] =
stunnel pid: 26281 (cached =3D true) connected to =
10.50.128.21:443<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221070 UNIX =
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|xmlrpc_client] =
with_recorded_stunnelpid task_opt=3DNone =
s_pid=3D26281<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221070 UNIX =
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|xmlrpc_client] =
stunnel pid: 26281 (cached =3D true) returned stunnel to =
cache<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221071 UNIX /var/xapi/xapi||mscgen] xapi=3D&gt;xapi =
[label=3D&quot;(XML)&quot;];<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221071 UNIX /var/xapi/xapi||xmlrpc_client] =
stunnel pid: 26281 (cached =3D true) connected to =
10.50.128.21:443<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221071 UNIX /var/xapi/xapi||xmlrpc_client] =
with_recorded_stunnelpid task_opt=3DNone =
s_pid=3D26281<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221071 UNIX /var/xapi/xapi||xmlrpc_client] stunnel =
pid: 26281 (cached =3D true) returned stunnel to =
cache<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221072 UNIX /var/xapi/xapi||mscgen] xapi=3D&gt;xapi =
[label=3D&quot;(XML)&quot;];<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221072 UNIX /var/xapi/xapi||stunnel] =
check_reusable: caught exception Unix.Unix_error(31, &quot;write&quot;, =
&quot;&quot;); assuming not reusable<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221072 UNIX /var/xapi/xapi||stunnel] =
get_reusable_stunnel: Found non-reusable stunnel in the cache. =
disconnecting from 10.50.128.21:443<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221072 UNIX /var/xapi/xapi||stunnel] =
get_reusable_stunnel: stunnel cache is empty; creating a fresh =
connection to 10.50.128.21:443<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221072 UNIX /var/xapi/xapi||xmlrpc_client] =
stunnel pid: 26287 (cached =3D true) connected to =
10.50.128.21:443<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221072 UNIX /var/xapi/xapi||xmlrpc_client] =
with_recorded_stunnelpid task_opt=3DNone =
s_pid=3D26287<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221072 UNIX /var/xapi/xapi||xmlrpc_client] stunnel =
pid: 26287 (cached =3D true) returned stunnel to =
cache<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221073 UNIX /var/xapi/xapi||mscgen] xapi=3D&gt;xapi =
[label=3D&quot;(XML)&quot;];<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221073 UNIX /var/xapi/xapi||stunnel] =
check_reusable: caught exception Unix.Unix_error(31, &quot;write&quot;, =
&quot;&quot;); assuming not reusable<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221073 UNIX /var/xapi/xapi||stunnel] =
get_reusable_stunnel: Found non-reusable stunnel in the cache. =
disconnecting from 10.50.128.21:443<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221073 UNIX /var/xapi/xapi||stunnel] =
get_reusable_stunnel: stunnel cache is empty; creating a fresh =
connection to 10.50.128.21:443<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|214513 INET 0.0.0.0:80|SR.scan =
R:eb94a1324f62|taskhelper] forwarded task =
destroyed<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221073 UNIX /var/xapi/xapi||xmlrpc_client] stunnel =
pid: 26292 (cached =3D true) connected to =
10.50.128.21:443<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221073 UNIX /var/xapi/xapi||xmlrpc_client] =
with_recorded_stunnelpid task_opt=3DNone =
s_pid=3D26292<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221073 UNIX /var/xapi/xapi||xmlrpc_client] stunnel =
pid: 26292 (cached =3D true) returned stunnel to =
cache<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221074 UNIX /var/xapi/xapi||mscgen] xapi=3D&gt;xapi =
[label=3D&quot;(XML)&quot;];<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221074 UNIX /var/xapi/xapi||stunnel] =
check_reusable: caught exception Unix.Unix_error(31, &quot;write&quot;, =
&quot;&quot;); assuming not reusable<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221074 UNIX /var/xapi/xapi||stunnel] =
get_reusable_stunnel: Found non-reusable stunnel in the cache. =
disconnecting from 10.50.128.21:443<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221074 UNIX /var/xapi/xapi||stunnel] =
get_reusable_stunnel: stunnel cache is empty; creating a fresh =
connection to 10.50.128.21:443<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221074 UNIX /var/xapi/xapi||xmlrpc_client] =
stunnel pid: 26297 (cached =3D true) connected to =
10.50.128.21:443<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221074 UNIX /var/xapi/xapi||xmlrpc_client] =
with_recorded_stunnelpid task_opt=3DNone =
s_pid=3D26297<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221074 UNIX /var/xapi/xapi||xmlrpc_client] stunnel =
pid: 26297 (cached =3D true) returned stunnel to =
cache<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221075 UNIX /var/xapi/xapi||mscgen] xapi=3D&gt;xapi =
[label=3D&quot;(XML)&quot;];<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221075 UNIX /var/xapi/xapi||stunnel] =
check_reusable: caught exception Unix.Unix_error(31, &quot;write&quot;, =
&quot;&quot;); assuming not reusable<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221075 UNIX /var/xapi/xapi||stunnel] =
get_reusable_stunnel: Found non-reusable stunnel in the cache. =
disconnecting from 10.50.128.21:443<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221075 UNIX /var/xapi/xapi||stunnel] =
get_reusable_stunnel: stunnel cache is empty; creating a fresh =
connection to 10.50.128.21:443<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221075 UNIX /var/xapi/xapi||xmlrpc_client] =
stunnel pid: 26302 (cached =3D true) connected to =
10.50.128.21:443<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221075 UNIX /var/xapi/xapi||xmlrpc_client] =
with_recorded_stunnelpid task_opt=3DNone =
s_pid=3D26302<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul=9A 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221075 UNIX /var/xapi/xapi||xmlrpc_client] stunnel =
pid: 26302 (cached =3D true) returned stunnel to =
cache<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>The only mention I found in internet didn&#8217;t give me a =
clue.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Still, cluster works fine, I&#8217;m just worried if =
there&#8217;s a bug somewhere deeper then I see and it can cause some =
problems<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'mso-fareast-language:RU'>Regards, =
<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:RU'>Ivan Derbenev<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_01EA_01CF9882.1A6C4F70--



--===============0235527498685828038==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--===============0235527498685828038==--



From xen-api-bounces@lists.xen.org Mon Jul 07 10:51:40 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Mon, 07 Jul 2014 10:51:40 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X46WA-0006Ux-C0; Mon, 07 Jul 2014 10:51:30 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <Jonathan.Ludlam@citrix.com>) id 1X46Uf-0006R3-ME
	for xen-api@lists.xen.org; Mon, 07 Jul 2014 10:49:58 +0000
Received: from [85.158.143.35:51394] by server-1.bemta-4.messagelabs.com id
	F8/AA-09496-45B7AB35; Mon, 07 Jul 2014 10:49:56 +0000
X-Env-Sender: Jonathan.Ludlam@citrix.com
X-Msg-Ref: server-4.tower-21.messagelabs.com!1404730194!16260668!1
X-Originating-IP: [185.25.65.24]
X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 15015 invoked from network); 7 Jul 2014 10:49:54 -0000
Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24)
	by server-4.tower-21.messagelabs.com with SMTP;
	7 Jul 2014 10:49:54 -0000
X-IronPort-AV: E=Sophos;i="5.01,617,1400025600"; d="scan'208,217";a="22888822"
Received: from unknown (HELO AMSPEX01CL02.citrite.net) ([10.69.60.9])
	by AMSPIP01.EU.Citrix.com with ESMTP; 07 Jul 2014 10:49:54 +0000
Received: from AMSPEX01CL01.citrite.net ([169.254.6.105]) by
	AMSPEX01CL02.citrite.net ([10.69.46.33]) with mapi id 14.03.0181.006;
	Mon, 7 Jul 2014 12:49:54 +0200
From: Jonathan Ludlam <Jonathan.Ludlam@citrix.com>
To: 'dobropalka' <dobropalka@gmail.com>, "xen-api@lists.xen.org"
	<xen-api@lists.xen.org>
Thread-Topic: [Xen-API] connection to pool master is buggy
Thread-Index: Ac+YYC92YgqTlRQGT7C9IFkmVI8m3ABcOPUA
Date: Mon, 7 Jul 2014 10:49:53 +0000
Message-ID: <660D43EB050DE94AACCFA0BB1489A98278C04F@AMSPEX01CL01.citrite.net>
References: <01e901cf9860$935928d0$ba0b7a70$@gmail.com>
In-Reply-To: <01e901cf9860$935928d0$ba0b7a70$@gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.69.129.53]
MIME-Version: 1.0
X-DLP: AMS1
X-Mailman-Approved-At: Mon, 07 Jul 2014 10:51:29 +0000
Subject: Re: [Xen-API] connection to pool master is buggy
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============5041203007781533768=="
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

--===============5041203007781533768==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_660D43EB050DE94AACCFA0BB1489A98278C04FAMSPEX01CL01citri_"

--_000_660D43EB050DE94AACCFA0BB1489A98278C04FAMSPEX01CL01citri_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Ivan,

These messages are benign. At some point we'd like to clean up the logging,=
 as it does tend to be a bit spammy.

Cheers,

Jon


From: xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org] =
On Behalf Of dobropalka
Sent: 05 July 2014 3:51 PM
To: xen-api@lists.xen.org
Subject: [Xen-API] connection to pool master is buggy

Hello, guys!
We got a little pool of 4 xenservers. Everything seems to work fine, but al=
l my xensource logs are full of these debug messages:

Jul  4 08:09:56 cloudstack22 xapi: [ info|cloudstack22|221070 UNIX /var/xap=
i/xapi|session.login_with_password D:9579fb00c72a|xapi] Session.create trac=
kid=3Dd99439bce7424c057acf8204cea45f24 pool=3Dfalse uname=3Droot is_local_s=
uperuser=3Dtrue auth_user_sid=3D parent=3Dtrackid=3D9834f5af41c964e225f2427=
9aefe4e49
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX /var/xap=
i/xapi|session.login_with_password D:9579fb00c72a|mscgen] xapi=3D>xapi [lab=
el=3D"(XML)"];
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX /var/xap=
i/xapi|session.login_with_password D:9579fb00c72a|stunnel] check_reusable: =
caught exception Unix.Unix_error(31, "write", ""); assuming not reusable
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX /var/xap=
i/xapi|session.login_with_password D:9579fb00c72a|stunnel] get_reusable_stu=
nnel: Found non-reusable stunnel in the cache. disconnecting from 10.50.128=
.21:443
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX /var/xap=
i/xapi|session.login_with_password D:9579fb00c72a|stunnel] get_reusable_stu=
nnel: stunnel cache is empty; creating a fresh connection to 10.50.128.21:4=
43
Jul  4 08:09:56 cloudstack22 xapi: [ info|cloudstack22|214513 INET 0.0.0.0:=
80|sm_exec D:176fe384092b|xapi] Session.destroy trackid=3D667f0d1664f406698=
854c89fe03aca7c
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX /var/xap=
i/xapi|session.login_with_password D:9579fb00c72a|xmlrpc_client] stunnel pi=
d: 26281 (cached =3D true) connected to 10.50.128.21:443
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX /var/xap=
i/xapi|session.login_with_password D:9579fb00c72a|xmlrpc_client] with_recor=
ded_stunnelpid task_opt=3DNone s_pid=3D26281
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX /var/xap=
i/xapi|session.login_with_password D:9579fb00c72a|xmlrpc_client] stunnel pi=
d: 26281 (cached =3D true) returned stunnel to cache
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221071 UNIX /var/xap=
i/xapi||mscgen] xapi=3D>xapi [label=3D"(XML)"];
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221071 UNIX /var/xap=
i/xapi||xmlrpc_client] stunnel pid: 26281 (cached =3D true) connected to 10=
.50.128.21:443
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221071 UNIX /var/xap=
i/xapi||xmlrpc_client] with_recorded_stunnelpid task_opt=3DNone s_pid=3D262=
81
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221071 UNIX /var/xap=
i/xapi||xmlrpc_client] stunnel pid: 26281 (cached =3D true) returned stunne=
l to cache
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX /var/xap=
i/xapi||mscgen] xapi=3D>xapi [label=3D"(XML)"];
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX /var/xap=
i/xapi||stunnel] check_reusable: caught exception Unix.Unix_error(31, "writ=
e", ""); assuming not reusable
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX /var/xap=
i/xapi||stunnel] get_reusable_stunnel: Found non-reusable stunnel in the ca=
che. disconnecting from 10.50.128.21:443
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX /var/xap=
i/xapi||stunnel] get_reusable_stunnel: stunnel cache is empty; creating a f=
resh connection to 10.50.128.21:443
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX /var/xap=
i/xapi||xmlrpc_client] stunnel pid: 26287 (cached =3D true) connected to 10=
.50.128.21:443
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX /var/xap=
i/xapi||xmlrpc_client] with_recorded_stunnelpid task_opt=3DNone s_pid=3D262=
87
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX /var/xap=
i/xapi||xmlrpc_client] stunnel pid: 26287 (cached =3D true) returned stunne=
l to cache
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX /var/xap=
i/xapi||mscgen] xapi=3D>xapi [label=3D"(XML)"];
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX /var/xap=
i/xapi||stunnel] check_reusable: caught exception Unix.Unix_error(31, "writ=
e", ""); assuming not reusable
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX /var/xap=
i/xapi||stunnel] get_reusable_stunnel: Found non-reusable stunnel in the ca=
che. disconnecting from 10.50.128.21:443
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX /var/xap=
i/xapi||stunnel] get_reusable_stunnel: stunnel cache is empty; creating a f=
resh connection to 10.50.128.21:443
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|214513 INET 0.0.0.0:=
80|SR.scan R:eb94a1324f62|taskhelper] forwarded task destroyed
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX /var/xap=
i/xapi||xmlrpc_client] stunnel pid: 26292 (cached =3D true) connected to 10=
.50.128.21:443
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX /var/xap=
i/xapi||xmlrpc_client] with_recorded_stunnelpid task_opt=3DNone s_pid=3D262=
92
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX /var/xap=
i/xapi||xmlrpc_client] stunnel pid: 26292 (cached =3D true) returned stunne=
l to cache
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX /var/xap=
i/xapi||mscgen] xapi=3D>xapi [label=3D"(XML)"];
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX /var/xap=
i/xapi||stunnel] check_reusable: caught exception Unix.Unix_error(31, "writ=
e", ""); assuming not reusable
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX /var/xap=
i/xapi||stunnel] get_reusable_stunnel: Found non-reusable stunnel in the ca=
che. disconnecting from 10.50.128.21:443
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX /var/xap=
i/xapi||stunnel] get_reusable_stunnel: stunnel cache is empty; creating a f=
resh connection to 10.50.128.21:443
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX /var/xap=
i/xapi||xmlrpc_client] stunnel pid: 26297 (cached =3D true) connected to 10=
.50.128.21:443
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX /var/xap=
i/xapi||xmlrpc_client] with_recorded_stunnelpid task_opt=3DNone s_pid=3D262=
97
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX /var/xap=
i/xapi||xmlrpc_client] stunnel pid: 26297 (cached =3D true) returned stunne=
l to cache
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX /var/xap=
i/xapi||mscgen] xapi=3D>xapi [label=3D"(XML)"];
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX /var/xap=
i/xapi||stunnel] check_reusable: caught exception Unix.Unix_error(31, "writ=
e", ""); assuming not reusable
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX /var/xap=
i/xapi||stunnel] get_reusable_stunnel: Found non-reusable stunnel in the ca=
che. disconnecting from 10.50.128.21:443
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX /var/xap=
i/xapi||stunnel] get_reusable_stunnel: stunnel cache is empty; creating a f=
resh connection to 10.50.128.21:443
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX /var/xap=
i/xapi||xmlrpc_client] stunnel pid: 26302 (cached =3D true) connected to 10=
.50.128.21:443
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX /var/xap=
i/xapi||xmlrpc_client] with_recorded_stunnelpid task_opt=3DNone s_pid=3D263=
02
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX /var/xap=
i/xapi||xmlrpc_client] stunnel pid: 26302 (cached =3D true) returned stunne=
l to cache

The only mention I found in internet didn't give me a clue.
Still, cluster works fine, I'm just worried if there's a bug somewhere deep=
er then I see and it can cause some problems

Regards,
Ivan Derbenev


--_000_660D43EB050DE94AACCFA0BB1489A98278C04FAMSPEX01CL01citri_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:2.0cm 42.5pt 2.0cm 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Ivan,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">These messages are ben=
ign. At some point we&#8217;d like to clean up the logging, as it does tend=
 to be a bit spammy.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Cheers,<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Jon<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;mso-fareast-language:ZH=
-CN">From:</span></b><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-fa=
mily:&quot;Tahoma&quot;,&quot;sans-serif&quot;;mso-fareast-language:ZH-CN">=
 xen-api-bounces@lists.xen.org
 [mailto:xen-api-bounces@lists.xen.org] <b>On Behalf Of </b>dobropalka<br>
<b>Sent:</b> 05 July 2014 3:51 PM<br>
<b>To:</b> xen-api@lists.xen.org<br>
<b>Subject:</b> [Xen-API] connection to pool master is buggy<o:p></o:p></sp=
an></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US">=
Hello, guys!<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">We got a little pool of 4 xense=
rvers. Everything seems to work fine, but all my xensource logs are full of=
 these debug messages:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [ info|cloudstack22|221070 UNIX /var/xapi/xapi|session.login_with_=
password D:9579fb00c72a|xapi] Session.create trackid=3Dd99439bce7424c057acf=
8204cea45f24 pool=3Dfalse uname=3Droot is_local_superuser=3Dtrue
 auth_user_sid=3D parent=3Dtrackid=3D9834f5af41c964e225f24279aefe4e49<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221070 UNIX /var/xapi/xapi|session.login_with_=
password D:9579fb00c72a|mscgen] xapi=3D&gt;xapi [label=3D&quot;(XML)&quot;]=
;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221070 UNIX /var/xapi/xapi|session.login_with_=
password D:9579fb00c72a|stunnel] check_reusable: caught exception Unix.Unix=
_error(31, &quot;write&quot;, &quot;&quot;); assuming not reusable<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221070 UNIX /var/xapi/xapi|session.login_with_=
password D:9579fb00c72a|stunnel] get_reusable_stunnel: Found non-reusable s=
tunnel in the cache. disconnecting from 10.50.128.21:443<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221070 UNIX /var/xapi/xapi|session.login_with_=
password D:9579fb00c72a|stunnel] get_reusable_stunnel: stunnel cache is emp=
ty; creating a fresh connection to 10.50.128.21:443<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [ info|cloudstack22|214513 INET 0.0.0.0:80|sm_exec D:176fe384092b|=
xapi] Session.destroy trackid=3D667f0d1664f406698854c89fe03aca7c<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221070 UNIX /var/xapi/xapi|session.login_with_=
password D:9579fb00c72a|xmlrpc_client] stunnel pid: 26281 (cached =3D true)=
 connected to 10.50.128.21:443<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221070 UNIX /var/xapi/xapi|session.login_with_=
password D:9579fb00c72a|xmlrpc_client] with_recorded_stunnelpid task_opt=3D=
None s_pid=3D26281<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221070 UNIX /var/xapi/xapi|session.login_with_=
password D:9579fb00c72a|xmlrpc_client] stunnel pid: 26281 (cached =3D true)=
 returned stunnel to cache<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221071 UNIX /var/xapi/xapi||mscgen] xapi=3D&gt=
;xapi [label=3D&quot;(XML)&quot;];<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221071 UNIX /var/xapi/xapi||xmlrpc_client] stu=
nnel pid: 26281 (cached =3D true) connected to 10.50.128.21:443<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221071 UNIX /var/xapi/xapi||xmlrpc_client] wit=
h_recorded_stunnelpid task_opt=3DNone s_pid=3D26281<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221071 UNIX /var/xapi/xapi||xmlrpc_client] stu=
nnel pid: 26281 (cached =3D true) returned stunnel to cache<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221072 UNIX /var/xapi/xapi||mscgen] xapi=3D&gt=
;xapi [label=3D&quot;(XML)&quot;];<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221072 UNIX /var/xapi/xapi||stunnel] check_reu=
sable: caught exception Unix.Unix_error(31, &quot;write&quot;, &quot;&quot;=
); assuming not reusable<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221072 UNIX /var/xapi/xapi||stunnel] get_reusa=
ble_stunnel: Found non-reusable stunnel in the cache. disconnecting from 10=
.50.128.21:443<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221072 UNIX /var/xapi/xapi||stunnel] get_reusa=
ble_stunnel: stunnel cache is empty; creating a fresh connection to 10.50.1=
28.21:443<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221072 UNIX /var/xapi/xapi||xmlrpc_client] stu=
nnel pid: 26287 (cached =3D true) connected to 10.50.128.21:443<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221072 UNIX /var/xapi/xapi||xmlrpc_client] wit=
h_recorded_stunnelpid task_opt=3DNone s_pid=3D26287<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221072 UNIX /var/xapi/xapi||xmlrpc_client] stu=
nnel pid: 26287 (cached =3D true) returned stunnel to cache<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221073 UNIX /var/xapi/xapi||mscgen] xapi=3D&gt=
;xapi [label=3D&quot;(XML)&quot;];<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221073 UNIX /var/xapi/xapi||stunnel] check_reu=
sable: caught exception Unix.Unix_error(31, &quot;write&quot;, &quot;&quot;=
); assuming not reusable<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221073 UNIX /var/xapi/xapi||stunnel] get_reusa=
ble_stunnel: Found non-reusable stunnel in the cache. disconnecting from 10=
.50.128.21:443<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221073 UNIX /var/xapi/xapi||stunnel] get_reusa=
ble_stunnel: stunnel cache is empty; creating a fresh connection to 10.50.1=
28.21:443<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|214513 INET 0.0.0.0:80|SR.scan R:eb94a1324f62|=
taskhelper] forwarded task destroyed<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221073 UNIX /var/xapi/xapi||xmlrpc_client] stu=
nnel pid: 26292 (cached =3D true) connected to 10.50.128.21:443<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221073 UNIX /var/xapi/xapi||xmlrpc_client] wit=
h_recorded_stunnelpid task_opt=3DNone s_pid=3D26292<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221073 UNIX /var/xapi/xapi||xmlrpc_client] stu=
nnel pid: 26292 (cached =3D true) returned stunnel to cache<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221074 UNIX /var/xapi/xapi||mscgen] xapi=3D&gt=
;xapi [label=3D&quot;(XML)&quot;];<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221074 UNIX /var/xapi/xapi||stunnel] check_reu=
sable: caught exception Unix.Unix_error(31, &quot;write&quot;, &quot;&quot;=
); assuming not reusable<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221074 UNIX /var/xapi/xapi||stunnel] get_reusa=
ble_stunnel: Found non-reusable stunnel in the cache. disconnecting from 10=
.50.128.21:443<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221074 UNIX /var/xapi/xapi||stunnel] get_reusa=
ble_stunnel: stunnel cache is empty; creating a fresh connection to 10.50.1=
28.21:443<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221074 UNIX /var/xapi/xapi||xmlrpc_client] stu=
nnel pid: 26297 (cached =3D true) connected to 10.50.128.21:443<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221074 UNIX /var/xapi/xapi||xmlrpc_client] wit=
h_recorded_stunnelpid task_opt=3DNone s_pid=3D26297<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221074 UNIX /var/xapi/xapi||xmlrpc_client] stu=
nnel pid: 26297 (cached =3D true) returned stunnel to cache<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221075 UNIX /var/xapi/xapi||mscgen] xapi=3D&gt=
;xapi [label=3D&quot;(XML)&quot;];<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221075 UNIX /var/xapi/xapi||stunnel] check_reu=
sable: caught exception Unix.Unix_error(31, &quot;write&quot;, &quot;&quot;=
); assuming not reusable<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221075 UNIX /var/xapi/xapi||stunnel] get_reusa=
ble_stunnel: Found non-reusable stunnel in the cache. disconnecting from 10=
.50.128.21:443<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221075 UNIX /var/xapi/xapi||stunnel] get_reusa=
ble_stunnel: stunnel cache is empty; creating a fresh connection to 10.50.1=
28.21:443<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221075 UNIX /var/xapi/xapi||xmlrpc_client] stu=
nnel pid: 26302 (cached =3D true) connected to 10.50.128.21:443<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221075 UNIX /var/xapi/xapi||xmlrpc_client] wit=
h_recorded_stunnelpid task_opt=3DNone s_pid=3D26302<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221075 UNIX /var/xapi/xapi||xmlrpc_client] stu=
nnel pid: 26302 (cached =3D true) returned stunnel to cache<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">The only mention I found in int=
ernet didn&#8217;t give me a clue.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Still, cluster works fine, I&#8=
217;m just worried if there&#8217;s a bug somewhere deeper then I see and i=
t can cause some problems<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"mso-fareast-language:R=
U">Regards, <o:p>
</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"mso-fareast-language:R=
U">Ivan Derbenev<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"RU"><o:p>&nbsp;</o:p></span></p>
</div>
</body>
</html>

--_000_660D43EB050DE94AACCFA0BB1489A98278C04FAMSPEX01CL01citri_--


--===============5041203007781533768==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--===============5041203007781533768==--


From xen-api-bounces@lists.xen.org Mon Jul 07 10:51:40 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Mon, 07 Jul 2014 10:51:40 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X46WA-0006Ux-C0; Mon, 07 Jul 2014 10:51:30 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <Jonathan.Ludlam@citrix.com>) id 1X46Uf-0006R3-ME
	for xen-api@lists.xen.org; Mon, 07 Jul 2014 10:49:58 +0000
Received: from [85.158.143.35:51394] by server-1.bemta-4.messagelabs.com id
	F8/AA-09496-45B7AB35; Mon, 07 Jul 2014 10:49:56 +0000
X-Env-Sender: Jonathan.Ludlam@citrix.com
X-Msg-Ref: server-4.tower-21.messagelabs.com!1404730194!16260668!1
X-Originating-IP: [185.25.65.24]
X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 15015 invoked from network); 7 Jul 2014 10:49:54 -0000
Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24)
	by server-4.tower-21.messagelabs.com with SMTP;
	7 Jul 2014 10:49:54 -0000
X-IronPort-AV: E=Sophos;i="5.01,617,1400025600"; d="scan'208,217";a="22888822"
Received: from unknown (HELO AMSPEX01CL02.citrite.net) ([10.69.60.9])
	by AMSPIP01.EU.Citrix.com with ESMTP; 07 Jul 2014 10:49:54 +0000
Received: from AMSPEX01CL01.citrite.net ([169.254.6.105]) by
	AMSPEX01CL02.citrite.net ([10.69.46.33]) with mapi id 14.03.0181.006;
	Mon, 7 Jul 2014 12:49:54 +0200
From: Jonathan Ludlam <Jonathan.Ludlam@citrix.com>
To: 'dobropalka' <dobropalka@gmail.com>, "xen-api@lists.xen.org"
	<xen-api@lists.xen.org>
Thread-Topic: [Xen-API] connection to pool master is buggy
Thread-Index: Ac+YYC92YgqTlRQGT7C9IFkmVI8m3ABcOPUA
Date: Mon, 7 Jul 2014 10:49:53 +0000
Message-ID: <660D43EB050DE94AACCFA0BB1489A98278C04F@AMSPEX01CL01.citrite.net>
References: <01e901cf9860$935928d0$ba0b7a70$@gmail.com>
In-Reply-To: <01e901cf9860$935928d0$ba0b7a70$@gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.69.129.53]
MIME-Version: 1.0
X-DLP: AMS1
X-Mailman-Approved-At: Mon, 07 Jul 2014 10:51:29 +0000
Subject: Re: [Xen-API] connection to pool master is buggy
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============5041203007781533768=="
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

--===============5041203007781533768==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_660D43EB050DE94AACCFA0BB1489A98278C04FAMSPEX01CL01citri_"

--_000_660D43EB050DE94AACCFA0BB1489A98278C04FAMSPEX01CL01citri_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Ivan,

These messages are benign. At some point we'd like to clean up the logging,=
 as it does tend to be a bit spammy.

Cheers,

Jon


From: xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org] =
On Behalf Of dobropalka
Sent: 05 July 2014 3:51 PM
To: xen-api@lists.xen.org
Subject: [Xen-API] connection to pool master is buggy

Hello, guys!
We got a little pool of 4 xenservers. Everything seems to work fine, but al=
l my xensource logs are full of these debug messages:

Jul  4 08:09:56 cloudstack22 xapi: [ info|cloudstack22|221070 UNIX /var/xap=
i/xapi|session.login_with_password D:9579fb00c72a|xapi] Session.create trac=
kid=3Dd99439bce7424c057acf8204cea45f24 pool=3Dfalse uname=3Droot is_local_s=
uperuser=3Dtrue auth_user_sid=3D parent=3Dtrackid=3D9834f5af41c964e225f2427=
9aefe4e49
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX /var/xap=
i/xapi|session.login_with_password D:9579fb00c72a|mscgen] xapi=3D>xapi [lab=
el=3D"(XML)"];
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX /var/xap=
i/xapi|session.login_with_password D:9579fb00c72a|stunnel] check_reusable: =
caught exception Unix.Unix_error(31, "write", ""); assuming not reusable
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX /var/xap=
i/xapi|session.login_with_password D:9579fb00c72a|stunnel] get_reusable_stu=
nnel: Found non-reusable stunnel in the cache. disconnecting from 10.50.128=
.21:443
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX /var/xap=
i/xapi|session.login_with_password D:9579fb00c72a|stunnel] get_reusable_stu=
nnel: stunnel cache is empty; creating a fresh connection to 10.50.128.21:4=
43
Jul  4 08:09:56 cloudstack22 xapi: [ info|cloudstack22|214513 INET 0.0.0.0:=
80|sm_exec D:176fe384092b|xapi] Session.destroy trackid=3D667f0d1664f406698=
854c89fe03aca7c
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX /var/xap=
i/xapi|session.login_with_password D:9579fb00c72a|xmlrpc_client] stunnel pi=
d: 26281 (cached =3D true) connected to 10.50.128.21:443
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX /var/xap=
i/xapi|session.login_with_password D:9579fb00c72a|xmlrpc_client] with_recor=
ded_stunnelpid task_opt=3DNone s_pid=3D26281
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX /var/xap=
i/xapi|session.login_with_password D:9579fb00c72a|xmlrpc_client] stunnel pi=
d: 26281 (cached =3D true) returned stunnel to cache
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221071 UNIX /var/xap=
i/xapi||mscgen] xapi=3D>xapi [label=3D"(XML)"];
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221071 UNIX /var/xap=
i/xapi||xmlrpc_client] stunnel pid: 26281 (cached =3D true) connected to 10=
.50.128.21:443
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221071 UNIX /var/xap=
i/xapi||xmlrpc_client] with_recorded_stunnelpid task_opt=3DNone s_pid=3D262=
81
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221071 UNIX /var/xap=
i/xapi||xmlrpc_client] stunnel pid: 26281 (cached =3D true) returned stunne=
l to cache
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX /var/xap=
i/xapi||mscgen] xapi=3D>xapi [label=3D"(XML)"];
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX /var/xap=
i/xapi||stunnel] check_reusable: caught exception Unix.Unix_error(31, "writ=
e", ""); assuming not reusable
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX /var/xap=
i/xapi||stunnel] get_reusable_stunnel: Found non-reusable stunnel in the ca=
che. disconnecting from 10.50.128.21:443
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX /var/xap=
i/xapi||stunnel] get_reusable_stunnel: stunnel cache is empty; creating a f=
resh connection to 10.50.128.21:443
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX /var/xap=
i/xapi||xmlrpc_client] stunnel pid: 26287 (cached =3D true) connected to 10=
.50.128.21:443
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX /var/xap=
i/xapi||xmlrpc_client] with_recorded_stunnelpid task_opt=3DNone s_pid=3D262=
87
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX /var/xap=
i/xapi||xmlrpc_client] stunnel pid: 26287 (cached =3D true) returned stunne=
l to cache
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX /var/xap=
i/xapi||mscgen] xapi=3D>xapi [label=3D"(XML)"];
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX /var/xap=
i/xapi||stunnel] check_reusable: caught exception Unix.Unix_error(31, "writ=
e", ""); assuming not reusable
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX /var/xap=
i/xapi||stunnel] get_reusable_stunnel: Found non-reusable stunnel in the ca=
che. disconnecting from 10.50.128.21:443
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX /var/xap=
i/xapi||stunnel] get_reusable_stunnel: stunnel cache is empty; creating a f=
resh connection to 10.50.128.21:443
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|214513 INET 0.0.0.0:=
80|SR.scan R:eb94a1324f62|taskhelper] forwarded task destroyed
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX /var/xap=
i/xapi||xmlrpc_client] stunnel pid: 26292 (cached =3D true) connected to 10=
.50.128.21:443
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX /var/xap=
i/xapi||xmlrpc_client] with_recorded_stunnelpid task_opt=3DNone s_pid=3D262=
92
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX /var/xap=
i/xapi||xmlrpc_client] stunnel pid: 26292 (cached =3D true) returned stunne=
l to cache
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX /var/xap=
i/xapi||mscgen] xapi=3D>xapi [label=3D"(XML)"];
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX /var/xap=
i/xapi||stunnel] check_reusable: caught exception Unix.Unix_error(31, "writ=
e", ""); assuming not reusable
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX /var/xap=
i/xapi||stunnel] get_reusable_stunnel: Found non-reusable stunnel in the ca=
che. disconnecting from 10.50.128.21:443
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX /var/xap=
i/xapi||stunnel] get_reusable_stunnel: stunnel cache is empty; creating a f=
resh connection to 10.50.128.21:443
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX /var/xap=
i/xapi||xmlrpc_client] stunnel pid: 26297 (cached =3D true) connected to 10=
.50.128.21:443
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX /var/xap=
i/xapi||xmlrpc_client] with_recorded_stunnelpid task_opt=3DNone s_pid=3D262=
97
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX /var/xap=
i/xapi||xmlrpc_client] stunnel pid: 26297 (cached =3D true) returned stunne=
l to cache
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX /var/xap=
i/xapi||mscgen] xapi=3D>xapi [label=3D"(XML)"];
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX /var/xap=
i/xapi||stunnel] check_reusable: caught exception Unix.Unix_error(31, "writ=
e", ""); assuming not reusable
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX /var/xap=
i/xapi||stunnel] get_reusable_stunnel: Found non-reusable stunnel in the ca=
che. disconnecting from 10.50.128.21:443
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX /var/xap=
i/xapi||stunnel] get_reusable_stunnel: stunnel cache is empty; creating a f=
resh connection to 10.50.128.21:443
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX /var/xap=
i/xapi||xmlrpc_client] stunnel pid: 26302 (cached =3D true) connected to 10=
.50.128.21:443
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX /var/xap=
i/xapi||xmlrpc_client] with_recorded_stunnelpid task_opt=3DNone s_pid=3D263=
02
Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX /var/xap=
i/xapi||xmlrpc_client] stunnel pid: 26302 (cached =3D true) returned stunne=
l to cache

The only mention I found in internet didn't give me a clue.
Still, cluster works fine, I'm just worried if there's a bug somewhere deep=
er then I see and it can cause some problems

Regards,
Ivan Derbenev


--_000_660D43EB050DE94AACCFA0BB1489A98278C04FAMSPEX01CL01citri_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:2.0cm 42.5pt 2.0cm 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Ivan,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">These messages are ben=
ign. At some point we&#8217;d like to clean up the logging, as it does tend=
 to be a bit spammy.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Cheers,<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Jon<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;mso-fareast-language:ZH=
-CN">From:</span></b><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-fa=
mily:&quot;Tahoma&quot;,&quot;sans-serif&quot;;mso-fareast-language:ZH-CN">=
 xen-api-bounces@lists.xen.org
 [mailto:xen-api-bounces@lists.xen.org] <b>On Behalf Of </b>dobropalka<br>
<b>Sent:</b> 05 July 2014 3:51 PM<br>
<b>To:</b> xen-api@lists.xen.org<br>
<b>Subject:</b> [Xen-API] connection to pool master is buggy<o:p></o:p></sp=
an></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US">=
Hello, guys!<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">We got a little pool of 4 xense=
rvers. Everything seems to work fine, but all my xensource logs are full of=
 these debug messages:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [ info|cloudstack22|221070 UNIX /var/xapi/xapi|session.login_with_=
password D:9579fb00c72a|xapi] Session.create trackid=3Dd99439bce7424c057acf=
8204cea45f24 pool=3Dfalse uname=3Droot is_local_superuser=3Dtrue
 auth_user_sid=3D parent=3Dtrackid=3D9834f5af41c964e225f24279aefe4e49<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221070 UNIX /var/xapi/xapi|session.login_with_=
password D:9579fb00c72a|mscgen] xapi=3D&gt;xapi [label=3D&quot;(XML)&quot;]=
;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221070 UNIX /var/xapi/xapi|session.login_with_=
password D:9579fb00c72a|stunnel] check_reusable: caught exception Unix.Unix=
_error(31, &quot;write&quot;, &quot;&quot;); assuming not reusable<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221070 UNIX /var/xapi/xapi|session.login_with_=
password D:9579fb00c72a|stunnel] get_reusable_stunnel: Found non-reusable s=
tunnel in the cache. disconnecting from 10.50.128.21:443<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221070 UNIX /var/xapi/xapi|session.login_with_=
password D:9579fb00c72a|stunnel] get_reusable_stunnel: stunnel cache is emp=
ty; creating a fresh connection to 10.50.128.21:443<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [ info|cloudstack22|214513 INET 0.0.0.0:80|sm_exec D:176fe384092b|=
xapi] Session.destroy trackid=3D667f0d1664f406698854c89fe03aca7c<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221070 UNIX /var/xapi/xapi|session.login_with_=
password D:9579fb00c72a|xmlrpc_client] stunnel pid: 26281 (cached =3D true)=
 connected to 10.50.128.21:443<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221070 UNIX /var/xapi/xapi|session.login_with_=
password D:9579fb00c72a|xmlrpc_client] with_recorded_stunnelpid task_opt=3D=
None s_pid=3D26281<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221070 UNIX /var/xapi/xapi|session.login_with_=
password D:9579fb00c72a|xmlrpc_client] stunnel pid: 26281 (cached =3D true)=
 returned stunnel to cache<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221071 UNIX /var/xapi/xapi||mscgen] xapi=3D&gt=
;xapi [label=3D&quot;(XML)&quot;];<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221071 UNIX /var/xapi/xapi||xmlrpc_client] stu=
nnel pid: 26281 (cached =3D true) connected to 10.50.128.21:443<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221071 UNIX /var/xapi/xapi||xmlrpc_client] wit=
h_recorded_stunnelpid task_opt=3DNone s_pid=3D26281<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221071 UNIX /var/xapi/xapi||xmlrpc_client] stu=
nnel pid: 26281 (cached =3D true) returned stunnel to cache<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221072 UNIX /var/xapi/xapi||mscgen] xapi=3D&gt=
;xapi [label=3D&quot;(XML)&quot;];<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221072 UNIX /var/xapi/xapi||stunnel] check_reu=
sable: caught exception Unix.Unix_error(31, &quot;write&quot;, &quot;&quot;=
); assuming not reusable<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221072 UNIX /var/xapi/xapi||stunnel] get_reusa=
ble_stunnel: Found non-reusable stunnel in the cache. disconnecting from 10=
.50.128.21:443<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221072 UNIX /var/xapi/xapi||stunnel] get_reusa=
ble_stunnel: stunnel cache is empty; creating a fresh connection to 10.50.1=
28.21:443<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221072 UNIX /var/xapi/xapi||xmlrpc_client] stu=
nnel pid: 26287 (cached =3D true) connected to 10.50.128.21:443<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221072 UNIX /var/xapi/xapi||xmlrpc_client] wit=
h_recorded_stunnelpid task_opt=3DNone s_pid=3D26287<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221072 UNIX /var/xapi/xapi||xmlrpc_client] stu=
nnel pid: 26287 (cached =3D true) returned stunnel to cache<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221073 UNIX /var/xapi/xapi||mscgen] xapi=3D&gt=
;xapi [label=3D&quot;(XML)&quot;];<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221073 UNIX /var/xapi/xapi||stunnel] check_reu=
sable: caught exception Unix.Unix_error(31, &quot;write&quot;, &quot;&quot;=
); assuming not reusable<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221073 UNIX /var/xapi/xapi||stunnel] get_reusa=
ble_stunnel: Found non-reusable stunnel in the cache. disconnecting from 10=
.50.128.21:443<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221073 UNIX /var/xapi/xapi||stunnel] get_reusa=
ble_stunnel: stunnel cache is empty; creating a fresh connection to 10.50.1=
28.21:443<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|214513 INET 0.0.0.0:80|SR.scan R:eb94a1324f62|=
taskhelper] forwarded task destroyed<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221073 UNIX /var/xapi/xapi||xmlrpc_client] stu=
nnel pid: 26292 (cached =3D true) connected to 10.50.128.21:443<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221073 UNIX /var/xapi/xapi||xmlrpc_client] wit=
h_recorded_stunnelpid task_opt=3DNone s_pid=3D26292<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221073 UNIX /var/xapi/xapi||xmlrpc_client] stu=
nnel pid: 26292 (cached =3D true) returned stunnel to cache<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221074 UNIX /var/xapi/xapi||mscgen] xapi=3D&gt=
;xapi [label=3D&quot;(XML)&quot;];<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221074 UNIX /var/xapi/xapi||stunnel] check_reu=
sable: caught exception Unix.Unix_error(31, &quot;write&quot;, &quot;&quot;=
); assuming not reusable<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221074 UNIX /var/xapi/xapi||stunnel] get_reusa=
ble_stunnel: Found non-reusable stunnel in the cache. disconnecting from 10=
.50.128.21:443<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221074 UNIX /var/xapi/xapi||stunnel] get_reusa=
ble_stunnel: stunnel cache is empty; creating a fresh connection to 10.50.1=
28.21:443<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221074 UNIX /var/xapi/xapi||xmlrpc_client] stu=
nnel pid: 26297 (cached =3D true) connected to 10.50.128.21:443<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221074 UNIX /var/xapi/xapi||xmlrpc_client] wit=
h_recorded_stunnelpid task_opt=3DNone s_pid=3D26297<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221074 UNIX /var/xapi/xapi||xmlrpc_client] stu=
nnel pid: 26297 (cached =3D true) returned stunnel to cache<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221075 UNIX /var/xapi/xapi||mscgen] xapi=3D&gt=
;xapi [label=3D&quot;(XML)&quot;];<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221075 UNIX /var/xapi/xapi||stunnel] check_reu=
sable: caught exception Unix.Unix_error(31, &quot;write&quot;, &quot;&quot;=
); assuming not reusable<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221075 UNIX /var/xapi/xapi||stunnel] get_reusa=
ble_stunnel: Found non-reusable stunnel in the cache. disconnecting from 10=
.50.128.21:443<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221075 UNIX /var/xapi/xapi||stunnel] get_reusa=
ble_stunnel: stunnel cache is empty; creating a fresh connection to 10.50.1=
28.21:443<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221075 UNIX /var/xapi/xapi||xmlrpc_client] stu=
nnel pid: 26302 (cached =3D true) connected to 10.50.128.21:443<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221075 UNIX /var/xapi/xapi||xmlrpc_client] wit=
h_recorded_stunnelpid task_opt=3DNone s_pid=3D26302<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jul&nbsp; 4 08:09:56 cloudstack=
22 xapi: [debug|cloudstack22|221075 UNIX /var/xapi/xapi||xmlrpc_client] stu=
nnel pid: 26302 (cached =3D true) returned stunnel to cache<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">The only mention I found in int=
ernet didn&#8217;t give me a clue.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Still, cluster works fine, I&#8=
217;m just worried if there&#8217;s a bug somewhere deeper then I see and i=
t can cause some problems<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"mso-fareast-language:R=
U">Regards, <o:p>
</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"mso-fareast-language:R=
U">Ivan Derbenev<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"RU"><o:p>&nbsp;</o:p></span></p>
</div>
</body>
</html>

--_000_660D43EB050DE94AACCFA0BB1489A98278C04FAMSPEX01CL01citri_--


--===============5041203007781533768==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--===============5041203007781533768==--


From xen-api-bounces@lists.xen.org Wed Jul 09 08:46:42 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 09 Jul 2014 08:46:42 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X4nWH-0005ld-1D; Wed, 09 Jul 2014 08:46:29 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <thomas.sanders@citrix.com>) id 1X4nWF-0005lY-L1
	for xen-api@lists.xen.org; Wed, 09 Jul 2014 08:46:28 +0000
Received: from [193.109.254.147:12120] by server-5.bemta-14.messagelabs.com id
	1D/37-07680-2610DB35; Wed, 09 Jul 2014 08:46:26 +0000
X-Env-Sender: thomas.sanders@citrix.com
X-Msg-Ref: server-3.tower-27.messagelabs.com!1404895585!16259260!1
X-Originating-IP: [185.25.65.24]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 15340 invoked from network); 9 Jul 2014 08:46:25 -0000
Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24)
	by server-3.tower-27.messagelabs.com with SMTP;
	9 Jul 2014 08:46:25 -0000
X-IronPort-AV: E=Sophos;i="5.01,630,1400025600"; d="scan'208";a="22943590"
Received: from unknown (HELO AMSPEX01CL02.citrite.net) ([10.69.60.9])
	by AMSPIP01.EU.Citrix.com with ESMTP; 09 Jul 2014 08:46:25 +0000
Received: from AMSPEX01CL01.citrite.net ([169.254.6.105]) by
	AMSPEX01CL02.citrite.net ([169.254.7.117]) with mapi id 14.03.0181.006;
	Wed, 9 Jul 2014 10:46:25 +0200
From: Thomas Sanders <thomas.sanders@citrix.com>
To: Jonathan Ludlam <Jonathan.Ludlam@citrix.com>, 'dobropalka'
	<dobropalka@gmail.com>, "xen-api@lists.xen.org" <xen-api@lists.xen.org>
Thread-Topic: [Xen-API] connection to pool master is buggy
Thread-Index: Ac+YYC92YgqTlRQGT7C9IFkmVI8m3ABcOPUAAGAYlFA=
Date: Wed, 9 Jul 2014 08:46:24 +0000
Message-ID: <06B80725944D5847804519C301FB87272AE4E8@AMSPEX01CL01.citrite.net>
References: <01e901cf9860$935928d0$ba0b7a70$@gmail.com>
	<660D43EB050DE94AACCFA0BB1489A98278C04F@AMSPEX01CL01.citrite.net>
In-Reply-To: <660D43EB050DE94AACCFA0BB1489A98278C04F@AMSPEX01CL01.citrite.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.69.129.153]
MIME-Version: 1.0
X-DLP: AMS1
Subject: Re: [Xen-API] connection to pool master is buggy
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

These particular messages no longer appear in current development versions =
of the software: we made stunnels reusable, and reduced the chattiness of t=
he relevant code somewhat. (Off the top of my head I don't remember for cer=
tain if/when the changes got into an official release... maybe XenServer 6.=
2 SP1?)

Jon's point about logging is still true more generally, though.

From: xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org] =
On Behalf Of Jonathan Ludlam
Sent: 07 July 2014 11:50 AM
To: 'dobropalka'; xen-api@lists.xen.org
Subject: Re: [Xen-API] connection to pool master is buggy

Hi Ivan,

These messages are benign. At some point we'd like to clean up the logging,=
 as it does tend to be a bit spammy.

Cheers,

Jon


From: xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org] =
On Behalf Of dobropalka
Sent: 05 July 2014 3:51 PM
To: xen-api@lists.xen.org
Subject: [Xen-API] connection to pool master is buggy

Hello, guys!
We got a little pool of 4 xenservers. Everything seems to work fine, but al=
l my xensource logs are full of these debug messages:

Jul=A0 4 08:09:56 cloudstack22 xapi: [ info|cloudstack22|221070 UNIX /var/x=
api/xapi|session.login_with_password D:9579fb00c72a|xapi] Session.create tr=
ackid=3Dd99439bce7424c057acf8204cea45f24 pool=3Dfalse uname=3Droot is_local=
_superuser=3Dtrue auth_user_sid=3D parent=3Dtrackid=3D9834f5af41c964e225f24=
279aefe4e49
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX /var/x=
api/xapi|session.login_with_password D:9579fb00c72a|mscgen] xapi=3D>xapi [l=
abel=3D"(XML)"];
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX /var/x=
api/xapi|session.login_with_password D:9579fb00c72a|stunnel] check_reusable=
: caught exception Unix.Unix_error(31, "write", ""); assuming not reusable
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX /var/x=
api/xapi|session.login_with_password D:9579fb00c72a|stunnel] get_reusable_s=
tunnel: Found non-reusable stunnel in the cache. disconnecting from 10.50.1=
28.21:443
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX /var/x=
api/xapi|session.login_with_password D:9579fb00c72a|stunnel] get_reusable_s=
tunnel: stunnel cache is empty; creating a fresh connection to 10.50.128.21=
:443
Jul=A0 4 08:09:56 cloudstack22 xapi: [ info|cloudstack22|214513 INET 0.0.0.=
0:80|sm_exec D:176fe384092b|xapi] Session.destroy trackid=3D667f0d1664f4066=
98854c89fe03aca7c
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX /var/x=
api/xapi|session.login_with_password D:9579fb00c72a|xmlrpc_client] stunnel =
pid: 26281 (cached =3D true) connected to 10.50.128.21:443
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX /var/x=
api/xapi|session.login_with_password D:9579fb00c72a|xmlrpc_client] with_rec=
orded_stunnelpid task_opt=3DNone s_pid=3D26281
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX /var/x=
api/xapi|session.login_with_password D:9579fb00c72a|xmlrpc_client] stunnel =
pid: 26281 (cached =3D true) returned stunnel to cache
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221071 UNIX /var/x=
api/xapi||mscgen] xapi=3D>xapi [label=3D"(XML)"];
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221071 UNIX /var/x=
api/xapi||xmlrpc_client] stunnel pid: 26281 (cached =3D true) connected to =
10.50.128.21:443
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221071 UNIX /var/x=
api/xapi||xmlrpc_client] with_recorded_stunnelpid task_opt=3DNone s_pid=3D2=
6281
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221071 UNIX /var/x=
api/xapi||xmlrpc_client] stunnel pid: 26281 (cached =3D true) returned stun=
nel to cache
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX /var/x=
api/xapi||mscgen] xapi=3D>xapi [label=3D"(XML)"];
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX /var/x=
api/xapi||stunnel] check_reusable: caught exception Unix.Unix_error(31, "wr=
ite", ""); assuming not reusable
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX /var/x=
api/xapi||stunnel] get_reusable_stunnel: Found non-reusable stunnel in the =
cache. disconnecting from 10.50.128.21:443
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX /var/x=
api/xapi||stunnel] get_reusable_stunnel: stunnel cache is empty; creating a=
 fresh connection to 10.50.128.21:443
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX /var/x=
api/xapi||xmlrpc_client] stunnel pid: 26287 (cached =3D true) connected to =
10.50.128.21:443
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX /var/x=
api/xapi||xmlrpc_client] with_recorded_stunnelpid task_opt=3DNone s_pid=3D2=
6287
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX /var/x=
api/xapi||xmlrpc_client] stunnel pid: 26287 (cached =3D true) returned stun=
nel to cache
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX /var/x=
api/xapi||mscgen] xapi=3D>xapi [label=3D"(XML)"];
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX /var/x=
api/xapi||stunnel] check_reusable: caught exception Unix.Unix_error(31, "wr=
ite", ""); assuming not reusable
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX /var/x=
api/xapi||stunnel] get_reusable_stunnel: Found non-reusable stunnel in the =
cache. disconnecting from 10.50.128.21:443
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX /var/x=
api/xapi||stunnel] get_reusable_stunnel: stunnel cache is empty; creating a=
 fresh connection to 10.50.128.21:443
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|214513 INET 0.0.0.=
0:80|SR.scan R:eb94a1324f62|taskhelper] forwarded task destroyed
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX /var/x=
api/xapi||xmlrpc_client] stunnel pid: 26292 (cached =3D true) connected to =
10.50.128.21:443
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX /var/x=
api/xapi||xmlrpc_client] with_recorded_stunnelpid task_opt=3DNone s_pid=3D2=
6292
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX /var/x=
api/xapi||xmlrpc_client] stunnel pid: 26292 (cached =3D true) returned stun=
nel to cache
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX /var/x=
api/xapi||mscgen] xapi=3D>xapi [label=3D"(XML)"];
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX /var/x=
api/xapi||stunnel] check_reusable: caught exception Unix.Unix_error(31, "wr=
ite", ""); assuming not reusable
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX /var/x=
api/xapi||stunnel] get_reusable_stunnel: Found non-reusable stunnel in the =
cache. disconnecting from 10.50.128.21:443
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX /var/x=
api/xapi||stunnel] get_reusable_stunnel: stunnel cache is empty; creating a=
 fresh connection to 10.50.128.21:443
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX /var/x=
api/xapi||xmlrpc_client] stunnel pid: 26297 (cached =3D true) connected to =
10.50.128.21:443
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX /var/x=
api/xapi||xmlrpc_client] with_recorded_stunnelpid task_opt=3DNone s_pid=3D2=
6297
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX /var/x=
api/xapi||xmlrpc_client] stunnel pid: 26297 (cached =3D true) returned stun=
nel to cache
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX /var/x=
api/xapi||mscgen] xapi=3D>xapi [label=3D"(XML)"];
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX /var/x=
api/xapi||stunnel] check_reusable: caught exception Unix.Unix_error(31, "wr=
ite", ""); assuming not reusable
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX /var/x=
api/xapi||stunnel] get_reusable_stunnel: Found non-reusable stunnel in the =
cache. disconnecting from 10.50.128.21:443
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX /var/x=
api/xapi||stunnel] get_reusable_stunnel: stunnel cache is empty; creating a=
 fresh connection to 10.50.128.21:443
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX /var/x=
api/xapi||xmlrpc_client] stunnel pid: 26302 (cached =3D true) connected to =
10.50.128.21:443
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX /var/x=
api/xapi||xmlrpc_client] with_recorded_stunnelpid task_opt=3DNone s_pid=3D2=
6302
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX /var/x=
api/xapi||xmlrpc_client] stunnel pid: 26302 (cached =3D true) returned stun=
nel to cache

The only mention I found in internet didn't give me a clue.
Still, cluster works fine, I'm just worried if there's a bug somewhere deep=
er then I see and it can cause some problems

Regards, =

Ivan Derbenev


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

From xen-api-bounces@lists.xen.org Wed Jul 09 08:46:42 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 09 Jul 2014 08:46:42 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X4nWH-0005ld-1D; Wed, 09 Jul 2014 08:46:29 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <thomas.sanders@citrix.com>) id 1X4nWF-0005lY-L1
	for xen-api@lists.xen.org; Wed, 09 Jul 2014 08:46:28 +0000
Received: from [193.109.254.147:12120] by server-5.bemta-14.messagelabs.com id
	1D/37-07680-2610DB35; Wed, 09 Jul 2014 08:46:26 +0000
X-Env-Sender: thomas.sanders@citrix.com
X-Msg-Ref: server-3.tower-27.messagelabs.com!1404895585!16259260!1
X-Originating-IP: [185.25.65.24]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 15340 invoked from network); 9 Jul 2014 08:46:25 -0000
Received: from smtp.eu.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24)
	by server-3.tower-27.messagelabs.com with SMTP;
	9 Jul 2014 08:46:25 -0000
X-IronPort-AV: E=Sophos;i="5.01,630,1400025600"; d="scan'208";a="22943590"
Received: from unknown (HELO AMSPEX01CL02.citrite.net) ([10.69.60.9])
	by AMSPIP01.EU.Citrix.com with ESMTP; 09 Jul 2014 08:46:25 +0000
Received: from AMSPEX01CL01.citrite.net ([169.254.6.105]) by
	AMSPEX01CL02.citrite.net ([169.254.7.117]) with mapi id 14.03.0181.006;
	Wed, 9 Jul 2014 10:46:25 +0200
From: Thomas Sanders <thomas.sanders@citrix.com>
To: Jonathan Ludlam <Jonathan.Ludlam@citrix.com>, 'dobropalka'
	<dobropalka@gmail.com>, "xen-api@lists.xen.org" <xen-api@lists.xen.org>
Thread-Topic: [Xen-API] connection to pool master is buggy
Thread-Index: Ac+YYC92YgqTlRQGT7C9IFkmVI8m3ABcOPUAAGAYlFA=
Date: Wed, 9 Jul 2014 08:46:24 +0000
Message-ID: <06B80725944D5847804519C301FB87272AE4E8@AMSPEX01CL01.citrite.net>
References: <01e901cf9860$935928d0$ba0b7a70$@gmail.com>
	<660D43EB050DE94AACCFA0BB1489A98278C04F@AMSPEX01CL01.citrite.net>
In-Reply-To: <660D43EB050DE94AACCFA0BB1489A98278C04F@AMSPEX01CL01.citrite.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.69.129.153]
MIME-Version: 1.0
X-DLP: AMS1
Subject: Re: [Xen-API] connection to pool master is buggy
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

These particular messages no longer appear in current development versions =
of the software: we made stunnels reusable, and reduced the chattiness of t=
he relevant code somewhat. (Off the top of my head I don't remember for cer=
tain if/when the changes got into an official release... maybe XenServer 6.=
2 SP1?)

Jon's point about logging is still true more generally, though.

From: xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org] =
On Behalf Of Jonathan Ludlam
Sent: 07 July 2014 11:50 AM
To: 'dobropalka'; xen-api@lists.xen.org
Subject: Re: [Xen-API] connection to pool master is buggy

Hi Ivan,

These messages are benign. At some point we'd like to clean up the logging,=
 as it does tend to be a bit spammy.

Cheers,

Jon


From: xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org] =
On Behalf Of dobropalka
Sent: 05 July 2014 3:51 PM
To: xen-api@lists.xen.org
Subject: [Xen-API] connection to pool master is buggy

Hello, guys!
We got a little pool of 4 xenservers. Everything seems to work fine, but al=
l my xensource logs are full of these debug messages:

Jul=A0 4 08:09:56 cloudstack22 xapi: [ info|cloudstack22|221070 UNIX /var/x=
api/xapi|session.login_with_password D:9579fb00c72a|xapi] Session.create tr=
ackid=3Dd99439bce7424c057acf8204cea45f24 pool=3Dfalse uname=3Droot is_local=
_superuser=3Dtrue auth_user_sid=3D parent=3Dtrackid=3D9834f5af41c964e225f24=
279aefe4e49
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX /var/x=
api/xapi|session.login_with_password D:9579fb00c72a|mscgen] xapi=3D>xapi [l=
abel=3D"(XML)"];
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX /var/x=
api/xapi|session.login_with_password D:9579fb00c72a|stunnel] check_reusable=
: caught exception Unix.Unix_error(31, "write", ""); assuming not reusable
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX /var/x=
api/xapi|session.login_with_password D:9579fb00c72a|stunnel] get_reusable_s=
tunnel: Found non-reusable stunnel in the cache. disconnecting from 10.50.1=
28.21:443
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX /var/x=
api/xapi|session.login_with_password D:9579fb00c72a|stunnel] get_reusable_s=
tunnel: stunnel cache is empty; creating a fresh connection to 10.50.128.21=
:443
Jul=A0 4 08:09:56 cloudstack22 xapi: [ info|cloudstack22|214513 INET 0.0.0.=
0:80|sm_exec D:176fe384092b|xapi] Session.destroy trackid=3D667f0d1664f4066=
98854c89fe03aca7c
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX /var/x=
api/xapi|session.login_with_password D:9579fb00c72a|xmlrpc_client] stunnel =
pid: 26281 (cached =3D true) connected to 10.50.128.21:443
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX /var/x=
api/xapi|session.login_with_password D:9579fb00c72a|xmlrpc_client] with_rec=
orded_stunnelpid task_opt=3DNone s_pid=3D26281
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX /var/x=
api/xapi|session.login_with_password D:9579fb00c72a|xmlrpc_client] stunnel =
pid: 26281 (cached =3D true) returned stunnel to cache
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221071 UNIX /var/x=
api/xapi||mscgen] xapi=3D>xapi [label=3D"(XML)"];
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221071 UNIX /var/x=
api/xapi||xmlrpc_client] stunnel pid: 26281 (cached =3D true) connected to =
10.50.128.21:443
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221071 UNIX /var/x=
api/xapi||xmlrpc_client] with_recorded_stunnelpid task_opt=3DNone s_pid=3D2=
6281
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221071 UNIX /var/x=
api/xapi||xmlrpc_client] stunnel pid: 26281 (cached =3D true) returned stun=
nel to cache
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX /var/x=
api/xapi||mscgen] xapi=3D>xapi [label=3D"(XML)"];
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX /var/x=
api/xapi||stunnel] check_reusable: caught exception Unix.Unix_error(31, "wr=
ite", ""); assuming not reusable
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX /var/x=
api/xapi||stunnel] get_reusable_stunnel: Found non-reusable stunnel in the =
cache. disconnecting from 10.50.128.21:443
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX /var/x=
api/xapi||stunnel] get_reusable_stunnel: stunnel cache is empty; creating a=
 fresh connection to 10.50.128.21:443
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX /var/x=
api/xapi||xmlrpc_client] stunnel pid: 26287 (cached =3D true) connected to =
10.50.128.21:443
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX /var/x=
api/xapi||xmlrpc_client] with_recorded_stunnelpid task_opt=3DNone s_pid=3D2=
6287
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX /var/x=
api/xapi||xmlrpc_client] stunnel pid: 26287 (cached =3D true) returned stun=
nel to cache
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX /var/x=
api/xapi||mscgen] xapi=3D>xapi [label=3D"(XML)"];
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX /var/x=
api/xapi||stunnel] check_reusable: caught exception Unix.Unix_error(31, "wr=
ite", ""); assuming not reusable
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX /var/x=
api/xapi||stunnel] get_reusable_stunnel: Found non-reusable stunnel in the =
cache. disconnecting from 10.50.128.21:443
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX /var/x=
api/xapi||stunnel] get_reusable_stunnel: stunnel cache is empty; creating a=
 fresh connection to 10.50.128.21:443
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|214513 INET 0.0.0.=
0:80|SR.scan R:eb94a1324f62|taskhelper] forwarded task destroyed
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX /var/x=
api/xapi||xmlrpc_client] stunnel pid: 26292 (cached =3D true) connected to =
10.50.128.21:443
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX /var/x=
api/xapi||xmlrpc_client] with_recorded_stunnelpid task_opt=3DNone s_pid=3D2=
6292
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX /var/x=
api/xapi||xmlrpc_client] stunnel pid: 26292 (cached =3D true) returned stun=
nel to cache
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX /var/x=
api/xapi||mscgen] xapi=3D>xapi [label=3D"(XML)"];
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX /var/x=
api/xapi||stunnel] check_reusable: caught exception Unix.Unix_error(31, "wr=
ite", ""); assuming not reusable
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX /var/x=
api/xapi||stunnel] get_reusable_stunnel: Found non-reusable stunnel in the =
cache. disconnecting from 10.50.128.21:443
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX /var/x=
api/xapi||stunnel] get_reusable_stunnel: stunnel cache is empty; creating a=
 fresh connection to 10.50.128.21:443
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX /var/x=
api/xapi||xmlrpc_client] stunnel pid: 26297 (cached =3D true) connected to =
10.50.128.21:443
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX /var/x=
api/xapi||xmlrpc_client] with_recorded_stunnelpid task_opt=3DNone s_pid=3D2=
6297
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX /var/x=
api/xapi||xmlrpc_client] stunnel pid: 26297 (cached =3D true) returned stun=
nel to cache
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX /var/x=
api/xapi||mscgen] xapi=3D>xapi [label=3D"(XML)"];
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX /var/x=
api/xapi||stunnel] check_reusable: caught exception Unix.Unix_error(31, "wr=
ite", ""); assuming not reusable
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX /var/x=
api/xapi||stunnel] get_reusable_stunnel: Found non-reusable stunnel in the =
cache. disconnecting from 10.50.128.21:443
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX /var/x=
api/xapi||stunnel] get_reusable_stunnel: stunnel cache is empty; creating a=
 fresh connection to 10.50.128.21:443
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX /var/x=
api/xapi||xmlrpc_client] stunnel pid: 26302 (cached =3D true) connected to =
10.50.128.21:443
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX /var/x=
api/xapi||xmlrpc_client] with_recorded_stunnelpid task_opt=3DNone s_pid=3D2=
6302
Jul=A0 4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX /var/x=
api/xapi||xmlrpc_client] stunnel pid: 26302 (cached =3D true) returned stun=
nel to cache

The only mention I found in internet didn't give me a clue.
Still, cluster works fine, I'm just worried if there's a bug somewhere deep=
er then I see and it can cause some problems

Regards, =

Ivan Derbenev


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

From xen-api-bounces@lists.xen.org Wed Jul 09 10:35:20 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 09 Jul 2014 10:35:20 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X4pDU-00030r-PU; Wed, 09 Jul 2014 10:35:12 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <lars.kurth.xen@gmail.com>)
	id 1X4pDS-00030d-UH; Wed, 09 Jul 2014 10:35:11 +0000
Received: from [85.158.143.35:57259] by server-2.bemta-4.messagelabs.com id
	01/80-18579-EDA1DB35; Wed, 09 Jul 2014 10:35:10 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-6.tower-21.messagelabs.com!1404902109!16718348!1
X-Originating-IP: [209.85.212.171]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 27768 invoked from network); 9 Jul 2014 10:35:09 -0000
Received: from mail-wi0-f171.google.com (HELO mail-wi0-f171.google.com)
	(209.85.212.171)
	by server-6.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	9 Jul 2014 10:35:09 -0000
Received: by mail-wi0-f171.google.com with SMTP id f8so1993315wiw.16
	for <multiple recipients>; Wed, 09 Jul 2014 03:35:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=sender:message-id:date:from:reply-to:user-agent:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	bh=cqhJstBFcMkeoWtdA1LrmHLl+/dVUqK75f1Ddy+Er7k=;
	b=JMOiyD6tgYeQAGTXLL/6xRGglAXJhPtcFrB5g9Hz3M7evnopesa+fYP7u1BurGa6DE
	erahD4qBtVPzQdy/7ziJLYluc6hWpAvR+n3Ss7TEU4mnMewk2nuLYw0xyv9snARqLxBz
	Tt/DkMo1xobikL3fSO4evAmLwbIGMiFggsgiQlh/QOxBsmUBuYgaKKsY6zOTY5D6rc6r
	PlTKO8QQhUjfH/LHNYgYU3iB8KHzh29y5XQwVhVJp16F7ByDvnvVTvN4NN32W9KOqY9Q
	10/4WgtbV9+0DzxjISvoH/9a0qNPgkrwmfjf27PjtwPK6IxIaocOorLG+pGCffuqwucZ
	NWZA==
X-Received: by 10.194.110.161 with SMTP id ib1mr2346731wjb.129.1404902109057; 
	Wed, 09 Jul 2014 03:35:09 -0700 (PDT)
Received: from [172.16.25.10] (97e5a05a.skybroadband.com. [151.229.160.90])
	by mx.google.com with ESMTPSA id o9sm17799978wib.22.2014.07.09.03.35.07
	for <multiple recipients>
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Wed, 09 Jul 2014 03:35:08 -0700 (PDT)
Message-ID: <53BD1AD8.9040802@xen.org>
Date: Wed, 09 Jul 2014 11:35:04 +0100
From: Lars Kurth <lars.kurth@xen.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Anil Madhavapeddy <anil@recoil.org>
References: <53B28517.9020807@xen.org>
	<75D6B875-6AF4-4176-B530-447D47B2A18A@recoil.org>
In-Reply-To: <75D6B875-6AF4-4176-B530-447D47B2A18A@recoil.org>
Cc: "xen-api@lists.xen.org" <xen-api@lists.xen.org>,
	Artem Mygaiev <artem.mygaiev@globallogic.com>,
	Alex Agizim <alex.agizim@globallogic.com>,
	"mirageos-devel@lists.xenproject.org"
	<mirageos-devel@lists.xenproject.org>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [Xen-API] [Xen-devel] [For Community Review] Embedded and
 Automotive PV Drivers Sub-Project Proposal (deadline July 11th)
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

Anil,
thank you for the feedback. I will need to let Artem and Alex answer 
your questions. I merely copied and pasted these from a document
Regards
Lars

On 01/07/2014 14:56, Anil Madhavapeddy wrote:
> On 1 Jul 2014, at 12:53, Lars Kurth <lars.kurth@xen.org> wrote:
>> Hi all,
>>
>> the "Embedded and Automotive PV Drivers Sub-Project Proposal" (see http://wiki.xenproject.org/wiki/Embedded_and_Automotive_PV_Drivers_Project_Proposal) is now open for community review. Please provide feedback by replying to this thread or using the Comment feature (see http://wiki.xenproject.org/wiki/Template:Comment) using "{{comment|~~~~}} My comment" on the relevant section of the wiki page.
> Looks great! A few comments:
>
> - "pv_fb driver provide audio driver back- " => audio should be "framebuffer"
>
> - Several of the drivers overlap with existing front/back drivers (for example, the pv_usb one).  Is there a plan to merge these, or at least document the differences between QNX and the Linux/BSD versions of the relevant ring protocols?
>
> - Not sure why the pv_gpu drivers has a "lnx-alsa-be/" entry in the drivers. Might be a c&p error.
>
> cheers,
> ANil
>
>> I extended the deadline by a few days, to account for the 4th of July holidays/vacation in the USA
>>
>> Best Regards
>> Lars
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xen.org
>> http://lists.xen.org/xen-devel
>>


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

From xen-api-bounces@lists.xen.org Wed Jul 09 10:35:20 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 09 Jul 2014 10:35:20 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X4pDU-00030r-PU; Wed, 09 Jul 2014 10:35:12 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <lars.kurth.xen@gmail.com>)
	id 1X4pDS-00030d-UH; Wed, 09 Jul 2014 10:35:11 +0000
Received: from [85.158.143.35:57259] by server-2.bemta-4.messagelabs.com id
	01/80-18579-EDA1DB35; Wed, 09 Jul 2014 10:35:10 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-6.tower-21.messagelabs.com!1404902109!16718348!1
X-Originating-IP: [209.85.212.171]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 27768 invoked from network); 9 Jul 2014 10:35:09 -0000
Received: from mail-wi0-f171.google.com (HELO mail-wi0-f171.google.com)
	(209.85.212.171)
	by server-6.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	9 Jul 2014 10:35:09 -0000
Received: by mail-wi0-f171.google.com with SMTP id f8so1993315wiw.16
	for <multiple recipients>; Wed, 09 Jul 2014 03:35:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=sender:message-id:date:from:reply-to:user-agent:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	bh=cqhJstBFcMkeoWtdA1LrmHLl+/dVUqK75f1Ddy+Er7k=;
	b=JMOiyD6tgYeQAGTXLL/6xRGglAXJhPtcFrB5g9Hz3M7evnopesa+fYP7u1BurGa6DE
	erahD4qBtVPzQdy/7ziJLYluc6hWpAvR+n3Ss7TEU4mnMewk2nuLYw0xyv9snARqLxBz
	Tt/DkMo1xobikL3fSO4evAmLwbIGMiFggsgiQlh/QOxBsmUBuYgaKKsY6zOTY5D6rc6r
	PlTKO8QQhUjfH/LHNYgYU3iB8KHzh29y5XQwVhVJp16F7ByDvnvVTvN4NN32W9KOqY9Q
	10/4WgtbV9+0DzxjISvoH/9a0qNPgkrwmfjf27PjtwPK6IxIaocOorLG+pGCffuqwucZ
	NWZA==
X-Received: by 10.194.110.161 with SMTP id ib1mr2346731wjb.129.1404902109057; 
	Wed, 09 Jul 2014 03:35:09 -0700 (PDT)
Received: from [172.16.25.10] (97e5a05a.skybroadband.com. [151.229.160.90])
	by mx.google.com with ESMTPSA id o9sm17799978wib.22.2014.07.09.03.35.07
	for <multiple recipients>
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Wed, 09 Jul 2014 03:35:08 -0700 (PDT)
Message-ID: <53BD1AD8.9040802@xen.org>
Date: Wed, 09 Jul 2014 11:35:04 +0100
From: Lars Kurth <lars.kurth@xen.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Anil Madhavapeddy <anil@recoil.org>
References: <53B28517.9020807@xen.org>
	<75D6B875-6AF4-4176-B530-447D47B2A18A@recoil.org>
In-Reply-To: <75D6B875-6AF4-4176-B530-447D47B2A18A@recoil.org>
Cc: "xen-api@lists.xen.org" <xen-api@lists.xen.org>,
	Artem Mygaiev <artem.mygaiev@globallogic.com>,
	Alex Agizim <alex.agizim@globallogic.com>,
	"mirageos-devel@lists.xenproject.org"
	<mirageos-devel@lists.xenproject.org>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [Xen-API] [Xen-devel] [For Community Review] Embedded and
 Automotive PV Drivers Sub-Project Proposal (deadline July 11th)
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

Anil,
thank you for the feedback. I will need to let Artem and Alex answer 
your questions. I merely copied and pasted these from a document
Regards
Lars

On 01/07/2014 14:56, Anil Madhavapeddy wrote:
> On 1 Jul 2014, at 12:53, Lars Kurth <lars.kurth@xen.org> wrote:
>> Hi all,
>>
>> the "Embedded and Automotive PV Drivers Sub-Project Proposal" (see http://wiki.xenproject.org/wiki/Embedded_and_Automotive_PV_Drivers_Project_Proposal) is now open for community review. Please provide feedback by replying to this thread or using the Comment feature (see http://wiki.xenproject.org/wiki/Template:Comment) using "{{comment|~~~~}} My comment" on the relevant section of the wiki page.
> Looks great! A few comments:
>
> - "pv_fb driver provide audio driver back- " => audio should be "framebuffer"
>
> - Several of the drivers overlap with existing front/back drivers (for example, the pv_usb one).  Is there a plan to merge these, or at least document the differences between QNX and the Linux/BSD versions of the relevant ring protocols?
>
> - Not sure why the pv_gpu drivers has a "lnx-alsa-be/" entry in the drivers. Might be a c&p error.
>
> cheers,
> ANil
>
>> I extended the deadline by a few days, to account for the 4th of July holidays/vacation in the USA
>>
>> Best Regards
>> Lars
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xen.org
>> http://lists.xen.org/xen-devel
>>


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

From xen-api-bounces@lists.xen.org Wed Jul 09 10:43:00 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 09 Jul 2014 10:43:00 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X4pKz-0003O9-8c; Wed, 09 Jul 2014 10:42:57 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <Ian.Campbell@citrix.com>)
	id 1X4pKy-0003NZ-L5; Wed, 09 Jul 2014 10:42:56 +0000
Received: from [85.158.137.68:42521] by server-16.bemta-3.messagelabs.com id
	D1/9A-28986-FAC1DB35; Wed, 09 Jul 2014 10:42:55 +0000
X-Env-Sender: Ian.Campbell@citrix.com
X-Msg-Ref: server-13.tower-31.messagelabs.com!1404902572!14905832!1
X-Originating-IP: [66.165.176.63]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 12301 invoked from network); 9 Jul 2014 10:42:54 -0000
Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63)
	by server-13.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	9 Jul 2014 10:42:54 -0000
X-IronPort-AV: E=Sophos;i="5.01,630,1400025600"; d="scan'208";a="151184332"
Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net)
	([10.9.154.239])
	by FTLPIPO02.CITRIX.COM with ESMTP; 09 Jul 2014 10:42:52 +0000
Received: from kazak.uk.xensource.com (10.80.2.80) by FTLPEX01CL01.citrite.net
	(10.13.107.78) with Microsoft SMTP Server id 14.3.181.6;
	Wed, 9 Jul 2014 06:42:52 -0400
Message-ID: <1404902570.16789.3.camel@kazak.uk.xensource.com>
From: Ian Campbell <Ian.Campbell@citrix.com>
To: <lars.kurth@xen.org>
Date: Wed, 9 Jul 2014 11:42:50 +0100
In-Reply-To: <53B28517.9020807@xen.org>
References: <53B28517.9020807@xen.org>
Organization: Citrix Systems, Inc.
X-Mailer: Evolution 3.12.2-1 
MIME-Version: 1.0
X-Originating-IP: [10.80.2.80]
X-DLP: MIA2
Cc: "xen-api@lists.xen.org" <xen-api@lists.xen.org>,
	Artem Mygaiev <artem.mygaiev@globallogic.com>,
	Alex Agizim <alex.agizim@globallogic.com>,
	"mirageos-devel@lists.xenproject.org"
	<mirageos-devel@lists.xenproject.org>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [Xen-API] [Xen-devel] [For Community Review] Embedded and
 Automotive PV Drivers Sub-Project Proposal (deadline July 11th)
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org


On Tue, 2014-07-01 at 10:53 +0100, Lars Kurth wrote:
> Hi all,
> 
> the "Embedded and Automotive PV Drivers Sub-Project Proposal" (see 
> http://wiki.xenproject.org/wiki/Embedded_and_Automotive_PV_Drivers_Project_Proposal) 
> is now open for community review. Please provide feedback by replying to 
> this thread

I think you should avoid the word "staging" entirely in this document.

A staging tree in Xen terminology is something completely different to
how you use it here: it's the tree where the committers push things which
serves as the input to our automated test. How about "development" tree?
Or just avoid them altogether by using the individual developer's own
trees and the lists.

WRT xen-devel being busy and the subproject's own lists, it might be
wise to have upstream exposure from early on, which would imply ccing
xen-devel/lkml etc in addition to the subproject list. Otherwise you get
into the issue where the subproject has accepted something (perhaps into
a "staging" tree) but when it gets sent upstream it requires major
reworking (and the developer is long gone, etc etc). Whether that needs
to be part of the charter though I don't know.

More minor thoughts:

"it is likely and desirable that the project may be useful for other"
        
        I'm not sure if this sentence has the end missing or if you
        intended other to be "others".

"Part of the reason for this is that some of the hardware to test is
also not yet available to open source communities."

        This is not (and should not be) a barrier to sending patches to
        the right place. We have reviewed and accepted plenty of patches
        for which we have no access to the h/w.

"To build these drivers, the QNX GNU libc variant is used (licensed
under GPL)."

        Not LGPL? QNX using GPL for it's libc seems like an odd choice
        for them, since it requires anything linking against it to be
        GPL compatible. I suspect this a typo.
        
"Must have OSI approved licenses that are required to link with and
usage the drivers within the native OS."

        I can't parse this sentence. I think s/usage/use might be what
        was meant but I'm not sure.

"upstreamns"

        Typo

WRT graduation -- can we include a requirement that any "staging" trees
have been retired (e.g. merged upstream or otherwise obsolete).

Ian.


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

From xen-api-bounces@lists.xen.org Wed Jul 09 10:43:00 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 09 Jul 2014 10:43:00 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X4pKz-0003O9-8c; Wed, 09 Jul 2014 10:42:57 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <Ian.Campbell@citrix.com>)
	id 1X4pKy-0003NZ-L5; Wed, 09 Jul 2014 10:42:56 +0000
Received: from [85.158.137.68:42521] by server-16.bemta-3.messagelabs.com id
	D1/9A-28986-FAC1DB35; Wed, 09 Jul 2014 10:42:55 +0000
X-Env-Sender: Ian.Campbell@citrix.com
X-Msg-Ref: server-13.tower-31.messagelabs.com!1404902572!14905832!1
X-Originating-IP: [66.165.176.63]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 12301 invoked from network); 9 Jul 2014 10:42:54 -0000
Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63)
	by server-13.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	9 Jul 2014 10:42:54 -0000
X-IronPort-AV: E=Sophos;i="5.01,630,1400025600"; d="scan'208";a="151184332"
Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net)
	([10.9.154.239])
	by FTLPIPO02.CITRIX.COM with ESMTP; 09 Jul 2014 10:42:52 +0000
Received: from kazak.uk.xensource.com (10.80.2.80) by FTLPEX01CL01.citrite.net
	(10.13.107.78) with Microsoft SMTP Server id 14.3.181.6;
	Wed, 9 Jul 2014 06:42:52 -0400
Message-ID: <1404902570.16789.3.camel@kazak.uk.xensource.com>
From: Ian Campbell <Ian.Campbell@citrix.com>
To: <lars.kurth@xen.org>
Date: Wed, 9 Jul 2014 11:42:50 +0100
In-Reply-To: <53B28517.9020807@xen.org>
References: <53B28517.9020807@xen.org>
Organization: Citrix Systems, Inc.
X-Mailer: Evolution 3.12.2-1 
MIME-Version: 1.0
X-Originating-IP: [10.80.2.80]
X-DLP: MIA2
Cc: "xen-api@lists.xen.org" <xen-api@lists.xen.org>,
	Artem Mygaiev <artem.mygaiev@globallogic.com>,
	Alex Agizim <alex.agizim@globallogic.com>,
	"mirageos-devel@lists.xenproject.org"
	<mirageos-devel@lists.xenproject.org>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [Xen-API] [Xen-devel] [For Community Review] Embedded and
 Automotive PV Drivers Sub-Project Proposal (deadline July 11th)
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org


On Tue, 2014-07-01 at 10:53 +0100, Lars Kurth wrote:
> Hi all,
> 
> the "Embedded and Automotive PV Drivers Sub-Project Proposal" (see 
> http://wiki.xenproject.org/wiki/Embedded_and_Automotive_PV_Drivers_Project_Proposal) 
> is now open for community review. Please provide feedback by replying to 
> this thread

I think you should avoid the word "staging" entirely in this document.

A staging tree in Xen terminology is something completely different to
how you use it here: it's the tree where the committers push things which
serves as the input to our automated test. How about "development" tree?
Or just avoid them altogether by using the individual developer's own
trees and the lists.

WRT xen-devel being busy and the subproject's own lists, it might be
wise to have upstream exposure from early on, which would imply ccing
xen-devel/lkml etc in addition to the subproject list. Otherwise you get
into the issue where the subproject has accepted something (perhaps into
a "staging" tree) but when it gets sent upstream it requires major
reworking (and the developer is long gone, etc etc). Whether that needs
to be part of the charter though I don't know.

More minor thoughts:

"it is likely and desirable that the project may be useful for other"
        
        I'm not sure if this sentence has the end missing or if you
        intended other to be "others".

"Part of the reason for this is that some of the hardware to test is
also not yet available to open source communities."

        This is not (and should not be) a barrier to sending patches to
        the right place. We have reviewed and accepted plenty of patches
        for which we have no access to the h/w.

"To build these drivers, the QNX GNU libc variant is used (licensed
under GPL)."

        Not LGPL? QNX using GPL for it's libc seems like an odd choice
        for them, since it requires anything linking against it to be
        GPL compatible. I suspect this a typo.
        
"Must have OSI approved licenses that are required to link with and
usage the drivers within the native OS."

        I can't parse this sentence. I think s/usage/use might be what
        was meant but I'm not sure.

"upstreamns"

        Typo

WRT graduation -- can we include a requirement that any "staging" trees
have been retired (e.g. merged upstream or otherwise obsolete).

Ian.


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

From xen-api-bounces@lists.xen.org Wed Jul 09 11:28:32 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 09 Jul 2014 11:28:32 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X4q33-0004Ye-0I; Wed, 09 Jul 2014 11:28:29 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <lars.kurth.xen@gmail.com>)
	id 1X4q31-0004YO-A5; Wed, 09 Jul 2014 11:28:27 +0000
Received: from [85.158.143.35:48846] by server-1.bemta-4.messagelabs.com id
	3F/DE-09496-A572DB35; Wed, 09 Jul 2014 11:28:26 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-12.tower-21.messagelabs.com!1404905305!16822071!1
X-Originating-IP: [74.125.82.181]
X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 7843 invoked from network); 9 Jul 2014 11:28:25 -0000
Received: from mail-we0-f181.google.com (HELO mail-we0-f181.google.com)
	(74.125.82.181)
	by server-12.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	9 Jul 2014 11:28:25 -0000
Received: by mail-we0-f181.google.com with SMTP id q59so7215691wes.26
	for <multiple recipients>; Wed, 09 Jul 2014 04:28:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=sender:message-id:date:from:reply-to:user-agent:mime-version:to:cc
	:subject:references:in-reply-to:content-type;
	bh=CfwbrO7QZ/LyanoguzONsY35npUBFO05s/qFPwP2M5M=;
	b=muzoqpWLZ9XVjxI6piw0/CeajfL+T/iLjfifqzOoBvnatuk+//BrPLoa9Ad4o0oLg4
	kHiXwU7liPGiGjt//qInNhOEInCf9rWGIfzHmloB0VOqGT+gpwx5ZposuakHtRsY5q/Q
	UfItx2XSr8dICs0ugCygEvIlThBU4+Gf4D/QkET+Zq877QabdOQhx0a2LhlNcHwHzA2h
	dxruHOmtT6aHs0mO7LsC2cMIrlpqz3LCRgvDcjqfEzJnYLgFh+rRvdneaiumZ4SXJ9OC
	bZad8p6wee+UrQCV0bnhL7X9kXJTF6zI9KtZ4sNR85T1ETv1DGhJtF1Keg07k9xs7g9B
	Zi7w==
X-Received: by 10.180.210.165 with SMTP id mv5mr10824733wic.70.1404905305207; 
	Wed, 09 Jul 2014 04:28:25 -0700 (PDT)
Received: from [172.16.25.10] (97e5a05a.skybroadband.com. [151.229.160.90])
	by mx.google.com with ESMTPSA id
	i12sm102770733wjr.32.2014.07.09.04.28.23 for <multiple recipients>
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Wed, 09 Jul 2014 04:28:24 -0700 (PDT)
Message-ID: <53BD2756.2070602@xen.org>
Date: Wed, 09 Jul 2014 12:28:22 +0100
From: Lars Kurth <lars.kurth@xen.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Ian Campbell <Ian.Campbell@citrix.com>
References: <53B28517.9020807@xen.org>
	<1404902570.16789.3.camel@kazak.uk.xensource.com>
In-Reply-To: <1404902570.16789.3.camel@kazak.uk.xensource.com>
Cc: Artem Mygaiev <artem.mygaiev@globallogic.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	"mirageos-devel@lists.xenproject.org"
	<mirageos-devel@lists.xenproject.org>,
	"xen-api@lists.xen.org" <xen-api@lists.xen.org>,
	Alex Agizim <alex.agizim@globallogic.com>,
	Andrii Tseglytskyi <andrii.tseglytskyi@globallogic.com>
Subject: Re: [Xen-API] [Xen-devel] [For Community Review] Embedded and
 Automotive PV Drivers Sub-Project Proposal (deadline July 11th)
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============6650576736798953476=="
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

This is a multi-part message in MIME format.
--===============6650576736798953476==
Content-Type: multipart/alternative;
 boundary="------------050007070204090703070908"

This is a multi-part message in MIME format.
--------------050007070204090703070908
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 09/07/2014 11:42, Ian Campbell wrote:
> On Tue, 2014-07-01 at 10:53 +0100, Lars Kurth wrote:
>> Hi all,
>>
>> the "Embedded and Automotive PV Drivers Sub-Project Proposal" (see
>> http://wiki.xenproject.org/wiki/Embedded_and_Automotive_PV_Drivers_Project_Proposal)
>> is now open for community review. Please provide feedback by replying to
>> this thread
> I think you should avoid the word "staging" entirely in this document.
>
> A staging tree in Xen terminology is something completely different to
> how you use it here: it's the tree where the committers push things which
> serves as the input to our automated test. How about "development" tree?
> Or just avoid them altogether by using the individual developer's own
> trees and the lists.
Either approach works for me.
I replaced "staging" with "development" for now and made it optional. We 
can leave a final decision open. It shouldn't block the proposal

Andrii requested a personal repo, which has not been created yet, but 
Ian Jackson is doing this as we speak

>
> WRT xen-devel being busy and the subproject's own lists, it might be
> wise to have upstream exposure from early on, which would imply ccing
> xen-devel/lkml etc in addition to the subproject list. Otherwise you get
> into the issue where the subproject has accepted something (perhaps into
> a "staging" tree) but when it gets sent upstream it requires major
> reworking (and the developer is long gone, etc etc). Whether that needs
> to be part of the charter though I don't know.
Agreed. CCing other relevant lists (aka xen-devel/lkml) is common 
practice and we should just continue doing this. I can stated this in 
the proposal.

>
> More minor thoughts:
>
> "it is likely and desirable that the project may be useful for other"
>          
>          I'm not sure if this sentence has the end missing or if you
>          intended other to be "others".
Should read "other use-cases". (fixed)
>
> "Part of the reason for this is that some of the hardware to test is
> also not yet available to open source communities."
>
>          This is not (and should not be) a barrier to sending patches to
>          the right place. We have reviewed and accepted plenty of patches
>          for which we have no access to the h/w.
You are correct. I deleted this sentence as it doesn't add anything
>
> "To build these drivers, the QNX GNU libc variant is used (licensed
> under GPL)."
>
>          Not LGPL? QNX using GPL for it's libc seems like an odd choice
>          for them, since it requires anything linking against it to be
>          GPL compatible. I suspect this a typo.
Corrected
>          
> "Must have OSI approved licenses that are required to link with and
> usage the drivers within the native OS."
>
>          I can't parse this sentence. I think s/usage/use might be what
>          was meant but I'm not sure.
Fixed. Meant "use"
>
> "upstreamns"
>
>          Typo
Fixed
>
> WRT graduation -- can we include a requirement that any "staging" trees
> have been retired (e.g. merged upstream or otherwise obsolete).
Done
>
> Ian.
>


--------------050007070204090703070908
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On 09/07/2014 11:42, Ian Campbell
      wrote:<br>
    </div>
    <blockquote
      cite="mid:1404902570.16789.3.camel@kazak.uk.xensource.com"
      type="cite">
      <pre wrap="">
On Tue, 2014-07-01 at 10:53 +0100, Lars Kurth wrote:
</pre>
      <blockquote type="cite">
        <pre wrap="">Hi all,

the "Embedded and Automotive PV Drivers Sub-Project Proposal" (see 
<a class="moz-txt-link-freetext" href="http://wiki.xenproject.org/wiki/Embedded_and_Automotive_PV_Drivers_Project_Proposal">http://wiki.xenproject.org/wiki/Embedded_and_Automotive_PV_Drivers_Project_Proposal</a>) 
is now open for community review. Please provide feedback by replying to 
this thread
</pre>
      </blockquote>
      <pre wrap="">
I think you should avoid the word "staging" entirely in this document.

A staging tree in Xen terminology is something completely different to
how you use it here: it's the tree where the committers push things which
serves as the input to our automated test. How about "development" tree?
Or just avoid them altogether by using the individual developer's own
trees and the lists.</pre>
    </blockquote>
    Either approach works for me. <br>
    I replaced "staging" with "development" for now and made it
    optional. We can leave a final decision open. It shouldn't block the
    proposal<br>
    <br>
    Andrii requested a personal repo, which has not been created yet,
    but Ian Jackson is doing this as we speak<br>
    <br>
    <blockquote
      cite="mid:1404902570.16789.3.camel@kazak.uk.xensource.com"
      type="cite">
      <pre wrap="">

WRT xen-devel being busy and the subproject's own lists, it might be
wise to have upstream exposure from early on, which would imply ccing
xen-devel/lkml etc in addition to the subproject list. Otherwise you get
into the issue where the subproject has accepted something (perhaps into
a "staging" tree) but when it gets sent upstream it requires major
reworking (and the developer is long gone, etc etc). Whether that needs
to be part of the charter though I don't know.</pre>
    </blockquote>
    Agreed. CCing other relevant lists (aka xen-devel/lkml) is common
    practice and we should just continue doing this. I can stated this
    in the proposal.<br>
    <br>
    <blockquote
      cite="mid:1404902570.16789.3.camel@kazak.uk.xensource.com"
      type="cite">
      <pre wrap="">

More minor thoughts:

"it is likely and desirable that the project may be useful for other"
        
        I'm not sure if this sentence has the end missing or if you
        intended other to be "others".</pre>
    </blockquote>
    Should read "<span style="color: rgb(0, 0, 0); font-family: Arial,
      sans-serif; font-size: 15.454545021057129px; font-style: normal;
      font-variant: normal; font-weight: normal; letter-spacing: normal;
      line-height: 22.85999870300293px; orphans: auto; text-align:
      start; text-indent: 0px; text-transform: none; white-space:
      normal; widows: auto; word-spacing: 0px;
      -webkit-text-stroke-width: 0px; display: inline !important; float:
      none; background-color: rgb(255, 255, 255);">other use-cases".
      (fixed)<br>
    </span>
    <blockquote
      cite="mid:1404902570.16789.3.camel@kazak.uk.xensource.com"
      type="cite">
      <pre wrap="">

"Part of the reason for this is that some of the hardware to test is
also not yet available to open source communities."

        This is not (and should not be) a barrier to sending patches to
        the right place. We have reviewed and accepted plenty of patches
        for which we have no access to the h/w.</pre>
    </blockquote>
    You are correct. I deleted this sentence as it doesn't add anything
    <br>
    <blockquote
      cite="mid:1404902570.16789.3.camel@kazak.uk.xensource.com"
      type="cite">
      <pre wrap="">

"To build these drivers, the QNX GNU libc variant is used (licensed
under GPL)."

        Not LGPL? QNX using GPL for it's libc seems like an odd choice
        for them, since it requires anything linking against it to be
        GPL compatible. I suspect this a typo.</pre>
    </blockquote>
    Corrected<br>
    <blockquote
      cite="mid:1404902570.16789.3.camel@kazak.uk.xensource.com"
      type="cite">
      <pre wrap="">
        
"Must have OSI approved licenses that are required to link with and
usage the drivers within the native OS."

        I can't parse this sentence. I think s/usage/use might be what
        was meant but I'm not sure.</pre>
    </blockquote>
    Fixed. Meant "use"<br>
    <blockquote
      cite="mid:1404902570.16789.3.camel@kazak.uk.xensource.com"
      type="cite">
      <pre wrap="">

"upstreamns"

        Typo</pre>
    </blockquote>
    Fixed<br>
    <blockquote
      cite="mid:1404902570.16789.3.camel@kazak.uk.xensource.com"
      type="cite">
      <pre wrap="">

WRT graduation -- can we include a requirement that any "staging" trees
have been retired (e.g. merged upstream or otherwise obsolete).</pre>
    </blockquote>
    Done<br>
    <blockquote
      cite="mid:1404902570.16789.3.camel@kazak.uk.xensource.com"
      type="cite">
      <pre wrap="">

Ian.

</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------050007070204090703070908--


--===============6650576736798953476==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--===============6650576736798953476==--


From xen-api-bounces@lists.xen.org Wed Jul 09 11:28:32 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 09 Jul 2014 11:28:32 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X4q33-0004Ye-0I; Wed, 09 Jul 2014 11:28:29 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <lars.kurth.xen@gmail.com>)
	id 1X4q31-0004YO-A5; Wed, 09 Jul 2014 11:28:27 +0000
Received: from [85.158.143.35:48846] by server-1.bemta-4.messagelabs.com id
	3F/DE-09496-A572DB35; Wed, 09 Jul 2014 11:28:26 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-12.tower-21.messagelabs.com!1404905305!16822071!1
X-Originating-IP: [74.125.82.181]
X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 7843 invoked from network); 9 Jul 2014 11:28:25 -0000
Received: from mail-we0-f181.google.com (HELO mail-we0-f181.google.com)
	(74.125.82.181)
	by server-12.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	9 Jul 2014 11:28:25 -0000
Received: by mail-we0-f181.google.com with SMTP id q59so7215691wes.26
	for <multiple recipients>; Wed, 09 Jul 2014 04:28:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=sender:message-id:date:from:reply-to:user-agent:mime-version:to:cc
	:subject:references:in-reply-to:content-type;
	bh=CfwbrO7QZ/LyanoguzONsY35npUBFO05s/qFPwP2M5M=;
	b=muzoqpWLZ9XVjxI6piw0/CeajfL+T/iLjfifqzOoBvnatuk+//BrPLoa9Ad4o0oLg4
	kHiXwU7liPGiGjt//qInNhOEInCf9rWGIfzHmloB0VOqGT+gpwx5ZposuakHtRsY5q/Q
	UfItx2XSr8dICs0ugCygEvIlThBU4+Gf4D/QkET+Zq877QabdOQhx0a2LhlNcHwHzA2h
	dxruHOmtT6aHs0mO7LsC2cMIrlpqz3LCRgvDcjqfEzJnYLgFh+rRvdneaiumZ4SXJ9OC
	bZad8p6wee+UrQCV0bnhL7X9kXJTF6zI9KtZ4sNR85T1ETv1DGhJtF1Keg07k9xs7g9B
	Zi7w==
X-Received: by 10.180.210.165 with SMTP id mv5mr10824733wic.70.1404905305207; 
	Wed, 09 Jul 2014 04:28:25 -0700 (PDT)
Received: from [172.16.25.10] (97e5a05a.skybroadband.com. [151.229.160.90])
	by mx.google.com with ESMTPSA id
	i12sm102770733wjr.32.2014.07.09.04.28.23 for <multiple recipients>
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Wed, 09 Jul 2014 04:28:24 -0700 (PDT)
Message-ID: <53BD2756.2070602@xen.org>
Date: Wed, 09 Jul 2014 12:28:22 +0100
From: Lars Kurth <lars.kurth@xen.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Ian Campbell <Ian.Campbell@citrix.com>
References: <53B28517.9020807@xen.org>
	<1404902570.16789.3.camel@kazak.uk.xensource.com>
In-Reply-To: <1404902570.16789.3.camel@kazak.uk.xensource.com>
Cc: Artem Mygaiev <artem.mygaiev@globallogic.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	"mirageos-devel@lists.xenproject.org"
	<mirageos-devel@lists.xenproject.org>,
	"xen-api@lists.xen.org" <xen-api@lists.xen.org>,
	Alex Agizim <alex.agizim@globallogic.com>,
	Andrii Tseglytskyi <andrii.tseglytskyi@globallogic.com>
Subject: Re: [Xen-API] [Xen-devel] [For Community Review] Embedded and
 Automotive PV Drivers Sub-Project Proposal (deadline July 11th)
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============6650576736798953476=="
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

This is a multi-part message in MIME format.
--===============6650576736798953476==
Content-Type: multipart/alternative;
 boundary="------------050007070204090703070908"

This is a multi-part message in MIME format.
--------------050007070204090703070908
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 09/07/2014 11:42, Ian Campbell wrote:
> On Tue, 2014-07-01 at 10:53 +0100, Lars Kurth wrote:
>> Hi all,
>>
>> the "Embedded and Automotive PV Drivers Sub-Project Proposal" (see
>> http://wiki.xenproject.org/wiki/Embedded_and_Automotive_PV_Drivers_Project_Proposal)
>> is now open for community review. Please provide feedback by replying to
>> this thread
> I think you should avoid the word "staging" entirely in this document.
>
> A staging tree in Xen terminology is something completely different to
> how you use it here: it's the tree where the committers push things which
> serves as the input to our automated test. How about "development" tree?
> Or just avoid them altogether by using the individual developer's own
> trees and the lists.
Either approach works for me.
I replaced "staging" with "development" for now and made it optional. We 
can leave a final decision open. It shouldn't block the proposal

Andrii requested a personal repo, which has not been created yet, but 
Ian Jackson is doing this as we speak

>
> WRT xen-devel being busy and the subproject's own lists, it might be
> wise to have upstream exposure from early on, which would imply ccing
> xen-devel/lkml etc in addition to the subproject list. Otherwise you get
> into the issue where the subproject has accepted something (perhaps into
> a "staging" tree) but when it gets sent upstream it requires major
> reworking (and the developer is long gone, etc etc). Whether that needs
> to be part of the charter though I don't know.
Agreed. CCing other relevant lists (aka xen-devel/lkml) is common 
practice and we should just continue doing this. I can stated this in 
the proposal.

>
> More minor thoughts:
>
> "it is likely and desirable that the project may be useful for other"
>          
>          I'm not sure if this sentence has the end missing or if you
>          intended other to be "others".
Should read "other use-cases". (fixed)
>
> "Part of the reason for this is that some of the hardware to test is
> also not yet available to open source communities."
>
>          This is not (and should not be) a barrier to sending patches to
>          the right place. We have reviewed and accepted plenty of patches
>          for which we have no access to the h/w.
You are correct. I deleted this sentence as it doesn't add anything
>
> "To build these drivers, the QNX GNU libc variant is used (licensed
> under GPL)."
>
>          Not LGPL? QNX using GPL for it's libc seems like an odd choice
>          for them, since it requires anything linking against it to be
>          GPL compatible. I suspect this a typo.
Corrected
>          
> "Must have OSI approved licenses that are required to link with and
> usage the drivers within the native OS."
>
>          I can't parse this sentence. I think s/usage/use might be what
>          was meant but I'm not sure.
Fixed. Meant "use"
>
> "upstreamns"
>
>          Typo
Fixed
>
> WRT graduation -- can we include a requirement that any "staging" trees
> have been retired (e.g. merged upstream or otherwise obsolete).
Done
>
> Ian.
>


--------------050007070204090703070908
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On 09/07/2014 11:42, Ian Campbell
      wrote:<br>
    </div>
    <blockquote
      cite="mid:1404902570.16789.3.camel@kazak.uk.xensource.com"
      type="cite">
      <pre wrap="">
On Tue, 2014-07-01 at 10:53 +0100, Lars Kurth wrote:
</pre>
      <blockquote type="cite">
        <pre wrap="">Hi all,

the "Embedded and Automotive PV Drivers Sub-Project Proposal" (see 
<a class="moz-txt-link-freetext" href="http://wiki.xenproject.org/wiki/Embedded_and_Automotive_PV_Drivers_Project_Proposal">http://wiki.xenproject.org/wiki/Embedded_and_Automotive_PV_Drivers_Project_Proposal</a>) 
is now open for community review. Please provide feedback by replying to 
this thread
</pre>
      </blockquote>
      <pre wrap="">
I think you should avoid the word "staging" entirely in this document.

A staging tree in Xen terminology is something completely different to
how you use it here: it's the tree where the committers push things which
serves as the input to our automated test. How about "development" tree?
Or just avoid them altogether by using the individual developer's own
trees and the lists.</pre>
    </blockquote>
    Either approach works for me. <br>
    I replaced "staging" with "development" for now and made it
    optional. We can leave a final decision open. It shouldn't block the
    proposal<br>
    <br>
    Andrii requested a personal repo, which has not been created yet,
    but Ian Jackson is doing this as we speak<br>
    <br>
    <blockquote
      cite="mid:1404902570.16789.3.camel@kazak.uk.xensource.com"
      type="cite">
      <pre wrap="">

WRT xen-devel being busy and the subproject's own lists, it might be
wise to have upstream exposure from early on, which would imply ccing
xen-devel/lkml etc in addition to the subproject list. Otherwise you get
into the issue where the subproject has accepted something (perhaps into
a "staging" tree) but when it gets sent upstream it requires major
reworking (and the developer is long gone, etc etc). Whether that needs
to be part of the charter though I don't know.</pre>
    </blockquote>
    Agreed. CCing other relevant lists (aka xen-devel/lkml) is common
    practice and we should just continue doing this. I can stated this
    in the proposal.<br>
    <br>
    <blockquote
      cite="mid:1404902570.16789.3.camel@kazak.uk.xensource.com"
      type="cite">
      <pre wrap="">

More minor thoughts:

"it is likely and desirable that the project may be useful for other"
        
        I'm not sure if this sentence has the end missing or if you
        intended other to be "others".</pre>
    </blockquote>
    Should read "<span style="color: rgb(0, 0, 0); font-family: Arial,
      sans-serif; font-size: 15.454545021057129px; font-style: normal;
      font-variant: normal; font-weight: normal; letter-spacing: normal;
      line-height: 22.85999870300293px; orphans: auto; text-align:
      start; text-indent: 0px; text-transform: none; white-space:
      normal; widows: auto; word-spacing: 0px;
      -webkit-text-stroke-width: 0px; display: inline !important; float:
      none; background-color: rgb(255, 255, 255);">other use-cases".
      (fixed)<br>
    </span>
    <blockquote
      cite="mid:1404902570.16789.3.camel@kazak.uk.xensource.com"
      type="cite">
      <pre wrap="">

"Part of the reason for this is that some of the hardware to test is
also not yet available to open source communities."

        This is not (and should not be) a barrier to sending patches to
        the right place. We have reviewed and accepted plenty of patches
        for which we have no access to the h/w.</pre>
    </blockquote>
    You are correct. I deleted this sentence as it doesn't add anything
    <br>
    <blockquote
      cite="mid:1404902570.16789.3.camel@kazak.uk.xensource.com"
      type="cite">
      <pre wrap="">

"To build these drivers, the QNX GNU libc variant is used (licensed
under GPL)."

        Not LGPL? QNX using GPL for it's libc seems like an odd choice
        for them, since it requires anything linking against it to be
        GPL compatible. I suspect this a typo.</pre>
    </blockquote>
    Corrected<br>
    <blockquote
      cite="mid:1404902570.16789.3.camel@kazak.uk.xensource.com"
      type="cite">
      <pre wrap="">
        
"Must have OSI approved licenses that are required to link with and
usage the drivers within the native OS."

        I can't parse this sentence. I think s/usage/use might be what
        was meant but I'm not sure.</pre>
    </blockquote>
    Fixed. Meant "use"<br>
    <blockquote
      cite="mid:1404902570.16789.3.camel@kazak.uk.xensource.com"
      type="cite">
      <pre wrap="">

"upstreamns"

        Typo</pre>
    </blockquote>
    Fixed<br>
    <blockquote
      cite="mid:1404902570.16789.3.camel@kazak.uk.xensource.com"
      type="cite">
      <pre wrap="">

WRT graduation -- can we include a requirement that any "staging" trees
have been retired (e.g. merged upstream or otherwise obsolete).</pre>
    </blockquote>
    Done<br>
    <blockquote
      cite="mid:1404902570.16789.3.camel@kazak.uk.xensource.com"
      type="cite">
      <pre wrap="">

Ian.

</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------050007070204090703070908--


--===============6650576736798953476==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--===============6650576736798953476==--


From xen-api-bounces@lists.xen.org Wed Jul 09 11:46:58 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 09 Jul 2014 11:46:58 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X4qKs-0005I2-MX; Wed, 09 Jul 2014 11:46:54 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <Ian.Campbell@citrix.com>)
	id 1X4qKr-0005Hp-GY; Wed, 09 Jul 2014 11:46:53 +0000
Received: from [193.109.254.147:40303] by server-2.bemta-14.messagelabs.com id
	82/80-30377-CAB2DB35; Wed, 09 Jul 2014 11:46:52 +0000
X-Env-Sender: Ian.Campbell@citrix.com
X-Msg-Ref: server-2.tower-27.messagelabs.com!1404906410!16354146!1
X-Originating-IP: [66.165.176.89]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 16765 invoked from network); 9 Jul 2014 11:46:52 -0000
Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89)
	by server-2.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	9 Jul 2014 11:46:52 -0000
X-IronPort-AV: E=Sophos;i="5.01,630,1400025600"; d="scan'208";a="150924619"
Received: from accessns.citrite.net (HELO FTLPEX01CL02.citrite.net)
	([10.9.154.239])
	by FTLPIPO01.CITRIX.COM with ESMTP; 09 Jul 2014 11:46:51 +0000
Received: from kazak.uk.xensource.com (10.80.2.80) by FTLPEX01CL02.citrite.net
	(10.13.107.79) with Microsoft SMTP Server id 14.3.181.6;
	Wed, 9 Jul 2014 07:46:49 -0400
Message-ID: <1404906408.16789.14.camel@kazak.uk.xensource.com>
From: Ian Campbell <Ian.Campbell@citrix.com>
To: <lars.kurth@xen.org>
Date: Wed, 9 Jul 2014 12:46:48 +0100
In-Reply-To: <53BD2756.2070602@xen.org>
References: <53B28517.9020807@xen.org>
	<1404902570.16789.3.camel@kazak.uk.xensource.com>
	<53BD2756.2070602@xen.org>
Organization: Citrix Systems, Inc.
X-Mailer: Evolution 3.12.2-1 
MIME-Version: 1.0
X-Originating-IP: [10.80.2.80]
X-DLP: MIA2
Cc: Artem Mygaiev <artem.mygaiev@globallogic.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	"mirageos-devel@lists.xenproject.org"
	<mirageos-devel@lists.xenproject.org>,
	"xen-api@lists.xen.org" <xen-api@lists.xen.org>,
	Alex Agizim <alex.agizim@globallogic.com>,
	Andrii Tseglytskyi <andrii.tseglytskyi@globallogic.com>
Subject: Re: [Xen-API] [Xen-devel] [For Community Review] Embedded and
 Automotive PV Drivers Sub-Project Proposal (deadline July 11th)
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

On Wed, 2014-07-09 at 12:28 +0100, Lars Kurth wrote:

> > 
> > "To build these drivers, the QNX GNU libc variant is used (licensed
> > under GPL)."
> > 
> >         Not LGPL? QNX using GPL for it's libc seems like an odd choice
> >         for them, since it requires anything linking against it to be
> >         GPL compatible. I suspect this a typo.
> Corrected

Just to be clear; I've no idea what license the QNX libc is under, it
could be GPL for all I know, I was just querying it because it surprised
me.

(Just want to be sure you didn't assume I know it was LGPL or something)

Ian.


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

From xen-api-bounces@lists.xen.org Wed Jul 09 11:46:58 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 09 Jul 2014 11:46:58 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X4qKs-0005I2-MX; Wed, 09 Jul 2014 11:46:54 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <Ian.Campbell@citrix.com>)
	id 1X4qKr-0005Hp-GY; Wed, 09 Jul 2014 11:46:53 +0000
Received: from [193.109.254.147:40303] by server-2.bemta-14.messagelabs.com id
	82/80-30377-CAB2DB35; Wed, 09 Jul 2014 11:46:52 +0000
X-Env-Sender: Ian.Campbell@citrix.com
X-Msg-Ref: server-2.tower-27.messagelabs.com!1404906410!16354146!1
X-Originating-IP: [66.165.176.89]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 16765 invoked from network); 9 Jul 2014 11:46:52 -0000
Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89)
	by server-2.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	9 Jul 2014 11:46:52 -0000
X-IronPort-AV: E=Sophos;i="5.01,630,1400025600"; d="scan'208";a="150924619"
Received: from accessns.citrite.net (HELO FTLPEX01CL02.citrite.net)
	([10.9.154.239])
	by FTLPIPO01.CITRIX.COM with ESMTP; 09 Jul 2014 11:46:51 +0000
Received: from kazak.uk.xensource.com (10.80.2.80) by FTLPEX01CL02.citrite.net
	(10.13.107.79) with Microsoft SMTP Server id 14.3.181.6;
	Wed, 9 Jul 2014 07:46:49 -0400
Message-ID: <1404906408.16789.14.camel@kazak.uk.xensource.com>
From: Ian Campbell <Ian.Campbell@citrix.com>
To: <lars.kurth@xen.org>
Date: Wed, 9 Jul 2014 12:46:48 +0100
In-Reply-To: <53BD2756.2070602@xen.org>
References: <53B28517.9020807@xen.org>
	<1404902570.16789.3.camel@kazak.uk.xensource.com>
	<53BD2756.2070602@xen.org>
Organization: Citrix Systems, Inc.
X-Mailer: Evolution 3.12.2-1 
MIME-Version: 1.0
X-Originating-IP: [10.80.2.80]
X-DLP: MIA2
Cc: Artem Mygaiev <artem.mygaiev@globallogic.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	"mirageos-devel@lists.xenproject.org"
	<mirageos-devel@lists.xenproject.org>,
	"xen-api@lists.xen.org" <xen-api@lists.xen.org>,
	Alex Agizim <alex.agizim@globallogic.com>,
	Andrii Tseglytskyi <andrii.tseglytskyi@globallogic.com>
Subject: Re: [Xen-API] [Xen-devel] [For Community Review] Embedded and
 Automotive PV Drivers Sub-Project Proposal (deadline July 11th)
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

On Wed, 2014-07-09 at 12:28 +0100, Lars Kurth wrote:

> > 
> > "To build these drivers, the QNX GNU libc variant is used (licensed
> > under GPL)."
> > 
> >         Not LGPL? QNX using GPL for it's libc seems like an odd choice
> >         for them, since it requires anything linking against it to be
> >         GPL compatible. I suspect this a typo.
> Corrected

Just to be clear; I've no idea what license the QNX libc is under, it
could be GPL for all I know, I was just querying it because it surprised
me.

(Just want to be sure you didn't assume I know it was LGPL or something)

Ian.


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

From xen-api-bounces@lists.xen.org Wed Jul 09 14:32:52 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 09 Jul 2014 14:32:52 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X4svK-0008AJ-OZ; Wed, 09 Jul 2014 14:32:42 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <dobropalka@gmail.com>) id 1X4svI-0008AE-O2
	for xen-api@lists.xen.org; Wed, 09 Jul 2014 14:32:41 +0000
Received: from [85.158.143.35:48256] by server-3.bemta-4.messagelabs.com id
	84/B3-16194-8825DB35; Wed, 09 Jul 2014 14:32:40 +0000
X-Env-Sender: dobropalka@gmail.com
X-Msg-Ref: server-8.tower-21.messagelabs.com!1404916357!16849594!1
X-Originating-IP: [209.85.217.181]
X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_14,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 23939 invoked from network); 9 Jul 2014 14:32:38 -0000
Received: from mail-lb0-f181.google.com (HELO mail-lb0-f181.google.com)
	(209.85.217.181)
	by server-8.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	9 Jul 2014 14:32:38 -0000
Received: by mail-lb0-f181.google.com with SMTP id p9so5021603lbv.40
	for <xen-api@lists.xen.org>; Wed, 09 Jul 2014 07:32:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=from:to:references:in-reply-to:subject:date:message-id:mime-version
	:content-type:thread-index:content-language;
	bh=VfmS/01wvzKHPAGflS5LpQ5QcfbttGTet5MOWjjaDAA=;
	b=wytMg0aXKHQAIESOvo1jvIZO58dmGxumtMYm3bVcTjxaY+cJG1zHUxVbx7xgJWgM+/
	jvceZmqfodeo2pLHcZYNZOI3SZyZEAQHwMIYaA5Gs5ApJBDSnGrdSUDb8qjizxvAjkiL
	yCECi1Ft5P2huURtgfm5aF7iu0nXJ6Z5lb0Z1cjuYulshg1MBvDe+B4fU8neaSoLwy6h
	i7y9DPMI2aBs50aJ9j42dj6iqVn7+9yENaKWemwBwIzCBRWRkv0y890E9OgmliQEUcvw
	yua4zyzKVqQF3XVgBXnowNhxWWWWmBdUJLTBJrd8kRnKaanFH4ML5RWZcBjZ+C4gyebl
	qdjw==
X-Received: by 10.152.42.172 with SMTP id p12mr2231022lal.61.1404916357735;
	Wed, 09 Jul 2014 07:32:37 -0700 (PDT)
Received: from RUIT06 ([217.23.88.19])
	by mx.google.com with ESMTPSA id q8sm60875087lbr.28.2014.07.09.07.32.36
	for <multiple recipients>
	(version=TLSv1.2 cipher=ECDHE-RSA-AES128-SHA bits=128/128);
	Wed, 09 Jul 2014 07:32:36 -0700 (PDT)
From: "dobropalka" <dobropalka@gmail.com>
To: "'Jonathan Ludlam'" <Jonathan.Ludlam@citrix.com>, <xen-api@lists.xen.org>
References: <01e901cf9860$935928d0$ba0b7a70$@gmail.com>
	<660D43EB050DE94AACCFA0BB1489A98278C04F@AMSPEX01CL01.citrite.net>
In-Reply-To: <660D43EB050DE94AACCFA0BB1489A98278C04F@AMSPEX01CL01.citrite.net>
Date: Wed, 9 Jul 2014 18:32:35 +0400
Message-ID: <02ee01cf9b82$a104bdd0$e30e3970$@gmail.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQLDfN62yPVY+SRfe8N+9vPz4GrQigGgVrGumaMIc9A=
Content-Language: ru
Subject: Re: [Xen-API] connection to pool master is buggy
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0322844046018217455=="
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

This is a multipart message in MIME format.

--===============0322844046018217455==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_02EF_01CF9BA4.2818F5E0"
Content-Language: ru

This is a multipart message in MIME format.

------=_NextPart_000_02EF_01CF9BA4.2818F5E0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Well, thanks for info. Actually, due to these messages it's hard to look
through logs.

Glad that it will be fixed

 

From: Jonathan Ludlam [mailto:Jonathan.Ludlam@citrix.com] 
Sent: Monday, July 7, 2014 2:50 PM
To: 'dobropalka'; xen-api@lists.xen.org
Subject: RE: [Xen-API] connection to pool master is buggy

 

Hi Ivan,

 

These messages are benign. At some point we'd like to clean up the logging,
as it does tend to be a bit spammy.

 

Cheers,

 

Jon

 

 

From: xen-api-bounces@lists.xen.org <mailto:xen-api-bounces@lists.xen.org>
[mailto:xen-api-bounces@lists.xen.org] On Behalf Of dobropalka
Sent: 05 July 2014 3:51 PM
To: xen-api@lists.xen.org <mailto:xen-api@lists.xen.org> 
Subject: [Xen-API] connection to pool master is buggy

 

Hello, guys!

We got a little pool of 4 xenservers. Everything seems to work fine, but all
my xensource logs are full of these debug messages:

 

Jul  4 08:09:56 cloudstack22 xapi: [ info|cloudstack22|221070 UNIX
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|xapi]
Session.create trackid=d99439bce7424c057acf8204cea45f24 pool=false
uname=root is_local_superuser=true auth_user_sid=
parent=trackid=9834f5af41c964e225f24279aefe4e49

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|mscgen] xapi=>xapi
[label="(XML)"];

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|stunnel]
check_reusable: caught exception Unix.Unix_error(31, "write", ""); assuming
not reusable

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|stunnel]
get_reusable_stunnel: Found non-reusable stunnel in the cache. disconnecting
from 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|stunnel]
get_reusable_stunnel: stunnel cache is empty; creating a fresh connection to
10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [ info|cloudstack22|214513 INET
0.0.0.0:80|sm_exec D:176fe384092b|xapi] Session.destroy
trackid=667f0d1664f406698854c89fe03aca7c

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|xmlrpc_client]
stunnel pid: 26281 (cached = true) connected to 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|xmlrpc_client]
with_recorded_stunnelpid task_opt=None s_pid=26281

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|xmlrpc_client]
stunnel pid: 26281 (cached = true) returned stunnel to cache

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221071 UNIX
/var/xapi/xapi||mscgen] xapi=>xapi [label="(XML)"];

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221071 UNIX
/var/xapi/xapi||xmlrpc_client] stunnel pid: 26281 (cached = true) connected
to 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221071 UNIX
/var/xapi/xapi||xmlrpc_client] with_recorded_stunnelpid task_opt=None
s_pid=26281

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221071 UNIX
/var/xapi/xapi||xmlrpc_client] stunnel pid: 26281 (cached = true) returned
stunnel to cache

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX
/var/xapi/xapi||mscgen] xapi=>xapi [label="(XML)"];

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX
/var/xapi/xapi||stunnel] check_reusable: caught exception
Unix.Unix_error(31, "write", ""); assuming not reusable

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX
/var/xapi/xapi||stunnel] get_reusable_stunnel: Found non-reusable stunnel in
the cache. disconnecting from 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX
/var/xapi/xapi||stunnel] get_reusable_stunnel: stunnel cache is empty;
creating a fresh connection to 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX
/var/xapi/xapi||xmlrpc_client] stunnel pid: 26287 (cached = true) connected
to 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX
/var/xapi/xapi||xmlrpc_client] with_recorded_stunnelpid task_opt=None
s_pid=26287

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX
/var/xapi/xapi||xmlrpc_client] stunnel pid: 26287 (cached = true) returned
stunnel to cache

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX
/var/xapi/xapi||mscgen] xapi=>xapi [label="(XML)"];

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX
/var/xapi/xapi||stunnel] check_reusable: caught exception
Unix.Unix_error(31, "write", ""); assuming not reusable

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX
/var/xapi/xapi||stunnel] get_reusable_stunnel: Found non-reusable stunnel in
the cache. disconnecting from 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX
/var/xapi/xapi||stunnel] get_reusable_stunnel: stunnel cache is empty;
creating a fresh connection to 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|214513 INET
0.0.0.0:80|SR.scan R:eb94a1324f62|taskhelper] forwarded task destroyed

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX
/var/xapi/xapi||xmlrpc_client] stunnel pid: 26292 (cached = true) connected
to 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX
/var/xapi/xapi||xmlrpc_client] with_recorded_stunnelpid task_opt=None
s_pid=26292

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX
/var/xapi/xapi||xmlrpc_client] stunnel pid: 26292 (cached = true) returned
stunnel to cache

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX
/var/xapi/xapi||mscgen] xapi=>xapi [label="(XML)"];

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX
/var/xapi/xapi||stunnel] check_reusable: caught exception
Unix.Unix_error(31, "write", ""); assuming not reusable

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX
/var/xapi/xapi||stunnel] get_reusable_stunnel: Found non-reusable stunnel in
the cache. disconnecting from 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX
/var/xapi/xapi||stunnel] get_reusable_stunnel: stunnel cache is empty;
creating a fresh connection to 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX
/var/xapi/xapi||xmlrpc_client] stunnel pid: 26297 (cached = true) connected
to 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX
/var/xapi/xapi||xmlrpc_client] with_recorded_stunnelpid task_opt=None
s_pid=26297

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX
/var/xapi/xapi||xmlrpc_client] stunnel pid: 26297 (cached = true) returned
stunnel to cache

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX
/var/xapi/xapi||mscgen] xapi=>xapi [label="(XML)"];

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX
/var/xapi/xapi||stunnel] check_reusable: caught exception
Unix.Unix_error(31, "write", ""); assuming not reusable

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX
/var/xapi/xapi||stunnel] get_reusable_stunnel: Found non-reusable stunnel in
the cache. disconnecting from 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX
/var/xapi/xapi||stunnel] get_reusable_stunnel: stunnel cache is empty;
creating a fresh connection to 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX
/var/xapi/xapi||xmlrpc_client] stunnel pid: 26302 (cached = true) connected
to 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX
/var/xapi/xapi||xmlrpc_client] with_recorded_stunnelpid task_opt=None
s_pid=26302

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX
/var/xapi/xapi||xmlrpc_client] stunnel pid: 26302 (cached = true) returned
stunnel to cache

 

The only mention I found in internet didn't give me a clue.

Still, cluster works fine, I'm just worried if there's a bug somewhere
deeper then I see and it can cause some problems

 

Regards, 

Ivan Derbenev

 


------=_NextPart_000_02EF_01CF9BA4.2818F5E0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 15 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:2.0cm 42.5pt 2.0cm 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DRU =
link=3D"#0563C1" vlink=3D"#954F72"><div class=3DWordSection1><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>Well, =
thanks for info. Actually, due to these messages it&#8217;s hard to look =
through logs.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>Glad that it will be =
fixed<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm'><p class=3DMsoNormal><b><span =
style=3D'mso-fareast-language:RU'>From:</span></b><span =
style=3D'mso-fareast-language:RU'> Jonathan Ludlam =
[mailto:Jonathan.Ludlam@citrix.com] <br><b>Sent:</b> Monday, July 7, =
2014 2:50 PM<br><b>To:</b> 'dobropalka'; =
xen-api@lists.xen.org<br><b>Subject:</b> RE: [Xen-API] connection to =
pool master is buggy<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
lang=3DEN-GB style=3D'color:#1F497D'>Hi Ivan,<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB style=3D'color:#1F497D'>These =
messages are benign. At some point we&#8217;d like to clean up the =
logging, as it does tend to be a bit spammy.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB =
style=3D'color:#1F497D'>Cheers,<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB =
style=3D'color:#1F497D'>Jon<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'><p class=3DMsoNormal><b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-l=
anguage:ZH-CN'>From:</span></b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-l=
anguage:ZH-CN'> <a =
href=3D"mailto:xen-api-bounces@lists.xen.org">xen-api-bounces@lists.xen.o=
rg</a> [<a =
href=3D"mailto:xen-api-bounces@lists.xen.org">mailto:xen-api-bounces@list=
s.xen.org</a>] <b>On Behalf Of </b>dobropalka<br><b>Sent:</b> 05 July =
2014 3:51 PM<br><b>To:</b> <a =
href=3D"mailto:xen-api@lists.xen.org">xen-api@lists.xen.org</a><br><b>Sub=
ject:</b> [Xen-API] connection to pool master is =
buggy<o:p></o:p></span></p></div></div><p class=3DMsoNormal><span =
lang=3DEN-GB><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><span lang=3DEN-US>Hello, =
guys!<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US>We =
got a little pool of 4 xenservers. Everything seems to work fine, but =
all my xensource logs are full of these debug =
messages:<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 xapi: [ =
info|cloudstack22|221070 UNIX /var/xapi/xapi|session.login_with_password =
D:9579fb00c72a|xapi] Session.create =
trackid=3Dd99439bce7424c057acf8204cea45f24 pool=3Dfalse uname=3Droot =
is_local_superuser=3Dtrue auth_user_sid=3D =
parent=3Dtrackid=3D9834f5af41c964e225f24279aefe4e49<o:p></o:p></span></p>=
<p class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 =
cloudstack22 xapi: [debug|cloudstack22|221070 UNIX =
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|mscgen] =
xapi=3D&gt;xapi [label=3D&quot;(XML)&quot;];<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221070 UNIX =
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|stunnel] =
check_reusable: caught exception Unix.Unix_error(31, &quot;write&quot;, =
&quot;&quot;); assuming not reusable<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221070 UNIX =
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|stunnel] =
get_reusable_stunnel: Found non-reusable stunnel in the cache. =
disconnecting from 10.50.128.21:443<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221070 UNIX =
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|stunnel] =
get_reusable_stunnel: stunnel cache is empty; creating a fresh =
connection to 10.50.128.21:443<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [ info|cloudstack22|214513 INET 0.0.0.0:80|sm_exec =
D:176fe384092b|xapi] Session.destroy =
trackid=3D667f0d1664f406698854c89fe03aca7c<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221070 UNIX =
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|xmlrpc_client] =
stunnel pid: 26281 (cached =3D true) connected to =
10.50.128.21:443<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221070 UNIX =
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|xmlrpc_client] =
with_recorded_stunnelpid task_opt=3DNone =
s_pid=3D26281<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221070 UNIX =
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|xmlrpc_client] =
stunnel pid: 26281 (cached =3D true) returned stunnel to =
cache<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221071 UNIX /var/xapi/xapi||mscgen] xapi=3D&gt;xapi =
[label=3D&quot;(XML)&quot;];<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221071 UNIX /var/xapi/xapi||xmlrpc_client] =
stunnel pid: 26281 (cached =3D true) connected to =
10.50.128.21:443<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221071 UNIX /var/xapi/xapi||xmlrpc_client] =
with_recorded_stunnelpid task_opt=3DNone =
s_pid=3D26281<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221071 UNIX /var/xapi/xapi||xmlrpc_client] stunnel =
pid: 26281 (cached =3D true) returned stunnel to =
cache<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221072 UNIX /var/xapi/xapi||mscgen] xapi=3D&gt;xapi =
[label=3D&quot;(XML)&quot;];<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221072 UNIX /var/xapi/xapi||stunnel] =
check_reusable: caught exception Unix.Unix_error(31, &quot;write&quot;, =
&quot;&quot;); assuming not reusable<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221072 UNIX /var/xapi/xapi||stunnel] =
get_reusable_stunnel: Found non-reusable stunnel in the cache. =
disconnecting from 10.50.128.21:443<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221072 UNIX /var/xapi/xapi||stunnel] =
get_reusable_stunnel: stunnel cache is empty; creating a fresh =
connection to 10.50.128.21:443<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221072 UNIX /var/xapi/xapi||xmlrpc_client] =
stunnel pid: 26287 (cached =3D true) connected to =
10.50.128.21:443<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221072 UNIX /var/xapi/xapi||xmlrpc_client] =
with_recorded_stunnelpid task_opt=3DNone =
s_pid=3D26287<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221072 UNIX /var/xapi/xapi||xmlrpc_client] stunnel =
pid: 26287 (cached =3D true) returned stunnel to =
cache<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221073 UNIX /var/xapi/xapi||mscgen] xapi=3D&gt;xapi =
[label=3D&quot;(XML)&quot;];<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221073 UNIX /var/xapi/xapi||stunnel] =
check_reusable: caught exception Unix.Unix_error(31, &quot;write&quot;, =
&quot;&quot;); assuming not reusable<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221073 UNIX /var/xapi/xapi||stunnel] =
get_reusable_stunnel: Found non-reusable stunnel in the cache. =
disconnecting from 10.50.128.21:443<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221073 UNIX /var/xapi/xapi||stunnel] =
get_reusable_stunnel: stunnel cache is empty; creating a fresh =
connection to 10.50.128.21:443<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|214513 INET 0.0.0.0:80|SR.scan =
R:eb94a1324f62|taskhelper] forwarded task =
destroyed<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221073 UNIX /var/xapi/xapi||xmlrpc_client] stunnel =
pid: 26292 (cached =3D true) connected to =
10.50.128.21:443<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221073 UNIX /var/xapi/xapi||xmlrpc_client] =
with_recorded_stunnelpid task_opt=3DNone =
s_pid=3D26292<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221073 UNIX /var/xapi/xapi||xmlrpc_client] stunnel =
pid: 26292 (cached =3D true) returned stunnel to =
cache<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221074 UNIX /var/xapi/xapi||mscgen] xapi=3D&gt;xapi =
[label=3D&quot;(XML)&quot;];<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221074 UNIX /var/xapi/xapi||stunnel] =
check_reusable: caught exception Unix.Unix_error(31, &quot;write&quot;, =
&quot;&quot;); assuming not reusable<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221074 UNIX /var/xapi/xapi||stunnel] =
get_reusable_stunnel: Found non-reusable stunnel in the cache. =
disconnecting from 10.50.128.21:443<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221074 UNIX /var/xapi/xapi||stunnel] =
get_reusable_stunnel: stunnel cache is empty; creating a fresh =
connection to 10.50.128.21:443<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221074 UNIX /var/xapi/xapi||xmlrpc_client] =
stunnel pid: 26297 (cached =3D true) connected to =
10.50.128.21:443<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221074 UNIX /var/xapi/xapi||xmlrpc_client] =
with_recorded_stunnelpid task_opt=3DNone =
s_pid=3D26297<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221074 UNIX /var/xapi/xapi||xmlrpc_client] stunnel =
pid: 26297 (cached =3D true) returned stunnel to =
cache<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221075 UNIX /var/xapi/xapi||mscgen] xapi=3D&gt;xapi =
[label=3D&quot;(XML)&quot;];<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221075 UNIX /var/xapi/xapi||stunnel] =
check_reusable: caught exception Unix.Unix_error(31, &quot;write&quot;, =
&quot;&quot;); assuming not reusable<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221075 UNIX /var/xapi/xapi||stunnel] =
get_reusable_stunnel: Found non-reusable stunnel in the cache. =
disconnecting from 10.50.128.21:443<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221075 UNIX /var/xapi/xapi||stunnel] =
get_reusable_stunnel: stunnel cache is empty; creating a fresh =
connection to 10.50.128.21:443<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221075 UNIX /var/xapi/xapi||xmlrpc_client] =
stunnel pid: 26302 (cached =3D true) connected to =
10.50.128.21:443<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221075 UNIX /var/xapi/xapi||xmlrpc_client] =
with_recorded_stunnelpid task_opt=3DNone =
s_pid=3D26302<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221075 UNIX /var/xapi/xapi||xmlrpc_client] stunnel =
pid: 26302 (cached =3D true) returned stunnel to =
cache<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>The only mention I found in internet didn&#8217;t give me a =
clue.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Still, cluster works fine, I&#8217;m just worried if =
there&#8217;s a bug somewhere deeper then I see and it can cause some =
problems<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'mso-fareast-language:RU'>Regards, =
<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:RU'>Ivan Derbenev<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_02EF_01CF9BA4.2818F5E0--



--===============0322844046018217455==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--===============0322844046018217455==--



From xen-api-bounces@lists.xen.org Wed Jul 09 14:32:52 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 09 Jul 2014 14:32:52 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X4svK-0008AJ-OZ; Wed, 09 Jul 2014 14:32:42 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <dobropalka@gmail.com>) id 1X4svI-0008AE-O2
	for xen-api@lists.xen.org; Wed, 09 Jul 2014 14:32:41 +0000
Received: from [85.158.143.35:48256] by server-3.bemta-4.messagelabs.com id
	84/B3-16194-8825DB35; Wed, 09 Jul 2014 14:32:40 +0000
X-Env-Sender: dobropalka@gmail.com
X-Msg-Ref: server-8.tower-21.messagelabs.com!1404916357!16849594!1
X-Originating-IP: [209.85.217.181]
X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_14,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 23939 invoked from network); 9 Jul 2014 14:32:38 -0000
Received: from mail-lb0-f181.google.com (HELO mail-lb0-f181.google.com)
	(209.85.217.181)
	by server-8.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	9 Jul 2014 14:32:38 -0000
Received: by mail-lb0-f181.google.com with SMTP id p9so5021603lbv.40
	for <xen-api@lists.xen.org>; Wed, 09 Jul 2014 07:32:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=from:to:references:in-reply-to:subject:date:message-id:mime-version
	:content-type:thread-index:content-language;
	bh=VfmS/01wvzKHPAGflS5LpQ5QcfbttGTet5MOWjjaDAA=;
	b=wytMg0aXKHQAIESOvo1jvIZO58dmGxumtMYm3bVcTjxaY+cJG1zHUxVbx7xgJWgM+/
	jvceZmqfodeo2pLHcZYNZOI3SZyZEAQHwMIYaA5Gs5ApJBDSnGrdSUDb8qjizxvAjkiL
	yCECi1Ft5P2huURtgfm5aF7iu0nXJ6Z5lb0Z1cjuYulshg1MBvDe+B4fU8neaSoLwy6h
	i7y9DPMI2aBs50aJ9j42dj6iqVn7+9yENaKWemwBwIzCBRWRkv0y890E9OgmliQEUcvw
	yua4zyzKVqQF3XVgBXnowNhxWWWWmBdUJLTBJrd8kRnKaanFH4ML5RWZcBjZ+C4gyebl
	qdjw==
X-Received: by 10.152.42.172 with SMTP id p12mr2231022lal.61.1404916357735;
	Wed, 09 Jul 2014 07:32:37 -0700 (PDT)
Received: from RUIT06 ([217.23.88.19])
	by mx.google.com with ESMTPSA id q8sm60875087lbr.28.2014.07.09.07.32.36
	for <multiple recipients>
	(version=TLSv1.2 cipher=ECDHE-RSA-AES128-SHA bits=128/128);
	Wed, 09 Jul 2014 07:32:36 -0700 (PDT)
From: "dobropalka" <dobropalka@gmail.com>
To: "'Jonathan Ludlam'" <Jonathan.Ludlam@citrix.com>, <xen-api@lists.xen.org>
References: <01e901cf9860$935928d0$ba0b7a70$@gmail.com>
	<660D43EB050DE94AACCFA0BB1489A98278C04F@AMSPEX01CL01.citrite.net>
In-Reply-To: <660D43EB050DE94AACCFA0BB1489A98278C04F@AMSPEX01CL01.citrite.net>
Date: Wed, 9 Jul 2014 18:32:35 +0400
Message-ID: <02ee01cf9b82$a104bdd0$e30e3970$@gmail.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQLDfN62yPVY+SRfe8N+9vPz4GrQigGgVrGumaMIc9A=
Content-Language: ru
Subject: Re: [Xen-API] connection to pool master is buggy
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0322844046018217455=="
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

This is a multipart message in MIME format.

--===============0322844046018217455==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_02EF_01CF9BA4.2818F5E0"
Content-Language: ru

This is a multipart message in MIME format.

------=_NextPart_000_02EF_01CF9BA4.2818F5E0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Well, thanks for info. Actually, due to these messages it's hard to look
through logs.

Glad that it will be fixed

 

From: Jonathan Ludlam [mailto:Jonathan.Ludlam@citrix.com] 
Sent: Monday, July 7, 2014 2:50 PM
To: 'dobropalka'; xen-api@lists.xen.org
Subject: RE: [Xen-API] connection to pool master is buggy

 

Hi Ivan,

 

These messages are benign. At some point we'd like to clean up the logging,
as it does tend to be a bit spammy.

 

Cheers,

 

Jon

 

 

From: xen-api-bounces@lists.xen.org <mailto:xen-api-bounces@lists.xen.org>
[mailto:xen-api-bounces@lists.xen.org] On Behalf Of dobropalka
Sent: 05 July 2014 3:51 PM
To: xen-api@lists.xen.org <mailto:xen-api@lists.xen.org> 
Subject: [Xen-API] connection to pool master is buggy

 

Hello, guys!

We got a little pool of 4 xenservers. Everything seems to work fine, but all
my xensource logs are full of these debug messages:

 

Jul  4 08:09:56 cloudstack22 xapi: [ info|cloudstack22|221070 UNIX
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|xapi]
Session.create trackid=d99439bce7424c057acf8204cea45f24 pool=false
uname=root is_local_superuser=true auth_user_sid=
parent=trackid=9834f5af41c964e225f24279aefe4e49

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|mscgen] xapi=>xapi
[label="(XML)"];

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|stunnel]
check_reusable: caught exception Unix.Unix_error(31, "write", ""); assuming
not reusable

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|stunnel]
get_reusable_stunnel: Found non-reusable stunnel in the cache. disconnecting
from 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|stunnel]
get_reusable_stunnel: stunnel cache is empty; creating a fresh connection to
10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [ info|cloudstack22|214513 INET
0.0.0.0:80|sm_exec D:176fe384092b|xapi] Session.destroy
trackid=667f0d1664f406698854c89fe03aca7c

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|xmlrpc_client]
stunnel pid: 26281 (cached = true) connected to 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|xmlrpc_client]
with_recorded_stunnelpid task_opt=None s_pid=26281

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221070 UNIX
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|xmlrpc_client]
stunnel pid: 26281 (cached = true) returned stunnel to cache

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221071 UNIX
/var/xapi/xapi||mscgen] xapi=>xapi [label="(XML)"];

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221071 UNIX
/var/xapi/xapi||xmlrpc_client] stunnel pid: 26281 (cached = true) connected
to 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221071 UNIX
/var/xapi/xapi||xmlrpc_client] with_recorded_stunnelpid task_opt=None
s_pid=26281

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221071 UNIX
/var/xapi/xapi||xmlrpc_client] stunnel pid: 26281 (cached = true) returned
stunnel to cache

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX
/var/xapi/xapi||mscgen] xapi=>xapi [label="(XML)"];

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX
/var/xapi/xapi||stunnel] check_reusable: caught exception
Unix.Unix_error(31, "write", ""); assuming not reusable

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX
/var/xapi/xapi||stunnel] get_reusable_stunnel: Found non-reusable stunnel in
the cache. disconnecting from 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX
/var/xapi/xapi||stunnel] get_reusable_stunnel: stunnel cache is empty;
creating a fresh connection to 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX
/var/xapi/xapi||xmlrpc_client] stunnel pid: 26287 (cached = true) connected
to 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX
/var/xapi/xapi||xmlrpc_client] with_recorded_stunnelpid task_opt=None
s_pid=26287

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221072 UNIX
/var/xapi/xapi||xmlrpc_client] stunnel pid: 26287 (cached = true) returned
stunnel to cache

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX
/var/xapi/xapi||mscgen] xapi=>xapi [label="(XML)"];

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX
/var/xapi/xapi||stunnel] check_reusable: caught exception
Unix.Unix_error(31, "write", ""); assuming not reusable

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX
/var/xapi/xapi||stunnel] get_reusable_stunnel: Found non-reusable stunnel in
the cache. disconnecting from 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX
/var/xapi/xapi||stunnel] get_reusable_stunnel: stunnel cache is empty;
creating a fresh connection to 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|214513 INET
0.0.0.0:80|SR.scan R:eb94a1324f62|taskhelper] forwarded task destroyed

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX
/var/xapi/xapi||xmlrpc_client] stunnel pid: 26292 (cached = true) connected
to 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX
/var/xapi/xapi||xmlrpc_client] with_recorded_stunnelpid task_opt=None
s_pid=26292

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221073 UNIX
/var/xapi/xapi||xmlrpc_client] stunnel pid: 26292 (cached = true) returned
stunnel to cache

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX
/var/xapi/xapi||mscgen] xapi=>xapi [label="(XML)"];

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX
/var/xapi/xapi||stunnel] check_reusable: caught exception
Unix.Unix_error(31, "write", ""); assuming not reusable

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX
/var/xapi/xapi||stunnel] get_reusable_stunnel: Found non-reusable stunnel in
the cache. disconnecting from 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX
/var/xapi/xapi||stunnel] get_reusable_stunnel: stunnel cache is empty;
creating a fresh connection to 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX
/var/xapi/xapi||xmlrpc_client] stunnel pid: 26297 (cached = true) connected
to 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX
/var/xapi/xapi||xmlrpc_client] with_recorded_stunnelpid task_opt=None
s_pid=26297

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221074 UNIX
/var/xapi/xapi||xmlrpc_client] stunnel pid: 26297 (cached = true) returned
stunnel to cache

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX
/var/xapi/xapi||mscgen] xapi=>xapi [label="(XML)"];

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX
/var/xapi/xapi||stunnel] check_reusable: caught exception
Unix.Unix_error(31, "write", ""); assuming not reusable

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX
/var/xapi/xapi||stunnel] get_reusable_stunnel: Found non-reusable stunnel in
the cache. disconnecting from 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX
/var/xapi/xapi||stunnel] get_reusable_stunnel: stunnel cache is empty;
creating a fresh connection to 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX
/var/xapi/xapi||xmlrpc_client] stunnel pid: 26302 (cached = true) connected
to 10.50.128.21:443

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX
/var/xapi/xapi||xmlrpc_client] with_recorded_stunnelpid task_opt=None
s_pid=26302

Jul  4 08:09:56 cloudstack22 xapi: [debug|cloudstack22|221075 UNIX
/var/xapi/xapi||xmlrpc_client] stunnel pid: 26302 (cached = true) returned
stunnel to cache

 

The only mention I found in internet didn't give me a clue.

Still, cluster works fine, I'm just worried if there's a bug somewhere
deeper then I see and it can cause some problems

 

Regards, 

Ivan Derbenev

 


------=_NextPart_000_02EF_01CF9BA4.2818F5E0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 15 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:2.0cm 42.5pt 2.0cm 3.0cm;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DRU =
link=3D"#0563C1" vlink=3D"#954F72"><div class=3DWordSection1><p =
class=3DMsoNormal><span lang=3DEN-US style=3D'color:#1F497D'>Well, =
thanks for info. Actually, due to these messages it&#8217;s hard to look =
through logs.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'color:#1F497D'>Glad that it will be =
fixed<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm'><p class=3DMsoNormal><b><span =
style=3D'mso-fareast-language:RU'>From:</span></b><span =
style=3D'mso-fareast-language:RU'> Jonathan Ludlam =
[mailto:Jonathan.Ludlam@citrix.com] <br><b>Sent:</b> Monday, July 7, =
2014 2:50 PM<br><b>To:</b> 'dobropalka'; =
xen-api@lists.xen.org<br><b>Subject:</b> RE: [Xen-API] connection to =
pool master is buggy<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
lang=3DEN-GB style=3D'color:#1F497D'>Hi Ivan,<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB style=3D'color:#1F497D'>These =
messages are benign. At some point we&#8217;d like to clean up the =
logging, as it does tend to be a bit spammy.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB =
style=3D'color:#1F497D'>Cheers,<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB =
style=3D'color:#1F497D'>Jon<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'><p class=3DMsoNormal><b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-l=
anguage:ZH-CN'>From:</span></b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-l=
anguage:ZH-CN'> <a =
href=3D"mailto:xen-api-bounces@lists.xen.org">xen-api-bounces@lists.xen.o=
rg</a> [<a =
href=3D"mailto:xen-api-bounces@lists.xen.org">mailto:xen-api-bounces@list=
s.xen.org</a>] <b>On Behalf Of </b>dobropalka<br><b>Sent:</b> 05 July =
2014 3:51 PM<br><b>To:</b> <a =
href=3D"mailto:xen-api@lists.xen.org">xen-api@lists.xen.org</a><br><b>Sub=
ject:</b> [Xen-API] connection to pool master is =
buggy<o:p></o:p></span></p></div></div><p class=3DMsoNormal><span =
lang=3DEN-GB><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><span lang=3DEN-US>Hello, =
guys!<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US>We =
got a little pool of 4 xenservers. Everything seems to work fine, but =
all my xensource logs are full of these debug =
messages:<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 xapi: [ =
info|cloudstack22|221070 UNIX /var/xapi/xapi|session.login_with_password =
D:9579fb00c72a|xapi] Session.create =
trackid=3Dd99439bce7424c057acf8204cea45f24 pool=3Dfalse uname=3Droot =
is_local_superuser=3Dtrue auth_user_sid=3D =
parent=3Dtrackid=3D9834f5af41c964e225f24279aefe4e49<o:p></o:p></span></p>=
<p class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 =
cloudstack22 xapi: [debug|cloudstack22|221070 UNIX =
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|mscgen] =
xapi=3D&gt;xapi [label=3D&quot;(XML)&quot;];<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221070 UNIX =
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|stunnel] =
check_reusable: caught exception Unix.Unix_error(31, &quot;write&quot;, =
&quot;&quot;); assuming not reusable<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221070 UNIX =
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|stunnel] =
get_reusable_stunnel: Found non-reusable stunnel in the cache. =
disconnecting from 10.50.128.21:443<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221070 UNIX =
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|stunnel] =
get_reusable_stunnel: stunnel cache is empty; creating a fresh =
connection to 10.50.128.21:443<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [ info|cloudstack22|214513 INET 0.0.0.0:80|sm_exec =
D:176fe384092b|xapi] Session.destroy =
trackid=3D667f0d1664f406698854c89fe03aca7c<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221070 UNIX =
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|xmlrpc_client] =
stunnel pid: 26281 (cached =3D true) connected to =
10.50.128.21:443<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221070 UNIX =
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|xmlrpc_client] =
with_recorded_stunnelpid task_opt=3DNone =
s_pid=3D26281<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221070 UNIX =
/var/xapi/xapi|session.login_with_password D:9579fb00c72a|xmlrpc_client] =
stunnel pid: 26281 (cached =3D true) returned stunnel to =
cache<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221071 UNIX /var/xapi/xapi||mscgen] xapi=3D&gt;xapi =
[label=3D&quot;(XML)&quot;];<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221071 UNIX /var/xapi/xapi||xmlrpc_client] =
stunnel pid: 26281 (cached =3D true) connected to =
10.50.128.21:443<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221071 UNIX /var/xapi/xapi||xmlrpc_client] =
with_recorded_stunnelpid task_opt=3DNone =
s_pid=3D26281<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221071 UNIX /var/xapi/xapi||xmlrpc_client] stunnel =
pid: 26281 (cached =3D true) returned stunnel to =
cache<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221072 UNIX /var/xapi/xapi||mscgen] xapi=3D&gt;xapi =
[label=3D&quot;(XML)&quot;];<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221072 UNIX /var/xapi/xapi||stunnel] =
check_reusable: caught exception Unix.Unix_error(31, &quot;write&quot;, =
&quot;&quot;); assuming not reusable<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221072 UNIX /var/xapi/xapi||stunnel] =
get_reusable_stunnel: Found non-reusable stunnel in the cache. =
disconnecting from 10.50.128.21:443<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221072 UNIX /var/xapi/xapi||stunnel] =
get_reusable_stunnel: stunnel cache is empty; creating a fresh =
connection to 10.50.128.21:443<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221072 UNIX /var/xapi/xapi||xmlrpc_client] =
stunnel pid: 26287 (cached =3D true) connected to =
10.50.128.21:443<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221072 UNIX /var/xapi/xapi||xmlrpc_client] =
with_recorded_stunnelpid task_opt=3DNone =
s_pid=3D26287<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221072 UNIX /var/xapi/xapi||xmlrpc_client] stunnel =
pid: 26287 (cached =3D true) returned stunnel to =
cache<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221073 UNIX /var/xapi/xapi||mscgen] xapi=3D&gt;xapi =
[label=3D&quot;(XML)&quot;];<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221073 UNIX /var/xapi/xapi||stunnel] =
check_reusable: caught exception Unix.Unix_error(31, &quot;write&quot;, =
&quot;&quot;); assuming not reusable<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221073 UNIX /var/xapi/xapi||stunnel] =
get_reusable_stunnel: Found non-reusable stunnel in the cache. =
disconnecting from 10.50.128.21:443<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221073 UNIX /var/xapi/xapi||stunnel] =
get_reusable_stunnel: stunnel cache is empty; creating a fresh =
connection to 10.50.128.21:443<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|214513 INET 0.0.0.0:80|SR.scan =
R:eb94a1324f62|taskhelper] forwarded task =
destroyed<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221073 UNIX /var/xapi/xapi||xmlrpc_client] stunnel =
pid: 26292 (cached =3D true) connected to =
10.50.128.21:443<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221073 UNIX /var/xapi/xapi||xmlrpc_client] =
with_recorded_stunnelpid task_opt=3DNone =
s_pid=3D26292<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221073 UNIX /var/xapi/xapi||xmlrpc_client] stunnel =
pid: 26292 (cached =3D true) returned stunnel to =
cache<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221074 UNIX /var/xapi/xapi||mscgen] xapi=3D&gt;xapi =
[label=3D&quot;(XML)&quot;];<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221074 UNIX /var/xapi/xapi||stunnel] =
check_reusable: caught exception Unix.Unix_error(31, &quot;write&quot;, =
&quot;&quot;); assuming not reusable<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221074 UNIX /var/xapi/xapi||stunnel] =
get_reusable_stunnel: Found non-reusable stunnel in the cache. =
disconnecting from 10.50.128.21:443<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221074 UNIX /var/xapi/xapi||stunnel] =
get_reusable_stunnel: stunnel cache is empty; creating a fresh =
connection to 10.50.128.21:443<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221074 UNIX /var/xapi/xapi||xmlrpc_client] =
stunnel pid: 26297 (cached =3D true) connected to =
10.50.128.21:443<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221074 UNIX /var/xapi/xapi||xmlrpc_client] =
with_recorded_stunnelpid task_opt=3DNone =
s_pid=3D26297<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221074 UNIX /var/xapi/xapi||xmlrpc_client] stunnel =
pid: 26297 (cached =3D true) returned stunnel to =
cache<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221075 UNIX /var/xapi/xapi||mscgen] xapi=3D&gt;xapi =
[label=3D&quot;(XML)&quot;];<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221075 UNIX /var/xapi/xapi||stunnel] =
check_reusable: caught exception Unix.Unix_error(31, &quot;write&quot;, =
&quot;&quot;); assuming not reusable<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221075 UNIX /var/xapi/xapi||stunnel] =
get_reusable_stunnel: Found non-reusable stunnel in the cache. =
disconnecting from 10.50.128.21:443<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221075 UNIX /var/xapi/xapi||stunnel] =
get_reusable_stunnel: stunnel cache is empty; creating a fresh =
connection to 10.50.128.21:443<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 =
xapi: [debug|cloudstack22|221075 UNIX /var/xapi/xapi||xmlrpc_client] =
stunnel pid: 26302 (cached =3D true) connected to =
10.50.128.21:443<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221075 UNIX /var/xapi/xapi||xmlrpc_client] =
with_recorded_stunnelpid task_opt=3DNone =
s_pid=3D26302<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Jul&nbsp; 4 08:09:56 cloudstack22 xapi: =
[debug|cloudstack22|221075 UNIX /var/xapi/xapi||xmlrpc_client] stunnel =
pid: 26302 (cached =3D true) returned stunnel to =
cache<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>The only mention I found in internet didn&#8217;t give me a =
clue.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Still, cluster works fine, I&#8217;m just worried if =
there&#8217;s a bug somewhere deeper then I see and it can cause some =
problems<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'mso-fareast-language:RU'>Regards, =
<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:RU'>Ivan Derbenev<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_02EF_01CF9BA4.2818F5E0--



--===============0322844046018217455==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--===============0322844046018217455==--



From xen-api-bounces@lists.xen.org Wed Jul 09 15:14:20 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 09 Jul 2014 15:14:20 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X4tZZ-0002Ai-QQ; Wed, 09 Jul 2014 15:14:17 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <lars.kurth.xen@gmail.com>)
	id 1X4tZY-0002AI-Di; Wed, 09 Jul 2014 15:14:16 +0000
Received: from [85.158.143.35:46762] by server-1.bemta-4.messagelabs.com id
	48/39-09496-74C5DB35; Wed, 09 Jul 2014 15:14:15 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-10.tower-21.messagelabs.com!1404918855!16892541!1
X-Originating-IP: [74.125.82.42]
X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 18327 invoked from network); 9 Jul 2014 15:14:15 -0000
Received: from mail-wg0-f42.google.com (HELO mail-wg0-f42.google.com)
	(74.125.82.42)
	by server-10.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	9 Jul 2014 15:14:15 -0000
Received: by mail-wg0-f42.google.com with SMTP id l18so711598wgh.13
	for <multiple recipients>; Wed, 09 Jul 2014 08:14:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=sender:message-id:date:from:reply-to:user-agent:mime-version:to
	:subject:content-type:content-transfer-encoding;
	bh=3ey3LshR9w1GjjEJDmQb9uUhMk4xQCEKuW3AQhnQsAg=;
	b=WcwIZ4LijDDywlxNwksR3H91aKYXCoa+eUkxdDqp4FcGMDozdJLlZown80Kat8G3UU
	Eoq7Ou9Rhee4N7OiTbo8jYiCKbH6eqx5164xYQAIYzD1nUsVnecTygchaA414En5CCu4
	ao73XkofFphEhdgVr0776LovIYDidwioN1CNEvNHV+3MRBFwhULo9rvlMHnTNoArVb53
	uOuZUG+LjlnbQFVmdzlhqdkBkP42nWCA32960caKC3hYp7ptpVnnI1KZdAYwQonNE46s
	e5ek0TKDlpM8Pvzfw0J/7OhRAj8BAxdQ1fzJgF0QSOfvNeZsFryBTZhia7J8qTBWzhzx
	tT0g==
X-Received: by 10.194.158.101 with SMTP id wt5mr3969815wjb.136.1404918854916; 
	Wed, 09 Jul 2014 08:14:14 -0700 (PDT)
Received: from [172.16.25.10] (97e5a05a.skybroadband.com. [151.229.160.90])
	by mx.google.com with ESMTPSA id d4sm11782883wiy.13.2014.07.09.08.14.13
	for <multiple recipients>
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Wed, 09 Jul 2014 08:14:14 -0700 (PDT)
Message-ID: <53BD5C45.807@xen.org>
Date: Wed, 09 Jul 2014 16:14:13 +0100
From: Lars Kurth <lars.kurth@xen.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>, 
	"xen-api@lists.xen.org" <xen-api@lists.xen.org>,
	"mirageos-devel@lists.xenproject.org" <mirageos-devel@lists.xenproject.org>
Subject: [Xen-API] [Input Needed] GitDM Config files & privacy
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

Hi all,

I was in the process of publishing GitDM including config files in my 
personal xenbits repository, such that other community members can run 
contribution stats. However the config files contain email addresses and 
thus there may be a potential privacy issue. Config files contain
* e-mail domain to employer mappings
* some e-mail address to employer mappings
* email address aliases mappings
* email address to name mappings (for acknowledgements)

Most of the information in them are public in the first place (i.e. they 
are available from git logs and mailing lists).

I know that open source foundations such as OpenStack publish their 
GitDM config files and I also found some other ones flying around.

But before I publish anything I did want to check whether there are 
objections.

Regards
Lars

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

From xen-api-bounces@lists.xen.org Wed Jul 09 15:14:20 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 09 Jul 2014 15:14:20 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X4tZZ-0002Ai-QQ; Wed, 09 Jul 2014 15:14:17 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <lars.kurth.xen@gmail.com>)
	id 1X4tZY-0002AI-Di; Wed, 09 Jul 2014 15:14:16 +0000
Received: from [85.158.143.35:46762] by server-1.bemta-4.messagelabs.com id
	48/39-09496-74C5DB35; Wed, 09 Jul 2014 15:14:15 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-10.tower-21.messagelabs.com!1404918855!16892541!1
X-Originating-IP: [74.125.82.42]
X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 18327 invoked from network); 9 Jul 2014 15:14:15 -0000
Received: from mail-wg0-f42.google.com (HELO mail-wg0-f42.google.com)
	(74.125.82.42)
	by server-10.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	9 Jul 2014 15:14:15 -0000
Received: by mail-wg0-f42.google.com with SMTP id l18so711598wgh.13
	for <multiple recipients>; Wed, 09 Jul 2014 08:14:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=sender:message-id:date:from:reply-to:user-agent:mime-version:to
	:subject:content-type:content-transfer-encoding;
	bh=3ey3LshR9w1GjjEJDmQb9uUhMk4xQCEKuW3AQhnQsAg=;
	b=WcwIZ4LijDDywlxNwksR3H91aKYXCoa+eUkxdDqp4FcGMDozdJLlZown80Kat8G3UU
	Eoq7Ou9Rhee4N7OiTbo8jYiCKbH6eqx5164xYQAIYzD1nUsVnecTygchaA414En5CCu4
	ao73XkofFphEhdgVr0776LovIYDidwioN1CNEvNHV+3MRBFwhULo9rvlMHnTNoArVb53
	uOuZUG+LjlnbQFVmdzlhqdkBkP42nWCA32960caKC3hYp7ptpVnnI1KZdAYwQonNE46s
	e5ek0TKDlpM8Pvzfw0J/7OhRAj8BAxdQ1fzJgF0QSOfvNeZsFryBTZhia7J8qTBWzhzx
	tT0g==
X-Received: by 10.194.158.101 with SMTP id wt5mr3969815wjb.136.1404918854916; 
	Wed, 09 Jul 2014 08:14:14 -0700 (PDT)
Received: from [172.16.25.10] (97e5a05a.skybroadband.com. [151.229.160.90])
	by mx.google.com with ESMTPSA id d4sm11782883wiy.13.2014.07.09.08.14.13
	for <multiple recipients>
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Wed, 09 Jul 2014 08:14:14 -0700 (PDT)
Message-ID: <53BD5C45.807@xen.org>
Date: Wed, 09 Jul 2014 16:14:13 +0100
From: Lars Kurth <lars.kurth@xen.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>, 
	"xen-api@lists.xen.org" <xen-api@lists.xen.org>,
	"mirageos-devel@lists.xenproject.org" <mirageos-devel@lists.xenproject.org>
Subject: [Xen-API] [Input Needed] GitDM Config files & privacy
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

Hi all,

I was in the process of publishing GitDM including config files in my 
personal xenbits repository, such that other community members can run 
contribution stats. However the config files contain email addresses and 
thus there may be a potential privacy issue. Config files contain
* e-mail domain to employer mappings
* some e-mail address to employer mappings
* email address aliases mappings
* email address to name mappings (for acknowledgements)

Most of the information in them are public in the first place (i.e. they 
are available from git logs and mailing lists).

I know that open source foundations such as OpenStack publish their 
GitDM config files and I also found some other ones flying around.

But before I publish anything I did want to check whether there are 
objections.

Regards
Lars

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

From xen-api-bounces@lists.xen.org Thu Jul 10 16:41:00 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 10 Jul 2014 16:41:00 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X5HOv-0002lb-QF; Thu, 10 Jul 2014 16:40:53 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <Ian.Campbell@citrix.com>)
	id 1X5HOu-0002lI-6o; Thu, 10 Jul 2014 16:40:52 +0000
Received: from [193.109.254.147:64719] by server-3.bemta-14.messagelabs.com id
	D0/CB-13460-312CEB35; Thu, 10 Jul 2014 16:40:51 +0000
X-Env-Sender: Ian.Campbell@citrix.com
X-Msg-Ref: server-12.tower-27.messagelabs.com!1405010444!16702051!2
X-Originating-IP: [66.165.176.89]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 25987 invoked from network); 10 Jul 2014 16:40:50 -0000
Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89)
	by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	10 Jul 2014 16:40:50 -0000
X-IronPort-AV: E=Sophos;i="5.01,638,1400025600"; d="scan'208";a="151455113"
Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net)
	([10.9.154.239])
	by FTLPIPO01.CITRIX.COM with ESMTP; 10 Jul 2014 16:40:26 +0000
Received: from kazak.uk.xensource.com (10.80.2.80) by FTLPEX01CL01.citrite.net
	(10.13.107.78) with Microsoft SMTP Server id 14.3.181.6;
	Thu, 10 Jul 2014 12:40:25 -0400
Message-ID: <1405010424.7406.1.camel@kazak.uk.xensource.com>
From: Ian Campbell <Ian.Campbell@citrix.com>
To: <lars.kurth@xen.org>
Date: Thu, 10 Jul 2014 17:40:24 +0100
In-Reply-To: <53BD5C45.807@xen.org>
References: <53BD5C45.807@xen.org>
Organization: Citrix Systems, Inc.
X-Mailer: Evolution 3.12.2-1 
MIME-Version: 1.0
X-Originating-IP: [10.80.2.80]
X-DLP: MIA1
Cc: "xen-api@lists.xen.org" <xen-api@lists.xen.org>,
	"mirageos-devel@lists.xenproject.org"
	<mirageos-devel@lists.xenproject.org>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [Xen-API] [Xen-devel] [Input Needed] GitDM Config files &
	privacy
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

On Wed, 2014-07-09 at 16:14 +0100, Lars Kurth wrote:
> Hi all,
> 
> I was in the process of publishing GitDM including config files in my 
> personal xenbits repository, such that other community members can run 
> contribution stats. However the config files contain email addresses and 
> thus there may be a potential privacy issue. Config files contain
> * e-mail domain to employer mappings
> * some e-mail address to employer mappings
> * email address aliases mappings
> * email address to name mappings (for acknowledgements)
> 
> Most of the information in them are public in the first place (i.e. they 
> are available from git logs and mailing lists).
> 
> I know that open source foundations such as OpenStack publish their 
> GitDM config files and I also found some other ones flying around.
> 
> But before I publish anything I did want to check whether there are 
> objections.

For stuff gleaned from public info it seems ok.

But for stuff which was taken from private conversations I think you
probably ought to ask if it is ok to share it (and get into the habit of
doing so when you first ask someone who there employer is).

Ian.


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

From xen-api-bounces@lists.xen.org Thu Jul 10 16:41:00 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 10 Jul 2014 16:41:00 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X5HOv-0002lb-QF; Thu, 10 Jul 2014 16:40:53 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <Ian.Campbell@citrix.com>)
	id 1X5HOu-0002lI-6o; Thu, 10 Jul 2014 16:40:52 +0000
Received: from [193.109.254.147:64719] by server-3.bemta-14.messagelabs.com id
	D0/CB-13460-312CEB35; Thu, 10 Jul 2014 16:40:51 +0000
X-Env-Sender: Ian.Campbell@citrix.com
X-Msg-Ref: server-12.tower-27.messagelabs.com!1405010444!16702051!2
X-Originating-IP: [66.165.176.89]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 25987 invoked from network); 10 Jul 2014 16:40:50 -0000
Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89)
	by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	10 Jul 2014 16:40:50 -0000
X-IronPort-AV: E=Sophos;i="5.01,638,1400025600"; d="scan'208";a="151455113"
Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net)
	([10.9.154.239])
	by FTLPIPO01.CITRIX.COM with ESMTP; 10 Jul 2014 16:40:26 +0000
Received: from kazak.uk.xensource.com (10.80.2.80) by FTLPEX01CL01.citrite.net
	(10.13.107.78) with Microsoft SMTP Server id 14.3.181.6;
	Thu, 10 Jul 2014 12:40:25 -0400
Message-ID: <1405010424.7406.1.camel@kazak.uk.xensource.com>
From: Ian Campbell <Ian.Campbell@citrix.com>
To: <lars.kurth@xen.org>
Date: Thu, 10 Jul 2014 17:40:24 +0100
In-Reply-To: <53BD5C45.807@xen.org>
References: <53BD5C45.807@xen.org>
Organization: Citrix Systems, Inc.
X-Mailer: Evolution 3.12.2-1 
MIME-Version: 1.0
X-Originating-IP: [10.80.2.80]
X-DLP: MIA1
Cc: "xen-api@lists.xen.org" <xen-api@lists.xen.org>,
	"mirageos-devel@lists.xenproject.org"
	<mirageos-devel@lists.xenproject.org>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [Xen-API] [Xen-devel] [Input Needed] GitDM Config files &
	privacy
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

On Wed, 2014-07-09 at 16:14 +0100, Lars Kurth wrote:
> Hi all,
> 
> I was in the process of publishing GitDM including config files in my 
> personal xenbits repository, such that other community members can run 
> contribution stats. However the config files contain email addresses and 
> thus there may be a potential privacy issue. Config files contain
> * e-mail domain to employer mappings
> * some e-mail address to employer mappings
> * email address aliases mappings
> * email address to name mappings (for acknowledgements)
> 
> Most of the information in them are public in the first place (i.e. they 
> are available from git logs and mailing lists).
> 
> I know that open source foundations such as OpenStack publish their 
> GitDM config files and I also found some other ones flying around.
> 
> But before I publish anything I did want to check whether there are 
> objections.

For stuff gleaned from public info it seems ok.

But for stuff which was taken from private conversations I think you
probably ought to ask if it is ok to share it (and get into the habit of
doing so when you first ask someone who there employer is).

Ian.


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

From xen-api-bounces@lists.xen.org Mon Jul 14 10:51:28 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Mon, 14 Jul 2014 10:51:28 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X6dqs-0004zp-Fm; Mon, 14 Jul 2014 10:51:22 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <lars.kurth.xen@gmail.com>)
	id 1X6dqr-0004zX-5c; Mon, 14 Jul 2014 10:51:21 +0000
Received: from [193.109.254.147:40442] by server-16.bemta-14.messagelabs.com
	id 65/B6-07101-826B3C35; Mon, 14 Jul 2014 10:51:20 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-4.tower-27.messagelabs.com!1405335079!17319773!1
X-Originating-IP: [74.125.82.180]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 20924 invoked from network); 14 Jul 2014 10:51:19 -0000
Received: from mail-we0-f180.google.com (HELO mail-we0-f180.google.com)
	(74.125.82.180)
	by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	14 Jul 2014 10:51:19 -0000
Received: by mail-we0-f180.google.com with SMTP id k48so2976511wev.25
	for <multiple recipients>; Mon, 14 Jul 2014 03:51:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=sender:message-id:date:from:reply-to:user-agent:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	bh=FMFiq8eWRY9oCqwJEroVSo6GBUR3PvRFwOjO8KhSnDk=;
	b=SFh5OkjzWIwBTz+X4Cw5iL1MYT+0bYuD6x7TdotuGZxB9su5e6ylgh50bIgyQTDvl7
	nVkvO6kbki95H1MnXE3FZtEMfha6LAkvmLUklEuHKsPaIUk9u7JVsbiFd2TT4NNOkbbH
	jKlNCelm+/qErAAGlMwU5lvMxD1e0dNENi380waQEoFTHts2sr0e9WWtLCZ+jN2ZX4JK
	/b55KkUB/8c/jTrQg6dGqlkOhJrSxJLv/uENIIEIhtNbOervN8JbrxPM3rYqZersMiTX
	MamKR0PBZ5UDGuziPOQmb+WNltmCKYN1bUqwRh036rjeDxfjXpJ5cR4k5Cr5qybDyTVd
	Bb1Q==
X-Received: by 10.194.9.198 with SMTP id c6mr2348745wjb.131.1405335079534;
	Mon, 14 Jul 2014 03:51:19 -0700 (PDT)
Received: from [172.16.25.10] (97e5a05a.skybroadband.com. [151.229.160.90])
	by mx.google.com with ESMTPSA id
	w10sm29735554wie.22.2014.07.14.03.51.18 for <multiple recipients>
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Mon, 14 Jul 2014 03:51:18 -0700 (PDT)
Message-ID: <53C3B625.3080607@xen.org>
Date: Mon, 14 Jul 2014 11:51:17 +0100
From: Lars Kurth <lars.kurth@xen.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Ian Campbell <Ian.Campbell@citrix.com>
References: <53B28517.9020807@xen.org>	
	<1404902570.16789.3.camel@kazak.uk.xensource.com>	
	<53BD2756.2070602@xen.org>
	<1404906408.16789.14.camel@kazak.uk.xensource.com>
In-Reply-To: <1404906408.16789.14.camel@kazak.uk.xensource.com>
Cc: Artem Mygaiev <artem.mygaiev@globallogic.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	"mirageos-devel@lists.xenproject.org"
	<mirageos-devel@lists.xenproject.org>,
	"xen-api@lists.xen.org" <xen-api@lists.xen.org>,
	Alex Agizim <alex.agizim@globallogic.com>,
	Andrii Tseglytskyi <andrii.tseglytskyi@globallogic.com>
Subject: Re: [Xen-API] [Xen-devel] [For Community Review] Embedded and
 Automotive PV Drivers Sub-Project Proposal (deadline July 11th)
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

On 09/07/2014 12:46, Ian Campbell wrote:
> On Wed, 2014-07-09 at 12:28 +0100, Lars Kurth wrote:
>
>>> "To build these drivers, the QNX GNU libc variant is used (licensed
>>> under GPL)."
>>>
>>>          Not LGPL? QNX using GPL for it's libc seems like an odd choice
>>>          for them, since it requires anything linking against it to be
>>>          GPL compatible. I suspect this a typo.
>> Corrected
> Just to be clear; I've no idea what license the QNX libc is under, it
> could be GPL for all I know, I was just querying it because it surprised
> me.
>
> (Just want to be sure you didn't assume I know it was LGPL or something)
I did go back and checked it. I tripped over it, as this was thrown into 
a collection with compilers. It needed drilling a level deeper down
Lars

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

From xen-api-bounces@lists.xen.org Mon Jul 14 10:51:28 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Mon, 14 Jul 2014 10:51:28 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X6dqs-0004zp-Fm; Mon, 14 Jul 2014 10:51:22 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <lars.kurth.xen@gmail.com>)
	id 1X6dqr-0004zX-5c; Mon, 14 Jul 2014 10:51:21 +0000
Received: from [193.109.254.147:40442] by server-16.bemta-14.messagelabs.com
	id 65/B6-07101-826B3C35; Mon, 14 Jul 2014 10:51:20 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-4.tower-27.messagelabs.com!1405335079!17319773!1
X-Originating-IP: [74.125.82.180]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 20924 invoked from network); 14 Jul 2014 10:51:19 -0000
Received: from mail-we0-f180.google.com (HELO mail-we0-f180.google.com)
	(74.125.82.180)
	by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	14 Jul 2014 10:51:19 -0000
Received: by mail-we0-f180.google.com with SMTP id k48so2976511wev.25
	for <multiple recipients>; Mon, 14 Jul 2014 03:51:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=sender:message-id:date:from:reply-to:user-agent:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	bh=FMFiq8eWRY9oCqwJEroVSo6GBUR3PvRFwOjO8KhSnDk=;
	b=SFh5OkjzWIwBTz+X4Cw5iL1MYT+0bYuD6x7TdotuGZxB9su5e6ylgh50bIgyQTDvl7
	nVkvO6kbki95H1MnXE3FZtEMfha6LAkvmLUklEuHKsPaIUk9u7JVsbiFd2TT4NNOkbbH
	jKlNCelm+/qErAAGlMwU5lvMxD1e0dNENi380waQEoFTHts2sr0e9WWtLCZ+jN2ZX4JK
	/b55KkUB/8c/jTrQg6dGqlkOhJrSxJLv/uENIIEIhtNbOervN8JbrxPM3rYqZersMiTX
	MamKR0PBZ5UDGuziPOQmb+WNltmCKYN1bUqwRh036rjeDxfjXpJ5cR4k5Cr5qybDyTVd
	Bb1Q==
X-Received: by 10.194.9.198 with SMTP id c6mr2348745wjb.131.1405335079534;
	Mon, 14 Jul 2014 03:51:19 -0700 (PDT)
Received: from [172.16.25.10] (97e5a05a.skybroadband.com. [151.229.160.90])
	by mx.google.com with ESMTPSA id
	w10sm29735554wie.22.2014.07.14.03.51.18 for <multiple recipients>
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Mon, 14 Jul 2014 03:51:18 -0700 (PDT)
Message-ID: <53C3B625.3080607@xen.org>
Date: Mon, 14 Jul 2014 11:51:17 +0100
From: Lars Kurth <lars.kurth@xen.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Ian Campbell <Ian.Campbell@citrix.com>
References: <53B28517.9020807@xen.org>	
	<1404902570.16789.3.camel@kazak.uk.xensource.com>	
	<53BD2756.2070602@xen.org>
	<1404906408.16789.14.camel@kazak.uk.xensource.com>
In-Reply-To: <1404906408.16789.14.camel@kazak.uk.xensource.com>
Cc: Artem Mygaiev <artem.mygaiev@globallogic.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	"mirageos-devel@lists.xenproject.org"
	<mirageos-devel@lists.xenproject.org>,
	"xen-api@lists.xen.org" <xen-api@lists.xen.org>,
	Alex Agizim <alex.agizim@globallogic.com>,
	Andrii Tseglytskyi <andrii.tseglytskyi@globallogic.com>
Subject: Re: [Xen-API] [Xen-devel] [For Community Review] Embedded and
 Automotive PV Drivers Sub-Project Proposal (deadline July 11th)
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

On 09/07/2014 12:46, Ian Campbell wrote:
> On Wed, 2014-07-09 at 12:28 +0100, Lars Kurth wrote:
>
>>> "To build these drivers, the QNX GNU libc variant is used (licensed
>>> under GPL)."
>>>
>>>          Not LGPL? QNX using GPL for it's libc seems like an odd choice
>>>          for them, since it requires anything linking against it to be
>>>          GPL compatible. I suspect this a typo.
>> Corrected
> Just to be clear; I've no idea what license the QNX libc is under, it
> could be GPL for all I know, I was just querying it because it surprised
> me.
>
> (Just want to be sure you didn't assume I know it was LGPL or something)
I did go back and checked it. I tripped over it, as this was thrown into 
a collection with compilers. It needed drilling a level deeper down
Lars

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

From xen-api-bounces@lists.xen.org Mon Jul 14 10:52:43 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Mon, 14 Jul 2014 10:52:43 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X6dsB-0005A1-6n; Mon, 14 Jul 2014 10:52:43 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <lars.kurth.xen@gmail.com>)
	id 1X6dsA-00059p-EC; Mon, 14 Jul 2014 10:52:42 +0000
Received: from [85.158.143.35:28035] by server-1.bemta-4.messagelabs.com id
	83/06-30046-976B3C35; Mon, 14 Jul 2014 10:52:41 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-10.tower-21.messagelabs.com!1405335160!17569832!1
X-Originating-IP: [74.125.82.48]
X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 15933 invoked from network); 14 Jul 2014 10:52:41 -0000
Received: from mail-wg0-f48.google.com (HELO mail-wg0-f48.google.com)
	(74.125.82.48)
	by server-10.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	14 Jul 2014 10:52:41 -0000
Received: by mail-wg0-f48.google.com with SMTP id x13so3866955wgg.31
	for <multiple recipients>; Mon, 14 Jul 2014 03:52:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=sender:message-id:date:from:reply-to:user-agent:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	bh=rOwbujRbSaif4scJPW5ZOjZJKzHV2uTbjAfjAbX9BPM=;
	b=HrM0Px4bfSX/OR+8Pk4EpRQi87RYrrytLD9ZaUKFkNkArUXQbin43qaOCNo9oo94cT
	KuaPE017zOUaIZouFhK3I4y03YN9kIw6FadkpNZLipFLyuEk3nbIrQiqBvVrpks0sNnz
	x6BYUSxeJldngEE1b52ZYiRbr/m1Qe0266zuxsTJt3eS6ue1bAZWPCO1HJBmavSampXZ
	xOTLPY26PXqAK7Qcj8jQ+gZPkeP/ZqM/vnx1H8J7oXiSRSNSSqzepInqBzwz3MXRwpVE
	+qxj/GqMq7ZMT2JK714lgBuENRcI07Q+qxmSlBOY48nC0r3EaYwvPw7a5MSu4XuuzRxP
	o2AA==
X-Received: by 10.180.89.143 with SMTP id bo15mr23250566wib.78.1405335160570; 
	Mon, 14 Jul 2014 03:52:40 -0700 (PDT)
Received: from [172.16.25.10] (97e5a05a.skybroadband.com. [151.229.160.90])
	by mx.google.com with ESMTPSA id h3sm24683997wjz.48.2014.07.14.03.52.39
	for <multiple recipients>
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Mon, 14 Jul 2014 03:52:39 -0700 (PDT)
Message-ID: <53C3B676.8050204@xen.org>
Date: Mon, 14 Jul 2014 11:52:38 +0100
From: Lars Kurth <lars.kurth@xen.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Ian Campbell <Ian.Campbell@citrix.com>
References: <53BD5C45.807@xen.org>
	<1405010424.7406.1.camel@kazak.uk.xensource.com>
In-Reply-To: <1405010424.7406.1.camel@kazak.uk.xensource.com>
Cc: "xen-api@lists.xen.org" <xen-api@lists.xen.org>,
	"mirageos-devel@lists.xenproject.org"
	<mirageos-devel@lists.xenproject.org>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [Xen-API] [Xen-devel] [Input Needed] GitDM Config files &
	privacy
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

On 10/07/2014 17:40, Ian Campbell wrote:
> On Wed, 2014-07-09 at 16:14 +0100, Lars Kurth wrote:
>> Hi all,
>>
>> I was in the process of publishing GitDM including config files in my
>> personal xenbits repository, such that other community members can run
>> contribution stats. However the config files contain email addresses and
>> thus there may be a potential privacy issue. Config files contain
>> * e-mail domain to employer mappings
>> * some e-mail address to employer mappings
>> * email address aliases mappings
>> * email address to name mappings (for acknowledgements)
>>
>> Most of the information in them are public in the first place (i.e. they
>> are available from git logs and mailing lists).
>>
>> I know that open source foundations such as OpenStack publish their
>> GitDM config files and I also found some other ones flying around.
>>
>> But before I publish anything I did want to check whether there are
>> objections.
> For stuff gleaned from public info it seems ok.
My view also
> But for stuff which was taken from private conversations I think you
> probably ought to ask if it is ok to share it (and get into the habit of
> doing so when you first ask someone who there employer is).
Of course the problem I have now is that I can't remember whom I asked.
Agreed on moving forward

Lars

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

From xen-api-bounces@lists.xen.org Mon Jul 14 10:52:43 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Mon, 14 Jul 2014 10:52:43 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X6dsB-0005A1-6n; Mon, 14 Jul 2014 10:52:43 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <lars.kurth.xen@gmail.com>)
	id 1X6dsA-00059p-EC; Mon, 14 Jul 2014 10:52:42 +0000
Received: from [85.158.143.35:28035] by server-1.bemta-4.messagelabs.com id
	83/06-30046-976B3C35; Mon, 14 Jul 2014 10:52:41 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-10.tower-21.messagelabs.com!1405335160!17569832!1
X-Originating-IP: [74.125.82.48]
X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 15933 invoked from network); 14 Jul 2014 10:52:41 -0000
Received: from mail-wg0-f48.google.com (HELO mail-wg0-f48.google.com)
	(74.125.82.48)
	by server-10.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	14 Jul 2014 10:52:41 -0000
Received: by mail-wg0-f48.google.com with SMTP id x13so3866955wgg.31
	for <multiple recipients>; Mon, 14 Jul 2014 03:52:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=sender:message-id:date:from:reply-to:user-agent:mime-version:to:cc
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	bh=rOwbujRbSaif4scJPW5ZOjZJKzHV2uTbjAfjAbX9BPM=;
	b=HrM0Px4bfSX/OR+8Pk4EpRQi87RYrrytLD9ZaUKFkNkArUXQbin43qaOCNo9oo94cT
	KuaPE017zOUaIZouFhK3I4y03YN9kIw6FadkpNZLipFLyuEk3nbIrQiqBvVrpks0sNnz
	x6BYUSxeJldngEE1b52ZYiRbr/m1Qe0266zuxsTJt3eS6ue1bAZWPCO1HJBmavSampXZ
	xOTLPY26PXqAK7Qcj8jQ+gZPkeP/ZqM/vnx1H8J7oXiSRSNSSqzepInqBzwz3MXRwpVE
	+qxj/GqMq7ZMT2JK714lgBuENRcI07Q+qxmSlBOY48nC0r3EaYwvPw7a5MSu4XuuzRxP
	o2AA==
X-Received: by 10.180.89.143 with SMTP id bo15mr23250566wib.78.1405335160570; 
	Mon, 14 Jul 2014 03:52:40 -0700 (PDT)
Received: from [172.16.25.10] (97e5a05a.skybroadband.com. [151.229.160.90])
	by mx.google.com with ESMTPSA id h3sm24683997wjz.48.2014.07.14.03.52.39
	for <multiple recipients>
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Mon, 14 Jul 2014 03:52:39 -0700 (PDT)
Message-ID: <53C3B676.8050204@xen.org>
Date: Mon, 14 Jul 2014 11:52:38 +0100
From: Lars Kurth <lars.kurth@xen.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Ian Campbell <Ian.Campbell@citrix.com>
References: <53BD5C45.807@xen.org>
	<1405010424.7406.1.camel@kazak.uk.xensource.com>
In-Reply-To: <1405010424.7406.1.camel@kazak.uk.xensource.com>
Cc: "xen-api@lists.xen.org" <xen-api@lists.xen.org>,
	"mirageos-devel@lists.xenproject.org"
	<mirageos-devel@lists.xenproject.org>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [Xen-API] [Xen-devel] [Input Needed] GitDM Config files &
	privacy
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: lars.kurth@xen.org
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

On 10/07/2014 17:40, Ian Campbell wrote:
> On Wed, 2014-07-09 at 16:14 +0100, Lars Kurth wrote:
>> Hi all,
>>
>> I was in the process of publishing GitDM including config files in my
>> personal xenbits repository, such that other community members can run
>> contribution stats. However the config files contain email addresses and
>> thus there may be a potential privacy issue. Config files contain
>> * e-mail domain to employer mappings
>> * some e-mail address to employer mappings
>> * email address aliases mappings
>> * email address to name mappings (for acknowledgements)
>>
>> Most of the information in them are public in the first place (i.e. they
>> are available from git logs and mailing lists).
>>
>> I know that open source foundations such as OpenStack publish their
>> GitDM config files and I also found some other ones flying around.
>>
>> But before I publish anything I did want to check whether there are
>> objections.
> For stuff gleaned from public info it seems ok.
My view also
> But for stuff which was taken from private conversations I think you
> probably ought to ask if it is ok to share it (and get into the habit of
> doing so when you first ask someone who there employer is).
Of course the problem I have now is that I can't remember whom I asked.
Agreed on moving forward

Lars

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

From xen-api-bounces@lists.xen.org Tue Jul 15 11:21:49 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 15 Jul 2014 11:21:49 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X70nj-0007Dr-P7; Tue, 15 Jul 2014 11:21:39 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <lars.kurth.xen@gmail.com>)
	id 1X70ni-0007DV-Nl; Tue, 15 Jul 2014 11:21:38 +0000
Received: from [193.109.254.147:64163] by server-9.bemta-14.messagelabs.com id
	80/91-14237-1CE05C35; Tue, 15 Jul 2014 11:21:37 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-3.tower-27.messagelabs.com!1405423297!17454348!1
X-Originating-IP: [74.125.82.180]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 23111 invoked from network); 15 Jul 2014 11:21:37 -0000
Received: from mail-we0-f180.google.com (HELO mail-we0-f180.google.com)
	(74.125.82.180)
	by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	15 Jul 2014 11:21:37 -0000
Received: by mail-we0-f180.google.com with SMTP id k48so4559047wev.39
	for <multiple recipients>; Tue, 15 Jul 2014 04:21:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=sender:message-id:date:from:reply-to:user-agent:mime-version:to:cc
	:subject:content-type:content-transfer-encoding;
	bh=7GyL7B6nlFKp3yyz8gv9RmhsTMCbaaB/NgEdrNdMF8I=;
	b=YkQnpktnNdvDY33s17/yXh/OU2FiVz1c+gZqjKCM2meukUSZJwKPcjL2aLAnb0KdUb
	RTUmaooxlrMoWnjOyJfPNgq9cCSc4sF4cOlI6zNjaXe9/7Cn5KGAe61HFNjaZdKmu5BL
	JsSRwiO3+RKmf/z7Mqqf2r67Z2iBAtdBUNAg59Ev5bDqS1iqrFO8kDl6ozLtumezVnVE
	sZ18kWWqCk/jT96/Ob0Klwqby1W5tMRZtSgjUVucHY1K9US5RNFU0iVL0hIyNPQuqgUn
	k0eEFRROyOwCg7MT4CGRtyuSacoexYim0Fw+j6OGNqiBDdZOmIUxtM7Vcw+J13YiEHIZ
	K81g==
X-Received: by 10.180.95.136 with SMTP id dk8mr4921475wib.8.1405423296862;
	Tue, 15 Jul 2014 04:21:36 -0700 (PDT)
Received: from [172.16.25.10] (97e5a05a.skybroadband.com. [151.229.160.90])
	by mx.google.com with ESMTPSA id w5sm42658277wif.3.2014.07.15.04.21.35
	for <multiple recipients>
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Tue, 15 Jul 2014 04:21:35 -0700 (PDT)
Message-ID: <53C50EBE.40107@xen.org>
Date: Tue, 15 Jul 2014 12:21:34 +0100
From: Lars Kurth <lars.kurth@xen.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: xen-devel <xen-devel@lists.xenproject.org>, 
	"xen-api@lists.xenproject.org" <xen-api@lists.xenproject.org>
Cc: advisory-board@lists.xenproject.org,
	Artem Mygaiev <artem.mygaiev@globallogic.com>,
	Alex Agizim <alex.agizim@globallogic.com>
Subject: [Xen-API] [Maintainer vote] Embedded and Automotive PV Drivers
 Project Proposal - closes July 23rd
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: "lars.kurth@xenproject.org" <lars.kurth@xenproject.org>
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

Hi all,

in accordance with http://xenproject.org/governance.html it is time to 
vote on "Embedded and Automotive PV Drivers Project Proposal" (or 
http://wiki.xenproject.org/wiki/Embedded_and_Automotive_PV_Drivers_Project_Proposal). 
The vote is open for a week as usual.

All maintainers of mature Xen Project sub-projects can vote, which 
includes the Hypervisor and XAPI project. The list of eligable people are
* Hypervisor : see 
http://xenbits.xenproject.org/gitweb/?p=xen.git;a=blob;f=MAINTAINERS;hb=HEAD
* XAPI :  see http://xenproject.org/developers/teams/xapi.html, note 
that XAPI PROJECT LEADS & COMMITERS and MAINTAINERS are listed on   
https://github.com/xapi-project/xen-api

If you are in favour, reply "+1" to this thread
If you do not care, reply "0"
If you object, reply "-1" with a comment justifying the objection

Best Regards
Lars

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

From xen-api-bounces@lists.xen.org Tue Jul 15 11:21:49 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 15 Jul 2014 11:21:49 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X70nj-0007Dr-P7; Tue, 15 Jul 2014 11:21:39 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <lars.kurth.xen@gmail.com>)
	id 1X70ni-0007DV-Nl; Tue, 15 Jul 2014 11:21:38 +0000
Received: from [193.109.254.147:64163] by server-9.bemta-14.messagelabs.com id
	80/91-14237-1CE05C35; Tue, 15 Jul 2014 11:21:37 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-3.tower-27.messagelabs.com!1405423297!17454348!1
X-Originating-IP: [74.125.82.180]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 23111 invoked from network); 15 Jul 2014 11:21:37 -0000
Received: from mail-we0-f180.google.com (HELO mail-we0-f180.google.com)
	(74.125.82.180)
	by server-3.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	15 Jul 2014 11:21:37 -0000
Received: by mail-we0-f180.google.com with SMTP id k48so4559047wev.39
	for <multiple recipients>; Tue, 15 Jul 2014 04:21:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=sender:message-id:date:from:reply-to:user-agent:mime-version:to:cc
	:subject:content-type:content-transfer-encoding;
	bh=7GyL7B6nlFKp3yyz8gv9RmhsTMCbaaB/NgEdrNdMF8I=;
	b=YkQnpktnNdvDY33s17/yXh/OU2FiVz1c+gZqjKCM2meukUSZJwKPcjL2aLAnb0KdUb
	RTUmaooxlrMoWnjOyJfPNgq9cCSc4sF4cOlI6zNjaXe9/7Cn5KGAe61HFNjaZdKmu5BL
	JsSRwiO3+RKmf/z7Mqqf2r67Z2iBAtdBUNAg59Ev5bDqS1iqrFO8kDl6ozLtumezVnVE
	sZ18kWWqCk/jT96/Ob0Klwqby1W5tMRZtSgjUVucHY1K9US5RNFU0iVL0hIyNPQuqgUn
	k0eEFRROyOwCg7MT4CGRtyuSacoexYim0Fw+j6OGNqiBDdZOmIUxtM7Vcw+J13YiEHIZ
	K81g==
X-Received: by 10.180.95.136 with SMTP id dk8mr4921475wib.8.1405423296862;
	Tue, 15 Jul 2014 04:21:36 -0700 (PDT)
Received: from [172.16.25.10] (97e5a05a.skybroadband.com. [151.229.160.90])
	by mx.google.com with ESMTPSA id w5sm42658277wif.3.2014.07.15.04.21.35
	for <multiple recipients>
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Tue, 15 Jul 2014 04:21:35 -0700 (PDT)
Message-ID: <53C50EBE.40107@xen.org>
Date: Tue, 15 Jul 2014 12:21:34 +0100
From: Lars Kurth <lars.kurth@xen.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1;
	rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: xen-devel <xen-devel@lists.xenproject.org>, 
	"xen-api@lists.xenproject.org" <xen-api@lists.xenproject.org>
Cc: advisory-board@lists.xenproject.org,
	Artem Mygaiev <artem.mygaiev@globallogic.com>,
	Alex Agizim <alex.agizim@globallogic.com>
Subject: [Xen-API] [Maintainer vote] Embedded and Automotive PV Drivers
 Project Proposal - closes July 23rd
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
Reply-To: "lars.kurth@xenproject.org" <lars.kurth@xenproject.org>
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

Hi all,

in accordance with http://xenproject.org/governance.html it is time to 
vote on "Embedded and Automotive PV Drivers Project Proposal" (or 
http://wiki.xenproject.org/wiki/Embedded_and_Automotive_PV_Drivers_Project_Proposal). 
The vote is open for a week as usual.

All maintainers of mature Xen Project sub-projects can vote, which 
includes the Hypervisor and XAPI project. The list of eligable people are
* Hypervisor : see 
http://xenbits.xenproject.org/gitweb/?p=xen.git;a=blob;f=MAINTAINERS;hb=HEAD
* XAPI :  see http://xenproject.org/developers/teams/xapi.html, note 
that XAPI PROJECT LEADS & COMMITERS and MAINTAINERS are listed on   
https://github.com/xapi-project/xen-api

If you are in favour, reply "+1" to this thread
If you do not care, reply "0"
If you object, reply "-1" with a comment justifying the objection

Best Regards
Lars

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

From xen-api-bounces@lists.xen.org Thu Jul 17 12:49:43 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 17 Jul 2014 12:49:43 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X7l7w-0007i7-Rg; Thu, 17 Jul 2014 12:49:36 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <scott.dj@gmail.com>)
	id 1X7l7v-0007hu-6Q; Thu, 17 Jul 2014 12:49:35 +0000
Received: from [85.158.137.68:28848] by server-14.bemta-3.messagelabs.com id
	BE/E0-09441-E56C7C35; Thu, 17 Jul 2014 12:49:34 +0000
X-Env-Sender: scott.dj@gmail.com
X-Msg-Ref: server-11.tower-31.messagelabs.com!1405601371!16520542!1
X-Originating-IP: [209.85.220.51]
X-SpamReason: No, hits=1.7 required=7.0 tests=BODY_RANDOM_LONG,
	HTML_10_20, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,
	spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 16769 invoked from network); 17 Jul 2014 12:49:33 -0000
Received: from mail-pa0-f51.google.com (HELO mail-pa0-f51.google.com)
	(209.85.220.51)
	by server-11.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	17 Jul 2014 12:49:33 -0000
Received: by mail-pa0-f51.google.com with SMTP id ey11so3334032pad.10
	for <multiple recipients>; Thu, 17 Jul 2014 05:49:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:date:message-id:subject:from:to:content-type;
	bh=vn8Unnass49RyFe293DkQUIR7XxCphmVfcOUV3oJsyE=;
	b=eqiBEK+WyOdkZk9NeUICfmBugYiZjml00Td/9pHbxVO/Fa3pac/fZvvsK80KlXGa0a
	BelVVNSdTJrn4Wbz72CxqSs3LOVms90iqoDm0MUL6+prxRcNXKmDJYgTvDFJshJYEFrw
	5jfBZK9DIpewDcSzEOOzQFLOYmUES0yNMQXjMa8PBI/zgOx5zaYuOf7hkPsB5GiQJ7PT
	0YbiHssrKUJ6lzBILpI1W6UKPZDpKDUqRE9NTHvxGbJwolngT83wjKK7rHRaaXPf/zt4
	0LUSd1JSIJiqcCPHx6xA24g1fdWd9kBfT/H10SiJ9NEq6kJjz7M4bNtlcCaQRY+lBVAb
	4Cfg==
MIME-Version: 1.0
X-Received: by 10.68.252.7 with SMTP id zo7mr27899424pbc.102.1405601371305;
	Thu, 17 Jul 2014 05:49:31 -0700 (PDT)
Received: by 10.70.11.65 with HTTP; Thu, 17 Jul 2014 05:49:31 -0700 (PDT)
Date: Thu, 17 Jul 2014 13:49:31 +0100
Message-ID: <CAG_esB2FAw2pctiPjvhq5-LYsVfMr+u+3E2woTvgXyiS9O8ozg@mail.gmail.com>
From: David Scott <scott.dj@gmail.com>
To: "mirageos-devel@lists.xenproject.org"
	<mirageos-devel@lists.xenproject.org>, xen-api@lists.xenproject.org
Subject: [Xen-API] Xenstore (client) updates
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============3136204823969627155=="
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

--===============3136204823969627155==
Content-Type: multipart/alternative; boundary=047d7b1630af6ebbb904fe631267

--047d7b1630af6ebbb904fe631267
Content-Type: text/plain; charset=UTF-8

Hi,

I've just merged updates to the Mirage Xenstore protocol and client
implementation to master (but not yet released). There are
backwards-incompatible API changes which I'd like to get right before
release, so feedback is welcome. Note the signatures are separate from the
Mirage V2_LWT ones -- this is an internal implementation library used for
Xen Mirage kernels only. I'll not release this code until (a) we're happy
with it; and (b) patches are available for all users in opam (typical users
include Mirage device drivers and Xen toolstacks)

The reasons I'm proposing backwards-incompatible changes are:

1. to hide the 'client' type from clients. Since there should only be one
real Xenstore connection per process (whether Unix domain sockets or shared
memory), this ended up being a singleton. There doesn't seem any point in
requesting the user 'create' and 'manage' these when the library was doing
it all anyway.

2. for transactions and watches, I've made this into a more monadic style.
The examples in the README.md show what I mean.

3. to move away from exceptions (I'm looking at you, ENOENT) and to use
option types. So we now have 'read' and 'read_exn'. Does anyone know of any
other functions whose signatures could be improved?

4. (for a crash-resistant Irmin Xenstore server): there's now control over
where we are in the shared memory ring. Previously a 'read' would 'consume'
data immediately, which would be lost if we crashed. Now 'read' should not
advance the stream, and the server must decide when is appropriate and call
an 'advance' function manually.

A couple of house-keeping items:

* The repo mirage/ocaml-xenstore which contains the Xenstore protocol
implementation and client code used to be a fork of djs55/ocaml-xenstore.
I've fixed this anomaly and now the mirage/ocaml-xenstore version is the
authoritative version.

* The license of the Xenstore protocol code and client is the Mirage
standard (ISC)

* The code has been re-indented with ocp-indent --syntax=lwt (Mirage
standard style?)

Cheers,
-- 
Dave Scott

--047d7b1630af6ebbb904fe631267
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<div><br></div><div>I&#39;ve just merged updates to the=
 Mirage Xenstore protocol and client implementation to master (but not yet =
released). There are backwards-incompatible API changes which I&#39;d like =
to get right before release, so feedback is welcome. Note the signatures ar=
e separate from the Mirage V2_LWT ones -- this is an internal implementatio=
n library used for Xen Mirage kernels only. I&#39;ll not release this code =
until (a) we&#39;re happy with it; and (b) patches are available for all us=
ers in opam (typical users include Mirage device drivers and Xen toolstacks=
)</div>
<div><br></div><div>The reasons I&#39;m proposing backwards-incompatible ch=
anges are:</div><div><br></div><div>1. to hide the &#39;client&#39; type fr=
om clients. Since there should only be one real Xenstore connection per pro=
cess (whether Unix domain sockets or shared memory), this ended up being a =
singleton. There doesn&#39;t seem any point in requesting the user &#39;cre=
ate&#39; and &#39;manage&#39; these when the library was doing it all anywa=
y.</div>
<div><br></div><div>2. for transactions and watches, I&#39;ve made this int=
o a more monadic style. The examples in the README.md show what I mean.</di=
v><div><br></div><div>3. to move away from exceptions (I&#39;m looking at y=
ou, ENOENT) and to use option types. So we now have &#39;read&#39; and &#39=
;read_exn&#39;. Does anyone know of any other functions whose signatures co=
uld be improved?</div>
<div><br></div><div>4. (for a crash-resistant Irmin Xenstore server): there=
&#39;s now control over where we are in the shared memory ring. Previously =
a &#39;read&#39; would &#39;consume&#39; data immediately, which would be l=
ost if we crashed. Now &#39;read&#39; should not advance the stream, and th=
e server must decide when is appropriate and call an &#39;advance&#39; func=
tion manually.</div>
<div><br></div><div>A couple of house-keeping items:</div><div><br></div><d=
iv>* The repo mirage/ocaml-xenstore which contains the Xenstore protocol im=
plementation and client code used to be a fork of djs55/ocaml-xenstore. I&#=
39;ve fixed this anomaly and now the mirage/ocaml-xenstore version is the a=
uthoritative version.</div>
<div><br></div><div>* The license of the Xenstore protocol code and client =
is the Mirage standard (ISC)<br clear=3D"all"><div><br></div><div>* The cod=
e has been re-indented with ocp-indent --syntax=3Dlwt (Mirage standard styl=
e?)</div>
<div><br></div><div>Cheers,</div>-- <br>Dave Scott
</div></div>

--047d7b1630af6ebbb904fe631267--


--===============3136204823969627155==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--===============3136204823969627155==--


From xen-api-bounces@lists.xen.org Thu Jul 17 12:49:43 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 17 Jul 2014 12:49:43 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X7l7w-0007i7-Rg; Thu, 17 Jul 2014 12:49:36 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <scott.dj@gmail.com>)
	id 1X7l7v-0007hu-6Q; Thu, 17 Jul 2014 12:49:35 +0000
Received: from [85.158.137.68:28848] by server-14.bemta-3.messagelabs.com id
	BE/E0-09441-E56C7C35; Thu, 17 Jul 2014 12:49:34 +0000
X-Env-Sender: scott.dj@gmail.com
X-Msg-Ref: server-11.tower-31.messagelabs.com!1405601371!16520542!1
X-Originating-IP: [209.85.220.51]
X-SpamReason: No, hits=1.7 required=7.0 tests=BODY_RANDOM_LONG,
	HTML_10_20, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,
	spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 16769 invoked from network); 17 Jul 2014 12:49:33 -0000
Received: from mail-pa0-f51.google.com (HELO mail-pa0-f51.google.com)
	(209.85.220.51)
	by server-11.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	17 Jul 2014 12:49:33 -0000
Received: by mail-pa0-f51.google.com with SMTP id ey11so3334032pad.10
	for <multiple recipients>; Thu, 17 Jul 2014 05:49:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:date:message-id:subject:from:to:content-type;
	bh=vn8Unnass49RyFe293DkQUIR7XxCphmVfcOUV3oJsyE=;
	b=eqiBEK+WyOdkZk9NeUICfmBugYiZjml00Td/9pHbxVO/Fa3pac/fZvvsK80KlXGa0a
	BelVVNSdTJrn4Wbz72CxqSs3LOVms90iqoDm0MUL6+prxRcNXKmDJYgTvDFJshJYEFrw
	5jfBZK9DIpewDcSzEOOzQFLOYmUES0yNMQXjMa8PBI/zgOx5zaYuOf7hkPsB5GiQJ7PT
	0YbiHssrKUJ6lzBILpI1W6UKPZDpKDUqRE9NTHvxGbJwolngT83wjKK7rHRaaXPf/zt4
	0LUSd1JSIJiqcCPHx6xA24g1fdWd9kBfT/H10SiJ9NEq6kJjz7M4bNtlcCaQRY+lBVAb
	4Cfg==
MIME-Version: 1.0
X-Received: by 10.68.252.7 with SMTP id zo7mr27899424pbc.102.1405601371305;
	Thu, 17 Jul 2014 05:49:31 -0700 (PDT)
Received: by 10.70.11.65 with HTTP; Thu, 17 Jul 2014 05:49:31 -0700 (PDT)
Date: Thu, 17 Jul 2014 13:49:31 +0100
Message-ID: <CAG_esB2FAw2pctiPjvhq5-LYsVfMr+u+3E2woTvgXyiS9O8ozg@mail.gmail.com>
From: David Scott <scott.dj@gmail.com>
To: "mirageos-devel@lists.xenproject.org"
	<mirageos-devel@lists.xenproject.org>, xen-api@lists.xenproject.org
Subject: [Xen-API] Xenstore (client) updates
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============3136204823969627155=="
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

--===============3136204823969627155==
Content-Type: multipart/alternative; boundary=047d7b1630af6ebbb904fe631267

--047d7b1630af6ebbb904fe631267
Content-Type: text/plain; charset=UTF-8

Hi,

I've just merged updates to the Mirage Xenstore protocol and client
implementation to master (but not yet released). There are
backwards-incompatible API changes which I'd like to get right before
release, so feedback is welcome. Note the signatures are separate from the
Mirage V2_LWT ones -- this is an internal implementation library used for
Xen Mirage kernels only. I'll not release this code until (a) we're happy
with it; and (b) patches are available for all users in opam (typical users
include Mirage device drivers and Xen toolstacks)

The reasons I'm proposing backwards-incompatible changes are:

1. to hide the 'client' type from clients. Since there should only be one
real Xenstore connection per process (whether Unix domain sockets or shared
memory), this ended up being a singleton. There doesn't seem any point in
requesting the user 'create' and 'manage' these when the library was doing
it all anyway.

2. for transactions and watches, I've made this into a more monadic style.
The examples in the README.md show what I mean.

3. to move away from exceptions (I'm looking at you, ENOENT) and to use
option types. So we now have 'read' and 'read_exn'. Does anyone know of any
other functions whose signatures could be improved?

4. (for a crash-resistant Irmin Xenstore server): there's now control over
where we are in the shared memory ring. Previously a 'read' would 'consume'
data immediately, which would be lost if we crashed. Now 'read' should not
advance the stream, and the server must decide when is appropriate and call
an 'advance' function manually.

A couple of house-keeping items:

* The repo mirage/ocaml-xenstore which contains the Xenstore protocol
implementation and client code used to be a fork of djs55/ocaml-xenstore.
I've fixed this anomaly and now the mirage/ocaml-xenstore version is the
authoritative version.

* The license of the Xenstore protocol code and client is the Mirage
standard (ISC)

* The code has been re-indented with ocp-indent --syntax=lwt (Mirage
standard style?)

Cheers,
-- 
Dave Scott

--047d7b1630af6ebbb904fe631267
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<div><br></div><div>I&#39;ve just merged updates to the=
 Mirage Xenstore protocol and client implementation to master (but not yet =
released). There are backwards-incompatible API changes which I&#39;d like =
to get right before release, so feedback is welcome. Note the signatures ar=
e separate from the Mirage V2_LWT ones -- this is an internal implementatio=
n library used for Xen Mirage kernels only. I&#39;ll not release this code =
until (a) we&#39;re happy with it; and (b) patches are available for all us=
ers in opam (typical users include Mirage device drivers and Xen toolstacks=
)</div>
<div><br></div><div>The reasons I&#39;m proposing backwards-incompatible ch=
anges are:</div><div><br></div><div>1. to hide the &#39;client&#39; type fr=
om clients. Since there should only be one real Xenstore connection per pro=
cess (whether Unix domain sockets or shared memory), this ended up being a =
singleton. There doesn&#39;t seem any point in requesting the user &#39;cre=
ate&#39; and &#39;manage&#39; these when the library was doing it all anywa=
y.</div>
<div><br></div><div>2. for transactions and watches, I&#39;ve made this int=
o a more monadic style. The examples in the README.md show what I mean.</di=
v><div><br></div><div>3. to move away from exceptions (I&#39;m looking at y=
ou, ENOENT) and to use option types. So we now have &#39;read&#39; and &#39=
;read_exn&#39;. Does anyone know of any other functions whose signatures co=
uld be improved?</div>
<div><br></div><div>4. (for a crash-resistant Irmin Xenstore server): there=
&#39;s now control over where we are in the shared memory ring. Previously =
a &#39;read&#39; would &#39;consume&#39; data immediately, which would be l=
ost if we crashed. Now &#39;read&#39; should not advance the stream, and th=
e server must decide when is appropriate and call an &#39;advance&#39; func=
tion manually.</div>
<div><br></div><div>A couple of house-keeping items:</div><div><br></div><d=
iv>* The repo mirage/ocaml-xenstore which contains the Xenstore protocol im=
plementation and client code used to be a fork of djs55/ocaml-xenstore. I&#=
39;ve fixed this anomaly and now the mirage/ocaml-xenstore version is the a=
uthoritative version.</div>
<div><br></div><div>* The license of the Xenstore protocol code and client =
is the Mirage standard (ISC)<br clear=3D"all"><div><br></div><div>* The cod=
e has been re-indented with ocp-indent --syntax=3Dlwt (Mirage standard styl=
e?)</div>
<div><br></div><div>Cheers,</div>-- <br>Dave Scott
</div></div>

--047d7b1630af6ebbb904fe631267--


--===============3136204823969627155==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--===============3136204823969627155==--


From xen-api-bounces@lists.xen.org Thu Jul 17 13:37:16 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 17 Jul 2014 13:37:16 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X7lry-0003gD-Fw; Thu, 17 Jul 2014 13:37:10 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <anil@recoil.org>) id 1X7lrx-0003g1-IM
	for xen-api@lists.xenproject.org; Thu, 17 Jul 2014 13:37:09 +0000
Received: from [85.158.139.211:49298] by server-7.bemta-5.messagelabs.com id
	86/7D-30824-481D7C35; Thu, 17 Jul 2014 13:37:08 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-8.tower-206.messagelabs.com!1405604227!16059095!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 29659 invoked from network); 17 Jul 2014 13:37:07 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-8.tower-206.messagelabs.com with SMTP;
	17 Jul 2014 13:37:07 -0000
Received: (qmail 23460 invoked by uid 634); 17 Jul 2014 13:37:00 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from global-1-27.nat.csx.cam.ac.uk (HELO
	dhcp-172-17-168-203.eduroam.wireless.private.cam.ac.uk)
	(131.111.184.27)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Thu, 17 Jul 2014 14:37:00 +0100
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Anil Madhavapeddy <anil@recoil.org>
In-Reply-To: <CAG_esB2FAw2pctiPjvhq5-LYsVfMr+u+3E2woTvgXyiS9O8ozg@mail.gmail.com>
Date: Thu, 17 Jul 2014 14:36:59 +0100
Message-Id: <F6189C04-B125-4298-AB70-F9EF92CAB36D@recoil.org>
References: <CAG_esB2FAw2pctiPjvhq5-LYsVfMr+u+3E2woTvgXyiS9O8ozg@mail.gmail.com>
To: David Scott <scott.dj@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: xen-api@lists.xenproject.org, "mirageos-devel@lists.xenproject.org"
	<mirageos-devel@lists.xenproject.org>
Subject: Re: [Xen-API] [MirageOS-devel] Xenstore (client) updates
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

On 17 Jul 2014, at 13:49, David Scott <scott.dj@gmail.com> wrote:

> Hi,
> 
> I've just merged updates to the Mirage Xenstore protocol and client implementation to master (but not yet released). There are backwards-incompatible API changes which I'd like to get right before release, so feedback is welcome. Note the signatures are separate from the Mirage V2_LWT ones -- this is an internal implementation library used for Xen Mirage kernels only. I'll not release this code until (a) we're happy with it; and (b) patches are available for all users in opam (typical users include Mirage device drivers and Xen toolstacks)
> 
> The reasons I'm proposing backwards-incompatible changes are:
> 
> 1. to hide the 'client' type from clients. Since there should only be one real Xenstore connection per process (whether Unix domain sockets or shared memory), this ended up being a singleton. There doesn't seem any point in requesting the user 'create' and 'manage' these when the library was doing it all anyway.
> 
> 2. for transactions and watches, I've made this into a more monadic style. The examples in the README.md show what I mean.
> 
> 3. to move away from exceptions (I'm looking at you, ENOENT) and to use option types. So we now have 'read' and 'read_exn'. Does anyone know of any other functions whose signatures could be improved?

Instead of option types, isn't the Or_error.t style better to avoid not losing the reason for the failure?  For example,

type 'a t =
  | Error of exn
  | Ok of 'a

> 
> 4. (for a crash-resistant Irmin Xenstore server): there's now control over where we are in the shared memory ring. Previously a 'read' would 'consume' data immediately, which would be lost if we crashed. Now 'read' should not advance the stream, and the server must decide when is appropriate and call an 'advance' function manually.

This is a significant improvement and probably relevant to other consumers of this style of RPC (e.g. a vchan2)!

> 
> A couple of house-keeping items:
> 
> * The repo mirage/ocaml-xenstore which contains the Xenstore protocol implementation and client code used to be a fork of djs55/ocaml-xenstore. I've fixed this anomaly and now the mirage/ocaml-xenstore version is the authoritative version.
> 
> * The license of the Xenstore protocol code and client is the Mirage standard (ISC)
> 
> * The code has been re-indented with ocp-indent --syntax=lwt (Mirage standard style?)

Yes, the `ocp-indent` defaults are becoming the defacto standard for indentation.  It doesn't tell you where to put newlines, so there's still some artistic style potential left for the individual programmer :-)

best,
Anil
_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

From xen-api-bounces@lists.xen.org Thu Jul 17 13:37:16 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 17 Jul 2014 13:37:16 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X7lry-0003gD-Fw; Thu, 17 Jul 2014 13:37:10 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <anil@recoil.org>) id 1X7lrx-0003g1-IM
	for xen-api@lists.xenproject.org; Thu, 17 Jul 2014 13:37:09 +0000
Received: from [85.158.139.211:49298] by server-7.bemta-5.messagelabs.com id
	86/7D-30824-481D7C35; Thu, 17 Jul 2014 13:37:08 +0000
X-Env-Sender: anil@recoil.org
X-Msg-Ref: server-8.tower-206.messagelabs.com!1405604227!16059095!1
X-Originating-IP: [89.16.177.154]
X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 29659 invoked from network); 17 Jul 2014 13:37:07 -0000
Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154)
	by server-8.tower-206.messagelabs.com with SMTP;
	17 Jul 2014 13:37:07 -0000
Received: (qmail 23460 invoked by uid 634); 17 Jul 2014 13:37:00 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-1.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: dark.recoil.org
Received: from global-1-27.nat.csx.cam.ac.uk (HELO
	dhcp-172-17-168-203.eduroam.wireless.private.cam.ac.uk)
	(131.111.184.27)
	(smtp-auth username remote@recoil.org, mechanism cram-md5)
	by dark.recoil.org (qpsmtpd/0.84) with ESMTPA;
	Thu, 17 Jul 2014 14:37:00 +0100
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Anil Madhavapeddy <anil@recoil.org>
In-Reply-To: <CAG_esB2FAw2pctiPjvhq5-LYsVfMr+u+3E2woTvgXyiS9O8ozg@mail.gmail.com>
Date: Thu, 17 Jul 2014 14:36:59 +0100
Message-Id: <F6189C04-B125-4298-AB70-F9EF92CAB36D@recoil.org>
References: <CAG_esB2FAw2pctiPjvhq5-LYsVfMr+u+3E2woTvgXyiS9O8ozg@mail.gmail.com>
To: David Scott <scott.dj@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
X-Virus-Checked: Checked by ClamAV on dark.recoil.org
Cc: xen-api@lists.xenproject.org, "mirageos-devel@lists.xenproject.org"
	<mirageos-devel@lists.xenproject.org>
Subject: Re: [Xen-API] [MirageOS-devel] Xenstore (client) updates
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

On 17 Jul 2014, at 13:49, David Scott <scott.dj@gmail.com> wrote:

> Hi,
> 
> I've just merged updates to the Mirage Xenstore protocol and client implementation to master (but not yet released). There are backwards-incompatible API changes which I'd like to get right before release, so feedback is welcome. Note the signatures are separate from the Mirage V2_LWT ones -- this is an internal implementation library used for Xen Mirage kernels only. I'll not release this code until (a) we're happy with it; and (b) patches are available for all users in opam (typical users include Mirage device drivers and Xen toolstacks)
> 
> The reasons I'm proposing backwards-incompatible changes are:
> 
> 1. to hide the 'client' type from clients. Since there should only be one real Xenstore connection per process (whether Unix domain sockets or shared memory), this ended up being a singleton. There doesn't seem any point in requesting the user 'create' and 'manage' these when the library was doing it all anyway.
> 
> 2. for transactions and watches, I've made this into a more monadic style. The examples in the README.md show what I mean.
> 
> 3. to move away from exceptions (I'm looking at you, ENOENT) and to use option types. So we now have 'read' and 'read_exn'. Does anyone know of any other functions whose signatures could be improved?

Instead of option types, isn't the Or_error.t style better to avoid not losing the reason for the failure?  For example,

type 'a t =
  | Error of exn
  | Ok of 'a

> 
> 4. (for a crash-resistant Irmin Xenstore server): there's now control over where we are in the shared memory ring. Previously a 'read' would 'consume' data immediately, which would be lost if we crashed. Now 'read' should not advance the stream, and the server must decide when is appropriate and call an 'advance' function manually.

This is a significant improvement and probably relevant to other consumers of this style of RPC (e.g. a vchan2)!

> 
> A couple of house-keeping items:
> 
> * The repo mirage/ocaml-xenstore which contains the Xenstore protocol implementation and client code used to be a fork of djs55/ocaml-xenstore. I've fixed this anomaly and now the mirage/ocaml-xenstore version is the authoritative version.
> 
> * The license of the Xenstore protocol code and client is the Mirage standard (ISC)
> 
> * The code has been re-indented with ocp-indent --syntax=lwt (Mirage standard style?)

Yes, the `ocp-indent` defaults are becoming the defacto standard for indentation.  It doesn't tell you where to put newlines, so there's still some artistic style potential left for the individual programmer :-)

best,
Anil
_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

From xen-api-bounces@lists.xen.org Thu Jul 17 14:09:31 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 17 Jul 2014 14:09:31 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X7mNC-0005g7-7N; Thu, 17 Jul 2014 14:09:26 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <scott.dj@gmail.com>)
	id 1X7mNB-0005ej-1s; Thu, 17 Jul 2014 14:09:25 +0000
Received: from [85.158.139.211:13324] by server-5.bemta-5.messagelabs.com id
	52/CB-09027-419D7C35; Thu, 17 Jul 2014 14:09:24 +0000
X-Env-Sender: scott.dj@gmail.com
X-Msg-Ref: server-5.tower-206.messagelabs.com!1405606161!16072269!1
X-Originating-IP: [209.85.220.44]
X-SpamReason: No, hits=1.7 required=7.0 tests=BODY_RANDOM_LONG,
	HTML_20_30, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,
	spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 23988 invoked from network); 17 Jul 2014 14:09:22 -0000
Received: from mail-pa0-f44.google.com (HELO mail-pa0-f44.google.com)
	(209.85.220.44)
	by server-5.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	17 Jul 2014 14:09:22 -0000
Received: by mail-pa0-f44.google.com with SMTP id eu11so3460457pac.3
	for <multiple recipients>; Thu, 17 Jul 2014 07:09:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=jp53jUiHP69Mw1jajz93HOtUe5VyMYpPbqqvokbp8Hg=;
	b=dJt53vi1jAq9IJc1s83kMtPUGDFH+h2WIkRrGHS2SWQRHNg3SasCp73iJfrgm2aWav
	ixalw00HE0hHOfZy2HaNnyiwnQU/UhK14MlpP4tByjhaUkxcYAD2qwhViz+OGnGgUR35
	2M40lADqFOo6GUxVobT8dOOzvFqT4YuDtf5m48ZszI7oF5NeV7KouseqpUa3+Rrl/RTs
	MejCzknQs8Ohe8njf7hM6SJa5Rja4m37QTpzwrsVzp1i0e0d2R8/AG7f/69RWwCRlCv5
	kWLxGVs4RPtXeUaz5fwxxGM4p6hqQvtwro/aU47rk/oRCZWM4CFDkCKVbCieXQSZjkyP
	HxSA==
MIME-Version: 1.0
X-Received: by 10.70.137.103 with SMTP id qh7mr26037011pdb.69.1405606160806;
	Thu, 17 Jul 2014 07:09:20 -0700 (PDT)
Received: by 10.70.11.65 with HTTP; Thu, 17 Jul 2014 07:09:20 -0700 (PDT)
In-Reply-To: <F6189C04-B125-4298-AB70-F9EF92CAB36D@recoil.org>
References: <CAG_esB2FAw2pctiPjvhq5-LYsVfMr+u+3E2woTvgXyiS9O8ozg@mail.gmail.com>
	<F6189C04-B125-4298-AB70-F9EF92CAB36D@recoil.org>
Date: Thu, 17 Jul 2014 15:09:20 +0100
Message-ID: <CAG_esB3wK_Zrm-8XcDGcmqYCw_hf59taf=MrUQrwgqwaxD62hQ@mail.gmail.com>
From: David Scott <scott.dj@gmail.com>
To: Anil Madhavapeddy <anil@recoil.org>
Cc: xen-api@lists.xenproject.org, "mirageos-devel@lists.xenproject.org"
	<mirageos-devel@lists.xenproject.org>
Subject: Re: [Xen-API] [MirageOS-devel] Xenstore (client) updates
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============5587768411392152592=="
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

--===============5587768411392152592==
Content-Type: multipart/alternative; boundary=001a1135ecb4e8b92c04fe642f59

--001a1135ecb4e8b92c04fe642f59
Content-Type: text/plain; charset=UTF-8

On Thu, Jul 17, 2014 at 2:36 PM, Anil Madhavapeddy <anil@recoil.org> wrote:

> On 17 Jul 2014, at 13:49, David Scott <scott.dj@gmail.com> wrote:
>
> > Hi,
> >
> > I've just merged updates to the Mirage Xenstore protocol and client
> implementation to master (but not yet released). There are
> backwards-incompatible API changes which I'd like to get right before
> release, so feedback is welcome. Note the signatures are separate from the
> Mirage V2_LWT ones -- this is an internal implementation library used for
> Xen Mirage kernels only. I'll not release this code until (a) we're happy
> with it; and (b) patches are available for all users in opam (typical users
> include Mirage device drivers and Xen toolstacks)
> >
> > The reasons I'm proposing backwards-incompatible changes are:
> >
> > 1. to hide the 'client' type from clients. Since there should only be
> one real Xenstore connection per process (whether Unix domain sockets or
> shared memory), this ended up being a singleton. There doesn't seem any
> point in requesting the user 'create' and 'manage' these when the library
> was doing it all anyway.
> >
> > 2. for transactions and watches, I've made this into a more monadic
> style. The examples in the README.md show what I mean.
> >
> > 3. to move away from exceptions (I'm looking at you, ENOENT) and to use
> option types. So we now have 'read' and 'read_exn'. Does anyone know of any
> other functions whose signatures could be improved?
>
> Instead of option types, isn't the Or_error.t style better to avoid not
> losing the reason for the failure?  For example,
>
> type 'a t =
>   | Error of exn
>   | Ok of 'a
>

I think this is a good idea. I started by making 'read' return a 'string
option' because the 'None' case means 'key doesn't exist' and isn't really
an error-- it's so common client code is riddled with code that expects it.
For all the 'real' errors which are actually fatal (Einval, Equota, Eperm
etc etc) Or_error.t looks nice.


>
> > 4. (for a crash-resistant Irmin Xenstore server): there's now control
> over where we are in the shared memory ring. Previously a 'read' would
> 'consume' data immediately, which would be lost if we crashed. Now 'read'
> should not advance the stream, and the server must decide when is
> appropriate and call an 'advance' function manually.
>
> This is a significant improvement and probably relevant to other consumers
> of this style of RPC (e.g. a vchan2)!
>
> >
> > A couple of house-keeping items:
> >
> > * The repo mirage/ocaml-xenstore which contains the Xenstore protocol
> implementation and client code used to be a fork of djs55/ocaml-xenstore.
> I've fixed this anomaly and now the mirage/ocaml-xenstore version is the
> authoritative version.
> >
> > * The license of the Xenstore protocol code and client is the Mirage
> standard (ISC)
> >
> > * The code has been re-indented with ocp-indent --syntax=lwt (Mirage
> standard style?)
>
> Yes, the `ocp-indent` defaults are becoming the defacto standard for
> indentation.  It doesn't tell you where to put newlines, so there's still
> some artistic style potential left for the individual programmer :-)
>

Cheers,
Dave

--001a1135ecb4e8b92c04fe642f59
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Thu, Jul 17, 2014 at 2:36 PM, Anil Madhavapeddy <span dir=3D"ltr=
">&lt;<a href=3D"mailto:anil@recoil.org" target=3D"_blank">anil@recoil.org<=
/a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"">On 17 Jul 2014, at 13:49, Da=
vid Scott &lt;<a href=3D"mailto:scott.dj@gmail.com">scott.dj@gmail.com</a>&=
gt; wrote:<br>

<br>
&gt; Hi,<br>
&gt;<br>
&gt; I&#39;ve just merged updates to the Mirage Xenstore protocol and clien=
t implementation to master (but not yet released). There are backwards-inco=
mpatible API changes which I&#39;d like to get right before release, so fee=
dback is welcome. Note the signatures are separate from the Mirage V2_LWT o=
nes -- this is an internal implementation library used for Xen Mirage kerne=
ls only. I&#39;ll not release this code until (a) we&#39;re happy with it; =
and (b) patches are available for all users in opam (typical users include =
Mirage device drivers and Xen toolstacks)<br>

&gt;<br>
&gt; The reasons I&#39;m proposing backwards-incompatible changes are:<br>
&gt;<br>
&gt; 1. to hide the &#39;client&#39; type from clients. Since there should =
only be one real Xenstore connection per process (whether Unix domain socke=
ts or shared memory), this ended up being a singleton. There doesn&#39;t se=
em any point in requesting the user &#39;create&#39; and &#39;manage&#39; t=
hese when the library was doing it all anyway.<br>

&gt;<br>
&gt; 2. for transactions and watches, I&#39;ve made this into a more monadi=
c style. The examples in the README.md show what I mean.<br>
&gt;<br>
&gt; 3. to move away from exceptions (I&#39;m looking at you, ENOENT) and t=
o use option types. So we now have &#39;read&#39; and &#39;read_exn&#39;. D=
oes anyone know of any other functions whose signatures could be improved?<=
br>

<br>
</div>Instead of option types, isn&#39;t the Or_error.t style better to avo=
id not losing the reason for the failure? =C2=A0For example,<br>
<br>
type &#39;a t =3D<br>
=C2=A0 | Error of exn<br>
=C2=A0 | Ok of &#39;a<br></blockquote><div><br></div><div>I think this is a=
 good idea. I started by making &#39;read&#39; return a &#39;string option&=
#39; because the &#39;None&#39; case means &#39;key doesn&#39;t exist&#39; =
and isn&#39;t really an error-- it&#39;s so common client code is riddled w=
ith code that expects it. For all the &#39;real&#39; errors which are actua=
lly fatal (Einval, Equota, Eperm etc etc) Or_error.t looks nice.</div>
<div>=C2=A0</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"=
margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=
=3D"">
&gt;<br>
&gt; 4. (for a crash-resistant Irmin Xenstore server): there&#39;s now cont=
rol over where we are in the shared memory ring. Previously a &#39;read&#39=
; would &#39;consume&#39; data immediately, which would be lost if we crash=
ed. Now &#39;read&#39; should not advance the stream, and the server must d=
ecide when is appropriate and call an &#39;advance&#39; function manually.<=
br>

<br>
</div>This is a significant improvement and probably relevant to other cons=
umers of this style of RPC (e.g. a vchan2)!<br>
<div class=3D""><br>
&gt;<br>
&gt; A couple of house-keeping items:<br>
&gt;<br>
&gt; * The repo mirage/ocaml-xenstore which contains the Xenstore protocol =
implementation and client code used to be a fork of djs55/ocaml-xenstore. I=
&#39;ve fixed this anomaly and now the mirage/ocaml-xenstore version is the=
 authoritative version.<br>

&gt;<br>
&gt; * The license of the Xenstore protocol code and client is the Mirage s=
tandard (ISC)<br>
&gt;<br>
&gt; * The code has been re-indented with ocp-indent --syntax=3Dlwt (Mirage=
 standard style?)<br>
<br>
</div>Yes, the `ocp-indent` defaults are becoming the defacto standard for =
indentation. =C2=A0It doesn&#39;t tell you where to put newlines, so there&=
#39;s still some artistic style potential left for the individual programme=
r :-)<br>
</blockquote><div><br></div><div>Cheers,</div><div>Dave</div></div></div></=
div>

--001a1135ecb4e8b92c04fe642f59--


--===============5587768411392152592==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--===============5587768411392152592==--


From xen-api-bounces@lists.xen.org Thu Jul 17 14:09:31 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 17 Jul 2014 14:09:31 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X7mNC-0005g7-7N; Thu, 17 Jul 2014 14:09:26 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <scott.dj@gmail.com>)
	id 1X7mNB-0005ej-1s; Thu, 17 Jul 2014 14:09:25 +0000
Received: from [85.158.139.211:13324] by server-5.bemta-5.messagelabs.com id
	52/CB-09027-419D7C35; Thu, 17 Jul 2014 14:09:24 +0000
X-Env-Sender: scott.dj@gmail.com
X-Msg-Ref: server-5.tower-206.messagelabs.com!1405606161!16072269!1
X-Originating-IP: [209.85.220.44]
X-SpamReason: No, hits=1.7 required=7.0 tests=BODY_RANDOM_LONG,
	HTML_20_30, HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,
	spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 23988 invoked from network); 17 Jul 2014 14:09:22 -0000
Received: from mail-pa0-f44.google.com (HELO mail-pa0-f44.google.com)
	(209.85.220.44)
	by server-5.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	17 Jul 2014 14:09:22 -0000
Received: by mail-pa0-f44.google.com with SMTP id eu11so3460457pac.3
	for <multiple recipients>; Thu, 17 Jul 2014 07:09:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=jp53jUiHP69Mw1jajz93HOtUe5VyMYpPbqqvokbp8Hg=;
	b=dJt53vi1jAq9IJc1s83kMtPUGDFH+h2WIkRrGHS2SWQRHNg3SasCp73iJfrgm2aWav
	ixalw00HE0hHOfZy2HaNnyiwnQU/UhK14MlpP4tByjhaUkxcYAD2qwhViz+OGnGgUR35
	2M40lADqFOo6GUxVobT8dOOzvFqT4YuDtf5m48ZszI7oF5NeV7KouseqpUa3+Rrl/RTs
	MejCzknQs8Ohe8njf7hM6SJa5Rja4m37QTpzwrsVzp1i0e0d2R8/AG7f/69RWwCRlCv5
	kWLxGVs4RPtXeUaz5fwxxGM4p6hqQvtwro/aU47rk/oRCZWM4CFDkCKVbCieXQSZjkyP
	HxSA==
MIME-Version: 1.0
X-Received: by 10.70.137.103 with SMTP id qh7mr26037011pdb.69.1405606160806;
	Thu, 17 Jul 2014 07:09:20 -0700 (PDT)
Received: by 10.70.11.65 with HTTP; Thu, 17 Jul 2014 07:09:20 -0700 (PDT)
In-Reply-To: <F6189C04-B125-4298-AB70-F9EF92CAB36D@recoil.org>
References: <CAG_esB2FAw2pctiPjvhq5-LYsVfMr+u+3E2woTvgXyiS9O8ozg@mail.gmail.com>
	<F6189C04-B125-4298-AB70-F9EF92CAB36D@recoil.org>
Date: Thu, 17 Jul 2014 15:09:20 +0100
Message-ID: <CAG_esB3wK_Zrm-8XcDGcmqYCw_hf59taf=MrUQrwgqwaxD62hQ@mail.gmail.com>
From: David Scott <scott.dj@gmail.com>
To: Anil Madhavapeddy <anil@recoil.org>
Cc: xen-api@lists.xenproject.org, "mirageos-devel@lists.xenproject.org"
	<mirageos-devel@lists.xenproject.org>
Subject: Re: [Xen-API] [MirageOS-devel] Xenstore (client) updates
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============5587768411392152592=="
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

--===============5587768411392152592==
Content-Type: multipart/alternative; boundary=001a1135ecb4e8b92c04fe642f59

--001a1135ecb4e8b92c04fe642f59
Content-Type: text/plain; charset=UTF-8

On Thu, Jul 17, 2014 at 2:36 PM, Anil Madhavapeddy <anil@recoil.org> wrote:

> On 17 Jul 2014, at 13:49, David Scott <scott.dj@gmail.com> wrote:
>
> > Hi,
> >
> > I've just merged updates to the Mirage Xenstore protocol and client
> implementation to master (but not yet released). There are
> backwards-incompatible API changes which I'd like to get right before
> release, so feedback is welcome. Note the signatures are separate from the
> Mirage V2_LWT ones -- this is an internal implementation library used for
> Xen Mirage kernels only. I'll not release this code until (a) we're happy
> with it; and (b) patches are available for all users in opam (typical users
> include Mirage device drivers and Xen toolstacks)
> >
> > The reasons I'm proposing backwards-incompatible changes are:
> >
> > 1. to hide the 'client' type from clients. Since there should only be
> one real Xenstore connection per process (whether Unix domain sockets or
> shared memory), this ended up being a singleton. There doesn't seem any
> point in requesting the user 'create' and 'manage' these when the library
> was doing it all anyway.
> >
> > 2. for transactions and watches, I've made this into a more monadic
> style. The examples in the README.md show what I mean.
> >
> > 3. to move away from exceptions (I'm looking at you, ENOENT) and to use
> option types. So we now have 'read' and 'read_exn'. Does anyone know of any
> other functions whose signatures could be improved?
>
> Instead of option types, isn't the Or_error.t style better to avoid not
> losing the reason for the failure?  For example,
>
> type 'a t =
>   | Error of exn
>   | Ok of 'a
>

I think this is a good idea. I started by making 'read' return a 'string
option' because the 'None' case means 'key doesn't exist' and isn't really
an error-- it's so common client code is riddled with code that expects it.
For all the 'real' errors which are actually fatal (Einval, Equota, Eperm
etc etc) Or_error.t looks nice.


>
> > 4. (for a crash-resistant Irmin Xenstore server): there's now control
> over where we are in the shared memory ring. Previously a 'read' would
> 'consume' data immediately, which would be lost if we crashed. Now 'read'
> should not advance the stream, and the server must decide when is
> appropriate and call an 'advance' function manually.
>
> This is a significant improvement and probably relevant to other consumers
> of this style of RPC (e.g. a vchan2)!
>
> >
> > A couple of house-keeping items:
> >
> > * The repo mirage/ocaml-xenstore which contains the Xenstore protocol
> implementation and client code used to be a fork of djs55/ocaml-xenstore.
> I've fixed this anomaly and now the mirage/ocaml-xenstore version is the
> authoritative version.
> >
> > * The license of the Xenstore protocol code and client is the Mirage
> standard (ISC)
> >
> > * The code has been re-indented with ocp-indent --syntax=lwt (Mirage
> standard style?)
>
> Yes, the `ocp-indent` defaults are becoming the defacto standard for
> indentation.  It doesn't tell you where to put newlines, so there's still
> some artistic style potential left for the individual programmer :-)
>

Cheers,
Dave

--001a1135ecb4e8b92c04fe642f59
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Thu, Jul 17, 2014 at 2:36 PM, Anil Madhavapeddy <span dir=3D"ltr=
">&lt;<a href=3D"mailto:anil@recoil.org" target=3D"_blank">anil@recoil.org<=
/a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"">On 17 Jul 2014, at 13:49, Da=
vid Scott &lt;<a href=3D"mailto:scott.dj@gmail.com">scott.dj@gmail.com</a>&=
gt; wrote:<br>

<br>
&gt; Hi,<br>
&gt;<br>
&gt; I&#39;ve just merged updates to the Mirage Xenstore protocol and clien=
t implementation to master (but not yet released). There are backwards-inco=
mpatible API changes which I&#39;d like to get right before release, so fee=
dback is welcome. Note the signatures are separate from the Mirage V2_LWT o=
nes -- this is an internal implementation library used for Xen Mirage kerne=
ls only. I&#39;ll not release this code until (a) we&#39;re happy with it; =
and (b) patches are available for all users in opam (typical users include =
Mirage device drivers and Xen toolstacks)<br>

&gt;<br>
&gt; The reasons I&#39;m proposing backwards-incompatible changes are:<br>
&gt;<br>
&gt; 1. to hide the &#39;client&#39; type from clients. Since there should =
only be one real Xenstore connection per process (whether Unix domain socke=
ts or shared memory), this ended up being a singleton. There doesn&#39;t se=
em any point in requesting the user &#39;create&#39; and &#39;manage&#39; t=
hese when the library was doing it all anyway.<br>

&gt;<br>
&gt; 2. for transactions and watches, I&#39;ve made this into a more monadi=
c style. The examples in the README.md show what I mean.<br>
&gt;<br>
&gt; 3. to move away from exceptions (I&#39;m looking at you, ENOENT) and t=
o use option types. So we now have &#39;read&#39; and &#39;read_exn&#39;. D=
oes anyone know of any other functions whose signatures could be improved?<=
br>

<br>
</div>Instead of option types, isn&#39;t the Or_error.t style better to avo=
id not losing the reason for the failure? =C2=A0For example,<br>
<br>
type &#39;a t =3D<br>
=C2=A0 | Error of exn<br>
=C2=A0 | Ok of &#39;a<br></blockquote><div><br></div><div>I think this is a=
 good idea. I started by making &#39;read&#39; return a &#39;string option&=
#39; because the &#39;None&#39; case means &#39;key doesn&#39;t exist&#39; =
and isn&#39;t really an error-- it&#39;s so common client code is riddled w=
ith code that expects it. For all the &#39;real&#39; errors which are actua=
lly fatal (Einval, Equota, Eperm etc etc) Or_error.t looks nice.</div>
<div>=C2=A0</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"=
margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=
=3D"">
&gt;<br>
&gt; 4. (for a crash-resistant Irmin Xenstore server): there&#39;s now cont=
rol over where we are in the shared memory ring. Previously a &#39;read&#39=
; would &#39;consume&#39; data immediately, which would be lost if we crash=
ed. Now &#39;read&#39; should not advance the stream, and the server must d=
ecide when is appropriate and call an &#39;advance&#39; function manually.<=
br>

<br>
</div>This is a significant improvement and probably relevant to other cons=
umers of this style of RPC (e.g. a vchan2)!<br>
<div class=3D""><br>
&gt;<br>
&gt; A couple of house-keeping items:<br>
&gt;<br>
&gt; * The repo mirage/ocaml-xenstore which contains the Xenstore protocol =
implementation and client code used to be a fork of djs55/ocaml-xenstore. I=
&#39;ve fixed this anomaly and now the mirage/ocaml-xenstore version is the=
 authoritative version.<br>

&gt;<br>
&gt; * The license of the Xenstore protocol code and client is the Mirage s=
tandard (ISC)<br>
&gt;<br>
&gt; * The code has been re-indented with ocp-indent --syntax=3Dlwt (Mirage=
 standard style?)<br>
<br>
</div>Yes, the `ocp-indent` defaults are becoming the defacto standard for =
indentation. =C2=A0It doesn&#39;t tell you where to put newlines, so there&=
#39;s still some artistic style potential left for the individual programme=
r :-)<br>
</blockquote><div><br></div><div>Cheers,</div><div>Dave</div></div></div></=
div>

--001a1135ecb4e8b92c04fe642f59--


--===============5587768411392152592==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--===============5587768411392152592==--


From xen-api-bounces@lists.xen.org Thu Jul 17 18:06:09 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 17 Jul 2014 18:06:09 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X7q46-00069Y-44; Thu, 17 Jul 2014 18:05:58 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <syao.work@gmail.com>) id 1X7q44-00069T-FW
	for xen-api@lists.xen.org; Thu, 17 Jul 2014 18:05:56 +0000
Received: from [193.109.254.147:28503] by server-12.bemta-14.messagelabs.com
	id 28/13-23742-38018C35; Thu, 17 Jul 2014 18:05:55 +0000
X-Env-Sender: syao.work@gmail.com
X-Msg-Ref: server-5.tower-27.messagelabs.com!1405620354!13440522!1
X-Originating-IP: [209.85.213.170]
X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 12588 invoked from network); 17 Jul 2014 18:05:55 -0000
Received: from mail-ig0-f170.google.com (HELO mail-ig0-f170.google.com)
	(209.85.213.170)
	by server-5.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	17 Jul 2014 18:05:55 -0000
Received: by mail-ig0-f170.google.com with SMTP id h3so6616igd.5
	for <xen-api@lists.xen.org>; Thu, 17 Jul 2014 11:05:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:date:message-id:subject:from:to:content-type;
	bh=6iObazf3CPF8/Pr2GVjwsmIAelE6bWwctt7jsRuRmeE=;
	b=Y4TXFQ42f6H9kHYJ7dNcPNEp8NuclLLLIg2J7E//MG/hbBPvg8PsSaHDgVRtT3K4sg
	SaSkL98BpJQD4q3N+cyJuP/z12OUJMz4qE32glTGU46Upef2h3YrKrzZowfOECLdsi5R
	2wbUeWQrNjQb4jVAUndnXa9Tydm2aZsS2vmEaEG6NHh7Um7yHMXNERRwBW+oVXz0PXtD
	/WChr0TBFeqK/DM9WOoJP5rollp4j2TZsPWfLJexChl8nBTIAQ52SA3IZ2CyMzQvyYlq
	tzUENWXtoXxX+CLvdrXUYYjfHAqw6Rf2XoWozqjs0B2Z7MKrj+krGSe+BVcVQbOz9Ps9
	P+pQ==
MIME-Version: 1.0
X-Received: by 10.182.87.9 with SMTP id t9mr6931423obz.72.1405620353607; Thu,
	17 Jul 2014 11:05:53 -0700 (PDT)
Received: by 10.76.141.231 with HTTP; Thu, 17 Jul 2014 11:05:53 -0700 (PDT)
Date: Thu, 17 Jul 2014 21:05:53 +0300
Message-ID: <CALMrCZ2DhgqV=ArjKFym+3MWMJJ2fAsioVz9Hv_KiV51ecguKA@mail.gmail.com>
From: Edgaras Work <syao.work@gmail.com>
To: xen-api@lists.xen.org
Subject: [Xen-API] Installing "XenServer" to CentOS 6.5 (using buildroot)
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2625899485530012847=="
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

--===============2625899485530012847==
Content-Type: multipart/alternative; boundary=089e013cb9aeddae0b04fe677dde

--089e013cb9aeddae0b04fe677dde
Content-Type: text/plain; charset=UTF-8

Hello,

I did install XenServer to CentOS using
https://github.com/xenserver/buildroot . but the were a problem, I wanted
to use "xe-*" console commands but I couldn't do it - the commands were not
found in the CentOS intallation. So it seems that the buildroot did not
install all the packages the original XenServer has.

Is there a way to install those packages?
Source compile isn't a problem.

P.S. I am installing CloudStack on Dom0 of Xen. Is there any other way
setting the config for machine that it would communicate with CloudStack?

Best regards,
Edgar

--089e013cb9aeddae0b04fe677dde
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello,<div><br></div><div>I did install XenServer to CentO=
S using=C2=A0<a href=3D"https://github.com/xenserver/buildroot">https://git=
hub.com/xenserver/buildroot</a> . but the were a problem, I wanted to use &=
quot;xe-*&quot; console commands but I couldn&#39;t do it - the commands we=
re not found in the CentOS intallation. So it seems that the buildroot did =
not install all the packages the original XenServer has.=C2=A0</div>
<div><br></div><div>Is there a way to install those packages?=C2=A0</div><d=
iv>Source compile isn&#39;t a problem.=C2=A0</div><div><br></div><div>P.S. =
I am installing CloudStack on Dom0 of Xen. Is there any other way setting t=
he config for machine that it would communicate with CloudStack?</div>
<div><br></div><div>Best regards,</div><div>Edgar</div></div>

--089e013cb9aeddae0b04fe677dde--


--===============2625899485530012847==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--===============2625899485530012847==--


From xen-api-bounces@lists.xen.org Thu Jul 17 18:06:09 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Thu, 17 Jul 2014 18:06:09 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X7q46-00069Y-44; Thu, 17 Jul 2014 18:05:58 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <syao.work@gmail.com>) id 1X7q44-00069T-FW
	for xen-api@lists.xen.org; Thu, 17 Jul 2014 18:05:56 +0000
Received: from [193.109.254.147:28503] by server-12.bemta-14.messagelabs.com
	id 28/13-23742-38018C35; Thu, 17 Jul 2014 18:05:55 +0000
X-Env-Sender: syao.work@gmail.com
X-Msg-Ref: server-5.tower-27.messagelabs.com!1405620354!13440522!1
X-Originating-IP: [209.85.213.170]
X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE,
	ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 12588 invoked from network); 17 Jul 2014 18:05:55 -0000
Received: from mail-ig0-f170.google.com (HELO mail-ig0-f170.google.com)
	(209.85.213.170)
	by server-5.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	17 Jul 2014 18:05:55 -0000
Received: by mail-ig0-f170.google.com with SMTP id h3so6616igd.5
	for <xen-api@lists.xen.org>; Thu, 17 Jul 2014 11:05:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:date:message-id:subject:from:to:content-type;
	bh=6iObazf3CPF8/Pr2GVjwsmIAelE6bWwctt7jsRuRmeE=;
	b=Y4TXFQ42f6H9kHYJ7dNcPNEp8NuclLLLIg2J7E//MG/hbBPvg8PsSaHDgVRtT3K4sg
	SaSkL98BpJQD4q3N+cyJuP/z12OUJMz4qE32glTGU46Upef2h3YrKrzZowfOECLdsi5R
	2wbUeWQrNjQb4jVAUndnXa9Tydm2aZsS2vmEaEG6NHh7Um7yHMXNERRwBW+oVXz0PXtD
	/WChr0TBFeqK/DM9WOoJP5rollp4j2TZsPWfLJexChl8nBTIAQ52SA3IZ2CyMzQvyYlq
	tzUENWXtoXxX+CLvdrXUYYjfHAqw6Rf2XoWozqjs0B2Z7MKrj+krGSe+BVcVQbOz9Ps9
	P+pQ==
MIME-Version: 1.0
X-Received: by 10.182.87.9 with SMTP id t9mr6931423obz.72.1405620353607; Thu,
	17 Jul 2014 11:05:53 -0700 (PDT)
Received: by 10.76.141.231 with HTTP; Thu, 17 Jul 2014 11:05:53 -0700 (PDT)
Date: Thu, 17 Jul 2014 21:05:53 +0300
Message-ID: <CALMrCZ2DhgqV=ArjKFym+3MWMJJ2fAsioVz9Hv_KiV51ecguKA@mail.gmail.com>
From: Edgaras Work <syao.work@gmail.com>
To: xen-api@lists.xen.org
Subject: [Xen-API] Installing "XenServer" to CentOS 6.5 (using buildroot)
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2625899485530012847=="
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

--===============2625899485530012847==
Content-Type: multipart/alternative; boundary=089e013cb9aeddae0b04fe677dde

--089e013cb9aeddae0b04fe677dde
Content-Type: text/plain; charset=UTF-8

Hello,

I did install XenServer to CentOS using
https://github.com/xenserver/buildroot . but the were a problem, I wanted
to use "xe-*" console commands but I couldn't do it - the commands were not
found in the CentOS intallation. So it seems that the buildroot did not
install all the packages the original XenServer has.

Is there a way to install those packages?
Source compile isn't a problem.

P.S. I am installing CloudStack on Dom0 of Xen. Is there any other way
setting the config for machine that it would communicate with CloudStack?

Best regards,
Edgar

--089e013cb9aeddae0b04fe677dde
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello,<div><br></div><div>I did install XenServer to CentO=
S using=C2=A0<a href=3D"https://github.com/xenserver/buildroot">https://git=
hub.com/xenserver/buildroot</a> . but the were a problem, I wanted to use &=
quot;xe-*&quot; console commands but I couldn&#39;t do it - the commands we=
re not found in the CentOS intallation. So it seems that the buildroot did =
not install all the packages the original XenServer has.=C2=A0</div>
<div><br></div><div>Is there a way to install those packages?=C2=A0</div><d=
iv>Source compile isn&#39;t a problem.=C2=A0</div><div><br></div><div>P.S. =
I am installing CloudStack on Dom0 of Xen. Is there any other way setting t=
he config for machine that it would communicate with CloudStack?</div>
<div><br></div><div>Best regards,</div><div>Edgar</div></div>

--089e013cb9aeddae0b04fe677dde--


--===============2625899485530012847==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--===============2625899485530012847==--


From xen-api-bounces@lists.xen.org Mon Jul 21 10:56:30 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Mon, 21 Jul 2014 10:56:30 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X9BGa-0000D6-OL; Mon, 21 Jul 2014 10:56:24 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <Stefano.Stabellini@citrix.com>)
	id 1X9BGZ-0000Co-7x; Mon, 21 Jul 2014 10:56:23 +0000
Received: from [85.158.139.211:20632] by server-7.bemta-5.messagelabs.com id
	CE/98-30824-6D1FCC35; Mon, 21 Jul 2014 10:56:22 +0000
X-Env-Sender: Stefano.Stabellini@citrix.com
X-Msg-Ref: server-5.tower-206.messagelabs.com!1405940179!16624439!1
X-Originating-IP: [66.165.176.63]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 3466 invoked from network); 21 Jul 2014 10:56:21 -0000
Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63)
	by server-5.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	21 Jul 2014 10:56:21 -0000
X-IronPort-AV: E=Sophos;i="5.01,700,1400025600"; d="scan'208";a="154622482"
Received: from accessns.citrite.net (HELO FTLPEX01CL02.citrite.net)
	([10.9.154.239])
	by FTLPIPO02.CITRIX.COM with ESMTP; 21 Jul 2014 10:55:47 +0000
Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com
	(10.13.107.79) with Microsoft SMTP Server id 14.3.181.6;
	Mon, 21 Jul 2014 06:55:47 -0400
Received: from kaball.uk.xensource.com ([10.80.2.59])	by
	ukmail1.uk.xensource.com with esmtp (Exim 4.69)	(envelope-from
	<stefano.stabellini@eu.citrix.com>)	id 1X9BFz-0002HG-3G;
	Mon, 21 Jul 2014 11:55:47 +0100
Date: Mon, 21 Jul 2014 11:54:50 +0100
From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
X-X-Sender: sstabellini@kaball.uk.xensource.com
To: "lars.kurth@xenproject.org" <lars.kurth@xenproject.org>
In-Reply-To: <53C50EBE.40107@xen.org>
Message-ID: <alpine.DEB.2.02.1407211154200.2295@kaball.uk.xensource.com>
References: <53C50EBE.40107@xen.org>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
MIME-Version: 1.0
X-DLP: MIA2
Cc: xen-devel <xen-devel@lists.xenproject.org>,
	advisory-board@lists.xenproject.org,
	Artem Mygaiev <artem.mygaiev@globallogic.com>,
	Alex Agizim <alex.agizim@globallogic.com>,
	"xen-api@lists.xenproject.org" <xen-api@lists.xenproject.org>
Subject: Re: [Xen-API] [Xen-devel] [Maintainer vote] Embedded and Automotive
 PV Drivers Project Proposal - closes July 23rd
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

On Tue, 15 Jul 2014, Lars Kurth wrote:
> Hi all,
> 
> in accordance with http://xenproject.org/governance.html it is time to vote on
> "Embedded and Automotive PV Drivers Project Proposal" (or
> http://wiki.xenproject.org/wiki/Embedded_and_Automotive_PV_Drivers_Project_Proposal).
> The vote is open for a week as usual.
> 
> All maintainers of mature Xen Project sub-projects can vote, which includes
> the Hypervisor and XAPI project. The list of eligable people are
> * Hypervisor : see
> http://xenbits.xenproject.org/gitweb/?p=xen.git;a=blob;f=MAINTAINERS;hb=HEAD
> * XAPI :  see http://xenproject.org/developers/teams/xapi.html, note that XAPI
> PROJECT LEADS & COMMITERS and MAINTAINERS are listed on
> https://github.com/xapi-project/xen-api
> 
> If you are in favour, reply "+1" to this thread
> If you do not care, reply "0"
> If you object, reply "-1" with a comment justifying the objection

+1

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

From xen-api-bounces@lists.xen.org Mon Jul 21 10:56:30 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Mon, 21 Jul 2014 10:56:30 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X9BGa-0000D6-OL; Mon, 21 Jul 2014 10:56:24 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <Stefano.Stabellini@citrix.com>)
	id 1X9BGZ-0000Co-7x; Mon, 21 Jul 2014 10:56:23 +0000
Received: from [85.158.139.211:20632] by server-7.bemta-5.messagelabs.com id
	CE/98-30824-6D1FCC35; Mon, 21 Jul 2014 10:56:22 +0000
X-Env-Sender: Stefano.Stabellini@citrix.com
X-Msg-Ref: server-5.tower-206.messagelabs.com!1405940179!16624439!1
X-Originating-IP: [66.165.176.63]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 3466 invoked from network); 21 Jul 2014 10:56:21 -0000
Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63)
	by server-5.tower-206.messagelabs.com with RC4-SHA encrypted SMTP;
	21 Jul 2014 10:56:21 -0000
X-IronPort-AV: E=Sophos;i="5.01,700,1400025600"; d="scan'208";a="154622482"
Received: from accessns.citrite.net (HELO FTLPEX01CL02.citrite.net)
	([10.9.154.239])
	by FTLPIPO02.CITRIX.COM with ESMTP; 21 Jul 2014 10:55:47 +0000
Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com
	(10.13.107.79) with Microsoft SMTP Server id 14.3.181.6;
	Mon, 21 Jul 2014 06:55:47 -0400
Received: from kaball.uk.xensource.com ([10.80.2.59])	by
	ukmail1.uk.xensource.com with esmtp (Exim 4.69)	(envelope-from
	<stefano.stabellini@eu.citrix.com>)	id 1X9BFz-0002HG-3G;
	Mon, 21 Jul 2014 11:55:47 +0100
Date: Mon, 21 Jul 2014 11:54:50 +0100
From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
X-X-Sender: sstabellini@kaball.uk.xensource.com
To: "lars.kurth@xenproject.org" <lars.kurth@xenproject.org>
In-Reply-To: <53C50EBE.40107@xen.org>
Message-ID: <alpine.DEB.2.02.1407211154200.2295@kaball.uk.xensource.com>
References: <53C50EBE.40107@xen.org>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
MIME-Version: 1.0
X-DLP: MIA2
Cc: xen-devel <xen-devel@lists.xenproject.org>,
	advisory-board@lists.xenproject.org,
	Artem Mygaiev <artem.mygaiev@globallogic.com>,
	Alex Agizim <alex.agizim@globallogic.com>,
	"xen-api@lists.xenproject.org" <xen-api@lists.xenproject.org>
Subject: Re: [Xen-API] [Xen-devel] [Maintainer vote] Embedded and Automotive
 PV Drivers Project Proposal - closes July 23rd
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

On Tue, 15 Jul 2014, Lars Kurth wrote:
> Hi all,
> 
> in accordance with http://xenproject.org/governance.html it is time to vote on
> "Embedded and Automotive PV Drivers Project Proposal" (or
> http://wiki.xenproject.org/wiki/Embedded_and_Automotive_PV_Drivers_Project_Proposal).
> The vote is open for a week as usual.
> 
> All maintainers of mature Xen Project sub-projects can vote, which includes
> the Hypervisor and XAPI project. The list of eligable people are
> * Hypervisor : see
> http://xenbits.xenproject.org/gitweb/?p=xen.git;a=blob;f=MAINTAINERS;hb=HEAD
> * XAPI :  see http://xenproject.org/developers/teams/xapi.html, note that XAPI
> PROJECT LEADS & COMMITERS and MAINTAINERS are listed on
> https://github.com/xapi-project/xen-api
> 
> If you are in favour, reply "+1" to this thread
> If you do not care, reply "0"
> If you object, reply "-1" with a comment justifying the objection

+1

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

From xen-api-bounces@lists.xen.org Wed Jul 23 01:02:16 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 23 Jul 2014 01:02:16 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X9kwW-0001lg-Id; Wed, 23 Jul 2014 01:02:04 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <bwestover@pletter.com>) id 1X9kwU-0001Wk-99
	for xen-api@lists.xen.org; Wed, 23 Jul 2014 01:02:03 +0000
Received: from [85.158.139.211:62530] by server-8.bemta-5.messagelabs.com id
	DE/52-22440-9890FC35; Wed, 23 Jul 2014 01:02:01 +0000
X-Env-Sender: bwestover@pletter.com
X-Msg-Ref: server-12.tower-206.messagelabs.com!1406077319!16990186!1
X-Originating-IP: [207.46.163.144]
X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 24506 invoked from network); 23 Jul 2014 01:02:00 -0000
Received: from mail-bn1lp0144.outbound.protection.outlook.com (HELO
	na01-bn1-obe.outbound.protection.outlook.com) (207.46.163.144)
	by server-12.tower-206.messagelabs.com with AES256-SHA encrypted SMTP;
	23 Jul 2014 01:02:00 -0000
Received: from DM2PR04MB829.namprd04.prod.outlook.com (10.141.180.11) by
	DM2PR04MB829.namprd04.prod.outlook.com (10.141.180.11) with Microsoft
	SMTP Server (TLS) id 15.0.990.7; Wed, 23 Jul 2014 01:01:57 +0000
Received: from DM2PR04MB829.namprd04.prod.outlook.com ([10.141.180.11]) by
	DM2PR04MB829.namprd04.prod.outlook.com ([10.141.180.11]) with mapi id
	15.00.0990.007; Wed, 23 Jul 2014 01:01:57 +0000
From: Brett Westover <bwestover@pletter.com>
To: "xen-api@lists.xen.org" <xen-api@lists.xen.org>
Thread-Topic: [Xen-API] XenServer Failed Import
Thread-Index: Ac+mEJXTNTUqRHanT8OHkEqri7+dfw==
Date: Wed, 23 Jul 2014 01:01:56 +0000
Message-ID: <7048b627f8794c17a8de213314e087ca@DM2PR04MB829.namprd04.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [173.162.3.97]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:
x-forefront-prvs: 028166BF91
x-forefront-antispam-report: SFV:NSPM;
	SFS:(6009001)(189002)(199002)(164054003)(2656002)(74662001)(105586002)(107046002)(107886001)(81342001)(74502001)(79102001)(2351001)(19609705001)(106356001)(92566001)(76576001)(64706001)(19625215002)(20776003)(85852003)(87936001)(66066001)(80022001)(86362001)(77982001)(95666004)(83322001)(19580395003)(81542001)(229853001)(74316001)(110136001)(4396001)(46102001)(76482001)(99396002)(19300405004)(15202345003)(15975445006)(99286002)(83072002)(101416001)(31966008)(50986999)(54356999)(33646002)(21056001)(85306003)(16236675004)(108616002)(24736002);
	DIR:OUT; SFP:; SCL:1; SRVR:DM2PR04MB829;
	H:DM2PR04MB829.namprd04.prod.outlook.com; FPR:; MLV:sfv;
	PTR:InfoNoRecords; MX:1; LANG:en; 
MIME-Version: 1.0
X-OriginatorOrg: pletter.com
Subject: [Xen-API]  XenServer Failed Import
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============6954718951091364998=="
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

--===============6954718951091364998==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_7048b627f8794c17a8de213314e087caDM2PR04MB829namprd04pro_"

--_000_7048b627f8794c17a8de213314e087caDM2PR04MB829namprd04pro_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hello,
  I'm trying to import OVF package to XenServer 6.2 build 70446c

I have installed, and re-installed the Transfer VM from:
/opt/xensource/packages/files/transfer-vm

The transfer VM version is 6.2.0-70314c , I find it odd that it's a differe=
nt build number.

When I try to import several different OVF packages I see the transfer VM s=
tartup and attach a disk.
After about 2 min and 30 seconds I get this error:

Error: Import Appliance - Failed to import.

I found an article suggesting this error could be a DHCP issue. I am settin=
g the transfer VM to use a
static IP address.

Any idea what I'm doing wrong, or how I can troubleshoot further?

Thanks,

Brett


--_000_7048b627f8794c17a8de213314e087caDM2PR04MB829namprd04pro_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hello,<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp; I&#8217;m trying to import OVF package to Xen=
Server 6.2 build 70446c<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I have installed, and re-installed the Transfer VM f=
rom:<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"text-indent:.5in">/opt/xensource/packages/f=
iles/transfer-vm<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The transfer VM version is 6.2.0-70314c , I find it =
odd that it&#8217;s a different build number.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">When I try to import several different OVF packages =
I see the transfer VM startup and attach a disk.<o:p></o:p></p>
<p class=3D"MsoNormal">After about 2 min and 30 seconds I get this error:<o=
:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"text-indent:.5in">Error: Import Appliance -=
 Failed to import.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I found an article suggesting this error could be a =
DHCP issue. I am setting the transfer VM to use a
<o:p></o:p></p>
<p class=3D"MsoNormal">static IP address.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Any idea what I&#8217;m doing wrong, or how I can tr=
oubleshoot further?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Brett<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_7048b627f8794c17a8de213314e087caDM2PR04MB829namprd04pro_--


--===============6954718951091364998==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--===============6954718951091364998==--


From xen-api-bounces@lists.xen.org Wed Jul 23 01:02:16 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 23 Jul 2014 01:02:16 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1X9kwW-0001lg-Id; Wed, 23 Jul 2014 01:02:04 +0000
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <bwestover@pletter.com>) id 1X9kwU-0001Wk-99
	for xen-api@lists.xen.org; Wed, 23 Jul 2014 01:02:03 +0000
Received: from [85.158.139.211:62530] by server-8.bemta-5.messagelabs.com id
	DE/52-22440-9890FC35; Wed, 23 Jul 2014 01:02:01 +0000
X-Env-Sender: bwestover@pletter.com
X-Msg-Ref: server-12.tower-206.messagelabs.com!1406077319!16990186!1
X-Originating-IP: [207.46.163.144]
X-SpamReason: No, hits=0.0 required=7.0 tests=HTML_MESSAGE
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 24506 invoked from network); 23 Jul 2014 01:02:00 -0000
Received: from mail-bn1lp0144.outbound.protection.outlook.com (HELO
	na01-bn1-obe.outbound.protection.outlook.com) (207.46.163.144)
	by server-12.tower-206.messagelabs.com with AES256-SHA encrypted SMTP;
	23 Jul 2014 01:02:00 -0000
Received: from DM2PR04MB829.namprd04.prod.outlook.com (10.141.180.11) by
	DM2PR04MB829.namprd04.prod.outlook.com (10.141.180.11) with Microsoft
	SMTP Server (TLS) id 15.0.990.7; Wed, 23 Jul 2014 01:01:57 +0000
Received: from DM2PR04MB829.namprd04.prod.outlook.com ([10.141.180.11]) by
	DM2PR04MB829.namprd04.prod.outlook.com ([10.141.180.11]) with mapi id
	15.00.0990.007; Wed, 23 Jul 2014 01:01:57 +0000
From: Brett Westover <bwestover@pletter.com>
To: "xen-api@lists.xen.org" <xen-api@lists.xen.org>
Thread-Topic: [Xen-API] XenServer Failed Import
Thread-Index: Ac+mEJXTNTUqRHanT8OHkEqri7+dfw==
Date: Wed, 23 Jul 2014 01:01:56 +0000
Message-ID: <7048b627f8794c17a8de213314e087ca@DM2PR04MB829.namprd04.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [173.162.3.97]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:
x-forefront-prvs: 028166BF91
x-forefront-antispam-report: SFV:NSPM;
	SFS:(6009001)(189002)(199002)(164054003)(2656002)(74662001)(105586002)(107046002)(107886001)(81342001)(74502001)(79102001)(2351001)(19609705001)(106356001)(92566001)(76576001)(64706001)(19625215002)(20776003)(85852003)(87936001)(66066001)(80022001)(86362001)(77982001)(95666004)(83322001)(19580395003)(81542001)(229853001)(74316001)(110136001)(4396001)(46102001)(76482001)(99396002)(19300405004)(15202345003)(15975445006)(99286002)(83072002)(101416001)(31966008)(50986999)(54356999)(33646002)(21056001)(85306003)(16236675004)(108616002)(24736002);
	DIR:OUT; SFP:; SCL:1; SRVR:DM2PR04MB829;
	H:DM2PR04MB829.namprd04.prod.outlook.com; FPR:; MLV:sfv;
	PTR:InfoNoRecords; MX:1; LANG:en; 
MIME-Version: 1.0
X-OriginatorOrg: pletter.com
Subject: [Xen-API]  XenServer Failed Import
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============6954718951091364998=="
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

--===============6954718951091364998==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_7048b627f8794c17a8de213314e087caDM2PR04MB829namprd04pro_"

--_000_7048b627f8794c17a8de213314e087caDM2PR04MB829namprd04pro_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hello,
  I'm trying to import OVF package to XenServer 6.2 build 70446c

I have installed, and re-installed the Transfer VM from:
/opt/xensource/packages/files/transfer-vm

The transfer VM version is 6.2.0-70314c , I find it odd that it's a differe=
nt build number.

When I try to import several different OVF packages I see the transfer VM s=
tartup and attach a disk.
After about 2 min and 30 seconds I get this error:

Error: Import Appliance - Failed to import.

I found an article suggesting this error could be a DHCP issue. I am settin=
g the transfer VM to use a
static IP address.

Any idea what I'm doing wrong, or how I can troubleshoot further?

Thanks,

Brett


--_000_7048b627f8794c17a8de213314e087caDM2PR04MB829namprd04pro_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hello,<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp; I&#8217;m trying to import OVF package to Xen=
Server 6.2 build 70446c<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I have installed, and re-installed the Transfer VM f=
rom:<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"text-indent:.5in">/opt/xensource/packages/f=
iles/transfer-vm<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The transfer VM version is 6.2.0-70314c , I find it =
odd that it&#8217;s a different build number.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">When I try to import several different OVF packages =
I see the transfer VM startup and attach a disk.<o:p></o:p></p>
<p class=3D"MsoNormal">After about 2 min and 30 seconds I get this error:<o=
:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"text-indent:.5in">Error: Import Appliance -=
 Failed to import.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I found an article suggesting this error could be a =
DHCP issue. I am setting the transfer VM to use a
<o:p></o:p></p>
<p class=3D"MsoNormal">static IP address.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Any idea what I&#8217;m doing wrong, or how I can tr=
oubleshoot further?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Brett<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_7048b627f8794c17a8de213314e087caDM2PR04MB829namprd04pro_--


--===============6954718951091364998==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

--===============6954718951091364998==--


From xen-api-bounces@lists.xen.org Fri Jul 25 17:36:04 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Fri, 25 Jul 2014 17:36:04 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1XAjPS-0006v0-QS; Fri, 25 Jul 2014 17:35:58 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <russell.pavlicek.xen@gmail.com>)
	id 1XAjPR-0006ui-KC; Fri, 25 Jul 2014 17:35:57 +0000
Received: from [193.109.254.147:41323] by server-16.bemta-14.messagelabs.com
	id BD/85-14741-C7592D35; Fri, 25 Jul 2014 17:35:56 +0000
X-Env-Sender: russell.pavlicek.xen@gmail.com
X-Msg-Ref: server-2.tower-27.messagelabs.com!1406309753!11849770!1
X-Originating-IP: [209.85.217.173]
X-SpamReason: No, hits=2.5 required=7.0 tests=RCVD_BY_IP,
  SUSPICIOUS_RECIPS
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 28703 invoked from network); 25 Jul 2014 17:35:54 -0000
Received: from mail-lb0-f173.google.com (HELO mail-lb0-f173.google.com)
	(209.85.217.173)
	by server-2.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	25 Jul 2014 17:35:54 -0000
Received: by mail-lb0-f173.google.com with SMTP id p9so3667813lbv.18
	for <multiple recipients>; Fri, 25 Jul 2014 10:35:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:sender:date:message-id:subject:from:to:content-type;
	bh=nAOMfZGKMqhT4JG64nphrc8G6NQLDxto9eK2WeUiF7c=;
	b=cLZ2pukMk8z8BKs1AjT5SSko7yY2Vikx/LHBdSv/+0oaXMrRUtlVaOVKMWH7vCTmym
	8sD3XLdQctiggTxfKSTDmIXPQAnC0MIGp7ysw4u3x02O+Jda7eeJvl3jPXnFpz4bqlea
	yI6QT9xvMKveM39UhyxVTCMoS4LqK+6Bq+XG+7kufNkvuc1BrQfy/xl+a9WSubRkpKVq
	rU3TuueuV84ruHf/dMtrNbD3D0+OPHV55gG9qgZ50PW0z6WD4E1ENgRU/lJ0OSHUdnD0
	s8tlT3a4AHNQmpG99LV0NViRi+tCK9vENHFJVaXtRl6IE9trVrBfd2towmu1+SBTuOXy
	9EuA==
MIME-Version: 1.0
X-Received: by 10.152.20.165 with SMTP id o5mr3924628lae.78.1406309753482;
	Fri, 25 Jul 2014 10:35:53 -0700 (PDT)
Received: by 10.112.22.39 with HTTP; Fri, 25 Jul 2014 10:35:53 -0700 (PDT)
Date: Fri, 25 Jul 2014 13:35:53 -0400
X-Google-Sender-Auth: w2YvmkbQh4W3-uTJ4D8oTCdX-U0
Message-ID: <CAHehzX0K3Xd=Ew8jXHuZ6QmL_8LSCGJOd6fED--HJ+g1UHwPKw@mail.gmail.com>
From: Russ Pavlicek <russell.pavlicek@xenproject.org>
To: "xen-users@lists.xen.org" <xen-users@lists.xen.org>,
	xen-devel@lists.xen.org, 
	mirageos-devel@lists.xenproject.org, xs-devel@lists.xenserver.org, 
	xen-api@lists.xen.org
Subject: [Xen-API] Xen Project Document Day is This Wednesday,
	July 30: Beginner's Guide needs
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

This is a reminder that next Wednesday, July 30, is Xen Project Document Day.

Xen Project Document Day is a day to help improve overall Xen Project
documentation, particularly that of the Wiki.

This month, it would be great if we could include the incomplete bits
needed for the Beginner's Guide, including at least one decent diagram
and some of the missing information called out in the Architecture
section:

http://wiki.xenproject.org/wiki/Xen_Project_Beginners_Guide

All the information you need to participate in Document Day is here:

http://wiki.xenproject.org/wiki/Xen_Document_Days

If you get a few moments in the next week, please take a look at the
current TODO list to see other items which need attention:

http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO

So please think about how you can help out.  If you haven't requested
to be made a Wiki editor, save time and do it now so you are ready to
go on Document Day.  Just fill out the form below:

http://xenproject.org/component/content/article/100-misc/145-request-to-be-made-a-wiki-editor.html

We hope to see you Wednesday in #xendocs!

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

From xen-api-bounces@lists.xen.org Fri Jul 25 17:36:04 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Fri, 25 Jul 2014 17:36:04 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1XAjPS-0006v0-QS; Fri, 25 Jul 2014 17:35:58 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <russell.pavlicek.xen@gmail.com>)
	id 1XAjPR-0006ui-KC; Fri, 25 Jul 2014 17:35:57 +0000
Received: from [193.109.254.147:41323] by server-16.bemta-14.messagelabs.com
	id BD/85-14741-C7592D35; Fri, 25 Jul 2014 17:35:56 +0000
X-Env-Sender: russell.pavlicek.xen@gmail.com
X-Msg-Ref: server-2.tower-27.messagelabs.com!1406309753!11849770!1
X-Originating-IP: [209.85.217.173]
X-SpamReason: No, hits=2.5 required=7.0 tests=RCVD_BY_IP,
  SUSPICIOUS_RECIPS
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 28703 invoked from network); 25 Jul 2014 17:35:54 -0000
Received: from mail-lb0-f173.google.com (HELO mail-lb0-f173.google.com)
	(209.85.217.173)
	by server-2.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	25 Jul 2014 17:35:54 -0000
Received: by mail-lb0-f173.google.com with SMTP id p9so3667813lbv.18
	for <multiple recipients>; Fri, 25 Jul 2014 10:35:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:sender:date:message-id:subject:from:to:content-type;
	bh=nAOMfZGKMqhT4JG64nphrc8G6NQLDxto9eK2WeUiF7c=;
	b=cLZ2pukMk8z8BKs1AjT5SSko7yY2Vikx/LHBdSv/+0oaXMrRUtlVaOVKMWH7vCTmym
	8sD3XLdQctiggTxfKSTDmIXPQAnC0MIGp7ysw4u3x02O+Jda7eeJvl3jPXnFpz4bqlea
	yI6QT9xvMKveM39UhyxVTCMoS4LqK+6Bq+XG+7kufNkvuc1BrQfy/xl+a9WSubRkpKVq
	rU3TuueuV84ruHf/dMtrNbD3D0+OPHV55gG9qgZ50PW0z6WD4E1ENgRU/lJ0OSHUdnD0
	s8tlT3a4AHNQmpG99LV0NViRi+tCK9vENHFJVaXtRl6IE9trVrBfd2towmu1+SBTuOXy
	9EuA==
MIME-Version: 1.0
X-Received: by 10.152.20.165 with SMTP id o5mr3924628lae.78.1406309753482;
	Fri, 25 Jul 2014 10:35:53 -0700 (PDT)
Received: by 10.112.22.39 with HTTP; Fri, 25 Jul 2014 10:35:53 -0700 (PDT)
Date: Fri, 25 Jul 2014 13:35:53 -0400
X-Google-Sender-Auth: w2YvmkbQh4W3-uTJ4D8oTCdX-U0
Message-ID: <CAHehzX0K3Xd=Ew8jXHuZ6QmL_8LSCGJOd6fED--HJ+g1UHwPKw@mail.gmail.com>
From: Russ Pavlicek <russell.pavlicek@xenproject.org>
To: "xen-users@lists.xen.org" <xen-users@lists.xen.org>,
	xen-devel@lists.xen.org, 
	mirageos-devel@lists.xenproject.org, xs-devel@lists.xenserver.org, 
	xen-api@lists.xen.org
Subject: [Xen-API] Xen Project Document Day is This Wednesday,
	July 30: Beginner's Guide needs
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

This is a reminder that next Wednesday, July 30, is Xen Project Document Day.

Xen Project Document Day is a day to help improve overall Xen Project
documentation, particularly that of the Wiki.

This month, it would be great if we could include the incomplete bits
needed for the Beginner's Guide, including at least one decent diagram
and some of the missing information called out in the Architecture
section:

http://wiki.xenproject.org/wiki/Xen_Project_Beginners_Guide

All the information you need to participate in Document Day is here:

http://wiki.xenproject.org/wiki/Xen_Document_Days

If you get a few moments in the next week, please take a look at the
current TODO list to see other items which need attention:

http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO

So please think about how you can help out.  If you haven't requested
to be made a Wiki editor, save time and do it now so you are ready to
go on Document Day.  Just fill out the form below:

http://xenproject.org/component/content/article/100-misc/145-request-to-be-made-a-wiki-editor.html

We hope to see you Wednesday in #xendocs!

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

From xen-api-bounces@lists.xen.org Mon Jul 28 08:19:22 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Mon, 28 Jul 2014 08:19:22 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1XBg9K-0007ve-4n; Mon, 28 Jul 2014 08:19:14 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <simon.beaumont@citrix.com>) id 1XBg9I-0007vM-TM
	for xen-api@lists.xen.org; Mon, 28 Jul 2014 08:19:13 +0000
Received: from [85.158.137.68:27313] by server-2.bemta-3.messagelabs.com id
	DB/E7-09149-08706D35; Mon, 28 Jul 2014 08:19:12 +0000
X-Env-Sender: simon.beaumont@citrix.com
X-Msg-Ref: server-9.tower-31.messagelabs.com!1406535549!14633023!1
X-Originating-IP: [185.25.65.24]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 26922 invoked from network); 28 Jul 2014 08:19:09 -0000
Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24)
	by server-9.tower-31.messagelabs.com with SMTP;
	28 Jul 2014 08:19:09 -0000
X-IronPort-AV: E=Sophos;i="5.01,747,1400025600"; d="scan'208";a="23453059"
Received: from unknown (HELO AMSPEX01CL02.citrite.net) ([10.69.60.9])
	by AMSPIP01.EU.Citrix.com with ESMTP; 28 Jul 2014 08:19:09 +0000
Received: from AMSPEX01CL03.citrite.net ([169.254.8.210]) by
	AMSPEX01CL02.citrite.net ([10.69.46.33]) with mapi id 14.03.0181.006;
	Mon, 28 Jul 2014 10:19:08 +0200
From: Simon Beaumont <simon.beaumont@citrix.com>
To: Edgaras Work <syao.work@gmail.com>, "xen-api@lists.xen.org"
	<xen-api@lists.xen.org>
Thread-Topic: [Xen-API] Installing "XenServer" to CentOS 6.5 (using buildroot)
Thread-Index: AQHPoeo44etWJKI+SECjKH2FH3k6Upu1NOnw
Date: Mon, 28 Jul 2014 08:19:07 +0000
Message-ID: <4B8F5D33B081C044AA43634E84ED7F96449A00@AMSPEX01CL03.citrite.net>
References: <CALMrCZ2DhgqV=ArjKFym+3MWMJJ2fAsioVz9Hv_KiV51ecguKA@mail.gmail.com>
In-Reply-To: <CALMrCZ2DhgqV=ArjKFym+3MWMJJ2fAsioVz9Hv_KiV51ecguKA@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.80.3.166]
MIME-Version: 1.0
X-DLP: AMS1
Subject: Re: [Xen-API] Installing "XenServer" to CentOS 6.5 (using buildroot)
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

Edgar,

These haven't been packaged into the RPM. There is an outstanding issue against buildroot you can track.

https://github.com/xenserver/buildroot/issues/495

Si

> -----Original Message-----
> From: xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org] On
> Behalf Of Edgaras Work
> Sent: Thursday 17 July 2014 19:06
> To: xen-api@lists.xen.org
> Subject: [Xen-API] Installing "XenServer" to CentOS 6.5 (using buildroot)
> 
> Hello,
> 
> I did install XenServer to CentOS using
> https://github.com/xenserver/buildroot . but the were a problem, I wanted to
> use "xe-*" console commands but I couldn't do it - the commands were not
> found in the CentOS intallation. So it seems that the buildroot did not
> install all the packages the original XenServer has.
> 
> Is there a way to install those packages?
> Source compile isn't a problem.
> 
> P.S. I am installing CloudStack on Dom0 of Xen. Is there any other way
> setting the config for machine that it would communicate with CloudStack?
> 
> Best regards,
> Edgar
_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

From xen-api-bounces@lists.xen.org Mon Jul 28 08:19:22 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Mon, 28 Jul 2014 08:19:22 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1XBg9K-0007ve-4n; Mon, 28 Jul 2014 08:19:14 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <simon.beaumont@citrix.com>) id 1XBg9I-0007vM-TM
	for xen-api@lists.xen.org; Mon, 28 Jul 2014 08:19:13 +0000
Received: from [85.158.137.68:27313] by server-2.bemta-3.messagelabs.com id
	DB/E7-09149-08706D35; Mon, 28 Jul 2014 08:19:12 +0000
X-Env-Sender: simon.beaumont@citrix.com
X-Msg-Ref: server-9.tower-31.messagelabs.com!1406535549!14633023!1
X-Originating-IP: [185.25.65.24]
X-SpamReason: No, hits=0.0 required=7.0 tests=
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 26922 invoked from network); 28 Jul 2014 08:19:09 -0000
Received: from smtp.ctxuk.citrix.com (HELO SMTP.EU.CITRIX.COM) (185.25.65.24)
	by server-9.tower-31.messagelabs.com with SMTP;
	28 Jul 2014 08:19:09 -0000
X-IronPort-AV: E=Sophos;i="5.01,747,1400025600"; d="scan'208";a="23453059"
Received: from unknown (HELO AMSPEX01CL02.citrite.net) ([10.69.60.9])
	by AMSPIP01.EU.Citrix.com with ESMTP; 28 Jul 2014 08:19:09 +0000
Received: from AMSPEX01CL03.citrite.net ([169.254.8.210]) by
	AMSPEX01CL02.citrite.net ([10.69.46.33]) with mapi id 14.03.0181.006;
	Mon, 28 Jul 2014 10:19:08 +0200
From: Simon Beaumont <simon.beaumont@citrix.com>
To: Edgaras Work <syao.work@gmail.com>, "xen-api@lists.xen.org"
	<xen-api@lists.xen.org>
Thread-Topic: [Xen-API] Installing "XenServer" to CentOS 6.5 (using buildroot)
Thread-Index: AQHPoeo44etWJKI+SECjKH2FH3k6Upu1NOnw
Date: Mon, 28 Jul 2014 08:19:07 +0000
Message-ID: <4B8F5D33B081C044AA43634E84ED7F96449A00@AMSPEX01CL03.citrite.net>
References: <CALMrCZ2DhgqV=ArjKFym+3MWMJJ2fAsioVz9Hv_KiV51ecguKA@mail.gmail.com>
In-Reply-To: <CALMrCZ2DhgqV=ArjKFym+3MWMJJ2fAsioVz9Hv_KiV51ecguKA@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.80.3.166]
MIME-Version: 1.0
X-DLP: AMS1
Subject: Re: [Xen-API] Installing "XenServer" to CentOS 6.5 (using buildroot)
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

Edgar,

These haven't been packaged into the RPM. There is an outstanding issue against buildroot you can track.

https://github.com/xenserver/buildroot/issues/495

Si

> -----Original Message-----
> From: xen-api-bounces@lists.xen.org [mailto:xen-api-bounces@lists.xen.org] On
> Behalf Of Edgaras Work
> Sent: Thursday 17 July 2014 19:06
> To: xen-api@lists.xen.org
> Subject: [Xen-API] Installing "XenServer" to CentOS 6.5 (using buildroot)
> 
> Hello,
> 
> I did install XenServer to CentOS using
> https://github.com/xenserver/buildroot . but the were a problem, I wanted to
> use "xe-*" console commands but I couldn't do it - the commands were not
> found in the CentOS intallation. So it seems that the buildroot did not
> install all the packages the original XenServer has.
> 
> Is there a way to install those packages?
> Source compile isn't a problem.
> 
> P.S. I am installing CloudStack on Dom0 of Xen. Is there any other way
> setting the config for machine that it would communicate with CloudStack?
> 
> Best regards,
> Edgar
_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

From xen-api-bounces@lists.xen.org Mon Jul 28 17:33:22 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Mon, 28 Jul 2014 17:33:22 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1XBonV-0007Nn-3A; Mon, 28 Jul 2014 17:33:17 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <jesse.benedict@citrix.com>)
	id 1XBonT-0007NH-Uz; Mon, 28 Jul 2014 17:33:16 +0000
Received: from [85.158.143.35:23844] by server-3.bemta-4.messagelabs.com id
	FD/0C-06192-A5986D35; Mon, 28 Jul 2014 17:33:14 +0000
X-Env-Sender: jesse.benedict@citrix.com
X-Msg-Ref: server-8.tower-21.messagelabs.com!1406568791!11997051!1
X-Originating-IP: [66.165.176.63]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 13496 invoked from network); 28 Jul 2014 17:33:13 -0000
Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63)
	by server-8.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	28 Jul 2014 17:33:13 -0000
X-IronPort-AV: E=Sophos;i="5.01,750,1400025600"; d="scan'208";a="156988745"
Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net)
	([10.9.154.239])
	by FTLPIPO02.CITRIX.COM with ESMTP; 28 Jul 2014 17:33:02 +0000
Received: from FTLPEX01CL02.citrite.net ([169.254.2.156]) by
	FTLPEX01CL03.citrite.net ([169.254.1.212]) with mapi id 14.03.0181.006;
	Mon, 28 Jul 2014 13:33:02 -0400
From: Jesse Benedict <jesse.benedict@citrix.com>
To: "xs-devel@lists.xenserver.org" <xs-devel@lists.xenserver.org>,
	"xen-users@lists.xen.org" <xen-users@lists.xen.org>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	"mirageos-devel@lists.xenproject.org"
	<mirageos-devel@lists.xenproject.org>, 
	"xen-api@lists.xen.org" <xen-api@lists.xen.org>
Thread-Topic: [xs-devel] Xen Project Document Day is This Wednesday, July
	30: Beginner's Guide needs
Thread-Index: AQHPqC8oK7lysQMLVk6yUCHXUHMEfpu1ww/w
Date: Mon, 28 Jul 2014 17:33:02 +0000
Message-ID: <B8C24FCCBFC459419478083491FF39E246E8E0@FTLPEX01CL02.citrite.net>
References: <CAHehzX0K3Xd=Ew8jXHuZ6QmL_8LSCGJOd6fED--HJ+g1UHwPKw@mail.gmail.com>
In-Reply-To: <CAHehzX0K3Xd=Ew8jXHuZ6QmL_8LSCGJOd6fED--HJ+g1UHwPKw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.11.24.218]
MIME-Version: 1.0
X-DLP: MIA1
Subject: Re: [Xen-API] [xs-devel] Xen Project Document Day is This Wednesday,
 July 30: Beginner's Guide needs
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

Without being daft --

XenServer is not greedy: ergo why we have 2 4GiB partitions.  It is the Guest VMs which are greedy, but most importantly: Xen disk management, such as syslog, patches, etc.

4GiB is PLENTY of space to work with so long as a System Administrator ensures an healthy system.

Need any documentation on disk management?  Specifically, for beginners, Syslog, logrotate, etc?

Sincerely,

Jesse Benedict, CCA | Citrix, Inc. | XenServer, XenClient Support Team
Work Better.  Live Better.  Call us at 1-800-4CITRIX!


-----Original Message-----
From: russell.pavlicek.xen@gmail.com [mailto:russell.pavlicek.xen@gmail.com] On Behalf Of Russ Pavlicek
Sent: Friday, July 25, 2014 1:36 PM
To: xen-users@lists.xen.org; xen-devel@lists.xen.org; mirageos-devel@lists.xenproject.org; xs-devel@lists.xenserver.org; xen-api@lists.xen.org
Subject: [xs-devel] Xen Project Document Day is This Wednesday, July 30: Beginner's Guide needs

This is a reminder that next Wednesday, July 30, is Xen Project Document Day.

Xen Project Document Day is a day to help improve overall Xen Project documentation, particularly that of the Wiki.

This month, it would be great if we could include the incomplete bits needed for the Beginner's Guide, including at least one decent diagram and some of the missing information called out in the Architecture
section:

http://wiki.xenproject.org/wiki/Xen_Project_Beginners_Guide

All the information you need to participate in Document Day is here:

http://wiki.xenproject.org/wiki/Xen_Document_Days

If you get a few moments in the next week, please take a look at the current TODO list to see other items which need attention:

http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO

So please think about how you can help out.  If you haven't requested to be made a Wiki editor, save time and do it now so you are ready to go on Document Day.  Just fill out the form below:

http://xenproject.org/component/content/article/100-misc/145-request-to-be-made-a-wiki-editor.html

We hope to see you Wednesday in #xendocs!

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

From xen-api-bounces@lists.xen.org Mon Jul 28 17:33:22 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Mon, 28 Jul 2014 17:33:22 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1XBonV-0007Nn-3A; Mon, 28 Jul 2014 17:33:17 +0000
Received: from mail6.bemta4.messagelabs.com ([85.158.143.247])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <jesse.benedict@citrix.com>)
	id 1XBonT-0007NH-Uz; Mon, 28 Jul 2014 17:33:16 +0000
Received: from [85.158.143.35:23844] by server-3.bemta-4.messagelabs.com id
	FD/0C-06192-A5986D35; Mon, 28 Jul 2014 17:33:14 +0000
X-Env-Sender: jesse.benedict@citrix.com
X-Msg-Ref: server-8.tower-21.messagelabs.com!1406568791!11997051!1
X-Originating-IP: [66.165.176.63]
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
	VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 13496 invoked from network); 28 Jul 2014 17:33:13 -0000
Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63)
	by server-8.tower-21.messagelabs.com with RC4-SHA encrypted SMTP;
	28 Jul 2014 17:33:13 -0000
X-IronPort-AV: E=Sophos;i="5.01,750,1400025600"; d="scan'208";a="156988745"
Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net)
	([10.9.154.239])
	by FTLPIPO02.CITRIX.COM with ESMTP; 28 Jul 2014 17:33:02 +0000
Received: from FTLPEX01CL02.citrite.net ([169.254.2.156]) by
	FTLPEX01CL03.citrite.net ([169.254.1.212]) with mapi id 14.03.0181.006;
	Mon, 28 Jul 2014 13:33:02 -0400
From: Jesse Benedict <jesse.benedict@citrix.com>
To: "xs-devel@lists.xenserver.org" <xs-devel@lists.xenserver.org>,
	"xen-users@lists.xen.org" <xen-users@lists.xen.org>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	"mirageos-devel@lists.xenproject.org"
	<mirageos-devel@lists.xenproject.org>, 
	"xen-api@lists.xen.org" <xen-api@lists.xen.org>
Thread-Topic: [xs-devel] Xen Project Document Day is This Wednesday, July
	30: Beginner's Guide needs
Thread-Index: AQHPqC8oK7lysQMLVk6yUCHXUHMEfpu1ww/w
Date: Mon, 28 Jul 2014 17:33:02 +0000
Message-ID: <B8C24FCCBFC459419478083491FF39E246E8E0@FTLPEX01CL02.citrite.net>
References: <CAHehzX0K3Xd=Ew8jXHuZ6QmL_8LSCGJOd6fED--HJ+g1UHwPKw@mail.gmail.com>
In-Reply-To: <CAHehzX0K3Xd=Ew8jXHuZ6QmL_8LSCGJOd6fED--HJ+g1UHwPKw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.11.24.218]
MIME-Version: 1.0
X-DLP: MIA1
Subject: Re: [Xen-API] [xs-devel] Xen Project Document Day is This Wednesday,
 July 30: Beginner's Guide needs
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

Without being daft --

XenServer is not greedy: ergo why we have 2 4GiB partitions.  It is the Guest VMs which are greedy, but most importantly: Xen disk management, such as syslog, patches, etc.

4GiB is PLENTY of space to work with so long as a System Administrator ensures an healthy system.

Need any documentation on disk management?  Specifically, for beginners, Syslog, logrotate, etc?

Sincerely,

Jesse Benedict, CCA | Citrix, Inc. | XenServer, XenClient Support Team
Work Better.  Live Better.  Call us at 1-800-4CITRIX!


-----Original Message-----
From: russell.pavlicek.xen@gmail.com [mailto:russell.pavlicek.xen@gmail.com] On Behalf Of Russ Pavlicek
Sent: Friday, July 25, 2014 1:36 PM
To: xen-users@lists.xen.org; xen-devel@lists.xen.org; mirageos-devel@lists.xenproject.org; xs-devel@lists.xenserver.org; xen-api@lists.xen.org
Subject: [xs-devel] Xen Project Document Day is This Wednesday, July 30: Beginner's Guide needs

This is a reminder that next Wednesday, July 30, is Xen Project Document Day.

Xen Project Document Day is a day to help improve overall Xen Project documentation, particularly that of the Wiki.

This month, it would be great if we could include the incomplete bits needed for the Beginner's Guide, including at least one decent diagram and some of the missing information called out in the Architecture
section:

http://wiki.xenproject.org/wiki/Xen_Project_Beginners_Guide

All the information you need to participate in Document Day is here:

http://wiki.xenproject.org/wiki/Xen_Document_Days

If you get a few moments in the next week, please take a look at the current TODO list to see other items which need attention:

http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO

So please think about how you can help out.  If you haven't requested to be made a Wiki editor, save time and do it now so you are ready to go on Document Day.  Just fill out the form below:

http://xenproject.org/component/content/article/100-misc/145-request-to-be-made-a-wiki-editor.html

We hope to see you Wednesday in #xendocs!

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

From xen-api-bounces@lists.xen.org Tue Jul 29 11:49:41 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 29 Jul 2014 11:49:41 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1XC5uM-0008F8-FW; Tue, 29 Jul 2014 11:49:30 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <lars.kurth.xen@gmail.com>)
	id 1XC5uL-0008Ex-32; Tue, 29 Jul 2014 11:49:29 +0000
Received: from [85.158.137.68:19221] by server-16.bemta-3.messagelabs.com id
	C0/B9-14115-84A87D35; Tue, 29 Jul 2014 11:49:28 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-2.tower-31.messagelabs.com!1406634566!18540675!1
X-Originating-IP: [74.125.82.169]
X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14,
	spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 23615 invoked from network); 29 Jul 2014 11:49:27 -0000
Received: from mail-we0-f169.google.com (HELO mail-we0-f169.google.com)
	(74.125.82.169)
	by server-2.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	29 Jul 2014 11:49:27 -0000
Received: by mail-we0-f169.google.com with SMTP id u56so8916049wes.0
	for <multiple recipients>; Tue, 29 Jul 2014 04:49:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=content-type:mime-version:subject:from:in-reply-to:date:cc
	:content-transfer-encoding:message-id:references:to;
	bh=Ff5ovejwZ3ViLXBPARXbHx/3gkhkQzSAxRsK7NJ7rQQ=;
	b=rD+RLqfY4VAjUH1ZHg8SfsPg5RKNmCJa8f7ft7JKPa2mPDnvSWvEF+tWnmD7KSQXFt
	zHJCUrQU1mIAn+pXvftF2vE7ZPAThnZIeVa9gCSTPzfkbcT2hZpAqrIQQWjgLd85g/mV
	Z8si5hlo4TLlL+Qls9/19kM79nRLI4Put5GdAxHhpHqt6h4imUdziK5RhYozKoQSpg8N
	srFYc/yPSvtJRcWYJyT33QibHJO0bI9x5tg9h70k5bbcjNIxz43Q4FkKUA2mUcPT20Ug
	fJcnoCM71YbLGv5UxO+12UxQUxNaccMH2JOAjIQbA+MR1Nc9g1Dgw927deMXqltLFKI0
	nTfA==
X-Received: by 10.180.90.233 with SMTP id bz9mr5478013wib.42.1406634565210;
	Tue, 29 Jul 2014 04:49:25 -0700 (PDT)
Received: from [192.168.0.25] (97e5a05a.skybroadband.com. [151.229.160.90])
	by mx.google.com with ESMTPSA id
	ey16sm42561322wid.14.2014.07.29.04.49.22 for <multiple recipients>
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Tue, 29 Jul 2014 04:49:24 -0700 (PDT)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Lars Kurth <lars.kurth.xen@gmail.com>
In-Reply-To: <53C50EBE.40107@xen.org>
Date: Tue, 29 Jul 2014 12:49:19 +0100
Message-Id: <E1784113-2043-4EF3-9C9B-6796C490D4CC@gmail.com>
References: <53C50EBE.40107@xen.org>
To: "lars.kurth@xenproject.org" <lars.kurth@xenproject.org>
X-Mailer: Apple Mail (2.1878.6)
Cc: xen-devel <xen-devel@lists.xenproject.org>,
	advisory-board@lists.xenproject.org,
	Artem Mygaiev <artem.mygaiev@globallogic.com>,
	Alex Agizim <alex.agizim@globallogic.com>,
	"xen-api@lists.xenproject.org" <xen-api@lists.xenproject.org>
Subject: [Xen-API] [Vote Results] Embedded and Automotive PV Drivers Project
	Proposal - closes July 23rd
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

Hi all,
I just counted the votes and we have 5 in favour and no against. That means the proposal carries
Lars

On 15 Jul 2014, at 12:21, Lars Kurth <lars.kurth@xen.org> wrote:

> Hi all,
> 
> in accordance with http://xenproject.org/governance.html it is time to vote on "Embedded and Automotive PV Drivers Project Proposal" (or http://wiki.xenproject.org/wiki/Embedded_and_Automotive_PV_Drivers_Project_Proposal). The vote is open for a week as usual.
> 
> All maintainers of mature Xen Project sub-projects can vote, which includes the Hypervisor and XAPI project. The list of eligable people are
> * Hypervisor : see http://xenbits.xenproject.org/gitweb/?p=xen.git;a=blob;f=MAINTAINERS;hb=HEAD
> * XAPI :  see http://xenproject.org/developers/teams/xapi.html, note that XAPI PROJECT LEADS & COMMITERS and MAINTAINERS are listed on   https://github.com/xapi-project/xen-api
> 
> If you are in favour, reply "+1" to this thread
> If you do not care, reply "0"
> If you object, reply "-1" with a comment justifying the objection
> 
> Best Regards
> Lars


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

From xen-api-bounces@lists.xen.org Tue Jul 29 11:49:41 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Tue, 29 Jul 2014 11:49:41 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1XC5uM-0008F8-FW; Tue, 29 Jul 2014 11:49:30 +0000
Received: from mail6.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <lars.kurth.xen@gmail.com>)
	id 1XC5uL-0008Ex-32; Tue, 29 Jul 2014 11:49:29 +0000
Received: from [85.158.137.68:19221] by server-16.bemta-3.messagelabs.com id
	C0/B9-14115-84A87D35; Tue, 29 Jul 2014 11:49:28 +0000
X-Env-Sender: lars.kurth.xen@gmail.com
X-Msg-Ref: server-2.tower-31.messagelabs.com!1406634566!18540675!1
X-Originating-IP: [74.125.82.169]
X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14,
	spamassassin: 
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 23615 invoked from network); 29 Jul 2014 11:49:27 -0000
Received: from mail-we0-f169.google.com (HELO mail-we0-f169.google.com)
	(74.125.82.169)
	by server-2.tower-31.messagelabs.com with RC4-SHA encrypted SMTP;
	29 Jul 2014 11:49:27 -0000
Received: by mail-we0-f169.google.com with SMTP id u56so8916049wes.0
	for <multiple recipients>; Tue, 29 Jul 2014 04:49:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=content-type:mime-version:subject:from:in-reply-to:date:cc
	:content-transfer-encoding:message-id:references:to;
	bh=Ff5ovejwZ3ViLXBPARXbHx/3gkhkQzSAxRsK7NJ7rQQ=;
	b=rD+RLqfY4VAjUH1ZHg8SfsPg5RKNmCJa8f7ft7JKPa2mPDnvSWvEF+tWnmD7KSQXFt
	zHJCUrQU1mIAn+pXvftF2vE7ZPAThnZIeVa9gCSTPzfkbcT2hZpAqrIQQWjgLd85g/mV
	Z8si5hlo4TLlL+Qls9/19kM79nRLI4Put5GdAxHhpHqt6h4imUdziK5RhYozKoQSpg8N
	srFYc/yPSvtJRcWYJyT33QibHJO0bI9x5tg9h70k5bbcjNIxz43Q4FkKUA2mUcPT20Ug
	fJcnoCM71YbLGv5UxO+12UxQUxNaccMH2JOAjIQbA+MR1Nc9g1Dgw927deMXqltLFKI0
	nTfA==
X-Received: by 10.180.90.233 with SMTP id bz9mr5478013wib.42.1406634565210;
	Tue, 29 Jul 2014 04:49:25 -0700 (PDT)
Received: from [192.168.0.25] (97e5a05a.skybroadband.com. [151.229.160.90])
	by mx.google.com with ESMTPSA id
	ey16sm42561322wid.14.2014.07.29.04.49.22 for <multiple recipients>
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Tue, 29 Jul 2014 04:49:24 -0700 (PDT)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Lars Kurth <lars.kurth.xen@gmail.com>
In-Reply-To: <53C50EBE.40107@xen.org>
Date: Tue, 29 Jul 2014 12:49:19 +0100
Message-Id: <E1784113-2043-4EF3-9C9B-6796C490D4CC@gmail.com>
References: <53C50EBE.40107@xen.org>
To: "lars.kurth@xenproject.org" <lars.kurth@xenproject.org>
X-Mailer: Apple Mail (2.1878.6)
Cc: xen-devel <xen-devel@lists.xenproject.org>,
	advisory-board@lists.xenproject.org,
	Artem Mygaiev <artem.mygaiev@globallogic.com>,
	Alex Agizim <alex.agizim@globallogic.com>,
	"xen-api@lists.xenproject.org" <xen-api@lists.xenproject.org>
Subject: [Xen-API] [Vote Results] Embedded and Automotive PV Drivers Project
	Proposal - closes July 23rd
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

Hi all,
I just counted the votes and we have 5 in favour and no against. That means the proposal carries
Lars

On 15 Jul 2014, at 12:21, Lars Kurth <lars.kurth@xen.org> wrote:

> Hi all,
> 
> in accordance with http://xenproject.org/governance.html it is time to vote on "Embedded and Automotive PV Drivers Project Proposal" (or http://wiki.xenproject.org/wiki/Embedded_and_Automotive_PV_Drivers_Project_Proposal). The vote is open for a week as usual.
> 
> All maintainers of mature Xen Project sub-projects can vote, which includes the Hypervisor and XAPI project. The list of eligable people are
> * Hypervisor : see http://xenbits.xenproject.org/gitweb/?p=xen.git;a=blob;f=MAINTAINERS;hb=HEAD
> * XAPI :  see http://xenproject.org/developers/teams/xapi.html, note that XAPI PROJECT LEADS & COMMITERS and MAINTAINERS are listed on   https://github.com/xapi-project/xen-api
> 
> If you are in favour, reply "+1" to this thread
> If you do not care, reply "0"
> If you object, reply "-1" with a comment justifying the objection
> 
> Best Regards
> Lars


_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

From xen-api-bounces@lists.xen.org Wed Jul 30 03:21:15 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 30 Jul 2014 03:21:15 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1XCKRr-0006pe-Kp; Wed, 30 Jul 2014 03:21:03 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <russell.pavlicek.xen@gmail.com>)
	id 1XCKRq-0006pK-60; Wed, 30 Jul 2014 03:21:02 +0000
Received: from [193.109.254.147:58469] by server-3.bemta-14.messagelabs.com id
	57/04-23707-D9468D35; Wed, 30 Jul 2014 03:21:01 +0000
X-Env-Sender: russell.pavlicek.xen@gmail.com
X-Msg-Ref: server-4.tower-27.messagelabs.com!1406690459!12587672!1
X-Originating-IP: [209.85.215.53]
X-SpamReason: No, hits=2.5 required=7.0 tests=RCVD_BY_IP,
  SUSPICIOUS_RECIPS
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 27570 invoked from network); 30 Jul 2014 03:21:00 -0000
Received: from mail-la0-f53.google.com (HELO mail-la0-f53.google.com)
	(209.85.215.53)
	by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	30 Jul 2014 03:21:00 -0000
Received: by mail-la0-f53.google.com with SMTP id gl10so409196lab.26
	for <multiple recipients>; Tue, 29 Jul 2014 20:20:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:sender:date:message-id:subject:from:to:content-type;
	bh=M40nNNPxFo/D1A/im50h5zjAeb3gbNRNBtVUKNxA9+o=;
	b=PQOKohJR050BmMrfvJSGEiVDQoWxO5OGh6JJsAEdmn1+kh4H8TjX0itMtepaunk0OT
	eNQdD7Nl20IAyOjsYHQSYEkCQM+Sw2xUrwG5GjFcGu1wbWNIXowaBchcO7wzciyZvBfX
	O+6pvNppgMV/VP9QzeMt93R8HmDlToEYWhdsgdlOUEuKS9zNGJs1uPQJZf/GczGb03og
	ImJlrzF+qMRF5+zsyO0mHbUXKjlTJfoAuD3cYFGnsioH6PgFrKfmsbPeDe50q2px4fX1
	9rFfVGVpGhJnyvKe7YxtSiakqIGqd5dClFA7Tz6KE4pdpBK55lDX+Fa2fc+jkyrX6JFW
	slsA==
MIME-Version: 1.0
X-Received: by 10.152.216.228 with SMTP id ot4mr1138165lac.40.1406690459520;
	Tue, 29 Jul 2014 20:20:59 -0700 (PDT)
Received: by 10.112.22.39 with HTTP; Tue, 29 Jul 2014 20:20:59 -0700 (PDT)
Date: Tue, 29 Jul 2014 23:20:59 -0400
X-Google-Sender-Auth: 4ekWGz4H78hRaKePXgkikAVOVk4
Message-ID: <CAHehzX3-j_Ja5DngK4Ut4V77SW1W_9kKb-aVQZ59zpX=bdMGrA@mail.gmail.com>
From: Russ Pavlicek <russell.pavlicek@xenproject.org>
To: "xen-users@lists.xen.org" <xen-users@lists.xen.org>,
	mirageos-devel@lists.xenproject.org, 
	xs-devel@lists.xenserver.org, xen-api@lists.xen.org,
	xen-devel@lists.xen.org
Subject: [Xen-API] Today is Xen Project Document Day!
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

As I mentioned last week, it would be great if we could include the
incomplete bits needed for the Beginner's Guide, including at least
one decent diagram and some of the missing information called out in
the Architecture section:

http://wiki.xenproject.org/wiki/Xen_Project_Beginners_Guide

And given the release of Mirage V2, I'm sure we'll want a good
overview document with links to the recent docs and blogs on the
Mirage site.

As usual, all the information you need to participate in Document Day is here:

http://wiki.xenproject.org/wiki/Xen_Document_Days

And here is the current TODO list to see other items which need attention:

http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO

If you haven't requested to be made a Wiki editor, just fill out the form below:

http://xenproject.org/component/content/article/100-misc/145-request-to-be-made-a-wiki-editor.html

And then join us on #xendocs to synchronize activities.

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

From xen-api-bounces@lists.xen.org Wed Jul 30 03:21:15 2014
Return-path: <xen-api-bounces@lists.xen.org>
Envelope-to: archives@lists.xen.org
Delivery-date: Wed, 30 Jul 2014 03:21:15 +0000
Received: from localhost ([127.0.0.1] helo=lists.xen.org)
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <xen-api-bounces@lists.xen.org>)
	id 1XCKRr-0006pe-Kp; Wed, 30 Jul 2014 03:21:03 +0000
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <russell.pavlicek.xen@gmail.com>)
	id 1XCKRq-0006pK-60; Wed, 30 Jul 2014 03:21:02 +0000
Received: from [193.109.254.147:58469] by server-3.bemta-14.messagelabs.com id
	57/04-23707-D9468D35; Wed, 30 Jul 2014 03:21:01 +0000
X-Env-Sender: russell.pavlicek.xen@gmail.com
X-Msg-Ref: server-4.tower-27.messagelabs.com!1406690459!12587672!1
X-Originating-IP: [209.85.215.53]
X-SpamReason: No, hits=2.5 required=7.0 tests=RCVD_BY_IP,
  SUSPICIOUS_RECIPS
X-StarScan-Received: 
X-StarScan-Version: 6.11.3; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 27570 invoked from network); 30 Jul 2014 03:21:00 -0000
Received: from mail-la0-f53.google.com (HELO mail-la0-f53.google.com)
	(209.85.215.53)
	by server-4.tower-27.messagelabs.com with RC4-SHA encrypted SMTP;
	30 Jul 2014 03:21:00 -0000
Received: by mail-la0-f53.google.com with SMTP id gl10so409196lab.26
	for <multiple recipients>; Tue, 29 Jul 2014 20:20:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:sender:date:message-id:subject:from:to:content-type;
	bh=M40nNNPxFo/D1A/im50h5zjAeb3gbNRNBtVUKNxA9+o=;
	b=PQOKohJR050BmMrfvJSGEiVDQoWxO5OGh6JJsAEdmn1+kh4H8TjX0itMtepaunk0OT
	eNQdD7Nl20IAyOjsYHQSYEkCQM+Sw2xUrwG5GjFcGu1wbWNIXowaBchcO7wzciyZvBfX
	O+6pvNppgMV/VP9QzeMt93R8HmDlToEYWhdsgdlOUEuKS9zNGJs1uPQJZf/GczGb03og
	ImJlrzF+qMRF5+zsyO0mHbUXKjlTJfoAuD3cYFGnsioH6PgFrKfmsbPeDe50q2px4fX1
	9rFfVGVpGhJnyvKe7YxtSiakqIGqd5dClFA7Tz6KE4pdpBK55lDX+Fa2fc+jkyrX6JFW
	slsA==
MIME-Version: 1.0
X-Received: by 10.152.216.228 with SMTP id ot4mr1138165lac.40.1406690459520;
	Tue, 29 Jul 2014 20:20:59 -0700 (PDT)
Received: by 10.112.22.39 with HTTP; Tue, 29 Jul 2014 20:20:59 -0700 (PDT)
Date: Tue, 29 Jul 2014 23:20:59 -0400
X-Google-Sender-Auth: 4ekWGz4H78hRaKePXgkikAVOVk4
Message-ID: <CAHehzX3-j_Ja5DngK4Ut4V77SW1W_9kKb-aVQZ59zpX=bdMGrA@mail.gmail.com>
From: Russ Pavlicek <russell.pavlicek@xenproject.org>
To: "xen-users@lists.xen.org" <xen-users@lists.xen.org>,
	mirageos-devel@lists.xenproject.org, 
	xs-devel@lists.xenserver.org, xen-api@lists.xen.org,
	xen-devel@lists.xen.org
Subject: [Xen-API] Today is Xen Project Document Day!
X-BeenThere: xen-api@lists.xen.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-api@lists.xen.org>
List-Help: <mailto:xen-api-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api>,
	<mailto:xen-api-request@lists.xen.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: xen-api-bounces@lists.xen.org
Errors-To: xen-api-bounces@lists.xen.org

As I mentioned last week, it would be great if we could include the
incomplete bits needed for the Beginner's Guide, including at least
one decent diagram and some of the missing information called out in
the Architecture section:

http://wiki.xenproject.org/wiki/Xen_Project_Beginners_Guide

And given the release of Mirage V2, I'm sure we'll want a good
overview document with links to the recent docs and blogs on the
Mirage site.

As usual, all the information you need to participate in Document Day is here:

http://wiki.xenproject.org/wiki/Xen_Document_Days

And here is the current TODO list to see other items which need attention:

http://wiki.xenproject.org/wiki/Xen_Document_Days/TODO

If you haven't requested to be made a Wiki editor, just fill out the form below:

http://xenproject.org/component/content/article/100-misc/145-request-to-be-made-a-wiki-editor.html

And then join us on #xendocs to synchronize activities.

_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api