[
https://issues.apache.org/jira/browse/CLOUDSTACK-6542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remi Bergsma updated CLOUDSTACK-6542:
-------------------------------------
Description:
When you create a snapshot schedule, the ‘intervaltype’ has to be entered like
‘DAILY, HOURLY’ etc.
create snapshotpolicy volumeid=2b606f51-6b56-46b5-b85e-6a3e02babf23
schedule=23:1 intervaltype=DAILY timezone=Europe/Amsterdam maxsnaps=1
When you list the snapshot schedule, the ‘intervaltype’ is an integer,
0=HOURLY, 1=DAILY etc.
> list snapshotpolicies volumeid=2b606f51-6b56-46b5-b85e-6a3e02babf23
count = 1
snapshotpolicy:
| maxsnaps | intervaltype | schedule | volumeid |
timezone | id |
| 1 | 1 | 23:1 | 2b606f51-6b56-46b5-b85e-6a3e02babf23 |
Europe/Amsterdam | 9b736a09-4549-4638-a88d-f8ae9cc87c51 |
Could this be made more consistent, maybe allow both formats in both calls?
When you want to list a schedule, and use this data to create a new one this
‘translating’ is a bit weird.
was:
When you create a snapshot schedule, the ‘intervaltype’ has to be entered like
‘DAILY, HOURLY’ etc.
create snapshotpolicy volumeid=2b606f51-6b56-46b5-b85e-6a3e02babf23
schedule=23:1 intervaltype=DAILY timezone=Europe/Amsterdam maxsnaps=1
When you list the snapshot schedule, the ‘intervaltype’ is an integer,
0=HOURLY, 1=DAILY etc.
> list snapshotpolicies volumeid=2b606f51-6b56-46b5-b85e-6a3e02babf23
count = 1
snapshotpolicy:
+----------+--------------+----------+--------------------------------------+------------------+--------------------------------------+
| maxsnaps | intervaltype | schedule | volumeid |
timezone | id |
+----------+--------------+----------+--------------------------------------+------------------+--------------------------------------+
| 1 | 1 | 23:1 | 2b606f51-6b56-46b5-b85e-6a3e02babf23 |
Europe/Amsterdam | 9b736a09-4549-4638-a88d-f8ae9cc87c51 |
+----------+--------------+----------+--------------------------------------+------------------+--------------------------------------+
Could this be made more consistent, maybe allow both formats in both calls?
When you want to list a schedule, and use this data to create a new one this
‘translating’ is a bit weird.
> Interval type not consistent in create/list snapshot schedules
> --------------------------------------------------------------
>
> Key: CLOUDSTACK-6542
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6542
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.3.0
> Reporter: Remi Bergsma
> Priority: Minor
>
> When you create a snapshot schedule, the ‘intervaltype’ has to be entered
> like ‘DAILY, HOURLY’ etc.
> create snapshotpolicy volumeid=2b606f51-6b56-46b5-b85e-6a3e02babf23
> schedule=23:1 intervaltype=DAILY timezone=Europe/Amsterdam maxsnaps=1
> When you list the snapshot schedule, the ‘intervaltype’ is an integer,
> 0=HOURLY, 1=DAILY etc.
> > list snapshotpolicies volumeid=2b606f51-6b56-46b5-b85e-6a3e02babf23
> count = 1
> snapshotpolicy:
> | maxsnaps | intervaltype | schedule | volumeid |
> timezone | id |
> | 1 | 1 | 23:1 | 2b606f51-6b56-46b5-b85e-6a3e02babf23 |
> Europe/Amsterdam | 9b736a09-4549-4638-a88d-f8ae9cc87c51 |
>
> Could this be made more consistent, maybe allow both formats in both calls?
> When you want to list a schedule, and use this data to create a new one this
> ‘translating’ is a bit weird.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
