Skip to content

Commit 083622d

Browse files
authored
Merge pull request #238 from nginx/internal/rsa-scaling-guidance
Add manual scaling guidance
2 parents c5e5a5c + 728f610 commit 083622d

File tree

2 files changed

+45
-112
lines changed

2 files changed

+45
-112
lines changed

content/nginxaas-google/getting-started/manual-scaling.md

Lines changed: 45 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,4 +8,48 @@ type:
88
- how-to
99
---
1010

11-
TBD
11+
F5 NGINXaaS for Google Cloud (NGINXaaS) supports manual scaling of your deployment, allowing you to adapt to application traffic demands while controlling cost.
12+
13+
An NGINXaaS deployment can be scaled out to increase the capacity or scaled in to decrease the capacity. Capacity is measured in [NGINX Capacity Units (NCU)](#nginx-capacity-unit-ncu).
14+
15+
In this document you will learn:
16+
17+
- What an NGINX Capacity Unit (NCU) is
18+
- How to manually scale your deployment
19+
- What capacity restrictions apply for your plan
20+
- How to monitor capacity usage
21+
- How to estimate the amount of capacity to provision
22+
23+
## NGINX Capacity Unit (NCU)
24+
25+
An NGINX Capacity Unit (NCU) quantifies the capacity of an NGINX instance based on the underlying compute resources. This abstraction allows you to specify the desired capacity in NCUs without having to consider the regional hardware differences.
26+
27+
## Manual scaling
28+
29+
To update the capacity of your deployment using the portal,
30+
31+
In the NGINXaaS Console,
32+
33+
1. On the left menu, select **Deployments**.
34+
2. Select the deployment you wish to edit the NCU capacity for.
35+
3. On the **Details** tab, select the **Edit** button on the right to open the Edit Deployment Metadata pane
36+
- Enter the desired value for the **NCU Capacity** under **Scale**.
37+
- Select **Update** to begin the scaling process.
38+
39+
The status of the deployment will be "Pending" while the deployment's capacity is being changed. Once the requested capacity provisioning is complete, the status will change to "Ready".
40+
41+
{{< call-out "note" >}}There's no downtime while an NGINXaaS deployment changes capacity.{{< /call-out >}}
42+
43+
## Capacity restrictions
44+
45+
The following table outlines constraints on the specified capacity based on the chosen Marketplace plan, including the minimum capacity required for a deployment to be highly available, the maximum capacity, and what value the capacity must be a multiple of. By default, an NGINXaaS for Google Cloud deployment will be created with the corresponding minimum capacity.
46+
47+
{{<bootstrap-table "table table-striped table-bordered">}}
48+
49+
| **Marketplace Plan** | **Minimum Capacity (NCUs)** | **Maximum Capacity (NCUs)** | **Multiple of** |
50+
|------------------------------|-----------------------------|-----------------------------|----------------------------|
51+
| Enterprise plan(s) | 10 | 100 | 10 |
52+
53+
{{</bootstrap-table>}}
54+
55+
{{< call-out "note" >}}If you have higher capacity needs than the maximum capacity, please [open a request](https://my.f5.com/manage/s/) and specify the Resource ID of your NGINXaaS deployment, the region, and the desired maximum capacity you wish to scale to.{{< /call-out >}}

content/nginxaas-google/quickstart/scaling.md

Lines changed: 0 additions & 111 deletions
This file was deleted.

0 commit comments

Comments
 (0)