Testing and Deployment: Quality Is King - Deploying and Managing a Cloud Infrastructure - page 307

In the staging environment, the service's globally unique identifier (GUID) identifies
the cloud service in URLs (e.g., GUID.cloudapp.net ). The subdomain name that the
user entered while creating the service is reserved to be used with the production envi-
ronment. Once the service is deployed, users can use the Swap option to redirect client
requests to the production deployment. Figure 10.8 shows uploading the service and
its associated package ( .cspkg ) and configuration ( .cscfg ). We used a C# Hello World
example. Both the package and configuration are built and packaged using Microsoft
Visual Studio.
FIGURE 10.8 Uploading cloud service package and configuration
5. If the cloud service will include any roles with only one instance, select the “Deploy
even if one or more roles contain a single instance” check box to enable the deployment
to proceed.
Windows Azure can guarantee only 99.95 percent access to the cloud service during
maintenance and service updates if every role has at least two instances. The user can
add additional role instances on the Scale page after you deploy the cloud service.
The user can monitor the status of the deployment in the notifications area, as shown in
Figure 10.9.
To verify that the staging deployment has completed successfully, the user can click the
site URL under the cloud service dashboard, as shown in Figure 10.10.
The dashboard gives a number of options to the user, including monitoring, Quick
Glance, Operation Logs, Autoscale Status, Usage Overview, Linked Resources, and more.