Geek Answers Handbook

Porting Web Roles to Windows Azure Virtual Machines

I have a web role running on Windows Azure and I have included two instances in my web role.

I decided to use the Windows Azure virtual machine to run my Windows Azure web role. I cannot find a migration document to transfer my role to the Windows Azure virtual machine. On the portal, I see git, TFS, and FTP migrations for Windows Azure sites, but not for the Windows Azure virtual machine.

What is the best way to port my web role to a Windows Azure virtual machine.

+4
source share
2 answers

If you use Windows Azure Virtual Machines, you own the virtual machines, so you decide how you want to deploy your application. Since when you decide to use Windows Azure Virtual Machines, you can use the “Virtual Stock Image” (from the gallery), or you can deploy your own VHD, you have the freedom to choose the deployment method for your application, and that’s why there is an option on Windows Azure portal. (With Windows Azure WebSites, you don’t have that freedom, and so GIT, FTP, TFS, and WebDeploy methods are provided to those who choose to choose Windows Azure websites.)

As you are trying to port the Windows Azure web role to virtual machines, the best option comes to my mind, below which I suggested to several other partners:

  • Extract the web role application from the Windows Azure Web Role solution so that you, regardless of the ASP.NET web application
  • Now you can use the WebDeploy method with this application.

To configure WebDeploy on a Windows Azure virtual machine, you need to do the following:

  • Install .Net 3.5 on Windows Azure Virtual Machine.
  • Install Web deploy 2.0 from the download link here .
  • Configure Web Deployment. Full steps can be found here.
  • Create a new 8172 endpoint port as open and closed for deployment on the Internet on your Windows Azure virtual machines.
  • Now use the VS2010 application and just deploy the application using the Visual Studio Publishing Wizard

Please note that if you do not want to use VS2010-based WebDeploy, you can first package your application and then RDP on your Windows Azure virtual machine and install it there. Since the Windows Azure virtual machine saves data, this step is much simpler, but very different from network deployment, but is the right choice.

+5
source

There are 3 modes of Windows Azure, and all 3 can launch a website.

  • Windows Azure Websites (WAWS)
  • Cloud services (platform as a service)
  • Virtual machines (infrastructure as a service)

In solving your web role exsting uses Cloud Service (PaaS). To upgrade to WAWS or virtual machines, you need to do the following (I assume Visual Studio is used here):

  • Make a copy of the existing solution and remove the Windows Azure project from it, leaving only the web project.
  • Using the new Windows Azure portal, provide the WAWS website or virtual machine.
  • Record your access accounts. When using WAWS, specify and remember the deployment credentials. When using virtual machines, configure and remember the credentials of the remote desktop.
  • Deploy web project files in the cloud. If using WAWS, select the deployment method (Web Deploy, FTP, Git, TFS) and deploy it from Visual Studio. When using virtual machines, invoke the remote desktop, configure shared access to the local disk, connect to the virtual machine, configure IIS and transfer files.

Since all 3 modes can be used to host a website, you can consider the following before deciding:

  • WAWS - for two-tier websites without a standard IIS configuration; for you; maintains portability between the cloud and in place. You share virtual machines with others if you are not promoting them from sharing to backup. Intense VM capabilities shared insistence. For Windows Server and IIS only; May use SQL Database or MySQL.

  • Cloud services - managed for you, can support universal architectures, powerful services available for storage, database, identification, communication, caching, virtual network. Your virtual machines are exclusively yours. Virtual machines have no persistence. For Windows Server only.

  • Virtual machines - you manage, you can support universal architectures; maintains portability. Your virtual machines are exclusively yours. You can capture a virtual machine and add it to the image gallery to easily create new instances. Virtual machines have individual perseverance. Windows Server or Linux.

+7
source

More articles:


All Articles