CephFS: Difference between revisions

Jump to navigation Jump to search

CephFS (view source)

Revision as of 21:59, 4 March 2024

360 bytes added ,  8 months ago
Marked this version for translation
No edit summary
(Marked this version for translation)
Line 34: Line 34:
<br clear=all>
<br clear=all>


<!--T:20-->
; Create an access rule to generate access key.
; Create an access rule to generate access key.
: In <i>Project --> Share --> Shares --> Actions</i> column, select <i>Manage Rules</i> from the drop-down menu.  
: In <i>Project --> Share --> Shares --> Actions</i> column, select <i>Manage Rules</i> from the drop-down menu.  
Line 43: Line 44:
<br clear=all>
<br clear=all>


<!--T:21-->
; Note the share details which you will need later.
; Note the share details which you will need later.
: In <i>Project --> Share --> Shares</i>, click on the name of the share.
: In <i>Project --> Share --> Shares</i>, click on the name of the share.
Line 49: Line 51:
== Attach the CephFS network to your VM == <!--T:8-->
== Attach the CephFS network to your VM == <!--T:8-->


=== On Arbutus ===
=== On Arbutus === <!--T:22-->
On <code>Arbutus</code> the cephFS network is already exposed to your VM, there is nothing to do here, '''[[CephFS#VM_configuration:_install_and_configure_CephFS_client|go to  VM configuration section]]'''.
On <code>Arbutus</code> the cephFS network is already exposed to your VM, there is nothing to do here, '''[[CephFS#VM_configuration:_install_and_configure_CephFS_client|go to  VM configuration section]]'''.


=== On SD4H/Juno ===
=== On SD4H/Juno === <!--T:23-->
On <code>SD4H/Juno</code>, you need to explicitly attack the cephFS network to the VM.
On <code>SD4H/Juno</code>, you need to explicitly attack the cephFS network to the VM.


<!--T:24-->
;With the Web Gui
;With the Web Gui
For each VM you need to attach, select <i>Instance --> Action --> Attach interface</i>  select the CephFS-Network, leave the Fixed IP Address box empty.
For each VM you need to attach, select <i>Instance --> Action --> Attach interface</i>  select the CephFS-Network, leave the Fixed IP Address box empty.
Line 72: Line 75:
</source>
</source>


<!--T:25-->
Select the ID of the VM you want to attach, will pick the first one here and run
Select the ID of the VM you want to attach, will pick the first one here and run
<source lang='bash'>
<source lang='bash'>
Line 85: Line 89:
</source>
</source>


<!--T:26-->
We can see that the CephFS network is attached to the first VM.
We can see that the CephFS network is attached to the first VM.


== VM configuration: install and configure CephFS client == <!--T:9-->
== VM configuration: install and configure CephFS client == <!--T:9-->


<!--T:27-->
;Install the required packages for Red Hat family (RHEL, CentOS, Fedora, Rocky, Alma ).
;Install the required packages for Red Hat family (RHEL, CentOS, Fedora, Rocky, Alma ).
Check the available releases here https://download.ceph.com/ and look for recent <code>rpm-*</code> directories, quincy is the right/latest stable release at the time of this writing. The compatible distro are listed here
Check the available releases here https://download.ceph.com/ and look for recent <code>rpm-*</code> directories, quincy is the right/latest stable release at the time of this writing. The compatible distro are listed here
  https://download.ceph.com/rpm-quincy/, we will show the full installation for <code>el8</code>.
  https://download.ceph.com/rpm-quincy/, we will show the full installation for <code>el8</code>.


=== Install relevant repositories for access to ceph client packages: ===
=== Install relevant repositories for access to ceph client packages: === <!--T:28-->


<!--T:29-->
{{File
{{File
   |name=/etc/yum.repos.d/ceph.repo
   |name=/etc/yum.repos.d/ceph.repo
Line 107: Line 114:
gpgkey=https://download.ceph.com/keys/release.asc
gpgkey=https://download.ceph.com/keys/release.asc


<!--T:30-->
[Ceph-noarch]
[Ceph-noarch]
name=Ceph noarch packages
name=Ceph noarch packages
Line 115: Line 123:
gpgkey=https://download.ceph.com/keys/release.asc
gpgkey=https://download.ceph.com/keys/release.asc


<!--T:31-->
[ceph-source]
[ceph-source]
name=Ceph source packages
name=Ceph source packages
Line 124: Line 133:
}}
}}


<!--T:32-->
The epel repo also needs to be in place
The epel repo also needs to be in place
  sudo dnf install epel-release
  sudo dnf install epel-release


<!--T:33-->
You can now install the ceph lib, cephfs client and other dependencies:
You can now install the ceph lib, cephfs client and other dependencies:
  sudo dnf install -y libcephfs2 python3-cephfs ceph-common python3-ceph-argparse
  sudo dnf install -y libcephfs2 python3-cephfs ceph-common python3-ceph-argparse




<!--T:34-->
;Install the required packages for Debian family (Debian, Ubuntu, Mint, etc.):
;Install the required packages for Debian family (Debian, Ubuntu, Mint, etc.):
You can get the repository one you have figured out your distro <code>{codename}</code> with <code>lsb_release -sc</code>
You can get the repository one you have figured out your distro <code>{codename}</code> with <code>lsb_release -sc</code>
Line 137: Line 149:
</source>
</source>


=== Configure ceph client: ===
=== Configure ceph client: === <!--T:35-->


<!--T:36-->
Once the client is installed, you can create a <code>ceph.conf</code> file, note the different Mon host for the different cloud.  
Once the client is installed, you can create a <code>ceph.conf</code> file, note the different Mon host for the different cloud.  
<tabs>
<tabs>
Line 173: Line 186:
</tabs>
</tabs>


<!--T:37-->
You can find the monitor information in the share details <i>Path</i> field that will be used to mount the volume. If the value of the web page is different than what is seen here, it means that the wiki page is out of date.  
You can find the monitor information in the share details <i>Path</i> field that will be used to mount the volume. If the value of the web page is different than what is seen here, it means that the wiki page is out of date.  


<!--T:38-->
You also need to put your client name and secret in the <code>ceph.keyring</code> file  
You also need to put your client name and secret in the <code>ceph.keyring</code> file  


<!--T:39-->
{{File
{{File
   |name=/etc/ceph/ceph.keyring
   |name=/etc/ceph/ceph.keyring
Line 185: Line 201:
}}
}}


<!--T:40-->
Again, the access key and client name (here MyCephFS-RW) are found under access rules on your project web page, hereL Project --> Share --> Shares, click on the name of the share.
Again, the access key and client name (here MyCephFS-RW) are found under access rules on your project web page, hereL Project --> Share --> Shares, click on the name of the share.




<!--T:41-->
; Retrieve the connection information from the share page for your connection:
; Retrieve the connection information from the share page for your connection:
: Open up the share details by clicking the name of the share in the <i>Shares</i> page.
: Open up the share details by clicking the name of the share in the <i>Shares</i> page.
: Copy the entire path of the share for mounting the filesystem.
: Copy the entire path of the share for mounting the filesystem.


<!--T:42-->
;Mount the filesystem
;Mount the filesystem
:Create a mount point directory somewhere in your host (<code>/cephfs</code>, is used here)</li>
:Create a mount point directory somewhere in your host (<code>/cephfs</code>, is used here)</li>
Line 217: Line 236:
</tabs>
</tabs>


<!--T:43-->
'''Note:'''
'''Note:'''
There is a non-standard/funky <code>:</code> before the device path, it is not a typo!  
There is a non-standard/funky <code>:</code> before the device path, it is not a typo!  
Line 222: Line 242:
The namespace option is required for SD4H/Juno while other options are performance tweaks.
The namespace option is required for SD4H/Juno while other options are performance tweaks.


<!--T:44-->
;It can also be done from the command line:
;It can also be done from the command line:
<tabs>
<tabs>
Line 236: Line 257:
</tabs>
</tabs>


<!--T:45-->
;Or via ceph-fuse if the file system needs to be mounted in user space
;Or via ceph-fuse if the file system needs to be mounted in user space
: No funky <code>:</code> here
: No funky <code>:</code> here


<!--T:46-->
Install the ceph-fuse lib
Install the ceph-fuse lib


<!--T:47-->
<source lang="bash">
<source lang="bash">
sudo dnf install ceph-fuse
sudo dnf install ceph-fuse
Line 246: Line 270:
Let the fuse mount be accessible in userspace by uncommenting  <code>user_allow_other</code> in the <code>fuse.conf</code> file.
Let the fuse mount be accessible in userspace by uncommenting  <code>user_allow_other</code> in the <code>fuse.conf</code> file.


<!--T:48-->
{{File
{{File
   |name=/etc/fstab
   |name=/etc/fstab
Line 254: Line 279:
}}
}}


<!--T:49-->
You can now mount cephFS in a user’s home:
You can now mount cephFS in a user’s home:
<source lang="bash">
<source lang="bash">
Diane27
rsnt_translations
56,420

edits

Retrieved from "https://docs.alliancecan.ca/wiki/Special:MobileDiff/150805"

Navigation menu