Increase TimescaleDB PVC Size
Use the steps detailed in this topic to manually increase the size for TimescaleDB persistent volume claim (PVC).
The minimum recommended system requirements to deploy a Paragon Automation cluster is described in Paragon Automation System Requirements. If you want to scale up your cluster you can increase the hardware resources that are required on each node VM when you are creating the VMs for the first time as per your requirement. If you have already deployed your cluster, use the information detailed in this topic to increase storage size, specifically Ceph and consequently TimescaleDB PVC.
Ceph storage is used for both object storage and the PVC for the pods. ~50% of Ceph storage is allocated for TimescaleDB PVC.
To increase the size of the PVC, perform the following steps:
Increase Ceph Storage
Increase the total Ceph storage size.
Update Timescale DB PVC Quota
If you increase the total size of Ceph storage, you must update the allocation quota between object storage and PVC. Use Paragon Shell to increase the allocation quota. For example:
root@vm1> request paragon deploy cluster input "-t rook-quota" Process running with PID: 1830232 To track progress, run 'monitor start /epic/config/log'
Increase Timescale DB PVC
You can increase the PVC size for TimescaleDB
by
using Paragon Shell. When you are installing Paragon Automation afresh, override
the default PVC size and add the set paragon cluster custom-config
keyValue paa-timescaledb-storage-size string
size
configuration before deploying the Paragon
Automation cluster.
Log in to the installer node VM.
Configure the new PVC size in configure mode. For example:
root@vm1> configure Entering configuration mode [edit] root@vm1# set paragon cluster custom-config keyValue paa-timescaledb-storage-size string 40Gi [edit] root@vm1# commit warning: *** operating on 10.1.2.8 *** warning: *** operation on 10.1.2.8 succeeds *** warning: *** operating on 10.1.2.7 *** warning: *** operation on 10.1.2.7 succeeds *** warning: *** operating on 10.1.2.6 *** warning: *** operation on 10.1.2.6 succeeds *** commit complete [edit] root@vm1# exit Exiting configuration mode root@vm1> request paragon config Paragon inventory file saved at /epic/config/inventory Paragon config file saved at /epic/config/config.yml
Deploy the Paragon Automation cluster as usual.