Thomas sch bel theuer universit t stuttgart schoebel@informatik uni stuttgart de www athomux net
Download
1 / 17

A LEGO-like Lightweight Component Architecture for Organic Computing - PowerPoint PPT Presentation


  • 68 Views
  • Uploaded on

Thomas Schöbel-Theuer, Universität Stuttgart schoebel@informatik.uni-stuttgart.de www.athomux.net. A LEGO-like Lightweight Component Architecture for Organic Computing. Outline. The LEGO principle: (almost) arbitrary combinability

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' A LEGO-like Lightweight Component Architecture for Organic Computing' - gavin-gamble


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Thomas sch bel theuer universit t stuttgart schoebel@informatik uni stuttgart de www athomux net

Thomas Schöbel-Theuer, Universität Stuttgart

schoebel@informatik.uni-stuttgart.de

www.athomux.net

A LEGO-like Lightweight Component Architecture for Organic Computing


Outline
Outline

  • The LEGO principle: (almost) arbitrary combinability

  • How to control that?=> Strategy Representations=> Organic Properties

  • Explicit Reasoning / Transformations=> Instance Orientation

  • Prototype: Athomux


Lego principle
LEGO Principle

  • Examples: LEGO, Fischertechnik, FESTO, Bosch-System Fördertechnik, ...

  • Key property: low number of interfaces=> Obvious Advantages!

  • Next logical step after Component Software


Execution layer of the Athomux filesystem

bricks ≅ transformers on instances of a memory abstraction

bricks may be stateless

Example


Insert bricks for replication transactions recovery mobility at any point of the execution layer

Insert bricks for replication, transactions / recovery, mobility, ... at any point of the execution layer

Advantages of Brick Systems


Control by strategy level
Control by Strategy Level mobility, ... at

  • Allows formal reasoning on system structure:=> organic properties (self-management /organization / healing, adaptation, ...)

  • Modularization at strategy level (LEGO...)

  • Multiple Views / Transformations in parallel:==> Instance Orientation


Full replication maximum redundancy partitioning local control

Full replication => maximum redundancy mobility, ... at

Partitioning => local control

Example: Virtual Computeron a Network


Implementation athomux www athomux net
Implementation: Athomux mobility, ... at www.athomux.net

  • Infrastructure / Preprocessor / brick description language (superset of C)

  • Prototype of a filesystem with strategy bricks for automatic path instantiation

  • Prototype of rudimentary Posix emulationopen(), close(), read(), write(), fork(), exec(), ...

  • Simple shell runs binaries statically linked with uClibc


Strategy representation
Strategy Representation mobility, ... at

  • brick=adapt_meta {

  • attr transfer_size=4096

  • input==in {

  • connect in=3000:out

  • }

  • output==out {

  • connect out=5000:in

  • }

  • }


Future work
Future Work mobility, ... at

  • Network transparency: automatically insert remote / mirror bricks at the execution layer, but hide them at a virtual system view:=> network location transparency=> automatic migration=> crash recovery, load balancing, ...

  • Transaction bricks => insertable at any position => make any part of the system recoverable

  • More organic properties ...


Conclusions
Conclusions mobility, ... at

  • LEGO principle: next step after component software

  • Explicit reasoning on system structure=> achieve organic properties

  • Instance orientation: multiple views in parallel

  • Athomux prototype: www.athomux.net

    • Preprocessor: brick description language,superset of C

    • Runtime environment for bricks, good performance

    • Filesystem and rudimentary Posix emulation=> Platform for experiments with organic computing


Example brick code

operation $get,$put,$transfer,$wait mobility, ... at

{

addr_t copy_addr = @log_addr;

@log_addr -= @>offset;

if (@log_addr >= 0 && @log_addr+@log_len <= @>len) {

@=call :<in$op @args;

}

@log_addr = copy_addr;

}

operation $output_init

{

// @>offset = ... ; @>len = ...;

@success = TRUE;

}

Example Brick Code

  • brick #selector

  • purpose Select a part of a nest

  • desc

  • Incomplete demo implementation

  • enddesc

  • input :<in

  • output :>out

  • data {

  • addr_t offset;

  • len_t len;

  • }


Remote may be inserted at any point

remote mobility, ... at may be inserted at any point

OS Example


Emulation of aop by instance orientation
Emulation of AOP mobility, ... at by Instance Orientation


Is equivalent to

is equivalent to mobility, ... at

Automated (Formal) Reasoning


Spatial locality better performance

Spatial locality => better performance mobility, ... at

Performance in Distributed Systems: Optional Locking



ad