xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Jim Fehlig <jfehlig@novell.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com, Berthold Gunreben <bg@suse.de>
Subject: Re: [PATCH] xend: drbd improvements
Date: Thu, 16 Dec 2010 17:45:12 -0700	[thread overview]
Message-ID: <4D0AB298.4080202@novell.com> (raw)
In-Reply-To: <4CDADB46.7020100@novell.com>

Jim Fehlig wrote:
> Jim Fehlig wrote:
>   
>> Ian Jackson wrote:
>>   
>>     
>>> Jim Fehlig writes ("[Xen-devel] [PATCH] xend: drbd improvements"):
>>>   
>>>     
>>>       
>>>> xend: drbd improvements
>>>>
>>>> 1) drbdadm state is debrecated, and the script tries to detect the
>>>> primary/secondary information from the deprecated message
>>>> 2) os.popen2 does not work with the array as argument
>>>> 3) popen2 is deprecated since python2.6
>>>>     
>>>>       
>>>>         
>>> Forgive my ignorance, but: why does xend need to mess with drbd at
>>> all ?  Why can't it just open the block device ?
>>>   
>>>     
>>>       
>> Good question.  I too was surprised to see special casing of drbd within
>> xend.  Seems c/s 20158 added this code to allow bootloaders (pygrub,
>> domUloader, et. al.) to work with drbd devices using the 'drbd:resource'
>> syntax.  Perhaps the author of that patch (cc'd) can provide more
>> details.
>>     
>
> The patch author's mail address is no longer valid, so we won't be
> receiving any feedback from him :-(.
>   

Sorry for the delay here, but I finally got around to investigating this
further.  As it turns out, drbd's block-drbd script handles all of the
details that c/s 20158 introduces within xend :-(.  IMO, this c/s should
be reverted as it causes a regression.  I've tested drbd without this
changeset and it works fine.

Regards,
Jim

  reply	other threads:[~2010-12-17  0:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-09 17:50 [PATCH] xend: drbd improvements Jim Fehlig
2010-11-09 18:26 ` Ian Jackson
2010-11-09 22:21   ` Jim Fehlig
2010-11-10 17:49     ` Jim Fehlig
2010-12-17  0:45       ` Jim Fehlig [this message]
2010-12-17  0:58         ` Shriram Rajagopalan
2010-12-17  3:46           ` Jim Fehlig
2011-01-05 23:32         ` Ian Jackson
2011-01-06 17:48           ` Shriram Rajagopalan
2011-01-10 23:31             ` Jim Fehlig
2011-01-13  3:38               ` Jim Fehlig
2011-01-13  7:36                 ` Shriram Rajagopalan
2011-01-13 11:45                 ` Ian Jackson
2011-01-13 15:59                   ` Jim Fehlig
2011-01-18 17:24               ` Ian Jackson

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=4D0AB298.4080202@novell.com \
    --to=jfehlig@novell.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=bg@suse.de \
    --cc=xen-devel@lists.xensource.com \
    /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).