Jump to: navigation, search

Difference between revisions of "Zaqar/docs/drivers"

(Introduction to Marconi Drivers)
m (Malini moved page Marconi/docs/drivers to Zaqar/docs/drivers: Project Rename)
 
(2 intermediate revisions by one other user not shown)
Line 1: Line 1:
 
= Introduction to Marconi Drivers =
 
= Introduction to Marconi Drivers =
  
Marconi has a modular architecture, and utilizes dynamically-loaded transport (frontend) and storage (backend) drivers via stevedore. All drivers have a defined base API that different implementations should inherit from and fully support. Also, both layers - frontend and backend - are tested and certified by a well structured and designed suite which verifies that the implementation details, resources life-cycles and live behavior.
+
Marconi has a modular architecture, and utilizes dynamically-loaded transport (frontend) and storage (backend) drivers via stevedore. All drivers have a defined base API that different implementations must inherit from and fully support.  
 +
 
 
<talk about requirments - functional ones are vetted by tests, also talk about non-functional reqs such as performance, duability, availability, operations, etc.>
 
<talk about requirments - functional ones are vetted by tests, also talk about non-functional reqs such as performance, duability, availability, operations, etc.>
  
Line 8: Line 9:
 
=== Storage ===
 
=== Storage ===
  
TBD
+
Storage drivers, also known as backends, are responsible for storing data within Marconi. These drivers are not accessible from outside but through Marconi's transport layer.
 +
 
 +
A storage driver is composed by 1 actual driver and 3 controllers.
  
 
=== Transport ===
 
=== Transport ===
  
 
TBD
 
TBD
 +
 +
 +
== Drivers Tests ==
 +
 +
Both layers - frontend and backend - are tested and certified by a well structured and designed suite which verifies that the implementation details, resources life-cycles and live behavior.
 +
 +
<add more contents about tests>

Latest revision as of 18:42, 7 August 2014

Introduction to Marconi Drivers

Marconi has a modular architecture, and utilizes dynamically-loaded transport (frontend) and storage (backend) drivers via stevedore. All drivers have a defined base API that different implementations must inherit from and fully support.

<talk about requirments - functional ones are vetted by tests, also talk about non-functional reqs such as performance, duability, availability, operations, etc.>

Compatible 3rd-Party Drivers

Storage

Storage drivers, also known as backends, are responsible for storing data within Marconi. These drivers are not accessible from outside but through Marconi's transport layer.

A storage driver is composed by 1 actual driver and 3 controllers.

Transport

TBD


Drivers Tests

Both layers - frontend and backend - are tested and certified by a well structured and designed suite which verifies that the implementation details, resources life-cycles and live behavior.

<add more contents about tests>