A WORLD OF BITS AND BYTES…
Altaro has kicked off the Altaro Dojo forums. The forum brings fellow IT pros together, connect the community and enable members to learn and share their knowledge with one another.
Some info on how people can use the forum can be found here.
Please register on the forum and share your knowledge with other IP pros! Let’s make some community!
I want to become a ‘Ninja’. Let’s go!!!
This video shows how powerful PowerShell is for doing some automation in Hyper-V and Azure (IaaS).
I’ve seen a lot of Hyper-V clusters during my daily work. Most of the time, I see a mixture of none standardised names or letters. Also a mixture of upper and lower case names.
There’s is only one option to have all your cluster nodes in Upper case names within the failover cluster manager, you’ll have to use the command line! For example:
cluster.exe /cluster:<name of the cluster> /add /node:<name of the node in UPPER case>
For this command to work, you’ve to install ‘Failover Cluster Command Interface’.
Within an Azure Virtual Machine, you should never store your (personal) data on the C: drive or the temporary disk. You can attach new storage disks to the virtual machine, how many disks depends on the VM size you’ve choosen.
View all VM sizes in Microsoft Azure:
https://docs.microsoft.com/en-us/azure/virtual-machines/virtual-machines-windows-sizes
In my example I’ve choosen the ‘DS1v2’ VM size, so I can attach two extra (premium storage) disks. Because the maximum size of an disk in Microsoft Azure is 1023 GB, I’ve created multiple disks. Both disks are attached to the virtual machine and we’re going to implement Storage Spaces within the virtual machine. Storage Spaces is software defined storage (SDS) from Windows Server 2012 R2 and above.
Storage Spaces is a built-in Windows Server Role. When combining all the data disks, you can create one, or more, big data volumes in your Windows Virtual Machine. Extremely powerful for example file servers.
1.) First of all I’ve created a new virtual machine using the Azure Portal
2.) Next I’ve created two new disks (premium storage – SSD) with tthe size of 1023 GB.
3.) Next I’ve logged in into the new created virtual machine and configured Storage Spaces.
4.) The next step is to create a new virtual disk
5.) The final step is to create the new volume for storing your data on.
As you can see, there’s a new volume of 2 TBwithin the virtual machine. If you’re changing the size of the virtual machine, it is also possible to add some more disks to the virtual machine and extend the Storage Spaces with more terabytes!!
The following movie shows the power of Storage Spaces Direct in Windows Server 2016. From the local disks, to storage pools and cluster, all the layers are explained!! Very useful when you want to know exactly how Storage Spaces Direct (S2D) works.
Software Defined will be the feature! So prepare yourself….. 🙂
This book focuses on providing essential information about the key services of Azure for developers and IT professionals who are new to cloud computing. Detailed, step-by-step demonstrations are included to help the reader understand how to get started with each of the key services. This material is useful not only for those who have no prior experience with Azure, but also for those who need a refresher and those who may be familiar with one area but not others. Each chapter is standalone; there is no requirement that you perform the hands-on demonstrations from previous chapters to understand any particular chapter.
Download the free eBook here.
Resizing a virtual hard disk in Azure Resource Manager is really easy to do through the Azure Managent Portal. In a few clicks you can extend the virtual hard disk size. Note that the VM should be turned off!! So you need to plan a maintenance window!!
You can also extend the virtual hard disk with PowerShell. In this example I’ve extended the data disk from 25 to 30 GB.
# Specify the VM
$VM = Get-AzureRmVM -ResourceGroupName MSS-DEMO -VMName MSS-DEMO-DC01
# Set the new size of the data disk
Set-AzureRmVMDataDisk -VM $VM -Name MSS-DEMO-DC01-20160801-100246 -DiskSizeInGB 30
# View the new size of the data disk(s)
$VM.StorageProfile.DataDisks
# Update the configuration in Azure
Update-AzureRmVM -VM $VM -ResourceGroupName MSS-DEMO
1.) Login to the Azure Management Portal
2.) Check the current size of the data disk. In my example 25 GB
3.) Start PowerShell and login to your Azure subscription
4.) Change the data disk to the new value
5.) Update the configuration to Azure
6.) Check the new size of the data disk with PowerShell or within the Azure Management Portal.
In my example the new size is 30 GB.
Automation is one of my favorite things. Some actions are just time consuming, so let’s automate these things!! For example, create a demo environment within Hyper-V. This environment needs 8 VM’s. With a few lines of code, this is realy easy to automate, off course with PowerShell.
## Create 8 Gen2 Virtual Machines
## 4 vCPU per VM
## 1 GB per VM
## C: drive 50 GB Dynamic
## D: drive 50 GB Dynamic
## NIC renamed to MGMT
$vSwitchName01 = "NIC - PRI"
$InstallRoot = "E:\DEMO"
$VMName = "HV-0"
## How much VM's 1..8 = 8 VM's
1..4 | % {
New-VHD -Path ($InstallRoot + "\$VMName" + "$_\" + "\$VMName" + "$_" + "_C.vhdx") -SizeBytes 50GB -Dynamic
New-VHD -Path ($InstallRoot + "\$VMName" + "$_\" + "\$VMName" + "$_" + "_D.vhdx") -SizeBytes 50GB -Dynamic
New-VM -VHDPath ($InstallRoot + "\$VMName" + "$_\" + "\$VMName" + "$_" + "_C.vhdx") -Generation 2 -MemoryStartupBytes 1GB -Name ("$VMName" + "$_") -Path $InstallRoot -SwitchName $vSwitchName01
Set-VMProcessor -VMName ("$VMName" + "$_") -Count 4
Set-VM -VMName ("$VMName" + "$_") -AutomaticStopAction ShutDown -AutomaticStartAction StartIfRunning
Enable-VMIntegrationService ("$VMName" + "$_") -Name "Guest Service Interface"
Rename-VMNetworkAdapter -VMName ("$VMName" + "$_") -NewName "MGMT"
Set-VMNetworkAdapter -VMName ("$VMName" + "$_") -Name "MGMT" -DeviceNaming On
Add-VMScsiController -VMName ("$VMName" + "$_")
Add-VMHardDiskDrive -VMName ("$VMName" + "$_") -ControllerType SCSI -ControllerNumber 1 -ControllerLocation 0 -Path ($InstallRoot + "\$VMName" + "$_\" + "\$VMName" + "$_" + "_D.vhdx")
Start-VM -Name ("$VMName" + "$_") | Out-Null
}
Within a few seconds, I’ve 8 VM’s up and running.
/ Happy Automation!