Skip to main content


Showing posts from December, 2013

Windows Azure: Powershell script to update instance type in .csdef file

Here is a simple PowerShell script to change your azure instance type in .csdef file. You need to run this from your code repository and enter the instance type ie "small", ExtraSmall","Medium" etc when prompted $allCsDefFiles = Get-ChildItem -Recurse -filter *.csdef | ForEach-Object -Process {$_.FullName} $newvmsize = Read-Host 'Enter the instance type' foreach ($thisCsDefFile in $allCsDefFiles) {     [xml]$thisCsDefXml = Get-Content $thisCsDefFile $root = $thisCsDefXml.get_DocumentElement(); If (!$root.WebRole.vmsize) { Write-Host "No webrole found in $($ " } else     {     $root.WebRole.vmsize = $newvmsize $thisCsDefXml.Save($thisCsDefFile) Write-host "Webrole size of $($ changed to $($root.WebRole.vmsize)"     } If (!$root.Workerrole.vmsize) { Write-Host "No Workerrole found in $($ " } else     { $root.Workerrole.vmsize = $newvmsize $thisCsDefXml.

Virtual fibre channel in Hyper V

Virtual fibre channel option in Hyper V allows the connection to pass through from physical  fibre channel HBA to virtual fibre channel HBA, and still have the flexibilities like live migration. Pre-requisites: VM should be running Windows Server 2008, 2008 R2 or Windows Server 2012 Supported physical HBA with N_Port Virtualization(NPIV) enabled in the HBA. This can be enabled using any management utility provided by the SAN manufacturer. If you need to enable live migration, each host should be having two physical HBAs and each HBA should have two World Wide Names(WWN). WWN is used to established connectivity to FC storage.When you perform migration, the second node can use the second WWN to connect to the storage and then the first node can release its connection. Thereby the storage connectivity is maintained during live migration Configuring virtual fibre channel is a two step process Step 1: Create a Virtual SAN in the Hyper-V host First you need to click on Virtual