Skip to content

Storage Access Groups documentation #503

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
37 changes: 36 additions & 1 deletion source/adminguide/storage.rst
Original file line number Diff line number Diff line change
Expand Up @@ -252,6 +252,38 @@ same set of tags on the primary storage for all clusters in a pod. Even
if different devices are used to present those tags, the set of exposed
tags can be the same.

Storage Access Groups
~~~~~~~~~~~~~~~~~~~~~

When a primary storage is added in CloudStack, either at the Zone or Cluster scope,
it gets connected to all the hosts within that scope. Using Storage Access Groups,
this behavior can be controlled by defining groups on both primary storage and hosts,
ensuring connections are established only within those groups. When a Storage Access
Group is set on a primary storage (a text string attribute similar to tag),
and the same group is assigned to a host, the primary storage will connect only to that host.
A Storage Access Group can also be applied at the Cluster, Pod, or Zone level, allowing
all hosts in that entity to inherit the group automatically.

For example, if there are 50 hosts across 10 clusters, with 5 hosts per cluster,
and a zone-wide primary storage is added, it will connect to all 50 hosts. If the
operator wants to limit the connection to a few hosts in just the first 2 clusters,
Storage Access Groups can be set on the primary storage and those specific hosts —
or directly on the two clusters to achieve the same effect.

Adding Storage Access Group on a primary storage.

|adding-storage-access-group-on-primary-storage.png|

Adding Storage Access Group on a host. Similarly it can be applied Cluster/Pod/Zone.

|adding-storage-access-group-on-host.png|

A primary storage with a Storage Access Group will connect only to hosts that have the
same Storage Access Group. A storage pool without a Storage Access Group will connect to all hosts,
including those with or without any Storage Access Group.

Note: Storage Access Groups are not applicable for local primary storages. Currently this is tested with NFS
and Dell PowerFlex storages.

Maintenance Mode for Primary Storage
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Expand Down Expand Up @@ -1719,4 +1751,7 @@ as well if they wish. Attaching and detaching a disk is not allowed on a Shared
:alt: NFS mount options in add Primary Storage
.. |nfs-mount-options-edit-primary-storage.png| image:: /_static/images/nfs-mount-options-edit-primary-storage.png
:alt: NFS mount options in edit Primary Storage

.. |adding-storage-access-group-on-primary-storage.png| image:: /_static/images/adding-storage-access-group-on-primary-storage.png
:alt: Adding storage access groups on primary storage
.. |adding-storage-access-group-on-host.png| image:: /_static/images/adding-storage-access-group-on-host.png
:alt: Adding storage access groups on host