Go to file
majiajun 35a3b06867 mission manager bugfix
Signed-off-by: majiajun <864428661@qq.com>

Change-Id: I412b0ee2946984aa3b3e2a7251f7674e8dee5e90
2022-02-28 23:01:08 -08:00
etc modify: cfg adapt parallel start 2022-02-09 17:40:33 +08:00
figures update readme 2022-02-25 09:48:55 +08:00
interfaces/innerkits/uri delete ipc_core dependent 2022-02-24 21:39:42 +08:00
sa_profile add dms 2021-06-17 13:10:47 +08:00
services/dtbschedmgr mission manager bugfix 2022-02-28 23:01:08 -08:00
utils/native fix code style warnings 2021-09-24 16:28:15 +08:00
.gitattributes update OpenHarmony 2.0 Canary 2021-06-02 02:21:10 +08:00
bundle.json Fix atomic ability bundle.json change 2022-02-14 14:00:43 +00:00
LICENSE update OpenHarmony 2.0 Canary 2021-06-02 02:21:10 +08:00
OAT.xml sync code to master 2021-12-21 23:26:50 -08:00
README_zh.md update readme 2022-02-25 09:48:55 +08:00
README.md update readme 2022-02-25 09:48:55 +08:00

Distributed Scheduler

Introduction

Distributed Scheduler is used for cross-device component management. It allows the local device to access or control remote components, and enables app collaboration in distributed scenarios. Its main functions are as follows:

  • Remote ability startup: Starts an ability on a remote device.
  • Remote ability migration: Migrates an ability to a remote device.
  • Remote ability binding: Binds an ability on a remote device.

System Architecture

Figure 1 Distributed Scheduler architecture

Directory Structure

/foundation/distributedschedule
├── dmsfwk                      # DMS framework (DMS is short for Distributed Manager Service, also called the Distributed Scheduler Service)
├── dms_fwk_lite                # Lightweight DMS framework

Repositories Involved

Distributed Scheduler

distributedschedule_dms_fwk

distributedschedule_dms_fwk_lite