Project

General

Profile

Actions

Bug #22143

closed

ceph-iscsi-[config/cli/tools] projects need official RPM builds

Added by Jason Dillaman over 6 years ago. Updated over 5 years ago.

Status:
Resolved
Priority:
High
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

Jenkins is already configured to build unofficial builds, but users need an official repo to download the signed packages.

Actions #1

Updated by Jason Dillaman almost 6 years ago

  • Priority changed from Normal to High
Actions #2

Updated by David Galloway almost 6 years ago

Do the packages need to be in a separate repo? In other words, is there a reason they can't be part of the main Ceph tree and package building process?

Actions #3

Updated by Jason Dillaman almost 6 years ago

@David: I would treat them more like nfs-ganesha releases since they aren't tied to Ceph releases (both can update independently). The three RPMs can be put into a single "ceph-iscsi" repo instead of three separate repos, though.

Actions #4

Updated by David Galloway almost 6 years ago

  • Assignee set to David Galloway

What version number should be used for the $RELEASE variable (this will end up being in the URL on download.ceph.com)?

For example: http://download.ceph.com/nfs-ganesha/

Actions #5

Updated by David Galloway almost 6 years ago

I guess, to clarify, is there a particular RPM or repo I should consider the "source of truth" and use its version and sha1 for the CI?

Actions #6

Updated by Jason Dillaman almost 6 years ago

@David: the officials repos are at [1], [2], and [3]. I would just create a generic "2" $RELEASE for all three projects.

[1] https://github.com/ceph/ceph-iscsi-config
[2] https://github.com/ceph/ceph-iscsi-cli
[3] https://github.com/ceph/ceph-iscsi-tools

Actions #7

Updated by David Galloway almost 6 years ago

What about sha1? If we're going to use a central dir/repo for all three packages, I need a sha1 to feed to the CI at least.

Actions #8

Updated by Jason Dillaman almost 6 years ago

@David: you can always just grab the latest and greatest tag from each repo.

Actions #9

Updated by David Galloway almost 6 years ago

  • Status changed from New to In Progress

Okay, I'm getting close. Is this essentially what you're after?

https://chacra.ceph.com/r/ceph-iscsi/2/267008b9043e119650a09cb164921c97be7f53dc/centos/7/flavors/default/

I still need to write the scripts to sign and push them to download.ceph.com.

Actions #10

Updated by Jason Dillaman almost 6 years ago

@David: yeah, essentially -- but hosted on downloads.ceph.com and properly signed.

Actions #12

Updated by Ben Webber over 5 years ago

@David, I think a newer version of ceph-iscsi-config is needed in the download.ceph.com repo as at the moment I get the following error when I try to install ceph-iscsi-cli:

Error: Package: ceph-iscsi-cli-2.7-2.7.el7.noarch (ceph-iscsi)
Requires: ceph-iscsi-config >= 2.6
Available: ceph-iscsi-config-2.3-2.3.el7.noarch (ceph-iscsi)
ceph-iscsi-config = 2.3-2.3.el7

Actions #13

Updated by David Galloway over 5 years ago

Ben Webber wrote:

@David, I think a newer version of ceph-iscsi-config is needed in the download.ceph.com repo as at the moment I get the following error when I try to install ceph-iscsi-cli:

Error: Package: ceph-iscsi-cli-2.7-2.7.el7.noarch (ceph-iscsi)
Requires: ceph-iscsi-config >= 2.6
Available: ceph-iscsi-config-2.3-2.3.el7.noarch (ceph-iscsi)
ceph-iscsi-config = 2.3-2.3.el7

Thanks. This is fixed!

Actions #14

Updated by David Galloway over 5 years ago

  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF