Skip to content

Latest commit

 

History

History
74 lines (50 loc) · 5.68 KB

cloud-services-deployment-faq.md

File metadata and controls

74 lines (50 loc) · 5.68 KB
Raw
title description services documentationcenter author manager editor tags ms.assetid ms.service ms.workload ms.tgt_pltfrm ms.devlang ms.topic ms.date ms.author
Deployment issues for Microsoft Azure Cloud Services FAQ| Microsoft Docs
This article lists the frequently asked questions about deployment for Microsoft Azure Cloud Services.
cloud-services
genlin
cshepard
top-support-issue
84985660-2cfd-483a-8378-50eef6a0151d
cloud-services
na
na
na
article
9/20/2017
genli

Deployment issues for Azure Cloud Services: Frequently asked questions (FAQs)

This article includes frequently asked questions about deployment issues for Microsoft Azure Cloud Services. You can also consult the Cloud Services VM Size page for size information.

[!INCLUDE support-disclaimer]

Why does deploying a cloud service to the staging slot sometimes fail with a resource allocation error if there is already an existing deployment in the production slot?

If a cloud service has a deployment in either slot, the entire cloud service is pinned to a specific cluster. This means that if a deployment already exists in the production slot, a new staging deployment can only be allocated in the same cluster as the production slot.

Allocation failures occur when the cluster where your cloud service is located does not have enough physical compute resources to satisfy your deployment request.

For help mitigating such allocation failures, see Cloud Service allocation failure: Solutions.

Why does scaling up or scaling out a cloud service deployment sometimes result in allocation failure?

When a cloud service is deployed, it usually gets pinned to a specific cluster. This means scaling up/out an existing cloud service must allocate new instances in the same cluster. If the cluster is nearing capacity or the desired VM size/type is not available, the request may fail.

For help mitigating such allocation failures, see Cloud Service allocation failure: Solutions.

Why does deploying a cloud service into an affinity group sometimes result in allocation failure?

A new deployment to an empty cloud service can be allocated by the fabric in any cluster in that region, unless the cloud service is pinned to an affinity group. Deployments to the same affinity group will be attempted on the same cluster. If the cluster is nearing capacity, the request may fail.

For help mitigating such allocation failures, see Cloud Service allocation failure: Solutions.

Why does changing VM size or adding a new VM to an existing cloud service sometimes result in allocation failure?

The clusters in a datacenter may have different configurations of machine types (e.g., A series, Av2 series, D series, Dv2 series, G series, H series, etc.). But not all the clusters would necessarily have all the kinds of VMs. For example, if you try to add a D series VM to a cloud service that is already deployed in an A series-only cluster, you will experience an allocation failure. This will also happen if you try to change VM SKU sizes (for example, switching from an A series to a D series).

For help mitigating such allocation failures, see Cloud Service allocation failure: Solutions.

To check the sizes available in your region, see Microsoft Azure: Products available by region.

Why does deploying a cloud service sometime fail due to limits/quotas/constraints on my subscription or service?

Deployment of a cloud service may fail if the resources that are required to be allocated exceed the default or maximum quota allowed for your service at the region/datacenter level. For more information, see Cloud Services limits.

You could also track the current usage/quota for your subscription at the portal: Azure portal => Subscriptions => <appropriate subscription> => “Usage + quota”.

Resource usage/consumption-related information can also be retrieved via the Azure Billing APIs. See Azure Resource Usage API (Preview).

How can I change the size of a deployed cloud service VM without redeploying it?

You cannot change the VM size of a deployed cloud service without redeploying it. The VM size is built into the CSDEF, which can only be updated with a redeploy.

For more information, see How to update a cloud service.

Why am I not able to deploy Cloud Services through Service Management APIs or PowerShell when using Azure Resource Manager Storage account? 

Since the Cloud Service is a Classic resource which is not directly compatible with the Azure Resource Manager model, you can't associate it with the Azure Resource Manager Storage accounts. Here are few options:   

  • Deploying through REST API.

    When you deploy through Service Management REST API, you could get around the limitation by specifying a SAS URL to the blob storage, which will work with both Classic and Azure Resource Manager Storage account. Read more about the 'PackageUrl' property here.  

  • Deploying through Azure portal.

    This will work from the Azure portal as the call goes through a proxy/shim which allows communication between Azure Resource Manager and Classic resources.