rsnt_translations
56,426
edits
No edit summary |
No edit summary |
||
Line 29: | Line 29: | ||
#* ''Share Type'' = cephfs | #* ''Share Type'' = cephfs | ||
#* ''Availability Zone'' = nova | #* ''Availability Zone'' = nova | ||
#* Do not check ''Make visible for all'', otherwise the share will be accessible by all users in all projects | #* Do not check ''Make visible for all'', otherwise the share will be accessible by all users in all projects. | ||
# Create an access rule to generate an access key. | # Create an access rule to generate an access key. | ||
#* In ''Project --> Share --> Shares --> Actions'' column, select ''Manage Rules'' from the dropdown menu. | #* In ''Project --> Share --> Shares --> Actions'' column, select ''Manage Rules'' from the dropdown menu. | ||
Line 36: | Line 36: | ||
#* ''Access Level'' = select ''read-write'' or ''read-only'' (you can create multiple rules for either access level if required) | #* ''Access Level'' = select ''read-write'' or ''read-only'' (you can create multiple rules for either access level if required) | ||
#* ''Access To'' = select a key name that describes the key (e.g. ''def-project-shareName-read-write'') | #* ''Access To'' = select a key name that describes the key (e.g. ''def-project-shareName-read-write'') | ||
# Note the share details | # Note the share details | ||
#* In ''Project --> Share --> Shares'', click on the name of the share. | #* In ''Project --> Share --> Shares'', click on the name of the share. | ||
#* In the ''Share Overview'', note the ''Path'' which you will need later. | #* In the ''Share Overview'', note the ''Path'' which you will need later. | ||
Line 66: | Line 66: | ||
<!--T:13--> | <!--T:13--> | ||
<ul> | <ul> | ||
<li>Debian family (Debian, Ubuntu, Mint, etc.):</li></ul> | <li><p>Debian family (Debian, Ubuntu, Mint, etc.):</li></ul> | ||
<!--T:14--> | <!--T:14--> | ||
Line 82: | Line 82: | ||
</pre></li></ul> | </pre></li></ul> | ||
</li> | </li> | ||
<li><p>File 2: /etc/ceph/client.keyonly.shareName (e.g client.keyonly.def-project-shareName-read-write)</p> | <li><p>File 2: /etc/ceph/client.keyonly.shareName (e.g ''client.keyonly.def-project-shareName-read-write'')</p> | ||
<ul> | <ul> | ||
<li>contents: | <li>contents: | ||
<pre>AccessKey | <pre>AccessKey | ||
</pre></li> | </pre></li> | ||
<li>This file only contains the | <li>This file only contains the access key.</li></ul> | ||
</li> | </li> | ||
<li><p>Own these files correctly to protect the key information:</p> | <li><p>Own these files correctly to protect the key information:</p> | ||
Line 109: | Line 109: | ||
</pre> | </pre> | ||
<ul> | <ul> | ||
<li>Note: these are the monitors for the Arbutus cluster | <li>Note: these are the monitors for the Arbutus cluster. If connecting to a different cluster, you will need the monitor information specific to that cluster. | ||
<ul> | <ul> | ||
<li>You can find the monitor information in the | <li>You can find the monitor information in the share details for your share in the ''Path'' field.</li></ul> | ||
</li></ul> | </li></ul> | ||
</li> | </li> | ||
<li><p>Retrieve the connection information from the share page for your connection:</p> | <li><p>Retrieve the connection information from the share page for your connection:</p> | ||
<ul> | <ul> | ||
<li>Open up the share details by clicking the name of the share in the Shares page.</li> | <li>Open up the share details by clicking the name of the share in the ''Shares'' page.</li> | ||
<li>Copy the entire path of the share for mounting the filesystem.</li></ul> | <li>Copy the entire path of the share for mounting the filesystem.</li></ul> | ||
</li> | </li> | ||
<li><p>Mount the filesystem</p> | <li><p>Mount the filesystem</p> | ||
<ul> | <ul> | ||
<li>Create mount point directory somewhere in your host (likely under /mnt/ - e.g. /mnt/ShareName)</li> | <li>Create a mount point directory somewhere in your host (likely under /mnt/ - e.g. /mnt/ShareName)</li> | ||
<li>Via kernel mount using the ceph driver: | <li>Via kernel mount using the ceph driver: | ||
<ul> | <ul> | ||
Line 144: | Line 144: | ||
<!--T:18--> | <!--T:18--> | ||
* A particular share can have more than one user key provisioned for it. | * A particular share can have more than one user key provisioned for it. | ||
** This allows a more granular access to the filesystem | ** 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. | |||
** 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. | ||
* This service is not available to hosts outside of the | |||
<!--T:19--> | <!--T:19--> |