Add periodic task for magnum conductor
Add a periodic task framework to update state periodically as it changes in upstream systems. For example, we need to sync bay status with heat when retry timeouts are reached before stack create finishes. Another use case is if the conductor crashes during bay create/update, then the bay status will be incorrect. This task will correct it.
Blueprint information
Related branches
Sprints
Whiteboard
hongbin points out [1], magnum will use heat notifications to check the status when creating stack.
eliqiao thinks it is useful even we have heat notify magnum, notifications will be only triggered one time, so if magnum misses it. then the status will be get lost, so periodic task will be useful in this case.
[1] http://
Gerrit topic: https:/
Addressed by: https:/
WIP: Add periodict task support for to rpc service
Addressed by: https:/
WIP: add periodic task to bay conductor
Gerrit topic: https:/
Addressed by: https:/
Add get_admin_context to Magnum context
Addressed by: https:/
Support use admin creds in KeystoneClientV3
Addressed by: https:/
Allow admin context to query all bay
Addressed by: https:/
Add periodic task to sync bay status
Addressed by: https:/
Devstack: Add admin creds in magnum.conf
Addressed by: https:/
Swith auth_uri to use v2.0
Addressed by: https:/
Update heat policy.json
Work Items
Dependency tree
* Blueprints in grey have been implemented.
