internal:oice_calendars
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| internal:oice_calendars [28.10.2016 - 05:50] – bschmid | internal:oice_calendars [04.07.2023 - 08:16] (current) – [OICE Calendars] bschmid | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| On romulus we host a [[http:// | On romulus we host a [[http:// | ||
| - | * seminars: Dates for lectures, workshops, seminars, demos, etc. | ||
| - | * visitors: Dates for external visitors | ||
| - | * meetings: Dates for internal meetings and meetings with users, etc | ||
| - | * maintainance: | ||
| - | * ralf_official: | ||
| + | * **OICE General**: Dates for meetings, workshops, seminars, visitors, demos, etc. (DAV url: https:// | ||
| + | * **Maintenance**: | ||
| + | * **Seminar-Room**: | ||
| + | * **Out of office**: (DAV url: https:// | ||
| + | * **Deadlines**: | ||
| + | * **Bene**: Bene's meetings with users (DAV url: https:// | ||
| + | * **Philipp**: | ||
| + | * **Ralf Official**: Official calendar for Ralf (DAV url: https:// | ||
| + | |||
| + | * < | ||
| + | * < | ||
| + | * < | ||
| + | |||
| + | * < | ||
| + | * < | ||
| + | * < | ||
| More calendars can be added as we find need for it. | More calendars can be added as we find need for it. | ||
| - | The OICE aims to supply an effective working environment for all its users. A typical workflow is as follows: | ||
| - | - The user contacts a staff member with details about the experiment that is to be conducted. The staff member will, together with the user, determine which OICE device or devices is/are best suited for the scientific question at hand. | + | ========= Access |
| - | - The user contacts the OICE IT administrator (from here: IT admin) or another staff member with the appropriate permissions for a **central OICE account** | + | Access |
| - | - The user uses his account to login to the OICE wiki pages to inform himself/ | + | |
| - | - If the user is not sufficiently apt at using the appropriate devices (mostly optical microscopes), | + | |
| - | - The user receives a security introduction to the OICE premises, including the S2-GenTech labs. | + | ========= Using thunderbird as client ========= |
| - | - The user provides proof that he/she has undergone the necessary yearly safety briefings and additionally, | + | |
| - | - The user uses his/her account to book time on the appropriate microscopes via the PPMS booking system (not hosted at the OICE). | + | {{: |
| - | - The user logs into the controlling PC of the booked microscopes via his/her central OICE account. After the login, his/her used time is reported periodically to the PPMS servers via a VBS script that runs on every device PC. | + | {{: |
| - | - After finishing the session, the user either manually uploads the acquired images to our central OMERO server or uses a provided CIFS share drive (usually on X:) to automatically trigger an upload via the OMERO Dropbox feature. If an automatic upload is chosen, | + | {{: |
| - | - When everything is finished, the user logs out which will stop the time keeping by the PPMS script. The time of this session is then saved by the PPMS system and can be used later for invoicing and statistics. | + | {{: |
| - | - 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. | + | {{:internal: |
| + | |||
| + | ========= Using Outlook as client ========= | ||
| + | |||
| + | MS Outlook cannot natively handle CalDAV calendars and therefore needs the [[https://sourceforge.net/projects/outlookcaldavsynchronizer/ | ||
| - | 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) // | ||
| - | The interdependence between these services is also shown in the following figure: | ||
| - | {{: | ||
| - | 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/oice_calendars.1477633801.txt.gz · Last modified: 28.10.2016 - 05:50 by bschmid