A coherent set of network services working together to run OpenIO’s solutions.


Processes running in the namespace. They can be stateless or stateful, or registered in the conscience for further load-balancing, then linked to references in the directory.


Usually represents a customer (the second ‘B’ in B2B2C). There is no limit to the number of accounts in a namespace. Accounts keep track of namespace usage of each customer (e.g. the list of containers and the number of bytes occupied by all objects of a customer).


Some kind of service container. Usually represents a final user (the ‘C’ in B2B2C). Several services may be linked to a reference (e.g. an object storage service and a database service). More details in Service Directory section.


Object buckets. They keep track of object locations. A container belongs to one (and only one) account. More details in Object Storage section.


The smallest data units visible by customers. An object belongs to one (and only one) container.


Parts of objects, not visible by customers. They are limited in size. They can be replicated or be accompanied by parity chunks.


A (set of) service(s) responsible for collecting, aggregating and distributing metrics about all other services of a namespace, in order to have a good load balancing and data placement. More details in Conscience section.


Groups of services sharing common characteristics like storage hardware type or physical location. More details in Slots section.


Rules to generate coherent sets of services. More details in Pools section.


An aggregation of metrics reflecting the health of each service, usually between 0 and 100. Scores are computed by Conscience, and used by load-balancers. See Load Balancing.

See also