starlingx/distcloud
Code Issues Proposed changes
67215f30fe
distcloud/dcorch/engine
History
Andy Ning 67215f30fe Keystone DB sync - update dcorch to use dcdbsync 
This commit updates dcorch to use the newly introduced dbsync service
APIs to synchronize identity resources from central cloud to subclouds.
The following identity resources are synced:

- users (local users only)
- user passwords
- projects
- roles
- project role assignments
- token revocation events

Story: 2002842
Task: 22787

Signed-off-by: Andy Ning <andy.ning@windriver.com>
(cherry picked from commit e9096c7a23)

Depends-On: https://review.opendev.org/#/c/655921
Depends-On: https://review.opendev.org/#/c/655773
Depends-On: https://review.opendev.org/#/c/655776
Depends-On: https://review.opendev.org/#/c/655927
Change-Id: I77c2cc712a1c3dc8a228883c3fea1423e5207dea
2019-04-30 14:50:55 -04:00
..
sync_services Keystone DB sync - update dcorch to use dcdbsync 2019-04-30 14:50:55 -04:00
__init__.py Integrate Distributed Cloud with containerized services 2019-03-14 15:13:21 -04:00
alarm_aggregate_manager.py Distributed Cloud: PTP parameters synchronization. 2018-08-28 15:51:39 -04:00
dc_orch_lock.py StarlingX open source release updates 2018-08-07 11:51:21 -04:00
fernet_key_manager.py Keystone DB sync - update dcorch to use dcdbsync 2019-04-30 14:50:55 -04:00
generic_sync_manager.py Keystone DB sync - update dcorch to use dcdbsync 2019-04-30 14:50:55 -04:00
quota_manager.py FIX: "dict" issue for Python 2/3 compatible code 2019-01-15 00:33:38 +00:00
README.rst StarlingX open source release updates 2018-08-07 11:51:21 -04:00
scheduler.py StarlingX open source release updates 2018-08-07 11:51:21 -04:00
service.py Keystone DB sync - update dcorch to use dcdbsync 2019-04-30 14:50:55 -04:00
subcloud.py Keystone DB sync - update dcorch to use dcdbsync 2019-04-30 14:50:55 -04:00
sync_thread.py Keystone DB sync - update dcorch to use dcdbsync 2019-04-30 14:50:55 -04:00

README.rst

Service

Distributed Cloud Orchestration Engine Service has responsibility for:

Monitoring the subcloud status, and return the result if needed.

There is a single engine, with each subcloud having one persistent sync thread per endpoint-type. Sync audit threads will be created on demand as needed.

service.py:

run orchengine service, and establish RPC server

generic_sync_manager.py

Manages all the generic resource syncing.