1. 22 Jun, 2017 1 commit
    • Eric Cano's avatar
      Fixed end of session being reported too early in ArchiveSessions. · bb2436c1
      Eric Cano authored
      This led to VID being marked as available during unmount, and another drive could try an mount the same tape.
      Added various logs.
      
      The following sequence was observed in tests (with a sleep(3) at the end of MigrationReportPacker::ReportDriveStatus::execute() ):
       [eric@localhost ~]$ date; kubectl -n cta exec ctacli -- cta dr ls VDSTK11
      Thu Jun 22 11:19:10 CEST 2017
          drive   host  library  mountType    status  desiredUp  forceDown     vid
        VDSTK11  tpsrv  VLSTK10    Archive  Mounting         UP             V01001
      [eric@localhost ~]$ date; kubectl -n cta exec ctacli -- cta dr ls VDSTK11
      Thu Jun 22 11:19:12 CEST 2017
          drive   host  library  mountType       status  desiredUp  forceDown     vid
        VDSTK11  tpsrv  VLSTK10    Archive  Transfering         UP             V01001
      [eric@localhost ~]$ date; kubectl -n cta exec ctacli -- cta dr ls VDSTK11
      Thu Jun 22 11:19:16 CEST 2017
          drive   host  library  mountType      status  desiredUp  forceDown     vid
        VDSTK11  tpsrv  VLSTK10    Archive  CleaningUp         UP             V01001
      [eric@localhost ~]$ date; kubectl -n cta exec ctacli -- cta dr ls VDSTK11
      Thu Jun 22 11:19:18 CEST 2017
          drive   host  library  mountType     status  desiredUp  forceDown     vid
        VDSTK11  tpsrv  VLSTK10    Archive  Unloading         UP             V01001
      [eric@localhost ~]$ date; kubectl -n cta exec ctacli -- cta dr ls VDSTK11
      Thu Jun 22 11:19:22 CEST 2017
          drive   host  library  mountType      status  desiredUp  forceDown     vid
        VDSTK11  tpsrv  VLSTK10    Archive  Unmounting         UP             V01001
      [eric@localhost ~]$ date; kubectl -n cta exec ctacli -- cta dr ls VDSTK11
      Thu Jun 22 11:19:25 CEST 2017
          drive   host  library  mountType  status  desiredUp  forceDown  vid
        VDSTK11  tpsrv  VLSTK10    NoMount      Up         UP               -
      bb2436c1
  2. 21 Jun, 2017 3 commits
  3. 20 Jun, 2017 12 commits
  4. 19 Jun, 2017 12 commits
  5. 16 Jun, 2017 3 commits
  6. 15 Jun, 2017 1 commit
  7. 14 Jun, 2017 3 commits
  8. 13 Jun, 2017 2 commits
  9. 12 Jun, 2017 2 commits
    • Steven Murray's avatar
      Fixed a bug introduced with the previous commit · aea06d98
      Steven Murray authored
      concerning this issue.
      aea06d98
    • Steven Murray's avatar
      cta/CTA#135 cta <subcommand> ls output order · 59d65ba0
      Steven Murray authored
      All CTA catalogue configuration entities (archive route, tape,
      tape pool, etc.) except for archive file and tape file are now
      ordered alphabetically.
      
      Archive files and tape files are ordered by archive ID and copy
      number.  This ordering is required so that we can implement our
      own application level cursor over potentionally all archived
      files.  This could be well over 4 billion files.  We do not
      rely on database cursors as they would most fail before we have
      had enough time to list all archived files.
      
      If in the future we require a file listing command that orders
      achive files alphabeltically, then I would suggest the
      cta::Catalogue class implements two separate methods.  The
      first implementation would list all files in archive ID order
      and would not rely on the underlying database to implement the
      cursor.  iBasically whta we have today.  The second
      implementation would list all files in alphabetcial order and
      would rely on the underlying database to achieve this.
      59d65ba0
  10. 11 Jun, 2017 1 commit