Skip to content

Remove tsm #2013

Merged
merged 1 commit into from
Nov 30, 2020
Merged

Remove tsm #2013

merged 1 commit into from
Nov 30, 2020

Conversation

donald
Copy link
Collaborator

@donald donald commented Nov 30, 2020

tsm ("Tivoli Storage Manager" which is now "IBM Spectrum Protect") is
used by a single application (archives). The installation of the current
client with bee on all systems would be much more complex now than
it was in the past, because

  • there is now a plugin machinery where shared libraries get loaded
    at runtime. So it is no longer trivial to see, which libraries are
    needed. A complete installation, on the other hand, consists of about
    600 files which seems to be kind of overkill when these files get
    distributed to and backed up on each system.

  • the client maintains more "local" data like keys generated for the
    client and certificates downloaded from the server. These maintained
    files, of course, would need to be special handled, otherwise they
    would be overwritten by the distmaster. This would require a lot of
    reverse engineering to identify everything and special code to handle
    it.

For our only application using tsm, I've created an installation
in its project directory (at /confidential/archive/tsm). The tsm backup
and archive client is no longer needed in the system.

So remove it. It is a binary anyway.

tsm ("Tivoli Storage Manager" which is now "IBM Spectrum Protect") is
used by a single application (archives). The installation of the current
client with bee on all systems would be much more complex now than
it was in the past, because

- there is now a plugin machinery where shared libraries get loaded
at runtime. So it is no longer trivial to see, which libraries are
needed. A complete installation, on the other hand, consists of about
600 files which seems to be kind of overkill when these files get
distributed to and backed up on each system.

- the client maintains more "local" data like keys generated for the
client and certificates downloaded from the server. These maintained
files, of course, would need to be special handled, otherwise they
would be overwritten by the distmaster. This would require a lot of
reverse engineering to identify everything and special code to handle
it.

For our only application using tsm, I've created a installation
in its project directory (at /confidential/archive/tsm ). The tsm backup
and archive client is no longer needed in the system.

So remove it. It binary anyway.
@pmenzel pmenzel merged commit cc98dea into master Nov 30, 2020
Sign in to join this conversation on GitHub.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants