Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

DSDP/TML/TmLusingTM

< DSDP‎ | TML
Revision as of 10:06, 23 July 2007 by Unnamed Poltroon (Talk) (TmL Definitions)

TmL Architecture proposed over DSDP-TM platform

  • This page has the purpose of give an overview about TmL Architecture and describes how we

are using and understanding the TM platform.

  • We can not create a hard dependency between both project because TM has not a cleaned API yet. We hope

in future has a better convergency between these projects.

TmL Definitions

  • Emulator Definition - each plugin type should be a new definition plugin. This plugin contains all classes need to create a new instance of this emulator, how the emulator read properties files and how manager instances of this emulator. The binary for the emulator is part of this plugin.
    • For instance: one qemu running linux arm is a single plugin. If I need another qemu running a redhat linux I need to create another plugin with the binaries and implements some classes to provide the TmL connections for this emulator.
  • Emulator Instance - each plugin definition could has different connections that we call instances. TmL creates projects into workbench to each instance and put into this project a properties file that is used to configure each instance.
  • VNC Viewer - the emulator in the first time will be displayed using RFB protocol (VNC). We implement a new view to support

this service.

  • Control Manager - There are a view to control the emulator and it allow the user to start and stop instances of the emulator.
  • Instance View - All instances are displayed in this view.

Adapting TmL Definitions for use TM

Screenshot of prototype using TM

Tml001.jpg

Back to the top