Capacity planning test environment

 

Applies To: Windows Azure Pack

To develop the capacity planning recommendations, the tests were run on a Windows Azure Packdistributed deployment that was scaled out by using virtual machines.

Hardware specifications

Component	RAM	Processors
Windows Azure Pack	4 GB	2-core virtual machines
Service Provider Foundation	16 GB	16-core virtual machines
System Center Virtual Machine Manager	4 GB	2-core virtual machines
Windows Azure Pack: Websites	4 GB	2-core virtual machines
Service Bus	4 GB	2-core virtual machines
SQL Server resource provider	4 GB	2-core virtual machines

Basic architecture

Tier	Components	High availability	Notes
Admin tier	AD FS*, Admin Site, Admin API, Tenant API, Service Provider Foundation, System Center Virtual Machine Manager, Usage	Two nodes, each behind Microsoft Network Load Balancers.	These components have administrator capability and are not exposed to the Internet. All virtual machines in this tier were registered to the management Active Directory.
Tenant tier	AD FS Proxy*, Tenant Site, Tenant Authentication Site, Tenant Public API	Two nodes, each behind hardware load balancers.	These components must be exposed to the Internet and have tenant-facing functionality.
Services tier	Windows Azure Pack: Websites, Service Bus, SQL Server resource provider	Two nodes, each behind Microsoft Network Load Balancers.	Platform-as-a-service (PaaS) services.

*Active Directory Federation Services (AD FS) was set up as a 2-node farm and was used to provide identities to the stack. A Web Application proxy was set up in the Tenant tier to proxy the AD FS functionality.

All tiers included appropriate firewalls and network boundaries.