cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From koushik-das <>
Subject [GitHub] cloudstack pull request: CLOUDSTACK-9022: keep Destroyed volumes f...
Date Wed, 04 Nov 2015 05:30:12 GMT
Github user koushik-das commented on a diff in the pull request:
    --- Diff: setup/db/db/schema-452to460.sql ---
    @@ -420,3 +420,6 @@ INSERT IGNORE INTO `cloud`.`guest_os_hypervisor` (uuid,hypervisor_type,
     INSERT IGNORE INTO `cloud`.`guest_os_hypervisor` (uuid,hypervisor_type, hypervisor_version,
guest_os_name, guest_os_id, created, is_user_defined) VALUES (UUID(),'KVM', 'default', 'CentOS
7', 246, utc_timestamp(), 0);
     UPDATE  `cloud`.`hypervisor_capabilities` SET  `max_data_volumes_limit` =  '32' WHERE
 `hypervisor_capabilities`.`hypervisor_type` =  'KVM';
    +INSERT IGNORE INTO `cloud`.`configuration` (`category`, `instance`, `component`, `name`,
`value`, `default_value`, `description`) VALUES ('Advanced', 'DEFAULT', 'StorageManager',
'storage.cleanup.delay', '86400', '86400', 'Determines how long (in seconds) to wait before
actually expunging destroyed volumes. The default value = the default value of storage.cleanup.interval.');
    --- End diff --
    This is not required when Configurable interface is used

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message