M #-: SaN LVM reordered (#475)

Re-ordered structure of SAN LVM section as well as introduced FE
configuration part which is reference to corresponding supported SAN
types.

Signed-off-by: Mikalai Kutouski <[email protected]>

Author: mkutouski

content/product/cluster_configuration/lvm/filemode.md

@@ -6,7 +6,7 @@ description:
 categories:
 pageintoc: "72"
 tags:
-weight: "3"
+weight: "6"
 ---
 
 In this setup, disk images are stored in file format, such as raw and qcow2, in the Image Datastore,
@@ -40,6 +40,9 @@ In case of rebooting the virtualization Host, the volumes need to be activated t
 
 Virtual Machine disks are symbolic links to the block devices. However, additional VM files like checkpoints or deployment files are stored under `/var/lib/one/datastores/<id>`. Be sure that enough local space is present.
 
+## Front-end Configuration
+
+The Front-end needs to be configured as it’s described in the corresponding section of either [PureStorage]({{% relref "purestorage_guide#front-end-and-hosts-configuration" %}}), [NetApp]({{% relref "netapp_guide#front-end-and-host-configuration" %}}) or [Generic SAN]({{% relref "generic_guide#front-end-configuration" %}}) depending on the SAN type you have.
 
 ## OpenNebula Configuration
 

content/product/cluster_configuration/lvm/generic_guide.md

@@ -1,7 +1,7 @@
 ---
 title: "SAN/LVM: Generic setup"
 linkTitle: "Generic SAN setup"
-weight: "6"
+weight: "4"
 ---
 
 

content/product/cluster_configuration/lvm/lvm.md

@@ -6,7 +6,7 @@ description:
 categories:
 pageintoc: "72"
 tags:
-weight: "2"
+weight: "5"
 ---
 
 With LVM SAN Datastore (EE), both disks images and actual VM drives are stored as Logical Volumes
@@ -43,6 +43,9 @@ In case of rebooting the virtualization Host, the volumes need to be activated t
 
 Virtual Machine disks are symbolic links to the block devices. However, additional VM files like checkpoints or deployment files are stored under `/var/lib/one/datastores/<id>`. To prevent filling local disks, allocate plenty of space for these files.
 
+## Front-end Configuration
+
+The Front-end needs to be configured as it’s described in the corresponding section of either [PureStorage]({{% relref "purestorage_guide#front-end-and-hosts-configuration" %}}), [NetApp]({{% relref "netapp_guide#front-end-and-host-configuration" %}}) or [Generic SAN]({{% relref "generic_guide#front-end-configuration" %}}) depending on the SAN type you have.
 
 ## OpenNebula Configuration
 

content/product/cluster_configuration/lvm/netapp_guide.md

@@ -1,7 +1,7 @@
 ---
 title: "SAN/LVM: NetApp setup"
 linkTitle: "NetApp: SAN setup"
-weight: "5"
+weight: "3"
 ---
 
 This setup assumes you are using NetApp ONTAP with iSCSI and are trying to use it as a backend for one of OpenNebula's [LVM datastore options]({{% relref "." %}}). The configuration uses standard volume and host mappings. If you are familiar with the NetApp ONTAP interface and its functionality, create the required resources as desired.

content/product/cluster_configuration/lvm/purestorage_guide.md

@@ -1,7 +1,7 @@
 ---
 title: "SAN/LVM: PureStorage setup"
 linkTitle: "PureStorage: SAN setup"
-weight: "4"
+weight: "2"
 ---
 
 This setup assumes you are using a PureStorage FlashArray with iSCSI and want to use it as a backend for one of OpenNebula's [LVM datastore options]({{% relref "." %}}). The configuration uses standard volume and host mappings. If you are familiar with the PureStorage interface, create the required resources as desired.