svn commit: r1667933 - /vcl/site/trunk/content/docs/UpgradePreviousVersions/UpgradeFrom2.2.2to2.4.1.mdtext

[jf...@apache.org]

Author: jfthomps
Date: Fri Mar 20 05:05:14 2015
New Revision: 1667933

URL: http://svn.apache.org/r1667933
Log:
updated content for 2.4.1

Modified:
    vcl/site/trunk/content/docs/UpgradePreviousVersions/UpgradeFrom2.2.2to2.4.1.mdtext

Modified: vcl/site/trunk/content/docs/UpgradePreviousVersions/UpgradeFrom2.2.2to2.4.1.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/docs/UpgradePreviousVersions/UpgradeFrom2.2.2to2.4.1.mdtext?rev=1667933&r1=1667932&r2=1667933&view=diff
==============================================================================
--- vcl/site/trunk/content/docs/UpgradePreviousVersions/UpgradeFrom2.2.2to2.4.1.mdtext (original)
+++ vcl/site/trunk/content/docs/UpgradePreviousVersions/UpgradeFrom2.2.2to2.4.1.mdtext Fri Mar 20 05:05:14 2015
@@ -1,4 +1,4 @@
-Title: Upgrade From 2.2.2 to 2.4
+Title: Upgrade From 2.2.2 to 2.4.1
 Notice:    Licensed to the Apache Software Foundation (ASF) under one
            or more contributor license agreements.  See the NOTICE file
            distributed with this work for additional information
@@ -18,7 +18,7 @@ Notice:    Licensed to the Apache Softwa
 
 # Scripted Upgrade
 
-VCL 2.4 is the first release to include an upgrade script. All you need to
+VCL 2.4.1 is the first release to include an upgrade script. All you need to
 upgrade VCL is the script. It will download and validate the VCL software and
 then upgrade your system. The script can be used to upgrade all three parts of
 VCL (database, web portal, and management node) or to upgrade each part
@@ -65,13 +65,13 @@ for the code to run.
 
 # Manual Upgrade Instructions
 
-These instructions explain how to upgrade from VCL 2.2.2 to VCL 2.4. Please note 
-it only applies for the upgrade from 2.2.2 to 2.4, this may or may not work for other 
+These instructions explain how to upgrade from VCL 2.2.2 to VCL 2.4.1. Please note 
+it only applies for the upgrade from 2.2.2 to 2.4.1, this may or may not work for other 
 versions.
 
 **The basic steps that will be performed**
 
-  - Download and Extract 2.4 code 
+  - Download and Extract 2.4.1 code 
   - Shutdown httpd and vcld services
   - Create backup of vcl database 
   - Update mysql schema
@@ -83,11 +83,11 @@ versions.
 ### Upgrade steps
 
 1. follow instructions on the [VCL download](http://vcl.apache.org/downloads/download.cgi) 
-page to download and verify apache-VCL-2.4.tar.bz2 and put in in /root
-2. **extract VCL 2.4 code**
+page to download and verify apache-VCL-2.4.1.tar.bz2 and put in in /root
+2. **extract VCL 2.4.1 code**
     
         :::BashLexer
-        tar xf apache-VCL-2.4.tar.bz2
+        tar xf apache-VCL-2.4.1.tar.bz2
 
 3. **Shutdown** the httpd and vcld services
            
@@ -99,12 +99,12 @@ page to download and verify apache-VCL-2
 necessary.
 
         :::BashLexer
-        mysqldump vcl > ~/vcl-pre2.4-upgrade.sql
+        mysqldump vcl > ~/vcl-pre2.4.1-upgrade.sql
 
 5. This step **updates the database** schema.
 
         :::BashLexer
-        mysql vcl < /root/apache-VCL-2.4/mysql/update-vcl.sql
+        mysql vcl < /root/apache-VCL-2.4.1/mysql/update-vcl.sql
 
 6. **Update the web code**. This step we will move the 2.2.2 web directory out of the 
 way, so we can copy in the new web code base. After copying in the new code, we will 
@@ -123,8 +123,8 @@ VCL web code at /var/www/html/vcl. If yo
 7. **Copy the new code** in place
 	
         :::BashLexer
-        cp -r /root/apache-VCL-2.4/web /var/www/html/vcl-2.4
-        ln -s /var/www/html/vcl-2.4 /var/www/html/vcl
+        cp -r /root/apache-VCL-2.4.1/web /var/www/html/vcl-2.4.1
+        ln -s /var/www/html/vcl-2.4.1 /var/www/html/vcl
 
 8. **Copy your 2.2.2 config files**
 	
@@ -211,15 +211,15 @@ VCL management node code at /usr/local/v
         :::BashLexer
         cp -r /usr/local/vcl /usr/local/vcl-2.2.2
 
-13. **Copy in the 2.4 management node code** to /usr/local. First, rename the existing
-management node code directory to vcl-2.4 so that any drivers or other files you've 
+13. **Copy in the 2.4.1 management node code** to /usr/local. First, rename the existing
+management node code directory to vcl-2.4.1 so that any drivers or other files you've 
 added are preserved. Then, create a symlink for /usr/local/vcl and copy the new 
 management code over top of it.
 	
         :::BashLexer
-        mv /usr/local/vcl /usr/local/vcl-2.4
-        ln -s /usr/local/vcl-2.4 /usr/local/vcl
-        /bin/cp -r /root/apache-VCL-2.4/managementnode/* /usr/local/vcl
+        mv /usr/local/vcl /usr/local/vcl-2.4.1
+        ln -s /usr/local/vcl-2.4.1 /usr/local/vcl
+        /bin/cp -r /root/apache-VCL-2.4.1/managementnode/* /usr/local/vcl
 
 14. **Run install_perl_libs.pl** to add any new perl library requirements: