Skip to content

Commit

Permalink
Wording
Browse files Browse the repository at this point in the history
Signed-off-by: Guillermo Ramos <[email protected]>
  • Loading branch information
1gramos committed Dec 19, 2024
1 parent 1ec2414 commit bbfa96f
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion source/open_cluster_deployment/storage_setup/nas_ds.rst
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ Automatic Setup

Automatic NFS setup is is available since OpenNebula version 6.10.3 as an opt-in feature. It's controlled via the ``NFS_AUTO_*`` family of datastore attributes documented :ref:`below <anfs-attributes>`. If enabled, OpenNebula will lazily mount the NFS share on demand (either on hosts or the frontend) before an operation requires it. Also, for the transfer operations where it makes sense (for example, when deploying a VM which uses a NFS-backed system image) the mounting information is persisted to the host's ``/etc/fstab``.

Also, for the moment, umounting/fstab cleanup is performed in a lazy way, similar to mounting. So, rutine operations will check whether the current machine has mounted a datastore which either has ``NFS_AUTO_ENABLE`` set to ``no``, or does not exist anymore, and clean it up.
Also, for the moment, unmounting/fstab cleanup is performed in a lazy way, similar to mounting. So, routine operations will check whether the current machine has mounted a datastore which either has ``NFS_AUTO_ENABLE`` set to ``no``, or does not exist anymore, and clean it up.

.. warning:: This also means that the user must be careful not to delete the filesystem from the NFS server until being sure that there are no hosts still having it mounted.

Expand Down

0 comments on commit bbfa96f

Please sign in to comment.