Set vCPU and Networking Quotas ​

Azure accounts are limited by various quotas. Quotas are the assigned number of resources for your Azure subscription and are designed to protect customers from mistaken consumption and inaccurate resourced deployments. They also serve a purpose for Azure to reduce the risk of unexpected demands and inappropriate consumption. For more information, please refer to Quotas Overview.

Azure accounts are limited by various quotas. The account you use for Yellowbrick installation may need changes to its vCPU and Azure Blob Storage (ABS) quotas.

vCPU Quota ​

vCPU quotas allocate sufficient CPUs for several components of a Yellowbrick deployment:

• Compute nodes, as defined when instances are created (and shared among virtual compute clusters)
• Compiler
• Bulk load services
• Shared services

Setting Account Quotas ​

For a successful installation and performance testing, the correct quotas must be requested beforehand. The given quota defines which Azure services will be shared across all the resources, actions, and items in your Azure account and will need to be large enough to ensure that Yellowbrick scalability is tested successfully. For more information see Azure Subscription and Service Limits, Quotas, and Constraints. Yellowbrick recommends requesting the appropriate vCPU quota:

For most accounts running and managing a Yellowbrick installation, the quota will need to be increased. Specifically, the quota must allow a corresponding number of virtual machines per your anticipated configuration of Yellowbrick instances in your VPC, plus a given number of CPUs needed by other Yellowbrick services. For more information, see Quota Requests.

Two hardware instance types are currently available for V1 compute nodes:

• Small: small-v1 (standard_L16s_v3)
• Large: large-v1 (standard_L80s_v3)

Note that other hardware instance types are used for other necessary Yellowbrick components and services.

Example 1: Small Installation ​

For a small installation example, the first two rows of shared services are immutable and cannot be scaled; therefore, the numbers shown in the table are to be provided by Yellowbrick Cloud Operations. All subsequent rows can be changed and scaled to your requirements. The next three rows are Yellowbrick instances; this example shows 1 instance, which requires 112 vCPUs.

If you anticipate creating instances that allocate a total of 4 small compute nodes then your vCPU quota would be 64. In total with Shared services and the Yellowbrick Instances, your total vCPU quota would be 216.

Example 2: Large Installation ​

For a large installation, the first two rows of shared services remain immutable and cannot be scaled. All rows after shared services can be changed and scaled to your requirements. The next three rows are for Yellowbrick instances. This example has 1 instance, which requires 240 vCPUs.

If you anticipate creating instances that allocate a total of 10 large compute nodes, your vCPU quota would be 800, and if you anticipate creating instances that allocate a total of 20 small compute nodes, your vCPU quota would be an additional 320. In addition to the shared services and Yellowbrick instances, your total vCPU quota will be roughly 1400, as shown in the following table:

Parent topic:Preparing for a New Installation