Upgrade Plan 290 II part

From D4Science Wiki
Revision as of 12:02, 13 July 2012 by Andrea.manzi (Talk | contribs) (→‎Upgrade)

Jump to: navigation, search

gHN Upgrade Instructions

It should be carried as follows:

1) Download the upgrade script from 

wget http://svn.research-infrastructures.eu/public/d4science/gcube/trunk/ghn-distribution/upgrade-scripts/upgrade-ghn-3-3-0.sh

and make it executable: 

chmod 700 upgrade-ghn-3-3-0.sh

2) Verify that the GLOBUS_LOCATION environment variable is correctly set 

echo $GLOBUS_LOCATION

3) Run the upgrade script with the following arguments:

  • <port>: The port where the container runs.
  • <restart/norestart>: tells if the container has to be restarted or not after the upgrade
./upgrade-ghn-3-3-0.sh <port> <restart/norestart>

Notes:

  • The script ask for the removal of previous GHNgCube Hosting Node. logs ( recommended )

4) Verify the upgrade operation using the infrastructure monitoring tools 

http://monitor.d4science.research-infrastructures.eu

Infrastructure (13 Jul AM)

A fix for the Deployer 2.3 needs to be deployed. (https://support.d4science-ii.research-infrastructures.eu/ticket/422)

  • DONE (CERN) node1.p.d4science.research-infrastructures.eu:8000: patch Deployer 2.3
  • DONE (CERN) node1.p.d4science.research-infrastructures.eu:8080: patch Deployer 2.3
  • DONE (CERN) node2.p.d4science.research-infrastructures.eu:8080: patch Deployer 2.3
  • DONE (CERN) node17.p.d4science.research-infrastructures.eu:8080: patch Deployer 2.3
  • DONE (CERN) node11.p.d4science.research-infrastructures.eu:8080: patch Deployer 2.3

gCubeApps VOVirtual Organization; (13 Jul AM)

A fix for the Deployer 2.3 needs to be deployed. (https://support.d4science-ii.research-infrastructures.eu/ticket/422)


  • DONE (CERN) node66.p.d4science.research-infrastructures.eu:8000: patch Deployer 2.3
  • DONE (CERN) node66.p.d4science.research-infrastructures.eu:8080: patch Deployer 2.3
  • (CERN) node65.p.d4science.research-infrastructures.eu:8080: patch Deployer 2.3
  • DONE (CERN) node36.p.d4science.research-infrastructures.eu:8080 : patch Deployer 2.3
  • DONE (CERN) rstudio.p.d4science.research-infrastructures.eu:8080 : patch Deployer 2.3
  • DONE (CERN) node39.p.d4science.research-infrastructures.eu:8080 : patch Deployer 2.3
  • DONE (CERN) node47.p.d4science.research-infrastructures.eu:8080 : patch Deployer 2.3
  • DONE (CERN) node49.p.d4science.research-infrastructures.eu:8080 : patch Deployer 2.3
  • DONE (CERN) node53.p.d4science.research-infrastructures.eu:8080 : patch Deployer 2.3
  • DONE (CERN) node54.p.d4science.research-infrastructures.eu:8080 : patch Deployer 2.3
  • DONE (CERN) node59.p.d4science.research-infrastructures.eu:8080 : patch Deployer 2.3
  • DONE (CERN) node60.p.d4science.research-infrastructures.eu:8080 : patch Deployer 2.3
  • DONE (CERN) node61.p.d4science.research-infrastructures.eu:8080 : patch Deployer 2.3
  • DONE (CERN) node62.p.d4science.research-infrastructures.eu:8080 : patch Deployer 2.3
  • DONE (CERN) node63.p.d4science.research-infrastructures.eu:8080 : patch Deployer 2.3
  • DONE (CERN) node64.p.d4science.research-infrastructures.eu:8080 : patch Deployer 2.3

FARM VOVirtual Organization;

FARM Enabling Services (12 Jul PM)

In order to enable the upgrade to the new Maven based dynamic deployment of packages, we need to have a procedure for the upgrade:

  • The old and new RM are incompatible, cause they use 2 different services for Dependencies resolution and deployment ( SR vs SG)
  • In order to undeploy the current installed packages we need to use the old version of the RM services
  • In parallel the new version should be deployed in order to perform the new deployment
  • In addition the undeployment of packages must be performed with the old version of the Deployer Service, while the deployment with the new one.
  • The flow of action is the following.
    • remove the service from VREVirtual Research Environment. scopes before performing the undeployment ( we fond a bug in this case (https://support.d4science-ii.research-infrastructures.eu/ticket/429), and nodes must be patched before removing the scope)
    • undeploy the service
    • upgrade the GHNgCube Hosting Node. to version 3.3.0
    • Deploy the upgraded service using the new version of the RM.

For this reason only the GHNs where we need to upgrade services are going to be upgraded to GHNgCube Hosting Node. 3.3.0

gHNs:


  • DONE (CNR) node24.p.d4science.research-infrastructures.eu:8080: upgrade node ( restart )
  • DONE (CNR) node26.p.d4science.research-infrastructures.eu:8080: upgrade node ( restart )
  • DONE (CNR) node32.p.d4science.research-infrastructures.eu:8000: upgrade node ( restart )

Services:

  • DONE (CNR) node26.p.d4science.research-infrastructures.eu:8080: upgrade IS-Registry
  • DONE (CNR) node32.p.d4science.research-infrastructures.eu:8000: install RM

Configuration:

The following RuntimeResource must be configured


  • DONE Geo Server
  • DONE GeoNetwork
  • DONE RStudio
  • DONE TimeSeries Database
  • DONE Ecological Modeling Database
  • DONE PostGis Database
  • Obis database
  • Species Link
  • Worms
  • CoL
  • Maven Repository
  • Transect


The SG must be added to FARM scope and 2.9.0 profile registered on this scope.

FARM VOVirtual Organization;/VREVirtual Research Environment. Services (13 Jul AM)

gHNs:

  • (FAO) ldvapp08.fao.org:8080: upgrade node (restart)
  • DONE (CNR) node14.p.d4science.research-infrastructures.eu:8080: upgrade node(restart)
  • DONE (CNR) node28.p.d4science.research-infrastructures.eu:8080: upgrade node(restart)
  • DONE (CNR) node44.p.d4science.research-infrastructures.eu:8080 : upgrade node (restart)
  • DONE (NKUA) dl16.di.uoa.gr:8084 : upgrade node (restart)
  • DONE (NKUA) dl25.di.uoa.gr:8084 : upgrade node (restart)


Services:

a patch to the previous version of the deployer is needed (https://support.d4science-ii.research-infrastructures.eu/ticket/429)

  • (CERN): ldvapp08.fao.org:8081 : patch Deployer 2.2
  • DONE (CERN) node6.p.d4science.research-infrastructures.eu:8000 : patch Deployer 2.2
  • DONE (CERN) node9.p.d4science.research-infrastructures.eu:8080 : patch Deployer 2.2
  • DONE (CERN) node23.p.d4science.research-infrastructures.eu:8080 : patch Deployer 2.2
  • DONE (CERN) node27.p.d4science.research-infrastructures.eu:8080 : patch Deployer 2.2
  • DONE (CERN) node30.p.d4science.research-infrastructures.eu:8080 : patch Deployer 2.2
  • DONE (CERN) node33.p.d4science.research-infrastructures.eu:8080 : patch Deployer 2.2
  • DONE (CERN) node38.p.d4science.research-infrastructures.eu:8080 : patch Deployer 2.2
  • DONE (CERN) node37.p.d4science.research-infrastructures.eu:8080: patch Deployer 2.2
  • DONE (CERN) dl17.di.uoa.gr:8080 : patch Deployer 2.2
  • (CERN) dl23.di.uoa.gr:8080 : patch Deployer 2.2
  • DONE (CERN) dl25.di.uoa.gr:8080 : patch Deployer 2.2
  • (CERN) node28.p.d4science.research-infrastructures.eu:8080:upgrade TS service
    • org.gcube.content-management.time-series.2-3-0
    • org.gcube.content-management.time-series-geo-tools.1-4-0
    • org.gcube.common.TSDBInterface.1-3-0
    • org.gcube.common.TSPostgresImplementation.1-3-0
    • org.gcube.common.GeoServerInterface.1-8-0
    • org.gcube.data-analysis.ecological-engine.1-2-0
    • org.gcube.content-management.codelist-manager.1-2-0
  • DONE (CERN) node44.p.d4science.research-infrastructures.eu:8080: upgrade VREModeler
  • DONE (CERN) node14.p.d4science.research-infrastructures.eu:8080: upgrade RM
  • (CERN) ldvapp08.fao.org:8080 : upgrade RM
  • (CERN) dl16.di.uoa.gr:8080: upgrade RM
  • (CERN) dl25.di.uoa.gr:8084: upgrade RM

Portals (13 July PM)

CNR is responsible for the portal upgrade activity, both D4science.org and Imarine portal need to complete their upgrade to gCube 2.9.0. The latest artifact build can be downloaded from:

http://grids16.eng.it/BuildReport/browse/Recent_Builds/org.gcube.2-9-0/BUILD_8


iMarine portal

Maven installation DONE

The new War Management portlet has introduced a dependency towards Maven client. The maven installation has been already performed on d4science.org portal so only Imarine portal is affected

In order to install the maven client on ubuntu node please type : 

sudo apt-get install maven2

once installed, the settings for gcube maven repository should be configured inside the file $HOME/.m2/settings.xml. Please check with the infrastructure-managers those settings

Upgrade

Artifacts are available at:

http://grids16.eng.it/BuildReport/browse/Recent_Builds/org.gcube.2-9-0/BUILD_9


new portlets:

  • org.gcube.portlets-user.species-discovery.1-0-0
  • org.gcube.application.aquamaps.aquamapsspeciesview.1-0-0

upgraded portlets:

  • org.gcube.messaging.accounting-portlet.1-6-0
  • org.gcube.messaging.monitoring-portlet.1-2-0
  • org.gcube.messaging.node-accounting-portlet.1-4-0
  • org.gcube.portlets-user.template-generator.3-4-0
  • org.gcube.portlets-user.report-generator-portlet.3-4-0
  • org.gcube.portlets-user.results-portlet.4-4-0
  • org.gcube.portlets-user.time-series-portlet.3-3-0
  • org.gcube.portlets-user.codelist-management-portlet.1-1-0
  • org.gcube.portlets-user.geoexplorer.1-1-0
  • org.gcube.portlets-user.gcube-geoexplorer.1-1-0
  • org.gcube.portlets-user.geoexplorer-portlet.1-1-0
  • org.gcube.portlets-user.workspace-portlet.5-0-0
  • org.gcube.portlets-user.war-management-portlet.1-1-1
  • org.gcube.portlets-user.web-application-management-portlet.1-1-1
  • org.gcube.portlets-user.wf-documents-portlet.1-1-0
  • org.gcube.portlets-admin.wf-docs-manager.1-1-0
  • org.gcube.application.aquamaps.aquamapsportlet.2-8-0
  • org.gcube.application.aquamaps.datamanagementfacilityportlet.1-4-0
  • org.gcube.portlets-user.gcube-login-portlet.1-6-0
  • org.gcube.portlets-admin.runtime-resource-creator.1-1-0

upgraded libraries:

  • org.gcube.portlets-user.war-management-widget.1-1-0
  • org.gcube.portlets-user.GISViewer.2-0-0
  • org.gcube.portlets-user.gcube-GISViewer.1-1-0
  • org.gcube.application.aquamaps.enhabling.iscrawler.1-2-0
  • org.gcube.messaging.accounting-portal.1-4-0
  • org.gcube.messaging.consumer-library.1-5-0
  • org.gcube.application.aquamaps.aquamapsservice-stubs.3-2-0
  • org.gcube.common.GeoServerInterface.1-8-0 ( to install from remote build cause the last fix is not available in the release).

new libraries:

  • species-products-discovery-stubs.1-0-0
  • tree-manager-stubs-1.0.0
  • tree-manager-library-1.0.0
  • tree-manager-framework-1.0.0
  • streams-.1.0.0
  • trees-1.0.0
  • common-gcore-clients-1.0.0
  • common-clients-1.0.0
  • org.gcube.vre-management.softwaregateway-client.1-0-0

Due to a problem in the previous upgrade operations, a lot of portal lib need to be restored from the backup server, the libs to be restored under $GLOBUS_LOCATION/lib/ext are the following:

DONE

  • commons-net-2.0.jar
  • datanucleus-cache-2.1.2.jar
  • datanucleus-core-2.2.3.jar
  • datanucleus-enhancer-2.1.3.jar
  • datanucleus-googlecollections-2.2.0-release.jar
  • datanucleus-javaxtime-2.1.2.jar
  • datanucleus-jdo-query-2.2.1.jar
  • datanucleus-jodatime-2.1.2.jar
  • datanucleus-jpa-2.1.7.jar
  • datanucleus-jpa-query-2.1.2.jar
  • datanucleus-ldap-2.2.1.jar
  • datanucleus-management-1.0.2.jar
  • datanucleus-rdbms-2.2.3.jar
  • DataTransformationHandlers.jar
  • G_CQLParser.jar
  • gcube-reporting-libray.jar
  • ij140g.jar
  • iText-2.1.4.jar
  • javassist.jar
  • jdo-api-3.1-SNAPSHOT-20110223.jar
  • jena.jar
  • mockito-all-1.8.5.jar
  • org.gcube.contentmanagement.contentmanager.stubs.jar
  • org.gcube.contentmanagement.gcubemodellibrary.jar
  • org.gcube.contentmanagement.lexicalmatcher.jar
  • org.gcube.contentmanagement.storagelayer.storagemanagementservice.stubs.jar
  • org.gcube.contentmanagement.timeseries.geotools.jar
  • org.gcube.contentmanagement.viewmanager.stubs.jar
  • org.gcube.datatransformation.datatransformationservice.stubs.jar
  • org.gcube.dir.master.stubs.jar
  • org.gcube.indexmanagement.forwardindexlookup.stubs.jar
  • org.gcube.indexmanagement.forwardindexmanagement.stubs.jar
  • org.gcube.indexmanagement.forwardindexupdater.stubs.jar
  • org.gcube.indexmanagement.fulltextindexlookup.stubs.jar
  • org.gcube.indexmanagement.fulltextindexmanagement.stubs.jar
  • org.gcube.indexmanagement.fulltextindexupdater.stubs.jar
  • org.gcube.indexmanagement.geoindexlookup.stubs.jar
  • org.gcube.indexmanagement.geoindexmanagement.stubs.jar
  • org.gcube.indexmanagement.geoindexupdater.stubs.jar
  • org.gcube.indexmanagement.incrementalindexupdater.stubs.jar
  • org.gcube.searchsystem.searchsystemservice.stubs.jar
  • ResourceRegistryAggregator.jar
  • RRGCubeBridge.jar
  • RRModel.jar
  • slf4j-api.jar
  • slf4j-log4j12.jar

for the same problem the following configuration files need to be restored under $GLOBUS_LOCATION/lib/_ext/property-files

  • config.gcubebridge.properties
  • datanucleus.buffer.properties
  • datanucleus.derby.properties
  • logging.rr.properties
  • targets.model.properties
Retrieved from "https://wiki.d4science.org/index.php?title=Upgrade_Plan_290_II_part&oldid=5758"