Difference between revisions of "Zaqar/docs/drivers"
< Zaqar
(outline) |
(→Introduction to Marconi Drivers) |
||
| 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. | + | 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. |
| − | |||
| − | |||
| − | |||
<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.> | ||
Revision as of 18:15, 3 September 2013
Contents
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. <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
TBD
Transport
TBD
