All of lore.kernel.org
 help / color / mirror / Atom feed
From: Owen Synge <osynge@suse.com>
To: Sage Weil <sweil@redhat.com>, ceph-devel@vger.kernel.org
Subject: Re: systemd status
Date: Fri, 31 Jul 2015 15:23:26 +0200	[thread overview]
Message-ID: <55BB76CE.9020009@suse.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1507281202370.22099@cobra.newdream.net>

On 07/28/2015 09:13 PM, Sage Weil wrote:
> Hey,
> 
> I've finally had some time to play with the systemd integration branch on 
> fedora 22.  It's in wip-systemd and my current list of issues includes:
> 
> - after mon creation ceph-create-keys isn't run automagically
>   - Personally I kind of hate how it was always run on mon startup and not 
> just during cluster creation so I wouldn't mind *so* much if this became 
> an explicit step, maybe triggered by ceph-deploy, after mon create.

I agree.

> - udev's attempt to trigger ceph-disk isn't working for me.  the osd 
> service gets started but the mount isn't present and it fails to start.

I have not had this issue with suse, I will investigate soon.

> I'm a systemd noob and haven't sorted out how to get udev to log something 
> meaningful to debug it.  Perhaps we should merge in the udev + 
> systemd revamp patches here too...
> 
> - ceph-detect-init is only recently unbroken in master for fedora 22.

noted. I have never yet tested the systemd patches on anything but
opensuse and SLE12.

> - ceph-deploy doesn't know that fedora should be systemd yet.

One of ceph or ceph-deploy has to change this first. I propose ceph.

> - ceph-deploy has a wip-systemd branch with a few things so far:
>   - on mon create, we unconditionally systemctl enable ceph.target.  
> i think osd create and mds create and rgw create should do the same thing, 
> since the ceph.target is a catch-all bucket for any ceph service, and i 
> don't think we want to enable it on install?
>   - rgw create and mds create don't work yet
>   - osd create doesn't enable ceph.target

rgw does work on suse, but I noticed a bug in the patches you where
working on, I am looking at the other issues, you raise.

https://github.com/SUSE/ceph/commit/08c805c18dd994d7b2c4c521a209bb50310b1bbd


Note mds is some thing I have never tested but have never even used the mds.

> - I'm guessing my ceph.spec changes to install teh systemd unit files 
> aren't quite right... please review!  The gitbuilder turnaround is so slow 
> it's hard to iterate and I don't really know what I'm doing here.

Yes I found this too on suse, I think I am near fixing these issues for
suse. Once they are fixed I will once again look at fedora.


Best regards

Owen

  parent reply	other threads:[~2015-07-31 13:25 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-28 19:13 systemd status Sage Weil
2015-07-28 22:16 ` Travis Rhoden
2015-07-29 11:25   ` Alex Elsayed
2015-07-29 12:55     ` Sage Weil
2015-07-29 13:09       ` Wyllys Ingersoll
2015-07-29 14:08       ` Alex Elsayed
2015-07-29 14:19         ` Sage Weil
2015-07-29 14:30           ` Alex Elsayed
2015-07-29 14:53             ` Sage Weil
2015-07-29 15:17               ` Alex Elsayed
2015-07-29 16:50                 ` Vasiliy Angapov
2015-07-31 13:29                   ` Owen Synge
2015-07-30 12:45                 ` Sage Weil
2015-07-30 19:40                   ` Robert LeBlanc
2015-08-03  8:53         ` Owen Synge
2015-07-31  8:11 ` Owen Synge
2015-07-31 13:23 ` Owen Synge [this message]
2015-08-03 19:01 ` Fedora 22 systemd and ceph-deploy Owen Synge
2015-08-03 19:07   ` Sage Weil
2015-08-04 10:13     ` Owen Synge
2015-08-04 12:32       ` Fedora 22 systemd and rgw Owen Synge
2015-08-04 13:07         ` Sage Weil
2015-08-04 16:10           ` Owen Synge

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=55BB76CE.9020009@suse.com \
    --to=osynge@suse.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=sweil@redhat.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 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.