search

MicrosoftDocs / azure-docs

Open source documentation of Microsoft Azure
https://docs.microsoft.com/azure
Creative Commons Attribution 4.0 International
10.25k stars 21.42k forks source link

ASEv2 Zone deployment -- clarification? #65291

Closed larryclaman closed 2 years ago

larryclaman commented 3 years ago

Two clarification questions about this page:

  1. If you do not do the steps on this page (eg you deploy an ASE with an ILB through the portal), is the ASE deployed across multiple zones? If not, what redundancy does it have? Are the scale units deployed instead across multiple availability sets / fault domains / update domains?

  2. Where the document says " If you pin your ILB ASE to a specific AZ, the resources used by a ILB ASE will either be pinned to the specified AZ, or deployed in a zone redundant manner", could you clarify the last phrase: "...or deployed in a zone redundant manner". When would an ASEv2 with an ILB be deployed in a zone redundant manner? Do you mean by following the steps later in this article?

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

RyanHill-MSFT commented 3 years ago

Thanks for the feedback! We are currently investigating and will update you shortly.

RyanHill-MSFT commented 3 years ago

Hi @larryclaman, I did not notice the steps you were referring to, but I did want to clarify if you mean deploying an ASE through an ARM template or through the CLI? When it comes to how appropriately setup your ASE for high availability, https://docs.microsoft.com/en-us/azure/architecture/reference-architectures/enterprise-integration/ase-high-availability-deployment is a great reference doc but no, ASEs aren't deployed across AZs by default. Furthermore, scale units aren't deployed across availability sets.

With regards to ...or deployed in a zone redundant manner, I'll confer witht the content author for clarification.

larryclaman commented 3 years ago

Hi @RyanHill-MSFT, When I referred to 'not following the steps on this page', I indeed meant "if you deploy an ASE via the portal or cli".

Per your comment "ASEs aren't deployed across AZs by default. Furthermore, scale units aren't deployed across availability sets." -> Yes, this is exactly the type of clarification that I would like to see added to the ASE documentation.

For example, you referred to the page https://docs.microsoft.com/en-us/azure/architecture/reference-architectures/enterprise-integration/ase-high-availability-deployment, where it says "App Services Environments can be deployed to multiple availability zones, only in internal or ILB mode. " Again, there's a lack of clarity, specifically around the use of the word "can". They way it's currently written could be interpreted as "an ASE can be optionally deployed across multiple availability zones", which is incorrect. It should be re-written as "App Service Environments are deployed into a single AZ, but here is a reference architecture that enables you to deploy two ASEs, each of which will be pinned to a distinct availability zone".

madsd commented 2 years ago

Hi @larryclaman you cannot deploy ASEv2 in a zone redundant manner. You can either deploy it normally (where Azure choses a zone) or you can zone pin it. This way, you can deploy two ASE instances in different zones and achieve zone resiliency. With ASEv3 you have zone redundancy built in, where the platform balances infrastructure and worker across three availability zones.

please-close