1. 15 Jun, 2021 1 commit
  2. 02 Jun, 2021 1 commit
  3. 14 Jan, 2021 1 commit
  4. 12 May, 2020 1 commit
  5. 14 Apr, 2020 1 commit
  6. 26 Jul, 2019 1 commit
    • Eric Cano's avatar
      #533 Changed strategy for implementation. · 6385126d
      Eric Cano authored
      Moved the space reservation information to the DriveStatus object store object instead of a new central registry.
      The central registry would have been a single point of contention as was the DriveRegistry before being split into
      DriveStates. As the problem is so close to the one of the drive status, we can actually reuse the drive status for this purpose.
      
      The algorithm will also change as we move the responsibility of querying the free space from the disk systems into the OStoreDb
      object instead of the Scheduler. This leads to a slightly worth layering of responsibilities, making the OStoreDb::RetrieveMount
      object a client of the disk::DiskSystemFreeSpaceList object.
      
      The current implementation will also query the free space from the disk systems on each pop, instead of doing so in a globally
      cached fashion. With the new model, we could cache the free space per drive (if needed), but not globally. This is not expected
      to be a real issue and free space is a global counter in the disk system, expected to be readily available.
      6385126d
  7. 23 Jul, 2019 1 commit
  8. 05 Jul, 2019 1 commit
  9. 03 Jul, 2019 1 commit
  10. 02 Jul, 2019 1 commit
  11. 01 Jul, 2019 1 commit
  12. 05 Mar, 2019 1 commit
    • Eric Cano's avatar
      Expanded retrieve requests for repack · 19266cc0
      Eric Cano authored
      The retrieve requests now carry all the information necessary to create the archive jobs.
      Retrive requests carry an isRepack boolean. The distinction between repack and non-repack behaviour
      is pushed as low as possible in the api (in the object store) so that client code can be more
      generic. For the same reason, the
      The expand repack mode (re-creation of missing tape files) is not supported yet.
      Changed the represenation of copy numbers to uint32 (as this is the smalled number supported but protocol buffers).
      Added ArchiveRoute::StorageClassMap and ArchiveRoute::FullMap to store archive routing in memory.
      Added repack buffer base URL support, and mechanism to compute temporary copy location in disk cache.
      Fixed bug in ObjectOps<>::asyncInsert();
      Inplemented the path generation for repack disk storage (<BaseURL>/<VID>/<FSeq (09%d)>).
      19266cc0
  13. 22 Jan, 2019 1 commit
  14. 29 May, 2018 1 commit
  15. 03 May, 2018 1 commit
  16. 22 Mar, 2018 1 commit
    • Eric Cano's avatar
      Implemented bulk retrieve request reporting · 72933cef
      Eric Cano authored
      Successful retrieve requests are asynchronously deleted as soon as they
      are complete. Then from time to time (every 500), the requests get removed from
      process ownership in bulk.
      72933cef
  17. 09 Aug, 2017 1 commit
  18. 27 Jul, 2017 1 commit
  19. 13 Jul, 2017 1 commit
  20. 12 Jul, 2017 2 commits
  21. 27 Jun, 2017 1 commit
  22. 26 May, 2017 1 commit
  23. 04 Jan, 2017 2 commits
  24. 15 Dec, 2016 2 commits
  25. 14 Dec, 2016 1 commit
  26. 08 Nov, 2016 1 commit
  27. 11 Oct, 2016 2 commits
    • Steven Murray's avatar
      Deleted mediachanger dir from castor dir · b38715e6
      Steven Murray authored
      b38715e6
    • Victor Kotlyar's avatar
      Ported commits from castor/master for Encryption: · 1a3812e0
      Victor Kotlyar authored
      6b6374d6c2e209c98c0d4d7aa665e1df83d71aaa
        CASTOR-5350: Introduce encryption SCSI commands in tape drive
        backend
      
        Implementation of two methods:
          * setEncryptionKey(key): Sets encryption params to drive.
          * clearEncryptionKey: Clears encryption params from drive.
      
      3cf91d48f5c7b0cb563c3037aee69ec769f5ab94
        Added support for an interface script that will setup drive
        encryption per tape
      
      e9ca601687508de20fab7154e63bb0dbd1b25a8a
        Migrate TapeWriteSingleThread::TapeCleaning::~TapeCleaning() body to
        .cpp
      
      266b02d8175b5cfc0b688135cbdc335e93060b
        CASTOR-5350: Refactor support for only external key management script
      
      789b26a0bc69053ff1ab792a02676a7753f093ed
        Merge branch 'encryption_backend' into 'master'
      
        CASTOR-5350: Encryption backend
      
        ## Description
          The aim of this merge request is to incorporate encryption support
          into CASTOR.
          The proposed changes are to be used in conjunction with the
          operators'
          [ExternalEncryptionKeyScript](https://gitlab.cern.ch/slaskari/castor-get-encryption-key).
      
          The **aim** is to enable encryption in specific tape pools of
          CASTOR.
        ## Changes
          * Introduce encryption SCSI backend to DriveGeneric.
          * Introduce encryption control wrapper
          * (`castor/tape/tapeserver/daemon/EncryptionControl`) for
          * abstracting the two sub-components of:
            * Calling the `ExternalEncryptionKeyScript`,
            * Calling the equivalent DriveGeneric function for
            * passing/clearing the encryption parameters to/from the drive.
          * Add new configuration option in `castor.conf` for the external key
          * management script.
          * Create a Subprocess wrapper for executing external commands as
          * CASTOR children (`castor/server/Subprocess.{h,c}pp`).
          * Incorporate encryption handling in the:
            * DataTransferSession
            * LabelSession
            * CleanerSession
          * Add encryption control timer in the task Watchdog.
        See merge request !1
      
      fa550707c42d80466bbd448e355aaf9be5ea8e04
        Clear encryption key only when encryption enabled
        Changes include:
          - Making EncryptionControl stateful
          - Calling clearEncryptionKey on the drive only when encryption is
            on.
        Also includes a minor duplicate code fix on DriveGeneric.
      cf4eb9f3ae36c9cfc9c40349d69ab6642020e81e
        Merge branch 'encryption_changes' into 'master'
        Clear encryption key only when encryption enabled
        ## Description
          Changes include:
          - Making EncryptionControl stateful
          - Calling `clearEncryptionKey()` on the drive only when encryption
            is on.
          Also includes a minor duplicate code fix on **DriveGeneric.cpp**.
        See merge request !2
      
      40366d963ee33ca081df6c991189b21369e461fd
        Check if the drive has encryption capability enabled:
          * Add isEncryptionCapEnabled() vendor-specific function
          * Check isEncryptionCapEnabled() before passing encryption params
          * Check isEncryptionCapEnabled() before clearing encryption params
          * Clear encryption key before unencrypted I/O
      
      4ccc661d01eccfc3fdfb9ee2578d15a147a0c55a
        Merge branch 'encryption_capability_enabled' into 'master'
        Drive encryption capabilities inclusion
        ## Description
          The aim of this merge request is to address issues related to
          encryption on drive without the encryption capability enabled.
          More specifically:
            * It introduces a vendor-specific way of identifying if the drive
            * has encryption capability enabled
            * **IBM**: Through the SPIN index SCSI page
            * **Oracle**: Through the general INQUIRY SCSI page
            * If the data to be written are to be encrypted, an additional check
            * of the encryption capability of the drive is made. In case of
            * encrypted data, but no encryption capability, the session fails.
            In essence, all encryption related operations are made modulo the
          encryption capability of the drive.
            Last, in case of unencrypted I/O, we clear the keys of the drive (if
          encryption capable) to avoid encrypted data with previous keys on
          CASTOR's system failure.
        ## Testing
          Before the merge request's submission, the following tests were
          passed:
            On drives with **encryption capability enabled**:
              * Label session
              * Label with previously set encryption key
              * Write without encryption
              * Read without encryption
              * Write with encryption
              * Read with encryption
              * Write with previously set encryption key
              * Read with previously set encryption key
            On drive with **encryption cabability disabled**:
              * Label session
              * Write without encryption
              * Read without encryption
              * Write with encryption - session **should** fail
              * Read with encryption - session **should** fail
          See merge request !3
      
      55b85a2cb4681d697565116c00ff98c6becea4fb
        Secure session against invalid encryption script output
      
      3a54875c680fe6c1c9d5cf25cf98d2780196e0d1
        Changes in encryption workflow
          - VMGR tag is updated only on write operations
          - Empty key signifies no encryption
      
      f5408cf0ccbae9a4ab94a533f3b6d7be323f72fb
        Minor encryption log enhancements
          * Error line in Read/Write session with ErrorMesage key
          * Fix for delimiter in the end of arguments in argsToString()
      2e7204fb0dd24b472a959fa5e13320c34df4f017
        Merging in improvements on tape encryption support.
      
      92533a1746d0744ee528781558a720c63ca3c4d1
        Removed nullptr which is not supported in SLC6's gcc.
        Added automatic deletion of json objects in
        EncryptionControl::parse_json_script_output.
      
      fca3bb9e7fce364b429fc0b5c036fb752fd67ff1
        Fix log typo
      1a3812e0
  28. 06 Oct, 2016 1 commit
    • Eric Cano's avatar
      Implemented drive status support in drive register structure and code. · 56c4c332
      Eric Cano authored
      Added drive status reporting in scheduler
      Added drive status reporting in OStoreDB
      Added support for drive status listing in the front end
      Removed virtual functions from the Scheduler, which is never overloaded.
      Added DesiredDriveState structure to drive state.
      Removed usage of duplicate MountType, DriveStatus and DriveState structures.
      Created DriveInfo structure to allow recreation of drive register entry in all
      reporting situation (potentially with partial/assumed info).
      56c4c332
  29. 04 Oct, 2016 1 commit
  30. 30 Sep, 2016 1 commit
    • Victor Kotlyar's avatar
      Ported commits from castor/master for general,drive,volume SCSI statistics: · e8b4ec34
      Victor Kotlyar authored
      fa889fed2541e22179b5e035d863f87e7be18fb9
        CASTOR-5322 RFE: Enhance tapeserverd logs with SCSI tape drive
          statistics
      
      b13f495e4ee229b2469f9470a2ffa6b4003a29ec
        Fix for mhtvl scsi log sense exceptions
      
      ad71058fbcb6de85e0440797d7ffa5358e26bf89
        CASTOR-5329 Enhance tape statistics
      
      806e48f4285122d8ab9f118364a15e740518028f
        CASTOR-5332 RFE: Reduce log level to INFO with MHVTL - SCSI Statistics
          could not be acquired from drive
      
      79c5a4c2c36b7acc5b10505ca1694fd521fc6832
      c7f6d4d7aaa564b37c2b36c3110dfe2fc96ec970
        Move volume SCSI statistics inside the dtor of TapeCleaningMove volume
          SCSI statistics inside the dtor of TapeCleaning
      
        ## Description
      
        When first introduced volume SCSI Statistics (at the moment
        IBM-specific), we explicitly put the function after the unmount of the
        tape was done due to an invalid file descriptor error occurring during
        the SCSI query.
      
        This bug no longer occurs for IBM drives.
        This may be attributed to the update of firmware of the IBM drives
      
        Apart from the change of the position of the changes, there is no
        alteration in terms of the metrics reported from the drive to the logs.
      
        ## Testing
      
        The tests the new code has been through are:
          * Write/Read file on IBM lib0 drive *(older one)*
          * Write/Read file on IBM lib4 drive *(newer one)*
          * Write/Read file on Oracle T10k drive
      e8b4ec34
  31. 09 Sep, 2016 1 commit
  32. 05 Sep, 2016 1 commit
  33. 01 Sep, 2016 1 commit
  34. 12 Feb, 2016 1 commit
  35. 29 Jan, 2016 1 commit
  36. 27 Jan, 2016 1 commit