Difference: ARGUSandGLEXECInstallations (3 vs. 4)

Revision 42013-10-25 - AlessandroPaolini

 			 META TOPICPARENT 
			 name="WebHome" 
		
 
  A guideline on how to deploy ARGUS and gLexec on own grid site 
  1 - Install an ARGUS server
   2 - Install and configure gLexec on your WNs
   3 - properly configure your CREAM
   4 - enable gLexec monitoring
- META TOPICPARENT
+ name="WebHome"
 - Install an ARGUS server
-<
<
+We recommend to install the EMI Argus.
->
>
+We recommend to install the EMI-3 Argus.
-<
<
+ EMI Case
->
>
+Use the following repository settings, from the EMI-3 generic installation and configuration guide; there is also an Argus specific installation guide that you may follow to install and configure this service
-<
<
+Use the following repository settings, instead in the EMI-1 generic installation and configuration guide you can find an Argus specific installation guide that you may follow to install and configure this service

The Mandatory genral variables are the following
->
>
+The Mandatory general variables are the following
  USERS_CONF
  GROUPS_CONF
  Yaim: /opt/glite/yaim/bin/yaim -c -s site-info.def -n ARGUS_server
-<
<
+ At this point, the Argus services (PAP, PDP and PEP Server) must be configured, up and running
->
>
+ At this point, the Argus services (PAP, PDP andP PEP Server, see Authorization Framework) must be configured, up and running: 
 information on The Simplified Policy Language.
  information on pap-admin command line interface.
  this is an example on the rules to set:
 
 
# pap-admin lp
-<
<
+ gLite Case
->
>
+default (local):
-<
<
+In case you want to install the ARGUS server on gLite, follow this guide plus the specific guide: the yaim variables are the same
->
>
+resource "http://cnaf.infn.it/igi-bologna" {
    obligation "http://glite.org/xacml/obligation/local-environment-map" {
    }

    action ".*" {
        rule permit { vo="ops" }
        rule permit { vo="dteam" }
        rule permit { vo="infngrid" }
        rule permit { vo="comput-er.it" }
        rule permit { vo="gridit" }
        rule permit { vo="igi.italiangrid.it" }
        rule permit { vo="drihm.eu" }
        rule deny { vo="enmr.eu" }
    }
}

resource "http://authz-interop.org/xacml/resource/resource-type/wn" {
    obligation "http://glite.org/xacml/obligation/local-environment-map" {
    }

    action "http://glite.org/xacml/action/execute" {
        rule permit { fqan="/ops/Role=pilot" }
    }
}
 - Install and configure gLexec on your WNs
-<
<
+We recommend to install the EMI version of gLexec (and obviously EMI WN!). So that plan the migration to EMI of your farm
->
>
+We suggest you upgrade the WNs to EMI-3 so you install the latest gLExec version.

Briefly the steps are the following:
 

 Installation: yum install glexec-wn
 
 

  Configuration: set at least the mandatory variables (and in case some of the default ones if you need a different value for them)
 
tipically set the following in services/glite-glexec_wn:
GLEXEC_WN_SCAS_ENABLED="no"

GLEXEC_WN_ARGUS_ENABLED="yes"

GLEXEC_WN_OPMODE="setuid"
-<
<
+ EMI Case 
You may have a look at the following notes to see how to install gLexec on your WNs. If you have lsf as batch system or the WNs already installed, please focus your attention on the gLexec part of those notes
->
>
+ Yaim: (example of WN with torque and MPI) /opt/glite/yaim/bin/yaim -c -s site-info.def -n MPI_WN -n WN -n TORQUE_client -n GLEXEC_wn
-<
<
+ gLite Case 
follow this guide in order to install the ig_GLEXEC_wn metapackage: the configuration files and the yaim variables to set are the same
 - properly configure your CREAM
 # In case ARGUS is to be used the following should be set
# The ARGUS service PEPD endpoints as a space separated list:
#ARGUS_PEPD_ENDPOINTS="http://pepd.example.org:8154/authz"
-<
<
+ARGUS_PEPD_ENDPOINTS="https://vgrid06.cnaf.infn.it:8154/authz"
->
>
+ARGUS_PEPD_ENDPOINTS="https://arguto.cnaf.infn.it:8154/authz"
 # ARGUS resource identities: The resource ID can be set
# for the cream CE, WMS and other nodes respectively.
 # CREAM_PEPC_RESOURCEID=urn:mysitename.org:resource:ce
# WMS_PEPC_RESOURCEID=urn:mysitename.org:resource:wms
# GENERAL_PEPC_RESOURCEID=urn:mysitename.org:resource:other
-<
<
+CREAM_PEPC_RESOURCEID="http://cnaf.infn.it/cremino"
->
>
+CREAM_PEPC_RESOURCEID="http://cnaf.infn.it/igi-bologna"
 Don't forget to set in CE_CAPABILITY the  glexec parameter, for example:
 Then reconfigure with yaim your CREAM as usual
-<
<
+ *4 - enable gLexec monitoring
->
>
+- enable gLexec monitoring
-<
<
+go on https://gocdb4.esc.rl.ac.uk/portal/ and add the service endpoint "gLExec" to your CREAM
->
>
+go on https://goc.egi.eu/portal/index.php and add the service endpoint "gLExec" to your CREAM
-<
<
+-- AlessandroPaolini - 2012-02-24
 \ No newline at end of file
->
>
+-- AlessandroPaolini - 2013-10-25

View topic | History: r5 < r4 < r3 < r2 | More topic actions...