none
Creating Azure VM role RRS feed

  • Question

  • Already enrolled in the VM role beta program. But it looks like a tedious process to create a Azure VM role. It seems one has to create a base VHD and then configure and then install some azure components and then some thing else and finally upload to windows azure. Is that so complicated to just get a hosted vhd(VM role) on azure. why cant microsoft provide a base VHD that can be directly deployed onto azure.  Is there a standard base VHD already available some where that we can upload to individuals account? Does one invariably need to have Hyper-V Manager to start working on the VM role? I dont see this kind of complication with Amazon EC2. There are instance templates already created and you just start and use the instance.  Am I missing something?

    http://msdn.microsoft.com/en-us/library/gg465391.aspx

    http://msdn.microsoft.com/en-us/library/gg465373.aspx

     

     

    Tuesday, February 1, 2011 6:22 AM

Answers

  • Keep in mind that Azure is not IaaS. The VM role is only for situations where the standard VM templates (aka roles) don't work for you.

     


    Dominick Baier | thinktecture | http://www.leastprivilege.com
    • Proposed as answer by Patriek van Dorp Monday, February 7, 2011 9:24 AM
    • Marked as answer by Mog Liang Tuesday, February 8, 2011 8:30 AM
    Wednesday, February 2, 2011 6:45 AM
  • You shouldn't confuse Azure VM Role as an IaaS offering as with Amazon EC2. Azure VM Role is meant to be a service only just as web and worker roles, as in the end you are creating a service model to point to a vhd and deploying it. You should go for VM Role only when you have by no means an option left to use web/worker roles even with admin mode startup tasks. 
    TechyFreak | Mobile Development Resources
    • Proposed as answer by Patriek van Dorp Monday, February 7, 2011 9:24 AM
    • Marked as answer by Mog Liang Tuesday, February 8, 2011 8:30 AM
    Sunday, February 6, 2011 8:54 PM

All replies

  • Keep in mind that Azure is not IaaS. The VM role is only for situations where the standard VM templates (aka roles) don't work for you.

     


    Dominick Baier | thinktecture | http://www.leastprivilege.com
    • Proposed as answer by Patriek van Dorp Monday, February 7, 2011 9:24 AM
    • Marked as answer by Mog Liang Tuesday, February 8, 2011 8:30 AM
    Wednesday, February 2, 2011 6:45 AM
  • You shouldn't confuse Azure VM Role as an IaaS offering as with Amazon EC2. Azure VM Role is meant to be a service only just as web and worker roles, as in the end you are creating a service model to point to a vhd and deploying it. You should go for VM Role only when you have by no means an option left to use web/worker roles even with admin mode startup tasks. 
    TechyFreak | Mobile Development Resources
    • Proposed as answer by Patriek van Dorp Monday, February 7, 2011 9:24 AM
    • Marked as answer by Mog Liang Tuesday, February 8, 2011 8:30 AM
    Sunday, February 6, 2011 8:54 PM