Scale: Refurbish page layout

Author: amotl

docs/admin/clustering/index.rst

@@ -12,8 +12,7 @@ adding more nodes. This section of the documentation covers that topic.
 .. toctree::
    :maxdepth: 1
 
-   multi-node-setup
-   multi-zone-setup
-   scale/index
-   scale/kubernetes
-   logical-replication-setup
+   Multi-Node Setup <multi-node-setup>
+   Multi-Zone Setup <multi-zone-setup>
+   Scale Clusters <scale/index>
+   Logical Replication <logical-replication-setup>

docs/admin/clustering/scale/auto.md

@@ -0,0 +1,8 @@
+(scale-auto)=
+
+# Autoscale a CrateDB Cloud Cluster
+
+CrateDB’s fully managed solution CrateDB Cloud comes with a REST API,
+which enables you to automate a lot of tasks. The tutorial demonstrates
+how to use the REST API to scale your CrateDB Cloud Cluster based on a
+threshold on the number of shards in a cluster.

docs/admin/clustering/scale/demand.md

@@ -0,0 +1,10 @@
+(scale-demand)=
+
+# Scale CrateDB clusters up and down to cope with peaks in demand
+
+This tutorial demonstrates the [shard allocation filtering] functionality,
+and how it is applied in a real-world data management scenario, specifically
+about tuning your database cluster to cope with high-demand situations.
+
+
+[shard allocation filtering]: inv:crate-reference#ddl_shard_allocation

docs/admin/clustering/scale/expand.md

@@ -0,0 +1,4 @@
+(scale-expand)=
+
+# How to expand an existing CrateDB cluster
+

docs/admin/clustering/scale/index.md

@@ -12,26 +12,70 @@ By running your database cluster on multiple nodes, you will gain two benefits.
   of replica nodes.
 
 
-(scaling-expand)=
-## Expand Cluster
-
-The article about [how to add new nodes to an existing cluster] walks you
-through the process of scaling up your database cluster, and educates you
-about the corresponding details to consider.
+:::{toctree}
+:maxdepth: 1
+:hidden:
 
+Expand <expand>
+On-Demand <demand>
+Autoscale <auto>
+On Kubernetes <kubernetes>
+:::
 
-(scaling-ondemand)=
-## Scale On-Demand
 
-The article about [scaling CrateDB clusters up and down to cope with peaks in
-demand] shares knowledge about the [shard allocation filtering] feature of
-CrateDB.
+## Learn
 
-Along the lines, it demonstrates how this functionality is applied in a real-
-world data management scenario, which is about tuning your database cluster to
-cope with high-demand situations.
+:::::{grid}
 
-Prepare adding extra nodes to the database cluster.
+::::{grid-item-card}
+:link: scale-expand
+:link-type: ref
+(scaling-expand)=
+:::{rubric} Expand Cluster
+:::
+Learn how to add new nodes to an existing CrateDB database cluster
+running on your premises, in order to expand its capacity using
+horizontal scaling.
++++
+{hyper-tutorial}`scale-expand`
+::::
+
+::::{grid-item-card}
+:link: scale-demand
+:link-type: ref
+(scaling-ondemand)=
+:::{rubric} On-Demand Scaling
+:::
+Learn how to use CrateDB's [shard allocation filtering] feature in
+practice, in order to scale CrateDB clusters up and down to cope
+with peaks in high-demand situations. 
++++
+{hyper-tutorial}`scale-demand`
+::::
+
+::::{grid-item-card}
+:link: scale-auto
+:link-type: ref
+(scaling-autoscale)=
+:::{rubric} Automatic Scaling
+:::
+Learn how to automatically scale your CrateDB Cloud Cluster based on a
+threshold on the number of shards in a cluster, using the
+CrateDB Cloud REST API.
++++
+{hyper-tutorial}`scale-auto`
+::::
+:::::
+
+
+## Synopsis
+
+A rough walkthrough how resource management works in CrateDB, to manage
+high-demand / peak situations.
+
+:::{rubric} Provision Resources
+:::
+Prepare by adding extra nodes to the database cluster.
 ```sql
 /* Apply routing setting to all existing partitions and new partitions. */
 ALTER TABLE test SET ("routing.allocation.exclude.storage" = 'temporarynodes');
@@ -40,13 +84,18 @@ ALTER TABLE test SET ("routing.allocation.exclude.storage" = 'temporarynodes');
 ALTER TABLE ONLY test RESET ("routing.allocation.exclude.storage");
 ```
 
-Before the high-demand event, properly configure table routing accordingly.
+:::{rubric} Scale Up
+:::
+Right before the high-demand event, adjust the table routing,
+so the cluster will use additional resources.
 ```sql
 ALTER TABLE ONLY test SET ("routing.allocation.total_shards_per_node" = 2);
 ```
 
-To decommission extra database nodes, we need to move the data collected during
-the days of the event.
+:::{rubric} Scale Down
+:::
+To decommission excess database nodes, move the data collected during
+the days of the event away.
 ```sql
 -- Move the collected data off the extra nodes.
 ALTER TABLE test SET ("routing.allocation.exclude.storage" = 'temporarynodes');
@@ -58,5 +107,5 @@ ALTER CLUSTER DECOMMISSION 'nodename';
 
 
 [how to add new nodes to an existing cluster]: https://community.cratedb.com/t/how-to-add-new-nodes-to-an-existing-cluster/1546
-[scaling CrateDB clusters up and down to cope with peaks in demand]: https://community.cratedb.com/t/scaling-cratedb-clusters-up-and-down-to-cope-with-peaks-in-demand/1314
+[how to scale CrateDB clusters up and down to cope with peaks in demand]: https://community.cratedb.com/t/scaling-cratedb-clusters-up-and-down-to-cope-with-peaks-in-demand/1314
 [shard allocation filtering]: inv:crate-reference#ddl_shard_allocation