Uncategorized

Running EMC ScaleIO In A Nested vSphere Environment–Part 2

Hi,

the first post includes the basic setup for 3 nested ESXi Hosts, in my laptop I only have 16GB of ram so that won’t work, so this post will describe the installation on only two ESX hosts, how can we do it if we need a minimum of 3 ScaleIO entities, well? im doing something here that isn’t supported in real life, basically, one ESX hosts will have one ScaelIO appliance and the 2nd ESX hosts will have 2 ScaleIO appliances (that’s the part that isnt supported), this will reduce the overall memory footprint while still “work”

this post will also include the setup of the ScaleIO packages + installation without the usage of the wizard that was included in the first post!

the screenshot below shows the configuration on the 2nd host, basically, it will run 2 ScaleIO ova appliances, each on the 10GB file, and each one of the 50GB file will be used as the “raw” “drive” that will be attach to each OVA.

image

image

in this case, I used one IP for the OVA that reside on ESX1

image

and this is how it looks when im using the ESX 2 iSCSI initiators to point to the iSCSI ScaleIO appliance

image

image

and two appliances on ESX2(one per appliance for the two that will run on ESX2)

image

image

and of course, this ESX hosts will now need to point to 2 ScaleIO appliances as well

image

but as we mention, this will not happen in real life, in real life, each ESX host will point to one ScaleIO appliance (the one that it runs)

like in the other post, we will need to copy the ScaleIO installation file to each appliance (opt/scaleio/siinstall) se the permissions properly (777)

image

now, we will need to extract the installation files (in each appliance)

image

ok, this is where stuff is starting to get different than in the automated install, as oppose to running the install.py script, we will install the RPM packages that are located in the “packages” folder

image

note that in the “3” node configuration, we will install the MDM cluster on two nodes and the Tie Breaker on the 3rd node, basically, the primary MDM goes to ESX01, Secondary node will goe to ESX2 OVA1 and the Tier Breaker will go to ESX02 OVA02

just as a reminder, it’s not a must to install the SDC and the SDS on the same ESX server if don’t want to but the majority of the real world use cases will do just this because it make more sense for your ESX host to provide compute (SDC) and storage (SDS)

ESX01 (MDM, SDC, SDS and the SCSI target package)

image

ESX02 – OVA1

image

ESX02 – OVA2 (Tie Breaker – NO MDM!)

image

Installing ScaleIO Components

1. Install the MDMs on nodes IP1 and IP2, using the command:
rpm –i <MDM package>
2. Install the Tie-Breaker on node IP3, using the command:
rpm –i <TB package>

Install the SDS on all nodes (IP1, IP2, IP3), using the command:
rpm –i <SDS package>
4. Install the SDC on node IP1, using the command:
MDM_IP=IP_Cluster rpm –i <SDC package>

ok, we now need to prepare the MDM’s on the different appliances

ESX01

image

ESX02

image

ESX03

image

Configuring the MDM’s / Tie Breaker

ESX01

image

ESX02 (performed from ESX01 !!)

image

ESX03 (performed from ESX01) – installing the Tier Breaker

image

Switch to cluster mode (performed from ESX01)

image

entering license key

SNAGHTMLf9dcc8

define protection domain

image

adding capacity (the local 50GB drives per appliance)

add the newly created 50GB drive to the appliance as an additional drive..(need to repeat this on ALL the ESX hosts)

image

image

image

image

and then format it as a VMFS datastore (eager zeroed thick)

the next stage is to add these 50GB drives to the appliances, each 50GB drive goes to another appliance

image

image

image

image

you need to reboot the appliances in order to see the newly added drives, after the reboot run fdisk –l to see if the 50GB drives have been added (run the command on all the appliances)

image

ESX01

image

ESX02

image

ESX03 (run this command from ESX01 since we don’t have scli installed on ESX03)

image

Creating Volumes

ESX01

image

you need to repeat this command on the other ESX hosts

you now need to export the GUI jar file to your PC

image

then launch the java

java -jar dashboard.jar

and then connect to the virtual IP

image

Categories: Uncategorized

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s