828cdcf2bb
This commit enhanced dcorch find_missing algorithm so that the first audit after subcloud becomes managed won't try to create resources that have matches in the subcloud (otherwise the creation will fail for DB duplication error). This is neccessary for resources that are created at deployment time and existing resources not yet tracked by dcorch. Story: 2002842 Task: 22787 Change-Id: I60f94057caf71265942f3b37b400eeba4f368fed Signed-off-by: Andy Ning <andy.ning@windriver.com> |
||
---|---|---|
.. | ||
sync_services | ||
__init__.py | ||
alarm_aggregate_manager.py | ||
dc_orch_lock.py | ||
fernet_key_manager.py | ||
generic_sync_manager.py | ||
quota_manager.py | ||
README.rst | ||
scheduler.py | ||
service.py | ||
subcloud.py | ||
sync_thread.py |
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.