II - Installation guide

Now that we've got the cta-release package installed and we created the versionlock.list, we can start downloading all of the CTA components in order to set up our instance. Again, note that you will probably need some other packages if you are using EOS instead of dCache.

It is up to you whether to distribute the elements that make up your infrastructure into different machines and how. For instance, you could have a dedicated machine for the frontend, another one acting as a tapeserver, and have the catalogue database on another third one to keep things organized, isolated and avoid overloading. Or you can just go and install everything on the same server if you have to do some testing, it will work as well. If you don't have a physical tape library to work and play with, you can always download MHVTL, which consists in a configurable virtual tape library. Again this is up to your choice and available resources. :-)

Installing the required packages

If you do this command you'll see there is a lot of CTA packages and dependencies that you are able download and install:

cta-versionlock check

Let's install the basic packages to set up a frontend, tapeserver and the other necessary tools all in one single server:

yum install cta-catalogueutils cta-cli cta-frontend cta-frontend-grpc cta-objectstore-tools cta-rmcd cta-smc cta-tape-label cta-taped krb5-workstation oracle-instantclient19.3-basic

You will see that a bunch of dependencies have to be installed too. You can check your already installed packages and if their version is correct with the following command:

cta-versionlock checkpkg

• To get frontend packages only:

yum install cta-frontend cta-frontend-grpc cta-common xrootd-server-libs cta-lib-common cta-objectstore-tools cta-lib cta-cli cta-lib-catalogue krb5-workstation xrootd-server xrootd-libs xrootd-client-libs libradosstriper1 librados2 

• To get tapeserver packages only:

yum install cta-taped cta-smc cta-rmcd cta-tape-label cta-lib cta-common cta-lib-common cta-catalogueutils cta-lib-catalogue cta-objectstore-tools eos-folly eos-folly-deps xrootd-server xrootd-server-libs xrootd-client xrootd-client-libs xrootd-libs libradosstriper1 librados2 

That's it, you are done installing everything needed in order to set up your CTA instance. Now CTA has to be able to communicate with dCache pools. These pools must first have the dcache-cta plugin installed. Jump to the next page to see the steps. If you are not using dCache or want to keep this for later, jump directly to III - Configuration guide.