How To Take Photographs From Windows 8 Applications And Automatically Upload Them To The Cloud–Part 5 of 6

Deploying to a Microsoft Data Center

1. This is an exciting section.
2. I'm going to guide you step by step in getting our web service up into a fully redundant cluster of IIS and hosted web roles.
3. I will show you how to deploy three instances of our service, All of them automatically load balanced and updateable without down time.
4. We will tap into a giant globally dispersed mega Data Centers.
5. We will use the portal to set this all up.
6. We will create a hosted service.
7. We will create a storage account.
8. We will deploy through the portal.

1. Windows Azure is the Microsoft public cloud platform, offering the biggest global reach and the most comprehensive service backend.
2. It supports the use of multiple OS, language, database and tool, providing automatic OS and service patching.
3. The network infrastructure behind it offers automatic load balancing and resiliency to hardware failure.
4. Last, but not least, it supports a deployment model that enables developers to upgrade applications without downtime.

1. We will need to create both a hosted account and a storage account at the portal.
2. If we want to store our photos in a Microsoft Data Center to make them available to the world, we will need a storage account.
3. Once again, this can be done at the portal.
4. If you don't have an account, here is how to get a trial account. It is FREE for 90 days.
   • http://www.microsoft.com/click/services/Redirect2.ashx?CR_CC=200114759

1. Once you have signed up to the Azure Portal, Login into the Azure Portal.
2. Follow the red boxes to navigate to Storage Accounts
3. Click New Storage Account. Specify a globally unique URL.

1. We will need to paste this URL into our Windows 8 Application.
2. You also need to choose from among several global data centers.
   • Notice I chose West US.
   • You could also replicate and route requests between data centers
3. Click OK

1. At this point the storage account has been created successfully.
2. The next step is to view the access keys.
3. We will need to paste in the Access Keys into our ASP.NET MVC Web API application.
4. Think of Access Keys being the password for the web service to be able to generate a Shared Access Signature.
5. After all, it wouldn't make sense for just any Web Service to be able to grant Shared Access Signatures on a the Azure Storage Service.
6. Take special note of the Access keys
7. At this point the storage account has been created successfully.
8. The next step is to view the access keys.
9. We will need to paste in the Access Keys into our ASP.NET MVC Web API application.

1. You will need to copy the access key to the clipboard so that you can paste it into our Web Service project.
2. Essentially, we have the two things we need for our web service
1. , the name of the storage account
1. brunoterkalyphotos
2. the access key
1. eTzHRURU3552j345kl3j4hY2cR53KYH1bxOqlzuyd04G0FlMimufaJ+Gw23fdgjasdgg==
3. Return back to Visual Studio and the Web Service project.
4. In Solution Explorer, double-click on Web.config.
5. Just under the <AppSetttings> section, add the following DataConnectionString (lines 31 to 33)

1. Now that we have the storage account created, we now need to create a hosted service.
2. A hosted service is simply a running instance of a web service inside IIS, inside Windows Server, inside a VM in a Microsoft Data Center.
3. We will deploy our web service to the hosted service we create at the portal.
4. We will choose our hosted service to be located in the same data center as our storage account.
5. This makes sense for both performance and economic reasons.
   • Login into the Azure Portal.
   • Follow the red boxes above to navigate to the Hosted Service section.

1. As we did with the storage account, we will now and two are some of the basic information necessary to creating a host that account.
2. You will need to indicate a URL for your service as well as the region.
3. Be sure to select the do not deploy radio button.
4. We will deploy momentarily.
5. It is important to remember that the URL that we entered above will need to be incorporated into the Windows 8 application we created previously.

1. There are three basic steps before we're ready to test everything. They include:
   • Updating the web service code to use the freshly entered storage account information.
   • Creating a deployment package of our web service and deploying it in a web role as a web service through the portal.
   • Updating the Windows 8 application to make use of the URL specified at the big red arrow above.

1. I am intentionally repeating myself below.
2. We have already updated the web.config file with the storage account information.
3. We will need to modify some code in the action method Get(), to make use of the DataConnectionString.
4. Currently it uses the development storage account information, which is essentially the local storage emulator.
5. You will now modify the web service to use the DataConnectionString setting in web.config.
6. We will now make use of the storage account that we created at the portal.
7. In a nutshell, we are modifying the ValuesController.cs file to support new DataConnectionString
8. We have already updated the web.config file with the storage account information from the portal
9. We will need to modify some code in the action method Get(), to make use of the DataConnectionString. Currently it uses the development storage account information, which is essentially the local storage emulator. This is good for testing purposes, but will not work in a production environment.
10. Double-click on the ValuesController.cs file
11. Modify the code to look like the diagram above. (Modifying the web service to use the DataConnectionString)

1. The modifications to our web service are complete. To deploy this application there are only two steps involved:
2. Before creating the package file, you might decide that you want more than one instance of our deployed application.
3. In other words, if we specify any instance count of 3, Windows Azure will automatically create 3 copies of our application, running on 3 CPU cores, on separate racks and fault domains.

1. It is a simple step of modifying the project properties and changing the instance count as follows:
2. Changing the Instance Count to 3

1. Right mouse click on the web service configuration project and select Package

1. We wish to use our cloud configuration project and this is a release version.
2. Click package.

1. This is where we use the portal to actually upload the files generated by the package process just described.
2. As soon as we click the OK button after having selected our configuration and package file, the deployment process begins now.

1. Click to browse locally buttons and select the package files just to generated.
2. Once again, when you click OK the deployment process begins.

1. You can see that after a few minutes my deployment did succeed .
2. Notice the three instances are running.
3. This is a beautiful thing.
   • I just change one member in a property of my Visual Studio project, And the result is a nice clean triply load-balanced web service .
4. I can do upgrades without bringing my users down.
5. I can grow and shrink this number very easily.
6. I can change my instance counter the portal or to some code.
   • I can even automate the process based on performance counters .
     • I may wish to use CPU utilization disk I owe or memory consumption as my guidelines for growing or shrinking scale .

1. Just one more post.
1. Adjusting the Windows 8 Client app to talk to our hosted service
2. Final testing and wrap up
2. Download the free trial
   • You will need a trial account for Windows Azure
     • Please sign up for it here:
       • http://www.microsoft.com/click/services/Redirect2.ashx?CR_CC=200114759