Skip to content

Commit 35d6248

Browse files
authored
Add Linstor storage section (#213)
* storage: fix intern linking and a heading * storage: add Linstor Primary Storage section
1 parent 1abd3dc commit 35d6248

File tree

1 file changed

+25
-5
lines changed

1 file changed

+25
-5
lines changed

source/adminguide/storage.rst

Lines changed: 25 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -69,8 +69,7 @@ can be created and dynamically attached to VMs. Data volumes are not
6969
deleted when VMs are destroyed.
7070

7171
Administrators should monitor the capacity of primary storage devices
72-
and add additional primary storage as needed. See the Advanced
73-
Installation Guide.
72+
and add additional primary storage as needed. See :ref:`add-primary-storage`.
7473

7574
Administrators add primary storage to the system by creating a
7675
CloudStack storage pool. Each storage pool is associated with a cluster
@@ -189,8 +188,7 @@ Secondary Storage
189188

190189
This section gives concepts and technical details about CloudStack
191190
secondary storage. For information about how to install and configure
192-
secondary storage through the CloudStack UI, see the Advanced
193-
Installation Guide. about-secondary-storage>`_
191+
secondary storage through the CloudStack UI, see :ref:`add-secondary-storage`.
194192

195193
Migration of data between secondary storages is now supported. One may choose
196194
to completely migrate the data or migrate data such that the stores
@@ -627,7 +625,7 @@ To resize a volume:
627625
#. Click OK.
628626

629627
Root Volume size defined via Service Offering
630-
~~~~~~~~~~~~~~~~
628+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
631629

632630
If a Service Offering is created with a root disk size, then resizing the Root volume is possible only by resizing the VMs service offering.
633631

@@ -878,6 +876,28 @@ snapshot data.
878876
format, and will continue to work as expected.
879877

880878

879+
Linstor Primary Storage
880+
~~~~~~~~~~~~~~~~~~~~~~~
881+
882+
LINSTOR is a configuration management system for storage on Linux systems.
883+
It manages LVM logical volumes and/or ZFS ZVOLs on a cluster of nodes.
884+
It leverages DRBD for replication between different nodes and to provide block storage devices
885+
to users and applications. It manages snapshots, encryption and caching of HDD backed data in SSDs via bcache.
886+
887+
LINSTOR can be used as volume storage provider for Cloudstack, it currently only supports KVM hypervisors.
888+
To get started first setup your LINSTOR cluster according to the `LINSTOR User Guide <https://linbit.com/drbd-user-guide/linstor-guide-1_0-en/>`_
889+
890+
.. note::
891+
Make sure a LINSTOR-Satellite is running on all nodes where you want to have a storage provided for you VM's
892+
and that the nodes have the exact same node names as the nodes in Cloudstack.
893+
Also add a resource group to LINSTOR which you intend to use in Cloudstack.
894+
895+
After you are finished with the LINSTOR cluster setup, you can add a Cloudstack primary storage as any other
896+
primary storage see :ref:`add-primary-storage`.
897+
For protocol choose ``Linstor`` and as server specify the controller REST-API URL e.g.: ``http://127.0.0.1:3370``
898+
and use the resource group name you added in the LINSTOR cluster.
899+
900+
881901
.. |AttachDiskButton.png| image:: /_static/images/attach-disk-icon.png
882902
:alt: Attach Disk Button.
883903
.. |resize-volume-icon.png| image:: /_static/images/resize-volume-icon.png

0 commit comments

Comments
 (0)