internal:oice_it_infrastructure
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
internal:oice_it_infrastructure [04.02.2016 - 16:16] – tnowak | internal:oice_it_infrastructure [25.02.2016 - 17:01] (current) – ↷ Links adapted because of a move operation tnowak | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== OICE IT infrastructure ====== | ====== OICE IT infrastructure ====== | ||
- | |||
- | ===== General description ===== | ||
The OICE aims to supply an effective working environment for all its users. A typical workflow is as follows: | The OICE aims to supply an effective working environment for all its users. A typical workflow is as follows: | ||
Line 17: | Line 15: | ||
- In periodic intervals, currently every night, all data saved via the OMERO framework is backed up to our backup-server (hopefully at the RRZE), so that it can be restored in case of an accidental erase by the user or a massive hard disk failure. | - In periodic intervals, currently every night, all data saved via the OMERO framework is backed up to our backup-server (hopefully at the RRZE), so that it can be restored in case of an accidental erase by the user or a massive hard disk failure. | ||
+ | This workflow is facilitated by a number of IT services mostly hosted on OICE servers. These are | ||
+ | * A **central user account database** provided by an LDAP server for managing user authentication with all externally provided OICE services (Wiki, PPMS, NT4 PDC, User DB), \\ hosted on //Romulus// | ||
+ | * An **Windows NT4 Primary Domain Controller** (NT4 PDC) for managing central logins on microscope controller PCs running Microsoft Windows and for providing CIFS share drives for users and staff members, \\ hosted on //Romulus// | ||
+ | * A **DokuWiki Wikipedia-styled framework** for internal and external dokumentation, | ||
+ | * A **booking system** (PPMS) for devices in the OICE pool, \\ externally hosted by StratoCore, but users are authenticated via the OICE LDAP server | ||
+ | * A dedicated high performance (RAID 6 array of 15000 rpm disks) Thecus N16000PRO **storage server** //Remus// directly connected to //Romulus// via iSCSI over 1000Mbps-Ethernet. | ||
+ | * A dedicated high capacity **backup server** (RAID 6 array of currently 8 disks holding 8 Terabyte each) // | ||
- | ===== Server: Romulus ===== | + | The interdependence between these services is also shown in the following figure: |
- | + | ||
- | ===== Server: Remus ===== | + | |
- | + | ||
- | ===== Server: RheaSilvia ===== | + | |
- | + | ||
- | + | ||
+ | {{: | ||
+ | The following links lead to a detailed description of the setup of each of the current OICE servers. Whenever custom scripts where used, please also refer to the comments in the code itself. | ||
+ | * [[internal: | ||
+ | * [[internal: | ||
+ | * [[internal: | ||
internal/oice_it_infrastructure.1454602590.txt.gz · Last modified: 04.02.2016 - 16:16 by tnowak