Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update mount-block-device.rst #408

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update mount-block-device.rst #408

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 22 additions & 2 deletions docs/tutorial/mount-block-device.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@ Create a pool for RBD images:
1 .mgr
2 block_pool

$ rbd pool init block_pool
$ sudo rbd pool init block_pool

Create RBD image:

Expand Down Expand Up @@ -96,6 +96,26 @@ For the sake of simplicity, we are using admin keys in this example.
The files are located at the paths shown above on any MicroCeph node.
Moving forward, we will assume that these files are located at mentioned path.

After 'ceph-common' package installation, 'ceph' command will start looking at the '/etc/ceph/' directory for keyring and conf files, which is not the correct place.
This could cause CLI errors similar to this:

.. code-block:: none

Error initializing cluster client: ObjectNotFound('RADOS object not found (error calling conf_read_file)')

To fix this, 'microceph.ceph' command can be used instead of 'ceph'. To continue using 'ceph' commands as usual, keyring and conf files must be linked to the '/etc/ceph/' directory as follows:

.. code-block:: none

$ sudo ln -s /var/snap/microceph/current/conf/ceph.conf /etc/ceph/
$ sudo ln -s /var/snap/microceph/current/conf/ceph.keyring /etc/ceph/
Comment on lines +110 to +111
Copy link
Contributor

@UtkarshBhatthere UtkarshBhatthere Sep 3, 2024 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These 2 could be combined to:
$ sudo ln -s /var/snap/microceph/current/conf/ /etc/ceph

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also look at line 126, 127. These would have to be removed as we are explicitly providing the conf paths.


$ ls -lrth /etc/ceph/
total 4.0K
-rw-r--r-- 1 root root 185 Aug 27 10:38 rbdmap
lrwxrwxrwx 1 root root 42 Aug 29 07:17 ceph.conf -> /var/snap/microceph/current/conf/ceph.conf
lrwxrwxrwx 1 root root 45 Aug 29 07:17 ceph.keyring -> /var/snap/microceph/current/conf/ceph.keyring

Map the RBD image on client:

.. code-block:: none
Expand Down Expand Up @@ -169,4 +189,4 @@ Ceph cluster state post IO:

Comparing the ceph status output before and after writing the file shows that
the MicroCeph cluster has grown by 30MiB which is thrice the size of the file
we wrote (10MiB). This is because MicroCeph configures 3 way replication by default.
we wrote (10MiB). This is because MicroCeph configures 3 way replication by default.
Loading