xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Tomoe Sugihara <sugihara-jCdQPDEk3idL9jVzuh4AOg@public.gmane.org>
To: Dave Scott <Dave.Scott-mvvWK6WmYclDPfheJLI6IQ@public.gmane.org>
Cc: "xen-devel-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org"
	<xen-devel-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org>,
	"xen-api-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org"
	<xen-api-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org>
Subject: Re: RE: [Xen-devel] XCP: request for review a sr driver
Date: Wed, 17 Nov 2010 14:13:25 +0900	[thread overview]
Message-ID: <4CE36475.80402@valinux.co.jp> (raw)
In-Reply-To: <81A73678E76EA642801C8F2E4823AD218080C98B1F-aFusIB7tbcLeU4JHVX8hdHnr0TU713UqXqFh9Ls21Oc@public.gmane.org>

Hi Dave,

Sorry for replying late.

On 07/16/2010 11:01 PM, Dave Scott wrote:
> 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?
>
> 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.


Thank you for the comment, but could you elaborate on the issue?
[ what's wrong with automatic detection by multipathd? ]

I took a look at mpathutil.py, but I couldn't figure out what you mean.
I think I'm missing how XCP uses multipath, so I'd appreciate your comment.

As we added Eucalyptus EBS support for vastsky, now our code for XCP is at:
http://vastsky.svn.sourceforge.net/viewvc/vastsky/trunk/drivers/xcp/

Best,
Tomoe

  
> 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-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org
>> http://lists.xensource.com/xen-devel
>
> _______________________________________________
> xen-api mailing list
> xen-api-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org
> http://lists.xensource.com/mailman/listinfo/xen-api
>

      parent reply	other threads:[~2010-11-17  5:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-07  7:42 XCP: request for review a sr driver YAMAMOTO Takashi
2010-07-16 14:01 ` Dave Scott
2010-07-21  0:47   ` YAMAMOTO Takashi
2010-09-28  9:05     ` YAMAMOTO Takashi
2010-09-29 15:43       ` Jonathan Ludlam
     [not found]   ` <81A73678E76EA642801C8F2E4823AD218080C98B1F-aFusIB7tbcLeU4JHVX8hdHnr0TU713UqXqFh9Ls21Oc@public.gmane.org>
2010-11-17  5:13     ` Tomoe Sugihara [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4CE36475.80402@valinux.co.jp \
    --to=sugihara-jcdqpdek3idl9jvzuh4aog@public.gmane.org \
    --cc=Dave.Scott-mvvWK6WmYclDPfheJLI6IQ@public.gmane.org \
    --cc=xen-api-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org \
    --cc=xen-devel-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).