‘Nuff said?
Maybe we could blame Microsoft to name the new VM role feature (Windows Server 2008 R2 is supported as guest OS, 2011 should show broader OS support) introduced at PDC10 in a confusing way – but the fact remains:
it is based on the Azure service model & the Windows Azure Fabric Controller (FC) is still in charge of everything. Although you uploaded your own prepared VM the FC may and will decide to take your VM instances offline, start new instances, reprogram the load balancers etc.
Yes, Windows Azure Compute is about PaaS (Platform-as-a-Service), also with the VM role now in place. Don’t get confused by the new role feature name. Your applications (and thus roles!) need to be state-agnostic.
BTW: What is not possible with the VM role today is automatic OS updates/patching.
This means that you have no feasible option to have an up-to-date OS. When you try to run Windows Update this might work (actually it should). But then two things can happen:
- your VM needs to reboot due to the Windows Update patches
- FC decides to reboot your VM, or take it offline and hook up an new instance
In either case you end up with your original VM – bingo (and in the first case you will feel like in Groundhog Day… “Hey babe –dududu – I got you babe…”). Therefore, the official hands-on lab illustrates to disable WU entirely.
Think about the Windows Azure VM role, twice.