In our day to day activity we come across to a situation where we need to increase or decrease CPU/Memory depending upon the requirements.
So what if the same situation arises in Windows Azure, Can we modify Virtual Machine? Can we increase or decrease the CPU/Memory as and when required? Will it affect the state of Virtual Machine?
Here I have my standard A1 tier VM named as ‘squons-vm1’ in Azure, which is currently having 2 CPU cores and 3.5 GB memory as you can see in below figure.
So what if the same situation arises in Windows Azure, Can we modify Virtual Machine? Can we increase or decrease the CPU/Memory as and when required? Will it affect the state of Virtual Machine?
Here I have my standard A1 tier VM named as ‘squons-vm1’ in Azure, which is currently having 2 CPU cores and 3.5 GB memory as you can see in below figure.
I have taken RDP of my VM, depicting the CPU/RAM allotted to VM.
Now I will increase the size of Virtual Machine to 4 CPU cores and 7 GB memory from VM configure tab.
Following figure describe the configuration tab which is accessible through Virtual Machines list by clicking on desired VM name whose configuration needs to be changed.
Following figure describe the configuration tab which is accessible through Virtual Machines list by clicking on desired VM name whose configuration needs to be changed.
As soon as after changing the VM size from A2 VM when you click on save button present on command bar it will display a message that Virtual machine could be restarted to take affect with respective changes made to the Virtual Machine.
Click yes to continue so that changes get applied on your VM and which will result in restart of VM or Click No to avoid changes getting applied.
For verifying the VM, I have taken RDP of my VM so as to ensure whether it remain intact or restarted.
After clicking yes you will find that the RDP session is lost and the VM is restarted.
For verifying the VM, I have taken RDP of my VM so as to ensure whether it remain intact or restarted.
After clicking yes you will find that the RDP session is lost and the VM is restarted.
After sometime you can able to take RDP of your VM and find upgraded VM with new configuration.
Following figure depicts the VM with new configuration.
Now let’s see what happen when we downgrade the Virtual Machine from current A3 standard VM to A1 standard VM which holds 1 CPU core and 1.75 GB memory.
Again go to respective VM configure tab and decrease the Virtual Machine size to A1 and click on save button so as to update the VM with changes.
Click Yes to continue so that changes get applied on your VM or Click No to avoid changes getting applied.
For verifying the VM, I have taken RDP of my VM so as to ensure whether it remain intact or restarted.
The respective VM gets restarted as soon you click Yes to continue and the RDP session is disconnected as you can find in below figure.
For verifying the VM, I have taken RDP of my VM so as to ensure whether it remain intact or restarted.
The respective VM gets restarted as soon you click Yes to continue and the RDP session is disconnected as you can find in below figure.
After sometime, take the RDP of the Virtual Machine and check the VM configuration. You will find that your Virtual Machine is degraded to A1 VM configuration as depicted below.
Note: The same kind of behaviour is seen with Amazon AWS, whereas Microsoft is coming with hot add and hot plug feature in Windows Threshold Server that is going to be released soon which allows adding memory and CPU on the go while Virtual Machine is running without affecting the VM process. Hence we can expect in future, Windows Azure to adopt the new Windows Threshold as a base to overcome the above mentioned problem as it is currently working on Windows 2012 Server.
No comments:
Post a Comment