From: Jeff Layton <jlayton@redhat.com>
To: John Spray <jspray@redhat.com>,
Ceph Development <ceph-devel@vger.kernel.org>
Cc: James Page <james.page@canonical.com>,
Tim Serong <tserong@suse.com>, Ken Dreyer <kdreyer@redhat.com>,
Andreas Gruenbacher <agruenba@redhat.com>
Subject: Re: richacl packaging for cephfs
Date: Tue, 20 Sep 2016 11:10:35 -0400 [thread overview]
Message-ID: <1474384235.19989.35.camel@redhat.com> (raw)
In-Reply-To: <CALe9h7f_q9iGzTRYhXHKiNFfn2qKfc-UUh+eWJ_XqTh9YoqQWg@mail.gmail.com>
On Tue, 2016-09-20 at 15:57 +0100, John Spray wrote:
> Hi all,
>
> I was just taking an updated look at how we could proceed to get
> richacl support[1,2,3] built and tested in cephfs (probably for
> luminous).
>
> The packages exist currently for Fedora. For testing, we will need
> them for Ubuntu (probably just Xenial?), CentOS and RHEL (once there
> are RHEL nodes in the sepia lab).
>
> I'm not very aware of ways forward for Ubuntu, but on the CentOS front
> it seems like we have at least a couple of possibilities:
> * Build ourselves (using some branch of the fedora packaging?) on a
> Ceph gitbuilder/jenkins job and install from that repo in teuthology
> jobs
> * Get packages into CentOS Storage SIG and point teuthology at
> external storage SIG repos during testing
>
> I believe we could ask nicely for some help from the storage SIG to
> package richacl, but I'm not immediately sure if that's actually our
> preferred approach for consuming packages in our CI vs. self-building
> anything that's not in the distro.
>
> Does anybody have thoughts on the best way to go?
>
> Would also love to hear any thoughts about richacl SUSE and Ubuntu
>
> John
>
> 1. https://github.com/ceph/ceph/pull/6341
> 2. https://github.com/andreas-gruenbacher/richacl
> 3. http://pkgs.fedoraproject.org/cgit/rpms/richacl.git/
> --
(cc'ing andreas)
There are already richacl packages for Fedora, and the build
requirements are pretty reasonable. Is there any reason not to just ask
for those packages to be added to EPEL7? Should be pretty trivial to
get them built.
In fact, I went ahead and built some candidate packages for el7
directly from the rawhide srpm and it seems to have worked:
http://koji.fedoraproject.org/koji/taskinfo?taskID=15718383
--
Jeff Layton <jlayton@redhat.com>
next prev parent reply other threads:[~2016-09-20 15:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 14:57 richacl packaging for cephfs John Spray
2016-09-20 15:10 ` Jeff Layton [this message]
2016-09-21 11:24 ` Andreas Gruenbacher
2016-09-21 12:19 ` Jeff Layton
2016-09-21 12:59 ` Andreas Gruenbacher
2016-09-22 12:01 ` Andreas Gruenbacher
2016-09-21 11:31 ` Andreas Grünbacher
2016-09-21 12:00 ` John Spray
2016-09-21 12:46 ` Jan Fajerski
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=1474384235.19989.35.camel@redhat.com \
--to=jlayton@redhat.com \
--cc=agruenba@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=james.page@canonical.com \
--cc=jspray@redhat.com \
--cc=kdreyer@redhat.com \
--cc=tserong@suse.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.