Skip to content

Commit 96beb7a

Browse files
authored
Add Resource Limits to Backups and Object Storage (apache#461)
* Added new resource limits to backup and object storage section * Add information about backup resource limits using physical size * Added new resource limits to the project page
1 parent 717903c commit 96beb7a

File tree

5 files changed

+57
-13
lines changed

5 files changed

+57
-13
lines changed
Loading

source/_static/images/add-bucket.png

3.61 KB
Loading

source/adminguide/backup_and_recovery.rst

Lines changed: 17 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -144,12 +144,12 @@ icon.
144144

145145
|B&R-createBackup.png|
146146

147-
To setup a recurring backup schedule, navigate to the Instance and click on the 'Backup Schedule'
147+
To setup a recurring backup schedule, navigate to the Instance and click on the 'Configure Backup Schedule'
148148
icon.
149149

150150
|B&R-BackupSchedule.png|
151151

152-
Then set the time and frequency of the backups, click 'Configure' and then 'Close'
152+
Then set the Interval type, timezone, time of taking the backup and maximum numbers of backups to retain.
153153

154154
|B&R-BackupScheduleEntry.png|
155155

@@ -178,6 +178,21 @@ Supported APIs:
178178
- **restoreVolumeFromBackupAndAttachToVM**: restore and attach a backed-up volume (of an Instance backup) to a specified Instance.
179179

180180

181+
Configuring resource limits on Backups
182+
--------------------------------------
183+
Administrators can enforce limits on the maximum number of backups that can be taken and
184+
the total backup storage size that can be used at an account, domain and project level.
185+
Administrators can do this by going to the configure limits tab in accounts, domains and projects
186+
similar to when enforcing resource limits on volumes, primary storage usage etc.
187+
188+
Unlike other resources like volumes, backup limits take into account the physical used size
189+
and not the allocated size of the backup. This is because the backup once taken can never
190+
grow into the allocated size. At the time of backup creation, Cloudstack doesn't know the
191+
size of the backup that will be taken, so it uses the physical size of the volumes to be
192+
backed up from Volume Stats to calculate the backup size for checking resource limits.
193+
If Volume Stats are not present, then the virtual size of the volumes is used to calculate
194+
the backup size, although the actual backup size may be less than the size use to do resource limit check.
195+
181196
.. |B&R-assignOffering.png| image:: /_static/images/B&R-assignOffering.png
182197
:alt: Assigning an SLA/Policy to an Instance.
183198
:width: 400 px

source/adminguide/projects.rst

Lines changed: 29 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -205,17 +205,35 @@ Setting the Global Project Resource Limits
205205

206206
.. cssclass:: table-striped table-bordered table-hover
207207

208-
+--------------------------+------------------------------------------------------------------------------------------------------------------------------+
209-
| max.project.public.ips | Maximum number of public IP addresses that can be owned by any project in the cloud. See About Public IP Addresses. |
210-
+--------------------------+------------------------------------------------------------------------------------------------------------------------------+
211-
| max.project.snapshots | Maximum number of Snapshots that can be owned by any project in the cloud. See Working with Snapshots. |
212-
+--------------------------+------------------------------------------------------------------------------------------------------------------------------+
213-
| max.project.templates | Maximum number of Templates that can be owned by any project in the cloud. See Working with Templates. |
214-
+--------------------------+------------------------------------------------------------------------------------------------------------------------------+
215-
| max.project.uservms | Maximum number of guest Instances that can be owned by any project in the cloud. See Working With Instances. |
216-
+--------------------------+------------------------------------------------------------------------------------------------------------------------------+
217-
| max.project.volumes | Maximum number of data volumes that can be owned by any project in the cloud. See Working with Volumes. |
218-
+--------------------------+------------------------------------------------------------------------------------------------------------------------------+
208+
+-----------------------------+-----------------------------------------------------------------------------------------------------------------------------+
209+
| max.project.public.ips | Default maximum number of public IP addresses that can be owned by any project in the cloud. See About Public IP Addresses. |
210+
+-----------------------------+-----------------------------------------------------------------------------------------------------------------------------+
211+
| max.project.snapshots | Default maximum number of Snapshots that can be owned by any project in the cloud. See Working with Snapshots. |
212+
+-----------------------------+-----------------------------------------------------------------------------------------------------------------------------+
213+
| max.project.templates | Default maximum number of Templates that can be owned by any project in the cloud. See Working with Templates. |
214+
+-----------------------------+-----------------------------------------------------------------------------------------------------------------------------+
215+
| max.project.uservms | Default maximum number of guest Instances that can be owned by any project in the cloud. See Working With Instances. |
216+
+-----------------------------+-----------------------------------------------------------------------------------------------------------------------------+
217+
| max.project.volumes | Default maximum number of data volumes that can be owned by any project in the cloud. See Working with Volumes. |
218+
+-----------------------------+-----------------------------------------------------------------------------------------------------------------------------+
219+
| max.project.networks | Default maximum number of networks that can be owned by any project in the cloud. |
220+
+-----------------------------+-----------------------------------------------------------------------------------------------------------------------------+
221+
| max.project.vpcs | Default maximum number of vpcs that can be owned by any project in the cloud. |
222+
+-----------------------------+-----------------------------------------------------------------------------------------------------------------------------+
223+
| max.project.cpus | Default maximum number of cpu cores that can be owned by any project in the cloud. |
224+
+-----------------------------+-----------------------------------------------------------------------------------------------------------------------------+
225+
| max.project.memory | Default maximum memory (in MB) that can be used by any project in the cloud. |
226+
+-----------------------------+-----------------------------------------------------------------------------------------------------------------------------+
227+
| max.project.primary.storage | Default maximum primary storage space (in GiB) that can be used by any project in the cloud. |
228+
+-----------------------------+-----------------------------------------------------------------------------------------------------------------------------+
229+
| max.project.backups | Default maximum number of backups that can be owned by any project in the cloud. |
230+
+-----------------------------+-----------------------------------------------------------------------------------------------------------------------------+
231+
| max.project.backup.storage | Default maximum backup storage (in GiB) that can be used by any project in the cloud. |
232+
+-----------------------------+-----------------------------------------------------------------------------------------------------------------------------+
233+
| max.project.buckets | Default maximum number of buckets that can be owned by any project in the cloud. |
234+
+-----------------------------+-----------------------------------------------------------------------------------------------------------------------------+
235+
| max.project.object storage | Default maximum Object storage (in GiB) that can be used by any project in the cloud. |
236+
+-----------------------------+-----------------------------------------------------------------------------------------------------------------------------+
219237

220238

221239
#. Restart the Management Server.

source/adminguide/storage.rst

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1505,6 +1505,8 @@ To create a new bucket, click create Bucket, provide the following details, and
15051505
15061506
#. Object Store: Select the object store where you want the Bucket to reside
15071507
1508+
#. Quota in GiB: Enforce a quota on the bucket. This is a mandatory field since 4.21 as it is used to enforce resource limit on object store usage.
1509+
15081510
Based on the selected Object Store, you can specify additional details like quota, encryption, policy.
15091511
15101512
|Createbucket.png|
@@ -1545,6 +1547,15 @@ Deleting objects from a bucket
15451547
15461548
2. Click on the |delete-button.png| button to delete the selected files from the bucket.
15471549
1550+
1551+
Configuring resource limits on buckets and object storage usage
1552+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1553+
Administrators can enforce limits on the maximum number of buckets they can be created and
1554+
the total object storage space that can be allocated at an account, domain and project level.
1555+
Allocated storage is the sum of quota used by all of the buckets.
1556+
Administrators can do this by going to the configure limits tab in accounts, domains and projects
1557+
similar to when enforcing resource limits on volumes, primary storage usage etc.
1558+
15481559
Shared FileSystems
15491560
------------------
15501561

0 commit comments

Comments
 (0)