Difference between revisions of "Upgrade UMD2"

From D4Science Wiki
Jump to: navigation, search
(CNR-PROD-PISA [http://gstat-prod.cern.ch/gstat/site/CNR-PROD-PISA/] upgrade details)
 
(7 intermediate revisions by the same user not shown)
Line 4: Line 4:
  
 
The UMD ( http://knowledge.eu-egi.eu/knowledge/index.php/UMD) software is the middleware integrated starting from the EMI software, which it's being deployed in the EGI infrastructure.
 
The UMD ( http://knowledge.eu-egi.eu/knowledge/index.php/UMD) software is the middleware integrated starting from the EMI software, which it's being deployed in the EGI infrastructure.
The latest version released is the 2.4 ( http://repository.egi.eu/2013/02/18/release-umd-2-4-0/)  
+
The latest version released is the 2.4 ( http://repository.egi.eu/category/umd_releases/distribution/umd-2/)  
  
 
The main reason of the middleware upgrade is the end of the support of all components  running UMD1.
 
The main reason of the middleware upgrade is the end of the support of all components  running UMD1.
Line 21: Line 21:
 
* WMS (dl06.di.uoa.gr)
 
* WMS (dl06.di.uoa.gr)
  
and the service specific installation instructions:
+
== CNR-PROD-PISA [http://gstat-prod.cern.ch/gstat/site/CNR-PROD-PISA/] upgrade details ==
  
* DPM -> http://repository.egi.eu/2012/01/30/dpm-1-8-2/
+
The sites as reported on the [http://wiki.i-marine.eu/index.php/GLite_Resources|gLite resource page], is running the following UMD 1 services:
* CREAM -> http://repository.egi.eu/2012/01/30/cream-1-13-3/
+
* WN -> http://repository.egi.eu/2011/07/11/torque-wn-config-1-0-0/
+
* APEL -> http://repository.egi.eu/2011/12/19/apel-publisher-3-2-8/
+
* BDII site -> http://repository.egi.eu/2011/10/31/bdii-site-1-0-1/
+
* LB -> http://repository.egi.eu/2012/01/30/logging-and-bookkeeping-3-1-0/
+
* UI -> http://repository.egi.eu/2011/07/11/user-interface-1-0-0/
+
* WMS -> http://repository.egi.eu/2012/01/30/workload-management-system-3-3-4/.
+
  
== d4science VO Configuration ==
+
* WNs ( wn01.research-infrastructures.eu, wn03.research-infrastructures.eu, wn04.research-infrastructures.eu, wn05.research-infrastructures.eu, wn07.research-infrastructures.eu)
 +
* BDII site (lcg-ce.research-infrastructures.eu)
 +
* UI (ui.grid.research-infrastructures.eu)
 +
* CREAM-CE  (cream-ce.research-infrastructures.eu):
 +
* DPM (dpm.research-infrastructures.eu)
 +
* LB ( lb.research-infrastructures.eu)
 +
* LFC ( lfc.research-infrastructures.eu)
 +
* VOMS (voms.research-infrastructures.eu)
 +
* WMS (wms.resaearch-infrastructures.eu)
  
You can find specific configuration for the D4science VO at:
+
==Upgrade Info ==
  
http://wiki.i-marine.eu/index.php/D4science_VO_configuration_parameters
+
A list of all Available UMD components is available at [http://repository.egi.eu/2012/07/10/all-umd-2-products/]
 +
 
 +
For most of the services is needed  just to configured the new repos and perform an upgrade of the packages. A reconfiguration trough yaim is also requested
 +
 
 +
* DPM -> http://repository.egi.eu/2013/02/18/dpm-1-8-6/
 +
* CREAM -> http://repository.egi.eu/2013/02/18/cream-torque-module-2-0-0-2/
 +
* WN -> http://repository.egi.eu/2012/11/20/emi-wn-2-0-1/
 +
* APEL -> http://repository.egi.eu/2012/07/10/apel-publisher-3-3-0/
 +
* BDII site -> http://repository.egi.eu/2012/07/10/bdii-site-1-1-0-2/
 +
* LB -> http://repository.egi.eu/2012/11/20/lb-3-2-8/
 +
* UI -> http://repository.egi.eu/2012/11/20/emi-ui-2-0-1/
 +
* WMS ->http://repository.egi.eu/2013/02/18/wms-3-4-0/
 +
** http://www.eu-emi.eu/emi-2-matterhorn/updates/-/asset_publisher/9AgN/content/update-4-23-10-2012-v-2-4-0-1#WMS_v_3_4_Task_21060
 +
* VOMS -> http://repository.egi.eu/2013/02/18/voms-2-0-10/
 +
* LFC -> http://repository.egi.eu/2013/02/18/lfc-1-8-6/

Latest revision as of 14:23, 2 March 2013

Overview

The UMD ( http://knowledge.eu-egi.eu/knowledge/index.php/UMD) software is the middleware integrated starting from the EMI software, which it's being deployed in the EGI infrastructure. The latest version released is the 2.4 ( http://repository.egi.eu/category/umd_releases/distribution/umd-2/)

The main reason of the middleware upgrade is the end of the support of all components running UMD1.

GR-09-UOA [1] upgrade details

The sites as reported on the resource page, is running the following UMD1 services:

  • WNs ( dl03.di.uoa.gr, dl04.di.uoa.gr, dl30.di.uoa.gr, dl31.di.uoa.gr, dl32.di.uoa.gr)
  • BDII site (dl01.di.uoa.gr)
  • UI (dl05.di.uoa.gr)
  • LB ( dl29.di.uoa.gr)
  • APEL (dl24.di.uoa.gr)
  • CREAM-CE (dl11.di.uoa.gr):
  • DPM (dl02.di.uoa.gr)
  • WMSSee Workload Management System or Web Mapping Service. (dl06.di.uoa.gr)

CNR-PROD-PISA [2] upgrade details

The sites as reported on the resource page, is running the following UMD 1 services:

  • WNs ( wn01.research-infrastructures.eu, wn03.research-infrastructures.eu, wn04.research-infrastructures.eu, wn05.research-infrastructures.eu, wn07.research-infrastructures.eu)
  • BDII site (lcg-ce.research-infrastructures.eu)
  • UI (ui.grid.research-infrastructures.eu)
  • CREAM-CE (cream-ce.research-infrastructures.eu):
  • DPM (dpm.research-infrastructures.eu)
  • LB ( lb.research-infrastructures.eu)
  • LFC ( lfc.research-infrastructures.eu)
  • VOMSVirtual Organization Membership Service. (voms.research-infrastructures.eu)
  • WMSSee Workload Management System or Web Mapping Service. (wms.resaearch-infrastructures.eu)

Upgrade Info

A list of all Available UMD components is available at [3]

For most of the services is needed just to configured the new repos and perform an upgrade of the packages. A reconfiguration trough yaim is also requested