Skip to content

Commit 7ecbace

Browse files
authored
Documentation for adding NFS mount options to storage pool (#396)
* Documentation for adding NFS mount options to storage pool * Pull 396: Addressed review comments * Pull 396: Added comment on what happens when incorrect mount option is given * Pull 396: storage pool remains in maintenance mode on mount failure
1 parent ae907be commit 7ecbace

File tree

4 files changed

+74
-0
lines changed

4 files changed

+74
-0
lines changed
Loading
Loading
Loading

source/adminguide/storage.rst

Lines changed: 74 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -185,6 +185,7 @@ ensure that the protocol is set to "Filesystem".
185185

186186
|adding-local-pool-via-ui.png|
187187

188+
188189
Storage Tags
189190
~~~~~~~~~~~~
190191

@@ -237,6 +238,73 @@ templates, and ISOs.
237238
.. note::
238239
If files or folders are not associated with a cloudstack resource, it doesn't mean that they are not used by cloudstack.
239240

241+
242+
Setting NFS Mount Options on the Storage Pool
243+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
244+
245+
NFS mount options can be added while creating an NFS storage pool for
246+
KVM hosts. When the storage pool is mounted on the KVM hypervisor host,
247+
these options will be used. Options currently tested and supported are
248+
`vers` and `nconnect`.
249+
250+
Although it depends on the NFS server, but commonly supported `vers` values
251+
are `3` for NFSv3 and minor versions `4.0, 4.1 and 4.2` for NFSv4.
252+
`nconnect` values can range from 1 to 16.
253+
254+
Administrator can give the NFS mount options while adding a Primary Storage
255+
from the Create Zone Wizard as well as the Add Primary Storage form.
256+
|nfs-mount-options-create-zone-wizard.png|
257+
|nfs-mount-options-add-primary-storage.png|
258+
259+
NFS mount options can be changed on a pre-existing Storage Pool in maintenance
260+
mode using the Edit Primary Storage form. Running VMs using volumes in the
261+
Storage Pool will either be stopped or the volumes would be migrated to other
262+
available pools upon enabling maintenance mode.
263+
Storage Pool will be unmounted and mounted again on the KVM hosts using the
264+
new options upon cancelling the maintenance mode.
265+
|nfs-mount-options-edit-primary-storage.png|
266+
267+
Mount failing due to an incorrect mount option
268+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
269+
Add Storage Pool will fail with the error ``An incorrect mount option was specified``.
270+
271+
In the Update storage pool case, cancel maintenance will throw the above error.
272+
The Administrator should set the correct mount option and cancel the maintenance mode again.
273+
274+
275+
Version Requirements
276+
^^^^^^^^^^^^^^^^^^^^
277+
This feature needs libvirt version 5.1.0 and above on the KVM hosts.
278+
279+
The `nconnect` mount option exists in all Linux distributions with kernel 5.3 or higher
280+
281+
A note on the `nconnect` option
282+
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
283+
284+
This option defines the count of TCP connections that the client makes
285+
to the NFS server. The `nconnect` setting is applied only during the
286+
first mount process to the particular NFS server for a given NFS version.
287+
288+
If the same client executes the mount command again to the same NFS server using
289+
the same version, it will get the same `nconnect` value as the first mount.
290+
All mount point to the same server at a given version share the same number
291+
of TCP connections. To change the `nconnect` settings all the such mount points
292+
need to be unmounted and then mounted again with the new `nconnect` value.
293+
294+
So, from CloudStack’s perspective also, the first storage pool created from an
295+
NFS server will set the `nconnect` setting on the hypervisor host corresponding
296+
to the server. Specifying a different `nconnect` mount option while creating a
297+
new storage pool from the same server will not change the `nconnect` setting on the host.
298+
299+
Similarly if there is only one pre-existing storage pool from a give NFS server
300+
mounted on the host, modifying the `nconnect` mount option via CloudStack will
301+
change the `nconnect` setting on that host. If there are more than one storage pools
302+
from the same server mounted on a host. Changing the `nconnect` mount option on one
303+
of the storage pools via CloudStack will not do anything. To change the `nconnect`
304+
setting on the host, after modifying `nconnect` mount option on all storage pools,
305+
the host needs to be restarted.
306+
307+
240308
Secondary Storage
241309
-----------------
242310

@@ -1421,4 +1489,10 @@ Deleting objects from a bucket
14211489
:alt: Import Volume
14221490
.. |unmanage-volume.png| image:: /_static/images/unmanage-volume.png
14231491
:alt: Unmanage Volume
1492+
.. |nfs-mount-options-create-zone-wizard.png| image:: /_static/images/nfs-mount-options-create-zone-wizard.png
1493+
:alt: NFS mount options in create Zone wizard
1494+
.. |nfs-mount-options-add-primary-storage.png| image:: /_static/images/nfs-mount-options-add-primary-storage.png
1495+
:alt: NFS mount options in add Primary Storage
1496+
.. |nfs-mount-options-edit-primary-storage.png| image:: /_static/images/nfs-mount-options-edit-primary-storage.png
1497+
:alt: NFS mount options in edit Primary Storage
14241498

0 commit comments

Comments
 (0)