Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Line: 119 to 119 | ||||||||
Briefly the steps are the following: | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Line: 51 to 51 | ||||||||
1 - Install an ARGUS server | ||||||||
Changed: | ||||||||
< < | We recommend to install the EMI Argus. | |||||||
> > | We recommend to install the EMI-3 Argus. | |||||||
Changed: | ||||||||
< < | 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 | |||||||
Changed: | ||||||||
< < | 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 | |||||||
| ||||||||
Line: 80 to 78 | ||||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
# pap-admin lp | |||||||
Changed: | ||||||||
< < | gLite Case | |||||||
> > | default (local): | |||||||
Changed: | ||||||||
< < | 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" } } } | |||||||
2 - Install and configure gLexec on your WNs | ||||||||
Changed: | ||||||||
< < | 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:
| |||||||
Changed: | ||||||||
< < | EMI CaseYou 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 | |||||||
> > |
| |||||||
Deleted: | ||||||||
< < | gLite Casefollow this guide in order to install the ig_GLEXEC_wn metapackage: the configuration files and the yaim variables to set are the same | |||||||
3 - properly configure your CREAM | ||||||||
Line: 117 to 153 | ||||||||
# 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" | ||||||||
Changed: | ||||||||
< < | 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. | ||||||||
Line: 126 to 162 | ||||||||
# CREAM_PEPC_RESOURCEID=urn:mysitename.org:resource:ce # WMS_PEPC_RESOURCEID=urn:mysitename.org:resource:wms # GENERAL_PEPC_RESOURCEID=urn:mysitename.org:resource:other | ||||||||
Changed: | ||||||||
< < | 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: | ||||||||
Line: 137 to 173 | ||||||||
Then reconfigure with yaim your CREAM as usual | ||||||||
Changed: | ||||||||
< < | *4 - enable gLexec monitoring | |||||||
> > | 4 - enable gLexec monitoring | |||||||
Changed: | ||||||||
< < | 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 | |||||||
Deleted: | ||||||||
< < | -- AlessandroPaolini - 2012-02-24 | |||||||
\ No newline at end of file | ||||||||
Added: | ||||||||
> > | -- AlessandroPaolini - 2013-10-25 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Line: 84 to 84 | ||||||||
gLite Case | ||||||||
Changed: | ||||||||
< < | In case you want to install the ARGUS server on gLite, follow this guide; the yaim variables are the same | |||||||
> > | In case you want to install the ARGUS server on gLite, follow this guide plus the specific guide: the yaim variables are the same | |||||||
2 - Install and configure gLexec on your WNs |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Line: 70 to 70 | ||||||||
| ||||||||
Changed: | ||||||||
< < | Moreover, have a look at the Administrators guide in order to see how to create and manage the authorization policies (an example will be provided soon). | |||||||
> > | Moreover, have a look at the Administrators guide ore here in order to see how to create and manage the authorization policies (an example will be provided soon). | |||||||
Briefly the steps are the following: |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Added: | ||||||||
> > |
A guideline on how to deploy ARGUS and gLexec on own grid site<--/twistyPlugin twikiMakeVisibleInline--> Dear site admins, this message is relevant for sites supporting one or more LHC experiments, i.e. any of the VOs "alice", "atlas", "cms" or "lhcb". These VOs submit Multi User Pilot Jobs that are foreseen to make use of the "glexec" utility to run payloads of individual users. Deployment ---------- Please proceed with the deployment of gLExec as detailed on this page: https://twiki.cern.ch/twiki/bin/view/LCG/GlexecDeployment Monitoring ---------- The glexec setup of any EGI partner site can be monitored by the SAM-Nagios instance of the site's NGI or ROC: 1. The NGI/ROC needs to run SAM-Nagios Update-10 or later and configure it to run glexec tests (e.g. apply for "pilot" role in "ops" VO). 2. The _site_ should declare its CEs with the "gLExec" type in the GOC DB. These matters are further explained here: https://twiki.cern.ch/twiki/bin/view/LCG/GlexecDeployment#Monitoring_of_gLExec_tests Please apply the necessary configurations such that your CEs appear on the MyWLCG gLExec summary page (the link marked "NEW" on that page). <--/twistyPlugin-->thereby all the sites that belong to WLCG federation should install gLexec on their farm and make monitor it. Here you can see how to do it 1 - Install an ARGUS serverWe recommend to install the EMI Argus.EMI CaseUse 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
gLite CaseIn case you want to install the ARGUS server on gLite, follow this guide; the yaim variables are the same2 - Install and configure gLexec on your WNsWe recommend to install the EMI version of gLexec (and obviously EMI WN!). So that plan the migration to EMI of your farmEMI CaseYou 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 notesgLite Casefollow this guide in order to install the ig_GLEXEC_wn metapackage: the configuration files and the yaim variables to set are the same3 - properly configure your CREAMYou have to properly set 3 yaim variable in the site.def related to CREAM/ARGUS interaction
######################################### # ARGUS authorisation framework control # ######################################### # Set USE_ARGUS to yes to enable the configuration of ARGUS USE_ARGUS=yes # 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 resource identities: The resource ID can be set # for the cream CE, WMS and other nodes respectively. # If a resource ID is left unset the ARGUS configuration # will be skipped on the associated node. # 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"Don't forget to set in CE_CAPABILITY the glexec parameter, for example: CE_CAPABILITY="CPUScalingReferenceSI00=1039 glexec"Then reconfigure with yaim your CREAM as usual *4 - enable gLexec monitoringgo on https://gocdb4.esc.rl.ac.uk/portal/ and add the service endpoint "gLExec" to your CREAM -- AlessandroPaolini - 2012-02-24 |