All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Mick <dan.mick@inktank.com>
To: Sage Weil <sage@inktank.com>
Cc: Gregory Farnum <greg@inktank.com>,
	James Page <james.page@ubuntu.com>,
	Mike Dawson <mdawson@gammacode.com>,
	"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: 0.55 init script Issue?
Date: Fri, 07 Dec 2012 13:38:43 -0800	[thread overview]
Message-ID: <50C261E3.4000007@inktank.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1212060534110.13653@cobra.newdream.net>

It did not delete the previously-installed /etc/init/ceph.conf; I'm 
guessing we need a postinstall fragment to do that fixup?

On 12/06/2012 05:35 AM, Sage Weil wrote:
> On Wed, 5 Dec 2012, Sage Weil wrote:
>> On Wed, 5 Dec 2012, Gregory Farnum wrote:
>>> On Wed, Dec 5, 2012 at 12:17 PM, James Page <james.page@ubuntu.com> wrote:
>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>> Hash: SHA256
>>>>
>>>> On 05/12/12 19:41, Dan Mick wrote:
>>>>> The story as best I know it is that we're trying to transition to
>>>>> and use upstart where possible, but that the upstart config does
>>>>> not (yet?) try to do what the init.d config did.  That is, it
>>>>> doesn't support options to the one script, but rather separates
>>>>> daemons into separate services, and does not reach out to remote
>>>>> machines to start daemons, etc.
>>>>>
>>>>> The intent is that init.d/ceph is left for non-Upstart distros,
>>>>> AFAICT.
>>>>>
>>>>> Tv had some design notes here:
>>>>>
>>>>> http://www.mail-archive.com/ceph-devel@vger.kernel.org/msg09314.html
>>>>>
>>>>>   We need better documentation/rationale here at least.
>>>>
>>>> Maybe it might be better if the ceph init script and the ceph upstart
>>>> configuration did not namespace clash; how about shifting the name of
>>>> the ceph upstart configuration to ceph-all?
>>>
>>> Yeah, this or something very similar is definitely the correct
>>> solution. Sage recently added the "ceph" upstart job, and we didn't
>>> put it through sufficient verification prior to release in order to
>>> notice this issue. Users who aren't using upstart (I expect that's all
>>> of them) should just delete the job after running the package install.
>>> We'll certainly sort this out prior to the next release; I'm not sure
>>> if we want to roll a v0.55.1 right away or not.
>>
>> Let's push it to the testing branch, but make sure any other fixes are
>> there before rolling a .1.. maybe tomorrow?
>
> I've pushed this to the testing branch.  If someone wants to verify the
> packages built at
>
> 	http://gitbuilder.ceph.com/ceph-deb-precise-x86_64-basic/ref/testing/
>
> are fixed, that would be fabulous!
>
> sage
>
>
>> Thanks!
>> sage
>>
>>
>>> -Greg
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>>
>>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>>

  reply	other threads:[~2012-12-07 21:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-05 16:15 0.55 init script Issue? Mike Dawson
2012-12-05 17:19 ` Franck Marchand
2012-12-05 18:04 ` James Page
2012-12-05 19:41 ` Dan Mick
2012-12-05 19:57   ` David Zafman
2012-12-05 20:17   ` James Page
2012-12-05 20:39     ` Gregory Farnum
2012-12-06  0:11       ` Sage Weil
2012-12-06  1:34         ` Matthew Via
2012-12-06 13:28           ` Sage Weil
2012-12-06 13:35         ` Sage Weil
2012-12-07 21:38           ` Dan Mick [this message]
2012-12-10  9:13           ` James Page

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=50C261E3.4000007@inktank.com \
    --to=dan.mick@inktank.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=greg@inktank.com \
    --cc=james.page@ubuntu.com \
    --cc=mdawson@gammacode.com \
    --cc=sage@inktank.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.