User Tools

Site Tools


system_requirements

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
system_requirements [2013/04/06 00:26]
bhyman
system_requirements [2013/04/06 00:27] (current)
bhyman [Typical Brick for an Evergreen Cluster]
Line 45: Line 45:
 Evergreen is typically deployed using commodity hardware in the following formation: Evergreen is typically deployed using commodity hardware in the following formation:
  
-Brick:hosts PAC services(both staff and public).Each brick is ideally comprised of two servers, a front running apache, and a back running drone services (auth, circ, cat, search). At smaller scales, the front and back can be on the same server.\\+Brick: hosts PAC services (both staff and public). Each brick is ideally comprised of two servers, a front running apache, and a back running drone services (auth, circ, cat, search). At smaller scales, the front and back can be on the same server.\\
  
 Firewall & Load-balancer:​ required in multiple brick environments tosplit HTTP/HTTPS traffic between bricks.\\ Firewall & Load-balancer:​ required in multiple brick environments tosplit HTTP/HTTPS traffic between bricks.\\
Line 51: Line 51:
 Reports: highly variable load\\ Reports: highly variable load\\
  
-Backend(holds,​fines,​A/​T,​etc.):​runs the drone services that would generally be considered background/​scheduled work. Examples would be processing holds as books are checked in, handling fines, email notifications.\\+Backend (holds,​fines,​A/​T,​etc.):​ runs the drone services that would generally be considered background/​scheduled work. Examples would be processing holds as books are checked in, handling fines, email notifications.\\
  
-SIP2:​Partially depends on the back end or a drone,but is a good candidate to separate out. SIP2 generally requires ~60-180MB per connection (lower while idle). Every self-check station will require it's own connection, as will many other things like PC reservations.\\+SIP2: Partially depends on the back end or a drone,but is a good candidate to separate out. SIP2 generally requires ~60-180MB per connection (lower while idle). Every self-check station will require it's own connection, as will many other things like PC reservations.\\
  
-Logging(via syslog protocol):​For security & problem detection/​analysis,​all of the other roles report to a central logging location.\\+Logging(via syslog protocol): For security & problem detection/​analysis,​all of the other roles report to a central logging location.\\
  
 DB: This is the PostgreSQL database. Heavy random read/write IO performance required.\\ DB: This is the PostgreSQL database. Heavy random read/write IO performance required.\\
system_requirements.txt · Last modified: 2013/04/06 00:27 by bhyman

© 2008-2017 GPLS and others. Evergreen is open source software, freely licensed under GNU GPLv2 or later.
The Evergreen Project is a member of Software Freedom Conservancy.