Demo ScriptDeploying My To Do ApplicationLab version: 2.0.0

Last updated: 5/9/2023

Prepared by: Ryan Dunn

Contents

OVERVIEW................................................................................................................................................. 3Key Messages......................................................................................................................................... 3

Key Technologies.................................................................................................................................... 3

Time Estimates........................................................................................................................................ 4

SETUP AND CONFIGURATION................................................................................................................. 4

DEMO FLOW.............................................................................................................................................. 4

OPENING STATEMENT............................................................................................................................. 5

STEP-BY-STEP WALKTHROUGH.............................................................................................................6Deploying the Application........................................................................................................................ 6

SUMMARY................................................................................................................................................ 15

KNOWN ISSUES...................................................................................................................................... 15

Overview

This document provides setup documentation, step-by-step instructions, and a written script for showing a demo of Windows Azure. This document can also serve as a tutorial or walkthrough of the technology. In this demo you will deploy a simple To Do list application to Windows Azure. For additional demos of the Azure Services Platform, please visit http://www.azure.com.

Note: In order to run through this complete demo, you must have network connectivity and a Live Id. You will also need a token if you wish to show token redemption.

Key Messages

In this demo you will see two key things:

1. How you can easily deploy applications and services to Windows Azure.

2. How you can easily scale applications via the Windows Azure portal.

Key Technologies

This demo uses the following technologies:

1. Windows Azure Portal

Time Estimates

Estimated time for setting up and configuring the demo: 5 min

Estimated time to complete the demo: 10 min

Setup and Configuration

This demo does not have any advanced configuration requirements. You simply need a web browser and a live id account. You only need to do these steps once.

1. Find the MyTodo.cspkg and ServiceConfiguration.cscfg files in the Assets directory. By default this would be found at C:\WAPTK\Demos\DeployWindowsAzure\Assets

2. We recommend to navigate to the Windows Azure portal and save this link on the IE favorites.

3. When demoing this, you should deploy your own copy of myTODO. Due to time constraints or any failure during provisioning, it is best to have a copy ready to show them while the attendees wait.

Demo Flow

The following diagram illustrates the high-level flow for this demo and the steps involved:

Figure 1Diagram

Opening Statement

In the next 5 minutes, we will show you how to deploy a simple TODO list creation and sharing application into Windows Azure. We will provision servers and network equipment without leaving our chair.

In this simple, Deployment demo you will specifically see two key things:

1. How you can easily deploy applications to the cloud without need to provisioning servers, load balances and other data center equipment.

2. How you can change the number of instances running the service with a few clicks.

Step-by-Step Walkthrough

This demo is composed of the following segments:

Deploying the application

Note: it’s best to let the customer drive this demo, you can guide them.

Deploying the Application

Action Script Screenshot

1. Open the Web Browser and navigate to the Windows Azure Portal at http://windows.azure.com

2. Sign in with the customers live id.

Let us first navigate to the Windows Azure portal and get you signed in.

We use live id for authentication on the portal – so lets get you logged in

NOTE: If they do not have a live id, have them signup for a new one – its instant.

3. The first time you sign into the portal, you will be asked to accept the agreement, and then you can redeem your token. Give them a token to redeem and have them enter it

To enable you to deploy an application you need a token. [give them a token] – this tells cloud that you have permission to deploy applications

4. Select the PDC08 CTP Project from the list under My Projects.

Here we have a list of projects associated to our LiveID

Also we will find the projects that we have purchased using our credit cards here for instance.

5. Click New Service, and then select Storage Account.

The application we will deploy requires both compute and storage.

First, we will create the storage account.

The storage account will give the application access to queues, blobs and tables. These are not SQL Azure tables, but Windows Azure Tables.

6. Enter a service label (such as davidtododb) and click Next.

We have to give the storage account a friendly name.

7. Enter the same name for the Public Storage Account Name.

8. Select the Region.

9. Check to make sure the account is available and then click Create.

It’s good to make the project and dns names for storage the same. However if the name is already taken you will need to think of another name.

We’d like to create the regions in the SW of the USA.

Once we launch, you will be able to select other regions around the world.

10. Copy the Primary Access Key and the dns name to notepad.

The dns name and the primary access key are the 2 pieces of information used when accessing storage. Without the access key, you cannot access storage.

We need these values when we deploy the application.

11. On the Windows Azure Portal, click New Service, and then select Hosted Services.

12. Enter a service label (such as davidMyToDo) and click Next.

Now that we have the storage project, we can create the Hosted service project and deploy the application.

Again we create a new application.

13. Enter the same name for the Public Service Name.

14. Select the Region.

15. Check to make sure the account is available and then click Create.

Again the name must be unique for the dns name.

It’s a good idea to keep the storage and compute in the same place. Although we don’t do it in this demo, we could have created an affinity group, which helps you keep storage and compute in the same regions.

16. When the project screen appears, go to Staging section and click Deploy.

Now the project is ready, we can start to deploy.

17. For the Application Package, upload MyTodo.cspkg.

18. For the Configuration Settings, upload ServiceConfiguration.cscfg.

19. For the OS Upgrade Method, select Automatic.

20. Enter v1 as the label for deployment. Click Deploy.

The Todo application is all ready to go. It was built using Visual Studio 2010.

The application was packaged up into the 2 files required. One is the actual application (the app package) and the other is the configuration file.

The configuration file contains storage details, as well as data that the cloud uses to deploy the application. We will edit this file and add the storage information shortly.

In general, it is recommended to use the latest available OS to take advantage of new features and security fixes.

21. Do nothing while the package deploys

Deployment should only take a minute or 2.

During deployment, the configuration file is analysed by Windows Azure. The service is then copied to the correct number of machines ready to start. Any load balancers, network devices and monitoring are also configured during this time.

22. Once the package has deployed, click Configure.

Once the package is deployed, we need to update the configuration and enter the details we copied to notepad earlier.

23. Replace the prompts with the key you copied to notepad earlier and the name of the storage account you created earlier.

24. Click Save

The configuration file contains 3 things we need to change.

First we copy the account dns name. Then we copy the shared key. There

are placeholders in the configuration file for these.

Next find the number of instance at the bottom and change the value 1 to 2. (unless we are giving out higher values, then change it to 5 (or higher)).

25. Once the package has updated, click Run.

Now Windows Azure is updating the configuration across the instances, in a few minutes there will be 2 (or more) instances ready.

Once that is finished, click run. NOTE: This can take a good few

minutes to complete.5+. It’s good at this point to appreciate

we haven’t touched anything more complicated that cut and paste.

Windows Azure is provisioning servers, load balancers and other networking devices. It’s also getting ready to monitor our app once we run it. All with a few mouse clicks at a booth in a conference.

Once its running in Windows Azure – it will also take care of patching the OS, recovering from hardware failure, ensuring storage is available. Again you don’t have to do anything here. Windows Azure takes care of it.

If the package is take a while to deploy, you may want to navigate to your to do list application and show them what it looks like.

If they need to leave, you can point out the next step so they can do it later.

26. Once the package is running, click the Swap button (that is the round button between the Staging and Production areas)

Now the service is running in “Staging” this is actually a virtual place as there is no physical difference between staging and production – it simple depends on where the load balancer is connected.

In the future, you will be able to have multiple “virtual” areas, for test, qa, pre-production etc. You will also be able to automate deployment and management of the services within these areas using the management API.

How many partners can really spin up test & QA environments in minutes?

We can swap from staging to production with a mouse click.

27. Once its swapped wait a minute before clicking on the URL.

Once the service is in production, give it a few seconds for the dns to propagate. Then you can click on the link and be taken to the application they deployed.

If you get a 404 errors, simply try again in a minute.

28. Click Start When the service runs for the first time, you have to create an account.

29. Have the customer enter their details Complete the account details. These are stored in the storage account created earlier. Data is not shared between to do lists.

Summary

In this demo, you saw how easy it was to create storage and compute accounts, deploy, and run applications to the cloud.

Known Issues

Please note the following known issues with this demo:

It can sometimes take several minutes to start a Windows Azure application in the cloud.

With the current CTP version of Windows Azure you are limited to two instances of a role.