Upgrade Plan 290 II part

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

FARM VOVirtual Organization;

FARM Enabling Services (xx Jul 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.