Project

General

Profile

Actions

Documentation #20309

closed

Manual installation guide needs updates

Added by Jens Harbott almost 7 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
% Done:

0%

Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:

Description

Couple of issues with http://docs.ceph.com/docs/master/install/manual-deployment/

- It doesn't explain how to generate the bootstrap-osd users, so the ceph-disk activate command will fail.
- Starting services should happen via systemd for all current distros.
- The link for mgr installation leads to nowhere http://docs.ceph.com/docs/master/install/manual-deployment/#manager-daemon-configuration

Actions #1

Updated by Jens Harbott almost 7 years ago

More issues:

The admin key that is generated also needs: --cap mgr 'allow *'

This command will fail and needs sudo added:

$ ceph-authtool /tmp/ceph.mon.keyring --import-keyring /etc/ceph/ceph.client.admin.keyring
can't open /etc/ceph/ceph.client.admin.keyring: can't open /etc/ceph/ceph.client.admin.keyring: (13) Permission denied
Actions #2

Updated by Zac Dover over 4 years ago

  • Assignee set to Zac Dover

I'll take this one.

Actions #3

Updated by Zac Dover over 3 years ago

  • Status changed from New to Resolved

At some point over the past seven months, the issues listed in this ticket have all been addressed.

Further improvements to this document are possible. For example, proper bash prompts should be added to this document. For another example, the language in this document could be made more direct and less mystifying ("The foregoing requirements do not imply the creation of a Ceph Configuration file. However, as a best practice, we recommend creating a Ceph configuration file and populating it with the fsid, the mon initial members and the mon host settings.") "imply" is a strange word to use in this context, and leaves me scratching my head.

Anyway, those issues will be dealt with elsewhere.

Since the complaints that gave rise to this tracker issue no longer present in the documentation, I am marking this issue as "resolved".

Actions

Also available in: Atom PDF