Difference between revisions of "GHN upgrade 330"

From D4Science Wiki
Jump to: navigation, search
(Created page with "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 ex...")
 
 
(One intermediate revision by the same user not shown)
Line 10: Line 10:
 
3) Run the upgrade script with the following arguments:
 
3) Run the upgrade script with the following arguments:
 
* <port>: The port where the container runs.
 
* <port>: The port where the container runs.
* <restart/norestart>: tells if the container has to be restarted or not after the upgrade
+
* norestart: the container has not to be restarted after the upgrade
  ./upgrade-ghn-3-3-0.sh <port> <restart/norestart>
+
  ./upgrade-ghn-3-3-0.sh <port> norestart
  
 
Notes:
 
Notes:
Line 17: Line 17:
  
 
4) Verify the upgrade operation using the infrastructure monitoring tools
 
4) Verify the upgrade operation using the infrastructure monitoring tools
  http://monitor.d4science.research-infrastructures.eu
+
 
 +
  http://www.d4science.org/web/guest/monitor

Latest revision as of 16:00, 17 October 2012

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.
  • norestart: the container has not to be restarted after the upgrade
./upgrade-ghn-3-3-0.sh <port> 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://www.d4science.org/web/guest/monitor