For some time now, the cephadm "binary" (executable program) has been
being processed specially (extracted from the build packages) and the
resultant single file has been placed in the "build artifacts" directory
of packages:
https://github.com/ceph/ceph-build/pull/1913
and followon bugfix in
https://github.com/ceph/ceph-build/pull/1919
The intent was to have a build-specific place for the appropriate
cephadm for testing, but also to have a stable place in the release
repositories for the unpackaged binary.
This seems to be working for final rpm releases:
http://download.ceph.com/rpm-17.2.3/el8/noarch/cephadm
and development rpm releases:
https://3.chacra.ceph.com/r/ceph/wip-yuri4-testing-2022-09-27-1405/cee7690a0a431bd223254670505200901fccbd16/centos/9/flavors/default/noarch/cephadm
but not for deb releases:
http://download.ceph.com/debian-17.2.3/pool/main/c/ceph/
https://4.chacra.ceph.com/r/ceph/wip-yuri4-testing-2022-09-27-1405/cee7690a0a431bd223254670505200901fccbd16/ubuntu/jammy/flavors/default/pool/main/c/ceph/
so something further apparently needs to be done to the deb repo build.
The hope was that, if anything about the build process ever evolved
(like, say, making the cephadm file a zipfile instead of a Python script
:)), this process would be immune to such changes. But we never
finished getting the documentation/recommended practice updated.
On 9/27/2022 11:22 AM, John Mulligan wrote:
Hi all,
As some of you are already aware the orchestration team is working on
refactoring the cephadm command line tool [1]. The first part of the effort:
building cephadm from source files into a consumable "binary" has been done.
When we last discussed the effort in the CLT call a couple of points came up.
First, the current instructions for bootstrapping a system with cephadm
recommends downloading a script directly from github [2] (see "CURL-Based
Installation"). We'd like to keep the general workflow but would need a new
download location for it. Following that, there was a suggestion that
artifacts that are built and provided by the Ceph project should be signed.
In order to proceed with the cephadm effort we're reaching out for help on
getting these tasks done. This is something we need assistance from those more
knowledgeable about the build and website infrastructure. I posted a work-in-
progress PR [3] that starts making related changes to the documentation, but
can't complete it until we have a more concrete plan on where people can
download (and verify) their bootstrap copy of cephadm.
Anyone who has pointers to who are the best team members to follow up with
this effort - please let us know!
Thank you.
-- John Mulligan (on behalf of the Ceph Orchestration team )
[1] - https://pad.ceph.com/p/cephadm-refactoring
[2] - https://docs.ceph.com/en/latest/cephadm/install/
[3] - https://github.com/ceph/ceph/pull/48180
_______________________________________________
Dev mailing list -- dev@xxxxxxx
To unsubscribe send an email to dev-leave@xxxxxxx
_______________________________________________
Dev mailing list -- dev@xxxxxxx
To unsubscribe send an email to dev-leave@xxxxxxx
