###########################################
#
# Propos :
# Deploiement d’un master en evironement virtuel (ESX) via FlexClone
#
# Pre requis :
# Serveur VMWare ESX
# FlexVol avec l’OS Master (Syspreped) + igroup “esx”
# NAS NetApp avec FlexClone
# SSH parametre entre les deux
#
## memo ssh
## netapp
##secureadmin setup ssh
##secureadmin enable ssh2
##
## from ESX
##esxcfg-firewall -e sshClient
##vi /etc/ssh/ssh_config
##change Ciphers aes256-cbc,aes128-cbc
##to Ciphers aes256-cbc,aes128-cbc,3des-cbc
##ssh @IPNetApp
##accepter la cle puis sortir (^D)
##ssh-keygen -t dsa -b 1024
##mount @IPNetApp:/vol/vol0 /mnt
##mkdir -p /mnt/etc/sshd/root/.ssh
##more /root/.ssh/id_dsa.pub >> /mnt/etc/sshd/root/.ssh/authorized_keys
##vi /mnt/etc/sshd/root/.ssh/authorized_keys (otter root@esx..)
##umount /mnt
##

###########################################

# VARIABLES Globales
NB_CLONE=”100″;
# VARIABLES NetApp
IP_NETAPP=”172.18.16.254″;
MASTER_VOL_NAME=”vol1″;
MASTER_SNAPSHOT_NAME=”snap_master”;
CLONE_VOL_NAME=”clone”;
IGROUP_NAME=”esx”;
# VARIABLES ESX
MASTER_VM_NAME=”master-vm”;
#NEW_RESSOURCE_POOL=”";
DATASTORE_NEW_NAME_PREFIX=”clone”;
NEW_VM_NAME_PREFIX=”clone”;
PATH_2_VMX_PREFIX=”/vmfs/volumes”;

###########################################
# NetApp side
#

# Create Master Snapshot
ssh $IP_NETAPP “snap create -V $MASTER_VOL_NAME $MASTER_SNAPSHOT_NAME”

i=”0″
while (( $i < $NB_CLONE )); do

# Clone from Master Snapshot
CLONE_VOL_NAME=”$CLONE_VOL_NAME$i”;
ssh $IP_NETAPP “vol clone create $CLONE_VOL_NAME -b $MASTER_VOL_NAME $MASTER_SNAPSHOT_NAME”;

# Set the Snapshot Scheduler to 0
ssh $IP_NETAPP “snap sched $CLONE_VOL_NAME 0″;
# Map Cloned Lun
CLONED_LUN_PATH=”/vol/$CLONE_VOL_NAME/lun0″;
ID_CLONED_LUN=$((i+1));
ssh $IP_NETAPP “lun map $CLONED_LUN_PATH $IGROUP_NAME $ID_CLONED_LUN”;

# Bring Cloned Lun Online
ssh $IP_NETAPP “lun online $CLONED_LUN_PATH”;

i=$((i+1));
done

###########################################
# ESX side
#

# Enable LVM resignature
/usr/sbin/esxcfg-advcfg -s 1 /LVM/EnableResignature

# Rescan Storage Adapters
for HBA in `vmware-vim-cmd hostsvc/summary/hba | grep vmhba | awk ‘{print $1}’`; do
vmware-vim-cmd hostsvc/storage/hba_rescan $HBA
done

# Refresh Storage
vmware-vim-cmd hostsvc/storage/refresh

# Set Cloned Datastore’s name
vmware-vim-cmd hostsvc/datastore/listsummary | egrep name | awk -F\” ‘{print $2}’
echo “Nom du (des) datastore(s) clone(s)”
read DATASTORE_CLONED_NAME

# Change Cloned Datastore’s Name & Register the Cloned VM inside
i=0
while (( $i < $NB_CLONE )); do
DATASTORE_NEW_NAME=”$DATASTORE_NEW_NAME_PREFIX$i”;
NEW_VM_NAME=”$NEW_VM_NAME_PREFIX$i”;
PATH_2_VMX=”$PATH_2_VMX/$DATASTORE_NEW_NAME/$MASTER_VM_NAME/$MASTER_VM_NAME.vmx”;
vmware-vim-cmd hostsvc/datastore/rename $DATASTORE_CLONED_NAME $DATASTORE_NEW_NAME;
vmware-vim-cmd solo/registervm $PATH_2_VMX_PREFIX $NEW_VM_NAME $NEW_RESSOURCE_POOL;
i=$((i+1));
done

# Disable LVM resignature
/usr/sbin/esxcfg-advcfg -s 0 /LVM/EnableResignature

sorry for the french comments.

#!/bin/bash
# this script registers every virtual machine found
# on this server. By Chauncey Willard
# Run this on each ESX hosts at the remote site

# rescan the scsi bus to find new luns
esxcfg-rescan vmhba32

# create a text file that lists all files that end with .vmx
# which should be all virtual machines
cd /
find -name *.vmx >/home/all_vmxs.txt

# While loop that runs through every line of the file created above
cat /home/all_vmxs.txt | while read LINE

do
# registers each virtual machine with VC
/usr/bin/vmware-cmd -s register $LINE
done

That’s it. Works fine. tested many times. Chauncey

Excellent point, you are absolutely correct. I will revise the article to suggest setting LVM.EnableResignature back to 0 after this process is complete. Thanks!

Mike

If you are using FlexClones and the clones are of FlexVols containing LUNs that were formatted as VMFS datastores, then enabling the LVM.EnableResignaturing option (setting it to 1) would be required. Also, keep in mind that the LUNs in the cloned volumes will, by default, be offline and will need to be remapped and put back online again in order for hosts to see them. Because they can’t be remapped into the igroup with the same LUN ID, they’ll have to be presented back as a different LUN ID, and that’s where resignaturing comes in. Check to make sure the LUNs in the cloned FlexVols are mapped and online.

And no, there is no way to use “Add Storage” without reformatting the LUN. If the LUN was already created as a VMFS datastore, then the resignaturing option should take care of it.

Good luck!

Thanks,
Mike

It sounds to me like you just need to create VMFS datastores on the other LUNs. The Storage section of the Configuration tab only shows you configured VMFS datastores. Try using the “Add Storage…” link up in the corner to add VMFS datastores on the other LUNs (which are already being recognized and listed in the Storage Adapters section).

Setting LVM.EnableResignature to 1 isn’t needed in this instance. It’s only necessary if you are going to take a Snapshot of one of the volumes, then create a FlexClone of that volume and re-present that back to the ESX servers with a different LUN ID.

Hope this helps!