Hardware Reference
In-Depth Information
FIGURE 10.6: Tera[gen, sort, validate] average job runtime vs. number of
remote clients. As the number of clients increases performance continues to
scale even through the number of servers is fixed.
(and clients) need not contact other servers in order to create objects that will
ultimately reside on another server. Servers (and clients) don't need to know
about all of the servers, only the servers with which each interacts. The initial
implementation of v3 uses universal unique identifiers (UUIDs [1]) as handles
for objects. This way, whenever an object is created, its handle can be allo-
cated without concern for its ultimate location. Later, a client or server can
select one or more locations for the object and send copies to each one. The
locations are recorded in metadata just as they are in v2. Servers also have a
UUID, which is used to manage sets of known servers. Protocols are provided
for locating nearby servers based on a variety of attributes. Still other pro-
tocols manage new servers and servers leaving service. Management routines
perform scrubbing operations to maintain consistency, replication levels, and
related operations.
10.3 Deployment
Easy to deploy and manage, OrangeFS builds out-of-the-box on a wide
variety of Linux distributions and has only a few required dependencies.
