Page History

...

1. follow instructions on VCL 2.3 Release page to download and verify apache-VCL-2.3-incubating.tar.bz2 and put in in /root
2. extract VCL 2.3 code

   Tip
   tar xjf apache-VCL-2.3-incubating.tar.bz2

Shutdown services

...

1. This step updates the mysql schema.

   Tip
   cd /root/apache-VCL-2.3-incubating mysql vcl < mysql/update-vcl.sql

   
   One item of note: A new resource group is added in update-vcl.sql - all profiles. Access to manage the group is added to the VCL->admin node in the privilege tree if that node exists. If not, you will need to add it manually after starting httpd again. To add it manually, pick a node in the privilege tree, scroll to Resources, click Add Resource Group, select serverprofile/all profiles from the drop-down box, check available, administer, manageGroup, and manageMapping, and click Submit New Resource Group.
   
   
2. Grant CREATE TEMPORARY TABLES to mysql user
   The web code now requires access to create temporary tables in mysql. You need to grant the user your web code uses to access mysql the "CREATE TEMPORARY TABLES" permission. Look at the secrets.php file in your web code for the user and hostname. For example, if your web code is installed at /var/www/html/vcl, your secrets.php file would be /var/www/html/vcl/.ht-inc/secrets.php. Look for $vclhost and $vclusername. The secrets.php file might have something like:

   Info
   $vclhost = 'localhost'; $vcluser = 'vcluser';

   Then, you need to issue the grant command to mysql. Using the values from above as examples, connect to mysql and then issue the grant command:

   Tip
   mysql GRANT CREATE TEMPORARY TABLES ON `vcl`.* TO 'vcluser'@'localhost'; exit

...

1. move your old code out of the way

   Tip
   cd /var/www/html mv vcl ~/vcl_2.1_web

2. copy the new code in place

   Tip
   cd /root/apache-VCL-2.3-incubating cp -r web /var/www/html/vcl

3. copy your 2.1 config files

   Tip
   cd ~/vcl_2.1_web/.ht-inc cp secrets.php pubkey.pem keys.pem /var/www/html/vcl/.ht-inc

4. Make the maintenance directory writable by the web server user. You will need to know what user httpd runs as on your server. This can be found with

   Tip
   ps aux | grep httpd

   Look at the first column. One process will be owned by root. The remaining processes will be owned by the web server user. Now, own /var/www/html/vcl/.ht-inc/maintenance to that user (replacing 'apache' with your web server user if different):

   Tip
   chown apache /var/www/html/vcl/.ht-inc/maintenance

5. update conf.php. When upgrading from 2.1, it is recommended to start with a fresh copy of conf-default.php from 2.3 and then apply your changes to it again.

   Tip
   cd /var/www/html/vcl/.ht-inc cp conf-default.php conf.php

   Look at each value in the top section labeled Things in this section must be modified and set the value to what you had in your old conf.php file. If you are using LDAP authentication, you can copy all entries from $authMech out of your 2.1 conf.php file into your 2.3 conf.php file. However, note that you will need to add the following two additional keys to each entry. A description of these keys can be found in the 2.3 conf-default.php file.

   Tip
   "lookupuserbeforeauth" => 0, "lookupuserfield" => '',

...

1. Copy 2.1 code base to a backup location

   Tip
   cd <your vcl MN code root path> ie. cd /usr/local/ cp -r vcl ~/vcl_2.1_managementnode

2. Copy in the 2.3 code base to /usr/local, copying in should preserve any drivers or other files you've added.

   Tip
   /bin/cp -r /root/apache-VCL-2.3-incubating/managementnode/* /usr/local/vcl

3. Run install_perl_libs.pl to add any new perl library requirements:

   Tip
   /usr/local/vcl/bin/install_perl_libs.pl

...