starlingx/distcloud
Code Issues Proposed changes
5e884374d2
distcloud/distributedcloud/dcorch/engine
History
Jessica Castelino b0636c1ed8 Prevent sync states from bouncing when a subcloud is managed 
When a subcloud is first set to managed, the dcorch endpoint
sync status keeps toggling between the two states - "in-sync"
and "out-of-sync", before settling on "in-sync". This is
because during the audit run, different endpoints (sysinv and
identity) are done in separate greenthreads and each
greenthread processes the resources (e.g. users, projects)
in series. Thus, an enhancement is made to reduce the
unnecessary messaging between dcorch and dcmanager, and to
avoid the bouncing sync states.

Change-Id: I98cec42eb5880d95d54182339dab6b5c951d6cfd
Story: 2007267
Task: 38996
Signed-off-by: Jessica Castelino <jessica.castelino@windriver.com>
2020-04-08 14:17:34 -04:00
..
sync_services Keystone token and resource caching 2020-03-23 21:31:04 -04:00
__init__.py Move content to subdir to support relocated packaging 2019-11-04 13:57:02 -05:00
dc_orch_lock.py Move content to subdir to support relocated packaging 2019-11-04 13:57:02 -05:00
fernet_key_manager.py Keystone token and resource caching 2020-03-23 21:31:04 -04:00
generic_sync_manager.py Fix subcloud manage/unmanage issues caused by identity sync 2020-02-18 07:23:08 -06:00
initial_sync_manager.py Remove dcorch-snmp and move alarm audit to dcmanager 2020-04-07 20:27:30 -04:00
quota_manager.py Keystone token and resource caching 2020-03-23 21:31:04 -04:00
README.rst Move content to subdir to support relocated packaging 2019-11-04 13:57:02 -05:00
scheduler.py Fix subcloud manage/unmanage issues caused by identity sync 2020-02-18 07:23:08 -06:00
service.py Remove dcorch-snmp and move alarm audit to dcmanager 2020-04-07 20:27:30 -04:00
subcloud.py Keystone token and resource caching 2020-03-23 21:31:04 -04:00
sync_thread.py Prevent sync states from bouncing when a subcloud is managed 2020-04-08 14:17:34 -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.