This memo summarizes the procedure to install new pipelines, new versions
of the DFS and similar issues related to the quality and the flowmgr
account on the dfo blades and the qc cluster.  The main feature of the
procedure is that OTS maintains the password of the quality account but
strictly maintains the account according individual tickets submitted
by QCDP.

use cases:

1 install a new pipeline version on the quality account
2 deinstall an older pipeline version on the quality account
3 reset the link to the default version of the pipeline
4 install a new DFS or related subsystem like MIDAS or CPL on the
flowmgr account.

Use cases 1-3 impact only one user of QCDP group. The proposed procedure
is:

use case 1:
a) The pipeline developer wants to send a new pipeline installation
   request to SOS Group scp  amber-pipeline-software-file
   sospipe@hsr01:/home/sospipe/amber password will be requested <passwd
   will be supplied by SOS Group> The developer will receive an e-mail
   confirming receipt of pipeline.  The QC scientist who is responsible
   for and the SOS Group will also receive an e-mail, so that OTS
   tickets can be logged and appropriate downtime slots can be
   negotiated for the installation.
b) The QC scientist gives green light within the OTS ticket 
    to trigger the installation.
c) SOS executes the request on the quality account.

use case 2 and 3:
a) The QC scientist issues an OTS ticket to trigger the deinstallation
   or the change of the link for the default pipeline version. 
b) OTS executes the request on the quality account.

Use case 4 impacts all users of the QCDP group.  The procedure involves
the QCDP contact person instead of the instrument specific QC scientist.

use case 4:
a) SEG puts the new software on a dedicated account on hsr01; an OTS
   installlation ticked is opened automatically and emails are send to
   seg, and QCDP contact person (for the time being whummel@eso.org)
   that a new DFS or other subsystem is available for the flowmgr
   account. SEG will attach related information: release notes,
   installation/configuration instructions and location.
b) The QCDP contact person issues an OTS ticket to trigger the installation.
c) OTS executes the request on the flowmgr account.