All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Serong <tserong@suse.com>
To: "HEWLETT, Paul (Paul)** CTR **" <paul.hewlett@alcatel-lucent.com>,
	Gaudenz Steinlin <gaudenz@debian.org>,
	Ken Dreyer <kdreyer@redhat.com>, Sage Weil <sweil@redhat.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
	"cjwatson@debian.org" <cjwatson@debian.org>,
	"ceph-maintainers@ceph.com" <ceph-maintainers@ceph.com>,
	"timm@fnal.gov" <timm@fnal.gov>, Owen Synge <osynge@suse.com>
Subject: Re: [Ceph-maintainers] statically allocated uid/gid for ceph
Date: Tue, 28 Apr 2015 15:00:17 +1000	[thread overview]
Message-ID: <553F13E1.6050207@suse.com> (raw)
In-Reply-To: <B1C372F943D5614C80F90CC0D60D4210485991A2@FR711WXCHMBA04.zeu.alcatel-lucent.com>

On 04/27/2015 09:29 PM, HEWLETT, Paul (Paul)** CTR ** wrote:
> What about making it configurable in ceph.conf or /etc/sysconfig/ceph? (or via PAM/ldap...)
> 
> That way individual users could make it a value that they know does not conflict and they will still be able to
> move OSDs between nodes etc...

IMO that's a bit chicken-and-eggy -- you really want the package to
create the user and group early during install (%pre in an rpm), so
that, say, log file directories and whatnot potentially owned by the
package can be installed with the correct ownership.

Regards,

Tim

> 
> Paul Hewlett
> Senior Systems Engineer
> Velocix, Cambridge
> Alcatel-Lucent
> t: +44 1223 435893
> 
> 
> 
> ________________________________________
> From: ceph-devel-owner@vger.kernel.org [ceph-devel-owner@vger.kernel.org] on behalf of Tim Serong [tserong@suse.com]
> Sent: 27 April 2015 10:56
> To: Gaudenz Steinlin; Ken Dreyer; Sage Weil
> Cc: ceph-devel@vger.kernel.org; cjwatson@debian.org; ceph-maintainers@ceph.com; timm@fnal.gov; Owen Synge
> Subject: Re: [Ceph-maintainers] statically allocated uid/gid for ceph
> 
> On 04/16/2015 03:14 AM, Gaudenz Steinlin wrote:
>>
>> Hi
>>
>> Ken Dreyer <kdreyer@redhat.com> writes:
>>
>>> On 04/14/2015 09:21 AM, Sage Weil wrote:
>>>> I think we still want them to be static across a distro; it's the
>>>> cross-distro change that will be relatively rare.  So a fixed ID from each
>>>> distro family ought to be okay?
>>>
>>> Sounds sane to me. I've filed https://fedorahosted.org/fpc/ticket/524 to
>>> request one from Fedora.
>>
>> I have now requested the same for Debian. If the request is granted we
>> will most likely get the uid/gid 64045. Maybe others could use the same.
>> It seems that only Debian has a range of reserved ids for this purpose.
>> I would expect Ubuntu to use the same id, but that's up to them finally.
> 
> Fedora has rejected the request for a static UID (see
> https://fedorahosted.org/fpc/ticket/524#comment:16), and I haven't made
> much progress on the SUSE front.  I did suggest everyone just do what
> Debian does ;) but both Fedora and SUSE people pointed out that the 64K
> range isn't safe to claim, what with not being specifically reserved.
> 
> I did make one small bit of progress - I've added the ceph user and
> group to rpmlint on openSUSE Factory
> (https://build.opensuse.org/request/show/303537) so at least the SUSE
> build won't bitch if files specified in any of the packages are owned by
> ceph:ceph.
> 
> Regards,
> 
> Tim
> --
> Tim Serong
> Senior Clustering Engineer
> SUSE
> tserong@suse.com
> --
> 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
> 


-- 
Tim Serong
Senior Clustering Engineer
SUSE
tserong@suse.com

  reply	other threads:[~2015-04-28  5:00 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.DEB.2.00.1412061245410.18213@cobra.newdream.net>
     [not found] ` <5488919E.4090109@redhat.com>
2014-12-10 18:48   ` [Ceph-maintainers] statically allocated uid/gid for ceph Sage Weil
2014-12-11  2:07     ` Tim Serong
2014-12-11 22:47       ` John Spray
2015-04-14  1:02       ` Sage Weil
2015-04-14  1:05       ` Sage Weil
2015-04-14  4:03         ` Tim Serong
2015-04-14 15:21           ` Sage Weil
2015-04-14 16:12             ` Ken Dreyer
2015-04-15 17:14               ` Gaudenz Steinlin
2015-04-27  9:56                 ` Tim Serong
2015-04-27 11:29                   ` HEWLETT, Paul (Paul)** CTR **
2015-04-28  5:00                     ` Tim Serong [this message]
2015-04-27 16:02                   ` Sage Weil
2015-05-14 12:16                     ` Tim Serong
2015-05-14 13:53                       ` Ken Dreyer
2015-05-14 16:08                       ` Sage Weil
     [not found]                         ` <CAANLjFpgivwxMhFLy4OcCxnJ_k5ssORCUm2r+BgtU+LEPQmvPw@mail.gmail.com>
2015-05-14 16:20                           ` Robert LeBlanc
2015-05-14 16:41                           ` Sage Weil
2015-05-15  3:27                             ` Tim Serong
2015-05-15 10:25                 ` Colin Watson
2015-04-15 10:32             ` Tim Serong

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=553F13E1.6050207@suse.com \
    --to=tserong@suse.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=ceph-maintainers@ceph.com \
    --cc=cjwatson@debian.org \
    --cc=gaudenz@debian.org \
    --cc=kdreyer@redhat.com \
    --cc=osynge@suse.com \
    --cc=paul.hewlett@alcatel-lucent.com \
    --cc=sweil@redhat.com \
    --cc=timm@fnal.gov \
    /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.