WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-api

RE: [Xen-devel] XCP: request for review a sr driver

To: Dave.Scott@xxxxxxxxxxxxx
Subject: RE: [Xen-devel] XCP: request for review a sr driver
From: yamamoto@xxxxxxxxxxxxx (YAMAMOTO Takashi)
Date: Tue, 28 Sep 2010 18:05:00 +0900 (JST)
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-api@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 28 Sep 2010 02:07:36 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: Your message of "Wed, 21 Jul 2010 09:47:28 +0900 (JST)" <20100721004728.267E57098A@xxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20100721004728.267E57098A@xxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
hi,

> hi,
> 
> thanks for taking a look at this.
> 
>> Hi,
>> 
>>> i think i mostly finished my sr driver for our product.
>>> you can find it at
>>>     http://vastsky.svn.sourceforge.net/viewvc/vastsky/trunk/xcp/
>> 
>> Cool!
>> 
>> How would you like the code to be incorporated? Would it be best to take 
>> infrequent tarball snapshots or to 'svn up' from your repo on every build?
> 
> i'd be happier if this code was kept in the xcp repo.
> when will it be publically available?

i'm still interested in this. 
is there any progress about xcp repo?

YAMAMOTO Takashi

> 
>> 
>> Looking at the driver code I think the only major thing we have to sort out 
>> is the multipath handling. XCP handles multipath in a slightly different way 
>> to standard CentOS. Rather than listen for asynchronous uevents, paths must 
>> be explicitly registered with multipathd -- see mpathutil.py for CLI-like 
>> commands.
> 
> i'll take a look.
> 
> YAMAMOTO Takashi
> 
>> 
>> Cheers,
>> Dave
>> 
>>> 
>>> can someone please review the code and consider to include it in
>>> the xcp distribution?  thanks.
>>> 
>>> YAMAMOTO Takashi
>>> 
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>>> http://lists.xensource.com/xen-devel
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-devel
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>