rsnt_translations
56,420
edits
CephFS: Difference between revisions
no edit summary
No edit summary |
|||
| Line 47: | Line 47: | ||
: In the <i>Share Overview</i>, note the three elements circled in red in the "Properly configured" image: <i>Path</i>, which will be used in the mount command on the VM, the <i>Access Rules</i>, which will be the client name and the <i>Access Key</i> that will let the VM's client connect. | : In the <i>Share Overview</i>, note the three elements circled in red in the "Properly configured" image: <i>Path</i>, which will be used in the mount command on the VM, the <i>Access Rules</i>, which will be the client name and the <i>Access Key</i> that will let the VM's client connect. | ||
== Attach the CephFS network to your VM == <!--T: | == Attach the CephFS network to your VM == <!--T:8--> | ||
=== On Arbutus === | === On Arbutus === | ||
| Line 87: | Line 87: | ||
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: | == VM configuration: install and configure CephFS client == <!--T:9--> | ||
;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 ). | ||
| Line 261: | Line 261: | ||
Note that the client name is here the <code>--id</code>. The <code>ceph.conf</code> and <code>ceph.keyring</code> content are exactly the same as for the ceph kernel mount. | Note that the client name is here the <code>--id</code>. The <code>ceph.conf</code> and <code>ceph.keyring</code> content are exactly the same as for the ceph kernel mount. | ||
=Notes= <!--T: | =Notes= <!--T:10--> | ||
<!--T: | <!--T:11--> | ||
A particular share can have more than one user key provisioned for it. This allows a more granular access to the filesystem, for example, if you needed some hosts to only access the filesystem in a read-only capacity. If you have multiple keys for a share, you can add the extra keys to your host and modify the above mounting procedure. This service is not available to hosts outside of the OpenStack cluster. | A particular share can have more than one user key provisioned for it. This allows a more granular access to the filesystem, for example, if you needed some hosts to only access the filesystem in a read-only capacity. If you have multiple keys for a share, you can add the extra keys to your host and modify the above mounting procedure. This service is not available to hosts outside of the OpenStack cluster. | ||
<!--T: | <!--T:12--> | ||
[[Category:Cloud]] | [[Category:Cloud]] | ||
</translate> | </translate> | ||