All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: Native systemd service files for multipathd
Date: Tue, 23 Aug 2011 17:06:09 +0200	[thread overview]
Message-ID: <4E53C1E1.7040504@suse.de> (raw)
In-Reply-To: <CAPXgP12DSQLWmwTcQEOMN4VtY-zAh0OxbW=KLQc+X70nb50sVA@mail.gmail.com>

On 08/22/2011 06:35 PM, Kay Sievers wrote:
> On Mon, Aug 22, 2011 at 17:45, Hannes Reinecke<hare@suse.de>  wrote:
>> On 08/22/2011 03:47 PM, Christophe Varoqui wrote:
>>> On jeu., 2011-06-30 at 14:10 +0000, "Jóhann B. Guðmundsson" wrote:
>>>>
>>>> Is anyone taking a look at porting the multipathd legacy sysv init
>>>> script to native systemd unit file?
>>>>
>>>> I filed 690828 on 2011-03-25 and yet to receive somekind of response on
>>>> it and unless some action is taken then a) device-mapper-multipath will
>>>> be blocking the Fedora 16 alpha release or b) be ripped out of @base and
>>>> be made sure it does not get installed on the official livecd.
>>>>
>>> What is the status of this request ? Has anyone stepped-in to the job ?
>>> If not I'll look into it. If you have Fedora-specific systemd
>>> implementation guideline, please point me to the appropriate
>>> documentation.
>>>
>> I have talked with Kay&  Lennart about this.
>>
>> The main problem here is that we don't / can't know if a device is
>> multipathed or not; this is basically a policy decision.
>> Even a simple switch (multipath on/off) wouldn't suffice here, as this
>> particular device might be excluded via the configuration file.
>>
>> Idea here is to modify the 'multipath' program to determine if a particular
>> device is handled by multipath or not. If so, _no other_ configuration must
>> be done in that device.
>> The multipathd daemon itself already listens on events from the udev socket;
>> it should be pretty trivial to convert that to socket activation.
>>
>> And, of course, we need to solve the mount problem. Last I've heard was that
>> systemd _won't_ be handling mounting, which in effect means we cannot mount
>> any systems provided via multipath ...
>>
>> What is the status here?
>
> It fully support mounts on boot, dynamically created, or on hotplug,
> with or without automounter support.
>
> But it will not assemble/handle/know anything about any dm/md devices.
>
Yeah, but this should taken care of if and when LVM2 and MD gets 
converted to systemd, right ?

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

  reply	other threads:[~2011-08-23 15:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-30 14:10 Native systemd service files for multipathd "Jóhann B. Guðmundsson"
2011-08-22 13:47 ` Christophe Varoqui
2011-08-22 13:57   ` "Jóhann B. Guðmundsson"
2011-08-22 15:45   ` Hannes Reinecke
2011-08-22 16:35     ` Kay Sievers
2011-08-23 15:06       ` Hannes Reinecke [this message]
2011-08-23 15:35         ` Kay Sievers
2011-08-22 16:01   ` Alasdair G Kergon

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=4E53C1E1.7040504@suse.de \
    --to=hare@suse.de \
    --cc=dm-devel@redhat.com \
    --cc=kay.sievers@vrfy.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.