This file provides information on how to upgrade from VCL 2.1 to VCL 2.2. Please note it only applies for the upgrade from 2.1 to 2.2, this may or may not work for other versions.
The basic steps that will be
...
performed
- Download and Extract 2.2 code
- Shutdown httpd and vcld services
- Create backup of vcl database
- Update mysql schema
- Create backup of web directory
- Create backup of vcl directory
- Copy in 2.2 web directory make any changes
- Copy in 2.2 vcl directory make any changes/customizations
Restart httpd and vcld services- Update Web code, create a backup, copy in new, make changes
- Restart httpd service
- Update Management node vcl code, create a backup, copy in new, make changes
- Restart vcld service
Download and Extract 2.2 code
- follow instructions on VCL 2.2 Release page to download and verify apache-VCL-2.2-incubating.tar.bz2 and put in in /root
- extract VCL 2.2 code
Code Block |
---|
tar xjf apache-VCL-2.2-incubating.tar.bz2
|
Shutdown services
Shutdown the httpd and vcld services
...
We will create a backup of the vcl database. This will provide a restore point if necessary.
Code Block |
---|
mysqlmysqldump vcl dump command> ~/vcl-pre2.2-upgrade.sql
|
Update mysql schema
This step updates the mysql schema.
Code Block |
---|
cd to vcl2.2 source directory
cd /<path to vcl 2.2 source>
/root/apache-VCL-2.2-incubating
mysql vcl < mysql/update-2.2.sql
|
...
This step we will move the 2.1 web directory out of the way, so we can copy in the new web code base. After copying in the new code, we will migrate any of your configuration changes, etc.
...
. These instructions assume that you installed the vcl web code at /var/www/html/vcl. If you installed it elsewhere, replace /var/www/html/vcl with your vcl web root.
- copy your old code out of the way
Code Block |
---|
cd /var/www/html
mv vcl ~/vcl_2.1_web
|
- copy the new code in place
Code Block |
---|
cd /root/apache-VCL-2.2-incubating
cp -r web /var/www/html/vcl
|
- copy your 2.1 config files
Code Block |
---|
cpcd ~/vcl_2.1_web/.ht-inc/conf.php
cp conf.php secrets.php pubkey.pem keys.pem /var/www/html/vcl/.ht-inc
|
- make /var/www/html/vcl/.ht-inc/maintenance writable by the web server - if httpd on your server is running as the user apache:
Code Block |
---|
chown apache /var/www/html/vcl/.ht-inc/maintenance
|
- add the following new entries to conf.php - You can copy them in from .ht-inc/conf.php
....-default.php. Descriptions of each item can also be found in conf-default.php
- date_default_timezone_set('America/New_York');
- $blockNotifyUsers = "adminuser@example.org";
- define("SCHEDULER_ALLOCATE_RANDOM_COMPUTER", 0);
- define("DOCUMENTATIONURL", "https://cwiki.apache.org/VCLDOCS/");
- define("USEFILTERINGSELECT", 1);
- define("FILTERINGSELECTTHRESHOLD", 1000);
- define("DEFAULTTHEME", 'default');
Restart httpd service
Code Block |
---|
service httpd start or /etc/init.d/httpd start
|
Update management node code
This step will move the 2.1 vcl code base out of the way, so we can cleanly copy in the new management node(MN) code.
- Copy 2.1 code base to a backup location
Code Block |
---|
cd <your vcl MN code root path>
ie. cd /usr/local/
|
...
cp -r vcl ~/vcl_2.1_managementnode
|
- Copy in the 2.2 code base to /usr/local, copying in should preserve any drivers or other files you've added.
Code Block |
---|
/bin/cp -r /root/apache-VCL-2.2-incubating/managementnode/* /usr/local/vcl
|
- Make changes related to vcld.conf settings
- Open VCL web interface
- Go to Management Nodes
- Select Edit Management Node Information
- Select Edit.
- Set any relevant fields:
- SysAdmin Email Address(es) - comma delimited list of vcl admin email addresses
- Address for Shadow Emails - a shared mail box, optional it receives email of all notifications
- Public NIC configuration method - Defines what type of NIC configuration is used, options are dynamic DHCP, Manual DHCP, or static
- End Node SSH Identity Key Files
Restart vcld service
Code Block |
---|
service vcld start or /etc/init.d/vcld startmanagement_node
|