[Bugs] [Bug 1215562] New: Package libgfapi-python for its consumers
bugzilla at redhat.com
bugzilla at redhat.com
Mon Apr 27 06:50:48 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1215562
Bug ID: 1215562
Summary: Package libgfapi-python for its consumers
Product: Red Hat Storage
Version: 3.1.0
Component: glusterfs
Sub Component: core
Keywords: Triaged
Severity: high
Priority: high
Assignee: rhs-bugs at redhat.com
Reporter: hchiramm at redhat.com
QA Contact: sdharane at redhat.com
CC: bugs at gluster.org, gluster-bugs at redhat.com,
lans.carstensen at dreamworks.com, rcyriac at redhat.com
Depends On: 1193474
Group: redhat
+++ This bug was initially created as a clone of Bug #1193474 +++
Description of problem:
Currently libgfapi-python is not packaged , so the consumers like vdsm,
openstack.etc are not able to make use of python bindings of libgfapi.
Version-Release number of selected component (if applicable):
N/A
How reproducible:
N/A
Steps to Reproduce:
N/A
Actual results:
No package/rpm shipped for libgfapi-python product.
Expected results:
An rpm named libgfapi-python has to be produced out of 'libgfapi-python'
project in review.gluster.org and has to be shipped with distros like 'fedora'.
Additional info:
--- Additional comment from Humble Chirammal on 2015-02-17 07:43:25 EST ---
The current source of libgfapi-python has subdirs in name 'glusterfs' and
setup.py list 'gfapi' as its name module name. There should be consistency in
name and the consumers should get a better picture from the 'name' itself. As
part of packaging, I have renamed the reference of 'glusterfs' from the source
to 'libgfapi'. The patch is available in review.gluster.org (
http://review.gluster.org/#/c/9668/ ) for the review.
--- Additional comment from Lans Carstensen on 2015-02-17 18:28:44 EST ---
FWIW, I'd recommend a package name of "glusterfs-api-python" for this rpm.
libgfapi bindings work really stems from and requires prior installation of
"glusterfs-api".
--- Additional comment from Lans Carstensen on 2015-02-18 09:50:17 EST ---
I read the review more carefully, please don't bother considering my previous
comment. I was speaking about rpm packaging, not Python module naming.
--- Additional comment from Humble Chirammal on 2015-02-20 00:56:58 EST ---
(In reply to Lans Carstensen from comment #2)
> FWIW, I'd recommend a package name of "glusterfs-api-python" for this rpm.
> libgfapi bindings work really stems from and requires prior installation of
> "glusterfs-api".
Thanks for the suggestion. Yeah, we can keep the 'rpm' name as
'glusterfs-api-python' or similar. We are discussing more on module naming
part at http://review.gluster.org/#/c/9668/ .
--- Additional comment from Humble Chirammal on 2015-04-15 12:24:50 EDT ---
The first draft of spec file is ready for review
@http://review.gluster.org/#/c/10256/ .
The spec file is compatible to make below structure for gluster namespace so
that it is more portable and scalable for future use.
<sitepackages>/gluster/
|
-- __init__.py
|
|
-- glupy
|
-- __init__.py
-- glupy.py
-- ........
|
|
-- gfapi
|
-- __init__.py
-- gfapi.py
-- ........
By above structure clients can import:
>>> from gluster import glupy
>>> from gluster import gfapi
--- Additional comment from Lans Carstensen on 2015-04-15 12:38:14 EDT ---
It's a nitpick, but since "glusterfs" is what's being used instead of "gluster"
for packaging the C API (glusterfs-api) which this package is dependent upon
I'd encourage you to use "glusterfs" here also. Imports would become:
from glusterfs import glupy
from glusterfs import gfapi
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1193474
[Bug 1193474] Package libgfapi-python for its consumers
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=Hzuit9WtUC&a=cc_unsubscribe
More information about the Bugs
mailing list