It is time to take a look at the greatest feature of EMC ScaleIO which is supporting wide range of Operating systems (Yes, that is a great advantage for ScaleIO over many other competitors) So in this post, I will be mixing Hyper-v and VMware SDSs nodes. In my previous post (here), I talked about implementing ScaleIO in VMware ESX environment. so I will be using the same setup I used in my previous post however, this time I will have another Hyper-v Server with 2 HDDs one is used for Boot partition and another disk will be used for ScaleIO.
We start first by installing ScaleIO components on my hyper-v server. The installer is included in ScaleIO iso file downloaded from EMC support site.
Extract the zip file and run ECS installer from <Extract Directory>\ECS\ECS-installer 1.xxx.msi. Afterwards, click next and accept the license agreement.
You should select ScaleIO components to be installed on your local server. I will install SDC,SDS and MDM however, I will be focusing mainly in this post on mixing SDSs. Mixing SDCs and MDMs to be covered in my next posts.
SDC component will add a new Storage Controller. From Device Manager, Under Storage Controllers:
At this stage we should work on adding the newly disk to storage pool HDD. From my Windows 2012 Hyper-v server, diskpart or diskmgmt.msc will list my available Disks:We should assign drive letter to the partition however, we should NOT format the volume as shown below (This is one of the prerequisites for ScaleIO Implementation in Widows Environment):
Once the wizard completes, we should have a RAW disk as shown below: We are almost done here, so now I will add the new sds for Windows 2012 hyper-v server from my Primary MDM:The next step is to create a volume so I will create a small volume for testing of size 30 GB.The last step is to map the volume to all SDCs, At this stage I will map the newly created volume to all SDCs (SDC component installed on Hyper-v has not been added yet to the configured SDCs in my ScaleIO environment):Now, the volume is ready to be used and be mapped to ISCSI initiators so i will map it here to my esx1 server:and from esxi rescan the HBAs and add the new VMFS datastore: