Adds in Vlado's comments on configuring ObjectStore

doc/latex/CTA_Admin_Install.tex

@@ -191,26 +191,55 @@ In a production system, configure the ObjectStore to use Ceph. To install Ceph:
 # yum-config-manager --enable ceph
 # yum -y install ceph-common
 \end{lstlisting}
+\begin{alertbox}
+The Ceph client version must match the version of the Ceph server you are connecting to. If there are problems
+connecting, check the required version number with the Ceph server administrator. At the time of writing, the
+required version is:
+\begin{lstlisting}
+# ceph --version
+ceph version v11.0.0-2590-g08becd3 (08becd34a82b2c541f0aeeaf28c4038faf268d47)
+\end{lstlisting}
+\end{alertbox}
+
 Specify the location of the Ceph cluster monitor daemon in \texttt{/etc/ceph/ceph.conf}. To use the CERN Ceph cluster
 monitor:
 \begin{lstlisting}
 [global]
    mon host = cephmond.cern.ch:6790
 \end{lstlisting}
-Specify the location of the new ObjectStore:
+Configure the following environment variables to specify the ObjectStore. For convenience, save these in a file
+(e.g. \texttt{/etc/sysconfig/ceph.conf}) which can be sourced from the shell:
 \begin{lstlisting}
+# Initialise ObjectStore configuration with:
+#
+# . /etc/sysconfig/ceph.conf
+#
+# Declare which type of ObjectStore you have. Possible values: file or ceph
 export OBJECTSTORETYPE=ceph
-export OBJECTSTOREID=cta-id
-export OBJECTSTOREPOOL=cta-tapepool
+
+# Define the ObjectStore ID, which corresponds to the Ceph user name. The Ceph
+# service manager should provide this value.
+export OBJECTSTOREID=eoscta
+
+# Define the ObjectStore pool name on Ceph. The Ceph service manager should
+# provide this value.
+export OBJECTSTOREPOOL=eoscta_metadata
+
+# Define the ObjectStore namespace name which will be prepended to all objects
+# in the ObjectStore. The CTA service manager defines this value. Usually it is
+# kept as "cta-ns".
 export OBJECTSTORENAMESPACE=cta-ns
-export OBJECTSTOREURL= rados://${OBJECTSTOREID}@${OBJECTSTOREPOOL}:${OBJECTSTORENAMESPACE}
+
+# This is just to construct the URL from the above values
+export OBJECTSTOREURL=rados://${OBJECTSTOREID}@${OBJECTSTOREPOOL}:${OBJECTSTORENAMESPACE}
 \end{lstlisting}
-Create the Ceph keyring for this CTA instance (\texttt{/etc/ceph/ceph.client.cta-id.keyring}):
+Create the Ceph keyring for this CTA instance (\texttt{/etc/ceph/ceph.client.\${OBJECTSTOREID}.keyring}). Fill in the
+values which correspond to the environment variables defined above:
 \begin{lstlisting}
-[client.cta-id]
+[client.OBJECTSTOREID]
    key = CEPH_OBJECTSTORE_SECRET_KEY
    caps mon = "allow r"
-   caps osd = "allow rwx pool=cta-tapepool namespace=cta-ns"
+   caps osd = "allow rwx pool=OBJECTSTOREPOOL namespace=OBJECTSTORENAMESPACE"
 \end{lstlisting}
 \begin{alertbox}
 There is also a configuration file \texttt{/etc/ceph/rbdmap} but this appears to contain only comments:
@@ -224,12 +253,16 @@ There is also a configuration file \texttt{/etc/ceph/rbdmap} but this appears to
 \begin{lstlisting}
 # cta-objectstore-initialize $OBJECTSTOREURL
 \end{lstlisting}
-List the ObjectStore content:
+To list the ObjectStore content:
 \begin{lstlisting}
 # rados -p $OBJECTSTOREPOOL --id $OBJECTSTOREID --namespace $OBJECTSTORENAMESPACE \
     ls
+cta-objectstore-initialize-p06253947b39467.cern.ch-192840-20170512-12:56:25 root
+driveRegister-cta-objectstore-initialize-p06253947b39467.cern.ch-192840-20170512-12:5
+agentRegister-cta-objectstore-initialize-p06253947b39467.cern.ch-192840-20170512-12:5
+schedulerGlobalLock-cta-objectstore-initialize-p06253947b39467.cern.ch-192840-2017051
 \end{lstlisting}
-Delete the ObjectStore content:
+To delete the ObjectStore content:
 \begin{lstlisting}
 # rados -p $OBJECTSTOREPOOL --id $OBJECTSTOREID --namespace $OBJECTSTORENAMESPACE \
     ls | xargs -itoto rados -p $OBJECTSTOREPOOL --id $OBJECTSTOREID --namespace \
@@ -259,12 +292,29 @@ To use this configuration to create a new database schema:
 \begin{lstlisting}
 # cta-catalogue-schema-create /etc/cta/cta_catalogue_db.conf
 \end{lstlisting}
-To delete an existing database schema:
+To drop an existing database schema:
 \begin{lstlisting}
-# cta-catalogue-schema-unlock /etc/cta/cta_catalogue_db.conf
-# cta-catalogue-delete-all-data /etc/cta/cta_catalogue_db.conf
-# cta-catalogue-schema-status /etc/cta/cta_catalogue_db.conf
 # cta-catalogue-schema-drop /etc/cta/cta_catalogue_db.conf
+WARNING
+You are about to drop the schema of the CTA calalogue database
+    Database name: devdb12
+Are you sure you want to continue?
+Please type either "yes" or "no" > yes
+DROPPING the schema of the CTA calalogue database
+Dropped table CTA_CATALOGUE
+Dropped table ARCHIVE_ROUTE
+Dropped table TAPE_FILE
+Dropped table ARCHIVE_FILE
+Dropped table TAPE
+Dropped table REQUESTER_MOUNT_RULE
+Dropped table REQUESTER_GROUP_MOUNT_RULE
+Dropped table ADMIN_USER
+Dropped table ADMIN_HOST
+Dropped table STORAGE_CLASS
+Dropped table TAPE_POOL
+Dropped table LOGICAL_LIBRARY
+Dropped table MOUNT_POLICY
+Dropped sequence ARCHIVE_FILE_ID_SEQ
 \end{lstlisting}
 
 \section{Configure CTA Front End}
@@ -417,10 +467,10 @@ host and user, by connecting directly to the catalogue database.
 If the CTA instance is not using real tape hardware, follow the directions in Appendix~\ref{install_mhvtl} to install the
 mhVTL Virtual Tape Library.
 
-Add the following lines to \texttt{/etc/cta/cta.conf}:
+Add the following lines to \texttt{/etc/cta/cta.conf}. Fill in OBJECTSTOREURL with the value defined in Section~\ref{install_cta_configure_objectstore}:
 \begin{lstlisting}
 taped BufferCount 10
-general ObjectStoreURL rados://cta-id@cta-tapepool:cta-ns
+general ObjectStoreURL OBJECTSTOREURL
 \end{lstlisting}
 \begin{alertbox}
 BufferCount specifies the size of the ObjectStore in blocks. But what is the size of a block?

doc/latex/CTA_Admin_Intro.tex

@@ -20,6 +20,8 @@ Documentation should explain and separate the various functions of individual se
 \section{Authentication between CTA Servers}
 
 \begin{alertbox}
-Documentation should explain why three SSS are needed. Picture explaining where and how they are used would be nice.
+Section~\ref{install_cta_configure_front_end} and Figure~\ref{fig:cta_krb5_sss_keys} explain why multiple Kerberos and
+Simple Shared Secret (SSS) keys are necessary. Probably we should move the conceptual information here and leave the
+instructions in Chapter~\ref{install_cta}.
 \end{alertbox}