You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/cloud-services/cloud-services-connectivity-and-networking-faq.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: This article lists the frequently asked questions about connectivit
4
4
services: cloud-services
5
5
documentationcenter: ''
6
6
author: genlin
7
-
manager: cshepard
7
+
manager: dcscontentpm
8
8
editor: ''
9
9
tags: top-support-issue
10
10
ms.assetid: 84985660-2cfd-483a-8378-50eef6a0151d
@@ -97,7 +97,7 @@ To make sure the public-facing IP address of your cloud service (also known as a
97
97
-[Reserve the IP address of an existing cloud service](../virtual-network/virtual-networks-reserved-public-ip.md#reserve-the-ip-address-of-an-existing-cloud-service)
98
98
-[Associate a reserved IP to a cloud service by using a service configuration file](../virtual-network/virtual-networks-reserved-public-ip.md#associate-a-reserved-ip-to-a-cloud-service-by-using-a-service-configuration-file)
99
99
100
-
If you have more than one instance for your roles, associating RIP with your cloud service shouldn't cause any downtime.Alternatively, you can whitelist the IP range of your Azure datacenter.You can find all Azure IP ranges at the [Microsoft Download Center](https://www.microsoft.com/en-us/download/details.aspx?id=41653).
100
+
If you have more than one instance for your roles, associating RIP with your cloud service shouldn't cause any downtime.Alternatively, you can add the IP range of your Azure datacenter to an allow list. You can find all Azure IP ranges at the [Microsoft Download Center](https://www.microsoft.com/en-us/download/details.aspx?id=41653).
101
101
102
102
This file contains the IP address ranges (including compute, SQL, and storage ranges) used in Azure datacenters. An updated file is posted weekly that reflects the currently deployed ranges and any upcoming changes to the IP ranges. New ranges that appear in the file aren't used in the datacenters for at least one week. Download the new .xml file every week, and perform the necessary changes on your site to correctly identify services running in Azure. Azure ExpressRoute users might note that this file used to update the BGP advertisement of Azure space in the first week of each month.
Copy file name to clipboardExpand all lines: articles/cloud-services/cloud-services-deployment-faq.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: This article lists the frequently asked questions about deployment
4
4
services: cloud-services
5
5
documentationcenter: ''
6
6
author: genlin
7
-
manager: cshepard
7
+
manager: dcscontentpm
8
8
editor: ''
9
9
tags: top-support-issue
10
10
ms.assetid: 84985660-2cfd-483a-8378-50eef6a0151d
@@ -26,22 +26,22 @@ If a cloud service has a deployment in either slot, the entire cloud service is
26
26
27
27
Allocation failures occur when the cluster where your cloud service is located does not have enough physical compute resources to satisfy your deployment request.
28
28
29
-
For help mitigating such allocation failures, see [Cloud Service allocation failure: Solutions](cloud-services-allocation-failures.md#solutions).
29
+
For help with mitigating such allocation failures, see [Cloud Service allocation failure: Solutions](cloud-services-allocation-failures.md#solutions).
30
30
31
31
## Why does scaling up or scaling out a cloud service deployment sometimes result in allocation failure?
32
32
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.
33
33
34
-
For help mitigating such allocation failures, see [Cloud Service allocation failure: Solutions](cloud-services-allocation-failures.md#solutions).
34
+
For help with mitigating such allocation failures, see [Cloud Service allocation failure: Solutions](cloud-services-allocation-failures.md#solutions).
35
35
36
36
## Why does deploying a cloud service into an affinity group sometimes result in allocation failure?
37
37
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.
38
38
39
-
For help mitigating such allocation failures, see [Cloud Service allocation failure: Solutions](cloud-services-allocation-failures.md#solutions).
39
+
For help with mitigating such allocation failures, see [Cloud Service allocation failure: Solutions](cloud-services-allocation-failures.md#solutions).
40
40
41
41
## Why does changing VM size or adding a new VM to an existing cloud service sometimes result in allocation failure?
42
-
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).
42
+
The clusters in a datacenter may have different configurations of machine types (for example, 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).
43
43
44
-
For help mitigating such allocation failures, see [Cloud Service allocation failure: Solutions](cloud-services-allocation-failures.md#solutions).
44
+
For help with mitigating such allocation failures, see [Cloud Service allocation failure: Solutions](cloud-services-allocation-failures.md#solutions).
45
45
46
46
To check the sizes available in your region, see [Microsoft Azure: Products available by region](https://azure.microsoft.com/regions/services).
47
47
@@ -59,15 +59,15 @@ For more information, see [How to update a cloud service](cloud-services-update-
59
59
60
60
## Why am I not able to deploy Cloud Services through Service Management APIs or PowerShell when using Azure Resource Manager Storage account?
61
61
62
-
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:
62
+
Since the Cloud Service is a Classic resource that 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:
63
63
64
64
- Deploying through REST API.
65
65
66
66
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](/previous-versions/azure/reference/ee460813(v=azure.100)).
67
67
68
68
- Deploying through [Azure portal](https://portal.azure.com).
69
69
70
-
This will work from the [Azure portal](https://portal.azure.com) as the call goes through a proxy/shim which allows communication between Azure Resource Manager and Classic resources.
70
+
This will work from the [Azure portal](https://portal.azure.com) as the call goes through a proxy/shim that allows communication between Azure Resource Manager and Classic resources.
71
71
72
72
## Why does Azure portal require me to provide a storage account for deployment?
Copy file name to clipboardExpand all lines: articles/cloud-services/cloud-services-workflow-process.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: This article provides overview of the workflow processes when you d
4
4
services: cloud-services
5
5
documentationcenter: ''
6
6
author: genlin
7
-
manager: Willchen
7
+
manager: dcscontentpm
8
8
editor: ''
9
9
tags: top-support-issue
10
10
ms.assetid: 9f2af8dd-2012-4b36-9dd5-19bf6a67e47d
@@ -37,7 +37,7 @@ The following diagram presents the architecture of Azure resources.
37
37
38
38
**D**. WindowsAzureGuestAgent is responsible for the following:
39
39
40
-
1. Configuring the Guest OS including firewall, ACLs, LocalStorage resources, service package and configuration, and certificates.Setting up the SID for the user account that the role will run under.
40
+
1. Configuring the Guest OS including firewall, ACLs, LocalStorage resources, service package and configuration, and certificates.Setting up the SID for the user account that the role will run under.
41
41
2. Communicating the role status to the fabric.
42
42
3. Starting WaHostBootstrapper and monitoring it to make sure that the role is in goal state.
43
43
@@ -54,7 +54,7 @@ The following diagram presents the architecture of Azure resources.
54
54
3. Setting up the AppPool for the configured role in the service model
55
55
4. Setting up IIS logging to point to the DiagnosticStore LocalStorage folder
56
56
5. Configuring permissions and ACLs
57
-
6. The website resides in %roleroot%:\sitesroot\0, and the apppool points to this location to run IIS.
57
+
6. The website resides in %roleroot%:\sitesroot\0, and the AppPool points to this location to run IIS.
58
58
59
59
**G**. Startup tasks are defined by the role model and started by WaHostBootstrapper. Startup tasks can be configured to run in the background asynchronously, and the host bootstrapper will start the startup task and then continue on to other startup tasks. Startup tasks can also be configured to run in Simple (default) mode in which the host bootstrapper will wait for the startup task to finish running and return a success (0) exit code before continuing to the next startup task.
60
60
@@ -70,7 +70,7 @@ The following diagram presents the architecture of Azure resources.
70
70
71
71
## Workflow processes
72
72
73
-
1. A user makes a request, such as uploading .cspkg and .cscfg files, telling a resource to stop or making a configuration change, and so on. This can be done through the Azure portal or a tool that uses the Service Management API, such as the Visual Studio Publish feature. This request goes to RDFE to do all the subscription-related work and then communicate the request to FFE. The rest of these workflow steps are to deploy a new package and start it.
73
+
1. A user makes a request, such as uploading ".cspkg" and ".cscfg" files, telling a resource to stop or making a configuration change, and so on. This can be done through the Azure portal or a tool that uses the Service Management API, such as the Visual Studio Publish feature. This request goes to RDFE to do all the subscription-related work and then communicate the request to FFE. The rest of these workflow steps are to deploy a new package and start it.
74
74
2. FFE finds the correct machine pool (based on customer input such, as affinity group or geographical location plus input from the fabric, such as machine availability) and communicates with the master fabric controller in that machine pool.
75
75
3. The fabric controller finds a host that has available CPU cores (or spins up a new host). The service package and configuration is copied to the host, and the fabric controller communicates with the host agent on the host OS to deploy the package (configure DIPs, ports, guest OS, and so on).
76
76
4. The host agent starts the Guest OS and communicates with the guest agent (WindowsAzureGuestAgent). The host sends heartbeats to the guest to make sure that the role is working towards its goal state.
@@ -79,7 +79,7 @@ The following diagram presents the architecture of Azure resources.
79
79
7. WaHostBootstrapper reads the **Startup** tasks from E:\RoleModel.xml and begins executing startup tasks. WaHostBootstrapper waits until all Simple startup tasks have finished and returned a “success” message.
80
80
8. For Full IIS web roles, WaHostBootstrapper tells IISConfigurator to configure the IIS AppPool and points the site to `E:\Sitesroot\<index>`, where `<index>` is a 0 based index into the number of `<Sites>` elements defined for the service.
81
81
9. WaHostBootstrapper will start the host process depending on the role type:
82
-
1.**Worker Role**: WaWorkerHost.exe is started. WaHostBootstrapper executes the OnStart() method.After it returns, WaHostBootstrapper starts to execute the Run() method, and then simultaneously marks the role as Ready and puts it into the load balancer rotation (if InputEndpoints are defined). WaHostBootsrapper then goes into a loop of checking the role status.
82
+
1.**Worker Role**: WaWorkerHost.exe is started. WaHostBootstrapper executes the OnStart() method.After it returns, WaHostBootstrapper starts to execute the Run() method, and then simultaneously marks the role as Ready and puts it into the load balancer rotation (if InputEndpoints are defined). WaHostBootsrapper then goes into a loop of checking the role status.
83
83
1.**SDK 1.2 HWC Web Role**: WaWebHost is started. WaHostBootstrapper executes the OnStart() method. After it returns, WaHostBootstrapper starts to execute the Run() method, and then simultaneously marks the role as Ready and puts it into the load balancer rotation. WaWebHost issues a warmup request (GET /do.rd_runtime_init). All web requests are sent to WaWebHost.exe. WaHostBootsrapper then goes into a loop of checking the role status.
84
84
1.**Full IIS Web Role**: aIISHost is started. WaHostBootstrapper executes the OnStart() method. After it returns, it starts to execute the Run() method, and then simultaneously marks the role as Ready and puts it into the load balancer rotation. WaHostBootsrapper then goes into a loop of checking the role status.
85
85
10. Incoming web requests to a Full IIS web role triggers IIS to start the W3WP process and serve the request, the same as it would in an on-premises IIS environment.
0 commit comments