Tags:
create new tag
, view all tags

MX-TCE Code Structure

The MX-TCE runner process is written in C++. The code is compiled and installed with the GNU autotool.

Source Layout

   mx-tce/...
            do_build.sh
            do_install.sh
            README
            TODO
            LICENSE
            doc/
            src/...
                 common/
                 main/
                 api/
                 tedb/
                 rm/
                 policy/
                 test/

Common Classes

The generic classes under src/common/ include:
  • Thread
  • Event
  • Message
  • Logger
  • Exception

Threads and Modules

The original version of MX-TCE modular design:

mx-tce-modular.jpg

The new thread composition is below:

  • MX-TCE API Server will remain a thread that runs an event queue w/ socket selector to handle client requests
  • API Thread will be combined with Computing Thread. Each Computing Thread will perform certain API function to get and send/post its own API data to API server
  • MX-TCE core will be a thread to managing main event loop and inter-thread message queue.
  • MX-TCE core thread will be responsible for event-driven workflow.
  • TEDB will be a thread. It may create TEDB API threads for topology I/O. The OSCARS-PCE fed topology data will be handled by TEDB main thread directly.
  • Reservation Manager and Policy Manager will also be separate threads.
Topic revision: r2 - 2010-11-29 - XiYang
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback