The following list shows the steps that are required to add a site to
the Dissemination testbed (GriDis)


1) User certificates are issued by CNRS, thus the CA CNRS needs to be
   trusted:

   see: 

   http://marianne.in2p3.fr/datagrid/ca/ca-table-ca.html

   which are the following 3 RPMs:

   [hst@lxshare0409 certificates]$ rpm -qa | grep ca | grep CNRS
   ca_CNRS-Projets-0.16-1
   ca_CNRS-DataGrid-0.16-1
   ca_CNRS-0.16-1

2) Add the tutorial users to the grid-mapfile. All the users are
   listed in the LDAP VO for tutor:

   ldap://marianne.in2p3.fr/ou=EDGtutorial,o=testbed,dc=eu-datagrid,dc=org

   In detail, you need to configure the grid-mapfile creation process
   as follows:

   /op/edg/etc/mkgridmap.conf needs to be extended by the following
   line:
   
   group ldap://marianne.in2p3.fr/ou=EDGtutorial,o=testbed,dc=eu-datagrid,dc=org .tutor
   

3) All machines (CEs, WNs, SEs) need to allow for the VO tutor and the
   grid-mapfiles need to updated with the tutorial users. Also,
   accounts for tutor need to be created (similar to other VOs
   e.g. tutor001, tutor002 etc.)

4) for data Management, the WNs need to be configured with the DM
   software for the VO tutor, in particular, the RC configuration file
   needs to point to the RC at NIKHEF which hosts the VO tutor:

   ldap://grid-vo.nikhef.nl:10789/lc=EDGtutorial WP1 Repcat, rc=EDGtutorialReplicaCatalog,dc=eu-datagrid,dc=org


   an example of a correct rc.conf is:

RC_REP_CAT_MANAGER_DN=cn=Manager, rc=EDGtutorialReplicaCatalog,dc=eu-datagrid,dc=org
RC_REP_CAT_MANAGER_PWD=EDGtutorial 
RC_REP_CAT_URL=ldap://grid-vo.nikhef.nl:10789/rc=EDGtutorialReplicaCatalog,dc=eu-datagrid,dc=org
RC_LOGICAL_COLLECTION=ldap://grid-vo.nikhef.nl:10789/lc=EDGtutorial WP1 Repcat,rc=EDGtutorialReplicaCatalog,dc=eu-datagrid,dc=org 
RLS=none
LRC=rls://ced-rc0.datagrid.cnr.it
GDMP_STAGING=no
GDMP_VO=tutor

5) on the SE, the Storage Directory for the VO tutor needs to be
   created. This can be done e.g. by running the configuration GDMP
   configuration for the VO tutor.

   NOTE: for the tutorial, GDMP is not used and thus it does not need
   to configured. Only the storage area needs to be correct:

   For example:

   /flatfiles/SE00/tutor   ... needs exists (or a similar directory)


---> most of the configuration part can actually done with LCFG for
     the CE/WN and SE



6) You must run a site GIIS that will register with the GriDis top GIIS.
   To run a site GIIS one of your CE, modify the file /etc/globus2.conf and
   add the following entries:

	[mds/gris/registration/site]
	regname=<tag>
	reghn=<cehost.domain.country>

        [mds/giis/site]
        name=<tag>

  where <cehost.domain.country> is the full DNS name of your CE host and
  <tag> is just a string identifying your site.
  If you already have a site GIIS running on your CE, then all the above 
  is already done.

  In order to have all GRISes at your site register with the site GIIS that
  you just setup, you have to add the following entry in the /etc/globus2.conf
  file of all SEs and CEs:

        [mds/gris/registration/site]
        regname=<tag>
        reghn=<cehost.domain.country>

  If you already have a site GIIS running on one CE, then all the above
  is already done.


  This site GIIS has to register with the GriDis TOP GIIS.
  To do so, the sites have to add the following entry in the 
  /etc/globus2.conf file of the site GIIS machine:

       [mds/giis/site/registration/cedpro]
       name=<tag>
       regname=cedpro
       reghn=ced-ii0.datagrid.cnr.it
 
  where <tag> is exactly the same as before, a string identifying your site.

  Once all the above is done, you need to restart the MDS daemons on all
  CEs and SEs at your site.
  To do so, please run the following:
	/etc/rc.d/init.d/globus-mds restart

  Please, communicate to hep-project-grid-tutorial@cern.ch the name
  of your site GIIS.

AIM:

A site can either contribute with CE(s) and/or SEs. The aim is that
the RB from GriDis can submit jobs to addition CEs and that our data
management tools work for release 1.4.x.

We can test that with:
  
  1) dg-job-submit -r resource file.JDL     (for the CE)
  2) edg-replica-mananger-copyAndRegister   (for the SE)
  3) edg-replica-manager-deleteFile         (for the SE)

Once these commands work, we whould be fine.

In EDG release 2.0 we use new replica manager client tools that can be
used on the same SE configuration.