| 2016-07-26 07:41:45 |
zengchen |
bug |
|
|
added bug |
| 2016-07-26 07:44:26 |
zengchen |
smaug: assignee |
|
zengchen (chenzeng2) |
|
| 2016-08-02 08:39:05 |
OpenStack Infra |
smaug: status |
New |
In Progress |
|
| 2016-08-16 06:29:42 |
zengchen |
summary |
Add pause and resume interface for scheduled operations |
Add suspend and resume interface for scheduled operations |
|
| 2016-08-16 06:35:18 |
zengchen |
description |
There are some use cases that user want to pause the scheduled operation (not schedule it from now), and then some time later he will resume it again (schedule it again). So in order to support this cases, we can add two APIs, one is pause and another is resume.
Based on the designs of Operation Engine, we can implement them by following steps separately.
1. pause
unregister the scheduled operation which is registered to some trigger;
change the state of scheduled operation to 'paused' in the DB
2. resume
register the scheduled operation to the trigger
change the state of scheduled operation to 'triggered' in the DB |
There are some use cases that user want to suspend the scheduled operation (not schedule it from now), and then some time later he will resume it again (schedule it again). So in order to support this cases, we can add 'update' api to scheduled operation..
Based on the designs of Operation Engine, we can implement them by following steps separately.
add a new filed named 'enable' to db table 'scheduled_operations'
1. suspend
unregister the scheduled operation which is registered to some trigger;
set the 'enable' to false
2. resume
register the scheduled operation to the trigger
set the 'enable' to True
When the Operation Engine service restarts, the operations which 'enable' is true can be resumed. |
|
| 2016-08-16 06:36:29 |
zengchen |
description |
There are some use cases that user want to suspend the scheduled operation (not schedule it from now), and then some time later he will resume it again (schedule it again). So in order to support this cases, we can add 'update' api to scheduled operation..
Based on the designs of Operation Engine, we can implement them by following steps separately.
add a new filed named 'enable' to db table 'scheduled_operations'
1. suspend
unregister the scheduled operation which is registered to some trigger;
set the 'enable' to false
2. resume
register the scheduled operation to the trigger
set the 'enable' to True
When the Operation Engine service restarts, the operations which 'enable' is true can be resumed. |
There are some use cases that user want to suspend the scheduled operation (not schedule it from now), and then some time later he will resume it again (schedule it again). So in order to support this cases, we can add 'update' api to scheduled operation..
Based on the designs of Operation Engine, we can implement them by following steps separately.
add a new filed named 'enable' to db table 'scheduled_operations'
1. suspend
unregister the scheduled operation which is registered to some trigger;
set the 'enable' to false
2. resume
register the scheduled operation to the trigger
set the 'enable' to True
When the Operation Engine service restarts, the operations whose 'enable' is true can be resumed. |
|
| 2016-09-13 14:05:33 |
OpenStack Infra |
karbor: status |
In Progress |
Fix Released |
|
