cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9861) Expire VM snapshots after configured duration
Date Thu, 06 Apr 2017 07:55:41 GMT


ASF GitHub Bot commented on CLOUDSTACK-9861:

Github user rhtyd commented on a diff in the pull request:
    --- Diff: setup/db/db/schema-4920to41000.sql ---
    @@ -232,3 +232,5 @@ WHERE (o.cpu is null AND o.speed IS NULL AND o.ram_size IS NULL) AND
     -- CLOUDSTACK-9827: Storage tags stored in multiple places
     DROP VIEW IF EXISTS `cloud`.`storage_tag_view`;
    +INSERT IGNORE INTO `cloud`.`configuration` VALUES ('Advanced', 'DEFAULT', 'VMSanpshotManager',
'vmsnapshot.expire.interval', '-1', 'VM Snapshot expire interval in hours','-1', NULL, 'Account',
    --- End diff --
    @abhinandanprateek Since you've used Configkey, no need to use this INSERT query. Also
typo in the 'VMSanpshotManager'.

> Expire VM snapshots after configured duration
> ---------------------------------------------
>                 Key: CLOUDSTACK-9861
>                 URL:
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Abhinandan Prateek
> Currently, users can keep VM snapshots for an indefinite time period.  Long-lived snapshots
can cause stability issues on the hypervisor.
> Requirement: Add a timeout for VM Snapshots, whereby snapshots get automatically deleted
after a given time period. This would be available at account level, with a default value
determined by a global setting. 

This message was sent by Atlassian JIRA

View raw message