From: Ian Campbell <Ian.Campbell@eu.citrix.com>
To: "rshriram@cs.ubc.ca" <rshriram@cs.ubc.ca>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: xl - no support for DRBD disks?
Date: Mon, 9 May 2011 15:40:01 +0100 [thread overview]
Message-ID: <1304952001.26692.230.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <BANLkTinK45wzJUDfLOAS5ObpiJdqaxMijg@mail.gmail.com>
On Mon, 2011-05-09 at 15:38 +0100, Shriram Rajagopalan wrote:
> On Mon, May 9, 2011 at 3:48 AM, Ian Campbell <Ian.Campbell@citrix.com>
> wrote:
>
> On Sun, 2011-05-08 at 04:24 +0100, Shriram Rajagopalan wrote:
> > I tried to create a domain with drbd based disk as the
> backend
> > "drbd:<resourcename>,..," and I get a "unknown disk type"
> error.
> >
> > I can spin out a patch if needed, but just wanted to know
> apriori if
> > this was left out for any specific reason.
>
>
> Not deliberate AFAIK.
>
> The intention is to make xl callout to a script whose name is
> derived
> from the initial part of the disk definition (e.g. the drdb
> part,
> similarly for iscsi and so on).
>
> So, the "callout to a script" functionality is already available as
> part of the scripts in /etc/xen/scripts/. This includes a call out to
> block-drbd (supplied by DRBD package) block-nbd, block-enbd (supplied
> as part of xen tree). Cant we just re-use them
> or is there some xend specific aspect to those scripts?
The plan is to reuse them.
>
> shriram
>
> IanJ was looking at overhauling disk handling, including that
> functionality.
>
> Ian.
>
>
prev parent reply other threads:[~2011-05-09 14:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-08 3:24 xl - no support for DRBD disks? Shriram Rajagopalan
2011-05-09 8:48 ` Ian Campbell
2011-05-09 14:38 ` Shriram Rajagopalan
2011-05-09 14:40 ` Ian Campbell [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=1304952001.26692.230.camel@zakaz.uk.xensource.com \
--to=ian.campbell@eu.citrix.com \
--cc=rshriram@cs.ubc.ca \
--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).