The Solution about using SAN Storage as Cloudstack Storage

[xuanyuanaosheng]

We have a SAN Storage is : Hitachi VSP (Hitachi Virtual Storage Platform 5000 Series),we want to use it as The Cloudstack Storage.

ISSUE TYPE

• Other

COMPONENT NAME

• Storage

CLOUDSTACK VERSION

• CloudStack Version: 4.15.2.0
• Cloudstack Hypervisor: KVM
• The Storage：SAN HITACHI VSP

Related Doc

1. https://docs.cloudstack.apache.org/en/latest/adminguide/storage.html
2. https://docs.cloudstack.apache.org/en/latest/installguide/configuration.html#add-primary-storage

Now we have assigned the same 5T on kvm001 and kvm002, The detail info is:

kvm001

# multipath -ll
mpatham (360060e801262eb00504062eb000000ea) dm-26 HITACHI,OPEN-V
size=5.0T features='0' hwhandler='0' wp=rw
`-+- policy='service-time 0' prio=1 status=active
  |- 1:0:8:1  sdbd 67:112 active ready running
  `- 2:0:10:1 sdbe 67:128 active ready running


# fdisk -l
Disk /dev/sda: 894.2 GiB, 960163569664 bytes, 1875319472 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 262144 bytes / 262144 bytes
Disklabel type: gpt
Disk identifier: ADE9C21E-CBF8-4F90-A4B4-F2EFC77C1AEA

Device       Start       End   Sectors  Size Type
/dev/sda1     2048   2099199   2097152    1G EFI System
/dev/sda2  2099200   4196351   2097152    1G Linux filesystem
/dev/sda3  4196352 570443775 566247424  270G Linux LVM


Disk /dev/mapper/ol-root: 50 GiB, 53687091200 bytes, 104857600 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 262144 bytes / 262144 bytes


Disk /dev/mapper/ol-swap: 10 GiB, 10737418240 bytes, 20971520 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 262144 bytes / 262144 bytes


Disk /dev/mapper/ol-opt: 50 GiB, 53687091200 bytes, 104857600 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 262144 bytes / 262144 bytes


Disk /dev/mapper/ol-var: 50 GiB, 53687091200 bytes, 104857600 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 262144 bytes / 262144 bytes


Disk /dev/mapper/ol-home: 10 GiB, 10737418240 bytes, 20971520 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 262144 bytes / 262144 bytes


Disk /dev/mapper/ol-image: 100 GiB, 107374182400 bytes, 209715200 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 262144 bytes / 262144 bytes


Disk /dev/sdbd: 5 TiB, 5497558138880 bytes, 10737418240 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/sdbe: 5 TiB, 5497558138880 bytes, 10737418240 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/mpatham: 5 TiB, 5497558138880 bytes, 10737418240 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


# lsblk
NAME         MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sda            8:0    0 894.2G  0 disk  
├─sda1         8:1    0     1G  0 part  /boot/efi
├─sda2         8:2    0     1G  0 part  /boot
└─sda3         8:3    0   270G  0 part  
  ├─ol-root  252:0    0    50G  0 lvm   /
  ├─ol-swap  252:1    0    10G  0 lvm   [SWAP]
  ├─ol-opt   252:2    0    50G  0 lvm   /opt
  ├─ol-var   252:3    0    50G  0 lvm   /var
  ├─ol-home  252:4    0    10G  0 lvm   /home
  └─ol-image 252:5    0   100G  0 lvm   /image
sdbd          67:112  0     5T  0 disk  
└─mpatham    252:26   0     5T  0 mpath 
sdbe          67:128  0     5T  0 disk  
└─mpatham    252:26   0     5T  0 mpath

kvm002

# multipath -ll
mpatham (360060e801262eb00504062eb000000ea) dm-50 HITACHI,OPEN-V
size=5.0T features='0' hwhandler='0' wp=rw
`-+- policy='service-time 0' prio=1 status=active
  |- 1:0:8:1  sdbd 67:112 active ready running
  `- 2:0:10:1 sdbe 67:128 active ready running

# fdisk -l
Disk /dev/sda: 894.2 GiB, 960163569664 bytes, 1875319472 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 262144 bytes / 262144 bytes
Disklabel type: gpt
Disk identifier: DB76AE3B-E647-4D38-9BF8-630958F8F240

Device       Start       End   Sectors  Size Type
/dev/sda1     2048   2099199   2097152    1G EFI System
/dev/sda2  2099200   4196351   2097152    1G Linux filesystem
/dev/sda3  4196352 591415295 587218944  280G Linux LVM


Disk /dev/mapper/ol-root: 50 GiB, 53687091200 bytes, 104857600 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 262144 bytes / 262144 bytes


Disk /dev/mapper/ol-swap: 10 GiB, 10737418240 bytes, 20971520 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 262144 bytes / 262144 bytes


Disk /dev/mapper/ol-opt: 50 GiB, 53687091200 bytes, 104857600 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 262144 bytes / 262144 bytes


Disk /dev/mapper/ol-home: 20 GiB, 21474836480 bytes, 41943040 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 262144 bytes / 262144 bytes


Disk /dev/mapper/ol-var: 50 GiB, 53687091200 bytes, 104857600 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 262144 bytes / 262144 bytes


Disk /dev/mapper/ol-image: 100 GiB, 107374182400 bytes, 209715200 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 262144 bytes / 262144 bytes


Disk /dev/sdbd: 5 TiB, 5497558138880 bytes, 10737418240 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/sdbe: 5 TiB, 5497558138880 bytes, 10737418240 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/mpatham: 5 TiB, 5497558138880 bytes, 10737418240 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes

# lsblk
NAME         MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sda            8:0    0 894.2G  0 disk  
├─sda1         8:1    0     1G  0 part  /boot/efi
├─sda2         8:2    0     1G  0 part  /boot
└─sda3         8:3    0   280G  0 part  
  ├─ol-root  252:0    0    50G  0 lvm   /
  ├─ol-swap  252:1    0    10G  0 lvm   [SWAP]
  ├─ol-opt   252:2    0    50G  0 lvm   /opt
  ├─ol-home  252:3    0    20G  0 lvm   /home
  ├─ol-var   252:4    0    50G  0 lvm   /var
  └─ol-image 252:5    0   100G  0 lvm   /image
sdbd          67:112  0     5T  0 disk  
└─mpatham    252:50   0     5T  0 mpath 
sdbe          67:128  0     5T  0 disk  
└─mpatham    252:50   0     5T  0 mpath

I have searched all the doc and google, But I still can not find how to add SAN Storage as the cloudstack primary Storage.

Cloud you please give some advices or solution?

[xuanyuanaosheng]

@sureshanaparti Any update?

The storage is : https://knowledge.hitachivantara.com/Documents/Storage/VSP_Gx00_and_VSP_Fx00/83-05-xx/VSP_G200_G400_G600_G800_Hardware_Reference/01_Hitachi_Virtual_Storage_Platform_G200_hardware_overview

[sureshanaparti]

@sureshanaparti Any update?

@xuanyuanaosheng I'm not sure about SAN storage, will check and update you.

[xuanyuanaosheng]

@sureshanaparti @DaanHoogland @andrijapanicsb I know that the zstack support SAN storage as zstack storage: https://www.zstack.io/help/en/product_manuals/maintenance_manual/v3/7.6.html
Does the cloustack support this feature ?

[xuanyuanaosheng]

@sureshanaparti Any update?