Upgrade Plan 290 Ecosystem

From D4Science Wiki
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

Ecosystem VOVirtual Organization;

Ecosystem Enabling Services (22 Jun AM)

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.


gHNs:

  • DONE (CERN) node7.p.d4science.research-infrastructures.eu:8080: upgrade node (restart)
  • (CERN) node8.p.d4science.research-infrastructures.eu:8080: upgrade node (restart)
  • DONE (CERN) node10.p.d4science.research-infrastructures.eu:8080: upgrade node (restart)
  • DONE ((CERN) dl28.di.uoa.gr:8080: upgrade node(restart)

Services:

  • DONE (CERN) node7.p.d4science.research-infrastructures.eu:8080: upgrade IS-Registry
  • (CERN) node8.p.d4science.research-infrastructures.eu:8080: upgrade RM
  • DONE (CERN) dl28.di.uoa.gr:8080: install RM

Configuration:

The following RuntimeResource must be Added to Ecosystem Scope

  • Maven Repository

gHNs:

  • (CNR) node1.hadoop.d4science.research-infrastructures.eu:8080: upgrade node ( restart )
  • (CNR) node6.p.d4science.research-infrastructures.eu:8080: upgrade node ( restart )
  • (CNR) node13.p.d4science.research-infrastructures.eu:8080: upgrade node ( restart )
  • (CNR) node20.p.d4science.research-infrastructures.eu:8080: upgrade node ( restart )
  • (CNR) node22.p.d4science.research-infrastructures.eu:8080: upgrade node ( restart )
  • (CNR) node25.p.d4science.research-infrastructures.eu:8080: upgrade node ( restart )
  • (CNR) node29.p.d4science.research-infrastructures.eu:8080: upgrade node ( restart )
  • (CNR) node31.p.d4science.research-infrastructures.eu:8080: upgrade node ( restart )
  • (CNR) node40.p.d4science.research-infrastructures.eu:8080: upgrade node ( restart )
  • (CNR) node41.p.d4science.research-infrastructures.eu:8080: upgrade node ( restart )
  • (CNR) node43.p.d4science.research-infrastructures.eu:8080: upgrade node ( restart )
  • (CNR) node46.p.d4science.research-infrastructures.eu:8080: upgrade node ( restart )
  • (CNR) node51.p.d4science.research-infrastructures.eu:8080: upgrade node ( restart )
  • (CNR) node55.p.d4science.research-infrastructures.eu:8080: upgrade node ( restart )
  • (CNR) node56.p.d4science.research-infrastructures.eu:8080: upgrade node ( restart )
  • (CNR) node57.p.d4science.research-infrastructures.eu:8080: upgrade node ( restart )
  • (NKUA) dewn01.madgik.di.uoa.gr:8080:upgrade node ( restart )
  • (NKUA) dewn02.madgik.di.uoa.gr:8080:upgrade node ( restart )
  • (NKUA) dewn03.madgik.di.uoa.gr:8080:upgrade node ( restart
  • (NKUA) dewn04.madgik.di.uoa.gr:8080:upgrade node ( restart )
  • (NKUA) dewn05.madgik.di.uoa.gr:8080:upgrade node ( restart )
  • (NKUA) dewn06.madgik.di.uoa.gr:8080:upgrade node ( restart )
  • (NKUA) dewn07.madgik.di.uoa.gr:8080:upgrade node ( restart )
  • DONE (NKUA) dewn08.madgik.di.uoa.gr:8080:upgrade node ( restart )
  • DONE (NKUA) dewn09.madgik.di.uoa.gr:8080:upgrade node ( restart )
  • DONE (NKUA) dewn10.madgik.di.uoa.gr:8080:upgrade node ( restart )
  • (NKUA) mlhec4.di.uoa.gr:8080:upgrade node ( restart )
  • (NKUA) mln11.di.uoa.gr:8080:upgrade node ( restart )
  • (NKUA) ocr5.madgik.di.uoa.gr:8080:upgrade node ( restart )
  • (NKUA) dl17.di.uoa.gr:8084:upgrade node ( restart )
  • (NKUA) dl18.di.uoa.gr:8080:upgrade node ( restart )
  • (NKUA) dl18.di.uoa.gr:8084::upgrade node ( restart )
  • (NKUA) dl19.di.uoa.gr:8080::upgrade node ( restart )
  • (NKUA) dl19.di.uoa.gr:8084::upgrade node ( restart )
  • (NKUA) dl20.di.uoa.gr:8084::upgrade node ( restart )
  • (NKUA) dl21.di.uoa.gr:8080::upgrade node ( restart )
  • (NKUA) dl21.di.uoa.gr:8084::upgrade node ( restart )
  • (NKUA) dl26.di.uoa.gr:8084::upgrade node ( restart )
  • (NKUA) dl27.di.uoa.gr:8080::upgrade node ( restart )
  • (NKUA) dl27.di.uoa.gr:8084::upgrade node ( restart )
  • (NKUA) dl28.di.uoa.gr:8080::upgrade node ( restart )


Services:

  • DONE (NKUA) dewn08.madgik.di.uoa.gr:8080:upgrade Execution Engine Service
  • DONE (NKUA) dewn09.madgik.di.uoa.gr:8080:upgrade Execution Engine Service
  • DONE (NKUA) dewn10.madgik.di.uoa.gr:8080:upgrade Execution Engine Service
Retrieved from "https://wiki.d4science.org/index.php?title=Upgrade_Plan_290_Ecosystem&oldid=5623"